Related
Be warned that this thread is now outdated. There might be more current guides available…
THE ULTIMATE GUIDE TO MAKING YOUR BATTERY LAST LONGER ON YOUR HTC HD2 WITH ANDROID
OK I suppose this should be stickied as I've found numerous threads saying various stuff, but not a single thread, dedicated solely to this, providing useful and organized info.
Note: This guide is by no means definitive. Please feel free to correct me and add more tips, I'll be sure to add them to this post.
STEPS:
1. Try out a few ROMs and Radios to see which combination works best for keeping Android run as long as possible.
I have yet to find the best combo for my phone, but generally, the lightest ROMs with not much bloat in them (lots of items removed, fast startup) work best. With Radios it's all trial and error – a Radio that works miracles for one user is useless for another. You just have to try and see.
I know this is probably driving you crazy as you can read it everywhere around, but this can't be stressed enough: Don't flash your phone with a ROM/Radio you're not absolutely sure won't brick it. No one wants you to brick your expensive device. Read the flashing guides very carefully before you go on and do it.
Updating your build's Kernel is also a good idea.
2. Make sure you boot Android up as fast after running Windows as possible.
This one is crucial as it seems to affect your battery a lot.
To aid this, you can:
Download and install this (free) app (Exceller Multiple Build Loader is what I use, but you can choose something else) for the WM6. It enables you to autoboot into Android in the timespan of three seconds after running Windows, which is what you ideally want to do.
Disable HTC Sense in WM, it's unnecessary if you just want to boot into Android and takes a lot of time to load up. To do this, go to System settings, press Home, go to the Items tab and uncheck HTC Sense. You may want to check Windows Default to have at least the Zune-style interface to start from, but this isn't necessary if you're ok with an empty homescreen in WM.
3. Decrease the system load by automatically killing apps you no longer use.
This one gives a fair battery boost. By default, Android keeps all apps ready in RAM even if you press Home or Back to exit them to make them start quickly next time you need them and to keep their state. Most apps have a suspend mode which enables them to demand close to zero system resources as they run in the background, but some don't and close to zero isn't zero.
Download and install Automatic Task Killer (free) from the Market.
It gives you a list of the installed apps and enables you to uncheck those you don't want to autokill. It can also add your new apps to the list automatically.
Don't forget to uncheck applications you need to be running constantly, such as SetCPU (see below).
According to hastarin, this doesn't give you a battery boost. See the "What DOESN'T improve battery life" section. You can use AutoKiller Memory Optimizer, if you want to tweak your RAM – this app lets you set the limits for automatically killing apps only when you're low on RAM, which in turn may give you a battery boost.
4. Decrease the CPU performance when it doesn't need to perform at full speed.
I'm sure you're proud of your HD2's Snapdragon running at 1 GHz, I know I am, but it also drains a lot of battery when running on full speed.
NOTE: Using SetCPU with hastarin's R8 Kernel makes it redundant as the Kernel already has an interactive CPU governor in it. Thanks to socrated13 and atticus182 for this tip.
Download and install SetCPU ($1.99) from the Market.
It allows you to underclock your CPU to save battery. You can set profiles and play around with them. Generally, you don't want to set the minimum frequency too low as some tasks may then consume significantly more time to complete, wasting the energy you gained.
If you just want to try the app first to see if it helps, you can get it for free (search for SetCPU here at xda) and donate later by buying it on the Market (and please do, the developer put a lot of effort into it).
5. [INFORMATIVE] See how much energy your phone drains.
This one is not compulsory, but helps to get a general idea of how much energy your phone drains when you do such and such.
Download and install the Current Widget (free) from this forum. Just do a search on "current widget" and it should be the first post that comes up (don't worry, yes it's under Samsung Vibrant, but it works just as good for the HD2)
It allows you to put a widget on one of your home screens, where you can see the current your phone is currently draining. Can be set to update at various intervals. I prefer 30 s as it gives me enough time to shut down an app and look at it to see how much current the app itself is draining.
6. Decrease the brightness of your display.
This saves an incredible amount of battery life. I know you love your AutoBrightness, but it sets the brightness unnecessarily high, so until someone makes an AutoBrightness app with customizable overall brightness (once I get into programming apps for the Droid a bit, I might do it), you're left with doing this yourself.
Download and install the Brightness Rocker Lite (free) app from the market.
It displays a brightness bar everytime you bring up the volume control and thus lets you quickly change the brightness. Use the minimum brightness to see everything clearly and you should conserve a lot of juice.
7. Only use wireless functions when needed.
Having the mobile data connection, wifi, GPS or bluetooth enabled all the time causes severe battery drain. Sometimes even after you disconnect, the data connection connects again without you even knowing, downloading Over-the-Air updates or Weather, draining your battery unnecessarily.
Have a quick way to monitor which services are on and to turn them off (preferrably, have a widget/widgets on your home screen - I recommend the native Android widgets).
8. Recondition your phone for your battery after flashing each new Android build. (Thanks to t1h5ta3 for this tip)
Flashing a new Android build erases the battery stats and automatically rebuilds them based on voltages it sees, i.e. you need to recondition after each flash to get max battery life. The values are stored in the following file: data/system/batterystats.bin – if you delete this file, you set the new ground for making a new one from the value you want.
You can use the "battery life" widget by curvefish to show you temperature, voltage etc. What you're going for is voltage larger than 4.2 V on full charge.
To recondition:
Turn off the phone, plug it in, preferably overnight.
Boot the phone up while still pluged in.
Delete the batterystats.bin file ether through adb or terminal.
Drain the battery fully, until it powers down. Wait a minute or two and reboot it to drain it completely.
Congrats... your phone now knows corect voltage values for 100% and dead.
To delete the batterystats.bin file:
Find the means to be able to punch in lines of code. You can do this either by downloading and setting up the Android SDK or using a simplifying app like Droid Explorer. Do a google search for whichever you prefer.
Punch in the following code:
Code:
rm data/system/batterystats.bin
Or just find the file in Droid Explorer and delete it.
What DOESN'T improve battery life:
Getting a slower (and thus presumably less power-consuming) SD Card – because a slower SD card actually makes things worse as it needs more time to perform a task and thus keep the CPU busy a longer time.
Underclocking your CPU too much – similar reasons
Killing tasks automatically immediately after closing them – this apparently makes battery life worse, because when a program is in RAM, it doesn't consume system resources, but when you run it again, it does. Thanks to hastarin for the clarification.
Useful threads concerning battery life:
[REF] UPDATE: ALL GOVERNORS! Save battery while running ANY Android build (featured by the xda crew)
battery voltage / wipe batt stats
Battery Solution the **FINAL POST**
Time to Recharge to Full Battery
[TIPS] Thoughts on improving battery life for Android on the HD2
[UPD] 48hours + battery with mDeejay Froyo Z v1.7
Best SD Card for Overall Android Battery Life
Increase Battery Life [WinMo registry tweaks - Need confirmation] (do give this a try)
Hope this helps. If you have more tips or on-topic threads, I'll be delighted to add.
also see http://forum.xda-developers.com/showthread.php?t=827355
a properly conditioned battery does wonders for battery life. a fully charged battery shuld be over 4.2v . i was finding that depending on the the true state of charge when flashing, that is the level that was being assumed by the phone as " 100%" charged. ie: when i flashed my current rom it quit charging @ only 3.7xx volts... far from fully charged.
see my thread on the file to delete etc.
edit: after doing alot more research; heres what ive found...
for what its worth: Li-Io battery technology realy isnt different whether it be a phone, rc car, etc...
our batterys are a single cell. ie: rated 3.7v
4.2-4.25v is concidered by the industry as fully charged
3.7v is nominal voltage
3.2v "shorted" voltage : ie: voltage sag due to max discharge @nominal voltage
3.0v discharged
2.5v protection circuitry kicks in.
this jives with what i am now seeing on my phone after wipeing stats and calibrating...
it is also a industry standard to fully discharge ( 3.0v )about every 30 discharge cycles.
edit
Thanks, I added your tip in the first post (will add the link to your thread too, forgot to do it now and can't edit within 5 minutes of last edit yet)
no problem.
im new to playing with the hd2, but been playing with android for well, just about 2 years (early G1 adopter)
it shocked me coming to this forum and seeing the same question worded diferently atleast 7 times on the first page.
lets hope mod's will sticky this..
I'm no expert but from what I've been seeing the difference setCPU makes with the new hastarin kernel's is negligible. In fact I don't think you can use setCPU with with r8 anymore...
Excellent thread! All info was scattered throughout the forums, and this is a nice thread to sum up everything!
Indeed, using hastarin's R8 you won't need to use setCPU since hastarin has included an interactive governor in his kernel
R8 is a vast improvement over the older kernels, I would reccommend it to everybody that uses Android on his/her HD2!
Slampisko,
Very nicely done and there should be more informative guides like this!
Should be made an instant sticky.
PLEASE do yourself a favor and don't use an automatic task killer. Just because an app is in memory doesn't mean it's using CPU and therefore battery but it will use it to run it again after you killed it.
If you must tweak things here use Autokiller Memory Optimizer to change the levels the out of memory optimizer kicks in at.
Of course if you have an app that refuses to close or is just chewing cpu for no reason then manually killing it is fine.
More info linked in my FAQ in my sig.
Sent from my HTC HD2
Thanks for all the feedback! I'll edit the first post to include the additional info...
Hey guys, cool guide
I tried somes tuff, and read various posts, but somehow I cant figure out why my HD2 with MDJ FroYo Sense Clean v. 2.2 [kernel: hastarin R8] keeps sucking the battery empty so far.
Only program i installed in addition to the Android version mentioned above, is the Current Widget to the how much mA it drains.
Those are my settings:
MDJ FroYo Sense Clean v. 2.2 [kernel: hastarin R8]
GSM only (2G)
Data disabled
Wifi disabled
GPS disabled
Bluetooth disabled
syncing disabled (Background data + auto sync both disabled)
I also killed all running things that i think i dont need and still Current Widget shows me, battery drains in standby 55mA-60mA
So i was wondering what i am missing??? since most of the users get a standby mA of 8 or below... I tried for several days now, but somehow i cant find a solution...
just an update from me....
after conditioning the battery, im currently @27 hours since unplugging, gps, and wifi turned on the entire time, im @ 3.873v or 61%! granted, its been light usage its my secondary phone right now, but i am on the outskirts of service, and the week signal usualy sucks the battery...
ill update again , probably this time tomorow once it finaly dies...
<edit> as you can see in post #2, after 27 hours of up time, i still have higher battery voltage than what the phone was assuming was 100% on initial flashing of the rom...... just food for thought...
That's very interesting, t1h5ta3... Trying it right now, will edit post with results
<Quote>Killing tasks automatically immediately after closing them – this apparently makes battery life worse, because when a program is in RAM, it doesn't consume system resources, but when you run it again, it does. Thanks to hastarin for the clarification.<End>
Do not necessaryly agree. A 'program' is a collection of endless conditions and calculations that puts strain on the CPU. Unless a 'freeze program' function is built in to Android to literally freeze a program when its idle in ram the, the program will still continue to consume valueble cpu power just to stay idle albeit at a reduced rate. But having many program in memory in this state can tax the system performance draining the battery.
I don't have the file batterystats.bin in data/sytem!!!
Any help?
Edit: In fact i found it with root explorer search however i am enabling view of hidden files and i don't see it!
Does deleting it While in android by root explorer will cause any problem?!
@Life Engineer: Nope, I deleted it by Droid Explorer's console while having android up and running and nothing bad happened.
Slampisko said:
@Life Engineer: Nope, I deleted it by Droid Explorer's console while having android up and running and nothing bad happened.
Click to expand...
Click to collapse
BTW i don't agree saying that conservative is the best governor; i guess many accept with me; latest tests showed that interactive is the best and it worked for me!
You may consider putting it in the thread
@Life Governor: I was thinking about that too. Will edit thread.
Question when it comes to draining the battery which side do I drain it on win or Android?
@WCENIGHTCRAWLER: Android I suppose, as Android needs to know the correct voltage for drained battery.
Slampisko said:
@WCENIGHTCRAWLER: Android I suppose, as Android needs to know the correct voltage for drained battery.
Click to expand...
Click to collapse
I'm unsure on this as well. Maybe I'm a bit behind on all the dev that's happened. But I remember if draining battery in Android, it messes up with the build on the SD card.
Might give this a go tonight and see.
Hi!
I actually found the settings to change the cpu frequency today the warning I was given when i pressed " Performance " have scared me of, but not anymore.
So I was wondering, what are the best settings in your opinion, about the settings, for the Hd2 only. For heavy use, medium ( just listening to music , from-to-work) and for preserving the battery as long as possible.
And I would also like some help with the combinations of the different types of governors with the min/max cpu settings.
I know what RJackson wrote about the different governors
http://forum.xda-developers.com/showthread.php?t=843406
Thanks!
first thing first - congrats for overcoming your fears!
for daily use I have the on demand governor with 245-998 Mhz. I find it to be the best because you can get the performance when you need it and yet the CPU can "calm down" at times you don't run the heavy apps, thing that also saves you some battery
settings
I use the same as above. on demand gov. also.
thanks for your replies =)
Any information about how long the battery last for you guys?
(my battery is 4201mV @ 100%)
I use the setting as I posted above, I unplugged my phone about 17 hours ago made a few calls and texts, gmail and viber are updating every 15 mins via wifi. still got 73% of juice left (I have the stock battery, don't know about V, mA capacity)
Disclaimer; This does not damage your phone at all or fry/mess your cpu.
This method is used to lower CPU stress and increase Battery life
This method works for all rooted phones.
IMPORTANT: The newer versions of SetCPU might prevent your phone from entering deep sleep. Download version 2.24 from the following link which is the one with no problems and completely works 100%.
LINK
Deep Sleep breaks when charger is plugged in, you can see this by CPU SPY application available on playstore
Stop Downloading Battery Saving Applications, they do nothing and uses RAM.:silly:
Also Turn BLN off when you are sleeping.(It also Consumes battery and sometimes prevent deep sleep of CPU)
Set your Brightness to minimum and disable auto brightness.
LINK to Display Brightness
Instead use lite app called - Display Brightness from play store.
Turn off wifi and mobile data when not in use.
Use toggle for auto rotation, and keep off when not needed.
For more battery Saving, disable all animations and set screen timeout to 1min.
The S plus sucks in battery life. We all know that.But here's a fix, Try Under clocking instead of Over clocking.
When screen is on:
MAX 1.4Ghz(Why to OC??, if your phone runs smoothly on 1.4Ghz)
MIN 192Mhz
Ondemand governor (This governor jumps up to max when needed but spends most time on the min freq. Best battery saver.)
When screen is off:
MAX 365 Mhz
MIN 192 MHz
(This prevents lagging when playing music and other activities when screen off)
This way, you have a beast quick phone when you're using it, and the best battery saver when you're not!
NOTE: Turn off Autosync from the settings. It's only used to sync your gmail and contacts and such. You can manually sync when you add a new contact and since I don't use gmail, I refresh manually whenever I do.
SetCPU:LINK
Specific instructions for those that can't get it to work!:
On SetCPU:
Click Add profile
Where it says Profile, select it and tap "Screen Off"
Set the frequencies you want in use while screen is off (If you want just one frecuency, put both sliders on the same number)
Set priority (in case you have other profiles, otherwise don't bother)
Select governor (Won't really matter since cpu is gonna be running at 1 frecuency)
Tap save
Go back to Profiles tab at the top, then tap Enable at the top left to make the profiles work.
For a list of most governors and I/O schedulers detailed;
Visit
1.LINK
2.LINK
To check if its all working, install CPU spy from the playstore: LINK
For Playing GAMES(HD)/HEAVY GAMES, Plug your Charger in and play if possible.:good:
Most Important thing is to calibrate battery,
Calibration of battery is needed when you change your ROM.
This process wipes batterystats.
Battery Calibration
1. Charge 100%(NON STOP)
2. Download any battery Calibration tool from play store; (Link to App)
3. Open that app, click battery calibrate
6. Unplug your charger
7. Discharge your phone down to 0% during the day
8. Charge back up to 100% (NON STOP)
This is to make sure you're using your battery at 100%. Only do this after you flash a new rom.
The worst battery killer is 3G. No matter how much you try to optimize battery by tweaking and underclock, if you have 3G on, you're gonna have a bad battery drain.
Make sure that Autosync is disabled.
Done A small test usage 14 mins , you can see in attachment your CPU should look like this.
THIS READINGS FROM MY SGA.
And never ever install the Facebook App if you want to use your phone for more than 3 hours!
Sent from my GT-I9001 using xda app-developers app
Don't get apps that take background processes like what xellar said, facebook, and some other apps like tap tap revenge 4. Anyways thanks for the tips and link to free setcpu
Other people can also share VALID ideas about saving battery.
Will help many users.
Nice advises. I'm already using these.
One more good thing is turning mobile data off whenever you are not using it, also bluetooth, lowering brightness.
Good app for doing so is Power Toggles. You can always have widget on home screen and switch on/of these things with one tap.
Riiight.. Turn off autosync, disable 3G and wi-fi, dont use apps or games.. I might as well buy Nokia 3310..my phone lasts easily whole day with wifi on..with 3G it can get me at least 6-9h which is fine.. The key is to turn off 3G when you are on wifi and turn down brightness.. Everything else is not using your smartphone smart..
1) Set your network mode to 2G only if you're not using 3G/WCDMA
2) Manually set your operator in settings.
PS: After flashing one of firmwares I got a bug - battery is not charging to 100% while phone is ON. Only to 99% and not showing a message about fully charged battery... But when the phone is in off mode - it charges to 100%. Anyone knows how to fix this thing?
apkfox said:
1) Set your network mode to 2G only if you're not using 3G/WCDMA
2) Manually set your operator in settings.
PS: After flashing one of firmwares I got a bug - battery is not charging to 100% while phone is ON. Only to 99% and not showing a message about fully charged battery... But when the phone is in off mode - it charges to 100%. Anyone knows how to fix this thing?
Click to expand...
Click to collapse
Change/upgrade your firmware...
Battery Calibration
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_Plus/GT-I9001#Calibrate_Battery
This way works without an app.
TheBlackWolf said:
Change/upgrade your firmware...
Click to expand...
Click to collapse
Didn't help. But deleting batterystats.bin helped. Thanks anyway. :good:
Take a other kernel with better voltage and governor configuration.
Set Display time to 30sec.
Kind regards.
enable "only 2G"
turn off wiifi
turn off bluetooth
black screen wallpaper help?
Sent from my GT-I9001 using Tapatalk 2
If you are on CM7 try this... From CyanogenMod setting.
This will help to save battery.
cheehsiang said:
black screen wallpaper help?
Sent from my GT-I9001 using Tapatalk 2
Click to expand...
Click to collapse
On Amoled-Displays it should help. Inverted Apps, too.
setCPU
i testet the new version of setCPU 3.0.9, deep sleep works perfectly.
If profiles are not used it exits and there is no use of RAM in both versions (But then you do not have the unique feature of auto switching profiles ).
Is there another app with auto-switching?
buffo1987 said:
On Amoled-Displays it should help. Inverted Apps, too.
setCPU
i testet the new version of setCPU 3.0.9, deep sleep works perfectly.
If profiles are not used it exits and there is no use of RAM in both versions (But then you do not have the unique feature of auto switching profiles ).
Is there another app with auto-switching?
Click to expand...
Click to collapse
Actually no idea.
But other simple and best app for controlling CPU is NoFrills.
TheBlackWolf said:
Actually no idea.
But other simple and best app for controlling CPU is NoFrills.
Click to expand...
Click to collapse
But it has no profile-autoswitching, in fact no profiles at all. Voltage control Extreme has at least profiles, but without autoswitching. What is good about Voltage Control Lite/Extreme is that it sets cpu setting with init.d and so the app does not have to start on boot
Yes that is nice...
fo more info how to use
visit here
Link to App
TheBlackWolf said:
[
Stop Downloading Battery Saving Applications, they do nothing and uses RAM.:silly:
<snip>
When screen is on:
MAX 1.4Ghz(Why to OC??, if your phone runs smoothly on 1.4Ghz)
MIN 192Mhz
Ondemand governor (This governor jumps up to max when needed but spends most time on the min freq. Best battery saver.)
When screen is off:
MAX 365 Mhz
MIN 192 MHz
(This prevents lagging when playing music and other activities when screen off)
This way, you have a beast quick phone when you're using it, and the best battery saver when you're not!
<snip>
Click to expand...
Click to collapse
Many thanks for the battery saving hints. I'll finally kick out the Task Killer App, doesn't really seem to do anything except creating problems ..
For the statement that Underclocking would help in saving battery I wouldn't fully agree. A slow cpu needs more time to complete a task before returning to a sleep state. Of course the battery drain is higher with a higher frequency (which also require higher voltages), but I believe, that there isn't much to gain on this front. As long as I don't see any profound evidence I'd even suspect, that an underlocked CPU overall could even cause more power consumption. You can also read more opinions about this in general in this thread.
Much more beneficial would be to identify those apps that cause frequent wakelocks. Does anybody have hints here, how to track down those 'bastards' ? (From my Linux I know 'powertop', does something similar exist for Android? (Or are the battery statistics in CM10 sufficient to decide which app to wipe?)
z3non said:
Many thanks for the battery saving hints. I'll finally kick out the Task Killer App, doesn't really seem to do anything except creating problems ..
For the statement that Underclocking would help in saving battery I wouldn't fully agree. A slow cpu needs more time to complete a task before returning to a sleep state. Of course the battery drain is higher with a higher frequency (which also require higher voltages), but I believe, that there isn't much to gain on this front. As long as I don't see any profound evidence I'd even suspect, that an underlocked CPU overall could even cause more power consumption. You can also read more opinions about this in general in this thread.
Much more beneficial would be to identify those apps that cause frequent wakelocks. Does anybody have hints here, how to track down those 'bastards' ? (From my Linux I know 'powertop', does something similar exist for Android? (Or are the battery statistics in CM10 sufficient to decide which app to wipe?)
Click to expand...
Click to collapse
Better battery stats is application useful for identifying partial wakelocks.
Its an paid app, but Google helps... Lol
Your above sentence about UC comes true for heavy usage.
Normal apps can run smoothly and at same speed as of OC.
I am using auroraspv3ce final.
With most of time in sleep with wifi, it goes 8-9 hours.
If i use for example twitter facebook, it goes maximum 4-5 hours.
And mostly applications stop or lag so ihave to stop activity. I am using automemory ptimizer in aggressive mode (100 mb free) but still i have this problem.
For example when someonecalls me, 2-3 seconds waiting, i can see the person name. It shows number first.
What applications do you suggetst or what should i do?
I want to do tests memroy and battery tests to see if something is wrong. How?
I have battery problem too is normal not that much. Did you try to reduce clock speed governor? Interactive is good. Try and report.
dark_vader said:
I have battery problem too is normal not that much. Did you try to reduce clock speed governor? Interactive is good. Try and report.
Click to expand...
Click to collapse
I dont know how to reduce and what governor is. Can you please tell me about it?
wHEN i open battery in settings, screen is about %25 at least. But my display is always lowets. %15 cell standby, %15 android %15 phone idle and twitter facebook each %4
Cursed Chico said:
I dont know how to reduce and what governor is. Can you please tell me about it?
wHEN i open battery in settings, screen is about %25 at least. But my display is always lowets. %15 cell standby, %15 android %15 phone idle and twitter facebook each %4
Click to expand...
Click to collapse
Yes of course. Go to menu and run application No-frills CPU control. For example select 806 Mhz for Max.clock and 245 Mhz for Min. clock. Governor you can choose Interactive.
dark_vader said:
Yes of course. Go to menu and run application No-frills CPU control. For example select 806 Mhz for Max.clock and 245 Mhz for Min. clock. Governor you can choose Interactive.
Click to expand...
Click to collapse
I did, it success but what is that for? To reduce battery? It seems now fast, opening apps, closing.
Yes it's for reduce battery. Namely if you don't play games (like me) that clock is perfect for that purpose. Interactive governor is good too mainly if you don't always need screen on aka idle.
You can test others clock for min and max but that governor is excellent.
so eeez
best way to improve battery live is propper calibration
https://play.google.com/store/apps/details?id=com.nema.batterycalibration
it needs root.
best way to calibrate battery is fully charge then unplug restart device plug in charge till 100% and do it again over and over for 3 times then... calibrate battery
fully discharge and charge again till 100 w/o breaks
also update your soft to soon coming v6 of auroraSP
hope i helpd
Battery Drain Wifi
I have done calibrations and changed clock speeds to no avail, Wifi really chews battery on most ROMs. e.g. Fully charged at 8pm and completely dead when i wake up the next morning.
Might simply be a case of new battery, does poor battery affect phone performance?
jo3fis said:
I have done calibrations and changed clock speeds to no avail, Wifi really chews battery on most ROMs. e.g. Fully charged at 8pm and completely dead when i wake up the next morning.
Might simply be a case of new battery, does poor battery affect phone performance?
Click to expand...
Click to collapse
Yes your battery is dead or almost it's not normal take out so fast
.
You can buy this battery http://www.bigupbattery.com/T-Mobile-HB4F1-Pulse-Battery-p/bupb1694.htm is good but don't except to be perfect. I have that and phone can be 1,5 2 days without charging.
Look at this topic http://forum.xda-developers.com/showthread.php?t=2029032&page=2
dark_vader said:
Yes your battery is dead or almost it's not normal take out so fast
.
You can buy this battery http://www.bigupbattery.com/T-Mobile-HB4F1-Pulse-Battery-p/bupb1694.htm is good but don't except to be perfect. I have that and phone can be 1,5 2 days without charging.
Look at this topic http://forum.xda-developers.com/showthread.php?t=2029032&page=2
Click to expand...
Click to collapse
Thanks mate, I bought this one shortly before reading your post http://www.trademe.co.nz/Browse/Listing.aspx?id=638683016 only $6NZD
Looking forward to having decent battery life again!
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