Related
I have Battery Status 1.04 beta on my 8125..I set the CPU Scaler to underclock to 112mhz when idle (original is 195mhz). It seems to be doing that, but idle battery life so far doesn't look any better, in fact maybe worse. Is CPUScaler not meant to be used like that?
Comit said:
I have Battery Status 1.04 beta on my 8125..I set the CPU Scaler to underclock to 112mhz when idle (original is 195mhz). It seems to be doing that, but idle battery life so far doesn't look any better, in fact maybe worse. Is CPUScaler not meant to be used like that?
Click to expand...
Click to collapse
it does / will / or is supposed to help by slowing down your processor when it isn't actively being used. But 112 seems really low to me. I've heard that some people find their phones won't wake back up when it drops too low (I think 123Mhz is what I've read people use but lower than that caused problems). Personally I set mine to 143 for the min.
If you are running WM6, there just seems to be more power drain. Also depends on what radio you are running (some are better than others) and if you leave WiFI and/or bluetooth turned on all the time.
Also I've read that some apps will cause more power draw due to them running. With BatteryStatus when your phone is idle, does the CPU % go down to 1 - 3%? If so, you should be ok. But if it stays higher, then something is running and that adds to more power draw.
There is also a thread in the Wizard WM6 forum on people finding that playing with the extended rom seems to impact on power draw if you've done a hard reset or similar (they are finding that by going back to an official rom like TMo 2.26 and then reinstalling the custom rom that doesn't have an extended rom the power draw seems to go away).
Hope some of that helps...
Haven't had any missed calls AFAIK, been running it like this for a couple days now. My ROM is Faria's AKU 3.3, which is pretty good might I add.
Idle CPU utilization stays at 1%
The extended ROM theory is interesting, maybe thats whats doing it. My last ROM didn't have anything like that and seemd to have better idle battery life.
If the phone is at idle, what does it matter where it's clocked? When the phone is active, the battery will be drained regardless of clock speed. I have my 8125 set at 192MHz, nd have no problem re-charging the battery.
Hi,
I rooted/overclocked (to 1.4Ghz) my Xoom a couple of weeks ago and everything seemed ok, all of a sudden though the battery is draining rapidly throughout the day.
In standby with light usage over the last 5 hours the battery has been depleted by nearly 30%, by light usage I mean I looked at my tweets in the Twitter app for about 15 mins.
I keep the screen brightness on auto but it generally stays quite dim, in SetCPU the scaling is set to OnDemand and the Xoom is connected to a wireless network with almost full signal so it's not constantly searching for a network. Before I rooted the battery would last for a few days with average usage and now I'm charging it every night.
Any ideas what could have happened? I'm running the 2.6.36.4Tiamat-Xoom-v2.0.0-Katana-GPUOC-gfed7aa6 kernal.
Thanks,
Rich
rich549 said:
Hi,
I rooted/overclocked (to 1.4Ghz) my Xoom a couple of weeks ago and everything seemed ok, all of a sudden though the battery is draining rapidly throughout the day.
In standby with light usage over the last 5 hours the battery has been depleted by nearly 30%, by light usage I mean I looked at my tweets in the Twitter app for about 15 mins.
I keep the screen brightness on auto but it generally stays quite dim, in SetCPU the scaling is set to OnDemand and the Xoom is connected to a wireless network with almost full signal so it's not constantly searching for a network. Before I rooted the battery would last for a few days with average usage and now I'm charging it every night.
Any ideas what could have happened? I'm running the 2.6.36.4Tiamat-Xoom-v2.0.0-Katana-GPUOC-gfed7aa6 kernal.
Thanks,
Rich
Click to expand...
Click to collapse
You are overclocking. That will drain battery faster. Also you didn't mention if you have set profiles in Set CPU to save battery charge when the screen is off, for instance. I set mine on interactive, as well, as Team Tiamat has advised. Also look at what is using your battery the most--screen will be most of it. Also, some apps try to sync all the time and your battery can drain faster that way.
Well I knew that by overclocking I'd drain the battery faster, but I didn't expect the drain to increase so dramatically! You've made a good point with the profiles in SetCPU, I'l be honest and say that I havent really had much of a look around the app other than overclocking the CPU and using the info screen to check the temperature, benchmarking etc.
I'll give the profiles a try, with regards to apps that sync data constantly I've only used the email, gmail and twitter clients for this since I brought the device so I wouldn't have expected this to contribute to the increased drain.
I'm no noob to Android devices and rooting but overclocking is a whole new thing to me
So you overclocked your CPU and gpu to use twitter and the gmail client?
albundy2010 said:
So you overclocked your CPU and gpu to use twitter and the gmail client?
Click to expand...
Click to collapse
Errrr no.... they're just the apps that are always syncing data from the web, I was giving an example of the apps that are always syncing to answer the previous poster's point that a lot of apps will sync data in the background.
--Update--
Adding a ScreenOff profile to SetCPU didnt help very much, set the max CPU to 312 and min to 216, also set scaling to Conservative. Proceeded to charge the Xoom to 100% and then left it on standby all night, this morning the battery was down to 68%.
I've now restored my Xoom to a backup I did the same day I overclocked it, as I mentioned in my original post this issue only started a couple of weeks after overclocking.
About a month ago, I was running RoyalGinger 3.0 with bluetooth, GPS, and background data disabled, and I was only using my home wifi to get online. My phone would pretty much hold a 100% charge for 5-8 hours if I left the screen off. I was pretty amazed at my battery life. Then I decided I wanted to try a different rom, so I backed up in CWM and did that. When I returned to RoyalGinger, my phone wasn't holding the 100% charge for as long anymore and hasn't done it since then (yes, I did re-calibrate the battery, like twice at least).
Recently though, my phone has been having horrible battery life under the same conditions. The only difference is that now I use LauncherPro instead of the stock launcher. I'll charge to 100% + 15 minutes or so, and with the screen off, the phone divebombs to about 95% within an hour and a half. If I actually use the phone, it will lose 30% in 2 hours. I have no idea what the problem could be since I don't have any data-syncing apps in the background and I'm really just texting people.
Any ideas?
The consumption doesn't sound like anything out of normal. A difference in signal quality (radio or WiFi) or using radio for data instead of WiFi can cause that.
In any case, just check the apps that use your battery, and see that you don't have any process getting CPU stuck on 100% (you can see CPU load in System Panel Lite, for example).
Download the apps below.....this will help you out.....
Use the app SetCPU for Root Users
It allows control of certain aspects of the Linux cpu freq driver, allowing for overclocking, underclocking, or tweaking speeds and settings. Download it here.
Use the app Battery Booster
Battery Booster is a powerful battery boosting tool and power management application specially designed for Android devices. Download it here.
Always remember to remove the charger immediately when the battery level reach 100% for longer battery life.
So I have the rev11 nexus 4 and it seems to have pretty awful battery life.. I'm running cm10.1 with the latest faux kernel with the faux clock app all set up: min clock is 594, max set at 1.35, intellidemand governor, eco mode and snake charmer on, voltage at -50mV, as well. I can't fit hardly any apps on this phone because I mistakenly got the 8gb version and can barely fit all the pictures and videos and music.. So no rouge apps or anything effecting the battery (I've already checked). The phones battery is at 40c, and CPU temp at 56c. Because of this, even when I have my phone set up the way it is and the brightness all the way down, I still only get 3 hours MAX of on screen time before it shuts off, completely dead. I've had this phone for a month but I'm about to call for yet another replacement (first one was defective but still had really good battery life). Does anyone have similar issues and should I definitely call and try to get a replacement?
BravoMotorola said:
So I have the rev11 nexus 4 and it seems to have pretty awful battery life.. I'm running cm10.1 with the latest faux kernel with the faux clock app all set up: min clock is 594, max set at 1.35, intellidemand governor, eco mode and snake charmer on, voltage at -50mV, as well. I can't fit hardly any apps on this phone because I mistakenly got the 8gb version and can barely fit all the pictures and videos and music.. So no rouge apps or anything effecting the battery (I've already checked). The phones battery is at 40c, and CPU temp at 56c. Because of this, even when I have my phone set up the way it is and the brightness all the way down, I still only get 3 hours MAX of on screen time before it shuts off, completely dead. I've had this phone for a month but I'm about to call for yet another replacement (first one was defective but still had really good battery life). Does anyone have similar issues and should I definitely call and try to get a replacement?
Click to expand...
Click to collapse
Battery drain is mostly caused by installed user apps running in the background and/or sync settings. Have you installed BetteBatteryStatts to see what consumes most energy? Also install CPU Spy for deep sleep issues.
gee2012 said:
Battery drain is mostly caused by installed user apps running in the background and/or sync settings. Have you installed BetteBatteryStatts to see what consumes most energy? Also install CPU Spy for deep sleep issues.
Click to expand...
Click to collapse
Well as I said in my post there are no rogue background apps. The only apps I even have installed are reddit, fauxclock, cpu spy, and xda. I've looked and no internal processes use up much battery also. It's just the screen which is on the lowest brightness setting that seems to suck all the battery which usually doesn't even last three hours.
BravoMotorola said:
Well as I said in my post there are no rogue background apps. The only apps I even have installed are reddit, fauxclock, cpu spy, and xda. I've looked and no internal processes use up much battery also. It's just the screen which is on the lowest brightness setting that seems to suck all the battery which usually doesn't even last three hours.
Click to expand...
Click to collapse
Maybe a faulty battery, i get 3,5 to 4 hours screen on time with 50% brightness. Running stock rom and kernel atm.
I haven't had any battery drainage with my N4, but with my previous phone I did. In most cases when I had that type of drain, I would reflash the radio or flash a different one and that would cure it. I'm not sure what would cause the drain, but I was flashing different roms and at some point radio performance would drop off. I have seen some complaints with severe battery drainage with the N4, but I haven't seen anyone trying a fresh radio install. Might not help, but could be worth a shot.
fernandezhjr said:
I haven't had any battery drainage with my N4, but with my previous phone I did. In most cases when I had that type of drain, I would reflash the radio or flash a different one and that would cure it. I'm not sure what would cause the drain, but I was flashing different roms and at some point radio performance would drop off. I have seen some complaints with severe battery drainage with the N4, but I haven't seen anyone trying a fresh radio install. Might not help, but could be worth a shot.
Click to expand...
Click to collapse
I think what I'm going to do is just flash it back completely to stock and just use it for a week without installing anything. If I still only get 3 hours of screen on time I will try to RMA it. There just has to be something screwed up with this phone though because my last phone with the same settings applied got at the very least 5 hours of screen on time. When I can't even go through half a day on this phone with normal usage, even after tweaking and cutting performance along with always having low brightness then I think there is a problem.
My Son's Nexus 10 had served its purpose. But Started to die at Random percent, Mostly above 50%.. So Got a new Tablet for him. But Did not want to throw away this Gem of a Tablet.
After weeks of Trial and Error finally found a solution Thanks to input from a Redditor.
Issue/Problem: Dies at Random % showing battery %0 and Shutdown. But In Recovery with Full Brightness it does not Die for hours.. (as later found out.. Recovery does not need much CPU power)
So What did I try:
1. Changed Rom's (All the way from Base Google Images to Oreo) >> Did NOT fix the Problem
2. Clearing battery stats.. etc. ( incl completely discharge and Charge and all those cycles usually we do to calibrate the battery) >> Did NOT Fix the Problem
2. Ordered a New Battery - (Samsung Model From Ebay - I guess it was used or who knows ) >> Did NOT fix the Problem
3. Changed Multiple chargers (Wall Adapters/ Cable from multiple brands which i have at home.. LG, Samsung etc etc) >> Did NOT Fix the Problem
Solution/ What Fixed:
Thanks to redditor.. Who mentioned about CPU power consumption.. And Old Mother board might not be providing enough Power to CPU. (As this tablet is Old.. It was just an Hobby to make it work and Did not want to spend more money on MotherBoard)
By this time I was on Marshmallow Linage OS Rom.. (As Everything works), Gave Root access to one of the CPU app's and Did this..(See Below) Enabled on Boot to keep the same settings.
Setting the CPU max to 1200MHz and Min to 200 it WORKED! I tried every damn thing before. For some reason... this idea did not strike my brain. So its the Power consumption from CPU.
EDIT 1: after some more testing You can go upto MAX 1600MHz (Your mileage may vary)
Finally Battery drained till zero without shutting down.
LET ME KNOW IF THIS FIXED YOUR TABLET TOO.. If you have the same issue as mine. (I Know many had this issue like mine.. but none had solution) Hope this helps.
streetsmart999 said:
My Son's Nexus 10 had served its purpose. But Started to die at Random percent, Mostly above 50%.. So Got a new Tablet for him. But Did not want to throw away this Gem of a Tablet.
After weeks of Trial and Error finally found a solution Thanks to input from a Redditor.
Issue/Problem: Dies at Random % showing battery %0 and Shutdown. But In Recovery with Full Brightness it does not Die for hours.. (as later found out.. Recovery does not need much CPU power)
So What did I try:
1. Changed Rom's (All the way from Base Google Images to Oreo) >> Did NOT fix the Problem
2. Clearing battery stats.. etc. ( incl completely discharge and Charge and all those cycles usually we do to calibrate the battery) >> Did NOT Fix the Problem
2. Ordered a New Battery - (Samsung Model From Ebay - I guess it was used or who knows ) >> Did NOT fix the Problem
3. Changed Multiple chargers (Wall Adapters/ Cable from multiple brands which i have at home.. LG, Samsung etc etc) >> Did NOT Fix the Problem
Solution/ What Fixed:
Thanks to redditor.. Who mentioned about CPU power consumption.. And Old Mother board might not be providing enough Power to CPU. (As this tablet is Old.. It was just an Hobby to make it work and Did not want to spend more money on MotherBoard)
By this time I was on Marshmallow Linage OS Rom.. (As Everything works), Gave Root access to one of the CPU app's and Did this..(See Below) Enabled on Boot to keep the same settings.
Setting the CPU max to 1200MHz and Min to 200 it WORKED! I tried every damn thing before. For some reason... this idea did not strike my brain. So its the Power consumption from CPU.
Finally Battery drained till zero without shutting down.
LET ME KNOW IF THIS FIXED YOUR TABLET TOO.. If you have the same issue as mine. (I Know many had this issue like mine.. but none had solution) Hope this helps.
Click to expand...
Click to collapse
Hi!
I have the same problem for a while. Could you tell me which CPU app did you use?
I thank you very much for your help.
Marco
Kukl said:
Hi!
I have the same problem for a while. Could you tell me which CPU app did you use?
I thank you very much for your help.
Marco
Click to expand...
Click to collapse
I used below app (But u can use any CPU app).. But other than those above setting(s).. I DID NOT change anything else. But u need ROOT to make that change.
Good Luck. hopefully it helps you too.
https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor
streetsmart999 said:
I used below app (But u can use any CPU app).. But other than those above setting(s).. I DID NOT change anything else. But u need ROOT to make that change.
Good Luck. hopefully it helps you too.
https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor
Click to expand...
Click to collapse
I try it immediately, I hope it works!
Thank you very much
Kukl said:
I try it immediately, I hope it works!
Thank you very much
Click to expand...
Click to collapse
Hey You can go MAX upto 1600.. If that doesn't work for u.. Keep reducing a lil by little.
streetsmart999 said:
Hey You can go MAX upto 1600.. If that doesn't work for u.. Keep reducing a lil by little.
Click to expand...
Click to collapse
Unfortunately at the moment I don't solved the problem, even if I set the cpu min to 200 and max to 1200.
I've installed a new ROM, deleted the cache and still the problem persists. I will do other tests trying to recalibrate the battery.
Kukl said:
Unfortunately at the moment I don't solved the problem, even if I set the cpu min to 200 and max to 1200.
I've installed a new ROM, deleted the cache and still the problem persists. I will do other tests trying to recalibrate the battery.
Click to expand...
Click to collapse
Humm... Anyway @1600 mine died at 30% .. So made it 1500 and past below 18% and Still running. So I guess 1500 is max I can go
Also Before coming this conclusion: I did the fowling
Charge 100%
Delete Batterystats.bin
Run this command from adb "adb shell dumpsys batterystats --reset"
And then Changed the CPU max (Please NOTE , Select "On Boot" to keep the same parameters). Once u change the CPU settings .. Reboot and see .. if its keeping the same settings.
Many thanks. I tried all of the the things you tried and setting the cpu max frequency is the only thing that worked.
I could get away with seeing it to 1600.
Deleting batterystats.bin does nothing https://www.xda-developers.com/goog...-battery-stats-does-not-improve-battery-life/
Now with a new battery, PureNexus Rom and your amazing fix my Nexus 10 is a thing of beauty again.
LET ME KNOW IF THIS FIXED YOUR TABLET TOO..
Click to expand...
Click to collapse
Streetmart you absolute legend. I'd never thought I'd see the day my Nexus 10 would drain down to zero again. I tried 1600, then 1500, to no avail; then I said screw it I'll just go down to 1200 (with little hope of it working).
It feels so weird to actually have an internet “solution” work. I'm super happy. I didn't want to buy another tablet. I love this one and it worka perfect for what I use it for.
Thank you! :good::highfive:
OMG! thank you for this thread! i was just posting to look for a replacement for my 10... i hope this fixes it BTW.. what's the normal max cpu speed? I REALLY don't want to replace it as the new dropbox 3 device thing really screws me..
Icetech3 said:
OMG! thank you for this thread! i was just posting to look for a replacement for my 10... i hope this fixes it BTW.. what's the normal max cpu speed? I REALLY don't want to replace it as the new dropbox 3 device thing really screws me..
Click to expand...
Click to collapse
I think the normal is 1700MHz. It's what the program showed before I changed it. All the best! Keep us updated.
Hez0 said:
I think the normal is 1700MHz. It's what the program showed before I changed it. All the best! Keep us updated.
Click to expand...
Click to collapse
What a difference... i installed that a few days ago, and i haven't used my N10 much but on standby it's still at 99% usually it would be WAY lower.. i think that program did more than just lower the max cpu a little.. don't care though. the N10 lives on!!
If you still have this issue, I have been updating the kernel and also found some of the power control settings needed tweaked. Disabling "opportunistic sleep" "logging time spent in suspend" and enabling "advanced power controls" seems to do the trick. had an issue where the device would shut off if battery level reached 20%. Haven't had it happen again yet.
DragonFire1024 said:
If you still have this issue, I have been updating the kernel and also found some of the power control settings needed tweaked. Disabling "opportunistic sleep" "logging time spent in suspend" and enabling "advanced power controls" seems to do the trick. had an issue where the device would shut off if battery level reached 20%. Haven't had it happen again yet.
Click to expand...
Click to collapse
I'm currently running at 1600 with this guy modified kernel and wow, besides no more suddenly shutdowns it runs very smoothly, it reminds me the pre-marshmallow age of this tablet.
DragonFire1024 said:
If you still have this issue, I have been updating the kernel and also found some of the power control settings needed tweaked. Disabling "opportunistic sleep" "logging time spent in suspend" and enabling "advanced power controls" seems to do the trick. had an issue where the device would shut off if battery level reached 20%. Haven't had it happen again yet.
Click to expand...
Click to collapse
Where are you finding these control settings to change?
I have replace the battery of my N10 because of low capacity.
Now it charge from 0% to 52% then it goes to 100%. On discharge it goes from 100% to 46% then shutdown and battery shows 0%. Percentage is the same in TWRP.
Since replacement of battery it have aroud 10 charge/discharge cycles without any changes.
Any solution for that?
Der_Graf said:
I have replace the battery of my N10 because of low capacity.
Now it charge from 0% to 52% then it goes to 100%. On discharge it goes from 100% to 46% then shutdown and battery shows 0%. Percentage is the same in TWRP.
Since replacement of battery it have aroud 10 charge/discharge cycles without any changes.
Any solution for that?
Click to expand...
Click to collapse
I have to agree on, that the N10 chipset/cpu/powersupply has degraded somewhat & as the battery voltage gets lower during discharge, it can not supply stable power any longer :crying:
If i reduce the CPU speed from 1700MHz to 1200MHz I get to go down to 20% instead the N10 shutting down abruptly at just 30%
I do have a spare battery in the fridge for later on. Once I open up the N10, I'll see if there is a capacitor or two, that could replaced in the power supply area to possibly fix the issue.
Note:
1. On second full charge since lowering the CPU to 1200MHz the battery got down to 14% & I have decided to charge it instead of letting it die at some point at a lower percentage
2. I should have mentioned earlier, that I still use the original N10 battery & plan to replace the original battery with a new aftermarket battery later on if I need to.
3. I use the N10 in an air-conditioned room for no longer, than half an hour at a time only browsing & reading articles with a short 10min video from YouTube.
4. Before lowering the CPU clock from 1700MHz to 1200MHz, the tablet consistently has shut down abruptly, at 27-30% battery level to my dismay.
5. Tried complete battery drain / cache reset to 0% in Recovery mode & then fully charging it while shut down 3 times without success.
6. So far lowering the CPU clock has made a difference & for prof now I am evaluating the N10 battery capacity with AccuBattery.
7. I charge my devices at around 20-25% or higher up to 80% to prolong battery life using apk's to stop charging or alert me.
I have switched to the UNOFFICIAL Resurrection Remix for Nexus 10 (ResurrectionRemix-M-v5.7.4-20161208-manta) MM ROM after rooting my N10 (Danke schön Corinna ) & had to update the baked in Kernel Adiutor.
Installing from APKMirror the "Kernel Adiutor (ROOT) 0.9.73 beta (Android 4.0.3+)" has allowed me to lower CPU MAX Frequency and have it stick after BOOT!
com.grarak.kerneladiutor_0.9.73_beta-241_minAPI15(nodpi)_apkmirror.com
Ottoman Mint said:
I have to agree on, that the N10 chipset/cpu/powersupply has degraded somewhat & as the battery voltage gets lower during discharge, it can not supply stable power any longer :crying:
Click to expand...
Click to collapse
I don´t think so. The capacity of new battery looks really good. I use the N10 as wall-mounted control tablet for my home. With activated DT2W, full brightness, showing cams on motion, controlling home and audio over the day, my new battery runs about 28 hours before it stops. With old battery it was around 15-18 hours from full to off. My workaround: Reading battery with tasker and starts charging at 50%
I think the china batterys have different voltages than samsung batterys and N10 can´t work with this.
Der_Graf said:
I don´t think so. The capacity of new battery looks really good. I use the N10 as wall-mounted control tablet for my home. With activated DT2W, full brightness, showing cams on motion, controlling home and audio over the day, my new battery runs about 28 hours before it stops. With old battery it was around 15-18 hours from full to off. My workaround: Reading battery with tasker and starts charging at 50%
I think the china batterys have different voltages than samsung batterys and N10 can´t work with this.
Click to expand...
Click to collapse
Hey,
That sounds very interesting. I may find out about that, when I replace the original N10 battery to my replacement battery from China.
I forgot to mention in my post earlier, that I am still using the original N10 battery. The original N10 battery keeps crashing at 30% unless I lower the CPU clock to 1200MHz.
After the first charge at (1200MHz max CPU) I got the N10 down to 20%+ before crashing to shut down & after the second charge I got it down to 14% at the same 1200MHz without crashing to shut down & just recharged it. Mind you I was just surfing the net & watching YouTube. I am also using AccuBattery to estimate the battery capacity atm. (Oh & don't install Battery Charge Limiter, because it boot-loops the N10 after install!)
DT2W sounds awesome. Which ROM are you using on your N10 to get DT2W, if you don't mind me asking?
Ottoman Mint said:
Hey,
That sounds very interesting. I may find out about that, when I replace the original N10 battery to my replacement battery from China.
I forgot to mention in my post earlier, that I am still using the original N10 battery. The original N10 battery keeps crashing at 30% unless I lower the CPU clock to 1200MHz.
After the first charge at (1200MHz max CPU) I got the N10 down to 20%+ before crashing to shut down & after the second charge I got it down to 14% at the same 1200MHz without crashing to shut down & just recharged it. Mind you I was just surfing the net & watching YouTube. I am also using AccuBattery to estimate the battery capacity atm. (Oh & don't install Battery Charge Limiter, because it boot-loops the N10 after install!)
DT2W sounds awesome. Which ROM are you using on your N10 to get DT2W, if you don't mind me asking?
Click to expand...
Click to collapse
Sometimes it shuts down at 20% and other times it won't. I'm almost pretty sure it doesn't have anything to do with advanced power settings or any kind of internal power settings with the kernel. There are no thermal configurations on this device and they don't add any drivers for it or support for it until much later versions. Heat seems to play a role especially down here Florida when outside. So far in my experience it's most likely to shut down at 20% if it's too hot and not likely to do so if it's been idle for a bit or not plugged in.
Sent from my Samsung Nexus 10 using XDA Labs