Watchdog detects Base System @ 60% frequently?! - Atrix 4G General

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.

Related

Possible cause and solution to X10 Battery? -"No Sleep Bug"

Hey guys,
Just updated to the x10 after my samsung galaxy died on me, so far i am rather happy - except for the lack of root, but that will come.
I have noticed many complaints on the forum about battery life, and have experienced the same thing myself. From my experience, i think this looks like the same issue that was faced on a leak of 1.6 for the galaxy - it was referred to as the "No Sleep Bug".
TBH, the name says it all - for some reason, in many builds of android 1.6, phones were not sleeping correctly. There are many theories as to why, from cpu not being allowed to sleep, to permanent communication with google servers.
Despite all these different theories, one thing seemed to fix the problem - turning off all location services. Some people argue that a different carrier build, turning off just 'share with google' under location, turning off just AGPS etc. would fix it, but from my experience, the only real way to fix the issue was to turn off all GPS usage unless you need it. The once you have used it, reboot your phone.
This fix obviously sucks, and a new fix has recently been released by a veritable android-demigod around the Galaxy.
HERE IS A THREAD ABOUT NO SLEEP ON i7500 GALAXY;
(ok, some stupid rule says i can't post links - can a mod help me out?)
HERE IS THE FIX FOR THAT PARTICULAR BUG;
(ok, some stupid rule says i can't post links - can a mod help me out?)
LINKS ARE IN POST #5 - THANKS TO ONDOTEAM (would still be nice to get them in this original post though)
Now, from my experience, no sleep behave exactly the same way on the x10 as it does on the Galaxy;
1) I turn of all location services, and my battery life at least doubles.
2) After said turning off of services, 'spare parts' no longer says 100% running time under battery usage - in fact it can be as low as 10%.
These two factors are identical to my experience with Galaxy. SO; is there any way drakaz's fix can be applied to our X10's? It seems to me that the files he mods are standard Android system files, not sony/samsung specific.
Now i am no developer, so i dont know it this is possible - the first question that comes to mind for me is "do we need root access, or can this be done through developer tools using the android SDK?"
Can anyone help shed anymore light on this?
Seems to work for me. I disabled all location services. Spare Parts went down from 100% to 7.6%.
I'll just have to enable GPS when I need to use it..
Awesome! Glad to hear it has helped.
Let's keep testing this guys - if it does show up to be a big cause, then perhaps the devs around this place can help is figure out a patch for Drakas' mod to make it work with our x10's!
n3man said:
Awesome! Glad to hear it has helped.
Let's keep testing this guys - if it does show up to be a big cause, then perhaps the devs around this place can help is figure out a patch for Drakas' mod to make it work with our x10's!
Click to expand...
Click to collapse
Hello send me a PM with links, I will try to post it
http://androidforums.com/samsung-i7500/61168-no-sleep-has-nothing-do-anything.html
http://androidforums.com/samsung-i7500/78471-no-sleep-bug-fixed-drakaz.html
Links from n3man
No sleep is easy to fix, took me a while to figure it...
Turn your screen brightness from manual to auto, spare parts will now start showing proper running stats, no more 100% running.
The screen is a little dark in auto but it will cure the 100% running.
GPS and location services etc make no difference to my X10i, I am running the 1.6 version unbranded UK handset, the only thing to stop mine running 100% is to put the screen on Auto.
ronnyuk said:
No sleep is easy to fix, took me a while to figure it...
Turn your screen brightness from manual to auto, spare parts will now start showing proper running stats, no more 100% running.
The screen is a little dark in auto but it will cure the 100% running.
GPS and location services etc make no difference to my X10i, I am running the 1.6 version unbranded UK handset, the only thing to stop mine running 100% is to put the screen on Auto.
Click to expand...
Click to collapse
LOL... this is already going the way of the Galaxy thread!
My phone came out of the box with auto-brightness and i never changed that option, yet i still had no sleep.
Drakaz has done some fairly deep digging and is next to certain that it is an artefact of the geolocation bug discussed in the thread in which the problem was fixed.
I can't see "Spare Parts" in About Phone -> Battery Info
tuxStyle said:
I can't see "Spare Parts" in About Phone -> Battery Info
Click to expand...
Click to collapse
Me neither.. I was wondering about that myself!..
Although I'd half assumed that they were referring to the total "up-time" figure which you can see at the bottom of the "about phone"; "Status" screen.. But perhaps not.?
Spare Parts is a standalone Program ...
(i don't know for sure if it is in the market or downloadable as .apk from somewhere here in the forum ...)
Bax
im_iceman said:
Me neither.. I was wondering about that myself!..
Although I'd half assumed that they were referring to the total "up-time" figure which you can see at the bottom of the "about phone"; "Status" screen.. But perhaps not.?
Click to expand...
Click to collapse
You can download it here
Spare parts is indeed available from the market - it is a much more powerful tool for indicating battery usage than the regular android methods. The galaxy stared on 1.5 which had NO indicator of battery usage statistics at all, so we all learned about spare parts very fast.
Perhaps that is why no x10 users have realised about the potential no sleep bug; because so far only the android usage indicators have been used?...
Anyway, hopefully this can help us all understand the way our phones are working better together
n3man said:
Spare parts is indeed available from the market - it is a much more powerful tool for indicating battery usage than the regular android methods. The galaxy stared on 1.5 which had NO indicator of battery usage statistics at all, so we all learned about spare parts very fast.
Perhaps that is why no x10 users have realised about the potential no sleep bug; because so far only the android usage indicators have been used?...
Anyway, hopefully this can help us all understand the way our phones are working better together
Click to expand...
Click to collapse
14% it's mine value for running time, not 100%. By the way thats 30 minutes of 210 in total :S
I'm also experiencing "No sleep bug" after i used GPS. I use Battery Graph to plot my power consumption and after I use GPS, I can clearly see that power consumption is high even if i turn the phone in plane mode.
In addition SE widget, used to turn on/off GPS, seems to not work very well for me. So, to fix the bug, i manually disable GPS in parameter menu and restart my phone. After that power consumption is hardly null (20% in 8h with MP3 on almost all the time).
mimok said:
I'm also experiencing "No sleep bug" after i used GPS. I use Battery Graph to plot my power consumption and after I use GPS, I can clearly see that power consumption is high even if i turn the phone in plane mode.
In addition SE widget, used to turn on/off GPS, seems to not work very well for me. So, to fix the bug, i manually disable GPS in parameter menu and restart my phone. After that power consumption is hardly null (20% in 8h with MP3 on almost all the time).
Click to expand...
Click to collapse
Do you have 3G always on?
My phone has no trouble sleeping.
Gps hasn't really been an issue but I keep it off when not needed.
Here's my solid settings:
1) No auto sync
2) No moxier
3) Gps off
4) Restart after using wireless
As long as it's like this my phone lasts 2 days easily
ondoteam said:
Do you have 3G always on?
Click to expand...
Click to collapse
Yes, but I made a lot of test with and without 3G enabled and 3G seems not to be a problem for me. I think my problem comes from GPS.
ondoteam said:
Do you have 3G always on?
Click to expand...
Click to collapse
3G always on.
n3man said:
LOL... this is already going the way of the Galaxy thread!
My phone came out of the box with auto-brightness and i never changed that option, yet i still had no sleep.
Drakaz has done some fairly deep digging and is next to certain that it is an artefact of the geolocation bug discussed in the thread in which the problem was fixed.
Click to expand...
Click to collapse
I have been playing with mine for a month to work out what caused mine to not go into sleep, I keep GPS wifi etc on 24/7 but in spare parts I was running 100%, after numerous reinstalls and removing everything i chanced on turning on auto screen brightness, now when i unplug my x10 the running sits at the correct level.
No Geolocation bug here
I have this problem with 100% on and off. Sometimes when I check its under control (~10%), other times its at 100%. I have GPS off, no WiFi, auto brightness... don't know why it sometimes just gets stuck at 100% :/

