As a noob I'm realizing I might have gotten pretty lucky. I've never rooted a phone (and probably won't - can't live without it if it bricks!) but I successfully rooted my Kindle on the first try and have been fooling around with various ROMs and have had only seemingly trivial issues. I started with Android Open Kang Project - otter - milestone 6. I can't even remember now the particulars of what I didn't like about it but I quickly switched to CM10 Jelly Bean with SG17 enhancements [linaro]. I liked it but had some instability with 20120916 so installed 20120920 which has been more stable for me so far. I also installed the UNOFFICIAL CM10 +3.x kernel for kindle fire but switched back alley because it didn't have a tablet UI (so odd since it's a build specifically for the kindle - did I overlook the setting???]
So my questions are:
How lucky have I been? Should I look for an older totally stable ROM and stick with it or even go back to stock?
If I do decide to continue experimenting what level of risk is it really to look for the ROM that I like - e.g. tablet UI, pretty basic, quick - vs looking solely for something rock solid.
Finally, what advice for a noob on what to look for and how to test various ROMs and any thoughts on your favorite for the Fire and why.
BTW, I also tried eye candy and did not care for it. In fact I'm irritated that my twrp was sort of hijacked with an eye candy mod and I can't figure out how to get it off. Have not loaded jandycane but want to because I can. Pushing that luck?
Sent from my Amazon Kindle Fire using xda app-developers app
I wanted to edit typos and add that use GO Launcher EX so the launcher features of the ROM are irrelevant. Don't see an edit option...
Sent from my Amazon Kindle Fire using xda app-developers app
Running custom roms are not for everyone. They normally come with some needed trouble shooting. As long as you do your needed research before hand you will be fine but there is always a risk when rewritting the OS on any device. Be it cellphone, tablet or PC.
No one will be able to tell you what is the best for your device. Its a flash and test yourself type of thing
Sent from my SGH-I777 using Tapatalk 2
sharonbw said:
As a noob I'm realizing I might have gotten pretty lucky. I've never rooted a phone (and probably won't - can't live without it if it bricks!) but I successfully rooted my Kindle on the first try and have been fooling around with various ROMs and have had only seemingly trivial issues. I started with Android Open Kang Project - otter - milestone 6. I can't even remember now the particulars of what I didn't like about it but I quickly switched to CM10 Jelly Bean with SG17 enhancements [linaro]. I liked it but had some instability with 20120916 so installed 20120920 which has been more stable for me so far. I also installed the UNOFFICIAL CM10 +3.x kernel for kindle fire but switched back alley because it didn't have a tablet UI (so odd since it's a build specifically for the kindle - did I overlook the setting???]
So my questions are:
How lucky have I been? Should I look for an older totally stable ROM and stick with it or even go back to stock?
If I do decide to continue experimenting what level of risk is it really to look for the ROM that I like - e.g. tablet UI, pretty basic, quick - vs looking solely for something rock solid.
Finally, what advice for a noob on what to look for and how to test various ROMs and any thoughts on your favorite for the Fire and why.
BTW, I also tried eye candy and did not care for it. In fact I'm irritated that my twrp was sort of hijacked with an eye candy mod and I can't figure out how to get it off. Have not loaded jandycane but want to because I can. Pushing that luck?
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
Rooting and installing ROMs may not be everyone's forte, but there is nothing to fear if you've done every step correctly. Many of these CM builds are nightly builds; that is they release one every short interval of time fixing small bugs encountered in the previous release. If you really want to enjoy CM, you could go for the latest stable build.
To your first question: Yeah, switch back to an older ROM. That's generally more stable and you have the whole thread to sort through if you get into some tough spot. You've been pretty lucky to have gotten so far without bricking your device, I must say. I don't recommend reverting back to stock; you'd miss a lot of the features that aren't there on the KF.
To your second one: that's totally up to you. I confess, I don't own a KF, but with the phones I've had, I've always been experimenting with them. My old Moto Razr, my Moto Ming, my Nokia 5800, my Nokia N8...the list goes on. Changing ROMs, it's kind of like an hobby of mine.
You could lean towards a better UI( I really like the one on stock KF though) or a rock solid feature rich performance ROM. It's up to you.
As to your third question: I can't really answer that sorry. I'm a Galaxy Tab user, so I don't know much about KFs. As to testing ROMs, well, you said it. Test them. There's no other way to know if you're going to like them or not otherwise.
Yes, install Jandycane. It's not pushing your luck. There's no room for error unless you're so excited that you even make silly mistakes.
You can modify posts by tapping on it, selecting Modify, then edit.
Hope I helped you some.
One ****ing minute! - Billie Joe Armstrong at iHeartRadio Music Fest 2012
It's not luck if u spent time reading n following the rooting tutorial, it's ur work, though small compared to developers. I'm exactly like u, 1st time ever use an android device, but with experience with my Nokia5800, it's easier for me to solve problems, not to panic when rooting a device .
For me, keep rooting different Roms until the most suitable for personal use is enough. As time passes, I feel tired of doing the setting again after installing every new Rom. I stick with twa 's Linaro 'til now.
I think the risk of experimenting new Rom is small because the device memory is very hard to malfunction. As long as ur PC and KF is there, u don't have to worry.
There's still a lot to learn abt android, not only rooting, I think. Right now I'm learning about OTG and how to use external devices with KF, like flash drive or microphone.
All credits and thanks to our developers such as hashcode and twa.
Sent from my Amazon Kindle Fire using Tapatalk 2
Thanks for the replies. I did go ahead and play around wiping and installing new ROMs starting with going back to stock all the way through pretty much the same sequence I did before with the same result LOL! I ended right back here with tw_priv's CM10. I like it very much and other than some random burps and glitches I've experienced - things others have also seen (Facebook - keyboard not opening; sleep of death - multiple times; WWF is totally messed up but that might be 100% zynga), its been pretty darn stable.
My biggest issue is that my battery life sucks! Anyone want to advise me on how to analyze/improve that?
I love reading here and learning but I'll never be a dev or even a power user. Do the dev of custom ROMs even want people like me to use them? This site is definitely not user friendly ha ha
Sent from my Amazon Kindle Fire using xda app-developers app
sharonbw said:
Thanks for the replies. I did go ahead and play around wiping and installing new ROMs starting with going back to stock all the way through pretty much the same sequence I did before with the same result LOL! I ended right back here with tw_priv's CM10. I like it very much and other than some random burps and glitches I've experienced - things others have also seen (Facebook - keyboard not opening; sleep of death - multiple times; WWF is totally messed up but that might be 100% zynga), its been pretty darn stable.
My biggest issue is that my battery life sucks! Anyone want to advise me on how to analyze/improve that?
I love reading here and learning but I'll never be a dev or even a power user. Do the dev of custom ROMs even want people like me to use them? This site is definitely not user friendly ha ha
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
That's what you get for a $200 tablet sorry. You could look around your device forum asking for prop.build tweak that optimize battery life.
You'll understand all the big dev terms sooner or later. Its just a matter of time.
Sent from my GT-S5360 using Tapatalk 2
zelendel said:
Running custom roms are not for everyone. They normally come with some needed trouble shooting. As long as you do your needed research before hand you will be fine but there is always a risk when rewritting the OS on any device. Be it cellphone, tablet or PC.
No one will be able to tell you what is the best for your device. Its a flash and test yourself type of thing
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
I know this is off topic, I'm sorry. But I don't see any risk with rewriting the OS of a PC versus a Phone. A Phone has a rom chip that is fairly easy to break. By unplugging the device during rooting, for example. But on a PC, if something goes wrong, you can always stick the disc in and try again.
On topic, with custom roms you will always run into stability issues. However, if you do not care about the latest and greatest, try a rom based on CM7. They are stable (in use for years on different devices)
x10knight said:
I know this is off topic, I'm sorry. But I don't see any risk with rewriting the OS of a PC versus a Phone. A Phone has a rom chip that is fairly easy to break. By unplugging the device during rooting, for example. But on a PC, if something goes wrong, you can always stick the disc in and try again.
On topic, with custom roms you will always run into stability issues. However, if you do not care about the latest and greatest, try a rom based on CM7. They are stable (in use for years on different devices)
Click to expand...
Click to collapse
There are many things that could go wrong when rewritting the OS on your PC that could make that not an option.
Sent from Arkham
My battery life (which wasn't terrible "cheap" tablet or not - this is the kindle fire forum, right?) got worse after I rooted it and flashed custom ROM. I had hoped it would get better since that seems to be something all the devs are after. I was hoping someone could point out settings I may not have adjusted correctly after installing. Or would that be too easy?
Sent from my Amazon Kindle Fire using xda app-developers app
sharonbw said:
My battery life (which wasn't terrible "cheap" tablet or not - this is the kindle fire forum, right?) got worse after I rooted it and flashed custom ROM. I had hoped it would get better since that seems to be something all the devs are after. I was hoping someone could point out settings I may not have adjusted correctly after installing. Or would that be too easy?
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
Yes, it is the KF forum. You could try underclocking the device. That way, less CPU and more battery. If you could point out your current ROM, I'll take a deeper look and help you out.
Sent from my asus_laptop using Tapatalk 2
gadgetroid said:
Yes, it is the KF forum. You could try underclocking the device. That way, less CPU and more battery. If you could point out your current ROM, I'll take a deeper look and help you out.
Sent from my asus_laptop using Tapatalk 2
Click to expand...
Click to collapse
I appreciate the offer! This is the first rooted device I've had. I don't really know what underclocking is but would like to learn. I'm using twa_priv's ROM 20120923 (I think - maybe 25)
Sent from my Amazon Kindle Fire using xda app-developers app
sharonbw said:
I appreciate the offer! This is the first rooted device I've had. I don't really know what underclocking is but would like to learn. I'm using twa_priv's ROM 20120923 (I think - maybe 25)
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
CM9 and CM10 roms (the one you are using is CM10) tend to have worse battery life than other ROMs. It's kind of a trade-off, worse battery for more functionality. If you want really great battery life, you could use one of the old CM7 roms. They'll likely have the best overall battery life, but won't be quite as fancy/snappy as the newer ROMs would be.
Aesrys said:
CM9 and CM10 roms (the one you are using is CM10) tend to have worse battery life than other ROMs. It's kind of a trade-off, worse battery for more functionality. If you want really great battery life, you could use one of the old CM7 roms. They'll likely have the best overall battery life, but won't be quite as fancy/snappy as the newer ROMs would be.
Click to expand...
Click to collapse
Yes, that's true.
@OP underclocking means that you simply set the CPU to operate at a give frequency. It doesn't go more than that. My Android tablet has an Intel Core i3-350M 2.26 GHz processor. Average battery life is around an hour; but then when I underclock it to 800MHz, I get close to five hours.
Sent from my asus_laptop using Tapatalk 2
gadgetroid said:
Yes, that's true.
@OP underclocking means that you simply set the CPU to operate at a give frequency. It doesn't go more than that. My Android tablet has an Intel Core i3-350M 2.26 GHz processor. Average battery life is around an hour; but then when I underclock it to 800MHz, I get close to five hours.
Sent from my asus_laptop using Tapatalk 2
Click to expand...
Click to collapse
I have some issues w/ sleep of death. I saw a post that suggested doubling minimum CPU frequency. Is that underclocking or overclocking or neither??
Clock data: min 300 Max 1200 current 300
CPU - whatever comes in the kindle fire. :8
Sent from my Amazon Kindle Fire using xda app-developers app
sharonbw said:
I have some issues w/ sleep of death. I saw a post that suggested doubling minimum CPU frequency. Is that underclocking or overclocking or neither??
Clock data: min 300 Max 1200 current 300
CPU - whatever comes in the kindle fire. :8
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
You're at 300 MHz? Wow! That's way too slow! I even wonder how you get most of the jobs done. You're underclocking the device. If you're having Sleep of death issues, then increase the frequency to about 600 MHz. That should take care of it. Also, that won't eat up much battery, so you should be safe. But, as suggested, you should switch to older CM7 ROMs as they have excellent battery backup.
Sent from my asus_laptop using Tapatalk 2
gadgetroid said:
You're at 300 MHz? Wow! That's way too slow! I even wonder how you get most of the jobs done. You're underclocking the device. If you're having Sleep of death issues, then increase the frequency to about 600 MHz. That should take care of it. Also, that won't eat up much battery, so you should be safe. But, as suggested, you should switch to older CM7 ROMs as they have excellent battery backup.
Sent from my asus_laptop using Tapatalk 2
Click to expand...
Click to collapse
[Q] Why would it be set that low in the first place? What is "normal"? Also is the type of CPU governor significant? Mine is defaulted to interactive.
I'll try upping frequency and see how it does. My battery life is OK - just not as good as it was pre-root/custom. I love my CM10 ROM so I will probably just live with it. (twa_priv's)
Sent from my Amazon Kindle Fire using xda app-developers app
sharonbw said:
[Q] Why would it be set that low in the first place? What is "normal"? Also is the type of CPU governor significant? Mine is defaulted to interactive.
I'll try upping frequency and see how it does. My battery life is OK - just not as good as it was pre-root/custom. I love my CM10 ROM so I will probably just live with it. (twa_priv's)
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
The KF on stock ROM operates between 400-800 MHz. It is set that low on all Custom ROMs, whatever the device may be (That is, if they have their own kernel). There is no normal frequency. It's like a car. You go in third gear or fourth gear as you wish. There are no steadfast rules that you have to go in fourth gear on a road and the fifth in another. CPU governors are how you set the frequencies. I don't know what you get on the KF, but on the other devices that I have tried, "Blackcats" is the one for day-day usage. Not too much, not too less.
Yes, that's the thing about having a fancy ROM. I have a completely transparent ROM on my Galaxy Y and sometimes, the thing goes bonkers. Since my phone doesn't have CM yet, these fancy transparent ROMs are the best bet for a flashy and beautiful ROM. On stock, I get around 1-2 days, but on these transparent ROMs, I get like 5-6 hours a day. Not too bad, considering that my completely transparent W7 laptop only stays for an hour on battery.
Sent from my asus_laptop using Tapatalk 2
sharonbw said:
[Q] Why would it be set that low in the first place? What is "normal"? Also is the type of CPU governor significant? Mine is defaulted to interactive.
I'll try upping frequency and see how it does. My battery life is OK - just not as good as it was pre-root/custom. I love my CM10 ROM so I will probably just live with it. (twa_priv's)
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
I honestly don't think your SOD (sleep of death) is due to the 300 Min frequency. I've had that set on any recent KF rom I've used without a problem (as mentioned previously, it tends to be the default value, with max being 1000 or 1200 (don't remember the exact value). It's more likely that something you have installed, or some setting that has been changed, is causing the problem.
One way to find out would be to do a complete wipe of the system in TWRP (factory reset, system, cache, and dalvik) and install whatever ROM you're interested in fresh (don't forget to install gapps too) and then see if you continue to have the SOD problems. Stick with stock settings for a while and see if something happens. Just my two cents of course.
Aesrys said:
I honestly don't think your SOD (sleep of death) is due to the 300 Min frequency. I've had that set on any recent KF rom I've used without a problem (as mentioned previously, it tends to be the default value, with max being 1000 or 1200 (don't remember the exact value). It's more likely that something you have installed, or some setting that has been changed, is causing the problem.
One way to find out would be to do a complete wipe of the system in TWRP (factory reset, system, cache, and dalvik) and install whatever ROM you're interested in fresh (don't forget to install gapps too) and then see if you continue to have the SOD problems. Stick with stock settings for a while and see if something happens. Just my two cents of course.
Click to expand...
Click to collapse
It's too early to know for sure but no SoD since I upped it. I've done clean several installs and i've had it since the first iteration using twa_priv's CM10. I'm currently running 20120923.
I'm still a little unclear on what clocking is but I guess that's a deficit in my knowledge of physics.
UPDATE: Well came back to my kindle after watching tv and it was in the SoD. Force power off and reboot and I'm back in business. I'll leave the clock speed at min 300 since I didn't notice any difference.
I'm going to do a search but anyone want to give me a link to a 'how to' for doing a logcat? (Is that even the right term? ) I don't know that the developers want to hear from me but I could at least post the log when I experience SoD.
Edit: nevermind. I found how to logcat.
Sent from my Galaxy Nexus using xda app-developers app
Related
I have to say I have tried EVERY ROM on the SGH-T989 and can say none are as stable and have the battery life to match the stock ROM.
I tried Darkside today. It is a clean ROM. Close to stock. I had two complete lockups on the phone that required battery removal in about a 6 hour period. I am not overclocking at all. The ROM has an underclock by default.
I just think it's time to give Samsung and the programmers there a thumbs up for doing such a great job on this phone.
It would be nice if they could release more of the header and source so the developers here could have a better chance of getting a stable ROM built...but until that happens I will just stay with a rooted and stock ROM.
Peace.
I've had no lockups or any problems in the 150 hour uptime I had with Juggernaut 5.0 with 009m faux's kernel.
Battery life is much better as well. Dropping down to 80% after 1 hour of display time.
Cool story bro
chlehqls said:
I've had no lockups or any problems in the 150 hour uptime I had with Juggernaut 5.0 with 009m faux's kernel.
Battery life is much better as well. Dropping down to 80% after 1 hour of display time.
Click to expand...
Click to collapse
I was on the stock ROM for 6 hours yesterday. Surfing, playing games, wifi enabled. Used a bit over 30% from a full charge.
I jumped right into custom ROM's when I got this phone. After going back to stock is when I realized how much the custom ROM's actually degrade the phone.
I have ran Jugg's 4.x with Faux kernel and Bullet kernels. Bullet was faster by a good bit. Battery sucker from hell though.
Do these phones really need the overclocks and tweaks? After going back to stock my opinion is no.
Peace.
You probably didnt follow the directions when installing any of the roms you tried.
If companies like samsung were as awesome as you say they are, would XDA exist at all in the 1st place?
Enjoy your bloatware.
Sent from my SGH-T989 using XDA App
ninrocket2 said:
I was on the stock ROM for 6 hours yesterday. Surfing, playing games, wifi enabled. Used a bit over 30% from a full charge.
I jumped right into custom ROM's when I got this phone. After going back to stock is when I realized how much the custom ROM's actually degrade the phone.
I have ran Jugg's 4.x with Faux kernel and Bullet kernels. Bullet was faster by a good bit. Battery sucker from hell though.
Do these phones really need the overclocks and tweaks? After going back to stock my opinion is no.
Peace.
Click to expand...
Click to collapse
Battery proof? Heres mine with Darkside:
http://db.tt/Dndk1SLW
http://db.tt/qxYSJxJv
http://db.tt/AydX5Jxx
Sent from my SGH-T989 using xda premium
Me being the analytical type....and to just keep this topic fact filled and useful will create a test bed to compare the 'popular' roms versus stock.
I will create a post in the next week to share the results.
Peace.
ninrocket2 said:
Me being the analytical type....and to just keep this topic fact filled and useful will create a test bed to compare the 'popular' roms versus stock.
I will create a post in the next week to share the results.
Peace.
Click to expand...
Click to collapse
Theres already a thread for that:
forum.xda-developers.com/showthread.php?t=1524569
Sent from my SGH-T989 using XDA App
jordanishere said:
You probably didnt follow the directions when installing any of the roms you tried.
If companies like samsung were as awesome as you say they are, would XDA exist at all in the 1st place?
Enjoy your bloatware.
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
Keep it civil and to the point. Don't attack my character by implying that I don't know how to follow directions and flash a ROM. I have been a member on XDA since the first year....much longer than you.
I don't have a problem with bloatware. I use a stock ROOTED ROM and remove the bloatware. Very easy to test and then delete bloatware using Titanium Backup.
XDA got it's start back when the CPU and chipsets on phones were very slow. Over time the new phones have become handheld computers. The processing speed is much faster.
In the beginning the OS's were in the infantile stages as well. They have all improved dramatically.
I remember when a flash on something like the HTC Tytan made a huge difference. You were getting the GPS and FM Radio Unlocked. The bloatware was removed in the ROM(Windows based...no ROOT access). It made a huge difference in the performance of the phone and unlocked a lot of features.
This isn't the case with the new phones. There really is nothing being added to the ROM's that can't be added via the market or removed using Titanium Backup.
What I have seen with every ROM is intermittent lockups that require battery removal and excessive battery consumption probably from the aggressive timings that aren't necessary.
Peace.
ninrocket2 said:
Keep it civil and to the point. Don't attack my character by implying that I don't know how to follow directions and flash a ROM. I have been a member on XDA since the first year....much longer than you.
I don't have a problem with bloatware. I use a stock ROOTED ROM and remove the bloatware. Very easy to test and then delete bloatware using Titanium Backup.
XDA got it's start back when the CPU and chipsets on phones were very slow. Over time the new phones have become handheld computers. The processing speed is much faster.
In the beginning the OS's were in the infantile stages as well. They have all improved dramatically.
I remember when a flash on something like the HTC Tytan made a huge difference. You were getting the GPS and FM Radio Unlocked. The bloatware was removed in the ROM(Windows based...no ROOT access). It made a huge difference in the performance of the phone and unlocked a lot of features.
This isn't the case with the new phones. There really is nothing being added to the ROM's that can't be added via the market or removed using Titanium Backup.
What I have seen with every ROM is intermittent lockups that require battery removal and excessive battery consumption probably from the aggressive timings that aren't necessary.
Peace.
Click to expand...
Click to collapse
I look forward to your battery testing!
Please include multiple kernels as you test various ROMs, especially faux and Synergy
And perhaps install Juice Defender as a best case.
Personally I haven't experienced any lockups with the two custom T989 ROMs I've tested, but have benefited from the improved battery life dramatically. I'd still love to see a more controlled experiment, however.
jordanishere said:
Theres already a thread for that:
forum.xda-developers.com/showthread.php?t=1524569
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
Read it. It is basically a generic thread. No stats or true testing methods just some user comments.
I want to actually test the phone in real life conditions. Watch some vids, talk on the phone, skype/gtalk/YM video call...etc. Actually run consecutive tests across the best ROMS and stock and see how they match up.
Benchmarking is a bit ridiculous....in several aspects.
If a game runs 30 fps or greater...you won't see the difference.
If a game runs a stable 30 fps versus a ROM that peaks at 50 but valleys at 15....you will definitely see the difference.
If a ROM runs 50 fps versus 30 and both are stable...you won't see the difference. The question then is which one uses less battery. The obvious answer is the one running 30fps. Less frames means less redraws and less CPU and GPU.
I just want to once an for all be able to definitively say what each ROM is really doing to the phone with graphs.
Not hard to do. Just takes a real world test model and some time. I think I can test one ROM a day. I will test the most popular ROM's....Juggs, Beast, Darkside, Bombardier, Gingersnap, etc... I have tested them all. I know which ones are legit and which ones aren't.
Peace
ninrocket2 said:
Keep it civil and to the point. Don't attack my character by implying that I don't know how to follow directions and flash a ROM. I have been a member on XDA since the first year....much longer than you.
I don't have a problem with bloatware. I use a stock ROOTED ROM and remove the bloatware. Very easy to test and then delete bloatware using Titanium Backup.
XDA got it's start back when the CPU and chipsets on phones were very slow. Over time the new phones have become handheld computers. The processing speed is much faster.
In the beginning the OS's were in the infantile stages as well. They have all improved dramatically.
I remember when a flash on something like the HTC Tytan made a huge difference. You were getting the GPS and FM Radio Unlocked. The bloatware was removed in the ROM(Windows based...no ROOT access). It made a huge difference in the performance of the phone and unlocked a lot of features.
This isn't the case with the new phones. There really is nothing being added to the ROM's that can't be added via the market or removed using Titanium Backup.
What I have seen with every ROM is intermittent lockups that require battery removal and excessive battery consumption probably from the aggressive timings that aren't necessary.
Peace.
Click to expand...
Click to collapse
Agree 100%
Nothing has performed better than stock 2.3.6, rooted and debloated.
Sent from my T989 hunting for Siri Connor
I run Juggernaut 5, ADW launcher, AOSP ICS themed, with Darkside's latest kernel (extracted it from Darkside ROM pakage), and I've had amazing battery life, OC'd to 1.83ghz with ondemand governor.
And IMO Touchwiz is ugly, samsung tries too hard to make all their stuff look like the iPhone. They do a crappy job of it and it ends up being a dissapointment.
I think any small degradation of battery life is worth the noticable boost in snappiness and cosmetics of the phone. I personally couldn't stand the stock phone, as soon as I could I flashed something different.
zander21510 said:
I run Juggernaut 5, ADW launcher, AOSP ICS themed, with Darkside's latest kernel (extracted it from Darkside ROM pakage), and I've had amazing battery life, OC'd to 1.83ghz with ondemand governor.
And IMO Touchwiz is ugly, samsung tries too hard to make all their stuff look like the iPhone. They do a crappy job of it and it ends up being a dissapointment.
I think any small degradation of battery life is worth the noticable boost in snappiness and cosmetics of the phone. I personally couldn't stand the stock phone, as soon as I could I flashed something different.
Click to expand...
Click to collapse
Strictly aesthetics can be achieved through the use of different launchers/lockscreens. The point of ROMs/Kernels need to be more than aesthetics. Hence, "some" of the ROMs offered [strictly speaking] are a pretty big disappointment because they're nothing more than themed stuff baked in and offer no real functionality.
I'm REALLY interested in a controlled experiment of battery claims of different ROMs/kernels. Preferably all at stock speeds.
djxcee said:
Battery proof? Heres mine with Darkside:
http://db.tt/Dndk1SLW
http://db.tt/qxYSJxJv
http://db.tt/AydX5Jxx
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Sorry but there is absolutely NO proof in these pictures.
I can see that your phone was on battery for a bit over 1 day.
I can also see that 45% of your phones battery usage was the display...and that the display was on for a bit over 7 hours.
What I don't know is what was your screen brightness set at?
Does the display percentage represent JUST the LED power for the screen or does it also include the GPU/CPU driving the display?
Where are the numbers for the stock ROM?
Those numbers mean nothing when you don't have a standardized test bed and procedure.
Peace.
zander21510 said:
I run Juggernaut 5, ADW launcher, AOSP ICS themed, with Darkside's latest kernel (extracted it from Darkside ROM pakage), and I've had amazing battery life, OC'd to 1.83ghz with ondemand governor.
And IMO Touchwiz is ugly, samsung tries too hard to make all their stuff look like the iPhone. They do a crappy job of it and it ends up being a dissapointment.
I think any small degradation of battery life is worth the noticable boost in snappiness and cosmetics of the phone. I personally couldn't stand the stock phone, as soon as I could I flashed something different.
Click to expand...
Click to collapse
You can use a home launcher on the stock debloated ROM and get the same results with more stability and better battery life.
I recommend you check DXHOME out to see a smooth launcher.
Peace.
ninrocket2 said:
Sorry but there is absolutely NO proof in these pictures.
I can see that your phone was on battery for a bit over 1 day.
I can also see that 45% of your phones battery usage was the display...and that the display was on for a bit over 7 hours.
What I don't know is what was your screen brightness set at?
Does the display percentage represent JUST the LED power for the screen or does it also include the GPU/CPU driving the display?
Where are the numbers for the stock ROM?
Those numbers mean nothing when you don't have a standardized test bed and procedure.
Peace.
Click to expand...
Click to collapse
Actually, unless that test was completely skewed (e.g. screen on displaying black screen), 7 hours of screen on time + 20 odd hours of standby time with use of radios/connectivity is very very impressive.
2hvy4grvty said:
Strictly aesthetics can be achieved through the use of different launchers/lockscreens. The point of ROMs/Kernels need to be more than aesthetics. Hence, "some" of the ROMs offered [strictly speaking] are a pretty big disappointment because they're nothing more than themed stuff baked in and offer no real functionality.
I'm REALLY interested in a controlled experiment of battery claims of different ROMs/kernels. Preferably all at stock speeds.
Click to expand...
Click to collapse
I agree with your first paragraph 100% and will get the experiment underway with Stock speeds.
Peace.
2hvy4grvty said:
Actually, unless that test was completely skewed (e.g. screen on displaying black screen), 7 hours of screen on time + 20 odd hours of standby time with use of radios/connectivity is very very impressive.
Click to expand...
Click to collapse
When you can refer us to pictures of a base ROM with the same parameters and settings for comparison then I might say it is impressive. But with no base ROM data it is purely speculation.
Peace.
enjoy the drm laden ciq enabled features... That cannot be removed by titanium unless it can magically decompile recompile frameworks on the fly...
Enjoy the Memeroy leaked jobsmanager....
Anyways now thats oout of the way
How much time did you spend between stock firmwares and custom firmwares?
Did you fully wipe the device before flashing and after
Did you do dirty nanoid restores?
A little more info woud be helpfull
at the end of the day if you enjoy stock more great for you.... Use it n move on...
Still missing the point of this thread on a dev website unless you like being trolled.
Coming from an e-ink Kindle I was a little shocked by the battery life initially. I now get that the lCD screen and wi-fi and a host of other differences make the fire an entirely different animal.
I was wondering though, what ROM gives the best battery life in your experience?
I'm tired of picking the thing up and finding it dead. I'm currently using AOKP or Simple CM9.
Also how often do you find that you need to recharge?
Well, the first tip i can give you is to turn off wifi when not using it. As for as roms go, it wont make much of a difference either. But if you get a custom kernel, that can make a difference. I would recommend picking a kernel of your choice, there are about 3-4 that you can use right now. Use set cpu to underclock the kindle fire. This will create more lag though.
gregory99mar said:
Well, the first tip i can give you is to turn off wifi when not using it. As for as roms go, it wont make much of a difference either. But if you get a custom kernel, that can make a difference. I would recommend picking a kernel of your choice, there are about 3-4 that you can use right now. Use set cpu to underclock the kindle fire. This will create more lag though.
Click to expand...
Click to collapse
OK. Already keeping WiFi off. Talk to me about Kernels. They are in the Dev Section. I know about Hashcode's Kernel. Are there others designed to be under clocked or conserve energy?
I have recently been playing around w/ different ROM’s on my Kindle Fire. When I use the Stock Kindle Fire ROM or Modded Fire ROM, battery life is great. When I use a Jellybean or ICS ROM (I have used Jandycane and Open Kang Project so far), battery drains even when I put the device to sleep. Both of the ROM’s I have tried have been amazing and simple to use/install.
I’d really like to run ICS or Jellybean based Android on this thing. Is there a fix or workaround for this?
It takes more processing power to provide the experience you would get by using JB or ICS, therefore your battery life will be affected accordingly.
So as the old saying goes...you get what you pay for.
soupmagnet said:
It takes more processing power to provide the experience you would get by using JB or ICS, therefore your battery life will be affected accordingly.
So as the old saying goes...you get what you pay for.
Click to expand...
Click to collapse
Ahh.. Very sound statement. However my battery drain is coming from the "sleeping" device, not from processing anything. I should have been more clear as to what the drain was coming from.
As far as getting what I paid for, I bought this as a Kindle Fire for my wife to use as... a Kindle Fire. She has logged a total of 2 hours, so I am merely attempting to get some life out of it. Already paid for an iPad (which gets plenty of use) before giving her this. Not being cheap.
scottfish said:
Ahh.. Very sound statement. However my battery drain is coming from the "sleeping" device, not from processing anything. I should have been more clear as to what the drain was coming from.
Click to expand...
Click to collapse
Believe it or not, there is still plenty of processing being done in sleep mode, mostly due to wifi. You could try turning it off (wifi or the device).
As far as getting what I paid for, I bought this as a Kindle Fire for my wife to use as... a Kindle Fire. She has logged a total of 2 hours, so I am merely attempting to get some life out of it. Already paid for an iPad (which gets plenty of use) before giving her this. Not being cheap.
Click to expand...
Click to collapse
You misunderstood my analogy. I was not speaking of the cost of the actual device. It was more a reference to the cost of processing power required to running a "higher end" ROM, comparitively speaking.
scottfish said:
Ahh.. Very sound statement. However my battery drain is coming from the "sleeping" device, not from processing anything. I should have been more clear as to what the drain was coming from.
As far as getting what I paid for, I bought this as a Kindle Fire for my wife to use as... a Kindle Fire. She has logged a total of 2 hours, so I am merely attempting to get some life out of it. Already paid for an iPad (which gets plenty of use) before giving her this. Not being cheap.
Click to expand...
Click to collapse
I have the same problem.
soupmagnet said:
Believe it or not, there is still plenty of processing being done in sleep mode, mostly due to wifi. You could try turning it off (wifi or the device).
You misunderstood my analogy. I was not speaking of the cost of the actual device. It was more a reference to the cost of processing power required to running a "higher end" ROM, comparitively speaking.
Click to expand...
Click to collapse
Cool. Hammering wifi makes perfect sense. Turning the device off seems like a waste of time (since it kills the instant on feature), but a wifi toggle could easily solve the problem. I am going to test that out.
I am intrigued by the 7 inch form factor as an everyday carry. This is my way of dipping my toe in. I would ultimately like something fairly robust that had SD storage and the ability to use an external mic for quality sound recording in a 7 inch package.
And by the way... Thanks for the response!
In my case the Wifi connection is by far the most power consumption I get.
I have flashed AlienDroid. Runs so well! Lost 40% of battery overnight. Strangely, the display seems to be my biggest battery hog.
Loving Jelly Bean. I may g snag a N7 today.
Sent from my Galaxy Nexus using xda app-developers app
I have notice running Jandycane the battery drain isn't as bad as the other JB roms
Sent from my Galaxy Nexus using xda app-developers app
So I turned off wifi and let her sit. No battery drain for three hours. Wifi is indeed the culprit.
For anyone keeping score, I am back to MoDaCo Custom ROM. Changed from Kindle Fire Launcher to ADW since I had purchased it a while back. Liking it better than stock Kindle experience as I customize, but not quite 4.0 or 4.1 either.
Seems to have solved my battery problem though. I think I am going to keep it like this for a while. Was about to grab a Nexus 7 then I read all of the posts about defects. May just grab a Transformer Infinity and toss the iPad to my wife. Guessing the Fire can be my 7 incher for now.
I am currently running twa-priv's ROM with SGT7 (CM10) and the battery drain < stock Amazon ROM. I also don't run many apps in the background and use the Droidwall firewall to block internet communication from various apps. The best ROM for battery life was Whistlestop's CM7. I also usually physically power OFF the Kindle when it won't be used for more than a couple hours while I'm running JB or ICS.
I know for a fact the phone gets hot when playing some games like Asphalt 7 and that is understandable but it never used to get hot while in regular use such as browsing the web or text messaging on stock and i could have the screen on for an hour. Ever since i installed CM10 and now on AOKP by task650 I have noticed the bottom half of the phone gets very warm even when doing simple things. I have the brightness set to auto at all times and within 15 minutes or so it starts to get hot.
Does this happen to anyone else or its just me? Also maybe there is a tweak for the screen in the ROM?
How long has it been since you installed these AOSP roms. In my experience, it takes one or two days for everything to settle down after installation, during which the phone might overheat and battery life takes a hit. My advice would be to give it some time, but if you're really worried, try fixing permissions or even going back to a touchwiz ROM.
jebise101 said:
I know for a fact the phone gets hot when playing some games like Asphalt 7 and that is understandable but it never used to get hot while in regular use such as browsing the web or text messaging on stock and i could have the screen on for an hour. Ever since i installed CM10 and now on AOKP by task650 I have noticed the bottom half of the phone gets very warm even when doing simple things. I have the brightness set to auto at all times and within 15 minutes or so it starts to get hot.
Does this happen to anyone else or its just me? Also maybe there is a tweak for the screen in the ROM?
Click to expand...
Click to collapse
I am having the same problem with CM10. I have tried multiple nightlies with the stock CM10 kernel and my phone just seems to run warmer. I can't figure it out. When I flash back to the stock ROM it doesn't do it unless like you said, I am playing Asphalt or some other games.
Nah not worried because i have extended warranty on my phone. Its just i like my electronics to function the way they should and when they don't i HAVE to fix them or i will loose my mind, plus its kinda annoying when hold it.
I know it needs a few charge cycles and installed CM earlier this week so its been at least 3 days, but still noticed the phone heating up. I installed AOKP today and will try cycling the battery a few times.
Pardon my ignorance but why would fixing permissions have anything to do with this? Also there is no negative effects to doing this? I don't see any as it wil just mark everything rwx-r--r-- or whatever the default is, but just want to confirm.
RobbieL811 said:
I am having the same problem with CM10. I have tried multiple nightlies with the stock CM10 kernel and my phone just seems to run warmer. I can't figure it out. When I flash back to the stock ROM it doesn't do it unless like you said, I am playing Asphalt or some other games.
Click to expand...
Click to collapse
I was thinking it maybe the CM kernel, would you mind flashing Kooz kernel? If you have CM for a few days. I still testing AOKP so might be a while before i can flash.
The bottom of mine gets real hot after about 15 minutes of browsing on LTE. It did it right out of the box, and I'm on stock.
Stock ICS on my S3
I disabled LTE yet its still gets hot.
jebise101 said:
Nah not worried because i have extended warranty on my phone. Its just i like my electronics to function the way they should and when they don't i HAVE to fix them or i will loose my mind, plus its kinda annoying when hold it.
I know it needs a few charge cycles and installed CM earlier this week so its been at least 3 days, but still noticed the phone heating up. I installed AOKP today and will try cycling the battery a few times.
Pardon my ignorance but why would fixing permissions have anything to do with this? Also there is no negative effects to doing this? I don't see any as it wil just mark everything rwx-r--r-- or whatever the default is, but just want to confirm.
I was thinking it maybe the CM kernel, would you mind flashing Kooz kernel? If you have CM for a few days. I still testing AOKP so might be a while before i can flash.
Click to expand...
Click to collapse
That's what I was thinking it might be and no, I don't mind flashing the other kernel. As a matter of fact, I was wanting to try that myself but I couldn't figure out wich download I needed off the link that you just posted. Wich one should I download and flash with CM10? He's got several flashable kernels posted under the "Downloads" section. I just need to know wich one I need to use with CM10.
jebise101 said:
Nah not worried because i have extended warranty on my phone. Its just i like my electronics to function the way they should and when they don't i HAVE to fix them or i will loose my mind, plus its kinda annoying when hold it.
I know it needs a few charge cycles and installed CM earlier this week so its been at least 3 days, but still noticed the phone heating up. I installed AOKP today and will try cycling the battery a few times.
Pardon my ignorance but why would fixing permissions have anything to do with this? Also there is no negative effects to doing this? I don't see any as it wil just mark everything rwx-r--r-- or whatever the default is, but just want to confirm.
I was thinking it maybe the CM kernel, would you mind flashing Kooz kernel? If you have CM for a few days. I still testing AOKP so might be a while before i can flash.
Click to expand...
Click to collapse
Fixing permissions tends to remedy certain glitches on my end. I don't nearly have enough knowledge to tell you why though. However, there are certain aspects of this phone that will lead to heat production no matter what you do: lte chip; powerful dual core CPU, etc. Furthermore, aosp ROMs are not stable nor are they fully optimized for the phone at this point, this will also lead to more resources being spent, which ultimately results in faster heat production. If it really bothers you, stick to what works and flash a stock ROM.
Sent from my SGH-I747 using xda premium
RobbieL811 said:
That's what I was thinking it might be and no, I don't mind flashing the other kernel. As a matter of fact, I was wanting to try that myself but I couldn't figure out wich download I needed off the link that you just posted. Wich one should I download and flash with CM10? He's got several flashable kernels posted under the "Downloads" section. I just need to know wich one I need to use with CM10.
Click to expand...
Click to collapse
You need to flash one of the AOSP JB kernels since you are on CM10. I can't tell you which one because that depends on which nightly you have installed. I guess there was major code changes after the 14th.
IUH1991 said:
Fixing permissions tends to remedy certain glitches on my end. I don't nearly have enough knowledge to tell you why though. However, there are certain aspects of this phone that will lead to heat production no matter what you do: lte chip; powerful dual core CPU, etc. Furthermore, aosp ROMs are not stable nor are they fully optimized for the phone at this point, this will also lead to more resources being spent, which ultimately results in faster heat production. If it really bothers you, stick to what works and flash a stock ROM.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Yeah but it never did that with stock and its not a deal breaker i love AOKP no way am i flashing back to touchwiz. You know the ROM has been so stable that I expected everything to work but your right its not stable yet and some things are probably not optimized and that is the cause for the phone to heat up more then usual or kernel. Guess it can't hurt to make a nandroid and then fix permissions and if it goes south i have a backup:victory:
jebise101 said:
Yeah but it never did that with stock and its not a deal breaker i love AOKP no way am i flashing back to touchwiz. You know the ROM has been so stable that I expected everything to work but your right its not stable yet and some things are probably not optimized and that is the cause for the phone to heat up more then usual or kernel. Guess it can't hurt to make a nandroid and then fix permissions and if it goes south i have a backup:victory:
Click to expand...
Click to collapse
Yeah, to my understanding, chipsets are designed to withstand a heat threshold of about 60 degrees Celsius. It is extremely hard to get it to that temp at stock speeds, so I wouldn't worry too much about something going awry with your phone.
Sent from my SGH-I747 using xda premium
jebise101 said:
You need to flash one of the AOSP JB kernels since you are on CM10. I can't tell you which one because that depends on which nightly you have installed. I guess there was major code changes after the 14th.
Yeah but it never did that with stock and its not a deal breaker i love AOKP no way am i flashing back to touchwiz. You know the ROM has been so stable that I expected everything to work but your right its not stable yet and some things are probably not optimized and that is the cause for the phone to heat up more then usual or kernel. Guess it can't hurt to make a nandroid and then fix permissions and if it goes south i have a backup:victory:
Click to expand...
Click to collapse
Ok. Thanks. I'll figure it out.
Can a mod please delete this unintended post?
RobbieL811 said:
Ok. Thanks. I'll figure it out.
Click to expand...
Click to collapse
hehe keep me posted. I fixed permissions, we will see how it goes.
jebise101 said:
hehe keep me posted. I fixed permissions, we will see how it goes.
Click to expand...
Click to collapse
I've clean flashed the new nightly and task's kernel. My phone still seems to be running warm! I'll run it for about 24 hours or so and see how it does. IDK what the hell it could be. Is there other people running CM10 that are having this same problem? And by the way...Do you know of a fix for the MMS? My pictures that were taken vertically show up in an MMS horizontally and visa versa. Is there no way to fix that?
RobbieL811 said:
I've clean flashed the new nightly and task's kernel. My phone still seems to be running warm! I'll run it for about 24 hours or so and see how it does. IDK what the hell it could be. Is there other people running CM10 that are having this same problem? And by the way...Do you know of a fix for the MMS? My pictures that were taken vertically show up in an MMS horizontally and visa versa. Is there no way to fix that?
Click to expand...
Click to collapse
It seemed a bit better today, but then i been out all day and its been wet and cold so might not have noticed. Its not Task's kernel but rather Kooz but they do work together. Can you also keep an eye on battery life? his kernel is suppose to have amazing battery life and CM/AOKP for me have very bad battery life. Also make sure to cycle the battery at least 3 time.
NOTE: Battery cycling mean charging it to 100% and letting it die to 0% and repeating, this will calibrate the battery and maybe will help.
Just a recommendation for you to give AOKP a try. I always used CM, but CM had some bugs when i tried so i thought might as well give AOKP a try and its actually been solid and has more features then CM. Best part is the build in LED configuration for apps/notifications.
These devs make it so hard to choose, both are very good ROMS.
Yeah. That's a problem I have too. I can't decide which one I want. The KT 747 kernel has seemed to take care of my heat problems. I was cycling the battery anyways. Where can I get the AOKP ROM? Is it posted under original development? The 747 kernel also gave me some much better benchmark scores!
Edit - I see in ktweaker where you can change some voltages but I have NO clue about any of that! Any advice? I think there is a thread on here somewhere about it. I'll have to find it & read it I guess.
Sent from my SAMSUNG-SGH-I747 using XDA Premium App
RobbieL811 said:
Yeah. That's a problem I have too. I can't decide which one I want. The KT 747 kernel has seemed to take care of my heat problems. I was cycling the battery anyways. Where can I get the AOKP ROM? Is it posted under original development? The 747 kernel also gave me some much better benchmark scores!
Edit - I see in ktweaker where you can change some voltages but I have NO clue about any of that! Any advice? I think there is a thread on here somewhere about it. I'll have to find it & read it I guess.
Sent from my SAMSUNG-SGH-I747 using XDA Premium App
Click to expand...
Click to collapse
go into the ktweaker voltages then hit menu and you have an option to add or subtract 5-25 mv. Take away a bit and do a stress test if its good then try some more etc etc. You get the picture
Sent from my SGH-I747M using xda premium
thatsupnow said:
go into the ktweaker voltages then hit menu and you have an option to add or subtract 5-25 mv. Take away a bit and do a stress test if its good then try some more etc etc. You get the picture
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
Yeah. But the lower I set my voltages, will that affect the speeds that my phone runs at? Idk how to word my question. I guess what I'm saying is, if I lower the voltage on my 1.5GHz setting will it make my benchmark lower?
Sent from my SAMSUNG-SGH-I747 using XDA Premium App
RobbieL811 said:
Yeah. But the lower I set my voltages, will that affect the speeds that my phone runs at? Idk how to word my question. I guess what I'm saying is, if I lower the voltage on my 1.5GHz setting will it make my benchmark lower?
Sent from my SAMSUNG-SGH-I747 using XDA Premium App
Click to expand...
Click to collapse
Pfft! You should know at this point in the game that benchmarks mean nothing, its all about real world performance. Basically I'd just start playing around its the only way to learn what works and what doesn't on your device! Cause afterall every device is different no 2 chips are the same, what works on one device might not work on another
Sent from my SGH-I747M using xda premium
Yeah. I know. I guess I didn't necessarily mean my benchmark. I guess I meant speed.
Sent from my SAMSUNG-SGH-I747 using XDA Premium App
Hello. Not sure if this is the correct section or not. But here goes.
I was running rootbox 4.2.2 and kt747 kernel. Along with baconatorx something script to apply settings to second core. I was getting roughly 3 to 4 hours screen on time. Great!
Recently I installed slimbean 4.3.1 after hearing so many people say it has the best battery life. With the according 4.3 kt747 kernel. I applied the same tweaks etc but at best I can get 2 hours of screen on time. Maybe there is a new script I'm unaware of.
I use my phone frequently but not heavily. Just phone calls SMS and abit of chrome. Can anyone give me some advice. Or someone with some working settings with the combo I have? Or should I just go back to what I had?
Any help would be great.
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
Anyone?
Sent from my Nexus 7 using XDA Premium HD app
See my posts on this page for my set and the battery life I am getting. Maybe these could help you:
http://forum.xda-developers.com/showthread.php?t=1969201&page=386
diablo009 said:
See my posts on this page for my set and the battery life I am getting. Maybe these could help you:
http://forum.xda-developers.com/showthread.php?t=1969201&page=386
Click to expand...
Click to collapse
Thanks. Just tried out your settings on my setup with the badass gov and slightly more under clock. And that's all you done?
I'm on 34% and only 1 hour 25 min screen on time.
And its 3rd on the list in battery stats.
I might be wrong but should cell stand by and phone idle be on top for battery usage? This is driving me nuts I have to carry my damn charger during the day.
I will report back after a few cycles.
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
ronedogg said:
Thanks. Just tried out your settings on my setup with the badass gov and slightly more under clock. And that's all you done?
I'm on 34% and only 1 hour 25 min screen on time.
And its 3rd on the list in battery stats.
I might be wrong but should cell stand by and phone idle be on top for battery usage? This is driving me nuts I have to carry my damn charger during the day.
I will report back after a few cycles.
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
Click to expand...
Click to collapse
What I am putting down below are purely from my view and my observations over the past few years.
There could be multiple issues:
1. Your battery might be getting old. On 2.8 I set the record at a whopping 7 hours display time (battery less than 6 months old). On the same ROM I was getting barely 2-3 hours (battery near to or over 18 months old) a few days before I flashed 4.1. So when I got 3h45m today, I consider that a pretty good battery.
2. You signal levels at home, the areas you roam, and at your work/school. These too kill more. Example, battery discharges slowly (when idle) at home compared to when I am at work cos of low signal levels at my work place.
3. Maybe there are too many background apps.
Example: Kik, Facebook, Google Plus. These are known battery hogs. You either uninstall these or freeze them when not needed. Your battery will thank you.
4. Kernels don't suit every phone. What works for me might not work for you. Example: Kernel of 2.8 people loved. But for me it drained battery crazy. I used Kernel C of prior version of ROM. Try out multiple, but give atleast 3 days to validate each.
5. Most importantly, do no UC too much. A phone spending 10 seconds at 1000 MHz could need 30 seconds at 800 MHz to get the same task done, and this could actually drain your battery more. For me, after using multiple phones on multiple ROMs, I found speeds between 800-1200 quite satisfactory. This is the reason my clock is normally set to 1000 as max.
6. I barely UV. UVing a little aggressively might seem to extend battery a little, but in the process it kills the phone processors and other parts. This is because they are getting strained working with lower currents than recommended. Also it is a normal practice to actually send a little more than needed currents to phone processor to avoid phone being shut off.
Our devs here who make kernels already reduce the voltage to sustainable levels to improvise on the kernel. This is also one reason why I don't bother about UVing any more.
Sorry about being lengthy and boring :victory:
diablo009 said:
What I am putting down below are purely from my view and my observations over the past few years.
There could be multiple issues:
1. Your battery might be getting old. On 2.8 I set the record at a whopping 7 hours display time (battery less than 6 months old). On the same ROM I was getting barely 2-3 hours (battery near to or over 18 months old) a few days before I flashed 4.1. So when I got 3h45m today, I consider that a pretty good battery.
2. You signal levels at home, the areas you roam, and at your work/school. These too kill more. Example, battery discharges slowly (when idle) at home compared to when I am at work cos of low signal levels at my work place.
3. Maybe there are too many background apps.
Example: Kik, Facebook, Google Plus. These are known battery hogs. You either uninstall these or freeze them when not needed. Your battery will thank you.
4. Kernels don't suit every phone. What works for me might not work for you. Example: Kernel of 2.8 people loved. But for me it drained battery crazy. I used Kernel C of prior version of ROM. Try out multiple, but give atleast 3 days to validate each.
5. Most importantly, do no UC too much. A phone spending 10 seconds at 1000 MHz could need 30 seconds at 800 MHz to get the same task done, and this could actually drain your battery more. For me, after using multiple phones on multiple ROMs, I found speeds between 800-1200 quite satisfactory. This is the reason my clock is normally set to 1000 as max.
6. I barely UV. UVing a little aggressively might seem to extend battery a little, but in the process it kills the phone processors and other parts. This is because they are getting strained working with lower currents than recommended. Also it is a normal practice to actually send a little more than needed currents to phone processor to avoid phone being shut off.
Our devs here who make kernels already reduce the voltage to sustainable levels to improvise on the kernel. This is also one reason why I don't bother about UVing any more.
Sorry about being lengthy and boring :victory:
Click to expand...
Click to collapse
Lengthy but not boring at all. ill try to add some more info on my phone and its setup.
1. my phone is less then 6 months old. 2.8 what? kernel version? 7 hours id poop a brick. lol
2. my signal strengths haven't changed at home or at work. I work outside lol however at home i do have a mountain behind me. literally a cliff side and i always got half signal since i got the phone.
3. i got the background stuff kicked. got greenify running and i have it hibernating just about everything it will let me.
4. ok this brings me back to what i was thinking originally. maybe i should just go back to what i had with rootbox 4.2.2 + kt747 kernel and scripts.... was trying to avoid this lol. 4.3 must just not jive with my phone.
5. i do have my voltages under volted 50 across the board. i have had the odd random reboot. my clocks were always either 1.2 or 1.0 ghz. never did oc or uc too much.
i will set my voltages back to stock after a few cycles.
also i run fs trim. supposed to stop lag or something. i been running it on all my devices so i figured i may as well follow suit with my s3. i also renamed mpdesion.
my standby time is still good. ill get 2 days on weekends when im not using phone much. but screen time is still less then 2 hours.
i just finished the first full charge with what u recommended. so lets see. heading out for 10 hours here soon. lets see how it does!
My bad! All my references to ROM or kernel versions pertains to Intergalatic ROM and its kernels. Sorry, I should've mentioned that.
diablo009 said:
My bad! All my references to ROM or kernel versions pertains to Intergalatic ROM and its kernels. Sorry, I should've mentioned that.
Click to expand...
Click to collapse
Thanks for your time. I've tried your settings for a few cycles. 3+ hours battery. And 2 days total. Not bad!
I have a question. I'm reading on that intergalactic ROM, and it says about certain bootloaders. One is non reverse able or something. I've read on it and I can't figure out what one to use. My phone is on telus if that means anything.
Sent from my Nexus 7 using XDA Premium HD app
ronedogg said:
Thanks for your time. I've tried your settings for a few cycles. 3+ hours battery. And 2 days total. Not bad!
I have a question. I'm reading on that intergalactic ROM, and it says about certain bootloaders. One is non reverse able or something. I've read on it and I can't figure out what one to use. My phone is on telus if that means anything.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I used the first one (reversible):
Option A: MJ2 bootloader and MJB modem
diablo009 said:
I used the first one (reversible):
Option A: MJ2 bootloader and MJB modem
Click to expand...
Click to collapse
Thanks man. I downloaded the mj2 boot loader and mjb modem package. Do I flash this prior to the ROM? And say I choose to go back to slimbean, do I have to do anything to reverse this?
Sorry I just never had to do this on my nexus 7 or ace Android devices . I just wanna make sure I cover all bases. I kinda miss a two based ROM and after hearing your success with battery on it. Its obvisouly the ROM and kernel combo for me. Games I could care less about, I use my phone for texting Facebook and browser. And I go long periods without access to charger.
Thank you so much for all your assistance.
ronedogg said:
Thanks man. I downloaded the mj2 boot loader and mjb modem package. Do I flash this prior to the ROM? And say I choose to go back to slimbean, do I have to do anything to reverse this?
Sorry I just never had to do this on my nexus 7 or ace Android devices . I just wanna make sure I cover all bases. I kinda miss a two based ROM and after hearing your success with battery on it. Its obvisouly the ROM and kernel combo for me. Games I could care less about, I use my phone for texting Facebook and browser. And I go long periods without access to charger.
Thank you so much for all your assistance.
Click to expand...
Click to collapse
Yes. Following the same sequence of steps mentioned there. I too did the same.
And rest assured, once you are on this, I don't see a reason you'd even want to go back
Until this release neither we had to do all this boot loader thingy. But with the latest release Samsung did something that created all this mess.
diablo009 said:
Yes. Following the same sequence of steps mentioned there. I too did the same.
And rest assured, once you are on this, I don't see a reason you'd even want to go back
Until this release neither we had to do all this boot loader thingy. But with the latest release Samsung did something that created all this mess.
Click to expand...
Click to collapse
Hey. When I try to flash the boot loader and modem zip it gives me a error in twrp saying it can't load the zip.
Sent from my Nexus 7 using XDA Premium HD app
ronedogg said:
Hey. When I try to flash the boot loader and modem zip it gives me a error in twrp saying it can't load the zip.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
1. Try updating your TWRP.
2. Try downloading the zip again, and verify the zip.
diablo009 said:
1. Try updating your TWRP.
2. Try downloading the zip again, and verify the zip.
Click to expand...
Click to collapse
Thanks. This wasn't my issue. I needed the i747m boot loader mk5. Intergalactic thread op directed me to it in the s3rx thread.
About to install here soon, backing up and doing a nandroid just incase.. Im going to go With kt kernel and your simple adjustments.
I see u were using 1 15 kernel. I got 1 18. Shouldn't make a difference?
What are u getting now for screen time?
ronedogg said:
Thanks. This wasn't my issue. I needed the i747m boot loader mk5. Intergalactic thread op directed me to it in the s3rx thread.
About to install here soon, backing up and doing a nandroid just incase.. Im going to go With kt kernel and your simple adjustments.
I see u were using 1 15 kernel. I got 1 18. Shouldn't make a difference?
What are u getting now for screen time?
Click to expand...
Click to collapse
That was very dangerous. Sorry, I too should've asked. Had it gone through, you could've ended up bricking your phone. Whew! Missed by a whisker!
And I flashed 1.15. I am not sure of 1.18 'cos I haven't installed it. But newer version should be better.
diablo009 said:
That was very dangerous. Sorry, I too should've asked. Had it gone through, you could've ended up bricking your phone. Whew! Missed by a whisker!
And I flashed 1.15. I am not sure of 1.18 'cos I haven't installed it. But newer version should be better.
Click to expand...
Click to collapse
Hey!
So I ended up leaving that tw ROM for now. I made a nandroid so I will try it again.
But I'm here to report my new setup and battery stats.
I'm running slimkat rc2 with the latest ktoonsez kernel.
I'm using your settings in ktweaker but I ended up back on koonservative gov and enabled hotplugging.
7h screen on time. WiFi on the whole time. Browsing forms reading emails.
Lag free 100%
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
Do I need to post a screenshot for proof? Or does it really matter lol
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
ronedogg said:
Do I need to post a screenshot for proof? Or does it really matter lol
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
Click to expand...
Click to collapse
We are all so used to getting good battery, it hardly matters anymore, unless someone posted a hard-to-believe 10 hours on stock battery.