Database Users

guide to control your battery and keep build smooth

There lot of interrogations and frustrations concerning slowdowns/battery drains on Android, sometimes not really fair.
You need to control your build and knowing what is going on into it, because most programs you install live from their own and can downgrade your stability and your battery performance.
A detailed guide is provided here in order to have a good battery drain with very smooth and reliable android experience on Hd2, gathering tips and advices users need to know when they come to this Os or want to improve it durably.
Following this guide, you will be able to have hundreds of apps into a super smooth, stable and battery friendly android build.
Most importantly, without transforming your smartphone into a dumbphone :
- Wifi and sync always on
- Mails checked every hour
- 148 applications installed (no I don’t need them all ;-) )
- 6 widgets running on the screen or in background (check screenshot) : Folder organizer, News, Facebook, Current widget, Powersnap, switch pro, pure calendar, pure grid calendar.
- In standby, it can last for 4 days :
{
"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"
}
- Smartphones are more and more looking like a laptop, so I consider that 5 or 6 hours with the screen alight is good.
The assumption is the battery drain can be affected by several factors:
1) Screen brightness.
2) Memory management if wrongly configured
3) Program launching in background if wrongly configured
4) Program updating in background if wrongly configured
5) Build and Kernel
6) Wm rom, radio, Sd card, Cpu in standby
7) Extras : Backups, customizing etc
Once you have the good utilities and understand how it works, it is easy to setup and need no more tweaks, unless you install new apps.
To keep a battery trace, current widget with logs and battery snap are mainly used.
1) Screen consumption
The screen battery consumption is huge when we use the phone. It was the same on windows mobile, and was to expect when buying it with that huge size.
Therefore, the screen brightness is an important factor to deal with.
In order to keep a good battery life when your phone is on, you need to keep your phone around 300 MiliAmpers or less. You have to keep in mind that a 75% brightness = 500Ma.
The best behavior is to keep your screen :
-25% brightness at home, with no sun.
-50% brightness mostly of the time
-75% and 100% brightness in very rare occasions with direct sun exposition.
In order to swich fast between this settings, and since we don’t have for now a functional kernel with auto brightness, using a brightness widget is recommended.
I personnaly use “Brighness level”, and launch it by swiping a dock icon into launcher pro.
Ps : Take care to not press 0%, or your screen will be completely dark. You can revert by guessing where the icons were, but it is tricky.
2) Memory management
In order to keep your hd2 fast and battery friendly, it is better to keep your phone with more than 200Mo free ram (when you are not using it).
There is a great free program for that, called task panel X. With it you can choose which program you want to close every time you put your phone in standby.
It is very important that you choose well the apps that need to stay in memory, and the others.
It is pretty simple: Keep the widget you use and system apps. Discard all the others by including them in the autokill list. It is a bit long to do if you have hundreds apps, but you have to do it only one time.
Example:
3) Programs launching automatically in background
You need to control the apps you install. Problem is that some programs are launched automatically into your memory at any time. I was surprised to see that programs that don’t need to be to stay in memory (when I don’t use them) launch by themselves at anytime. “Mabilo wallpapers” was the best (or worst) example.
You need an app to control that. I recommend “Startup Auditor”, and set carefully wich apps that can launch by themselves or not. Same as with task panel, just keep system apps and widgets. You can keep too your mail app. If you don’t use the Gmail app program, remove it from the list.
You will see into task panel that very few programs keeps running despite of that. You have to question yourself: “Ok this one is great to find new wallpapers, but it is constantly running in my memory and I don’t know why (suspicious) -> Do I really need it ?”
4) Programs updating in background
Programs that you authorize to launch automatically in your memory are often in order to update automatically things. (Mail, weather, facebook, tweeter etc…)
It is important that you know what they are, and where are located their update settings in order to not to waste uselessly your battery. Checking mails each hour or two hour is sufficient. Checking every 15mn cause obvious battery drains.
For most needs, manual updates for social apps or weather is sufficient, because it take only two seconds when you want to see them. If manual updating is not available, choose the longer updating interval (one day for example)
5) Builds
The following is based on my personal opinion; you are free to use and test every build you want.
First, i don’t recommend using sense builds due to personal bad experiments. I had crash and a lot of slowdowns, but most importantly it was battery draining due to all the htc third apps hard coded into. It is a build very hard to control.
I use and recommend a shubCRAFT 1.5 with stock Cyanogen mod 6 Final :
http://forum.xda-developers.com/showthread.php?t=740963
Don’t forget to download the 1Go user data file in order to install more apps.
It’s a build very fast to boot, smooth, efficient and highly customizable. The kernel provided in it is good for now.
Launcher Pro is used here, very smooth and easy to customize.
6) Wm rom, radio, Sd card, Cpu
SetCpu can be usefull, depending on the kernel you are using. There is a lot of threads on it, the most important setting is to downclock your cpu at standby.
Sd card
There is some evidences that your sd card can drain your battery. If you follow this guide and still have battery drain, it can be the cause. Check into this post :
http://forum.xda-developers.com/showthread.php?t=781433
I use a Kingston 16Go class 10 micro sdhc card with no issue.
Registry tricks :
I had before these regitry settings into windows mobile rom, no idea how it affect Android :
http://forum.xda-developers.com/showthread.php?t=585729
Radio
I use 2.12.50.02_02
Ppp or rmnet
I don't have dataplans, so i can't tell about rmnet or ppp battery drains, but my suggestions to users who use it, is to activate it when you turn on your phone or every one hour, with a third app like Tasker.
SuperUser permissions
Polo735 suggest that, in rare cases, the superuser permissions program can be faulty and need te reinstalled, otherwise it drains your battery.
Symptoms are : When installing an app requiring superuser permissions, no pop up granting it appear.
See his post here
7) Extras :
If you like the screenshots design, it is the stock Shubcraft froyo framework with a custom black toolbar form manup revolution theme, compressed for speed. You can download it bellow and copy the file to /sdcard/Android/root/system/framework/ You have to set some custom colors into the cyanogens mod settings:
-Toolbar color in black
-Clock color in white
-Date and toolbar title in white.
Have fun !

