Ayo mates.
So who doesn't have battery problems? Probably everyone has. Even if you don't you'd want more ? huh ?
So after owning the phone for almost 3 months I had serious variations in battery life from 10 hours screen on to 7 hours screen on (*cough* 4.1.2) and back to 10 hours with xxdmb6 (YEAH!)
Also the screen off consumption.
So I am gonna talk about wakelocks in this thread. So what can use battery when you aren't using your phone... can also use the battery when you are using it. So fixes or possible fixes should improve the total battery life as well.
This thread is divided into 3 parts - basic tips , wakelock fixes and advanced fixes.
Install BetterBatteryStats. This is gonna monitor the wakelocks and the elements that drain the battery.
Tip 1 - (Install CurrentWidget) If you keep charging the battery even after it has reached 100% you will see that the battery continues to accept charge. This is true. If you charge the battery till it stops accepting power(by monitoring it through currentwidget) you will see that 100% lasts for a long time. i mean that suppose your phone uses 1% battery per 10 minutes, now if you just unplug and start using the phone, it will stay at 100% for a long time.
But this may even damage your battery. I am not sure. I do it considering how much technology has advanced.
Tip 2 - So from wanam's thread -
wanam said:
Disable auto sync for accounts if you don't need it
Disable GPS (and wifi gps) when not in use
Disable auto backup of Google account
Set brightness level to automatic
Disable motion if you don't use it
Check your apps settings and disable useless background sync
Disable useless animations
Click to expand...
Click to collapse
List of general Wakelocks -
PowerManagerService - It is a sum up of partial wakelocks.
MultiPDP - This indicates a high network usage(2g/3g/4g).
AlarmManager -
AlarmManager provides access to the system alarm services. These allow you to schedule an application to be run at some point in the future. When an alarm goes off, the Intent that had been registered for it is broadcast by the system, automatically starting the target application if it is not already running. Registered alarms are retained while the device is asleep (and can optionally wake the device up if they go off during that time), but will be cleared if it is turned off and rebooted. The Alarm Manager holds a CPU wake lock as long as the alarm receiver's onReceive() method is executing. This guarantees that the phone will not sleep until you have finished handling the broadcast.
Click to expand...
Click to collapse
These are the findings of asksven, so have been quoted. So it is a sum up of different wakelocks again
AudioOut_2 - When apps run in the background that use sounds, this wakelock is always there.
deleted_wake_locks - A wakelock that is no more, generally when you turn wifi or data or gps on and off. But it still reflects wifi wakelock. You can sum it up as a wifi wakelock and some other wakelocks.
network-location - This is a gps wakelock.
wlan_rx - Wifi wakelock
wlan_wake - Wifi wakelock
mediaserver - when something uses media files or may even when you play heavy games like real racing 3 which uses data on internal sd card
l2_hsic - A possible explanation is unplugging the charger while phone is asleep.
I have attached a pic. You can see the difference
Wakelock Fixes
AudioOut_2 - AudioOut_2 is a major wakelock on many devices. The solution is simple. Before turning the screen off. remove all recent apps and in task manager , go to ram tab and hit clear memory. Then close task manager and swipe it away from recent apps as well. Then lock the phone. Alternatively you can download advanced task killer. (Viber seems to cause this on many devices.)
MediaServer - Flash the attached fix via a custom recovery. Someone posted this and said that he got from alliance rom ota app. I asked the Dev and he said that I can use it but it may cause a boot loop. So keep nandroid a ready. Credits go to comnam90.
Other fixes could be to download Rescan Media Root. This app fixes wakelock but it might still come up sometime.
If you are comfortable with decompiling try this.
l2_hsic - This wakelock is incorrigible. But possible fixes are in thread. I will jot down what works for me.
NetworkLocation/SignalCollector Hierarchy - Many wakelocks happen due to this maps app. This is because maps app try to update the location of the device. Modify the settings according to the image attached. But better is to disable all location services. This will also decrease AlarmManager wakelock.
But if you really don't use maps then best is to Freeze local app, maps app, navigation app. This wouldn't harm the phone as they can also be downloaded from play store which means android os can cope without it.
Processes - There are many user apps which are a necessity but eat up the battery. We can't freeze it nor uninstall it due to the need. What can we do about 'em ? This is where Greenify comes in. Don't let the uber simple UI fool you. The app is simple and self explanatory. I have greenified almost all the apps and this app doesn't eat up your battery !
I will be adding more as I find more...
Advanced Fixes
These aren't very advanced if you know what you are doing.
Try another kernel. (like perseus, uneak, redpill). I find almost similar results but it may vary as we move to the next parts
Undervolt(CPU). Believe me it will help. You should start off by reducing each voltage by 25m for each step. This requires a custom kernel and a compatible app. STweaks for redpill or perseus or uNeak Engine for uneak kernel.
Do stress tests after reducing value. It is recommended not to go below 800mV.
Thanks!
One of the best things I did to save battery is to remove Facebook and Viber.
Now I'm trying to Greenify Facebook. I hope it will not do any wake locks.
Nice article Utkarsh.
Those are general wakelocks, but there are others as well, like in the attached pic.
Btw- What's that wakelockfix.zip?
'Swyped' from my GT-N7100
jujuburi said:
Nice article Utkarsh.
Those are general wakelocks, but there are others as well, like in the attached pic.
Btw- What's that wakelockfix.zip?
'Swyped' from my GT-N7100
Click to expand...
Click to collapse
That wakelock is generic with exchange services. Remove it to get rid of it.
Well that will probably fix media server. It did for me but I will see if it comes up again.
Sent from my GT-N7100
UtkarshGupta said:
That wakelock is generic with exchange services. Remove it to get rid of it.
Well that will probably fix media server. It did for me but I will see if it comes up again.
Sent from my GT-N7100
Click to expand...
Click to collapse
Yeah, I know. But I use that on daily purpose. No question of removing it
'Swyped' from my GT-N7100
jujuburi said:
Yeah, I know. But I use that on daily purpose. No question of removing it
'Swyped' from my GT-N7100
Click to expand...
Click to collapse
Well you gotta try hampering with update settings. I am a student and not in business so email delay is not gonna hurt me at all.
It would hurt business men(that's what I derive of you) or someone whose most work is done through mails.
Nice thread, but I'd like to chime in that wakelocks aren't necessarily an absolute evil. You will always have some wakelocks, and it's supposed to be that way. Network, wifi, location services and some apps won't work properly without being able to wake the phone from time to time. It's when these wakelocks sum up to a considerable ratio of your uptime that you should begin to worry.
Might I also suggest you add greenify to your list of countermeasures.
Sent from my GT-N7100 using Tapatalk 2
UtkarshGupta said:
Undervolt. Believe me it will help. You should start off by reducing each voltage by 25m for each step. This requires a custom kernel and a compatible app. STweaks for redpill or perseus or uNeak Engine for uneak kernel.
Do stress tests after reducing value. It is recommended not to go below 900mV.
Click to expand...
Click to collapse
Is this for cpu or gpu? Thanks for the guide.
gyxter said:
Is this for cpu or gpu? Thanks for the guide.
Click to expand...
Click to collapse
Thanks should have mentioned. It is CPU.
Sent from my GT-N7100
adytum said:
Nice thread, but I'd like to chime in that wakelocks aren't necessarily an absolute evil. You will always have some wakelocks, and it's supposed to be that way. Network, wifi, location services and some apps won't work properly without being able to wake the phone from time to time. It's when these wakelocks sum up to a considerable ratio of your uptime that you should begin to worry.
Might I also suggest you add greenify to your list of countermeasures.
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
Greenify is already there. Check in 2nd post processes part.
Sent from my GT-N7100
UtkarshGupta said:
These aren't very advanced if you know what you are doing.
Try another kernel. (like perseus, uneak, redpill). I find almost similar results but it may vary as we move to the next parts
Undervolt(CPU). Believe me it will help. You should start off by reducing each voltage by 25m for each step. This requires a custom kernel and a compatible app. STweaks for redpill or perseus or uNeak Engine for uneak kernel.
Do stress tests after reducing value. It is recommended not to go below 900mV.
Click to expand...
Click to collapse
Hi, just one question, why not go below 900mV? Is there any reason for that? I´ve got my Note 2 uVd to these values (762, 775, 800, 825, 850, 875, 925, 950, 1000, 1050, 1075, 1125, 1150, 1175, 1250) for the frequencies from 200Mhz to 1600Mhz, I don´t think it wil harm it as I´ve been running these settings with RedPill Kernel and STweaks app for a couple of months now and I haven´t had any freezes at all or any issues, could you explain why it´s not recommended to go below 900mV? Is it just for the different tolerance to uV every chip has? Thank you anyway for your marvelous post and for the greenify app, looks promising, I´ll report how it goes since I´ve just started using it today, thanks.
thecrab93 said:
Hi, just one question, why not go below 900mV? Is there any reason for that? I´ve got my Note 2 uVd to these values (762, 775, 800, 825, 850, 875, 925, 950, 1000, 1050, 1075, 1125, 1150, 1175, 1250) for the frequencies from 200Mhz to 1600Mhz, I don´t think it wil harm it as I´ve been running these settings with RedPill Kernel and STweaks app for a couple of months now and I haven´t had any freezes at all or any issues, could you explain why it´s not recommended to go below 900mV? Is it just for the different tolerance to uV every chip has? Thank you anyway for your marvelous post and for the greenify app, looks promising, I´ll report how it goes since I´ve just started using it today, thanks.
Click to expand...
Click to collapse
Well I read somewhere. But I will update the op.
Sent from my GT-N7100
Deep sleep results....
Sent from my GT-N7100
how about just use the power-saving mode...
thanks for guide...
fly2dheaven said:
thanks for guide...
Click to expand...
Click to collapse
Welcome but plz use thanks button. It isn't about no of thanks but it helps prevent clogging of threads
Sent from my GT-N7100
Audio out 2 for me has been causing an annoying battery drain. Turns out viber is causing it for me. Yesterday it was the best part of two hours.
Today I quarantined viber and my audio out 2 dropped to 6 seconds after the phone being on for 6 hours. Half an hour ago I re started viber and my wakelock now reads 22 minutes. So I have now uninstalled viber.
How this info helps others.
arjunr24724 said:
how about just use the power-saving mode...
Click to expand...
Click to collapse
Well this doesn't hit performance.
Sent from my GT-N7100
Related
I installed Spare Parts and saw that my phone was never sleeping, even though it was on standby all the time.
This was caused by the location by antenna feature.
Ever since i unchecked that feature i've had around 50-60 hours of uptime, with a few calls and a lot of texts.
hope this helps alot others
With the new firmware the problem of battery dissapears completely
There is a known issue with network location detection in android 1.6. I had the same issue with my galaxy and it was solved. Now that we have root, we can hopefully do the same.
Also, br aware that I have found spare parts to actually stop the phone from sleeping, as well as tapatalk. I suggest rebooting after using either program.
-------------------------------------
Sent via the XDA Tapatalk App
adrianoftyriel said:
There is a known issue with network location detection in android 1.6. I had the same issue with my galaxy and it was solved. Now that we have root, we can hopefully do the same.
Also, br aware that I have found spare parts to actually stop the phone from sleeping, as well as tapatalk. I suggest rebooting after using either program.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Actually that issue is fixed in the latest update so it's already fixed without needing root.
Which firmware? I know I'm still experiencing it.
RBA020 solved the battery issues for me.
Where in spare parts does it show you if your phone has been sleeping?
you don't need spare parts. Just dial *#*#4636#*#* and click battery history and then the running bar.
Sent from my X10a using XDA App
Inebriatef said:
This was caused by the location by antenna feature.
Click to expand...
Click to collapse
I hope this means that under Location, you had Wireless Networks and Assisted GPS enabled.
One question tho... how did you isolate this feature as the one that was keeping the system awake?
I just found that my phone has been running most of the time, I see Running at 100% under Battery History. Then I select Partial Wake usage and see Android System has the largest share. But what part of Android System? how does one get to know?
I know from having a Samsung galaxy and being part of the androidforums community that was going nuts until Simone found a bug report with Google saying that network location was stopping devices from sleeping. We had root so a Dev applied a patch to services.odex and voila! Phones were napping again.
Sent from my X10a using XDA App
adrianoftyriel said:
I know from having a Samsung galaxy and being part of the androidforums community that was going nuts until Simone found a bug report with Google saying that network location was stopping devices from sleeping. We had root so a Dev applied a patch to services.odex and voila! Phones were napping again.
Sent from my X10a using XDA App
Click to expand...
Click to collapse
Hmm... time to give this a try... so is it just Wireless Network or also AGPS that causes this problem?
I hope I can still leave GPS turned on?
EDIT:
adrianoftyriel said:
Sent from my X10a using XDA App
Click to expand...
Click to collapse
Didn't know that there was an XDA App till I saw your sig. Looks like its worth a try since its free!!
Update after turning location off completely
Well first run with all location methods disabled (I can still enable GPS quickly via a widget when I need to use it)... the battery performance is up phenomenally!!
I charged fully before going to bed last night, then kept the phone unplugged... woke up and found the battery was at 97%. This has never happened to me.
Ok, one thing tho, I use Juice Defender with night time schedule, so my wifi and 3G were off during most of the night. Anyways, its been around 3 hours since I woke up, and I've been using the phone on and off to do some browsing.
The battery is now at 93%.
I do not use any other aid other than Juice Defender... no task killers, no startup editors. Will update on how the rest of the day progresses.
EDIT: my thanks to Inebriatef and adrianoftyriel for pointing this out.
j4mm3r said:
I hope this means that under Location, you had Wireless Networks and Assisted GPS enabled.
One question tho... how did you isolate this feature as the one that was keeping the system awake?
I just found that my phone has been running most of the time, I see Running at 100% under Battery History. Then I select Partial Wake usage and see Android System has the largest share. But what part of Android System? how does one get to know?
Click to expand...
Click to collapse
I too would like to hear a bit more. Could the OP please elaborate?
I'm running the latest FW and although my battery life increased exponentially, I find that it's not going to sleep anymore! I had close to 50 hours battery life and now I repeat everything to get just under 20 hours.
I don't use task killers and crap anymore, just before I put my phone away. If I don't, I have a trillion programs running with like 40mb of RAM free. Although I understand this is Linux based, these programs are RUNNING and not idle. All my **** is draining the battery again after a clean reinstall of everything. What a bummer.
bongd said:
I too would like to hear a bit more. Could the OP please elaborate?
I'm running the latest FW and although my battery life increased exponentially, I find that it's not going to sleep anymore! I had close to 50 hours battery life and now I repeat everything to get just under 20 hours.
I don't use task killers and crap anymore, just before I put my phone away. If I don't, I have a trillion programs running with like 40mb of RAM free. Although I understand this is Linux based, these programs are RUNNING and not idle. All my **** is draining the battery again after a clean reinstall of everything. What a bummer.
Click to expand...
Click to collapse
@bongd, by latest FW, do you mean the R2BA020? If yes, then you shouldn't be affected by the problem being reported here. I'm still on R1FB001, which apparently has this Android 1.6 bug related to location.
As in my case, simply by disabling location settings (even though this reports that network location is the culprit, I disabled them all), the phone is now able to suspend itself and basically consume very little battery in standby.
Personally, I dont see any issue with lot of applications running and having little RAM left because I trust the Android system to manage it efficiently. Furthermore, the RAM on these phones is not as fast as what you would see typically on desktop systems, so it actually helps having things around in memory rather than aggressively cleaning it out. Checkout this link to understand a bit more about Android task management features: http://android-developers.blogspot.com/2010/04/multitasking-android-way.html
I suggest you use Spare Parts to isolate your battery drain, there might be some app that is misbehaving and hogging systems resources. Also turning off very frequent updates/refresh intervals in some applications is the way forward.
I found through trial and error that fancy widgets keeps my phone from sleeping.sad cause I really want to use it.
Sent from my X10a using XDA App
j4mm3r said:
@bongd, by latest FW, do you mean the R2BA020? If yes, then you shouldn't be affected by the problem being reported here. I'm still on R1FB001, which apparently has this Android 1.6 bug related to location.
As in my case, simply by disabling location settings (even though this reports that network location is the culprit, I disabled them all), the phone is now able to suspend itself and basically consume very little battery in standby.
Personally, I dont see any issue with lot of applications running and having little RAM left because I trust the Android system to manage it efficiently. Furthermore, the RAM on these phones is not as fast as what you would see typically on desktop systems, so it actually helps having things around in memory rather than aggressively cleaning it out. Checkout this link to understand a bit more about Android task management features: http://android-developers.blogspot.com/2010/04/multitasking-android-way.html
I suggest you use Spare Parts to isolate your battery drain, there might be some app that is misbehaving and hogging systems resources. Also turning off very frequent updates/refresh intervals in some applications is the way forward.
Click to expand...
Click to collapse
Thanks, j4mm3r. I am using R2BA020. It looks like I have some diagnostic troubleshooting to do when I get home.
Sitting here at work charging my phone, it isn't loading craploads of programs anymore. And it seems to be sleeping okay. I'll play around when I have some free time.
Fixed my problem big time
Hey guys,
I just wanted to throw my two cents into the pot.
OK – so after experimenting with Task Killers, Task Managers, Spare Parts, Juice Defender, etc. I came to the conclusion that they (for the most part) did more bad than good. It was getting to the point that I was just starting to accept that “The X10 just has ****ty battery life” end of story.
I also read in a Google released post on the web, that there are a number of reasons that Task Killers, etc. are actually not required to end tasks. Android actually has a fairly intelligent and systematic approach to killing tasks that are not being used. I haven’t used any sort of proprietary battery saver, task ender, startup cleaner, etc. and I’ve been having the best phone performance since I got the headset.
The time now (Eastern Standard) is 3:30pm on Monday. The last time I charged my phone was Saturday evening at 6pm, and currently I am showing 24% battery remaining. Let those numbers do the talking!
My settings are:
Wi-Fi always off unless I am going to be actively using it (browsing)
Using Phone info, I change WCDMA Preferred to GSM Only (enables 2g instead of 3g without disabling data altogether)
GPS always off
Screen settings, brightness, etc. I believe have a much smaller effect than people tend to believe. The SINGLE BIGGEST factors for me, and noticing this huge increase in battery life are:
Settings -> About Phone -> Software Update -> UNCHECK Automatic Search (this constantly searches the market, etc. for app updates and what not)
Cycle power immediately after charging. Once my phone completes its charge, I turn off and then on again.
I hope that some people can enjoy moderately extended battery life as I have. I am SO ecstatic to be at HOUR 43 and still at 20%+
Worth mentioning also that I am on Rogers (Canada) and have not received any updates, so this extended battery life is not a result of a firmware update.
How I Fixed My Batter Life Problem
My Incredible would run dead in about 4 hrs doing nothing. I finally dug into several "task killer" programs and found that about 20 - 30 apps were invisibily running in the background constantly. As soon as I permanently killed them, my battery life went to normal. I can now get about 2 days of normal use on 1 charge. Even a day of pretty heavy use will last almost all day.
So for me, it was all the new apps I installed when I first got the phone that were running in the background. The free "task killer" program was not showing them. I finally found the app called "System Panel." It was the ONLY app that would show me all the "invisible" apps that were still running invisibly in the background and let me kill them. Once I killed them with System Panel, they stayed dead and the free "task killer" program could auto-kill them from them on.
Not sure why the free programs could not see the rogue apps, but my battery life is GREAT now.
Inebriatef said:
I installed Spare Parts and saw that my phone was never sleeping, even though it was on standby all the time.
This was caused by the location by antenna feature.
Ever since i unchecked that feature i've had around 50-60 hours of uptime, with a few calls and a lot of texts.
hope this helps alot others
Click to expand...
Click to collapse
What do you mean caused by the location of the antenna feature?
Where is this option to uncheck this feature.
Thanks dear.
Vatis
I'm running R2BA023 and I am struggling to get a full day from the phone at the moment. It normally lasts around 12 hours and then its flat.
However, I ran the Telenor R2BA020 update and I manage to get a full day with ease.
I have just done a clean install of R2BA023 Generic UK "root" edtion and going to see how I get on. What I did notice before is that the phone was not returning to a idle state.
Hi All,
Running CM7.0.3.1 with Savaged-Zen 2.1.0 BFS kernel. Also using v1 of viperboy's undervolting at -100. There was a time I had stellar battery life (back on an early CM7 nightly and a way earlier version of SZ kernel), but for the life of me I cannot get back to that point. I've been checking spare parts and it is showing k9 and palmary weather with some partial wakelock but it doesn't look too severe from what I can tell, or maybe I'm reading it wrong.
Anyway, here's a view of my battery history. Does all that awake time seem odd? I'm kind of at a loss here for what is going on and how to fix it.
Thanks!
cody_dingo said:
Hi All,
Running CM7.0.3.1 with Savaged-Zen 2.1.0 BFS kernel. Also using v1 of viperboy's undervolting at -100. There was a time I had stellar battery life (back on an early CM7 nightly and a way earlier version of SZ kernel), but for the life of me I cannot get back to that point. I've been checking spare parts and it is showing k9 and palmary weather with some partial wakelock but it doesn't look too severe from what I can tell, or maybe I'm reading it wrong.
Anyway, here's a view of my battery history. Does all that awake time seem odd? I'm kind of at a loss here for what is going on and how to fix it.
Thanks!
Click to expand...
Click to collapse
this question should be address in the cyanogen sub-forum. there are literally people there with the same setup as you that can better help you.
I wasn't aware there was a sub-forum dedicated to CM ?
There is a CyanogenMod forum thread in the development forum and one for the nightlys in the general forum.
Sent from my PC36100 using XDA App
Rem3Dy said:
There is a CyanogenMod forum thread in the development forum and one for the nightlys in the general forum.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Right, I just didn't know that there was an actual subforum. I did know there were threads.
Thanks!!
That doesn't look like a wake lock to me. Your history shows your phone being asleep most of the time. I would guess that that is an app or apps that are using too much data or cpu time. Use spare parts to check app usage, partial wake lock, ect. Make sure you don't have facebook, twitter, ect set to update every 5 mins.
nukedukem said:
That doesn't look like a wake lock to me. Your history shows your phone being asleep most of the time. I would guess that that is an app or apps that are using too much data or cpu time. Use spare parts to check app usage, partial wake lock, ect. Make sure you don't have facebook, twitter, ect set to update every 5 mins.
Click to expand...
Click to collapse
What criteria have to be met for the phone to actually sleep? Does it sleep immediately when the screen is off? The only apps that auto update are palmary weather (2 hours) and k9 email which gets imap push.
The way I understand it, an app can request a wake lock which prevents the phone from sleeping. This can be normal for certain functions, however sometimes the app won't release the wake lock and that's when the battery drains constantly even with the screen off. Spare parts will tell you everything you need to know to find the battery drain.
nukedukem said:
The way I understand it, an app can request a wake lock which prevents the phone from sleeping. This can be normal for certain functions, however sometimes the app won't release the wake lock and that's when the battery drains constantly even with the screen off. Spare parts will tell you everything you need to know to find the battery drain.
Click to expand...
Click to collapse
Thank you, that is very helpful. Here's where I am now:
On battery 2h16m and I'm at 91%.
On spare parts under partial wake usage:
Android System - 38m23s
k-9 mail - 10m1s
Those are the two highest. The other entries are negligible.
CPU Usage:
k-9 - user time - 24s
Everything else is way under 24s
So you think K-9 is a big contender here? How about whatever android system has going on?
How much of that 2 hours have you had the screen on and doing stuff? Android system has been on for almost half of the time since you unplugged. That sounds high. I would do a full wipe and reflash the ROM or try a CFS build of savagezen. A reboot usually stops the battery drain if you catch it.
nukedukem said:
How much of that 2 hours have you had the screen on and doing stuff? Android system has been on for almost half of the time since you unplugged. That sounds high. I would do a full wipe and reflash the ROM or try a CFS build of savagezen. A reboot usually stops the battery drain if you catch it.
Click to expand...
Click to collapse
Hardly any. Been just letting it sit with the screen off, letting it discharge.
Thank you again for your help!
Yeah you've a problem with android service. I would first try another kernel maybe CFS this time. If that doesn't help I would completely wipe everything and flash again. If you use titanium to restore your apps, only restore the purchased apps, not the system apps and data.
nukedukem said:
That doesn't look like a wake lock to me. Your history shows your phone being asleep most of the time. I would guess that that is an app or apps that are using too much data or cpu time. Use spare parts to check app usage, partial wake lock, ect. Make sure you don't have facebook, twitter, ect set to update every 5 mins.
Click to expand...
Click to collapse
nukedukem said:
Yeah you've a problem with android service. I would first try another kernel maybe CFS this time. If that doesn't help I would completely wipe everything and flash again. If you use titanium to restore your apps, only restore the purchased apps, not the system apps and data.
Click to expand...
Click to collapse
Woke up today with about the same rate of battery drain. This time, it didn't look like an android system problem at all, so know knows?! So frustrating.
I still may do a complete wipe though.
You're not alone..My battery sucks and I even bought 2 new batterys and its all the same..I just carry an extra around with me..I got tired of monitoring everything.
Heyo bros so I'm experiencing what I'm afraid might be a problem:
I've been getting watchdog alerts regarding the "Base System" process. It notifies me that the CPU % at the time of the captures range from 40% to 60+%. Coincidence or not, it usually happens when I wake my phone from sleep- not when I unlock it, just when I press the power button. The moment the lock screen pops up, the phone's already vibrating and the watchdog notification is up in the status bar.
Battery life so far is:
9h 22m @ 74%; Phone Idle- 56% | Cell Standby- 22% | Display 17% (40m) | Android OS 3% | Voice calls- 3%
Who knows, maybe this^ looks normal. I just want to be sure.
I've heard talk of 'wakelocks' but I don't know exactly what they are, what might cause them, and how I can track them.
I'm currently running:
Atrix 4G (not 2, just for clarification)
CM7 xB^xN
Baseband reads: N_01.77.30P
Kernel version reads: 2.6.32.39-MB860-GB-Faux123-v0.2.1 [email protected] #14
Build number: GWK74
Totally honest, I don't know if that might be able to help diagnose the problem, but for what it's worth, I want to check two things:
1) I flashed Faux's enhanced stock CM7 kernel, and am pretty sure it took, but does that look to be the proper kernel version? I just want to be sure.
2) While I also flashed the "latest radio" in the CM7 xB^xN thread, I was certain there was an xx.97 radio (vs the x.77 radio that mine appears to currently have). Am I indeed on the latest radio version?
Would it hurt to reflash these two? Could either one, or maybe both, be the cause of this?
It also occurs to me: I've been using SetCPU and have ONE profile set up that forces my CPU to min/max 216/216 when the screen is off. Could that be causing it?
Thanks so much for any and all insight bros. Also, please let me know if there's any more info you might want to help diagnose what the dealio is.
Heyo guys,
I hate to bump this kinda soon, but this is definitely a problem.
It's getting to be that I don't even have to wake the phone up for the Base System to spike. I was woken up a couple times in the middle of the night by notifications saying it was really high.
You guys have any thoughts? I'd really like to get this resolved as CM7 is AWESOME.
Yes, you guessed it- I'm not anal about the fingerprint scanner or webtop. Just a stable and fully functional release.
Thanks for any help bros I really appreciate it.
Hi, new member here.
I get the same weird spike to 50-60% (and was woken up too in the middle of the night by watchdog). I have narrowed this occurrence to when I have both Watchdog & Juice Defender enabled at the same time. (Yeah it took me a while to figure out)
When I disable Juice defender the problem seems to go away. So I'm thinking one of the power saving settings turns the radio off & a core system process really does not like that.
This is on a non-rooted Atrix, I have not tested on a rooted Atrix.
So far I had to turn off the watchdog alarm so I can sleep. If anyone can think of a solution it would be appreciated!
AX-MA said:
Hi, new member here.
I get the same weird spike to 50-60% (and was woken up too in the middle of the night by watchdog). I have narrowed this occurrence to when I have both Watchdog & Juice Defender enabled at the same time. (Yeah it took me a while to figure out)
When I disable Juice defender the problem seems to go away. So I'm thinking one of the power saving settings turns the radio off & a core system process really does not like that.
This is on a non-rooted Atrix, I have not tested on a rooted Atrix.
So far I had to turn off the watchdog alarm so I can sleep. If anyone can think of a solution it would be appreciated!
Click to expand...
Click to collapse
Thanks for the insight bro. For what it's worth, I'm not running Juice defender, or any other kind of battery saver app.
Looks like a couple of us are having problems then, though. We'd both really appreciate any info, advice, or help.
Ok, it seems it was just a coincidence with Juice Defender then.
The problem may be unrelated to power savings, but it is indeed a problem.
xyrovice said:
For what it's worth, I'm not running Juice defender, or any other kind of battery saver app.
Click to expand...
Click to collapse
AX-MA said:
Ok, it seems it was just a coincidence with Juice Defender then.
The problem may be unrelated to power savings, but it is indeed a problem.
Click to expand...
Click to collapse
It doesn't have to be unrelated to power saving just because xyrovice is not running Juice Defender, there is a option for power saving in the battery settings for the Atrix that does a similar function.. Before ruling out power savings as unrelated I would make sure xyrovice is set to "performance mode".
WiredPirate said:
It doesn't have to be unrelated to power saving just because xyrovice is not running Juice Defender, there is a option for power saving in the battery settings for the Atrix that does a similar function.. Before ruling out power savings as unrelated I would make sure xyrovice is set to "performance mode".
Click to expand...
Click to collapse
I'm running CM7 and skimmed through the settings menu and didn't find anything about 0ower features. I know that in Blue ROMs there's the battery manager section, but I don't think CM7 has this. Anything else I should look at, though?
Thanks for the insight too bro.
xyrovice said:
I'm running CM7 and skimmed through the settings menu and didn't find anything about 0ower features. I know that in Blue ROMs there's the battery manager section, but I don't think CM7 has this. Anything else I should look at, though?
Thanks for the insight too bro.
Click to expand...
Click to collapse
oIc, no I dont guess you will have those settings in CM, I should have thought of that. I wish I could help because I had the exact same prob with Watchdog constantly alerting for "Android Core Processes" and "Android Media processes", but I dont get those alerts anymore. I haven't changed ROMs or anything.. The only thing I can think of is I changed the MinFree values, I used the app "AutoKiller Memory Optimizer" to change them.
WiredPirate said:
oIc, no I dont guess you will have those settings in CM, I should have thought of that. I wish I could help because I had the exact same prob with Watchdog constantly alerting for "Android Core Processes" and "Android Media processes", but I dont get those alerts anymore. I haven't changed ROMs or anything.. The only thing I can think of is I changed the MinFree values, I used the app "AutoKiller Memory Optimizer" to change them.
Click to expand...
Click to collapse
Do you know why that seemed to solve the problem...or if it even WAS the problem, per se?
Also, is there any reason CM7 would have the minfree set to a default that causes this?
Lastly, what did you alter the minfree values to? You think ROM toolbox might have this capability?
Thanks so much for saying this bro. Who knows, this might be the problem.
PS: I just tried this and am going to see if it works. Post #13 is the one that would really sum up my reaction of successful.
Hopefully maybe this helps my other bros.
xyrovice said:
1Do you know why that seemed to solve the problem...or if it even WAS the problem, per se?
2Also, is there any reason CM7 would have the minfree set to a default that causes this?
3Lastly, what did you alter the minfree values to? You think ROM toolbox might have this capability?
Click to expand...
Click to collapse
1.) no I can't say for sure what the problem was or why I no longer get the Watchdog alerts. I was just trying to think what I have changed since they stopped because I haven't changed ROMs.. Since changing the MinFree has to do with how many or what apps are left running I'm just kinda throwing it out there as a possibility since your at a loss for things to try.
2.) no I can't think of any reason, and most with CM don't have this prob right..?
3.) It's posible it does have the capability because it does allot but I am not sure.
Foreground 12
Visible 18
Secondary 36
Hidden 121
Content 129
Empty 137
possible solutionary steps I've taken:
So Update:
I actually ended up checking out my (partial) Wakelocks with betterbatterystats, and I think I may have found a problem (diagnosed with alarmdump.txt from the Alarm Manager):
1) When I first flashed CM7 I thought, "Oh well why not really get comprehensive about keeping apps up to date" and I actually, for every single app, checked the "Automatically update" box in each one's market page. This led to a CATACLYSMIC wakelock that I'm now pretty sure could be the problem.
2)Google talk also seemed to be a little active with the screen off so I unticked the "sign me in auto..." box and made sure I signed out.
Lastly (not related to wakelocks), I checked on my TTS settings (see my last post about that).
Oh also LASTLY lastly I froze the modem fastdormancy manager in TiBU (kinda just for ****s and giggles). That said though, is the consensus on this that it's pretty harmless?
So, other bro who was having a problem, check and see if this might help you at all AYY
WiredPirate said:
1.) no I can't say for sure what the problem was or why I no longer get the Watchdog alerts. I was just trying to think what I have changed since they stopped because I haven't changed ROMs.. Since changing the MinFree has to do with how many or what apps are left running I'm just kinda throwing it out there as a possibility since your at a loss for things to try.
2.) no I can't think of any reason, and most with CM don't have this prob right..?
3.) It's posible it does have the capability because it does allot but I am not sure.
Foreground 12
Visible 18
Secondary 36
Hidden 121
Content 129
Empty 137
Click to expand...
Click to collapse
Thanks for posting this. I checked ROM toolbox and it does indeed have the capability. That said, if my aforementioned possible solutions don't work, I'm turning here. Thanks for the info bro.
Watchdog is flagging the "base process" app because IT IS using over 60% of your CPU BUT it is using 60% of your CPU that is running at 216MHZ.
It's your screen off setcpu profile of 216/216, if you bump up the max to 456 the alert will go away. When you have it set as 216/216 Watchdog (I believe) thinks that is the actual max cpu speed and bases its percentages off of that. I got that warning before and after a bit of troubleshooting (actually tried several different things) found that was the problem.
I am not sure but if you "whitelist" a app in watchdog it might ignore it as well. However my alert level was set at 80% and it would still set it off, so I think the higher speed might just be better.
My Android OS is showing a stay always time of over 17 hours (out of a 20 hour run time where my battery is completely depleted). Is there anyway I can find out what cause it?
I am already on 4.2.2
elty123 said:
My Android OS is showing a stay always time of over 17 hours (out of a 20 hour run time where my battery is completely depleted). Is there anyway I can find out what cause it?
I am already on 4.2.2
Click to expand...
Click to collapse
Android os = apps . Facebook maybe ?
You're experiencing wakelocks. Might wanna do some research on the forum so that you can post logs for people to analyze what's really eating your battery.
Sfkn2 said:
You're experiencing wakelocks. Might wanna do some research on the forum so that you can post logs for people to analyze what's really eating your battery.
Click to expand...
Click to collapse
THIS. I was having problems with wakelocks and traced them back to these few things below which got my battery life to greatly increase once disabled.
1) using dashclock extensions like FB and gmail
2) leaving google sync on in settings for the various google services
3) corporate email exchange servers
4) setting a long time variable for the phone to lock after the screen turns off (i did this to prevent putting in a pin to unlock but it kept the phone awake after the screen turned off)
5) live wall papers
There is also a known issue in the stock kernel that causes the phone to stay awake when it is supposed to go into sleep mode during extended periods of inactivity. This can be solved by using a custom kernel just as Franco r90 which has implemented patches in order to allow the phone to go into sleep to preserve battery. It is expected to be fixed in the next official OTA from google although this was also expected to be in 4.2.2 and was not fixed fully.
Same issue here. 4.2.2 stock kernel+rom, rooted
BBS shows "suspend_backoff" is at 45% no idea what's causing that.
Disabled pretty much all of the sync services but no improvement.
Interestingly right after the 4.2.2 update, the battery life was good.
Download this app and it will keep your applications from running in the background.
https://play.google.com/store/apps/...GwsMSwxLDMsImNvbS5vYXNpc2ZlbmcuZ3JlZW5pZnkiXQ..
Here's the forum for the application.
http://forum.xda-developers.com/showthread.php?t=2155737
scream4cheese said:
Download this app and it will keep your applications from running in the background.
https://play.google.com/store/apps/...GwsMSwxLDMsImNvbS5vYXNpc2ZlbmcuZ3JlZW5pZnkiXQ..
Here's the forum for the application.
http://forum.xda-developers.com/showthread.php?t=2155737
Click to expand...
Click to collapse
So far so good! totally eliminated the suspend_backoff wakeup
akiv said:
So far so good! totally eliminated the suspend_backoff wakeup
Click to expand...
Click to collapse
Update: Worked for a day now suspend_backoff is back. Happened after a recharge.
Could it be that afther the phone is charged something gets changed.
Edit: Runnig franco r90 kernel
I'm having the same problem with the Android OS draining lots of battery. When I reboot it sometimes helps but not consistently unfortunately.
Jester23 said:
I'm having the same problem with the Android OS draining lots of battery. When I reboot it sometimes helps but not consistently unfortunately.
Click to expand...
Click to collapse
I have narrowed my problem down to places where I use wifi transmitted by a lot of routers (Office wifi)
akiv said:
I have narrowed my problem down to places where I use wifi transmitted by a lot of routers (Office wifi)
Click to expand...
Click to collapse
I turn off my wifi when not home so I don't think that's the issue here.. I've tried removing a few apps like dash clock and my live wallpaper to see if it helps my issue. Will report back.
Sent from my Nexus 4 using Tapatalk 2
Google play services has something to do with the high usage. Yesterday I was near 20% usage today I disabled it and android os is at 7%. It only affects YouTube app for me, but the browser version is fine. I haven't seen any adverse affects other than maybe losing updates to the play store and ota updates which I don't care about because that's what xda and Roms are for. Now it may be placebo, but it also seems like the ui is smoother. Battery has improved greatly with sot of 3 hours with 57% left.
Hi,
how do you disable Google play services?
Try using the app greenify if your rooted.. It's been helping my battery life. Use it on maps and that will help. If maps is set as a system app, move it or just install banks minimal gapps so you can download from play store.
Sent from my Nexus 4 using xda app-developers app
SInce Greenify works with the new MOFO method, I thought it would be interesting to see how it's affecting the Turbo's already superior battery life. How much further are people getting on a single charge?
i completely forgot about that. i will let you know. may take a couple days though to really see.
I've been using greenify since owning the turbo. Without xposed, root only allows for hibernation without having to turn the screen on. Otherwise, I haven't noticed much of a difference - though it is nice not watching the screen turn on, stop processes, then turn off many times a day.
Sent from my device
Demiurge7 said:
I've been using greenify since owning the turbo. Without xposed, root only allows for hibernation without having to turn the screen on. Otherwise, I haven't noticed much of a difference - though it is nice not watching the screen turn on, stop processes, then turn off many times a day.
Sent from my device
Click to expand...
Click to collapse
i thought without root it could not autohibernate. before root you had ot manually hit the button to close apps. at least i couldnt find a way to have it auto hibernate without root
johnbravado said:
i thought without root it could not autohibernate. before root you had ot manually hit the button to close apps. at least i couldnt find a way to have it auto hibernate without root
Click to expand...
Click to collapse
No it can auto hibernate without root. You just have to set greenify as a device administrator - and it has to turn the screen on to stop apps. This function may require the paid version (dont remember), but not root. I think root may also allow hibernation of system apps, but even then I think that was an option without root.
Sent from my mobile device
does not work 100%?
My workaround was to use fast reboot pro since it stops apps without root or turning on the screen.
Haven't rooted my turbo yet (not paying for it when they give disclaimers and there was a bounty) but frp seems to save some battery plus switching to ART helps as well.
I don't think greenify will do much difference because it requires more of cpu downclocking and Governor change.
wadamean said:
I don't think greenify will do much difference because it requires more of cpu downclocking and Governor change.
Click to expand...
Click to collapse
Huh? Greenify does not "downclock" or change your governor. It keeps wake locks down, and prevents apps from using battery by running when they don't need to be.
Sent from my mobile device
My battery barelly holds 16 hours and I have the donation package of greenify. What am I doing wrong? My Z2 battery used to hold like 18~20 hours or even more.
Demiurge7 said:
Huh? Greenify does not "downclock" or change your governor. It keeps wake locks down, and prevents apps from using battery by running when they don't need to be.
Sent from my mobile device
Click to expand...
Click to collapse
I am well aware of that. My lack of not seperating the sentences may have brought confusion. What I was implying, was that greenify won't do so much of a difference because to obtain legit battery improvements it requires tweaking of kernel and cpu and governors and achieve the best battery possible.
maximuscesar said:
My battery barelly holds 16 hours and I have the donation package of greenify. What am I doing wrong? My Z2 battery used to hold like 18~20 hours or even more.
Click to expand...
Click to collapse
Do not be mislead to how many hours it lasts in the long run of quantity but focus on screen on time which matters most. I am not rooted whatsoever and I constantly achieve this battery life.
wadamean said:
I am well aware of that. My lack of not seperating the sentences may have brought confusion. What I was implying, was that greenify won't do so much of a difference because to obtain legit battery improvements it requires tweaking of kernel and cpu and governors and achieve the best battery possible.
Click to expand...
Click to collapse
I see. I do think greenify does its job, and certainly helps battery life (especially in conjunction with xposed). I would, and I am sure many others would agree that it's still an effective and legitimate tool. I agree, not as much so as throttling, but that's not really what I thought this thread was about. We are unfortunately far from kernel tweaks at the moment ☺
Sent from my mobile device
wadamean said:
I am well aware of that. My lack of not seperating the sentences may have brought confusion. What I was implying, was that greenify won't do so much of a difference because to obtain legit battery improvements it requires tweaking of kernel and cpu and governors and achieve the best battery possible.
Click to expand...
Click to collapse
apps not waking the cpu from deep sleep and being more efficient than a super fast cpu running more slowly and performing the tasks for longer. sounds better to me at least thats the idea behind the new job scheduler api in 5.x and greenify thats longer that all the components on the phone have to be operating and creating heat Im not an expert but my 2 cents
53?!?
Thats right, 53 hours, or around there at least. So I am using the original root image from mofo, with Greenify Donation Package installed, so I get auto hibernation, but not the system function hibernation....yet. I may be updating to an Xposed image soon, to unlock those features. I have every app possible except Carbonite Mobile (Auto Pic/Video backup/access) and TextSecure ( 3rd party SMS/MMS) set to auto-hibernate, including my 3rd party email K-9 Mail, I don't use the normal GMail app. With my current combination, normal usage inc. phone calls, texts, (mostly) web browsing or stalking the XDA app, I got a whopping ~53 hours of battery life before I had to charge at 2%. My phone is also my alarm clock. Unfortunately I forgot to take a screen shot, but I will try and duplicate it and take one.
BEDickey said:
Thats right, 53 hours, or around there at least. So I am using the original root image from mofo, with Greenify Donation Package installed, so I get auto hibernation, but not the system function hibernation....yet. I may be updating to an Xposed image soon, to unlock those features. I have every app possible except Carbonite Mobile (Auto Pic/Video backup/access) and TextSecure ( 3rd party SMS/MMS) set to auto-hibernate, including my 3rd party email K-9 Mail, I don't use the normal GMail app. With my current combination, normal usage inc. phone calls, texts, (mostly) web browsing or stalking the XDA app, I got a whopping ~53 hours of battery life before I had to charge at 2%. My phone is also my alarm clock. Unfortunately I forgot to take a screen shot, but I will try and duplicate it and take one.
Click to expand...
Click to collapse
That's intense.
Just rooted and got xposed working last night to hibernate some system apps. Excited to see how it works.
Sooooooooo..... Battery life with greenify and lux after root and disabling bloat. My location services are on high accuracy. My Bluetooth is always on with my moto 360. Wi-Fi and data are also always on. I receive all notifications. How can I ask for any better.....
That picture doesn't really mean anything without also showing screen on time.
JasonJoel said:
That picture doesn't really mean anything without also showing screen on time.
Click to expand...
Click to collapse
Because of the moto 360 not a lot of screen time. I reply and skip music through through the watch.
So for people like me that means a lot. Just news when I'm free for screen on time.
XT1225, Kit Kat with some apps greenified and some bloat removed/frozen.