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.
[Q] "Android OS" vs. "Android System". WTH is "Android OS"?
This is a rather widely reported problem, although I can't seem to find a definitive answer to it.
From time to time (pretty often) the phone starts consuming the battery rather rapidly, even though it is sitting in sleep mode with the screen turned off. The quick check of the battery consumers reveals that most of it is consumed by something called "Android OS". What is that "Android OS" and why is it consuming so much battery power?
Note, that in normal mode the biggest consumer is usually the "Display". The list of consumers normally also include "Android System" (note: "Android System", not "Android OS") and its battery consumption is usually rather low. Most of the time "Android OS" is not even in the list. Or sometimes it is with some very low consumption value.
When the problem begins, that "Android OS" begins to consume the battery in large amounts and quickly rises to the top of the consumer list.
For example, what I currently see on my phone is
- Android OS - 44%
- Display - 30%
- Stand By - 10%
...
- Android System - some low value
...
Now I do a soft reboot (power + touchpad + vol down). And now, immediately after reboot my battery consumption screen shows
- Display - 70%
- Android System - 13%
- Android OS - 6%
- Stand By - 3%
...
This doesn't seem to make any sense. A reboot shall not, of course, redistribute the percentages in such drastic fashion. It appears that the consumption initially attributed to "Android OS" is now taken away from it and given over to "Display" or something like that.
So, again what it that "Android OS", how is it different from "Android System"? And why does that "Android OS" act that way with regard to battery consumption?
OS = "operating system"
SEARCH the forum for "init" and "suspend" and "Watchdog" for answers to battery consumption by OS processes.
Use http://acronymfinder.com for help with acronyms.
HTC Glacier running CM7 #15
jggimi said:
OS = "operating system"
SEARCH the forum for "init" and "suspend" and "Watchdog" for answers to battery consumption by OS processes.
Use http://acronymfinder.com for help with acronyms.
Click to expand...
Click to collapse
Beautiful. If I call an Android application "HIV", knowing that HIV stands for "Human immunodeficiency virus" would not help me much, would it? So, it is not about acronyms. Meanwhile, operating system that runs on the phone reports itself as "Android System", as is explicitly stated in my original message. Not "Android OS", but "Android System".
I got a rather meaningful suggestion on another forum that "Android OS" is actually the low-level kernel, while "Android System" is actually the higher-level OS service layer, although it doesn't help much in answering the question of why "Android OS" starts eating up the battery sometime (acronym finders don't help much either).
Your consumption is likely caused by either the suspend process bug, or the init bug. You can discover which by installing Watchdog and enabling monitoring and display of phone processes in Watchdog's settings. You could then search for solutions and circumventions appropriate to your specific problem.
Both problems have been discussed in many threads here.
HTC Glacier running CM7 #15
jggimi said:
Your consumption is likely caused by either the suspend process bug, or the init bug. You can discover which by installing Watchdog and enabling monitoring and display of phone processes in Watchdog's settings.
Click to expand...
Click to collapse
Thanks for the suggestion. I have immediately installed Watchdog on my phone and was running it continuously ever since. It does catch some apps sometimes, but that does not seem to be related to the issue I describe.
In fact, when "Android OS" enters that runaway battery consumption mode, thus rapidly draining the battery, Watchdog catches absolutely nothing. Is there something I should tweak in Watchdog settings in order to make it catch it?
Bump
Sent From My Rooted HTC Glacier- It Just Makes SENSE
My android System is 32% and my android os is 2%. what would have my android system so high? Was never like this before.
Sent from my HTC Glacier using Tapatalk
Uninstall the updates for the "My Account" app and then never open or update it again.
bet it solves your problem!
A lot of people seem to be having this problem of "Android OS" eating up all of their battery by keeping the CPU constantly processing.
There are a number of bugs which have been associated with this behaviour, in the case of my phone it was the ubiquitous "init" bug: the underlying Linux kernel/system is trying to start a process or activity, which subsequently fails and falls into an infinite loops, hence burning up the CPU/battery.
Install "WatchDog" from the marketplace and you'll soon find out if it's this or something else which is the problem.
The fix for the init bug which worked for me (and for others I've encountered online) was to enable the "USB debugging mode" in Settings->Applications->Development.
Presumably this sets debug parameters which cause this process not to fail/loop.
Hope this helps.
D.
wouldn't it be hilarious to find out that watchdog was behind the bug just to get everyone to download their app.. just saying...
This is for the WiFi only A500.
Just noticed that if you install the power control widget (the free one) from the market, and configure one of the buttons as a 2G/3G switch, on pressing it you get to a menu that's not available through Settings (is missing from the WiFi and connections menu). There you have the option to unselect the Data enabled checkbox. I'm not sure yet, but I seem to be getting better battery life (although Cell standby will still show up in Battery use; still, that value is a percent of the total drainage, which seems to be smaller).
Please try it out and let the others know of your results.
Noted Before - Did Not Seem To Resolve Much
Actually many widgets have the property of opening up "hidden" settings, e.g.,
docfreed said:
Wow! I just went into my Beautiful Weather settings and under the "Advanced Panel" you can specify an action for clicking on the time (or weather). When this is done, it provides a large list of action - this list, to the best of my knowledge, doesn't show up anywhere.
Anyway, Mobile Data was checked (yes or on) so I cleared the list (resulting in mobile data being UNCHECKED) and rebooted. Mobile data remained unchecked so I'll watch for a while and report results later.
Click to expand...
Click to collapse
Could be placebo, I agree. Well, no harm done in any way
sure fire fix
Although it has been said that by renaming the phone.apk and telephony.apk you may risk bricking the device during a factory reset, I have renamed both and have seen an incredible increase in battery life.
Currently at six and a half hours of moderate use for music and web with some standby time and have 88% battery left. No cell standby being shown in battery stats either.
Reboots are fine, just don't factory reset without renaming the apk files back.
Installed Free Power Widget from the Market, says its installed but doesnt show in my widget list, strange.
Cell standby is simply terminology for when the tablet is asleep meaning screen off. So I wouldn't start changing it. In all likelihood you have an application that tries to access those two apps and when it doesn't find them it can't run its background process. I bet finding the culprit app would equally fix battery life.
cbotd said:
Although it has been said that by renaming the phone.apk and telephony.apk you may risk bricking the device during a factory reset, I have renamed both and have seen an incredible increase in battery life.
Currently at six and a half hours of moderate use for music and web with some standby time and have 88% battery left. No cell standby being shown in battery stats either.
Reboots are fine, just don't factory reset without renaming the apk files back.
Click to expand...
Click to collapse
Sent from my A500 using Tapatalk
peejayw said:
Installed Free Power Widget from the Market, says its installed but doesnt show in my widget list, strange.
Click to expand...
Click to collapse
I had the same, switch off and reboot made it appear in the list.
In much the same way photos I copied from a portable hdd onto the micro SD didn't show until I had powered off and on again.
Thanks, that did the trick.
@Canadoc: "Cell standby is simply terminology for when the tablet is asleep meaning screen off. So I wouldn't start changing it."
I do not believe this is correct. If this were true, removing Phone.apk and Telephony.apk would not affect battery usage, because the tablet would still use just as much power when the screen is off and it would still list "Cell standby" on the battery usage screen. In actuality, removing these two apps causes Cell Standby to disappear from the battery usage list and decreases actual battery usage. Plus, my "Cell Standby" % on the battery usage screen is highest when I have my tablet awake all day, and lowest on days when I let it go to sleep much of the time. So it must be doing something else in Cell Standby that uses power, probably trying to contact cell towers (in vain) even though it is a wi-fi only device.
A few minutes of Googling reveals that many Android wi-fi only models have the same problem (they try to access cell service even though they have no cell capability) and removing Phone.apk and TelephonyProvider.apk seems to fix the problem for everyone who's tried it. I have rooted my own A500 and removed them and it has given it an extra hour of battery time per full charge. YMMV, and it may someday brick when there's an update or something, but for now it works great. Cell standby was definitely doing something that it is now no longer doing.
I'm not 100% sure if android respects them(more experience on Linux than Android), but couldn't we just remove the exec flag off of the apk and not worry about bricking?
Or possibly set it's owner to system and deny rights to everyone but owner? Would that still allow updates?
I thought anything PRIOR to Honeycomb was made for phone ? ( froyo, gingerbread ...etc )
That info was actually made in press by Google !
So in essence, HC is for tablet ONLY ! why are we still seeing cell standby and phone apk ?
even if you argue because some tablets are 3G models ... 3G is about DATA ... not making a phone call !!! ( imagine bringing a 10" device up to the side of your ears )
there are some 7" tablets that are GSM capable... so, they CAN make GSM calls, and they DON'T use Honeycomb either.
anyone care to enlighten me why here we are with Honeycomb and still have the cellstandby and phone APK ??
UnicornKaz said:
anyone care to enlighten me why here we are with Honeycomb and still have the cellstandby and phone APK ??
Click to expand...
Click to collapse
Because Google are a bloody idiots?
Because hc was built on gingerbread. It wasn't built from nothing.
Sent from my Desire HD using Tapatalk
Battery issue (AndroidOS "bug") - workaround (3% loss over 9 hours!!!) - final update
Yes, I know, another battery thread. But after scouring many other threads for scraps of information, I feel I still have something to contribute on this widely talked about topic. If you’re not interested, don’t read or write on this thread – save your time, and mine. If it is useful to you, then great, please let us know. Here goes.
Like many people, I’ve been plagued with poor battery life on my SGS2. There are plenty of threads out there discussing how to trace the battery consumption back to the “Android OS” processes, specifically the “events” & “suspend” processes. Unfortunately, once isolating those processes, there’s not much we can do. Some say that when we get Android 2.3.4, battery issues might be solved, however:
My first Android phone was a HTC HD2, which was actually a WinMo phone that some clever people had managed to get a working Android ROM for. I started with Android 2.2.1, and as updates were released, upgraded to 2.2.2, 2.2.3, 2.3.1, 2.3.2, 2.3.3, and then I moved on to a new phone. All throughout these different Android versions, I had excellent battery life. The power draw on standby would be between 4ma – 6ma. (Unfortunately we can’t measure the power draw on our SGS2s.) If my phone was fully charged at night, I would wake about 8 hours later, to around 92% battery left. My SGS2 has more like 40-70% after that timeframe. The HD2 had great battery life before 2.3.4. We can all theorise about whether 2.3.4 will fix the issues, but I don’t know, you don’t know, and life goes on. (Personally, I suspect the Samsung base rather than the Android build, but that’s just a guess.)
So I decided to do a systematic approach to troubleshooting the battery issue on my phone, and identified the following possible causes & possible resolutions, based on other people’s comments, and a bit of logic:
• Battery itself
• Battery calibration
• Data connection
• Wifi
• Bluetooth
• GPS
• Location-awareness
• Latitude
• FastDormancy
• Phone connection
• SD card
• Kernel
• CPU speed
• Task killer
• Live Wallpaper
• Launcher
• Widgets
• Applications
• Stock vs custom ROM
• Hard-reset/data-wipe
Some details about my SGS2.I have a lot of applications installed, including the following that are always running (as services):
• WhatsApp
• PhoneWeaver
• Enhanced SMS & Caller ID
• NetQin Anti-virus
• Extended Controls
• Executive Assistant
• Enhanced Email
• Droidin
• Astrid Tasks
• SystemPanel
• SwiftKey X Beta
As well as the standard Samsung & Google background services.
I have used various versions of VillainROM, LiteningROM, and am now on CognitionROM 1.06. (All similar battery usage for me.)
I use LauncherPro Plus home launcher, and also have plenty of widgets on my screens:
• Beautiful Weather
• Agenda Plus
• Jorte
• Extended Controls
• Elixir (updating every 10 secs)
• LauncherPro Plus Facebook
• BBC News
• SetCPU (updating every 30 secs)
• 4 other miscellaneous small widgets
Ok, so here are my results, after testing most of the possibilities, for at least a couple of hours each, and some of them for longer:
Battery itself
I have 3 batteries, and all perform similarly, high drain occurs.
Battery calibration
I have used a battery calibration app several times, and followed the instructions to the letter, high drain still occurs.
This is however, still a useful process when changing ROMs, to help your battery stats be more accurate.
Data connection (tested for 8 hours multiple times)
Data connection turned off, high drain still occurs.
Wifi (tested for 8 hours multiple times)
Wifi turned off, high drain still occurs.
Bluetooth (I usually keep this off)
Bluetooth turned off, high drain still occurs.
GPS
GPS disabled, high drain still occurs.
Location-awareness
All location-awareness methods disabled, high drain still occurs.
Latitude
Never joined, high drain still occurs.
FastDormancy (tested for more than 8 hours in all 3 modes)
1. Default settings, high drain still occurs.
2. Configured for correct settings (my network supports FD) in /data/data/com.android.providers.telephony/databases, high-drain still occurs.
3. Disabled FD completely, high drain still occurs.
Phone connection (tested for 10 hours)
1. Set to GSM only, high drain still occurs.
2. Flight mode enabled (ie all network off), high drain still occurs. This is significant!
SD card
Removed external SD card, high drain still occurs.
Kernel
1. CF-Root KE7, KE8, KF1, KF2, KF4, high drain still occurs.
2. Cognition 1.03, 1.04, 1.05, 1.06, high drain still occurs.
CPU speed
Throttled to maximum 800mhz, high drain still occurs.
Task killer
1. Advanced Task Killer auto-kill when screen off, high drain still occurs.
2. Advanced Task Killer auto-kill disabled, high drain still occurs.
3. Advanced Task Killer auto-kill every hour, untested.
Live Wallpaper
I use a LWP that I have written, and am fairly satisfied that the code is efficient, and does not take up any noticeable amount of CPU when the phone is in standby. However, untested.
Launcher
Tried using LauncherPro, high drain still occurs.
Tried using TouchWiz, high drain still occurs.
Widgets
Removed all my widgets, <insert fanfare> high drain disappeared!!!
WiFi Sharing
Not exactly the "Android OS bug", but it can cause other battery drainage issues. I freeze it with Titanium Backup to prevent any grief.
Applications
Untested.
Stock vs custom ROM
Untested.
Hard-reset/data-wipe
I am sceptical of this approach, as it changes too many settings. Yes, everything will be faster, with less issues, more battery life, etc, when you do a data-wipe. However, once you configure everything back to how it was before, you’re in the same boat as when you started, and none the wiser.
So! A couple of important findings:
1. With Flight-mode enabled, I get poor battery. This pretty much eliminates any possibilities of 2G vs 3G, FastDromancy, and anything else that uses phone/WiFI/BT type stuff.
2. Widgets are what trigger the issues for me. I use a lot of them, and some of them update frequently. Android should be able to handle this, but something (probably either Android or Samsung code) is adding some battery overhead. This may be fixed by Google or Samsung in the future, but until then, I need a workaround. The next step for me is to add my widgets back in gradually, and see which ones trigger the battery grief. I'll update this thread with my findings regarding which widgets cause me grief, once I have them.
I'm back to having all my location services, data, phone, HSDPA/3G, SD card, and other basic services enabled. The only thing I don't have, is widgets on my homescreen, and battery performance is good.
Hopefully this will be of some help to those people still struggling with battery issues! If you're having battery issues, remove your widgets, monitor for at least a few hours, and report back!
------------------------------------------------
Update - 23/06/11
Every night at 10pm, my Data, AutoSync, & WiFi, are all switched off by PhoneWeaver. This should mean that minimal battery life is being used. I still usually get 30-60% drain though, which as we all know, is due to the "Android OS bug".
Last night, after having removed all my widgets, I charged my phone to 98%, and it entered its usual "Night mode" at 10pm. At 7am this morning, it automatically (via PhoneWeaver) went back in to "Home mode", which enabled AutoSync & WiFi. At 7:15am, my alarm went off, woke me up, and I checked the battery usage. It was down to 95%.
That's 3% drainage over 9 hours and 15 minutes!!!
This is the battery life that we should be expecting when we have things like Data & WiFi turned off.
I value my widgets, but I also value battery life. I'm going to keep working to find a decent compromise between the two. In the meantime, if you need battery life now, maybe consider removing some or all of your widgets.
------------------------------------------------
Update - 24/06/11
Last night, I re-added all of my widgets except Elixir, charged the phone to 100%, and let my phone enter "Night mode" (Data & WiFi off). Again, 9 hours later, WiFi auto-enabled, sync operations completed, etc. I checked it at 9 hours 15 minutes, and battery remaining was down to 96% - only 4% drop over the 9 hours. Similar to the night before. Very happy with that.
I've done a couple of tests today, and have found that adding the Elixir widget back on, brings back the "Android OS bug" for me. I have a lot of items configured in my Elixir widget (including some that show internal storage usage and SD card usage), and although I had set it to update only every hour, it still seems to trigger the hogging of my CPU by "Android OS". I'm going to try some different configurations of the Elixir widget (as it is a useful app), but at this stage, I've narrowed the battery issue trigger on my phone, to Elixir.
I haven't really heard of any confirmations from anyone else, that removing widgets has helped with their battery issues, so if you do have success with this, please let me know. I doubt it's specific to Elixir, but if you're affected, then the trigger may be something similar on your phone. If you want to test, I suggest the following:
1. Freeze the "Wi-Fi Sharing" app in Titanium Backup, as it commonly causes other battery drain issues. (Use "Wireless Tether" if you need that functionality.)
2. Remove all widgets from your home screen.
3. Turn off Data & WiFi connections.
4. Stop any running foreground applications (such as games etc), or reboot your phone.
5. Charge your phone, and note your battery percentage.
6. Turn off your screen, and leave it off for at least 2 hours.
7. Turn your screen back on, and check your percentage.
8. If there has still been a high drain (any more that 1 or 2%), check your battery usage to see if "Android OS" is the culprit.
9. If it's something else, target that. If it's still "Android OS", then I guess widgets are not your trigger.
10. Let us know whether it worked for you or not!
------------------------------------------------
Update - 28/06/11
Probably the last update from me, as my battery usage is nice and stable now, and I have no other information to give.
Happy to hear success stories from a few people - removing widgets has improved their battery life. Obviously we don't want to be removing all of our widgets, as if we wanted to cripple our phones, we'd probably just get evil iPhones, instead of the powerhouse that is the SGSII. For me, I've been able to add all my widgets back in, and narrowed down the drain to Elixir. Fortunately, I've found that I can use Elixir without any issues, as long as I take out the CPU & storage card stats icons. Even though I had it set to update only ever hour, it would still drain my battery way too quickly. I can live without a running commentary on how much free space I have on my SD card, and how much CPU I'm currently using. (SystemPanel gives me all the monitoring I need.)
So if you're still having trouble, my advice is to:
first calibrate your battery with a battery calibration tool (or manually delete your battery stats file)
second, freeze the "Wi-Fi Sharing" app, and
third, check your widgets. Most widgets probably won't impact your battery noticeably, and shortcuts shouldn't either. Once you've tracked down the problem widget(s), try to determine whether you can reconfigure it/them to avoid the drain (perhaps with less updates).
Some battery usage results from posters:
lindsaytheflint - 0.32% per hour, over 9.5 hours, in flight-mode.
JJEgan - 0.08% per hour, over 13 hours, in flight-mode.
sjedwardz - 1.77% per hour, over 22 hours.
So we can get good battery life with these phones, even without 2.3.4, and with only a little bit of tweaking. Obviously, using the phones (i.e. screen on) will (and should) use the battery faster, so the important test is while the phone is in standby. Good luck!
lindsaytheflint said:
Yes, I know, another battery thread. But after scouring many other threads for scraps of information, I feel I still have something to contribute on this widely talked about topic. If you’re not interested, don’t read or write on this thread – save your time, and mine. If it is useful to you, then great, please let us know. Here goes.
Like many people, I’ve been plagued with poor battery life on my SGS2. There are plenty of threads out there discussing how to trace the battery consumption back to the “Android OS” processes, specifically the “events” & “suspend” processes. Unfortunately, once isolating those processes, there’s not much we can do. Some say that when we get Android 2.3.4, battery issues might be solved, however:
My first Android phone was a HTC HD2, which was actually a WinMo phone that some clever people had managed to get a working Android ROM for. I started with Android 2.2.1, and as updates were released, upgraded to 2.2.2, 2.2.3, 2.3.1, 2.3.2, 2.3.3, and then I moved on to a new phone. All throughout these different Android versions, I had excellent battery life. The power draw on standby would be between 4ma – 6ma. (Unfortunately we can’t measure the power draw on our SGS2s.) If my phone was fully charged at night, I would wake about 8 hours later, to around 92% battery left. My SGS2 has more like 40-70% after that timeframe. The HD2 had great battery life before 2.3.4. We can all theorise about whether 2.3.4 will fix the issues, but I don’t know, you don’t know, and life goes on. (Personally, I suspect the Samsung base rather than the Android build, but that’s just a guess.)
So I decided to do a systematic approach to troubleshooting the battery issue on my phone, and identified the following possible causes & possible resolutions, based on other people’s comments, and a bit of logic:
• Battery itself
• Battery calibration
• Data connection
• Wifi
• Bluetooth
• GPS
• Location-awareness
• Latitude
• FastDormancy
• Phone connection
• SD card
• Kernel
• CPU speed
• Task killer
• Live Wallpaper
• Widgets
• Applications
• Stock vs custom ROM
• Hard-reset/data-wipe
Some details about my SGS2.I have a lot of applications installed, including the following that are always running (as services):
• WhatsApp
• PhoneWeaver
• Enhanced SMS & Caller ID
• NetQin Anti-virus
• Extended Controls
• Executive Assistant
• Enhanced Email
• Droidin
• Astrid Tasks
• SystemPanel
• SwiftKey X Beta
As well as the standard Samsung & Google background services.
I have used various versions of VillainROM, LiteningROM, and am now on CognitionROM 1.06. (All similar battery usage for me.)
I use LauncherPro Plus home launcher, and also have plenty of widgets on my screens:
• Beautiful Weather
• Agenda Plus
• Jorte
• Extended Controls
• Elixir (updating every 10 secs)
• LauncherPro Plus Facebook
• BBC News
• SetCPU (updating every 30 secs)
• 4 other miscellaneous small widgets
Ok, so here are my results, after testing most of the possibilities, for at least a couple of hours each, and some of them for longer:
Battery itself
I have 3 batteries, and all perform similarly, high drain occurs.
Battery calibration
I have used a battery calibration app several times, and followed the instructions to the letter, high drain still occurs.
Data connection (tested for 8 hours multiple times)
Data connection turned off, high drain still occurs.
Wifi (tested for 8 hours multiple times)
Wifi turned off, high drain still occurs.
Bluetooth (I usually keep this off)
Bluetooth turned off, high drain still occurs.
GPS
GPS disabled, high drain still occurs.
Location-awareness
All location-awareness methods disabled, high drain still occurs.
Latitude
Never joined, high drain still occurs.
FastDormancy (tested for more than 8 hours in all 3 modes)
1. Default settings, high drain still occurs.
2. Configured for correct settings (my network supports FD) in /data/data/com.android.providers.telephony/databases, high-drain still occurs.
3. Disabled FD completely, high drain still occurs.
Phone connection (tested for 10 hours)
1. Set to GSM only, high drain still occurs.
2. Flight mode enabled (ie all network off), high drain still occurs. This is significant!
SD card
Removed external SD card, high drain still occurs.
Kernel
1. CF-Root KE7, KE8, KF1, KF2, KF4, high drain still occurs.
2. Cognition 1.03, 1.04, 1.05, 1.06, high drain still occurs.
CPU speed
Throttled to maximum 800mhz, high drain still occurs.
Task killer
1. Advanced Task Killer auto-kill when screen off, high drain still occurs.
2. Advanced Task Killer auto-kill disabled, high drain still occurs.
3. Advanced Task Killer auto-kill every hour, untested.
Live Wallpaper
I use a LWP that I have written, and am fairly satisfied that the code is efficient, and does not take up any noticeable amount of CPU when the phone is in standby. However, untested.
Widgets
Removed all my widgets, <insert fanfare> high drain disappeared!!!
Applications
Untested.
Stock vs custom ROM
Untested.
Hard-reset/data-wipe
I am sceptical of this approach, as it changes too many settings. Yes, everything will be faster, with less issues, more battery life, etc, when you do a data-wipe. However, once you configure everything back to how it was before, you’re in the same boat as when you started, and none the wiser.
So! A couple of important findings:
1. With Flight-mode enabled, I get poor battery. This pretty much eliminates any possibilities of 2G vs 3G, FastDromancy, and anything else that uses phone/WiFI/BT type stuff.
2. Widgets are what trigger the issues for me. I use a lot of them, and some of them update frequently. Android should be able to handle this, but something (probably either Android or Samsung code) is adding some battery overhead. This may be fixed by Google or Samsung in the future, but until then, I need a workaround. The next step for me is to add my widgets back in gradually, and see which ones trigger the battery grief. I'll update this thread with my findings regarding which widgets cause me grief, once I have them.
I'm back to having all my location services, data, phone, HSDPA/3G, SD card, and other basic services enabled. The only thing I don't have, is widgets on my homescreen, and battery performance is good.
Hopefully this will be of some help to those people still struggling with battery issues! If you're having battery issues, remove your widgets, monitor for at least a few hours, and report back!
Click to expand...
Click to collapse
Thanks for the in-depth analysis.
I figured it as much that it had to be Active Widgets that cause a higher drain than normal. I dont have any widgets active and dont have any drain, but I can see them running as a service.
I always wondered that if they were removed from the service, will the battery life improve or not make any difference, since the widget isnt really running, only the service. Force Quiting the Widget Service only has them come back shortly after.
Ok I jump in. I've the same issues. Now I disabled my lockscreen (widget locker) and deleted all my widgets. I'll report later if this was the key. BTW what about the screen settings for the brightness? I've set my brightness to 40% static.
Sent from my GT-I9100 using XDA App
What kind of router do you have? Your drain is to high to be just the android-os bug.
Sent from my GT-I9100 using XDA Premium App
[germany]merlot said:
BTW what about the screen settings for the brightness? I've set my brightness to 40% static.
Click to expand...
Click to collapse
I haven't looked at the brightness, as I've been troubleshooting the drain issue purely for when the phone is in standby (i.e. screen off). My display is set to automatic brightness.
TheGhost1233 said:
What kind of router do you have? Your drain is to high to be just the android-os bug.
Click to expand...
Click to collapse
My home WiFi router is not the issue. I only have WiFi enabled for a few hours each day, but my drain is always. My tests included disabling all network connections.
A drain of 30-60% (i.e. resulting in 40-70% left after 8 hours from a 100% charge) is typical of the kind of issues a lot of people have been having. If it wasn't so bad, so many of us wouldn't be so desperate to have it fixed. And yes, my battery usage in both the built-in battery tracking, & SystemPanel, both indicate "Android OS".
Hmm..it could be because I also have high drain and I currently have 13 widgets on my homescreens:Simple calendar, Simi Clock, Spotify, 7xHangping chinese, Snowstorm (update every 3h), CNN(update every 6h), Pure messenger(update every 6hours).
I wouldn't want to get rid of any of those widgets because after all these are the main difference compared to iPhone. What is the point of having Android if you just want the icons on your homescreen.
On the other hand I have been wondering one other issue with the battery drain. When I used to have Touch Pro 2, I used many different ROMs and there the battery was hugely affected by which radio it had. For example I live in Finland and if I used chinese rom with chinese radio the phone did work but the signal was never as good as with European/Finnish radio and also more drain affected.
I noticed similarity when updated to Hong Kong firmware, I didn't get so good signal in any place and I think I lost more battery.
Of course this isn't the whole solution if the battery drain is high also with the airplane mode. But for me even if I turn the data off and use only 2G I get pretty decent battery. So I think there is more than one problem effecting this.
I THINK that CNN widget might be quite bad for the battery..that I could try to get rid off..
There have been plenty of reports of people with a specific router that, once connected just one time, will cause high drain until you do a factory reset. And yes it also displays under android-os but it's a second bug.
Sent from my GT-I9100 using XDA Premium App
I lost 30% battery from 100 to 70 in 8 hours i slept. The only thing that was on was the yahoo mail push service. I deleted all the widgets that came pre-installed except the time/date one on the home screen. The phone was locked with screen off and brightness set to 0.
Is this normal? I have frozen a lot of samsung apps and services that are not needed.
Maybe its launcher pro, I might try deleting that and see how it goes for a while
Hi TS,
good effort here. i am wondering, after you removed all the widget and experiencing better battery life, does Android OS still use high usage?
this is the first android phone that i notice Android OS taking up such a significant portion. all my previous phones, one hardly notices it's usage in the battery stats.
Great list with tests! Although I don't think widgets are causing the high drain. It's something more deep underlying in the stock ROM... All working ROMs are based on the stock one and that's why we all have the Android OS bug.
I've seen people that report no Android OS drain on AOSP ROM (which someone only got booting, it's not usable but there is no battery drain). On the MUIUI ROM which we also got booting is also no battery drain...
What we can do now is WAITING... until we either 1. get a new updated ROM from samsung which solves the issue. or 2. we get a clean and stable CM7 ROM
Thanks my opinion...
Think I'm going to post this everywhere as there seems to be huge amout of people that blame poor battery life on this bug even if it's not the case.
The example of my phone:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
djfatrod said:
Maybe its launcher pro, I might try deleting that and see how it goes for a while
Click to expand...
Click to collapse
Yes, next thing I was going to try was a different launcher. I may still try switch to TouchWiz, and putting on all my widgets. Launcher Pro doesn't have any such issues with other Android phones I've had, but there may be something in the SGS2 code that causes an incompatibility.
sunwee said:
Hi TS,
good effort here. i am wondering, after you removed all the widget and experiencing better battery life, does Android OS still use high usage?
this is the first android phone that i notice Android OS taking up such a significant portion. all my previous phones, one hardly notices it's usage in the battery stats.
Click to expand...
Click to collapse
After removing the widgets, Android OS is no longer high. Other things are now higher (such as when I use the phone etc) which is what you'd expect in Android.
I agree with you - I haven't had this issue on other phones either.
(TS?)
d3sm0nd said:
Great list with tests! Although I don't think widgets are causing the high drain. It's something more deep underlying in the stock ROM... All working ROMs are based on the stock one and that's why we all have the Android OS bug.
I've seen people that report no Android OS drain on AOSP ROM (which someone only got booting, it's not usable but there is no battery drain). On the MUIUI ROM which we also got booting is also no battery drain...
What we can do now is WAITING... until we either 1. get a new updated ROM from samsung which solves the issue. or 2. we get a clean and stable CM7 ROM
Thanks my opinion...
Click to expand...
Click to collapse
I agree - I don't believe the widgets are the cause, but I do think having widgets is triggering the high drain. Something in Samsung's build is doing it.
I'm sure on a AOSP, MIUI, or CM7 the issue won't occur. It doesn't occur on proper builds on other phones. Just something in Samsung's build.
Definitely looking forward to a working non-Samsung build!
Personally I doubt, that the Battery usage stats from android give enough details about the battery usage. Therefore I think its misleading...
Btw, I am on stock rom KE7, no bug/drain here...
aurelm said:
Think I'm going to post this everywhere as there seems to be huge amout of people that blame poor battery life on this bug even if it's not the case.
The example of my phone:
Click to expand...
Click to collapse
I'm not sure what this adds, or how it's relevant. I don't think you read my first post properly, or if I was unclear, then I apologise.
The issue I was having, was that my phone was discharging very rapidly, even under various different scenarios, including my phone display being switched off for 8 hours, and flight-mode being enabled, etc. After this 8 hours of non-use, the battery would have discharged by 30-60%, and the "Android OS" processes (specifically, "suspend" and "events") were taking up around 90% of the usage.
This thread is not about debating the existence of the "Android OS bug", nor about how to identify it. This thread is about testing to see what can be done to workaround the "bug".
I think you also missed my statement in the first post: "If you’re not interested, don’t read or write on this thread – save your time, and mine."
pik1 said:
Personally I doubt, that the Battery usage stats from android give enough details about the battery usage. Therefore I think its misleading...
Btw, I am on stock rom KE7, no bug/drain here...
Click to expand...
Click to collapse
System Panel gives quite a bit of useful detail around things like CPU usage, which is a significant factor in battery usage.
lindsaytheflint said:
System Panel gives quite a bit of useful detail around things like CPU usage, which is a significant factor in battery usage.
Click to expand...
Click to collapse
It is actually interesting to see that there is Accu weather, AP mobile, digital clock and all those rest apps in the memory even thou I dont use them and never even opened them.
Sight...maybe I have to root the phone once again and freeze those apps after all even thou I was wishing that I could just keep my phone close to stock.
Im currently on XXJVS with Semaphore 1.7 kernel, but i have experienced the same behaviour the last weeks (or maybe i just started noticing recently): traveling starts a battery drain
Update: see post #22
Some background:
I suffered from the Android Process battery drain up to XXJVR. Flashing XXJVS seems to have improved things (after numerous reflashes of XXJVR and XXJVQ which didnt help. My phone's cpu keeps between 1% and 3% when sleeping, but i have noticed that Cpu rockets to like 30% as soon as i leave my house to go to work, or leave work to go home. Its as if the phone keeps trying to connect to some network all the time, but only while in motion (and trying to lock in from tower to tower?). The problem is however that Systempanel nor the log give great clues where to look.
Examples:
In this first example, my phone is hooked to the charger during the night, and the alarm clock is running (hence the steady 10% cpu load). As soon as the phone is disconnected, cpu drops to low levels. On the exact minute i leave home, cpu rockets. And yes,i arrived at work around 07:50.
Home environment:
- connected to wifi
- good 3G coverage
- 3G, Bluetooth,GPS enabled
- no Bluetooth profiles present
Work environment
- wifi network present but not connected
- average 3G coverage
In this second example, i'm at work, hardly using the phone. Without touching the phone, stepping into my car and driving off, the cpu kicks in again. Notice there is no Device Usage whatsoever at the moment the CPU climbs. Bluetooth profiles active at this point and paired & connected to the carkit.
This last screenshot shows the typical clues (or lack thereof) that SystemPanel shows: just the System process using the most CPU.
Also the logcat doesn't provide much clues (or too many maybe) either. I have found that some applications couldn't contact GoogleAnalystics because i have AdFree installed, so i uninstalled those apps.
Frankly, i don't know where took look further. The damn android 'System'process just doesn't give enough clues. I have formatted internal & external SD, deleted cache & Dalvik cache, flashed & factory resetted to no avail. I'll try to have a log running tomorrow morning just before leaving the house to see if i can find what log entry corresponds to the system process kicking in. In the meantime, has anyone ever seen this behaviour, or any hints where to look?
adb bugreport > c:/report.txt
look there maybe
Install System Tuner pro it has option to record processes(+analyzer ) better than System Panel.
..try freze Maps or turn off network localization -Uncle Google likes to locate phone very often .
Sent from my GT-I9000 using xdapp
Hi,
Same phone and ROM, same problem.
Keep us updated!
Hmm, I have heard Galaxian kernel is battery sucker too...
Regards
wingg said:
Install System Tuner pro it has option to record processes(+analyzer ) better than System Panel.
..try freze Maps or turn off network localization -Uncle Google likes to locate phone very often .
Click to expand...
Click to collapse
in short words - bull****
i have not touched (freezed/deleted) any app
yet still i have not noticed a drain, any kind of drain
let him determine what app is causing the 100% cpu usage first
prior to advising him to freeze or delete anything - that is wise you have to agree
also localization service would not provide such high cu usage
think please
Hi,
It might be facebook 1.7.1. There are several complaining comments that "upload manager" process is running in the background and prevents phone from going into deep sleep mode.
i got data connection active all the time with all apps syncing (gmail, twitter, facebook)
and phone got no problem sleepin =)
pwhooftman said:
Im currently on XXJVS with Semaphore 1.7 kernel, but i have experienced the same behaviour the last weeks (or maybe i just started noticing recently): traveling starts a battery drain
Some background:
I suffered from the Android Process battery drain up to XXJVR. Flashing XXJVS seems to have improved things (after numerous reflashes of XXJVR and XXJVQ which didnt help. My phone's cpu keeps between 1% and 3% when sleeping, but i have noticed that Cpu rockets to like 30% as soon as i leave my house to go to work, or leave work to go home. Its as if the phone keeps trying to connect to some network all the time, but only while in motion (and trying to lock in from tower to tower?). The problem is however that Systempanel nor the log give great clues where to look.
Examples:
In this first example, my phone is hooked to the charger during the night, and the alarm clock is running (hence the steady 10% cpu load). As soon as the phone is disconnected, cpu drops to low levels. On the exact minute i leave home, cpu rockets. And yes,i arrived at work around 07:50.
Home environment:
- connected to wifi
- good 3G coverage
- 3G, Bluetooth,GPS enabled
- no Bluetooth profiles present
Work environment
- wifi network present but not connected
- average 3G coverage
In this second example, i'm at work, hardly using the phone. Without touching the phone, stepping into my car and driving off, the cpu kicks in again. Notice there is no Device Usage whatsoever at the moment the CPU climbs. Bluetooth profiles active at this point and paired & connected to the carkit.
This last screenshot shows the typical clues (or lack thereof) that SystemPanel shows: just the System process using the most CPU.
Also the logcat doesn't provide much clues (or too many maybe) either. I have found that some applications couldn't contact GoogleAnalystics because i have AdFree installed, so i uninstalled those apps.
Frankly, i don't know where took look further. The damn android 'System'process just doesn't give enough clues. I have formatted internal & external SD, deleted cache & Dalvik cache, flashed & factory resetted to no avail. I'll try to have a log running tomorrow morning just before leaving the house to see if i can find what log entry corresponds to the system process kicking in. In the meantime, has anyone ever seen this behaviour, or any hints where to look?
Click to expand...
Click to collapse
i think you should go out and do some thing better with your life then watching what a battery uses
i think its a waste of space to quote WHALE post
and well if he got battery drained overnight it is important to determine why
it should not happend
Just a quick question, where is the phone when you are in the car? I have noticed that if I keep my phone in my trouser pocket while driving, I loose signal frequently, shown on Bluetooth unit, and over a 3hour journey I can loose 30% battery, but if I put the phone in my shirt pocket I do not loose signal and my battery loss is about 20%.
My theory is that the phone signal finds it easier to penetrate the glass windows of the car rather that the metalwork.
Similarly to Geryatrix, when I leave my phone beside my bed (=~~, best place for alarm), my battery drains because the phone stays with a very low network signal and keeps searching for better antennas, I guess. But then at "Battery Usage" I could see that "Cell Standby" was eating my bat, not the "Android System".
battery drains from wifi staying connected in idle state - thats a bug in my opinion from samsung - it should not use such ammount of energy
data connection in idle is almost unnoticable in battery use
When I had facebook 1.7.1 installed, "Android System" was consuming 20% battery.
After I uninstalled facebook 1.7.1 and the problem is gone, "Android System is back
to normal, about 4%.
got-petrol said:
i think you should go out and do some thing better with your life then watching what a battery uses
Click to expand...
Click to collapse
I think you should learn not to quote an entire long message for the sake of making 1 stupid remark
Start post will be updated in a few minutes with some new information.
seems like one of apps you use is trying to connect somewhere
have you made bugreport - i think you will find the culprit there
Have you tried disabling fast dormancy? Maybe these wakelocks are caused by incompatible 3g cell.
Use *#*#9900#*#* to find option to disable it.
Sent from my GT-I9000 using xda premium
$omator said:
think please
Click to expand...
Click to collapse
No comment...
Sent from my GT-I9000 using xda premium
wingg said:
No comment...
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
and what is your problem to start oftop whining?
use report button if you do not like my post or tone of it
and freezing/deleting apps is not and never will be an issue solver
system works perfect with none of stock apps touched
using memory killers and altering system with such freeze options
is on the other hand source of 9 on 10 problems
$omator said:
battery drains from wifi staying connected in idle state - thats a bug in my opinion from samsung - it should not use such ammount of energy
data connection in idle is almost unnoticable in battery use
Click to expand...
Click to collapse
Hi,
I have opposite experience. Keeping Wifi enabled causes almost no battery drain for me, keeping 3G enabled does big time. My Galaxy Tab 10.1 Wifi version is set to never let the wifi connection sleep, and still battery drains no more than 1% or 2% a day is the tablet is not used.
I tested today with Wifi disabled. Still the Enter Dormancy messages appear each 5 seconds, altough the CPU hit is less. The Fast Dormacy messages seem purely cell-tower related, and wifi-unrelated. The Dormancy messages start as soon as i start moving, and stop when i'm home. I will update the startpost agan tonight.
---------- Post added at 06:55 PM ---------- Previous post was at 06:52 PM ----------
Kurre said:
Have you tried disabling fast dormancy? Maybe these wakelocks are caused by incompatible 3g cell.
Use *#*#9900#*#* to find option to disable it.
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
Hi,
I entered this Sysdump menu, the button read ""Enable Fast Dormancy" so i guess that means it was disabled all along. I enabled fast dormancy and will continue to test.