Nice one, thanks!

Blame73 said:
Nice one, thanks!
Click to expand...
Click to collapse
Happy to help

Sichroteph said:
I don't have dataplans...
Click to expand...
Click to collapse
This is possibly the major reason of your low battery consumption...

Wildcopper said:
This is possibly the major reason of your low battery consumption...
Click to expand...
Click to collapse
Na, I use data most of the and with it turned on I get between 7 and 10 mA in standby,
Nice thread was already using most fixes just different apps, any chance of a link for task panel x can't find it on market.
And like the brightness app, lol first thing I did was press 0%
Sent from my HTC HD2 using Tapatalk

Sichroteph said:
Happy to help
Click to expand...
Click to collapse
I'd recommend you give bangsters build a shot, according to shu8i's Twitter he's offline till October :-\ bangster us constantly updating and everything is pretty stable
Sent from my HTC HD2 using Tapatalk

whynot66 said:
Na, I use data most of the and with it turned on I get between 7 and 10 mA in standby,
Nice thread was already using most fixes just different apps, any chance of a link for task panel x can't find it on market.
And like the brightness app, lol first thing I did was press 0%
Sent from my HTC HD2 using Tapatalk
Click to expand...
Click to collapse
Try this link from your htc hd2, should bring you directly to the market :
market://search?q=pname:com.taskpanel

