Related
I noticed battery life on ae leaked Captivate Froyo 2.2 build (with AT&T bloatwares intact) was stellar!!! The battery life nearly doubled the custom ROMs that I have tried (the latest Cognition 2.3b8 and Axura 2.3 ROms).
I have tried all three on a regular work schedule from 8am - 4pm in a same location. I left all the ROMs installed as is. Here are the battery life meter findings at the end of my shift listed by ROM:
1. Leaked Captivate Froyo 2.2 --- Battery Life (92%)
2. Axura 2.3 --- Battery Life (69%)
3. Cognition 2.3b8 --- Battery Life (65%)
Anyone know why is this? Don't get me wrong, I love the Axura new functions and all that extras built-in. However, the battery life is discouraging.
did you recalibrate the battery and delete the batterystats.bin each time you changed to a different ROM? also, im not sure but the different modems could be the cause of the battery drain.
I almost want to say this is common sense. If you load something that increases your phones speed with a lagfix, gives you stronger reception and faster download speeds with using a different modem, and has many more enabled options would you not think battery may be effected?
All this being said I can get 20 hrs of moderate use on my current configuration. I do not need much more then that
Sent from my SAMSUNG-SGH-I897 using XDA App
mcord11758 said:
I almost want to say this is common sense.
Click to expand...
Click to collapse
*almost*
I have questioned this myself sometimes, then realizing that there is a lagfix installed. it's like buying a Vette for the gas mileage.. not gonna happen.
Hence, some custom ROM's do have damn good battery life with lagfixes! So, it's just a matter of finding what suits your needs.
The issue I've been seeing with the latest builds of most of the ROMs in the Dev Forums are:
Using customized i9000 Kernels and Modems. These are hacks/tweaks (and very good ones) to work with Captivate phones.
OC/UV Kernels that offer awesome overclocking/voltage capabilities but at a price - battery usage.
Using a Vibrant build for Captivate phones.
Custom "Captivate Kernels" (sorry the quotes aren't there for sarcasm just emphasis) that are still in beta or development.
All of the above cause battery issues as they are not optimized for our phone, missing some bits in the software that handle the OS/battery life, or straight up bleed the battery to death as your OVERCLOCKING YOUR PHONE.
And to make it worse utilizing different modems just exacerbates the problem.
Lag Fixes - SHOULD NOT AFFECT BATTERY LIFE AS THEY ARE JUST CHANGING YOUR EXISTING FILE STRUCTURE IN YOUR PHONE.
So it does make sense that while using a "stock" ROM you would get better battery life.
Now.. on to battery life/usage:
Calibrating the battery helps at least keep a more accurate track of how your phone's battery performance is doing.
You can do a few things to optimize your battery usage:
Of course Calibrate your battery - removing battery stats on your phone, doing the drain it down to 0% and re-charge to 100% to ensure you have an accurate idead of true battery usage is always helpful. I delete battery stats right after every flash to a new ROM.
Turning off Wireless/GPS/Data etc. while not in use. This does NOT mean to use a task killer since if you have an errant app running it will just make battery life worse not better.
If your using an OC kernel - then the usually install Voltage Control is a must! I have heard great things about tweaking these settings and people getting great battery life from their devices. Now.. mind you you don't have to overclock if your running the OC kernel. It's just there if you want it.
Also - being careful of what you have installed on your phone is one of the biggest ones most people miss. If it's trying to do a push every 3 seconds that is utilizing your battery/proc and that will be killing your phone.
With all that being said though? The custom ROMs are all awesome and I'm very glad we have them - even if it means I sacrifice a little bit of battery performance (which to me is horrid to begin with). I use a little common sense and I can at least get through an entire day with average usage (txts, email, calls, xda, angry birds etc..) without having to throw it on a charger.
Sorry.. long post - too much coffee and 90 wpm does that to me sometimes
cachookaman said:
did you recalibrate the battery and delete the batterystats.bin each time you changed to a different ROM? also, im not sure but the different modems could be the cause of the battery drain.
Click to expand...
Click to collapse
whats the easiest way to do this?
vuoflfan said:
whats the easiest way to do this?
Click to expand...
Click to collapse
For battery stats - you go into the advanced Clockwork Recovery Menu - go to Advanced - and you should see Clear Battery Stats there.
I would make sure that your phone is charged to 100% before doing this.
There is another trick you can do also that works for some people.
Charge your phone in.. as SOON as you get the notification stating to unplug your phone you should unplug it - wait 30 seconds then plug it back in. If it wasn't calibrated correctly you will see the percentage on your battery typically at around 97% instead of the reported 100%.
The improved battery life can probably be most attributed to the difference between the Java interpreter in 2.1 and Froyo's JIT.
In short, when Java does interpretation, it reads a single application instruction, decides what to do with it, does it, and repeats. If the same function is encountered again, the interpreter still has to re-read the instructions, decide what to do again, and do it.
In comparison, when Froyo's JIT encounters an application function, it reads the instructions in a large batch, decides what all of them should do, and records the result in the processor's "native-language". If the same function is encountered again, the processor just does it without needing to make all of those decisions again.
The speed difference is more than 30x. Running application code is only a small fraction of the total "working time", so benchmarks typically only see about 3x improvement. For the parts that are running applications (including even the home screen), Froyo is ultimately running 1 operation that used to take 30 operations - that means fewer electrons are wasted on the processor.
Also, Samsung's crappy filesystem decision certainly will impact battery life, since the format they chose (a relative of the old DOS format) performs seeks optimized for linear mechanical devices (like hard drives), not from FLASH, which suffers on fractional block reads and excels at non-linear reads. Lots of electrons will be wasted interacting with FLASH unnecessairily, but that kind of interaction is rare compared to other battery consumers.
- Kipp
Embedded Systems Hardware and Software Engineer
Hi,
I don't have sufficient posts to be able to participate directly in that forum, so have no other choice but to raise my queries here.
I've just flashed over from Overcome "Hermes" to "Jupiter". All's well except that the battery performance is quite drastically affected for me.
I've been reading the improved battery life "Jupiter" gets over earlier versions of the Overcome ROMs, but I seem to be experiencing the opposite.
Already did the batt stat wipe via recovery menu. Do I need to so call "run-in" before it reflects correctly? Even if accuracy is one thing... but dropping 3% just on bootup.... is this typical of an uncalibrated battery?
Appreciate any advise here on what I should do. (Apart from a fresh wipe install )
Thanks
I appreciate the enthusiasm these coding geniuses have in rolling out update after updates in the ROMS yet I am apprehensive about the effect of these frequent flashing on the Galaxy Tab components itself. This includes the battery.
My job involves electronic repair and there is a so called number of hours before an equipment goes for a thorough check(preventive maintenance) say for example 1000 hours on a meter. Unfortunately the galaxy tab (or any tablet) does not have this. So if you frequently do a flashing on your tab you subject the electronic components to unnecessary stress,thereby affecting the life of the components like the battery.
In "normal" everyday use of the tab you will seldom do any restart/reboot of your tab,yet in flashing ROMs as many as 3 reboots is needed. As I don't know how to measure the surge in current during reboot, I can just imagine how high an initial current during startup is generated, thus putting a big strain on the battery.
Unfortunately the battery is not user detachable.
There was an author here in XDA describing himself/herself as an "flashing addict"(or something similar). I would like to appeal to everyone-please don't be a flashing addict.
As for battery issue read here
JUST MY FEW CENTS!
PCdumb said:
Hi,
I don't have sufficient posts to be able to participate directly in that forum, so have no other choice but to raise my queries here.
I've just flashed over from Overcome "Hermes" to "Jupiter". All's well except that the battery performance is quite drastically affected for me.
I've been reading the improved battery life "Jupiter" gets over earlier versions of the Overcome ROMs, but I seem to be experiencing the opposite.
Already did the batt stat wipe via recovery menu. Do I need to so call "run-in" before it reflects correctly? Even if accuracy is one thing... but dropping 3% just on bootup.... is this typical of an uncalibrated battery?
Appreciate any advise here on what I should do. (Apart from a fresh wipe install )
Thanks
Click to expand...
Click to collapse
According to the Tweaks section at the team overcome website, it will take several charge cycles before you notice an improvement after the stat wipe. Try giving it a few days before going any further.
PS Not to question your ability to follow instructions (sometimes we miss things) but did you charge to 100% with the tab off?
Yes, I did charge to 100% with the Tab off.
Now upon reading the instructions once more..... I might have conducted it slightly different from the written procedure.
I unplugged the Tab from the mains, then only booted up and wiped the batt stats before re-booting. Hmmm.... maybe I'll go try booting up while still plugged into the mains, do the batt stat wipe, and re-boot. (all while plugged into the mains). Then only unplug the charger.
Wonder is there any diff in doing so.....
Would definitely try re-doing it with the tab plugged in while doing the stat wipe. And if it doesn't seem to fix it, do go through a few cycles before reverting back to a previous ROM.
It's important to completely drain your battery before recharging it to 100% in order to complete a cycle.
Hope you fix it. Battery life results vary between tab's even if they are used very similarly, I'm running the OVERCOME Jupiter ROM with IMPROVED battery life. I keep my Bluetooth, Wifi and GPS on all the time. I also flash quite often and have not seen a decrease in overall battery life. It seams that each tab is a bit different, hardware wise, than one another. Everything from battery to board it seems is slightly different coming out of the manufacturing process.
Thanks. Will try that out.
But it just seems strange coming from Overcome ver 1.4 (Froyo) which had no batt drain problem.... to Hermes which was better in batt performance.... to Jupiter which I'm experiencing heavy drain.
As I did a NoWipe install, all apps and setting are similar (except the new market app).
I was able to run 2 movies back to back (about 3 hours total) and still have at least 40% life left (usually about 45 to 50%). Now on Jupiter, just fiddling around testing the various features for functionality, plus maybe an hour of NFS (total about 3 hours as well).... the batt drops to about 10% life.
Anyway, I'll re-do the calibration and and give it some time to "settle in". Hopefully, that is all that is needed. (I would hate to have to do a full wipe install... and re-installing all apps)
PCdumb said:
Thanks. Will try that out.
But it just seems strange coming from Overcome ver 1.4 (Froyo) which had no batt drain problem.... to Hermes which was better in batt performance.... to Jupiter which I'm experiencing heavy drain.
As I did a NoWipe install, all apps and setting are similar (except the new market app).
I was able to run 2 movies back to back (about 3 hours total) and still have at least 40% life left (usually about 45 to 50%). Now on Jupiter, just fiddling around testing the various features for functionality, plus maybe an hour of NFS (total about 3 hours as well).... the batt drops to about 10% life.
Anyway, I'll re-do the calibration and and give it some time to "settle in". Hopefully, that is all that is needed. (I would hate to have to do a full wipe install... and re-installing all apps)
Click to expand...
Click to collapse
As mentioned in the Tweaks section, perform the Stat wipe and then two full recharge cycle
recharge to 100% (while the Tab is closed) then drain the battery till it is off then repeat the cycle and you will enjoy it man
Please tell me if you need anything
bongski55 said:
I appreciate the enthusiasm these coding geniuses have in rolling out update after updates in the ROMS yet I am apprehensive about the effect of these frequent flashing on the Galaxy Tab components itself. This includes the battery.
My job involves electronic repair and there is a so called number of hours before an equipment goes for a thorough check(preventive maintenance) say for example 1000 hours on a meter. Unfortunately the galaxy tab (or any tablet) does not have this. So if you frequently do a flashing on your tab you subject the electronic components to unnecessary stress,thereby affecting the life of the components like the battery.
In "normal" everyday use of the tab you will seldom do any restart/reboot of your tab,yet in flashing ROMs as many as 3 reboots is needed. As I don't know how to measure the surge in current during reboot, I can just imagine how high an initial current during startup is generated, thus putting a big strain on the battery.
Unfortunately the battery is not user detachable.
There was an author here in XDA describing himself/herself as an "flashing addict"(or something similar). I would like to appeal to everyone-please don't be a flashing addict.
As for battery issue read here
JUST MY FEW CENTS!
Click to expand...
Click to collapse
where you were hiding this all ? i bet you were so damn angry to say all of this , i never saw you writing more than 3-4 lines , chill out buddy .
@The OP flashing custom roms means battery need to re-life back
bongski55 said:
I appreciate the enthusiasm these coding geniuses have in rolling out update after updates in the ROMS yet I am apprehensive about the effect of these frequent flashing on the Galaxy Tab components itself. This includes the battery.
My job involves electronic repair and there is a so called number of hours before an equipment goes for a thorough check(preventive maintenance) say for example 1000 hours on a meter. Unfortunately the galaxy tab (or any tablet) does not have this. So if you frequently do a flashing on your tab you subject the electronic components to unnecessary stress,thereby affecting the life of the components like the battery.
In "normal" everyday use of the tab you will seldom do any restart/reboot of your tab,yet in flashing ROMs as many as 3 reboots is needed. As I don't know how to measure the surge in current during reboot, I can just imagine how high an initial current during startup is generated, thus putting a big strain on the battery.
Unfortunately the battery is not user detachable.
There was an author here in XDA describing himself/herself as an "flashing addict"(or something similar). I would like to appeal to everyone-please don't be a flashing addict.
As for battery issue read here
JUST MY FEW CENTS!
Click to expand...
Click to collapse
Viewed purely from an engineering perspective, I'm unable to see any significant connection between the flashing of the ROM and a degradation of battery capacity. Further, in the event that the TAB was connected to a charger during the flashing, I can see absolutely no connection at all! Please help me understand your logic.
Ok Back on topic. PCdumb (dude what's with the username lol). Check your app list. It could a new app you or an old app you updated or an app you didnt use before but you use now that is being a battery hog. A small trick I learned is checking apps running services in the background. Go to Settings, applications, running services and check (why is skype working after Isigned out its not a battery drainer but I hope you got the picture).
Thanks for the advise. That was one of the 1st few things I did to check that there's nothing out of the ordinary running in the background and taking up the juice.
Mine's actually draining alot when in usage. Not too sure about when in standby.... will check later.
If after a few charge cycles and the drain is still bad, guess my only next best option is to do a full wipe, re-stock and re-install.....
I did not get any effect from Battery calibration. As expeced. Anybody did actually?
The background services instead might have an effect on power consumption, I agree. But needs numerous testing...
Batt recal did not give me better battery life. There's no difference in the battery performance after 3 recharge cycles.
My tab can at most get slightly more than 5 hours of continuous usage compared to about close to 7 hours on hermes. This is when i dial down the OC from smartass mode to conservative and also put the min freq to 200 instead of 400 which was the setting i was using all the while.
Doesn't seem to be anything else running in the background. On standby overnight, i only lose about 3% which is not too bad. But when in use, that's where the Batt drains fast. Just for comparison, i only lost 1% at most for overnight standby of about 7 hours when running hermes.
Guess I'll have to live with this if i want the speed and smoothness. Still contemplating whether to restock and do a clean flash.
PCdumb said:
Batt recal did not give me better battery life. There's no difference in the battery performance after 3 recharge cycles.
My tab can at most get slightly more than 5 hours of continuous usage compared to about close to 7 hours on hermes. This is when i dial down the OC from smartass mode to conservative and also put the min freq to 200 instead of 400 which was the setting i was using all the while.
Doesn't seem to be anything else running in the background. On standby overnight, i only lose about 3% which is not too bad. But when in use, that's where the Batt drains fast. Just for comparison, i only lost 1% at most for overnight standby of about 7 hours when running hermes.
Guess I'll have to live with this if i want the speed and smoothness. Still contemplating whether to restock and do a clean flash.
Click to expand...
Click to collapse
If you want to confirm that JUPITER is the reason that you are experiencing poor battery life, try re-installing a previous version that you feel worked better for you. Maybe reverting back to a previous version may yield better battery results, and I sure hope so, this way you will know if it's the ROM or other elements affecting the abnormal battery drain.
If you do see an increase in battery life, try flashing JUPITER again, see what the results are. I don't know if flashing and re-flashing will have a negative long term effect on your SGT, I know that I flash every time a new release is out (Stock safe, cooked ROM, Kernel) and if i'm not happy with the release i go back to a proven one by flashing another three times (stock safe, cooked ROM, Kernel) and so far I have not had any (knock on wood) abnormal battery activity.
It's worth giving it a shot (if you haven't already).
EDIT: I know, I know the proper sequence is stock safe, kernel, rom.
after week of using the Overcome ROM i can confirm that the battery performance is between 85 and 90% from the Orignial stock ROM performance
No problem since this is normal as we are using a cooked ROM
bongski55 said:
I appreciate the enthusiasm these coding geniuses have in rolling out update after updates in the ROMS yet I am apprehensive about the effect of these frequent flashing on the Galaxy Tab components itself. This includes the battery.
My job involves electronic repair and there is a so called number of hours before an equipment goes for a thorough check(preventive maintenance) say for example 1000 hours on a meter. Unfortunately the galaxy tab (or any tablet) does not have this. So if you frequently do a flashing on your tab you subject the electronic components to unnecessary stress,thereby affecting the life of the components like the battery.
In "normal" everyday use of the tab you will seldom do any restart/reboot of your tab,yet in flashing ROMs as many as 3 reboots is needed. As I don't know how to measure the surge in current during reboot, I can just imagine how high an initial current during startup is generated, thus putting a big strain on the battery.
Unfortunately the battery is not user detachable.
There was an author here in XDA describing himself/herself as an "flashing addict"(or something similar). I would like to appeal to everyone-please don't be a flashing addict.
As for battery issue read here
JUST MY FEW CENTS!
Click to expand...
Click to collapse
WOW ! This was an eye opener for me...
Thanks for clarifying this...... I didn't know this was so bad for the hardware ....
Sent from my GT-I9003 using Tapatalk
PCdumb said:
Batt recal did not give me better battery life. There's no difference in the battery performance after 3 recharge cycles.
My tab can at most get slightly more than 5 hours of continuous usage compared to about close to 7 hours on hermes. This is when i dial down the OC from smartass mode to conservative and also put the min freq to 200 instead of 400 which was the setting i was using all the while.
Doesn't seem to be anything else running in the background. On standby overnight, i only lose about 3% which is not too bad. But when in use, that's where the Batt drains fast. Just for comparison, i only lost 1% at most for overnight standby of about 7 hours when running hermes.
Guess I'll have to live with this if i want the speed and smoothness. Still contemplating whether to restock and do a clean flash.
Click to expand...
Click to collapse
After reading all this superb discussion....
I would just recommend you to go back to your older rom.....
Its forbthe best....
Sent from my GT-I9003 using Tapatalk
I do get 4 to 5 hours of continuous use with overcome Jupiter, mostly browsing the web over
WLAN or umts. Hermes release didn't gave me so much more juice, probably 5 hours.
In the background I have emai push, contacts and calendar sync and some instant messaging apps, if I switch off all that I might get an hour or so more.
PCdumb said:
...On standby overnight, i only lose about 3% which is not too bad. But when in use, that's where the Batt drains fast. Just for comparison, i only lost 1% at most for overnight standby of about 7 hours when running hermes...
Click to expand...
Click to collapse
Wow, maybe your tab is one of the ones with a battery from the bad batch, and it's finally on its way out. I upgraded from the stock AT&T Rom to Overcome Jupiter, and on Airplane Mode with all stock settings (no overclock or undervolt), mine only drops 1% in standby over 14 hours and I can get about 5 hours of video watching straight with the brightness on max before it dies!
DarkPal said:
A small trick I learned is checking apps running services in the background. Go to Settings, applications, running services and check (why is skype working after Isigned out its not a battery drainer but I hope you got the picture).
Click to expand...
Click to collapse
I also been experiencing a major increase in battery drain even after doing a couple wipes exactly according to the tweak guide. I went from about 24 hour normal use down to 6-8 hours normal use.
Checked the services as per your suggestion above and found a couple major battery drainers running. Skype and Yahoo but also Google+. What I dont understand is why Skype and Yahoo would be running even though I had not started either since at least several re-boots ago. I had Skype and Yahoo installed for quite a while Google+ is a new one. Anyway I killed all of them and now and will see what happens next.
Not sure thought that this is all there is to the issue. Recahrging is finiky as well. I can turn off the tab and let it charge all night just to find that it charged to about 70% if I re-plug it might charge to 90%-95% and then if re-plug it might get to 100%. The drain from 100% to 60%-70% is extremely fast and still quite fast from there. On one occasion after complete drain I couldnt get it to start charging at all for about 5-10 minutes. I was checking power, cables, connections and starting to panic when all of a sudden it started to charge.
Any advice on possible reasons or solution woud be appreciated. Not sure I want to go beck to stock ROM and un-root just to take it to service center for repairs.
EMulator like gameboid, FPSE or android games like zenonia, destinia and inotia
emulators i guess
3g network and DSP manager
3D games, I guess.
And Wi-Fi (especially connecting/disconnecting)
hi i am always here people moaning about battery but im on gdx v019 now since last night and in 24hours i have used 47% wifi,gps on all the time i play some games but not much and since gdx v016 i get 2-3days battery.
if you wont a hand held games console with good battery try a sony psp as when i last checked the x8 was a mobile phone
All of the said actually take most battery up. Your launcher takes up battery to.
Android system uses battery (duh)
But wifi and 3g are the hoggers. They take up most of the battery
sent from my rooted x8 using gingerdx
x8 [email protected] ONDEMAND
with wifi (Never sleep policy) and 3.5G on - max 18h battery uptime (even 12h if I'm on the go and phone is switching from one cell tower to another frequently)
without wifi - kinda 1.5 days
Without wifi and in 2G only mode - almost 3 days (2d20h)...
The rom/kernel influence in the life or the battery? What is the best rom to time saving battery?
I'm thinking for a work use: read and write documents (Isilo, Documents to Go, Swype), internet (Gmail, Opera Mini, Maps, Barnacle Wifi, read news, etc). For me clearly the biggest battery drain is the 3G internet (according to BMW reaches 600 mAh, while Documents to Go does not exceed 200 mAh)
I am using v22 Froyobread with smartass, and the battery lasts me 20 hours. (I have a low screen brightness, wifi, bluetooth, GPS off). My question is mainly about the different roms, have several more efficient than others in the use of the battery? Do rom based in Gingerbread spend more than those based on Froyo? The union of a custom kernel and custom rom can be more efficient in the use of the battery?
Thanks and excuse my English
APD500 said:
The rom/kernel influence in the life or the battery? What is the best rom to time saving battery?
I'm thinking for a work use: read and write documents (Isilo, Documents to Go, Swype), internet (Gmail, Opera Mini, Maps, Barnacle Wifi, read news, etc). For me clearly the biggest battery drain is the 3G internet (according to BMW reaches 600 mAh, while Documents to Go does not exceed 200 mAh)
I am using v22 Froyobread with smartass, and the battery lasts me 20 hours. (I have a low screen brightness, wifi, bluetooth, GPS off). My question is mainly about the different roms, have several more efficient than others in the use of the battery? Do rom based in Gingerbread spend more than those based on Froyo? The union of a custom kernel and custom rom can be more efficient in the use of the battery?
Thanks and excuse my English
Click to expand...
Click to collapse
If you use 3G that's like talking with the phone continuosly. It can't be affected with anything.
In my case I think FroyoBread (or FroyoPRO for now) is the most battery friendly ROM with UV of course. With Wifi (never sleep) GPS on all the time it can last around 3 days. With GDX the maximum for me is around the same, but with GPS off and wifi off if phone is idle, and I think it is more smooth overall.
For the main question, the ROM can affect the battery life of the phone, bot so do the user. If you use live wallpaper, DSP manager, a lot of widgets, fancy launcher, it will eat your battery no matter what you do. The two is almost equal in my opinion, but I'm no developer to say that it's just my personal view.
Thanks for your answer. Only one question what is UV? Is it the Undervolt module?
APD500 said:
The rom/kernel influence in the life or the battery? What is the best rom to time saving battery?
I'm thinking for a work use: read and write documents (Isilo, Documents to Go, Swype), internet (Gmail, Opera Mini, Maps, Barnacle Wifi, read news, etc). For me clearly the biggest battery drain is the 3G internet (according to BMW reaches 600 mAh, while Documents to Go does not exceed 200 mAh)
I am using v22 Froyobread with smartass, and the battery lasts me 20 hours. (I have a low screen brightness, wifi, bluetooth, GPS off). My question is mainly about the different roms, have several more efficient than others in the use of the battery? Do rom based in Gingerbread spend more than those based on Froyo? The union of a custom kernel and custom rom can be more efficient in the use of the battery?
Thanks and excuse my English
Click to expand...
Click to collapse
if your talking about does the rom affect the battery, yes, the rom can affect the battery life, depending how heavy the rom is like gingerbread, that seem to take up most battery whilst froyo, well lats a lightweight android so it would save up more battery for not having to run more stuff on it unlike gingerbread...
thanks youuu .. your supper
who?
alessiocerci said:
thanks youuu .. your supper
Click to expand...
Click to collapse
who? all of us? were here to help
Battery life tested by me:
Both cases same use, no WiFi, no 3g, only calls and sms:
GingerDX = 2 days
Froyobread = 6 days
Note: similar results on other roms based on CM, the main diference is between CM6(2.2) and CM7(2.3).
So I've been testing CM9 for quite a while now and can't help notice the battery life has been reduced heavily compared to Honeycomb 3.x.
Now, I don't mind that my battery life gets a bit shorter as ICS brings more features and might be more power hungry. But I went from my tab being able to hold a charge in standby mode in 3 weeks to barely 3 days. And if I use it more heavily, it barely holds a day, which is worse than my Motorola Atrix and that's just not normal.
Now, I've been discussing this with pershoot and for him it must coming from something I do. Honestly I don't see what. In the Honeycomb days, I used to have so many apps installed (may 100-150) and battery life was fine. In CM9, I'm running 50 apps, the essential ones. All the apps that could be power hungry have those settings set to off. No push notifications, very large updates intervals (a day) or none when possible. Also, I run most on these apps on my Atrix (which has more apps installed) and my battery life is way better on the Atrix.
In usage itself, I don't see any change, it seems the tab consumes the same amount of battery than before. It's the sleeping battery life that is terrible. In my case, in sleep mode, wifi is off, brightness is set to Auto and data is off (not the signal itself but I tried to take off the SIM and the battery life is the same).
Honestly, not having to care about charging every day is a must feature for a tablet.
I'm running now RS125 ICS, based on stock and the issue is also there. So I wouldn't say it's something related to CM9 but more on how ICS behaves with our tab.
I've read report of other people complaining (with the 10.1 also) so I wonder if it's a general issue. Could you please fill the poll so we can see if there's an issue and if so, how could we identify it ?
Don't hesitate to describe your tab usage and battery life !
Thanks !
For me worsts battery life was with the official 3.0.1. 3.1 was big improvement. 3.2 and 4.x were a little bit better than 3.1.
Got gmail and exchange push notifications turned on, but most of the time the tab is connected to the wi-fi, not to the 3G network
Attached is my personal stand-by record on the 10.1v. I think it was with one of the first pershoot's CM9 roms
Hi Danny,
Same for me. Especially the standby mode I see a battery drain.
By the way, somehow my battery usage is not working since I moved to the official ICS ...
Cheers
No problem @all. Stock 4.0.4 with OC kernel.. Looks like this:
GT-P7500 [email protected]
Kernel info...
GT-P7500 [email protected]
Hi,
first, thanks to Maclaw & co for their s3 ports!
I've flashed CM11 on a new phone, and am very happy with it. The only straight up bug I found: reading contacts & SMS from the SIM card was impossible. Reverted to stock backup, pulled them down and backed up, then went back and imported them in CM11.
On battery drain - this is my first smartphone, and I ditched stock immediately. So I am missing some frame of reference here. Also I just got this two days ago, so I will need another week for some real-world statistics. But from what I've seen so far, I kind of doubt it will make it through a single day. Now I don't expect it to hold charge for a week like the old Nokia I am migrating from, but still...
What kind of battery life can I reasonably suspect? I understand "it depends", but let's say location turned off, mobile data only when needed (maybe an hour/day or so), dark themes, dim screen, etc.. Basically I am trying to figure out if this is an issue with the mod/build, or just how things are in android land.
Now I do have some suspicions that cpu load is a bit excessive. During "idle" (no apps running but htop, location&mobile data off, wifi on), both cores are at ~30% consistently. Attached is a screenshot after 1) bootup, 2) turn off screen 3) turn back on after 30min and start htop in terminal. The base system also seems to draw more power than the screen (set near minimum brightness). But again, maybe normal?
I went with CM11 because it looked like it was the most widely used / best supported one, but if it actually has some battery issues I would need to try out some alternatives. Would be happy to help in debugging if there is something I can do as well.
Have a look at Slimkat. Been using this for quite some time and I have no complaints about battery life. Obviously the battery life will depend on how and what you use your phone for.
Pacperformance is a system app in Slim so you can set your governed, CPU Max/main etc. Use wake lock detector too just so you can see if pacperform is showing your not getting deep sleep.
I have used many, many custom roms and CM11 has never really appealed.
Good luck in your quest!
Slim link
http://forum.xda-developers.com/showthread.php?t=2758098
Sent from my GT-I8190N running SlimKat
Thanks for the tips, I'll check them out. I was a bit wary with trying out other mods since I'd like to not spend too much time on it and just have it stable, but I think I will just give them a go - easy enough to revert from a backup. Regarding governors, I checked and mine is set to interavtice, there are a bunch of others available though:
Code:
$cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
abyssplug pegasusq hotplug conservative ondemand userspace powersave interactive performance
Hmm, most of them I've never heard off - any preferences?
BTW, for whatever reason battery drains a lot slower now (maybe it just needed a few cycles to settle in?). I also verified via adb shell that it idles at around zero load when the screen is off.
Have a look here
http://forum.xda-developers.com/showthread.php?t=2017715
And here!
http://forum.xda-developers.com/showthread.php?t=2810435
Very informative
Sent from my GT-I8190N running SlimKat