Related
After I did he market place lag fix I found my battery drained a little more than usual. I downloaded a program called memory task cleaner. This will also allow you to set auto kill on apps you dont want always running n the back ground. simply add as many programs as you dont use or want in the back ground running to the auto kill list. Set the safety level to medium in options in auto kill screen. also set intervals of auto kill to every 2 minutes. auto kill when screen off as well.
There you go. You should notice the phone is back to normal with the battery life as well as if your like me, no need for tee nav or blutooth and things like that you will notice the battery may even last longer.
Let me know your results. Settings so fourth.
By the way there will be plenty to auto kil. the galaxy s runs alot of programs all the time for no reason.
so far so good
I had my phone fully charged and tried this so far so good! Ill report more when I can test more. But it has definitely lasted longer so far. about an hour off the charger using wifi online and all, still full batt!
Lets hope this fixes it or Ill have to go back to stock.
So instead you have a program running that every two minutes kills running programs that will start again anyways, beginning the cycle all over again?
Edit: and the way android works, "running" is poor word choice
What its the difference between this and ATK? I'm pretty sure this will so more harm than good.
Sent from my SGH-T959 using XDA App
Oh, nice OP. Now you have programs constantly fighting themselves to run/kill each other. So now instead of the Android OS taking care of itself, you have these programs sucking down CPU cycles and battery juice.
Dump the autokiller and use ATK to manually kill things if you don't want them running. I get about 35hr of standby time.
Edit: If you really want to be smarter than the Android OS, uninstall the app/widget that's sucking down your battery.
I have seen over and over people state how they use ATK or other task killers to improve battery life, when in fact they are actually hurting android 2.2 multi tasking. In 2.2 google changed the api that devs used to kill apps in all other versions of android. I myself use Auto Killer and Auto starts. Those two apps tweak androids internal task manager and keep my phone running smooth
Even the creator of ATK and the other most popular task manager Advance task killer have stated it. Your better of using an app like Auto Killer ( http://www.appbrain.com/app/com.rs.autokiller ). It tweaks android internal task manager.
AutoKiller is an award winner minfree tweaker, it fine tunes android's inner memory manager to keep your device fast and lowers battery consumption. Also includes a manual process/service manager.
Click to expand...
Click to collapse
Here are a couple articles about why you dont need them in android 2.2
FAQ: Why You Shouldn’t Be Using a Task Killer with Android
http://geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/
Froyo update kills Android task killer apps
http://androinica.com/2010/08/09/froyo-update-kills-android-task-killer-apps/
Task killers have long been a crutch for users to forcefully shut down applications and “free up memory” to conserve battery life and space. However, that’s a common misconception buoyed by old Android flaws and the power of the placebo effect. Task killers actually get in the way of Android handling memory management as intended. We’ve already written an article on why you should not be using a task killer, so read that post for more information.
Click to expand...
Click to collapse
Google and Cyanogen comments imply task killer/manager apps are pointless
http://androinica.com/2010/05/07/go...-imply-task-killermanager-apps-are-pointless/
However, developers of task killing apps are of a different opinion. Arron La, developer of Advance Task Manager, suggests that task killers are more important for legacy devices like the G1 and phones running older versions of Android.
“Task Managers were absolutely needed in the past before the new services UI came out in Android 2.0 or 2.1,” La said in an e-mail. “Task Managers had a niche of allowing users to quickly kill services associated with apps – including all the other stuff as well, such as alarms – but that was the only way to do it before the introduction of the new services UI.”
Click to expand...
Click to collapse
I am gunna try out the difference. I do follow cyanogen and I saw that exact tweet lol. at the time though i was on windows. we will see what happens.
This needs to be moved to the head of the class as it is great info and everyone should read.
There is a lot of people running around saying task killers need to be used.
THis isnt winmo.
The idea that leaving all your applications open not hurting performance or battery flies against what most of us expect to be true. Lately ATK hasn't worked. I'll kill all apps, then minutes later they will all reappear. I will try going without a task killer for a while and monitor subsequent battery life.
What about all the OCD people? I would imagine it being hard for people with OCD to not compulsively close tasks.
I would add the use of auto killer as the op has stated. It works in conjunction with the way android kills task. You can set it aggressively or not. I cannot quote on battery life as I tend to damage mine. Only a rogue app would cause major drain. I also use a program called data on demand. That works by turning off data when the phone is off and lock.
this is indeed an interesting light for us all!
testing begins.
Deleted...
polo735 said:
The idea that leaving all your applications open not hurting performance or battery flies against what most of us expect to be true. Lately ATK hasn't worked. I'll kill all apps, then minutes later they will all reappear. I will try going without a task killer for a while and monitor subsequent battery life.
What about all the OCD people? I would imagine it being hard for people with OCD to not compulsively close tasks.
Click to expand...
Click to collapse
As an actual sufferer of OCD who is trying out the no task killer method, I will say that it IS making me itch a little bit :/
....need to stop killing tasks. Its hard. I'm so used to it now. Will report my findings!
Sent from my HTC HD2 using XDA App
Glad to see everyone is finding this info helpful. The word really needs to be spread.
Also you can add an app called watchdog that monitors your memory and lets you know when it gets below a certain threshold. it will then notify you and let you know wich app caused the memory drain.
You can do it. Consider this the support group for those who don't use task killers.
Thank u mvp77 for bringing this to light. For me my hd2 runs so smooth!!!
Well, with no task killer, after about 90 minutes of sitting on my desk at work, sending about 20 texts & listenening to 2 songs, my battery went from 70% to 35%. I was shocked at the accelerated battery drain, and I noticed that the back of my phone started getting hot too, which it NEVER did before I disabled the ATK. I re-enabled it around 5:30 on the way home, and after heavier texting, data, and music usage, it's only gone down to 22% after 4 hours.
I'm gonna conclude that my task killer serves a very good purpose, at least with my specific setup. Methinks I'll keep it enabled!
wow thats really strange because that actually goes against the way android actually works. as it stands the task killer is needlessly killing so called process's that may not even be active.
This is based on what the google android developers say. To each their own I will continue you to run without it as a see a speed increase without it. I would venture to say that there is a program that is causing problems.
kabuk1 said:
Well, with no task killer, after about 90 minutes of sitting on my desk at work, sending about 20 texts & listenening to 2 songs, my battery went from 70% to 35%. I was shocked at the accelerated battery drain, and I noticed that the back of my phone started getting hot too, which it NEVER did before I disabled the ATK. I re-enabled it around 5:30 on the way home, and after heavier texting, data, and music usage, it's only gone down to 22% after 4 hours.
I'm gonna conclude that my task killer serves a very good purpose, at least with my specific setup. Methinks I'll keep it enabled!
Click to expand...
Click to collapse
I have never experienced battery drain like that. It would seem you have a bad app causing it. I would suggest you install watchdog and set the threshold at 30% and see what app is causing the problem.
The Creator of ATK stated on his blog, witch I can't find now, that his app does not work the same with 2.2 because the API used is no longer there.
Also install autokiller and autostarts to tweak android internal task manager and to stop unnecessary apps from starting.
I think it is the placebo effect cyangon and others mentioned.
I actually think my screen is killing my battery. I have to much current draw as noted using current widget.
I'll try Watchdog, and I've already got autokiller & autostarts installed.
I'm thinking about hard resetting. I've noticed that lately my battery hasn't even been charging completely, it only goes to 95% unless I charge it in WM or when it's turned off.
hazard99 said:
I actually think my screen is killing my battery. I have to much current draw as noted using current widget.
Click to expand...
Click to collapse
I believe I have the same issue running ShubCraft 1.5. 95% of the power consumption goes to display, while everything else is at 5%. This is after 1 hour of usage.
In comparison. If I use MattC SenseUI build. 45% goes to battery while everything else goes to Phone Standy or Idle.
Though I can get about 20 hours on Shubcraft instead of like 8 hours for MattC. SenseUI must be very taxing on battery.
Well Like i stated at the beginning I ruin batterys by constantly tethering or atleast I think it does.
Watching the current widget the ma's can be upwards of 150ma which isnt right at all. When I look at watchdog I am under 95% idle which means apps are behaving correctly.
looking at the battery information it shows that the display is using the most of my battery.
Watch dog states that the android system is using 1.3% of cpu.
If i select real time watchdog jump to 6.8 percent which is understandable since it isnt being passive.
Right now I think the screen management is the problem. I cant do this any scientific way but based on what I see it seems to be the only reasonable thought.
+1 for screen being the cause every thing i use to test shows as screen being the issue of battery drain next to some live wallpapers
100% AGREE!!!
I have tried Taskiller and ATK and both did what they were made to do but my battery simply was eaten 12% every hour... So, I uninstalled EVERYTHING related to "battery preservation" and installed AUTOKILLER - this gave me 60% improvement over my old setup and battery life... I now easily pull more than 24hrs in stand-by - about 15hrs with average usage!
FYI: When installing certain apps (as AutoKiller) allow three four charging cycles - use phone as usual and re-charge 3-4 times... You will see that battery self-operates into the best working option and it starts working great...
With setCpu and ATK installed (with kill set during screen off and setcpu on ignore list) I had 12% drain / hr on stand-by ...
Both have been uninstalled now and only Autokiller is installed (Akiller shrinks memory threshold so Apps are shut-down natural "organic" way by Android OS) and I get less than 5%/hr drain on batery...
How is that possible? Simple - Linux is not like WinMo or WinOS - running process does not necessarily means it will drain battery.
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.
CASE CLOSED!!! Please read bottom part or flash stock GB 2.3.4!
I have posted this already on another thread (almost word for word) but I just really want you guys know and not panic about this problem and avoid going through difficult fixes like deleting system apps, recalibrating battery or even resetting your phone.
Since JVK was released, many observed that Android OS sometimes get hungry and devours battery. For some reason it is triggered to go berserk. Others say that the main culprit is the Auto update app. But other apps like Google Maps, Latitude and even just in a place where there is very low network signal or Wifi reception could also trigger this problem.
Now, I have a very simple solution: Turn off device, remove battery for a minute, put it back then turn it ON. Yes it is just that simple, REBOOT YOUR DEVICE.
Yeah after you turn on your device Android OS is still on the top of the list with high percentage but I believe it is just as it is because it previously consumed a lot of battery. All you have to do is observe again for an hour if your battery is dropping again, look into the graph and see if it is still steeping to the bottom. If it is dropping like Mt Everest, do the procedure above again.
If not, you will observe that after a couple of hours Android OS's percentage is getting low. Problem is fixed, (temporarily though).
Why go through deleting apps, recalibrate battery etc when you could just turn off your device for a minute?
I have experienced it a lot of times already (one of the first users who upgraded to JVK) but it doesn't bother me anymore. Turning off then on your device is very simple ain't it?
I highly advise that you do not touch anything on the sensitive part of your phone as there is no known single root of this problem. Just like I told you, many situations or apps could trigger Android OS to go berserk. Until there is no definite solution to this problem, I suggest you do the above procedure and save yourself from going through the pain of removing system apps, battery calibration or even hard reset.
By the way my battery usually lasts 3-4 days unless I made Android OS angry again.
INVESTIGATION
INVESTIGATION CLOSED!!! The culprit is caught. But the fix is not so simple. Only Samsung and genius devs (apparently the fix requires closed source modification) could fix this. If the problem occurs on your device, just do the temporary fix above. Please do not try to mess with your device for now.It is now fixed in XXJVP 2.3.4!
Click HERE and read the bottom part for more details.
All this is due to Tatsuya who pointed us to the right direction. A big thanks to him for helping us in this investigation. CASE CLOSED
Tatsuya79 said:
Ok thanks for the credits.
This previous link I gave explains how you can use watchdog to alert you when this bug triggers, so you know when to reboot your phone to stop this leakage (if you really want to stay on gingerbread until a fix is made by Samsung).
Click to expand...
Click to collapse
Guys if you want to help out please please please dial this *#*#4636#*#* and check "Usage Statistics" and let us know the top 3 items on the list! (highly suggested by {Angel}).
Below are some of the possible culprits currently pointed out by some users (I will update the list based from your feedback):
1. Software Update service
2. Google Maps
3. Latitude
4. Low network signal
5. Very low WIFI reception
6. Auto updates in Market
If this helps, a simple thanks is enough
This is a post coming from Angel:
{Angel} said:
Those of you with high drain, you can also check battery history through *#*#4636#*#* and see what you have under other usage 'running' and see if your phone as not been sleeping lately. I get this occasionaly with froyo and I suspect many people do also. A reboot fixes it for me, after that my battery usage is superb, but it's annoying as hell.
Click to expand...
Click to collapse
And this is my post somewhere:
jbdroid said:
Yes just like I said in the first post, this is just a temporary fix. But I think users should just do this rather than touch anything on their phone unless they really know the source of the problem.
That is why I suggested that they report what could be the possible triggers, like apps or situations, that make Android OS to awake and gobble up the battery. If we could just pinpoint those triggers maybe we can now figure out the root of the problem. Your fix of removing a system app, the auto update app, is not even the single source of the problem. We just do not know if that app is an essential app or not. Sooner or later you will have that problem again.
I am not saying we should just sit and wait. All I am saying is if you are a plain user and you do not know the exact root of the problem, then just do what I suggested. But if you are a dev and is exploring the root of the problem, then do as you like and we will be most thankful if you find out the answer.
People are mislead about what works and what is not. I just want to help.
Click to expand...
Click to collapse
Rebooting works, and it seems to be working until you start some apps again. I have the same apps installed as I had on JPY, but JVB drains my battery dead in half a day.
luci.pacurar said:
Rebooting works, and it seems to be working until you start some apps again. I have the same apps installed as I had on JPY, but JVB drains my battery dead in half a day.
Click to expand...
Click to collapse
Could you pinpoint some apps? I will update the OP to keep track of possible culprits so that others will avoid triggering this problem. Thanks!
I once saw that the battery drain from 95% to 9% after one night, and the android os used most of it. I rebooted my phone, and the problem has gone away, since. Happy with Gingerbread!
I'll give it a go! thnx
Active Widgets: WeatherBug Elite, 3G Watchdog, BatStat and Calendar.
Apps: All from above plus Twitter, Titanium Backup, Facebook, Twitter, Tapatalk, Camera360 Ultimate, Root Explorer, Foursquare.
Mostly I use the Twitter client and the browser. Location services are disabled.
It is hard to figure out from the above apps or which is the most probable suspect. Just incase the problem recurs on your phone, dial this: *#*#4636#*#*, Go to Usage statistics and Battery Information and please report back (include also information on the Battery Use in Settings).
I hope we can help others avoid having this problem until there is a fixed solution.
Thanks!
Did what you suggested and pulled the battery at 30% waited 5 minutes and put it back in.... 1hr later it was at 35% (WTF!) and 30min later it was at 38% (WTF!)
im assuming its recalibrating?
Not necessarily. Maybe the battery meter is anticipating the fast consumption rate of Android OS that is why when it got fixed, the meter is able to readjust the readings based from the current consumption rate of your phone. Good to know it helped
Maybe use the 'forbidden' task killer? Works for me... Maybe im imagening it but works.
Btw my battery goes quickly down after getting below 25%. My battery not calibrated? Should i.calibrate it? I have this program to do it but am afraid that calibration goes wrong. (example what if my battery is 95% and will calibrate to 100. What if.i charge my battery higher than this.. Will it show 104%? Or will android stop working for it cannot be displayed in the notificationbar.
Using cm7.
Sent from my HTC Desire using XDA App
You do not have to recalibrate. Cm7 has a known issue about battery. I think you cannot charge past 94 or 95 percent and battery usage is a bit terrible. Please refer to cm7 thread for possible fixes, (the last time I checked their thread, they say it is probably kernel related).
Just turning off, pulling the battery and turning on does do a lot for me! i went from 10% per hour to only 1%! great thnx!
Hi,
About battery drain in gb, once fixed the wifi sleep policy issue ( by setting it to "never") u shouldn't have batt drain, but i've installed green power ( juice defender do the work too i think) to get some wifi management possibility back and it improuved my batt life.
But never the less, my battery won't last more than one day of hard usage ( being hanged on xda all day long, for instance ;-)
Sent from my GT-I9000 using XDA App
Guys, just turn off the task killer, it helped in my case. looks like its not working well on ginger
Rebooting works just temporarily.
It will come back the next day or so.
This is not a solution at all tbh.
Yes just like I said in the first post, this is just a temporary fix. But I think users should just do this rather than touch anything on their phone unless they really know the source of the problem.
That is why I suggested that they report what could be the possible triggers, like apps or situations, that make Android OS to awake and gobble up the battery. If we could just pinpoint those triggers maybe we can now figure out the root of the problem. Your fix of removing a system app, the auto update app, is not even the single source of the problem. We just do not know if that app is an essential app or not. Sooner or later you will have that problem again.
I am not saying we should just sit and wait. All I am saying is if you are a plain user and you do not know the exact root of the problem, then just do what I suggested. But if you are a dev and is exploring the root of the problem, then do as you like and we will be most thankful if you find out the answer.
People are mislead about what works and what is not. I just want to help
Guys, on Gingerbread I've had battery drain two times:
1. Had about 14% drain in 3 hours all of a sudden, without doing anything at all. Just started going down for some reason.
2. This morning, saw about 40% drain in 7 hours..
And, both time I solved it by Clearing Memory from the Task Manager.. Went back to normal 2-3% drain per 6-7 hours after that..
So this might also be a solution. Go to Task Manager, RAM tab, and Clear Memory..
i'm on ginger also and my battery acts weird. 2 days ago i charged my phone over night while it was closed. the battery holds for 15 hours with massive use.
last night i did it again, but today it went from 98% to 80% in about an hour !
this is really weird.
addicted2088 said:
Guys, on Gingerbread I've had battery drain two times:
1. Had about 14% drain in 3 hours all of a sudden, without doing anything at all. Just started going down for some reason.
2. This morning, saw about 40% drain in 7 hours..
And, both time I solved it by Clearing Memory from the Task Manager.. Went back to normal 2-3% drain per 6-7 hours after that..
So this might also be a solution. Go to Task Manager, RAM tab, and Clear Memory..
Click to expand...
Click to collapse
Did you manage to check first what is running on your device by looking into Battery Usage settings? I think you have a case of rogue application running in the background.
If you have not rebooted yet could you please attach a screenshot of the battery usage list and graph? In that way we might possibly identify the app running prior to the clearing of memory. Thanks!
I thought this was important enough to move out of the Volume Control--USB Audio thread as it contains some information which runs counter to prevailing beliefs and suggests a way to test these beliefs.
This report is the result of my struggles to figure out the power drain issue with Phone.apk since I discovered that enabling it restores the volume "button" control over Media volume. Be prepared to be surprised. I was.
If you search online for issues with the generic "phone.apk" and battery consumption you will see the same drum beat over and over. Nearly everyone is convinced that the app is eating up their battery (even when they don't actually have a phone). They cite the battery usage stats which show the "cell standby" process (whatever that is) eating up huge percentages of the battery life. They also (mostly) cite a marked increase in battery life (and a disappearance of the "cell standby") when the app is deleted or disabled. Some also claim that simply changing to "airplane mode" kills the "cell standby" process.
It's difficult to argue with someone's personal experience, but there are a few voices amidst the clamor which say something more or less like this:
The problem is that the statusbar in the systemUI process actually reports the status of cellular radio to the battery stats service. It apparently does know that there isn't a *connected* radio, and then incorrectly assumes there is an *unconnected* radio which would be consuming battery searching for a signal (if it existed!). So it is just reporting time to the service, and it is sending that number through some formula that computes battery usage and displays it.
I assure you (as someone who is a programmer, but more relevantly has common sense) that a nonexistent cellular radio is NOT consuming your tablet's battery. It is simply a stat reporting error.
Click to expand...
Click to collapse
But, you know, it is a well-established fact that disabling Phone.apk improves battery life. I don't claim to know very much about the Android operating system but as I've delved into this issue one thing has occurred to me that seems completely illogical. I don't understand all of what happens when a device is rooted, but I doubt that a whole bunch of system apps that were somehow disabled before rooting are suddenly enabled during rooting. So before the NST is rooted, surely the underlying Android 2.1 system is chugging along and none of the apps present is actually disabled. Why then, does Phone.apk suddenly become a current hog only when the device is rooted?
So my quest took me down the rabbit hole in an attempt to disable all functions of Phone.apk except the desired ability to control the media volume. This led me to track down obscure settings menus (for the curious geek: AnyCut in the PlayStore--be careful, some settings will cause a reboot), alter the settings.db file (the only place that seems to have any say about "airplane mode"). Would you have imagined that Phone.apk has data roaming set as default "on"? Ever wonder why Phone.apk never appears when enabled? Turns out it has a dependency on Contacts.apk which is absent from the NST. Anyway it was all for naught. By the time I was finished my NST was leaking power like a sieve even without Phone.apk re-enabled.
Fortunately I had an old backup from December and didn't have to restore too much. Back to square one and more reading. It eventually occurred to me that the Nook Color had been the source of some of the audio work, so I visited that forum. Didn't find anything. Of course the Nook Color has native audio capabilities. But I did find a long thread in which proponents and opponents "discussed" Phone.apk and its possible effect on battery drain. That and member @HotShotAzn (his research is here) led me to SystemPanel. The paid version allows you to monitor the system for as long as a week at a time and follow things like CPU usage, power consumption, what's running, etc. If you're interested in SystemPanel for yourself, there's an extensive overview of it here.
Lies, D*mned Lies, and Statistics
Before I lay out the data from my experiments, let me just disclaim the whole thing right now so that anyone with a different experience can still feel validated. I don't claim this study is definitive. To do it right, I should have restored my NST to stock, rooted and then compared power consumption with and without Phone.apk. I judged that as too tiresome although the backup capability of NookManager really would have made it rather easy.
My system: I am running rooted stock 1.21 with the most recently amended kernal that includes gussied up audio but I note here that the audio implementation in that kernal is not quite complete, being a few details shy of enabling full mic capabilities. I filled those in myself. I use NoFrills CPU governor to regulate the CPU between 300 MHz and 1 GHz, on demand. I run Tasker in the background for a number of things, principally to autostart/stop WiFi for those apps that need it, and to control/lock rotation on some apps. There's a lot of little stuff that fritters away a little CPU time in the background, like the BBC News, TuneIn Radio, etc. I also have all the B&N stuff going except for NookCommunity and Social, both of which I consider nagware.
Day 1-2: No Phone.apk
I fully charged my NST before retiring and let it do its thing overnight. It was down to 99% the next morning. I read lightly during that day and the next, but did nothing else with the device. You can see the power drop-off in section 1 of the first image below. Pretty good.
These are the basic stats from those two days:
Remaining charge: 92%
Active:
ADW
Home
Library
Reader
SystemPanel
Service-only processes
CloudService
com.bn.nook.affileddownloadservice
DeviceManagerService
Market
News and Weather
Settings
Tasker
TestCenterService
USB Audio
USB Host
WaveformDownloaderService
Inactive (cached) apps
AdAway
Email
Maps
Pandora
Shop
thumbnailservice
TuneInRadio
Internal System Processes
Android keyboard
android.process.acore
android.process.media
com.bn.cloud.svc:svc
com.google.process.gapps
system
Top apps
System Processes
system
SystemPanel
Days 3-4: Volume control "kludge"
I fully charged the NST before retiring and also briefly ran the USB Audio toggle app so I could use ES Task Manager to wake up the volume control as described here. Then I left the NST to sleep.
The next two days I read lightly as before, nothing more. I was shocked at the power drop-off as seen in section 2 of the first image below.
These are the basic stats from those two days:
Remaining charge: 50%
Active:
ADW
Home
Library
Reader
SystemPanel
Service-only processes
CloudService
com.bn.nook.affileddownloadservice
DeviceManagerService
Market
News and Weather
Settings
Tasker
TestCenterService
USB Host
WaveformDownloaderService
Inactive (cached) apps
AdAway
Email
Maps
Pandora
Screenshot Easy
Internal System Processes
Android keyboard
android.process.media
com.bn.cloud.svc:svc
com.google.process.gapps
system
Top apps
system
TestCenterService
SystemPanel
You can see from the plot that the discharge rate and CPU usage are both elevated for that two-day period. The Top Apps have also changed. "system" has moved up and TestCenterService has made the top three (the list is much longer). I more deeply investigated both of these and, sure enough, the increased CPU activity comes mainly from "system" (which I believe is the underlying Linux, as opposed to "System") and to a smaller extent, TestCenterService (com.bn.serviceone). What exactly is going on when the volume control kludge has been executed is anyone's guess, but it's clear that the result and any side effects continue to propagate through the CPU until a reboot, even when USB Audio is not in use.
I couldn't believe this result so after wrapping up all my tests today I disabled Phone.apk again, rebooted and set up the volume control kludge using ES Task Manager. Immediately the undercurrent of increased CPU usage showed up in the real-time stats from SystemPanel. So whatever volume control strategy you choose, it probably should not be this one.
Days 5-6: Phone.apk enabled
After enabling Phone.apk I rebooted (cancels effect of kludge), fully charged, and left the NST to sleep overnight. The next morning, I was down to 98% battery. So far so good.
I read for the next two days, as before, although perhaps a little more heavily since I got into a good mystery You can see the power drop-off in section 3 of the first image below. It's very similar to the first two days without Phone.apk enabled, and certainly MUCH better than that of days 3 & 4.
These are the basic stats from those two days:
Remaining charge: 91%
Active:
ADW
Home
Library
Reader
SystemPanel
Service-only processes
com.bn.nook.affileddownloadservice
DeviceManagerService
Market
News and Weather
Set Cover
Settings
Tasker
TestCenterService
USB Audio
USB Host
WaveformDownloaderService
Inactive (cached) apps
AdAway
Email
ES Task Manager
Google Partner Setup
Maps
No Frills CPU Control
Pandora
TuneIn Radio
WiFi File Transfer
Internal System Processes
Android keyboard
android.process.acore
android.process.media
com.bn.cloud.svc:svc
com.google.process.gapps
Dialer
system
Top apps
system
System Processes
SystemPanel
There's some jockeying for place among the various apps and services, but the bottom line (or rather the top one in this case) is that the remaining charge after two days is essentially the same as without Phone.apk running.
Of course there is no mention of the mysterious "cell standby" in all of these stats. You'll notice that the Dialer shows up low on the list of Internal System Processes. For the curious I called up the details on that. They are in the second image below. Clearly, enabling Phone.apk has nothing to do with battery life on my NST. But it does give me full volume control without any silly kludge that can't be explained and actually consumes even more juice. And now that I'm done with my experiments I don't need the SystemPanel monitor on so that will save a little more juice
YMMV.
I've found that the free GSam Battery monitor is very useful for tracking down apps that drain the nook. http://bit.ly/1Xclacj . I found two apps that I had installed that were trying to call home and draining my battery.