The only thing that helped my batterydrain

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.

[13.JAN] standby 60mA - 5 Tips that may help

hey
1.
just use system panel to kill "ALL" processes include system process
then its will be back to normal mA
[well its better then restarting the phone no ?]
2.
Forgetting to disable bt or gps in winmobile
can cause that too
3.
remove with titanium backup CSPeopleSyncService [ thx to fruchtfliege ]
dont like apps that cant be controlled and do what they like
4. same apps make drain more in standby i think cos its not really full standby
5. unmount sdcard when u gonna "put ur phone to sleep"
[this one should help a lot but in testing for 8 hours gonna try it on nites]
that doesn't always work, if you don't isolate the cause then the app will re-open itself at times.
as i mentioned in some other threads, the 60ma bug is caused by the process "CSPeopleSyncService". you can kill this process as you wrote, or just disable syncing facebook and google contacts in options. at least i sync them once a day automatically (don't want to loose the sync feature), and the 60ma bug never came back...
fruchtfliege said:
as i mentioned in some other threads, the 60ma bug is caused by the process "CSPeopleSyncService". you can kill this process as you wrote, or just disable syncing facebook and google contacts in options. at least i sync them once a day automatically (don't want to loose the sync feature), and the 60ma bug never came back...
Click to expand...
Click to collapse
Might be a nOOb question but how do you kill that CSPeopleSyncService process?
I've been suffering from this 6mA for a couple of minutes and going to 60mA thing. Rebooting 'might' work but I don't want to monitor the consumption every hour.
If you don't feel like disabling sync, Quick Reboot (free in market) is a good alternative. Some builds have hot rebooting built-in, even easier.
Back in the game in less than 30 seconds, as opposed to the rather lengthy full reboot.
StephanV said:
If you don't feel like disabling sync, Quick Reboot (free in market) is a good alternative. Some builds have hot rebooting built-in, even easier.
Back in the game in less than 30 seconds, as opposed to the rather lengthy full reboot.
Click to expand...
Click to collapse
LoL just downloaded it. It really says what it does. Click it and the device reboots without a single warning.
lukesan said:
Might be a nOOb question but how do you kill that CSPeopleSyncService process?
I've been suffering from this 6mA for a couple of minutes and going to 60mA thing. Rebooting 'might' work but I don't want to monitor the consumption every hour.
Click to expand...
Click to collapse
the best way is a taskkiller. i'm using systempanel light (included in mdj hd builds), where you can add programs and processes to ignore list. but as i said, changing sync to once a day fixed my problem with 60ma in standby completely! i don't know why
StephanV said:
If you don't feel like disabling sync, Quick Reboot (free in market) is a good alternative.
Click to expand...
Click to collapse
lukesan said:
LoL just downloaded it. It really says what it does. Click it and the device reboots without a single warning.
Click to expand...
Click to collapse
I think he meant fast reboot. It just kills everything so it's as if you've just rebooted (sort of).
johncmolyneux said:
I think he meant fast reboot. It just kills everything so it's as if you've just rebooted (sort of).
Click to expand...
Click to collapse
No, I mean Quick Reboot. I'm still not convinced this battery drain is caused by certain processes, so Fast Reboot isn't an option imo.
StephanV said:
No, I mean Quick Reboot. I'm still not convinced this battery drain is caused by certain processes, so Fast Reboot isn't an option imo.
Click to expand...
Click to collapse
Fair enough. So you just mean reboot then. Ah well.
No, it's hot rebooting: basically only rebooting Android (it's a little more complex than that).
I used to do regular reboots but they take way longer.
im suffering from this in Desire HD build
wanna kill this permanently without quick reboot (since my ROM is not Deodex) completely.
disabling sync? its all "disabled"
You all might try a different SD card, had the 30ma bug, was 60. Changed micro SD card, re loaded android, now 3-7ma
Sent from my HTC Desire using XDA App
Just saying, I reboot using dev tools: bad behavior-> crash system server. Probably not the cleanest way to do it but it works.
fruchtfliege said:
as i mentioned in some other threads, the 60ma bug is caused by the process "CSPeopleSyncService". you can kill this process as you wrote, or just disable syncing facebook and google contacts in options. at least i sync them once a day automatically (don't want to loose the sync feature), and the 60ma bug never came back...
Click to expand...
Click to collapse
Where did 'find' this information?
Without background sync enabled and facebook not even installed it can draw up to 60mA.
I'm not sure it's that single process causing the drain to be honest.
(Please don't take this the wrong way )
For me I think it is after I turn on WiFi and then back off again. It never goes back to 7ish mA. It stays at around 65mA as if WiFi was still on.
I'm using darkstone SuperRAM FroYo v1.5.
strange?
I just found something interesting while using autokiller.
In the processes (i had the high drain again) there was twice the 'android system' mentioned.
I killed one of those entries, and the drain went back to 6mA.
Of course, can't be sure enough so i rebooted the phone, played with it a little and after 10 minutes of standby, i checked again. 54mA.
Again, Autokiller > processes and twice the android system. Killed 1 of them and back to 7mA.
I can't say why this happens, because in older builds (MDJ 2.4 Froyo clean w/ it's own kernel i don't have that issue).
I am no DEV or programmer, but maybe it's something others could test as well? I've been playing with this and trying to find out why this happens ever since the hastarin 8.6 kernel was released and I noticed it only happens with later kernels and mostly on RAM builds.
Just my 2 cents (or local currency my 2 bani )
I found this on other post
DarkStone1337 said:
Lets see how many people will ignore this...
To fix high power drain / usage in standby (60mA or 70mA) disable 'Use wireless networks' in Settings>Location menu. You will now get 7mA or less constantly. I discovered this as the main culprit last night. Also works in other builds.
Click to expand...
Click to collapse
For whatever its worth: On MDJ Froyo HD 4.6 (and earlier builds) I can get 3-6mA in standby but anytime I change the Kernel or framework-res.apk and reboot, standby consumption goes up to around 55 mA all the time. Doesn't matter how many times I reboot.
I've been correcting this by rebooting to WM and recopying all the files in the android folder (CLRCAD.exe, Haret.exe, initrd.gz, rootfs.img, startup.txt, system.etx2, ts-calibration) except zImage (because I'm using a different Kernel than came with the build) and data.img. When I boot back to Android, back to 3-7 mA. I don't know why this works, but it consistantly does. At least for me.
another tip by darkstone:
turn off the "use Wireless" in the Locations Settings help to solve the problem if you are having high drain when you got data/wifi

Battery dying very quickly - what to do?

My Evo battery is draining at a rate that is all together too fast. I took it off the charger about 3.5 hours ago and it has drained about 30-40%. I have not made a call nor used the net at all save for the receipt of 3-4 emails. I had a rooted phone but I reset the phone back to complete unrooted stock. I have not even so much as installed an app. What can I do about this?
turn off your mobile data when not in use. This will save tremendous amounts of battery.
if you search the forums you should find countless threads on battery and how to find out what is draining your battery and to extend life.
not sure why you would unroot unless you were exchanging it at sprint store but it greatly limits what you can do to help prevent battery drain. If you dont want to mess with much jsut use a rooted stock rom and it is pretty much the same thing as being unrooted but you keep the extra rooted benefits.
your best bet on non rooted device make sure mobile data, 4g, auto orientation, bluetooth etc are turned off. do the HTC battery condition/charge trick. and turn off background sync.
my suggestion is to re root and look into undervolted kernels and many other battery saving tricks found using search!
hopefully it helps some.
I had the same problem OP.
Turns out my radios weren't update.
Head over to the developer section and download the newest radios and stuff.
I've seen significant improvement of my battery life by using Collin_ph Battery Tweak 1 that was offered by Myn's when I flashed his/her's rom. I had my BF take his Evo to work after he come home complaining that the charge would only last about an hour or two and behold, he got through the whole day without having to charge his battery. This is after listening to music at work for 8 hours also. I HIGHLY recommend this tweak for ROOTED PHONES as I and everyone else I've recommended loves their Evo now and have no complaints...I'm at work right now and I'm at 79% and when I usually get home the battery is either still green (full) or orange (med) charge. I'm not sure if this tweak can be used with other mods but I'm very happy with this tweak as it has made my phone perfect now~~
Could be a Rogue app running killing your battery or radios not updated like stated above.
I recently started having the same issue. Advice such as turning of data and the GPS aren't helpful since the device functioned fine with GPS and data on before. Also if the battery was draining at a slower rate on the current radio before, you shouldn't need to update it, should you?
Seems that either something is making the Evo use more juice than it was before or that the battery is not holding the same capacity it used to. For some reason Phone Idle and Cell Standby have been using quite a bit more juice than they used to.
I don't like some of the software mentioned to try and locate anything that could be using more juice since those programs seem to use quite a bit themselves. Either way, what could be doing it that would come up as Phone Idle or Cell Standby in the included battery monitor? Wouldn't anything else come up under Android System?
The battery draining that quickly is not normal even with background sync, GPS (idle), 4g, data, or anything else on. There is another issue which must be solved. To troubleshoot so far I've tried another battery (same thing happens) and now I'm trying with everything turned off. If I can isolate what was causing my sudden rapid battery drain, I'll update everyone. This just started a couple nights ago for me. I think I'm on the latest radio, but I'll check.
Last post sums up my problem perfectly. I have an extended battery that lasts half the time it has over the last 4 months. Started with the radio updates. running myk
Use the battery usage functions of 'spareparts' to determine what's consuming cpu or preventing the phone from sleeping.
Can't fix the problem until you've isolated what's at fault.
Turning off mobile data will indeed fix a problem of some app trying to access the network, but it won't solve the actual cause.
bcarter2000 said:
turn off your mobile data when not in use. This will save tremendous amounts of battery.
Click to expand...
Click to collapse
I think juice defender does this automatically when the screen is off.
In the case of my phone, and I believe the OP's, we don't have any rogue apps or things running in the background. I know this phone like the back of my hand. I have completely uninstalled unnecessary apps like facebook, twitter, all things like news and weather are on manual update, i don't keep 4g or gps on, and I use wifi at home. I turn off 3g in terrible reception areas. I'm not a new user who doesn't understand the basic ways to save a little battery. I'm pretty sure the OP isn't either by his post. I use my phone the same every day. My chinese extended battery would last me easily from morning to bedtime with 20 to 30 percent to spare. Now I can't get near that after the radio updates. Since it's been well known that something is weird with these current updates, I've downgraded to 1.77 to see if that helps. My phone was sleeping fine though, so I don't know how much it will help. Always some BS with this phone.
Log out of gtalk and latitude. Those two seem to kill battery.
Bielinsk said:
Log out of gtalk and latitude. Those two seem to kill battery.
Click to expand...
Click to collapse
I appreciate it. I really do. But that is exactly the things I'm saying are already off. GTalk is turned off immediately on my phone from the jump and latitude has never been opened. It's got to be radios. I guess I'm not really asking a question, I'm just telling the OP he isn't alone.
cruecu said:
I appreciate it. I really do. But that is exactly the things I'm saying are already off. GTalk is turned off immediately on my phone from the jump and latitude has never been opened. It's got to be radios. I guess I'm not really asking a question, I'm just telling the OP he isn't alone.
Click to expand...
Click to collapse
this is the thread with flashable .zips of alllll the radio updates ever out for the EVO.
http://forum.xda-developers.com/showthread.php?t=715485&highlight=radio
if you are having trouble after a radio update, just try some of these other radios and see if that helps
Your best bet would be to root your phone again and give one of the SBC kernels a shot. I'm running CM 6.1.2 along with Zendroid 1.1.0 BFS AVS SBC and I can easily get 16+ hours with HEAVY use. And when I say heavy use, I mean hundreds of sms, dozens of calls and lots of websurfing. You will love the SBC kernels. Give it a try.
PS. My name is HondaCop and I approve this message.
We can offer suggestions until we're blue in the face.
First off, the OP needs to provide specifics of what's installed on the device, including rom, kernel, radio, etc, not to mention the hardware version itself.
Assuming it's not the known pri /rom conflict, then determination needs to be made as to what's actually consuming cpu - see first sentence above.
Need to use a systematic approach to troubleshoot this, otherwise it's a waste of time.
hgelpke said:
My Evo battery is draining at a rate that is all together too fast. I took it off the charger about 3.5 hours ago and it has drained about 30-40%. I have not made a call nor used the net at all save for the receipt of 3-4 emails. I had a rooted phone but I reset the phone back to complete unrooted stock. I have not even so much as installed an app. What can I do about this?
Click to expand...
Click to collapse
That sounds like a very weak cellular signal is forcing the radio to keep searching for it, draining the battery very quickly.
One way to somewhat alleviate this problem is to force roaming, to connect to a provider with a better signal.
"Roam Control" app does this (Market).
gpz1100 said:
We can offer suggestions until we're blue in the face.
First off, the OP needs to provide specifics of what's installed on the device, including rom, kernel, radio, etc, not to mention the hardware version itself.
Assuming it's not the known pri /rom conflict, then determination needs to be made as to what's actually consuming cpu - see first sentence above.
Need to use a systematic approach to troubleshoot this, otherwise it's a waste of time.
Click to expand...
Click to collapse
Dude....This is the best post in this thread...
Sometimes I wonder how far android users went in school....is scientific method lost these days? By no means am I qualified to help here..so my flamesuit is on for the post but damn.."my ****z broke...halp" won't cut it in a developer forum...
"it works on my machine"....words to die by.
d3x502 said:
....is scientific method lost these days?
Click to expand...
Click to collapse
What's that??????
d3x502 said:
Dude....This is the best post in this thread...
Sometimes I wonder how far android users went in school....is scientific method lost these days? By no means am I qualified to help here..so my flamesuit is on for the post but damn.."my ****z broke...halp" won't cut it in a developer forum...
"it works on my machine"....words to die by.
Click to expand...
Click to collapse
Actually,
some android users looked at the posting date, saw that the op hasn't updated in over 24 hours, wanted to complain about it, decided against it, posted quickly the most useful idea they had.
All that while doing real science.

[Tips]How to get a sexy battery life.

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

Categories

Resources