Sichroteph said:
Try this link from your htc hd2, should bring you directly to the market :
market://search?q=pname:com.taskpanel
Click to expand...
Click to collapse
Thanks but Not there for me :-( where are you based? Must need the market enabler
Sent from my HTC HD2 using Tapatalk

whynot66 said:
Na, I use data most of the and with it turned on I get between 7 and 10 mA in standby
Click to expand...
Click to collapse
I use data and get 5mA in standby (screen off).
If this was true, the 1230mAh battery should last 1230/5=246 hours in standby mode running Android, which is 10.25 days, right?
We all know this isn't true.
The battery consumption gadget is cute, but not precise

whynot66 said:
I'd recommend you give bangsters build a shot, according to shu8i's Twitter he's offline till October :-\ bangster us constantly updating and everything is pretty stable
Sent from my HTC HD2 using Tapatalk
Click to expand...
Click to collapse
Agree, it is a good build too. Cyanogen makes thing so smooth. I recommended Shubcraft, just because i have no drawback to say about it, but fortunately there are other builds we can use.

Wildcopper said:
I use data and get 5mA in standby (screen off).
If this was true, the 1230mAh battery should last 1230/5=246 hours in standby mode running Android, which is 10.25 days, right?
We all know this isn't true.
The battery consumption gadget is cute, but not precise
Click to expand...
Click to collapse
Who's gonna leave there phone in standby for ten days to test it, infact who's gonna leave their hd2 in there pocket for 30minutes, fact is my data is on I've just been to my current widget log and for the last ten minutes (logging every 2mins) my usage was 4mA, 5mA, 3mA, 6mA, 4mA
So you tell me? Guess the current widget doesn't work
Is there any other battery widgets so I can run multiple ones and compare.results?
I left off charge last night for 8 hours while I slept and used 5% I think its pretty accurate reality.
Sent from my HTC HD2 using Tapatalk

Wildcopper said:
I use data and get 5mA in standby (screen off).
If this was true, the 1230mAh battery should last 1230/5=246 hours in standby mode running Android, which is 10.25 days, right?
We all know this isn't true.
The battery consumption gadget is cute, but not precise
Click to expand...
Click to collapse
I made a simplier calculation. I lost 1% per hour, so 4 days in standby. maybe a more rigorous way. Current widget is not always very precise, but it can help a lot to trace possible battery drains.

whynot66 said:
Thanks but Not there for me :-( where are you based? Must need the market enabler
Sent from my HTC HD2 using Tapatalk
Click to expand...
Click to collapse
I extracted the Taskpanel X apk from a titanium backup ... Don't know if it will work for you.

Sichroteph said:
I made a simplier calculation. I lost 1% per hour, so 4 days in standby. maybe a more rigorous way. Current widget is not always very precise, but it can help a lot to trace possible battery drains.
Click to expand...
Click to collapse
Yeah, that's more accurate. That's approximatively what I lose too. But it's definitely draining more than 5mA.
It's not THAT bad, but Windows Mobile is still way more energy efficient.
My guess is that there are some things that should be turned off but aren't, hardware wise, when the HD2 runs under Android.

Wildcopper said:
Yeah, that's more accurate. That's approximatively what I lose too. But it's definitely draining more than 5mA.
It's not THAT bad, but Windows Mobile is still way more energy efficient.
My guess is that there are some things that should be turned off but aren't, hardware wise, when the HD2 runs under Android.
Click to expand...
Click to collapse
That's not the point of this thread. I am pretty sure this it is useful to new users because wm and android are obviously different to manage. I want to bring something rational here, talking about screen consumption and memory management. Not about "something" we can't see but drains.
I saw several windows mobile threads concerning battery life frustrations too, so it would be more constructive to make some real battery tests between this two Os. For now, what some users complains are just "feelings" for me.

Hey, I didn't want to belittle your thread, the OP is definitely useful
My point was, right now even with all tweaks, the situation is not really satisfying, and hopefully soon we won't need any tweaking anymore because the developers will have perfected the HD2 port.

One thing that may help some people:
Make sure that your phone is using superuser permissions correctly. A while back on an earlier build I installed setcpu and autokiller. I thought they were working correctly but my battery life was poor. I tried opening superuser permissions and it crashed. I uninstalled Superuser Permissions, then reinstalled. Now setcpu and autokiller work correctly and battery is very good.
There is no indication that these apps aren't working besides the "... granted superuser permissions" popup. If you don't know to look for that message you may not realize there is a problem.

polo735 said:
One thing that may help some people:
Make sure that your phone is using superuser permissions correctly. A while back on an earlier build I installed setcpu and autokiller. I thought they were working correctly but my battery life was poor. I tried opening superuser permissions and it crashed. I uninstalled Superuser Permissions, then reinstalled. Now setcpu and autokiller work correctly and battery is very good.
There is no indication that these apps aren't working besides the "... granted superuser permissions" popup. If you don't know to look for that message you may not realize there is a problem.
Click to expand...
Click to collapse
Never saw that problem before, nevertheless with no doubt it can help a lot.
Added in first post, thanks.

Android OS process eating away battery life

Hi all,
So, this problem appears common on other phones as well, and appears to be a Gingerbread issue. Drilling down further using Watchdog Lite on the phone, it appears to be a process called Suspend causing the high CPU usage.
There are a few threads on this:
http://code.google.com/p/android/issues/detail?id=11126#makechanges
http://code.google.com/p/android/issues/detail?id=15057
http://forum.xda-developers.com/showthread.php?p=10004299&posted=1#post10004299
http://forums.t-mobile.com/t5/myTouch-4G/quot-suspend-quot-linux-process/m-p/605813
Personally, I'm getting pretty terrible battery life out of my S2, and I can confirm that in the Battery Status menu, Android OS appears extremely high at around 40% (a friends Nexus has this sitting at around 2%).
Not sure there's much we can do about it but wait and hope for a fix from Samsung (or Google)... People are reporting that rebooting the phone can help, but it's only temporary.
Anyway, just something to check if you're having issues.

+1 second that.
Android os eats the most of the battery
Reboot helps temporarily.
Sent from my GT-I9100 using XDA Premium App

My os is at 79% i have no idea whats going on? but i am running launcher pro plus?

OK. So now we have identified an "issue".
Could you guys post juiceplotter logs while phone is asleep and draining, and while in use?
For asleep, i mean literally not touching it for half an hour. On, just occasional tap to keep screen on.
What we are after is an idea of what is causing system to use the power. Can we compare configurations of push email etc, to see if anything differs?
Are we rooted? Etc

{
"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"
}
this is a screen print of my usage.
How do you do the log thing ?
http://imageshack.us/photo/my-images/59/sc20110509160954.jpg/

pulser_g2 said:
OK. So now we have identified an "issue".
Could you guys post juiceplotter logs while phone is asleep and draining, and while in use?
For asleep, i mean literally not touching it for half an hour. On, just occasional tap to keep screen on.
What we are after is an idea of what is causing system to use the power. Can we compare configurations of push email etc, to see if anything differs?
Are we rooted? Etc
Click to expand...
Click to collapse
Hi mate,
I rooted my phone yesterday, but I don't think that's a cause as it was just as bad before. In fact I rooted it just so I could freeze some apps
At the moment, I only have my google account set to sync (calendar, mail, contacts), and I have gmail pushing through emails.
All the stock Samsung apps are frozen. No widgets are running (I'm trying to run it fairly barebones to see how long I can get out of it).
I don't have juiceplotter installed, I'll look into that. I do have Watchdog though, and from all the other threads on this issue the problem seems to be the Suspend process (confirmed by a Google employee).
I don't think there's much we can do aside from wait for a fix. The problem appears to have been around since at least September last year.

I had this the first few days I had the phone, my battery was being wiped out in hours.
I formatted both my mem cards and hard reset. Since then my battey life has been amazing (got through the whole day yesterday only using 25% battery), and os use has dropped to about 18% (still a bit high but better than 40%).

Same issue here, both new flashed roms and my own slim roms suffer from same issue. I have a look tonight if i can find any solution.

simonk83 said:
Hi mate,
I rooted my phone yesterday, but I don't think that's a cause as it was just as bad before. In fact I rooted it just so I could freeze some apps
At the moment, I only have my google account set to sync (calendar, mail, contacts), and I have gmail pushing through emails.
All the stock Samsung apps are frozen. No widgets are running (I'm trying to run it fairly barebones to see how long I can get out of it).
I don't have juiceplotter installed, I'll look into that. I do have Watchdog though, and from all the other threads on this issue the problem seems to be the Suspend process (confirmed by a Google employee).
I don't think there's much we can do aside from wait for a fix. The problem appears to have been around since at least September last year.
Click to expand...
Click to collapse
OK. I will see if I can think of anything, as I remember we fixed a similar issue when popping 2.1 onto it, when some binary was giving us trouble...

Root or no root don not affect this issue. Only time i dont get it: fresh flash of new rom without anything installed.

Same issue here and I rooted freezing load of Apps but still drain
*edit*
It seems to stop drain when using reboot the phone.. not yet confirmed just a speculation... Btw these processes eat a lot of battery never got these problems on sgs1 custom gingers rom
Sent from my GT-I9100 using Tapatalk

Seem that ginger on SGS 2 has this bug present:
http://phandroid.com/2011/03/04/android-2-3-3-gingerbread-update-killing-nexus-one-battery-life/

Did anyone tried this? I had a similar issue with Gingerbread on SGS1 and it was fixed after clearing the data for System Update.
http://forum.xda-developers.com/showthread.php?t=1021711

Haven't encountered the problem yet with pretty heavy use plus a few resets. It's probably a specific app or settings that you're turning on/using after each hard reset that causes it.
I'm still on the original firmware though, haven't flashed a new one yet. Might be related.

this is not universal, i don't have this problem. sgs 2 rooted with insecure kernel by chainfire.

*subscribing*
I also have the same drain issue. I have the S2 setup exactly the same way my Captivate was, and the battery life isn't the same.

I got better results after disabling background data in accounts ans sync (settings)
More testing ongoing.

DocRambone said:
I got better results after disabling background data in accounts ans sync (settings)
More testing ongoing.
Click to expand...
Click to collapse
Not really relevant I think - all Android users are going to have background data enabled in accounts and sync. Mine is enabled without the issue, anyway. I am only syncing a single gmail account though.
Have you tried what the linked thread recommends - going into manage applications and clearing data for the update system? You might want to try clearing data for all of the android system tasks.

RyanZA said:
Not really relevant I think - all Android users are going to have background data enabled in accounts and sync. Mine is enabled without the issue, anyway. I am only syncing a single gmail account though.
Click to expand...
Click to collapse
Yes, but this 2.3.3 bug eat 5-10% battery/h in idle!... so all solutions is good.
I tried a number of "solutions", none helped. The background data seems to help

MaelstromXC said:
Did anyone tried this? I had a similar issue with Gingerbread on SGS1 and it was fixed after clearing the data for System Update.
http://forum.xda-developers.com/showthread.php?t=1021711
Click to expand...
Click to collapse
I just tried this, gonna charge to 100% then unplug it and let juiceplotter run to see what happens. Also I have the Samsung account app frozen.

[Guide] How to Keep Android System Drain Minimal - Battery Life Boost

Good Day all,
I have benefitted greatly from Google and XDA. So I thought I would provide a consolidated way of saving our battery's grace from Android System demonic drain.
I am running Euphoria with Furnace, and I had loads of Gapps installed.
I tried multiple attempts over a 3 days period and did many researches back and forth. And it came down to these few main culprits:
1. Android Location Services
2. Google Play Services
3. Qualcomm Location Services
4. Google Now Launcher
5. Unwanted Sync
Tools I have used to assist in this matter.
1. Disable Service - here
2. Greenify
3. Privacy Guard (should be in built in most custom roms)
4. Titanium Backup
Basically the highest causing drain came from Google Play Services and Qualcomm Location Services. These items persistently wakes the phone up and runs on the background. Using greenify on there further cause issues as greenify tries to hibernate these services over and over again, making this a self-made draining routine.
I followed this thread on Google Play Services drain fix and used the Privacy Guard to perform those tricks. I ran through ALL Google Related Apps and as long as "Keep Awake", "Wake up" or "Auto Start" is enabled, I disabled them. I also look through apps I suspect were waking phone up by looking at the last activation of those events (Keep Awake, Wake Up, Auto Start).
Next I followed this thread on Guide to disable google play internal services using Disable Service app. I also took the opportunity to look at both 3rd party apps and system apps to see if there are services that could be disabled. I disabled Apex Notifier as I realize I didn't needed its service.
Then the next sneaky culprit was the Qualcomm Location Services. Even though I froze them with Titanium Backup, they persist in the system. So making a backup of them, I uninstalled them completely. Hasn't caused me any issue with GPS or Maps. They are namely, com.qualcomm.location and com.qualcomm.services.location. Both appeared as LocationServices 1.0 on Titanium Backup.
I went ahead to Greenify many Google Apps, namely Google App, Google Play Store, Google Services Framework, Google+. I also Greenify many apps that Greenify suggested would slow system down or appear to run in the background which I have no use for.
Lastly I uninstalled Google Now Launcher as it was persistently coming up as alternative home launcher even though I froze it. And I also went through settings of apps to make sure sync were turn off. I only kept Calender and Contacts and Gmail Sync on.
Now I have reduced Android System from 34% to 2% and increased my SOT from 2++ hours to 4++ hours at least. Not an out of earth SOT, but I believe that's decent.
Hope I helped and I wish you all the best in your endeavour to reduce Android System Drain. Cheers.

Thanks bro
Will try and give feedback asap

Suscribed, Rated, and Thanked.
I didn't had time to do any research on this, and this thread appeared on the right time.
Thanks

Paradoxxx said:
Suscribed, Rated, and Thanked.
I didn't had time to do any research on this, and this thread appeared on the right time.
Thanks
Click to expand...
Click to collapse
metuncc said:
Will try and give feedback asap
Click to expand...
Click to collapse
Your feedbacks will be appreciated. It works for me and I hope it works for you. And hopefully help many others that face our problem. Cheers

I can't seem to find App Ops anywhere..
Edit: found it by the name "Access lock" but there is no google play services in there..

bestest609 said:
I can't seem to find App Ops anywhere..
Edit: found it by the name "Access lock" but there is no google play services in there..
Click to expand...
Click to collapse
It should be found in settings page, "Privacy".

I know that this guide is meant for CM based ROMs but I said to myself "ehh, what the hell" and I tried it on my Cloudy 2.2 and the results were horrible. Had to fully charge my device twice in order to go through 22 hours and a total of 2h of screen on time which consisted mostly of browsing and messaging. Wakelock Detector told me that the device was mostly asleep and everything was normal in the Batter Usage menu. Usually I get around 18-20h on a full charge with 2,5-3h SoT. Maybe the locations tweeks were not liked by my Tasker app and caused a huge battery drain, although it didn't appear that much as a wakelock trigger.
I am wondering if the problem was caused by Tasker or the stock ROM itself, but badly I do not have the time now to tweak around and I am reverting back to my previous configuration.

steelclaw said:
I know that this guide is meant for CM based ROMs but I said to myself "ehh, what the hell" and I tried it on my Cloudy 2.2 and the results were horrible. Had to fully charge my device twice in order to go through 22 hours and a total of 2h of screen on time which consisted mostly of browsing and messaging. Wakelock Detector told me that the device was mostly asleep and everything was normal in the Batter Usage menu. Usually I get around 18-20h on a full charge with 2,5-3h SoT. Maybe the locations tweeks were not liked by my Tasker app and caused a huge battery drain, although it didn't appear that much as a wakelock trigger.
I am wondering if the problem was caused by Tasker or the stock ROM itself, but badly I do not have the time now to tweak around and I am reverting back to my previous configuration.
Click to expand...
Click to collapse
Try using GSam battery monitor to find out the real culprit. I used that to boil down to the final two irritants - Qualcomm LocationServices.

Really enjoying the app.
Here are the screenshots:
https://www.dropbox.com/sc/fvzvyvdsfqr1e89/AABeH-BwUHKOjpqnXaFcATbaa

steelclaw said:
Really enjoying the app.
Here are the screenshots:
https://www.dropbox.com/sc/fvzvyvdsfqr1e89/AABeH-BwUHKOjpqnXaFcATbaa
Click to expand...
Click to collapse
Kernel OS issue I am not too sure what issues are they. The issues I had was high Android OS drain.

@JokerAce my friend ...nice to see you posting useful advice ....gonna grab it ...especially qualcomm service....thanks mate
/LG-G3/d-855/16Gb/Titanium Black/

m1trand1r said:
@JokerAce my friend ...nice to see you posting useful advice ....gonna grab it ...especially qualcomm service....thanks mate
/LG-G3/d-855/16Gb/Titanium Black/
Click to expand...
Click to collapse
Thanks mate )

Ho to get your battery life back.

Dear OP2 friends,
HUGE DISCLAIMER:
Below setup works for MY use and needs. If you are like me it will work for you too, if not go find information somewhere else and don't complain "I cannot get the same results" or things like that. It takes common sense and experience to achieve and understand below info. If you don't have common sense, I pity you, if you don't have experience it's OK. If you are polite and follow the XDA rules I don't mind answering your well structured questions, and maybe others don't mind too, there are a lot more experienced people on XDA than me.
If your question is related to any of the apps/threads mentioned below, please go to that (app) thread, that's why I have put the info right there, one click away.
battery life is something we all want to be endless, well we can't have that, but at least we can improve it from a certain point.
This is what I have been doing for the past weeks and the results are incredible, that's why I decided to share them.
First of all sharing this information is ambiguous because it's somewhat device and user dependent especially how people use it and what apps are installed.
I know that but I believe with the right approach you can get the same results as me, hopefully even better, on the OP2 and possibly other device as well.
I have 148 apps installed at the moment and sometimes even more than 200. If you control your apps properly there is no limit to the amount of apps installed related to battery life.
There are numerous threads on improving battery life out there already so please check out those threads first.
Extreme battery threads:
https://forum.xda-developers.com/android/general/guide-extreme-battery-life-t3095884
https://forum.xda-developers.com/android/general/guide-0-0-hour-idle-battery-drain-stock-t2973588
You can also post your BBS logs there, please don't do that in this thread as I will not investigate them.
Most useful info is already out there so I would appreciate it to go look there first before cluttering this thread. If not I will close this thread.
Let's get started:
improving battery life on Android is (unfortunately) always a combination of things, there is no 1-push button (yet).
In this case I use the following:
- privacy guard (baked in almost any Nougat ROM)
- custom kernel (I use Boeffla: original thread here, I use the Linaro version from ZaneZam)
- Greenify (original thread here)
- Wakelock blocker (built in ROM) + WakeBlock app (optional, original thread here)
- Alarm Blocker (built in ROM)
- Doze apps
- BetterBatteryStats (for finding your excessive wakelocks, thread here)
Obviously you have to be rooted to implement all of this.
The ROM of my choice is RR unofficial.
I like it because of the functionality and features but I believe any ROM with the above features should be able to achieve the same results.
Speaking of results, below screenshots are from my last cycle before writing this thread. One charge got me almost through 3 full days (66 hours).
I fully charged in the afternoon, got through the evening and the first night, then got through the full second day and night, then got through another full day and night and charged only again in the next morning.
If your still following, those are 66 hours of straight juice...
EXPLANATION: There is ALWAYS a tradeoff between SOT (screen on time) and how long your battery will last in one cycle. On my below cycle you can see that I have "only" 4 hours of SOT but almost 3 days of battery life. That is light usage.
If I would use my phone more (more SOT) the battery life cycle would have been significantly shorter. If you complain to me that you "only" have 24hrs of battery life but you show me a SOT of 7-8 hours, I would consider that great battery life! It's all relative...
I have never used one battery cycle from 100% to 0% in one go so I don't know the max SOT I would get with my setup. I would guess around 6.5-9 hours depending on the activity (gaming <=> ebook reading, mobile data <=> wifi, ...). It's all relative...
The screenshots in the bottom of the post might bring clarity for you.
See the following posts for more explanation.
Thanks to:
@nicesoni_ash
@Lord Boeffla
@ZaneZam
@oasisfeng @GioBozza @chamonix
@ssrij @The Peterle

Privacy Guard:
*setting things up wrong without thinking straight can delay notifications or not execute certain tasks*
I enable this for all user apps because I don't want any app keeping the system awake. I even have this enabled for some system apps like:
Calendar storage
Google play services
Google play store
Google app
cLock
I mostly disable all locations (if it's not a location dependent app), keep awake, run in background and even start at boot (if the app doesn't need to start on boot) toggles.
Again, use your common sense to figure out if a app needs to run on boot (for example, youtube doesn't need to run on boot, tasker does for starting up along with the system boot).
obviously some system apps need to run in the background for example cLock or calendar storage otherwise your weather and calendar will not update...
You can also configure all the apps on a gradual basis. You let the privacy guard as is on clean install an if you see excessive wakelocks from a certain app, you start blocking it one by one.

Custom kernel:
I use Boeffla config app with always the latest version of his kernel compiled by ZaneZam (Linaro 6 version).
The latest as of the time writing this thread is LOS14.1-beta14 in combination with config app 2.4.34.
I use profile IMPULSE TUNED V3.0, no lags, good performance and crazy battery life.
Screenshots of my minor changes, the rest is identical to the stock IMPULSE TUNED V3.0 profile.

Greenify:
*setting things up wrong without thinking straight can delay notifications or not execute certain tasks*
I Greenify a lot of apps, as much as I can basically, even system apps.
I cannot give too much advice on this part so please go to the Greenify thread to ask related questions. For me it's mostly a hit and miss and right now my config is a big hit.
If you want to know if you can Greenify a particular app you can ask me.
Configuration below in screenshots.

Wakelock Blocker (+ WakeBlock app):
*setting things up wrong without thinking straight can delay notifications or not execute certain tasks*
I personally think this feature is essential in getting good battery life so I'm glad it's integrated in the ROM of my choice (since we don't have xposed yet).
In combination with the WakeBlock app it basically works like Amplify on Xposed, but ROM integrated.
This part is the hardest to explain because it's different for most users. On the screenshots below you can find most of my blocked wakelocks (without losing functionality).
The procedure to block wakelocks is the same as all the other parts explained above and below:
Let your system run for some hours/days (essential!).
After that, trough BBS you can find your excessive wakelocks and through wakelock blocker you can block them completely. If you don't want to completely block the wakelocks you can use the WakeBlock app to put a timer like in Amplify for Xposed, for example I want wakelock x to run every 9999 milliseconds....

Alarm blocker:
*setting things up wrong without thinking straight can delay notifications or not execute certain tasks*
Another essential feature for keeping your device under control.
I block a lot of alarms (without losing functionality) so get ready...

Doze apps:
I use Force Doze from the Playstore to put my device in Doze mode as soon as the screen goes off.
Naptime is an alternative but I find it to generate too many wakelocks (sometimes up to 19 per hour).
I might change this app once in a while if there are better alternatives that come up.
Anyway Force Doze will work for now.

reserved. will add some advices.

CounterC said:
Doze apps:
I use Force Doze from the Playstore to put my device in Doze mode as soon as the screen goes off.
Naptime is an alternative but I find it to generate too many wakelocks (sometimes up to 19 per hour).
I might change this app once in a while if there are better alternatives that come up.
Anyway Force Doze will work for now.
Click to expand...
Click to collapse
Lesser wakelocks means not necessarily lesser drain, good example is definitely the very first lines from this Thread of an old friend from galaxy s3 lte times, he implemented microG on his device and achieved lesser wakelocks but no significant impact on his battery life(see here), what I want to point out is that this equation (more wakelocks - more battery drain) isn't so simple unfortunately, even if true for most of the time, regarding to franco's naptime, I personally made very good experience with this app in combination with his custom kernel, I think especially in this combination it's absolutely recommended..
Furthermore some inspiration about battery life a wonderful guide with plenty of useful information, the absolute majority is generally valid, so don't get confused by the i9305 tag...
Sent from my OnePlus 2 using XDA Labs

Sam Nakamura said:
Lesser wakelocks means not necessarily lesser drain, good example is definitely the very first lines from this Thread of an old friend from galaxy s3 lte times, he implemented microG on his device and achieved lesser wakelocks but no significant impact on his battery life(see here), what I want to point out is that this equation (more wakelocks - more battery drain) isn't so simple unfortunately, even if true for most of the time, regarding to franco's naptime, I personally made very good experience with this app in combination with his custom kernel, I think especially in this combination it's absolutely recommended..
Furthermore some inspiration about battery life a wonderful guide with plenty of useful information, the absolute majority is generally valid, so don't get confused by the i9305 tag...
Click to expand...
Click to collapse
Good point Sam, that's why I always say check BBS first if it's actually a wakelock, then treat it properly (disable or time-lapse it).

Overnight drain

does blocking the *alarm* wakelock cause the system to reboot!?

aditya_pan said:
does blocking the *alarm* wakelock cause the system to reboot!?
Click to expand...
Click to collapse
No, not with me.

Guide for hunting down wakelocks and battery drain (No Root)

I've posted this guide on reddit already, but thought it might be useful here as well. A lot of users promote intense usage of package disablers to reduce battery drain, but this is not required to such an insane extend.
---
After experimenting with my S8 for 2-3 months now, I've collected some data and constructed some basic idea on how to fight wakelocks without having to root your device. I'll try to lay down everything here under a few categories.
First of all, I'll say that I tried using my S8 with a package disabler with hundreds of apps and services disabled, and also tried using it with no package disabler at all. I did not see a significant difference. It's too hard to determine if there is one, but I have to note that disabling TOO MUCH can actually hurt your battery usage.
Finally, I settled on using the device with a disabler again, only this time I disabled things strategically after some investigation with battery stats measurement and wakelock detection.
The apps I used were:
BK Package Disabler + BK Plugin
Better Battery Stats or GSam
These are paid apps, but I am happy with what they can do. BK can be replaced with another disabler (as long as it gives you control over individual package services) and BBS can be replaced with GSam Battery Stats, which is free.
General tips on using these apps:
BBS will require your device to have USB debugging enabled, so that you can connect the phone to your PC and unlock the permission manually. You need an ADB command prompt to do that, and you need to give it the following permission with the following command (read more here).
Code:
adb -d shell pm grant com.gsamlabs.bbm android.permission.BATTERY_STATS
You can use BBS if you do not restart your phone while testing. If you do, it will wipe stats and likely not activate for another few hours, or until you charge again.
You should be using BBS to observe Deep Sleep percentage in the Summary tab (which should be above 95% when the phone is left in idle mode for hours), and Partial Wakelocks to find individual wakelocks that come from apps. Kernel wakelocks are hardly ever something you can do anything about and shouldn't be observed too much, no point in that unless you are rooted. The highest kernel wakelocks should be the ones related to your screen-on time - they are easy to point out as their awake time equals your screen on time.
BK Package disabler, or any other disabler for that matter, WILL require admin privileges to work on your device, so keep that in mind.
BK Package disabler should be used in tandem with BBS, only once you have found wakelocks and/or managed to understand which service is the actual cause. I will give examples below.
---
So, let's start.
Google Play Services battery drain
This one really sucks and it seems to plague any Android device at some point. Most often than not, this problem will occur after you do a system update without doing a factory reset. Last time it occurred on my S8 was right after I did the AQI7 update, after having very good idle drain previous to updating.
What to do in this case?
Log out of your Google account(s).
Enroll for Google Play Services BETA. To enroll, scroll down on this page and find the beta button OR Find Play services in your App list, and do "Uninstall updates", then update it right after that.
Turn off your phone and then boot it in recovery mode (Hold volume up + bixby key, then also hold power button) and select Wipe Cache - This will erase Dalvik cache.
Reboot the phone and delete system cache from the Storage settings
Log back into your Google account(s).
Charge your device and then observe idle drain overnight, or over a few hours.
If this process does not help your problem at all, you might have to do a factory reset to cure the services issue, or the problem might be related to something else, like a google service from some particular app. Use BBS to investigate wakelocks as you check your idle drain.
If this process helps you, but you see the issue again in future without changing anything, try going to the Developer Settings, look for active processes, and find Google Play services. Open them and then hit 'STOP' for each of their sub-services. Don't worry, they will restart on their own. After doing this, you might reboot your phone as well. Last time this little chore helped me out and the drain went away.
---
General Wakelocks
It's normal to get wakelocks even on a perfect system, but BBS will show exact percentages on each of them. Normal wakelocks usually show 0-1% of awake time for a session. If you start seeing numbers like 3%, 7% , 9%, or more, on some specific wakelock, then there is definitely a problem.
Wakelock battery drain will usually appear in your Android System/OS drain stats, so it's impossible to determine without an app.
The most common wakelocks for me are:
- *net_scheduler* wakelock - this one can be related to your WiFi connection. In order to fix it you should have access to the router's settings, and that is not always possible. If you do have access, you can try changing the Wi-Fi channel (choose channel based on Channel Width, for example 40Hz width on 2.4GHz network could use channel 11), and Beacon Interval (set the interval to the highest possible). I found this helped in my case. This wakelock can also be related to google play services - check the previous part of the post on how to possibly resolve the GPS issue. Also, the wakelock can appear under the icons of other apps, when there is little you can do to track down exactly why it happens.
- *com.google.android.gms.measurement* wakelock - this is a VERY common one in my case, and BBS usually shows it comes from Google Services, but always has a specific app icon next to it. In order to resolve this wakelock I had to do the following:
Open my package disabler and go through each app that might be using background data, or the app that is shown next to that wakelock, and then open their lists of individual services. I searched for:
1. AppMeasurementService
2. AppMeasurementJobService
3. Firebase... any service starting with Firebase in its name
These services are related to apps collecting some usage statistics on how you use them and sending them back somewhere, probably the app vendors. You do not need them for any app to be functional, and many apps don't have them. For some reason they can keep your device awake for long periods of time. I disabled them on ALL apps I could find them in and it seemed to resolve a lot of wakelocks after investigating the next following days. This process was probably one of the things that helped me the most with hunting down daily wakelocks as the drain is very stable for me now. For example, today I came back from work with 20 hours of phone usage since charge, almost 1h of SoT and 75% battery left. Other days, I have come back from home with 10 hours of usage, 1.5h of SoT and ~60%. I've seen a lot of improvement lately after doing all of the suggested things and keeping Google services at bay in parallel to that.
---
Bluetooth wakelock
This one was the most inexplicable to me. I never use Bluetooth, or turn it ON for any reason at all. I could not understand why the wakelock occurs.
Ultimately, my solution was to completely disable the Bluetooth System package and all services in it through the BK disabler.
I know this solution doesn't sound good to anyone, but at the same time it might be useful if you also do not use BT at all.
I plan to buy BT headphones in the near future and will be re-enabling this, and at that point I will start observing the behavior of the package once again and maybe turn it on/off at will if the wakelock re-appears too often.
---
Other wakelocks
The general rule here still applies. First, you record your usage with BBS. Then you note down which wakelocks appear on top, and google them as best as you can. Search is your friend here, as the wakelocks are endless and it is impossible for me to list them all and give solutions for even a small percentage of them. Sometimes you might get lucky and find an easy fix. In other times, there will be no easy explanation, or no explanation at all. Such is the nature of Android.
In some cases the wakelocks might be specific services that you can disable for specific apps. In other cases, they will be too general and it will be unclear why they occur. For example, I sometimes get *net_scheduler* wakelock with the Viber app, that can last for 20-30 minutes at random times, and still have not found a way to resolve that, other than uninstalling Viber completely (which is not a bad idea but sadly some of my contacts insist on using that crap. Telegram is your friend).
---
General Tips:
Use an AMOLED black theme. System theme from Samsung Themes (!) and individual app themes / status bar from Substratum. Do not use overlays for the system UNLESS you do not use samsung themes. I found out that Samsung themes do a better job at painting all system apps black, while some substratum overlays miss a few things. It will also be a LOT less painful to update overlays as you uninstall all of them and re-install them, because using Samsung for the system means less packages from Substratum to be installed. REMEMBER to always uninstall system overlays and statusbar overlays (ALL overlays if you want to be super safe) before doing a system update! Otherwise you can soft-brick your device.
Use auto-brightness and make sure to make it as low as you are comfortable with in rooms that you stay often in (like your own room, your office room, etc). Smart auto-brightness will remember you preference and you will hardly ever use more brightness than you need.
Turn off notifications for any apps that are not essential to you. In fact, I have turned off everything except Gmail, because I have a habit of checking my phone very often and do not miss out on anything, while notifications have become a bit annoying to me anyway.
Put almost all of your apps to 'Always Sleeping' in the device optimization app.
Do NOT always sleep apps that you need to be awake, like your Messaging app, Home Launcher, utility stuff like Navbar Apps, Keyboard. Put those in the 'Unmonitored' category instead.
DE-OPTIMIZE your fingerprint scanner from battery optimization settings if you are having issues with waking up the device with it. It is optimized by default if I remember correctly.
If you are feeling BRAVE, you can do your own investigation for each app that you use often to look for any services that might look like Analytics services. Experiment at your own risk, but generally such services are always a benefit to turn OFF for both battery and privacy reasons.
---
Overall, that's it. If I remember something, I will update the thread. Hopefully this can help someone.
In my personal results, I've managed to achieve a 0.3% idle drain per hour with Wi-Fi active during a test of 12 hours of standby. As visible in the screenshot, the Wi-Fi signal is not even perfect.
Here is an example of idle drain with about 1h 10m of SoT at the time it was taken.
---
Feel free to use this guide in conjunction with Neomancr's general battery and performance tuning guide

Thanks!

magarto said:
Thanks!
Click to expand...
Click to collapse
No problem!

This should be on top! Thanks a lot!
The "Service Disabler" functionality has been removed from the latest app version due to Google Play policies.
Fortunately we can find the previous apk version in the developers website.
https://kunkunsoft.wordpress.com/news_2/
Cheers!

hey thanks a ton for this article! My battery is horrible...REALLY. 2 h ost...I've just completed the first part. please explaind better what do you mean with "sign out from Google accounts" step by step. and in my case BBS was not adb enabled...I was not able to see wakelocks. the command explained here https://alexus.org/howto/better-battery-stats-no-root/amp (the google play store version) granted permissions for me. maybe you want to update the guide! I'll let you know how it goes.
cheers

@brokich
Could you please point us exactly to what are the main apps with AppMeasurement and Firebase services?
Until now I have found only the Google play store app.
Thanks for your great guide.

Thanks for the guide. Starting to debug battery issues. Meanwhile tried setting up the black theme. What do you mean by installing only Samsung theme? Do you mean a specific theme made by Samsung electronics or any black theme from Samsung theme market?

Here are the correct adb commands to BBS, as shown in the app in first start:
adb -d shell pm grant com.asksven.betterbatterystats android.permission.BATTERY_STATS
adb -d shell pm grant com.asksven.betterbatterystats android.permission.DUMP
adb -d shell pm grant com.asksven.betterbatterystats android.permission.PACKAGE_USAGE_STATS