Related
I'm running Gingervitis, just flashed it a couple days ago. So far I really like it but I'm noticeing some battery issues. Not sure if it's due to the ROM itself, gingerbread, or my phone.
First, it seems like the battery drain is a lot quicker that when I was running Froyo. Doesn't bother me as much I guess.
Last night I plugged my phone in at about 2:00 AM. It was at about 20%. It is now 9:30 and it is at 8:00 is was at 85% and now at 9:40 it's at 96%. Over 7 hours and not fully charged???
That seems crazy to me. The phone sat idle all night so I don't think there was any load eating up any additional power.
What is causing this?
schmaltzy said:
I'm running Gingervitis, just flashed it a couple days ago. So far I really like it but I'm noticeing some battery issues. Not sure if it's due to the ROM itself, gingerbread, or my phone.
First, it seems like the battery drain is a lot quicker that when I was running Froyo. Doesn't bother me as much I guess.
Last night I plugged my phone in at about 2:00 AM. It was at about 20%. It is now 9:30 and it is at 8:00 is was at 85% and now at 9:40 it's at 96%. Over 7 hours and not fully charged???
That seems crazy to me. The phone sat idle all night so I don't think there was any load eating up any additional power.
What is causing this?
Click to expand...
Click to collapse
Known issue, unknown fix afaik.
Try flashing imos latest kernal--did not do well with my phone but the charging seemed to be a lot faster IMHO.
schmaltzy said:
I'm running Gingervitis, just flashed it a couple days ago. So far I really like it but I'm noticeing some battery issues. Not sure if it's due to the ROM itself, gingerbread, or my phone.
First, it seems like the battery drain is a lot quicker that when I was running Froyo. Doesn't bother me as much I guess.
Last night I plugged my phone in at about 2:00 AM. It was at about 20%. It is now 9:30 and it is at 8:00 is was at 85% and now at 9:40 it's at 96%. Over 7 hours and not fully charged???
That seems crazy to me. The phone sat idle all night so I don't think there was any load eating up any additional power.
What is causing this?
Click to expand...
Click to collapse
Read my new post. Thanks n good luck! (Check your kernel)
4Geezy ON DopeDiculous's ROOTED TBeezy!
Charging speed seems fine until it gets into the upper 90s. I've been waiting for 20 mins for it to go from 98-99 to 100 so I can finally do my battery calibration.
(Imo's latest and DasBamf GingerRemix)
Gotta love the Thunderbolt's ability to destroy a fully charged battery and take forever to recharge. I was using rooted stock and now I'm on Cyanogenmod and I haven't seen too much of a change in charge/discharge behavior.
I know this may not be the answer you are looking for but if you could go without your phone being on for an hour or so than just power it off to charge, it goes a lot quicker n.n
Sent from my ADR6400L using XDA Premium App
Charging
To address the OP and your comment......
Yes try a different kernel, Dream's new one is based off IMO's with some nice tweaks. As for charging to 90%.... thats standard for any device that utilizes quick charging. You can NOT charge a battery on fast charge all the way to 100% with out ruining the battery. Some kernels have issues with quick charging, so they disable it, others quick charge to 60% and then trickle charge.
Apple and HP were one of the first companies to throw in the quick charge method 80/20 80% quick charge @ ~1% per 1min and then trickle for the last 20%.
Hope that helps....
jschecter said:
Charging speed seems fine until it gets into the upper 90s. I've been waiting for 20 mins for it to go from 98-99 to 100 so I can finally do my battery calibration.
(Imo's latest and DasBamf GingerRemix)
Click to expand...
Click to collapse
ready5 said:
To address the OP and your comment......
Yes try a different kernel, Dream's new one is based off IMO's with some nice tweaks. As for charging to 90%.... thats standard for any device that utilizes quick charging. You can NOT charge a battery on fast charge all the way to 100% with out ruining the battery. Some kernels have issues with quick charging, so they disable it, others quick charge to 60% and then trickle charge.
Apple and HP were one of the first companies to throw in the quick charge method 80/20 80% quick charge @ ~1% per 1min and then trickle for the last 20%.
Hope that helps....
Click to expand...
Click to collapse
Thanks for the suggestion. I think I'll give it a try.
Might as well ask another question right away.... I have not been having good luck with the battery life on these new GB ROMS. I've been running Das BAMF 2.0.5 for a couple days now and it seems to not be so great on the battery. With pretty much NO usage today, my battery is already at %80.
My battery usage shows it off the charger for a little over 5 hours, and normally I'd say 5 hours and %80 isn't bad, but like I stated above, I haven't used it at all today. No texts, phone calls, or games.
Any battery improvement with Dream's kernal?
I don't know about the battery life but after you plug your phone in to charge just reboot it and it should charge fine. I read that somewhere on here and just did it this morning. Worked great for me.
Sent from my HTC Thunderbolt
schmaltzy said:
Thanks for the suggestion. I think I'll give it a try.
Might as well ask another question right away.... I have not been having good luck with the battery life on these new GB ROMS. I've been running Das BAMF 2.0.5 for a couple days now and it seems to not be so great on the battery. With pretty much NO usage today, my battery is already at %80.
My battery usage shows it off the charger for a little over 5 hours, and normally I'd say 5 hours and %80 isn't bad, but like I stated above, I haven't used it at all today. No texts, phone calls, or games.
Any battery improvement with Dream's kernal?
Click to expand...
Click to collapse
I dont like recommending one ROM over another.. but there is alot of buzz over Th3oryofGinger, its got some.. but not alot to do with the ROM. Try that if you like none other. The kernel is key. Try dreams with Th3oryofGinger and see how that works. Remember to run speedtweak.sh in terminal and use the extreme setting (extremely undervolted, overclocked to 1400mhz) and then select the setting to remove limits for governor. I use interactiveX with setCPu and get decent results.
No ROM, MOD or Kernel will give you enough battery allday with normal intended use be it gaming or business. Fact is it was a crappy hardware design in that respect. With the Tbolt you should expect 1hour per 10% of battery for decent use... 10 text messages, 4 emails, and a few pages of internet searches on 3g per hour is what I consider decent use. Realistically it should last an 8 hour work day... with some to spare before you charge on the ride home. Dont expect much more.
ready5 said:
I dont like recommending one ROM over another.. but there is alot of buzz over Th3oryofGinger, its got some.. but not alot to do with the ROM. Try that if you like none other. The kernel is key. Try dreams with Th3oryofGinger and see how that works. Remember to run speedtweak.sh in terminal and use the extreme setting (extremely undervolted, overclocked to 1400mhz) and then select the setting to remove limits for governor. I use interactiveX with setCPu and get decent results.
No ROM, MOD or Kernel will give you enough battery allday with normal intended use be it gaming or business. Fact is it was a crappy hardware design in that respect. With the Tbolt you should expect 1hour per 10% of battery for decent use... 10 text messages, 4 emails, and a few pages of internet searches on 3g per hour is what I consider decent use. Realistically it should last an 8 hour work day... with some to spare before you charge on the ride home. Dont expect much more.
Click to expand...
Click to collapse
Thanks for the suggestion! I may give Th3ory a try. I download the newest Dream kernel but before I flashed it I jumped on Imoseyon's page and found out that I was running an OLDER version on his kernel with Das BAMF. So I flashed his newest (3.0.1 test 1) and am going to try that out for a couple days and see how it is.
I do disagree with you on the fact that a phone should last a little more than an 8 hour work day. On some Froyo ROMs and kernels I was getting a least 15+ hours with minimal/medium usage.
Mine charges very slow, running liquid ginger 1.1 battery goes down faster too.
Sent from my ADR6400L using XDA App
Hi all, I'm new to this part of the xda forums as I had a nexus before, just got the upgrade to the Atrix, rooting,unlocking of bootloader everything went well but I just flashed Aura's from with feux kernel and im getting really really bad battery life, like I'm talking 4-5 hours. There is one process thats really confusing me, its just called "x" and its sitting there taking about 35% battery, my screen is taking 55% battery.
It's getting really annoying as my nexus used to give me about 12 hours and the only reason I moved to the atrix was to get the better battery life that I saw with all my atrix touting friends (they all had 1-2 days battery life) I'm about to flash homebase and see if that fixes it but I don't know whats going on. I have a UK MB860 and I used http://forum.xda-developers.com/showthread.php?t=1196747&highlight=t-mobile+root to root. Pleaseee can someone help!
X is the webtop and there is a fix somewhere for that (doesn't completely work). Just flash CM7 beta. Its much better than any other ROM and has the best battery life. Everything except the finger print scanner and webtop work.
Also I had really good battery on the Ying Yang ROM.
Speedily sent from CM7 Beta
I think I might give CM7 a go you know, I loved CM on the nexus, even after it killed the memory chips it was still good! Im going to try it, is it really stable?
EDIT:
since updating to CM7 and Wiping my battery stats I have some how gained 39% battery!
amzter said:
I think I might give CM7 a go you know, I loved CM on the nexus, even after it killed the memory chips it was still good! Im going to try it, is it really stable?
EDIT:
since updating to CM7 and Wiping my battery stats I have some how gained 39% battery!
Click to expand...
Click to collapse
I haven't had any issues with it. And the gain is very odd.
Speedily sent from CM7 Beta
Try alien, i had some battery issues with some other roms and kernels and tried alien and all is good.This phone comes with an 1930Mah battery one of the largest i've ever seen and it lasts me 12 hrs on heavy use.
battery stats
I've had great battery life on the atrix, now I'm getting a good look at the atrix on the 4800mah battery. I'm a heavy user and I could not get over 24 hours. And now I have 59 hours and I have yet to actually see how far I can take it. Cm7 beta. Juicey....
I find that all gingerbread roms have horrible battery life compared to froyo on the atrix. Cm7 battery is worse but the phone is smoother. Faux 1.3ghz kernel has even worse battery.
Regardless of the radio or magical method of resetting the battery state you use.
1:25 screen time and at 47% battery. Been off the charger for 6:15. It will make it through my 10hr shift with about 20% remaining if I'm lucky, usually I just toss it on the charger.
Background data is off, email and social apps are manual sync and wifi is off.
Sent from my MB860 using XDA Premium App
one weird thing I am seeing is the display which is at 0% brightness is using 91% battery
Also the better battery stats app says my actual battery is 91% but the phone is reporting 66% I wiped thenbattery stats but nothing!
please help!
If you haven't taken a look at it, give this a shot:
http://forum.xda-developers.com/showthread.php?t=1198333
Starting to mess around with your phone opens up a world of things that can go wrong. Learn to calm down, search the forums, and try a variety of fixes before giving up on something.
...and use nandroid.
ian426 said:
If you haven't taken a look at it, give this a shot:
http://forum.xda-developers.com/showthread.php?t=1198333
Starting to mess around with your phone opens up a world of things that can go wrong. Learn to calm down, search the forums, and try a variety of fixes before giving up on something.
...and use nandroid.
Click to expand...
Click to collapse
I was just about to post that lol. Also make sure every time you flash a new rom you are at 100% if not that is a sure fire way to cheat yourself out of battery life. I don't know if I'm just one of "the lucky ones" but I easily get over 16+ hours with moderate usage. I'm running CM7 beta with quite a few things frozen.
Ok so I followed the guide to perfection and it didn't improve the battery life one bit! I'm trying hard to find a t-mobile radio I can flash as I have read around it could be my radio that is the culprit and I am also getting rubbish HSDPA readings, I should be getting full bars but since switching to homebase Im only getting one bar.
Using watchdog I have noticed that the Xorg process is using over 50% cpu which does not seem right to be and I believe that because its a linux process Watchdog can't kill it. Is there anyway of fixing this?
1) Uninstall Tango, Facebook and Handcent SMS if any of the three are installed. They are huge battery drainers and you can find less battery hogging substitutes
2) Freeze any unnecessary apps, I believe there is a thread somewhere in the General section that has a pretty decent freeze list (if you flash CM7, you will have very little to freeze but that's good!)
3) Keep brightness down to a minimum when you can, I've noticed kicking the brightness up rather high can be pretty demanding on your battery
4) Set SetCPU Profiles to something like this...
Screen Off 216/216
Charging 1100/216
In Call 456/216
Battery <20% 456/216
Battery <10% 216/216
5) If you have the proper kernel set the CPU govner to power saver.
6) Undervolt, test yours and never apply set on boot unless you are positive it's stable, mine are something like this...
1100 MHz -50mV
1000 MHz -50mV
912 MHz -50mV
750 MHz -50mV
608 MHz -100mV
456 MHz -150mV
216 MHz -200mV
This way when you're phone is idling with the screen off, in a call or low on battery it is undervolting heavily to save maximum amounts of battery
With this setup I can get 30+ hours pretty regularly with moderate-to-heavy usage (weekdays/non-work days), 22-25 hours with more heavy usage (work days) and close to 48 hours with little usage (weekends).
It all depends on your usage and your phone but I have found this setup here to work fairly well.
I am currently on CM7 Beta, stock CM7 radio and stock CM7 kernel, running at 1100/216 when above profile conditions aren't met. 32% been running since 9 am this morning, it is now 3:15 am, today was a long workday.
I can almost guarantee (almost) that its your rom/kernel combination. Had same problem til I changed.
Sent from my MB860 using XDA Premium App
fastboot erase osh
That will nuke your webtop & fix your problem.
I'm now using faux kernel for CM7 and that hasn't improved anything, in fact I think it it has made it worse. It's getting really irretating because using the watch dog app it always says there is one linux process on every rom I use that is clocking at over 50% cpu usage and It won't let me kill it (probably because it's a linux process), its really annoying me because all I want is my phone to work properly but to enjoy the full rooting experience. I know countless amounts of people with atrix's and they get a full day and a bit out of their phone with heavy usage i can't even manage 10 hours!
amzter said:
I'm now using faux kernel for CM7 and that hasn't improved anything, in fact I think it it has made it worse. It's getting really irretating because using the watch dog app it always says there is one linux process on every rom I use that is clocking at over 50% cpu usage and It won't let me kill it (probably because it's a linux process), its really annoying me because all I want is my phone to work properly but to enjoy the full rooting experience. I know countless amounts of people with atrix's and they get a full day and a bit out of their phone with heavy usage i can't even manage 10 hours!
Click to expand...
Click to collapse
Watchdog eats battery like a mthrfckr, get away from that. Install BetterBatterStats instead & look for wakelocks. Which linux process are you noticing with that high cpu usage?
How many hours of screen time do you get in those 10 hrs?
Have you tried with a fastboot wipe & internal storage format prior to installing a new rom? Are you using the latest recommended radio for your phone?
amzter said:
please help!
Click to expand...
Click to collapse
Turn background syncing off if you are using that, and get in the habit of doing manual updates.
Too many times (with ANY Android device) people leave background syncing on and it tries sending/receiving data in a weak signal spot when you don't realize it. That's like a hot knife through butter on a battery.
Leave syncing off permanently if possible! That's a huge improvement right there for anyone...
Sent from my GT-I9000 using xda premium
ccrows said:
Turn background syncing off if you are using that, and get in the habit of doing manual updates.
Too many times (with ANY Android device) people leave background syncing on and it tries sending/receiving data in a weak signal spot when you don't realize it. That's like a hot knife through butter on a battery.
Leave syncing off permanently if possible! That's a huge improvement right there for anyone...
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
That's a bit radical, no?
I'd say use Green Power so the phone can update every half hour or hour. It's a smartphone at the end of the day..
When I was on 2.4.4, my battery lasted all day, no problem... But with dsc, it shuts off after about 14 hours... Without really doing anything... 50, maybe 100 texts, and occasionally checking fb. Should I reset the batterystat?
Don't get me wrong, it's better than 2.4.4, in every other way. But it drains battery like no ones business. I also always have it underclocked. So, the default overclock is not the issue.
Yes, it is you, check the back ground apps running, for me DSC has the best battery life after 360 .
No its not just him. I got pathetic battery life with DSC on pheonix kernel. I swapped it with olleh 407 and now battery lasts 2 days.
Sent from my Dell Streak using Tapatalk
The dsc has a problem with goggle maps running in the background. Try freezing gmapps and see if that helps.
Well, I've noticed that the scaling in setcpu kind of suck... I realized what was wrong. I accidentally had my min set for 768 >.> Conservative doesn't jump up fast enough to meet needs, and ondemand jumps up too much, draining the battery, lol... What happened to smartass/smartass v2?
So I took the plunge and unlocked my bootloader, and flashed the latest weekly of CM7. I love it so far, very responsive and quick.
I decided to flash the latest Faux123 kernel (CM7 Unified). After getting great quadrant scores, I was happy. I have a custom kernel on my Transformer TF-101 as well.
Here's my issue:
I get about 3 hours of battery life.
I clocked the kernel to max at 1.2ghz, and I even scaled the governor to powersave. (Using Rom Toolbox, min/max in SetCPU).
I have not undervolted anything at all.
My phone idle seems to shoot up to 40-50% most of the time, and SetCPU says that my phone spends most of it's time at 1ghz+. My TF would pretty much fall asleep at 216mhz, but that's a different device.
Is there something I'm missing?
This was a clean flash, and I always have plenty of free ram. I don't seem to have any wakelocks longer than 10 mins (alarm manager) either.
Oh, and my battery has been properly calibrated.
The stock kernel gave me great life (30+ hours). I expected a little loss, but not this bad after flashing.
Help!
Try a newer kernel. Governors don't work properly with our tegras. A newer kernel should have that disabled and more power save options.
Sent from my MB860 using XDA
What kernel do you suggest? Ive been out of the atrix scene for a good bit now lol.
My issues with battery life disappeared after installing jokersax's cm9 beta along with faux's kernel for cm9
Also be sure your battery isnt old and calibrate it(guides on main atrix forum)
Can I use a cm9 kernel on cm7? I don't really want to take the ICS route until it's developed a bit more.
My battery has been properly calibrated, though it still doesn't always hit 100%. I have no idea why either.
silentecho13 said:
Can I use a cm9 kernel on cm7? I don't really want to take the ICS route until it's developed a bit more.
My battery has been properly calibrated, though it still doesn't always hit 100%. I have no idea why either.
Click to expand...
Click to collapse
I woldnt try that.. About cm9, even though its beta, its pretty usable right now, most stuff works fine, you can always go back id it doesnt work.. I didnt went back bcuz battery is most important for me
Hmm, what about kholk or clemsyn's kernels?
silentecho13 said:
What kernel do you suggest? Ive been out of the atrix scene for a good bit now lol.
Click to expand...
Click to collapse
I've stuck with fauxs. I think I'm using version 23. I'm not using the lastest one as it makes one of my apps buggy and I don't like how my CPU jumps around when idle. He is currently working on those bugs, but they are hard to correct. Lots of other people are using it though with good results. I also stay with the 1.0ghz versions. Overclocks are nice but I don't need them and perfer the extra battery life.
Sent from my MB860 using XDA
So after a night's recharge, it seems to be working a little better.
CPU Spy says that it's in deep sleep most of the time.
Turns out I had SetCPU, Rom Toolbox, and CM7's settings regulating the clock speed. I uninstalled SetCPU, turned off Rom Toolbox, and let CM7 take care of it.
Life isn't as great as I expected, but its an improvement. The processor still does "jump around", but I expect that to be fixed at some point.
I considered clemsyn's kernel, but I don't want to risk not having an "elite tegra" and blow up my phone.
I really like the .24 1.3ghz Faux kernel. With SetCpu I change between 1.2OC (using lapdock) and 1.1OC (rest of time).
Battery life is equivalent to stock kernel. (I put it on charge when I go to bed and take it off early in the am). It usually has 50% left after streaming music to and from work/Endomondo using gps to track 45 minute workout, all my widgets (news and weather) and a few phone calls.
Phone stays much cooler.
Quadrant standard vs my wife's Atrix (fully stock) with the kernel at 1.1 is 30% better.
Stock ROM; not CM7 however.
I just looked at a days logs. It says that my phone spends 3+ hours in both 1.2ghz and 800mhz, and about 9 hours in deep sleep.
I haven't used my phone much today (40m of display time), and it already got to 15% between 9am and 6pm.
I can't seem to find what's keeping it up either, no obscene wakelocks.
My dad's galaxy s2 seems to drain pretty fast. When hardly using the phone (screen time of less than 20 minutes) the phone dies after being idle for a maximum of 13 hours.
When using GSam Battery Monitor to see what is draining the battery, everything seems normal expect for 'Kernel'. 'Kernel' uses 40% up to 85% of battery out of everything running on the phone. When the phone has been on for 10+ hours 'Kernel' is using more than 2 hour cpu time.
When looking at BetterBatteryStats nothing strange shows.
When looking at Cpu Spy the phone deep sleeps a lot (60-80%) and 200 Mhz being the most used frequency after deep sleep (15-35%).
Pretty much everything seems to be fine, no apps draining the phone as far as I can see. No sync stuff draining the phone.
The only thing I noticed is that 'android system' is using the accelerometer and gyroscope for quite some time (it seems the accelerometer is always in use, the gyroscope can be in use for 30min-2 hours depending on how long the phone has been on).
For me it's not clear why 'Kernel' is using that much bettery. Looking at my HTC One X for example it almost never uses more than 9% battery (out of 100% which includes everything, radio, apps, wifi, etc). On my HTC One X 'Kernel' also almost never uses more than 25min cpu time even when the phone has been on for 13+ hours. It sounds to me that the kernel shouldn't drain the battery that much, especially when the phone is deep sleeping a lot.
I'm running CM9 RC2 (been using the CM9 nightlies before RC2, same issues). Tried other roms like NeatLite and NeatFull. Tried stock kernels from those roms, and tried other kernels as well. Same issue.
Any help is very appreciated. Thanks in advance.
damanrico said:
My dad's galaxy s2 seems to drain pretty fast. When hardly using the phone (screen time of less than 20 minutes) the phone dies after being idle for a maximum of 13 hours.
When using GSam Battery Monitor to see what is draining the battery, everything seems normal expect for 'Kernel'. 'Kernel' uses 40% up to 85% of battery out of everything running on the phone. When the phone has been on for 10+ hours 'Kernel' is using more than 2 hour cpu time.
When looking at BetterBatteryStats nothing strange shows.
When looking at Cpu Spy the phone deep sleeps a lot (60-80%) and 200 Mhz being the most used frequency after deep sleep (15-35%).
Pretty much everything seems to be fine, no apps draining the phone as far as I can see. No sync stuff draining the phone.
The only thing I noticed is that 'android system' is using the accelerometer and gyroscope for quite some time (it seems the accelerometer is always in use, the gyroscope can be in use for 30min-2 hours depending on how long the phone has been on).
For me it's not clear why 'Kernel' is using that much bettery. Looking at my HTC One X for example it almost never uses more than 9% battery (out of 100% which includes everything, radio, apps, wifi, etc). On my HTC One X 'Kernel' also almost never uses more than 25min cpu time even when the phone has been on for 13+ hours. It sounds to me that the kernel shouldn't drain the battery that much, especially when the phone is deep sleeping a lot.
I'm running CM9 RC2 (been using the CM9 nightlies before RC2, same issues). Tried other roms like NeatLite and NeatFull. Tried stock kernels from those roms, and tried other kernels as well. Same issue.
Any help is very appreciated. Thanks in advance.
Click to expand...
Click to collapse
ok it isn't normal that the phone die after 13hours while sleeping, however the only app that will tell you every thing about the battery drain issue will be better battery status , try it and provide us with log, you will see about each app, and know if there is any app missbehaving, but if every works as expected , i think it will be abattery issue, change it and try,
btw: with cm9 you can't use stock kernels, use aosp/aokp kerenls, stock kernels only with samsung based roms
evaworld said:
ok it isn't normal that the phone die after 13hours while sleeping, however the only app that will tell you every thing about the battery drain issue will be better battery status , try it and provide us with log, you will see about each app, and know if there is any app missbehaving, but if every works as expected , i think it will be abattery issue, change it and try,
btw: with cm9 you can't use stock kernels, use aosp/aokp kerenls, stock kernels only with samsung based roms
Click to expand...
Click to collapse
I meant stock kernel as in the stock cm9 kernel.
I do think GSam Battery Monitor is a decent app for a global overview of what has been using the battery. When it says the kernel has been using the battery (by using a lot of cpu time), I do believe that's true. Especially since other phones in my household that aren't draining show the kernel is hardly using cpu time.
Here's a log file from BBS. Nothing strange to me, but maybe I'm looking at it wrong. See the attachment for the BBS log.
Bump, same issue. Accelerometer is also on for multiple hours. Battery drains too fast, noghing is amiss in BBS or Gsam.
i have exactly the same problem with my fathers s2.
can someone help?
michael
the same problem is with my SII & its started after I switched to AOKP JB MILESTIONE 1 ROM with Dorimanx Kernel..... Kernel CPU usgae is very high when screen is off for 5-6hrs.
Now, i have switched to Siyah kernel.... lets see if that improves the situation.