I have got a battery drain issue with my nexus s I9023 working on android 4.1.2 default factory image , no rom no kernet edited
While sleeping in 6 hours battery Drain down from 55% to 5%
The was the last day , I have this issue over two weeks ago , I have used BetterBatteryStats trying to find the process causing that ,
and I found the suspend backoff process cause that , I have changed the wifi with a static IP instead of a dynamic one and the problem still there
any suggestion ?
And thanks in advance for any help.
Have you installed any recent apps that might be causing this (any system panel app, chrome, etc)?
In Wireless Settings, press the Menu button and go to Advance.
You can try to check/uncheck (so that you can test) the following options:
- Wi-Fi optimization
- Keep Wi-Fi on during sleep --> Try setting to Always or Never
You can also check for any app that might be causing this. I've seen Chrome opening this process and staying there, causing the battery drain. But this might not be your case. You can try to reboot your phone (to clear all processes), and then open one app, close it, lock your phone and let it suspend and check if the suspend_wakelock occurs in betterbatterystats. Tedious....yes....but that way you can know which one is causing the battery drain.
Oogway13 said:
Have you installed any recent apps that might be causing this (any system panel app, chrome, etc)?
In Wireless Settings, press the Menu button and go to Advance.
You can try to check/uncheck (so that you can test) the following options:
- Wi-Fi optimization
- Keep Wi-Fi on during sleep --> Try setting to Always or Never
You can also check for any app that might be causing this. I've seen Chrome opening this process and staying there, causing the battery drain. But this might not be your case. You can try to reboot your phone (to clear all processes), and then open one app, close it, lock your phone and let it suspend and check if the suspend_wakelock occurs in betterbatterystats. Tedious....yes....but that way you can know which one is causing the battery drain.
Click to expand...
Click to collapse
Mine does it with wifi off and fresh reboot not opening any apps. I seem to get between 4 hours and 12 hours of lifetime from 100%. I should be upgrading this year but it would be nice if someone could figure this out because I know I am not the only one having an issue.
Since I (involuntarily) had to upgrade to firmware 14.4.A.0.157, I noticed unwanted periodic (~every 15min) location pings.
After a long time of trying to determine the culprit, I'm pretty sure it is "Google Play Services 6.5.99 (1642632-036)". If I downgrade it to version 6.1.05, the periodic location pings disappear.
My location mode is "Device only" because I don't want Google to send anonymous location data in the background.
I set "Location reporting" and "Location history" to "Off".
BTW, these settings are rendered in a grey fonts suggesting they are disabled, but I can operate them. I'm guessing this is Google trying to discourage people to mess with these settings, but the grey font could also be an indication of an issue. When I use a very old "Google Play Services" version, the font is black. Can anyone confirm this is normal?
I don't have any wake-lock problems, I just don't want these completely pointless (GPS does not work indoors) and battery consuming (GPS takes a toll on battery) location pings.
I suspect new versions of "Google Play Service" do more location pinging because of the recent "Google Fit" integration, but that's just conjecture.
Can anyone confirm the location pings?
With the above settings (I guess the location mode is important, otherwise GPS won't be used), you should be seeing periodic ticks in the "GPS on" bar when looking at the "History details" battery usage chart by going to "Settings | Power management | Battery usage" and tapping on the top chart.
Any ideas of what I could be doing instead of repeatedly reverting to Google Play Services 6.1.05? The shame is that they automatically update to 6.5.99 from time to time. I don't get how the latter is possible without the user's consent, in particular Goog
If you are that conseious, why not turn off Location Service all together ?
I'd suggest confirming weather indeed Location Pings are happening or not. Install [APP][2.1+][21 Dec. - V2.0RC4] BetterBatteryStats Follow the instructions on that thread on how to install and pull an Idle Log. Take a look at the Text Log. If it has Entries such as "NLP Service" then there are pings. It will also tell you which application is requesting location.
You might also wish to review [GUIDE] Insanely Better Battery Life When Idle - Battery Life Thread
It might not be your device, but the thread is applicable nonetheless.
Perseus said:
If you are that conseious, why not turn off Location Service all together ?
Click to expand...
Click to collapse
If I want to use an application like Maps, I'd like to be able to simply start it and use it without having to manually enable "Location Service" first (and then disable "Location Service" again, once I'm done).
This has been working fine before and I believe it is reasonable for "Location Service" to be enabled all the time but actual resources (like GPS) only be used when necessary.
I may should add that I'm not too worried about my location being known -- although I deny browsers and apps to know about my location per default because it is nobody's business where I am, I'm not overly fuzzed if something should leak -- but I'm against anything depleting my battery, in Google's case probably for their good, rather than mine.
Perseus said:
I'd suggest confirming weather indeed Location Pings are happening or not. Install [APP][2.1+][21 Dec. - V2.0RC4] BetterBatteryStats Follow the instructions on that thread on how to install and pull an Idle Log. Take a look at the Text Log. If it has Entries such as "NLP Service" then there are pings. It will also tell you which application is requesting location.
Click to expand...
Click to collapse
Thanks a lot for this suggestion, but I understand doing the above would require a "rooted" phone. I'm using a stock ROM, non-rooted, bootloader locked and initially planned to just use the phone, instead of discovering a whole new world of spending one's time.
I can see that I will eventually become someone running a custom ROM (e.g., to get back AppOps), but for now I just want to enjoy the phone (retaining warranty being part of the motivation).
Perseus said:
You might also wish to review [GUIDE] Insanely Better Battery Life When Idle - Battery Life Thread
Click to expand...
Click to collapse
Thanks heaps!
I'll have a look now.
Hey guys.
Lately whenever I'm flashing a new kernel either on KitKat or Lollipop I get terrible wakelocks that kill my battery. Not sure why this is happening. I'm using CWM. Basically after flashing I can just notice a huge battery drainage and I tend to install either GSam or WakelockDetector to see what's the problem. WakelockDetector (Rooted) gives me an overall idea of my battery problem. Usually SystemUpdateService, Audiomix "1013", "NlpWakeLock" , "EventlogService" and "CheckinService" drain my battery the most. Sometimes "ConfigFetchService" as well.
Thanks
KodRoute said:
Hey guys.
Lately whenever I'm flashing a new kernel either on KitKat or Lollipop I get terrible wakelocks that kill my battery. Not sure why this is happening. I'm using CWM. Basically after flashing I can just notice a huge battery drainage and I tend to install either GSam or WakelockDetector to see what's the problem. WakelockDetector (Rooted) gives me an overall idea of my battery problem. Usually SystemUpdateService, Audiomix "1013", "NlpWakeLock" , "EventlogService" and "CheckinService" drain my battery the most. Sometimes "ConfigFetchService" as well.
Thanks
Click to expand...
Click to collapse
[Battery Life Help] Troubleshoot battery issues here!
Application wakelocks have absolutely nothing to do with the kernel.
Keep in mind a "wakelock" is simply a request to keep the device awake; they can happen regardless whether the screen is on or off, they are only an issue if they occur while the screen is OFF.
SystemUpdateService is a pretty obviously named wakelock, it's used while an OTA is being downloaded. You can disable the service and it's receivers with an app like Autorun Manager (https://play.google.com/store/apps/details?id=com.rs.autorun, open in advanced mode, go into it's settings to enable for system apps, tap on Google Play Services, disable everything with SystemUpdateService in it's name).
AudioMix is triggered every time there is an audio event, including touch sounds. Harmless as it's usually only used while the screen is on.
NlpWakeLock is a location wakelock.
EventlogService and CheckinService are harmless, unless they occur 24/7 and don't go away EVER, which means you disabled their services but not their receivers.
ConfigFetchService is mostly harmless, it simply fetches your settings from Google's servers when you open a Google app, if that app stores it's settings on the cloud instead of locally.
Lethargy said:
[Battery Life Help] Troubleshoot battery issues here!
Application wakelocks have absolutely nothing to do with the kernel.
Keep in mind a "wakelock" is simply a request to keep the device awake; they can happen regardless whether the screen is on or off, they are only an issue if they occur while the screen is OFF.
SystemUpdateService is a pretty obviously named wakelock, it's used while an OTA is being downloaded. You can disable the service and it's receivers with an app like Autorun Manager (https://play.google.com/store/apps/details?id=com.rs.autorun, open in advanced mode, go into it's settings to enable for system apps, tap on Google Play Services, disable everything with SystemUpdateService in it's name).
AudioMix is triggered every time there is an audio event, including touch sounds. Harmless as it's usually only used while the screen is on.
NlpWakeLock is a location wakelock.
EventlogService and CheckinService are harmless, unless they occur 24/7 and don't go away EVER, which means you disabled their services but not their receivers.
ConfigFetchService is mostly harmless, it simply fetches your settings from Google's servers when you open a Google app, if that app stores it's settings on the cloud instead of locally.
Click to expand...
Click to collapse
Disabling the receivers works indeed. Thanks! By the way, another issue I'm having is that my Nexus 5's CPU heats too fast operating in UI and doing basic stuff, like installing apps from Play Store or watching videos on YouTube. Normally after about 5 min. of running if I go to System Monitor the CPU's temp is around 40-47ºC on action, in standby cools down to 34-35ºC but then after I use it again the temp rise to 45-47ºC. Usually when this happens the battery's temperature is also triggered and reaches 28-30ºC. Is this normal?
KodRoute said:
Disabling the receivers works indeed. Thanks! By the way, another issue I'm having is that my Nexus 5's CPU heats too fast operating in UI and doing basic stuff, like installing apps from Play Store or watching videos on YouTube. Normally after about 5 min. of running if I go to System Monitor the CPU's temp is around 40-47ºC on action, in standby cools down to 34-35ºC but then after I use it again the temp rise to 45-47ºC. Usually when this happens the battery's temperature is also triggered and reaches 28-30ºC. Is this normal?
Click to expand...
Click to collapse
The CPU throttles at 65C by default (some kernels change this or give you an option to change it), and shuts down at 105C. 47C is hardly anything.
Sony xperia Z3 Dual D6633 Android 5.0.2 Build 23.1.1.E.0.1
Hi there,
Upgraded my Z3 to lollipop last week and, despite the fact that the upgrade itself was flawless, I think I went from a device that used to work like a charm to one full of annoyances.
On day #1, noticed the batt drain skyrocket. 3h after disconnecting it, it was at 68%, half way through the morning. WTF? was my first thought. On a typical day on kitkat, I was able to end the day at 40% at least.
The second thing I´ve noticed was the phone app. It starts giving me errors, saying that the "network could not be reached" when I try to dial a number. If I insist for 4, 5 more times, it crashes. Dialing is only possible again if I reset the phone.
The third thing is the lock screen. It seems that lollipop has a drop down menu that makes it possible to enable/disable lots of things, like communications and even setting the phone in airplane mode. Imho that´s a huge liability / security risk and it appears that there is no way around that.
Still about the lock screen, it seems to have a bug: if you have any activesync account setup, not notifications will show up, no matter how you configure it (to show all or hide sensitive content).
So, I had only one thing to do, after reading forums etc... factory reseting it.
Surprise! All problems are still there.
Does any1 have any tips on those?
Thanks in advance.
There will be a widget on one of the screens which keeps refreshing itself and I found that to be the battery killer on my 6603.
Did you use any specific app to pinpoint the culprit?
1. It is possible that the battery levels are calibrating and will be imprecise for a while after the update, using the device normally for a couple of days will fix it, or at least this is what I observed in many phones I owned.
2. This is very weird and I can't help you with. If not even factory reset did help you may have some corrupted data on one of your contacts maybe? Try to make a thread about this issue on the Sony forum.
3. I noticed that as well, but even on pervious versions you could turn off the phone so I don't think it changes anything. Make sure to disable the multi user options that would allowanyone to add a new user from the lock screen.
4. Another weird thing, I use exchange accounts on my phone and I don't have any problem on mine. See point 2.
Under
settings>sound and notifications>when device is locked
Set to hide sensitive notification content or don't show notification content at all.
This should fix lock screen displaying email notifications from your exchange account.
Also, unlock phone, pull down notifications, pull down again to reveal quick settings, hit the edit button (pencil) and remove icons but clicking and holding and drawing them to the top. Unfortunately this removes them even when phone is unlocked but of your worried about unauthorised toggling of things on off its the best you can do I think.
As for battery drain, check the battery usage in
Settings>power management
Make sure stamina mode is on, toggle it off then on to make sure.
Select battery usage and check to see if any apps are using more than they should. Make sure brightness is set low but enable adaptive brightness under display settings.
ozzy lion said:
Under
settings>sound and notifications>when device is locked
Set to hide sensitive notification content or don't show notification content at all.
This should fix lock screen displaying email notifications from your exchange account.
Also, unlock phone, pull down notifications, pull down again to reveal quick settings, hit the edit button (pencil) and remove icons but clicking and holding and drawing them to the top. Unfortunately this removes them even when phone is unlocked but of your worried about unauthorised toggling of things on off its the best you can do I think.
As for battery drain, check the battery usage in
Settings>power management
Make sure stamina mode is on, toggle it off then on to make sure.
Select battery usage and check to see if any apps are using more than they should. Make sure brightness is set low but enable adaptive brightness under display settings.
Click to expand...
Click to collapse
That's not a smartphone anymore, with all functions shut down and brightness low.
This phone has the best screen, use it at least 50% brightness.
I have no issues with the brightness down. It bumps up nicely in brighter conditions and will even max out in daylight. If I ever need it brighter then it's easy to boost temporarily. It's a small price to pay for nearly 24 hours of battery with 5 hours screen on time.
I never mentioned shutting down functions. The only thing I mentioned removing was the toggles that concerned the op on the quick settings. Removing mobile data and aeroplane mode from quick settings hardly cripples the device, I never use these anyway.
I don't think it very useful that there's not more customisation available here such as a complete set of separate lockscreen settings. But if all you can do is comprise then what else can you suggest?
I don't think unlocking the bootloader and installing a custom ROM is something the op wants to do.
ozzy lion said:
I have no issues with the brightness down. It bumps up nicely in brighter conditions and will even max out in daylight. If I ever need it brighter then it's easy to boost temporarily. It's a small price to pay for nearly 24 hours of battery with 5 hours screen on time.
I never mentioned shutting down functions. The only thing I mentioned removing was the toggles that concerned the op on the quick settings. Removing mobile data and aeroplane mode from quick settings hardly cripples the device, I never use these anyway.
I don't think it very useful that there's not more customisation available here such as a complete set of separate lockscreen settings. But if all you can do is comprise then what else can you suggest?
I don't think unlocking the bootloader and installing a custom ROM is something the op wants to do.
Click to expand...
Click to collapse
You said stamina.
Stamina means already some functions off.
Update:
1. Batt drain
Remains without an explanation. My daily use profile is basically the same as before the update. 3PM and I am at 28%, with stamina on. I can´t recall a day, running kitkat, that I would hit the charger at night with 28% of batt remaining (and I still have 4h to go). It was always on 40% ish. GSAM is reporting that 47% of the batt drain is caused by apps and, from that, 30% is represented by android core apps + android system + kernel. I might be wrong, but I think it is related to reindexing, contact + agenda sync etc and it will probably get lower eventually (I hope!)
2. Phone App giving errors
I think I have isolated the problem. It seems to be caused by TrueCaller.
3. Lock screen
Regarding the drop down menu, It is clear now that what I think is a problem is, in fact, by design and there is no way around it without rooting. But regarding the notifications, I just removed both activesync accounts and I started getting notifications in the lock screen again. So, my guess is that there is a policy of some sort that is being interpreted by the phone as it should hide all notifications from the lock screen.
In fact, there are lots of things that got blocked / disabled because of those policies. Here is a list of things that were disabled and now appear to be working again, after the removal of the activesync accounts:
. notifications are showing again in the lock screen;
. smart lock;
. screen lock options (none, swipe, pattern);
note: I thought that I would be able to enable services in Accessibility, like LastPass or App Advisor by Norton, but it still does not work (I try to enable any of them, but pressing "ok" on the warning dialog does nothing and the only option working is "cancel").
Thinking about resetting it again...
Hi, if problems are persistant you can always downgrad software at KitKat by using FlashTool and wait Lollipop 5.1 (5.1 will probably solve many problems).
StealthNet said:
Update:
1. Batt drain
Remains without an explanation. My daily use profile is basically the same as before the update. 3PM and I am at 28%, with stamina on. I can´t recall a day, running kitkat, that I would hit the charger at night with 28% of batt remaining (and I still have 4h to go). It was always on 40% ish. GSAM is reporting that 47% of the batt drain is caused by apps and, from that, 30% is represented by android core apps + android system + kernel. I might be wrong, but I think it is related to reindexing, contact + agenda sync etc and it will probably get lower eventually (I hope!)
2. Phone App giving errors
I think I have isolated the problem. It seems to be caused by TrueCaller.
3. Lock screen
Regarding the drop down menu, It is clear now that what I think is a problem is, in fact, by design and there is no way around it without rooting. But regarding the notifications, I just removed both activesync accounts and I started getting notifications in the lock screen again. So, my guess is that there is a policy of some sort that is being interpreted by the phone as it should hide all notifications from the lock screen.
In fact, there are lots of things that got blocked / disabled because of those policies. Here is a list of things that were disabled and now appear to be working again, after the removal of the activesync accounts:
. notifications are showing again in the lock screen;
. smart lock;
. screen lock options (none, swipe, pattern);
note: I thought that I would be able to enable services in Accessibility, like LastPass or App Advisor by Norton, but it still does not work (I try to enable any of them, but pressing "ok" on the warning dialog does nothing and the only option working is "cancel").
Thinking about resetting it again...
Click to expand...
Click to collapse
A new firmware version has dropped for the Z3 which I think fixes your issues with notifications.
I received it OTA yesterday, I'm running the Balkans customisation.
Thank you for the tip! I hope it does! Will keep it posted here just for the reference. I am starting to feel other "symptoms" as well, like bluetooth instability (you pair a device and it stops working, have to pair again).
.
Just hit another weird thing.
I am not being able to create a new vpn connection. I am trying to use the PureVPN and IPVanish client software, but when I try to setup the conection, I receive a disclaimer, saying that my traffic might be monitored, with a "CANCEL" and "OK" options. The OK doesn´t work, only "CANCEL".
My device is encrypted and I have also noticed that I am not able to decrypt it.
Also, If I go to Accessibility and try to enable a service, the same thing happens: a disclaimer appears, saying that the service might observe my actions, with a "CANCEL" and "OK" options. The OK doesn´t work, only "CANCEL".
Any ideas?
Ok, just a quick fup: the ability to create VPNs from apps is disabled if you encrypt the phone. It seems that if you create if before encrypting, it won´t be disabled; but you wont be able to create a new vpn from an app downloaded, after encryption.
Regarding the Accessibility > Services, after a *lot* of research, I have found that Twilight was the culprit. For the reference:
https://code.google.com/p/android/issues/detail?id=79637