Related
I have my phone running 99.6% of the time in spare parts and it shows android system as the culprit holding a partial wakelock.
so my question is, how do i fix this? i've tried a factory reset three times, am updated to 1.21 ota and have slowly started to reintegrate apps but it always starts again and always after a different app.
i'm getting pretty frustrated anyone got any ideas?
UPDATE In my case it was network time abusing wireless location service that was causing the problem and hence the reason a factory reset didnt solve it, i switched off network time and voila!
just to clarify, no live wallpapers, and phone is in airplane mode to avoid any data usage drainig the battery.
i have got beautiful widgets homescreen small clock and pure cal widget installed at the moment but even when i uninstall them it doesnt fix it, also im running launcher pro 0.4.2 but also had the problem when i reverted to sense.
and i have read every other thread here about battery life that i could find but no-one seems to have this problemo
anyone with any advice on why my phone wont sleep?
A long shot, but go in to Mobile Settings and untick Enable always-on mobile data.
Philosoma said:
A long shot, but go in to Mobile Settings and untick Enable always-on mobile data.
Click to expand...
Click to collapse
ok cool, giving that i try now but i had been leaving it in airplane mode to try and take the vagaries of data out of the equation.
this started about a week ago and i really noticed it when i was in a 6 hour long meeting and my battery basically draines 60% even though the phone was in airplane mode
ok tried that but with my phone just factory reset, airplane mode and no apps installed other than spare parts it's showing running 94.1 % of the time and all of it is android system.
that cant be right
i have restored data, maybe i shouldnt restore data either but that just seems plain crazy
Re: Android system - partial wake lock
What exact foreground and background processes/services do you have running when this is happening, any idea?
Apps like System Panel can show you them and some useful other details. That is certainly too high.
-------------------------------------
- Sent via my HTC Desire -
th3 said:
What exact foreground and background processes/services do you have running when this is happening, any idea?
Apps like System Panel can show you them and some useful other details. That is certainly too high.
-------------------------------------
- Sent via my HTC Desire -
Click to expand...
Click to collapse
ok right now there is
com.android.syncml.service
sense
market
messages
people
rss reader
syncml provider
sys panel
touch input
updater
and then a load of inactive cached applications
do you see anything unusual there?
ok so i downloaded system app and killed all apps except excluded and sytem apps and my running usage has gone down, now thats no suprise in and of itself but now i need to see if it stays down.
i've just checked again and the percentage is still going down, so it's either an inactive app which i didnt list ( is that even possible if its inactive) or one of the items i listed above.
has anyone got any thoughts.
What do the logs say upon going to standby? (Use aLogcat to watch/save system log).
I had same problem I tried the turning off network always on to off, didn't change anything. the thing that worked for me was turning off my flickr account!? For some reason it kept my calendar awake so keeping system from sleeping, don't ask me why as I can't figure it out, though since doing this I'm now getting up to 2 days of average use from the battery. Also I've done the usual of reducing the different accounts sync timings etc.
Have you typed *#*#4636#*#* into the phone key pad to look at what is happening? This can give valuable info on what's draining the battery.
Jazd71 said:
I had same problem I tried the turning off network always on to off, didn't change anything. the thing that worked for me was turning off my flickr account!? For some reason it kept my calendar awake so keeping system from sleeping, don't ask me why as I can't figure it out, though since doing this I'm now getting up to 2 days of average use from the battery. Also I've done the usual of reducing the different accounts sync timings etc.
Have you typed *#*#4636#*#* into the phone key pad to look at what is happening? This can give valuable info on what's draining the battery.
Click to expand...
Click to collapse
I have the same problem as OP since the latest update. The *#*#4636#*#* code is not helping in this case. The partial wake lock is displayed as Android System - which doesn't tell me anything.
I read something about the Calendar issues but I am unable to stop the calendar in running processes.
How did you solve your problem?
ferus said:
I have the same problem as OP since the latest update. The *#*#4636#*#* code is not helping in this case. The partial wake lock is displayed as Android System - which doesn't tell me anything.
I read something about the Calendar issues but I am unable to stop the calendar in running processes.
How did you solve your problem?
Click to expand...
Click to collapse
Ok i seem to have had some luck since last night though i'm not sure of the exact reason.
i did as th3 said and downloaded system monitor and then killed all background active and inactive tasks and that seems to have solved the problem. I have no idea why that would be the case though and i am watching it carefully to see if it stays fixed.
i dont have a flickr account setup
djet said:
What do the logs say upon going to standby? (Use aLogcat to watch/save system log).
Click to expand...
Click to collapse
Djet, I installed alogcat and have found all references to wakelock, rather than post the entire log
D/PowerManagerService( 77): wakelock: PARTIAL_WAKE_LOCK 'NetworkLocation Check Location' activated (minState=0)
D/PowerManagerService( 77): wakelock: PARTIAL_WAKE_LOCK 'NetworkLocation Check Location' activated (minState=0)
D/PowerManagerService( 77): wakelock: PARTIAL_WAKE_LOCK 'keyguardWakeAndHandOff' activated (minState=0)
D/PowerManagerService( 77): wakelock: FULL_WAKE_LOCK 'keyguard'ACQUIRE_CAUSES_WAKEUP activated (minState=3)
there are also some entries in red like this one
E/vold ( 53): Unable to lookup media '/devices/platform/msm_sdcc.1/mmc_host/mmc0/mmc0:0001'
and a load of errors to do with global search etc but this is all pretty much gobbledegook to me, what am i looking for?
thanks
ok so based on that log i have switched of the use wireless networks to find my location (not gps i hardly ever use that anyway) and now the running % is dropping fast.
i will keep you posted as to whether it keeps coming down or not.
it is going to be an enormous bummer if i cant use wireless location, thats one of a smartphones greatest powers, why would this suddenly start happening now ( started about a week before the ota update) and continues even when i factory reset.
kinkade said:
ok so based on that log i have switched of the use wireless networks to find my location (not gps i hardly ever use that anyway) and now the running % is dropping fast.
i will keep you posted as to whether it keeps coming down or not.
it is going to be an enormous bummer if i cant use wireless location, thats one of a smartphones greatest powers, why would this suddenly start happening now ( started about a week before the ota update) and continues even when i factory reset.
Click to expand...
Click to collapse
I suppose it's not the feature itself guilty but the applications using it. I had the same issue with battery running out because of Location service wake locks. It turned out one of the Locale app plugins was abusing this service. Having it uninstalled battery run became normal.
djet said:
I suppose it's not the feature itself guilty but the applications using it. I had the same issue with battery running out because of Location service wake locks. It turned out one of the Locale app plugins was abusing this service. Having it uninstalled battery run became normal.
Click to expand...
Click to collapse
Yes i know what you mean, how did you go about diagnosing that? also i have done several factory resets and it still happens
Re: Android system - partial wake lock
There are a many app settings that drain battery and the stock setup is nothing I am fond of. Location/locale was one of them for me, calendar, network time and widget/app syncs being the others. A non-stock app causing such problems was NetCounter.
Calendar was fixed by killing it and restarting it. It's a known bug for many.
If many widgets are running sync very often, then you can imagine battery draining fast.
-------------------------------------
- Sent via my HTC Desire -
th3 said:
There are a many app settings that drain battery and the stock setup is nothing I am fond of. Location/locale was one of them for me, calendar, network time and widget/app syncs being the others. A non-stock app causing such problems was NetCounter.
Calendar was fixed by killing it and restarting it. It's a known bug for many.
If many widgets are running sync very often, then you can imagine battery draining fast.
-------------------------------------
- Sent via my HTC Desire -
Click to expand...
Click to collapse
th3 you are legend, it was network time, i switched that off and all is now well in the world. cheers dude
Good find. I had the thing off anyway, but it is good to know.
The date I noticed my battery issues coincides with when the update went live. I've tried tinkering as much as I can to disable wake lock permissions in all sorts of apps and using wake lock detector, but I can't really find the culprit.
I'm rooted, on 4.6.3. Is there a way to turn off the OTA check, or fool it into thinking I have 4.6.3.
Is it something else? I have a lot of apps, but the only thing wake lock can tell me about the sheer number of wakes is google play services, which has had it's permission to wake disabled but still is somehow the cause. That and system are about equal. Awake time is 91% since my last full charge and unplug. Not good.
Thanks for any help.
Just to maybe assist you in finding the culprit I'm on 4.6.3 with google apps but no root. I've not experienced any wake locks. Perhaps clearing Google's cache and data?
Sorry I meant I was on 4.6.1 still. Will clear data and see.
adam.nox said:
The date I noticed my battery issues coincides with when the update went live. I've tried tinkering as much as I can to disable wake lock permissions in all sorts of apps and using wake lock detector, but I can't really find the culprit.
I'm rooted, on 4.6.3. Is there a way to turn off the OTA check, or fool it into thinking I have 4.6.3.
Is it something else? I have a lot of apps, but the only thing wake lock can tell me about the sheer number of wakes is google play services, which has had it's permission to wake disabled but still is somehow the cause. That and system are about equal. Awake time is 91% since my last full charge and unplug. Not good.
Thanks for any help.
Click to expand...
Click to collapse
Probably one of those glitches that can be solved by a reboot. However, you can disable updates using hdxposed module for xposed if you want.
Done both of those things plus much more. Anyone else having this issue?
try taking a titanium backup of everything and then factory reset.. with everything backed up to your PC. then root and start restoring everything gradually.. start by social apps and call log and messages.. then your essential apps.. and see.. then add the rest of the apps bit by bit till you find the offending application or maybe something just got screwed will be fixed when the data clears..
just make sure there is nothing out of the norm in your essential apps, meaning they are all tried and tested by everyone.. facebook, whatsapp, keep, launcher.. that stuff. and also make sure in these apps to limit their ability to check every X minutes as they can really drain your battery.
I've disabled wakelock on anything that has reported to use it by wake lock detector that I don't absolutely need to have it. I've uninstalled any non-essential apps. I've done too much tinkering and have too much important app data to risk doing a reset when it may not work.
I need a way to actually get to the bottom of it first.
Why is google play services waking the phone 2000+ times per day? Wake lock detector says the phone has been awake 5 hours out of 10, but then the list of times for each app only adds up to 20 minutes. How do I find out what was keeping it awake the rest of the time?
Possibly some kind of location based frippery. Try removing location access from troublesome app. And turn off auto sync if it's on
Location services are completely disabled. Auto sync is off. Both have been since this started happening.
Used app quarantine to disable almost every app I put on here, and Fire OS is still 51%.
Possible culprits, though I'm not sure if I find it likely: Ultimate dynamic navbar, lightning chat, foscam viewer, google apps, xposed mods (have a few). greenify (that would be ironic), flixter, es file explorer, buildprop editor, calculator, jellybean keyboard, multi timer, skana battery alerts, nova launcher, power toggles, slacker radio, bank app, super user, terminal emulator, outlook, wakelock detector.
Get better battery stats from xda, it gives a better breakdown of wake locks.
Alright what should I look for in there?
Ok here is what I believe I have found out, using network log along with better battery stats.
The phone is waking up constantly due to netbios pings (I know not technically pings), from various computers on my network, mostly my main PC. I don't know why it's doing this. Could be one of many background processes. In my opinion, it shouldn't matter. The phone shouldn't be that stupid.
I was able to... I think, mitigate a lot of this by doing a few things.
The first is editing qcom's ini inside etc/wifi so that if it says offload, I put a 0, I assume it's offloading to the cpu, which causes it to wake for pointless crap. The second thing I did was re-enable optimized wifi. This is probably already on, on everyone else's phone. I turned it off because I was trying to figure out how to tether while connected to a vpn through the phone. Still can't get that to work. And I know how to, because I did it on my nexus prime, but something in the fire OS is f'ing that method up (iptable configs).
I'm considering seeking an app to turn off wifi when the phone sleeps, because better battery shows wifi on 100%, and even with the changes above, I was still responding to some netbios pings in the network (about 1/5th as many). I imagine most networks will have noise like this.
However, even after all this, fire OS is still the main battery draw. Better Battery doesn't account for all the wake time, not even by half.
For now I've put enough time into this.
Hello everybody.
I have recently rooted my phone to try and identify the cause to my fast battery drain, which is primarily from the Android OS process.
I can't seem to find it. I see that the process "system" is working a lot and that the Android OS is awake for way to long.
Maybe you guys can point out something I'm missing here.
I would appreciate every help from you !
Thx
raied115 said:
Hello everybody.
I have recently rooted my phone to try and identify the cause to my fast battery drain, which is primarily from the Android OS process.
I can't seem to find it. I see that the process "system" is working a lot and that the Android OS is awake for way to long.
Maybe you guys can point out something I'm missing here.
I would appreciate every help from you !
Thx
Click to expand...
Click to collapse
This really could be anything. I recently had this and experimented for days whenever I took a break. For me, it turns out that it was my work's wifi hotspot making my phone stay awake to stay connected. I turned off wifi and it was fixed. But this isn't a solution. I ended up connecting to my own wireless repeater and problem was gone.
Bottom line is you'll have to figure out what's going on yourself.
htr5 said:
This really could be anything. I recently had this and experimented for days whenever I took a break. For me, it turns out that it was my work's wifi hotspot making my phone stay awake to stay connected. I turned off wifi and it was fixed. But this isn't a solution. I ended up connecting to my own wireless repeater and problem was gone.
Bottom line is you'll have to figure out what's going on yourself.
Click to expand...
Click to collapse
Thank you for your reply.
I couldn't find any cause to the problem, that's why I thought that maybe another pair of eyes (or more ) might help...
raied115 said:
Thank you for your reply.
I couldn't find any cause to the problem, that's why I thought that maybe another pair of eyes (or more ) might help...
Click to expand...
Click to collapse
I'll tell you what I've done for battery life on my phone and maybe on of those will fix your problem.
1. Uninstall stock bloat (only the stuff actually running in the background; no need to remove stock launcher ect.)
2. Disable Wi-Fi scanning when wifi off
3. Use Amplify to limit wakelocks and alarms
4. Freeze the apps you don't regularly use. I have a titanium backup widget on my homescreen that will unfreeze snapchat and launch it. It is the pressed again to freeze it after use.
5. Greenify apps you don't want running in the background for no good reason. If you get the donate version, you can still get GCM notifications so it's win win. For apps that don't have GCM notifications, it will coalesce the notifications so your phone doesn't wake up as often.
6. Make sure you have all logging turned off from the LG hidden menu.
7. If you're on a bad wi-fi network run by work/school, then get the auto disable IPv6 app on the play store.
8. Use the HEBF Optimzer app to prevent Google wakelocks and battery drains.
9. Use PNF Root app on the play store to custom choose how often your phone checks for GCM notifications.
With these changes, I finish the day with around 4 hours of screen on time doing regular things. Don't believe the posts about 7-8 hours SOT because you don't know what they were doing. I once used my phone as a timer while studying and had the screen on for 3 hours and only drained 12% battery.
absolutely the same issue here. No luck with factory reset, not using whatsapp or messenger, not using wifi, not using mobile data, no luck with any kind of debloating, uninstalling, installing greenify, amplify whatever. In the end, the Android OS will come back and drain the battery. I've spent a way too much time on this issue.
kakaovnik said:
absolutely the same issue here. No luck with factory reset, not using whatsapp or messenger, not using wifi, not using mobile data, no luck with any kind of debloating, uninstalling, installing greenify, amplify whatever. In the end, the Android OS will come back and drain the battery. I've spent a way too much time on this issue.
Click to expand...
Click to collapse
Try clearing the Google Play Services data, then removing all Google accounts and then adding them back. This time, make sure not to agree to any data collection.
When you turn GPS on, it should show as GPS only in the location settings. Disagree to any prompts.
If your location defaults to high energy GPS and networks, then try flicking the toggle on and off very quickly after you have cleared the play services data. This is how I got the prompt for data collection to come back. It's annoying and you have to always disagree but it fixed my mysterious battery drains from android os.
Hi all,
I'm running several apps that should run all the time (AdGuard, Network Speed Meter) or for a long time (speed trap warner,...) but OxygenOS kills them after a certain period. Some of them restart automatically, some don't. Of course all of these apps are 'not battery optimized'. Is there any chance to prevent OxygenOS from killing them?
Are there custom ROMs that can overcome this problen?
I'm on the latest OxygenOS Pie Beta, but the behavior was similar on Android O...
Thanks a lot,
W
Did you try locking the app via recents menu?
Thank for the info, didn't know that.
Unfortunately it doesn't help, Adguard and the network monitor don't appear in recents. The speed trap warner automatically starts and stops when I'm in the car, i don't want to open recents manually every time.
Battery - Battery optimisation - Don't optimise
safwankatharudheen said:
Battery - Battery optimisation - Don't optimise
Click to expand...
Click to collapse
This is not changing anything,e ven with disable battery disabled, even with adaptative battery disabled.
I have the same problem. I have not found any solution whatsoever. This is really frustrating. I've made sure apps aren't optimized. Advanced optimization is disabled. Developer options background limit is at standard. I've pinned the apps in recent apps and it still happens. Apps get killed all the time.
For example,
1. I use Google Fit to start tracking a run. Within 10 minutes of tracking, the app is closed and workout not tracked. Its not even like i touched the phone and opened other apps during this.
2. I have VoIP account setup in the default dialer. Calls come through only 50% of the time cause the dialer is closed.
3. YouTube Music, constantly gets closed if i simply pause the music. Within 2 minutes, the app is closed.
4. Trying to transfer 15GB of files through Explorer app from phone to file server, never succeeds if i don't watch the app and keep the screen on.
5. Plex gets closed and therefore my photos don't auto backup with the phone is plugged in.
This is absolutely ridiculous! Why the hell a phone with 8GB of RAM is killing apps is beyond me!
Custom ROM on the same phone, like Lineage OS, no issues. Can have optimization on, battery manager on and all. In fact, battery life is better on custom when its not killing the apps! Seems to be the only solution until OOS can stop killing apps so aggressively.
M3drvr said:
I have the same problem. I have not found any solution whatsoever. This is really frustrating. I've made sure apps aren't optimized. Advanced optimization is disabled. Developer options background limit is at standard. I've pinned the apps in recent apps and it still happens. Apps get killed all the time.
For example,
1. I use Google Fit to start tracking a run. Within 10 minutes of tracking, the app is closed and workout not tracked. Its not even like i touched the phone and opened other apps during this.
2. I have VoIP account setup in the default dialer. Calls come through only 50% of the time cause the dialer is closed.
3. YouTube Music, constantly gets closed if i simply pause the music. Within 2 minutes, the app is closed.
4. Trying to transfer 15GB of files through Explorer app from phone to file server, never succeeds if i don't watch the app and keep the screen on.
5. Plex gets closed and therefore my photos don't auto backup with the phone is plugged in.
This is absolutely ridiculous! Why the hell a phone with 8GB of RAM is killing apps is beyond me!
Custom ROM on the same phone, like Lineage OS, no issues. Can have optimization on, battery manager on and all. In fact, battery life is better on custom when its not killing the apps! Seems to be the only solution until OOS can stop killing apps so aggressively.
Click to expand...
Click to collapse
My app is not killed when i lock it in the switch app menu
There's a whole website regarding that issue on several devices, maybe it helps: dontkillmyapp(dot)com/general#user-solution
Is there a way to prevent an app from ever being killed? I have 2 examples:
1) Fitbit app (background sync service, specifically) - when this stops running, some features on my watch quit working until I launch the app and sync manually.
2) Battery monitor app - I've tried AccuBattery (my preferred app), GSam, and BBS, but they all get killed and restart, and therefore give inaccurate information. BBS doesn't die as often as the others, but I don't like it as well. All 3 have persistent notifications, so I can tell when they last restarted.
I've set Battery Optimization to "Don't Optimize" for all of these. I've tried turning off all 3 of the settings under Advanced Optimization (probably unnecessary, no noticeable difference). I've also Locked each of these from recent apps. Are there any other settings I'm missing that could prevent an app from being killed? Possibly something new to Android 11? Fitbit and AccuBattery worked fine on my previous OP7P with Android 10.
terlynn4 said:
Is there a way to prevent an app from ever being killed? I have 2 examples:
1) Fitbit app (background sync service, specifically) - when this stops running, some features on my watch quit working until I launch the app and sync manually.
2) Battery monitor app - I've tried AccuBattery (my preferred app), GSam, and BBS, but they all get killed and restart, and therefore give inaccurate information. BBS doesn't die as often as the others, but I don't like it as well. All 3 have persistent notifications, so I can tell when they last restarted.
I've set Battery Optimization to "Don't Optimize" for all of these. I've tried turning off all 3 of the settings under Advanced Optimization (probably unnecessary, no noticeable difference). I've also Locked each of these from recent apps. Are there any other settings I'm missing that could prevent an app from being killed? Possibly something new to Android 11? Fitbit and AccuBattery worked fine on my previous OP7P with Android 10.
Click to expand...
Click to collapse
I have try to to go to developer mode and go to standby application. go inside and set the app you want to always on to active and remember still set battery to don't Optimize and locked the app. Do not click the clear all button.
fifasax said:
I have try to to go to developer mode and go to standby application. go inside and set the app you want to always on to active and remember still set battery to don't Optimize and locked the app. Do not click the clear all button.
Click to expand...
Click to collapse
Interesting, I haven't seen that before. Thanks for introducing me to something new. All of the apps in question are currently grayed out and say Exempted, so they shouldn't ever be put into standby.
Disable all power management*, Android does fine without it. Address any remaining power hogs individually on a case by case basis.
Power management will cause erratic behavior and can even increase battery usage even after its lame "adjustment" period.
To check if it is fully disabled go to Developer options>Standby apps, all buckets should show to be in their active state (and can't be manually assigned), if not power management is enabled.
Make sure allow background usage isn't disabled on the apps you want to run.
*yeah turn all those optimizing toggles OFF.
Only fast charging should be toggled on if you use it.
blackhawk said:
Disable all power management*, Android does fine without it. Address any remaining power hogs individually on a case by case basis.
Power management will cause erratic behavior and can even increase battery usage even after its lame "adjustment" period.
To check if it is fully disabled go to Developer options>Standby apps, all buckets should show to be in their active state (and can't be manually assigned), if not power management is enabled.
Make sure allow background usage isn't disabled on the apps you want to run.
*yeah turn all those optimizing toggles OFF.
Only fast charging should be toggled on if you use it.
Click to expand...
Click to collapse
How does one disable all power management? I don't see any sort of global switch for that. Turning it off entirely seems drastic, but I agree that power management is generally more trouble than it's worth.
I did verify that the apps in question are allowed to run in the background and use unlimited data.
terlynn4 said:
How does one disable all power management? I don't see any sort of global switch for that. Turning it off entirely seems drastic, but I agree that power management is generally more trouble than it's worth.
I did verify that the apps in question are allowed to run in the background and use unlimited data.
Click to expand...
Click to collapse
It seems like you're setting up right. Check the Stand by apps status.
When you first load Accubattery it gives an option to disable task killing in settings, Pro version.
Uninstalling then reinstalling it sometimes works for me; clearing its data does not. I was getting the same error message until I just reinstalled it
Just don't take Accubattery too seriously... it's useful up to a point.
I'm on Pie. Google really screwed up 10 and especially 11... so yeah it could something new as Google insists on changing things even if they're already nearly perfect
If that fails check with Accubattery for guidance with 11. They are responsive to emails.
They may also be punching out an update.