Related
My battery will completely drain after <10 hours while the screen is off!
However I was able to find out thatquickgooglesearchbar is always the top app.
Those screenshots are a bit old but it's still the same thing, I did manage to root it today, and I was testing Greenify which did nothing even with the Xposed modules, service disabler apps just did not show that specific service for some reason. I was able to remove the widget with Xposed GEL settings but it was still running even though the widget wasn't there.
So can someone please help me out here, maybe the search bar isn't the problem but I just want some battery life.
h ttp://imgur.com/a/gdXKW
(I still can't post links sorry If this is against your forum rules but this is urgent)
Eidoss said:
My battery will completely drain after <10 hours while the screen is off!
However I was able to find out thatquickgooglesearchbar is always the top app.
Those screenshots are a bit old but it's still the same thing, I did manage to root it today, and I was testing Greenify which did nothing even with the Xposed modules, service disabler apps just did not show that specific service for some reason. I was able to remove the widget with Xposed GEL settings but it was still running even though the widget wasn't there.
So can someone please help me out here, maybe the search bar isn't the problem but I just want some battery life.
h ttp://imgur.com/a/gdXKW
(I still can't post links sorry If this is against your forum rules but this is urgent)
Click to expand...
Click to collapse
search and install betterbatterystats (read the whole first post) and it will tell you if its wakelocks etc.
Service disabler apps will need a setting to show system apps (or something similar) ticked or switched to etc.
greenify system apps in greenify also needs to be selected. You may also need to cut wake up paths to get it to stay greenified.
You could alternatively delete the apk of hibernate it (byfar the easiest option of all this).
Darke5tShad0w said:
search and install betterbatterystats (read the whole first post) and it will tell you if its wakelocks etc.
Service disabler apps will need a setting to show system apps (or something similar) ticked or switched to etc.
greenify system apps in greenify also needs to be selected. You may also need to cut wake up paths to get it to stay greenified.
You could alternatively delete the apk of hibernate it (byfar the easiest option of all this).
Click to expand...
Click to collapse
I don't need betterbatterystats, I have battery Battery Historian, check the screenshots, It's clearly the search bar, on my other phone It isn't shown as a top app.
Also I went in the system folder /apps and there was no googlesearchbar, or in any other system apk remover tool, perhaps it was removed by another app, but it's still for some reason running.
Eidoss said:
I don't need betterbatterystats, I have battery Battery Historian, check the screenshots, It's clearly the search bar, on my other phone It isn't shown as a top app.
Also I went in the system folder /apps and there was no googlesearchbar, or in any other system apk remover tool, perhaps it was removed by another app, but it's still for some reason running.
Click to expand...
Click to collapse
Your 3rd image shows googlequicksearchbox had 370ms (milliseconds) of wakelocks over a 9hr period. I really doubt that is your issue.
If it is your top app, then it is probably because of Google Now launcher listening for OK Google spoken keyword.
I seriously doubt that is your battery drain problem as almost 90% of people probably have OK Google turned on and are using Google Now launcher and only a very few have serious battery drain.
BTW wakelocks aren't the issue usually. In the past it has been "partial wakelocks" which means an app locked the device from sleeping, but never released the lock, so the device never goes to full sleep. If you see some app with partial wakelocks or if you see some app with hours of regular wakelocks then that might be an issue. Minutes or microseconds of wakelocks are inconsequential.
I suggest you flash factory image and install your battery tester only. Turn off wifi, bluetooth, nfc, cell radio. Test the drain overnight. That is a baseline for the minimum drain your device can have. Then enable what wireless stuff you normally have turned on. See what that drain is. Then start installing apps and see what that drain is.
If you have reasonable/expected battery drain with stock and everything turned off, then it is just a process of elimination to see what is causing your battery drain.
If you can't get reasonable/expected battery drain with stock and everything turned off, then you probably have a bad battery.
For the record, my overnight battery drain with everything turned off is 0-1% With wifi turned on about 1-2%. With wifi+cell about 2-3%.
IMO the biggest drains for standby are wifi and/or cell signal related. Either bad signals or apps sending data in background or apps that are polling all the time.
sfhub said:
Your 3rd image shows googlequicksearchbox had 370ms (milliseconds) of wakelocks over a 9hr period. I really doubt that is your issue.
If it is your top app, then it is probably because of Google Now launcher listening for OK Google spoken keyword.
I seriously doubt that is your battery drain problem as almost 90% of people probably have OK Google turned on and are using Google Now launcher and only a very few have serious battery drain.
BTW wakelocks aren't the issue usually. In the past it has been "partial wakelocks" which means an app locked the device from sleeping, but never released the lock, so the device never goes to full sleep. If you see some app with partial wakelocks or if you see some app with hours of regular wakelocks then that might be an issue. Minutes or microseconds of wakelocks are inconsequential.
I suggest you flash factory image and install your battery tester only. Turn off wifi, bluetooth, nfc, cell radio. Test the drain overnight. That is a baseline for the minimum drain your device can have. Then enable what wireless stuff you normally have turned on. See what that drain is. Then start installing apps and see what that drain is.
If you have reasonable/expected battery drain with stock and everything turned off, then it is just a process of elimination to see what is causing your battery drain.
If you can't get reasonable/expected battery drain with stock and everything turned off, then you probably have a bad battery.
For the record, my overnight battery drain with everything turned off is 0-1% With wifi turned on about 1-2%. With wifi+cell about 2-3%.
IMO the biggest drains for standby are wifi and/or cell signal related. Either bad signals or apps sending data in background or apps that are polling all the time.
Click to expand...
Click to collapse
Factory reset didn't do anything a few days ago, the results were exactly the same that was when my phone wasn't rooted, so I guess I should return the phone, and get a new one?
Eidoss said:
Factory reset didn't do anything a few days ago, the results were exactly the same that was when my phone wasn't rooted, so I guess I should return the phone, and get a new one?
Click to expand...
Click to collapse
What is your battery drain per hour with nothing installed and all wireless turned off and everything stock?
I'd only return it if that is significantly more than 0-.2% or 1% every 5 hours.
Otherwise it is something you have installed or something to do with the signal and how it interacts with your phone.
Once you start installing stuff or turning on wireless (wifi/bt/cell) then it is no longer purely about the battery and there are more factors that need to be isolated independently.
You really need to establish a baseline to see what the minimum battery drain is. Then you can determine if the battery is the problem or something else.
If you just install everything and turn everything on, there are too many moving parts.
sfhub said:
What is your battery drain per hour with nothing installed and all wireless turned off and everything stock?
I'd only return it if that is significantly more than 0-.2% or 1% every 5 hours.
Otherwise it is something you have installed or something to do with the signal and how it interacts with your phone.
Once you start installing stuff or turning on wireless (wifi/bt/cell) then it is no longer purely about the battery and there are more factors that need to be isolated independently.
You really need to establish a baseline to see what the minimum battery drain is. Then you can determine if the battery is the problem or something else.
If you just install everything and turn everything on, there are too many moving parts.
Click to expand...
Click to collapse
Okay, I now have android N, and my battery life seems to be better, I will leave mobile data off. I will see tomorrow if my battery life has changed.
Do you think I should use Adaptive brightness for more battery life?
Eidoss said:
Okay, I now have android N, and my battery life seems to be better, I will leave mobile data off. I will see tomorrow if my battery life has changed.
Do you think I should use Adaptive brightness for more battery life?
Click to expand...
Click to collapse
Which battery life was the one you think you have a problem with, standby or in use? IMO for in use battery time this phone is about average. Your title of "wakelock" made it seem like you were concerned about standby battery time as it doesn't matter if there is a wakelock if the device is already turned on and in active use.
When turned on, the screen is probably the number one thing eating power, so adaptive brightness could help, but if you are in a bright area, it might be worse than if you fixed the brightness below max.
Even if you have adaptive brightness turned on, the slider scale still is useful as you give the adaptive brigthness mechanism some idea what level of brightness you feel comfortable when the mechanism detects dark, med, bright situations.
One of the worse things for eating power is for the cell radio to be turned on but have no signal, like inside office building or just a bad signal area in general. The reason is the cell radio is power efficient once it establishes signal, but when it is searching for (or loses) signal it uses a lot of power.
If you are doing a lot of disk activity like taking video or hdr pictures, it would probably help to have your userdata unencrypted as this device does software (kernel) encryption and doesn't use the fast/more power efficient co-processor.
sfhub said:
Which battery life was the one you think you have a problem with, standby or in use? IMO for in use battery time this phone is about average. Your title of "wakelock" made it seem like you were concerned about standby battery time as it doesn't matter if there is a wakelock if the device is already turned on and in active use.
When turned on, the screen is probably the number one thing eating power, so adaptive brightness could help, but if you are in a bright area, it might be worse than if you fixed the brightness below max.
Even if you have adaptive brightness turned on, the slider scale still is useful as you give the adaptive brigthness mechanism some idea what level of brightness you feel comfortable when the mechanism detects dark, med, bright situations.
One of the worse things for eating power is for the cell radio to be turned on but have no signal, like inside office building or just a bad signal area in general. The reason is the cell radio is power efficient once it establishes signal, but when it is searching for (or loses) signal it uses a lot of power.
If you are doing a lot of disk activity like taking video or hdr pictures, it would probably help to have your userdata unencrypted as this device does software (kernel) encryption and doesn't use the fast/more power efficient co-processor.
Click to expand...
Click to collapse
Standby is the problem, on screen times are good enough.
Anyway, I don't even know what to do at this point. Android N didn't help enough (cell data is off), I guess I can flash Android 6.0 again and then try to fix it using apps...
What do you suggest I should do, I'm out of ideas at this point.
Eidoss said:
Standby is the problem, on screen times are good enough.
Anyway, I don't even know what to do at this point. Android N didn't help enough (cell data is off), I guess I can flash Android 6.0 again and then try to fix it using apps...
What do you suggest I should do, I'm out of ideas at this point.
Click to expand...
Click to collapse
What is the power drain over a couple of hours with *no apps installed* completely stock, and wifi/cell turned off? What is the change when wifi is turned on?
Eidoss said:
What do you suggest I should do, I'm out of ideas at this point.
Click to expand...
Click to collapse
Have you set "WiFi on during sleep" to "Never"? in the Advanced WiFi settings?
In the original release, there was a bug where WiFi would stay on even if you had set it to "Never" draining battery in standby.
Somewhere between MDA89E and MHC19Q they fixed it and WiFi will go to deep sleep after being in standby for a while, but they introduced another (or exposed existing) bug where WiFi will not resume after coming out of sleep, unless you cycle WiFi off/on. So you're standby battery should be better with this setting, but it'll be a little more annoying when turning on your device.
Guys got my OP3 few days back but what I'm noticing is that after 2-3 days that my Android System is higher then Screen usage which wasn't before. Never facing this kind of drain before on OP3 or on my Nexus 5 that I used to use before. Is there anything unusual? I'm attaching screenshot of better battery stats also please do look into them.
Anyone ?
I had the same issue resulting in terrible battery life since Android System was constantly working the CPU. It's probably due to the Oxygen OS kernel. I sent back my unit and asked for a replacement because I didn't want to install a custom ROM on a brand new phone just yet.
Same issue here, Android System uses more battery than my screen. Also it looks like the phone was awake all night tonight with screen off, so I had more standby drain.
This is most likely due to an app that has a rogue process running in the background constantly keeping gms awake. Try clearing data for the play store and turning off sync for any apps you have. See the drain overnight and report back.
Same problem here... "Android-System" is consuming the highest amount of all my other apps ...
My OP3 has a lifetime of about 6-8 hours ...
Yeah even it's the same for me... Even did a factory reset but didn't help
Sent from my ONEPLUS A3003 using Tapatalk
Facing the same problem. Amplify Forcedoze and Greenify don't help
Turn off the auto sync. I am consistently getting 8hrs SOT. Using LTE and wifi.
Sent from my ONEPLUS A3003 using Tapatalk
nickporwal said:
Turn off the auto sync. I am consistently getting 8hrs SOT. Using LTE and wifi.
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
when you turn off auto sync, does whatsapp still work without having to manually sync every now and then? afaik, most of the social apps rely on this sync to function properly and having to manually sync every time for whatsapp or twitter would defeat its purpose.
sahirhussain said:
when you turn off auto sync, does whatsapp still work without having to manually sync every now and then? afaik, most of the social apps rely on this sync to function properly and having to manually sync every time for whatsapp or twitter would defeat its purpose.
Click to expand...
Click to collapse
Whatsapp doesn't use sync to fetch messages. Sync is for syncing contacts on Whatsapp
guys try disabling ambient mode and see if that lowers the android system drain.
i'm checking it myself on my op3
That does not work for me. I have everything disabled - daydreams, ambient, proximity wake, Google now, now on tap, auto sync, oneplus launcher but android system continues to take up more battery even when the screen is off.
The Opskin package is included in Android system, maybe rendering the ui drains more battery
I think I fixed this by disabling "location" and/or "location determination" (DE: Standortbestimmung)
cruzs said:
I think I fixed this by disabling "location" and/or "location determination" (DE: Standortbestimmung)
Click to expand...
Click to collapse
Nope ... not fixed
Hi there,
Please look at the attached screenshot. The red area shows the time I was sleeping. The phone was stationery all night long. It shouldn't decrease like that, right? It should show something more horizontal if Doze is actually working, right? I believe I read something about this somewhere on these forums.
Yes, I do have "WiFi: Always On" enabled. Is that the problem?
My thinking is that I want WiFi always turned on, but I also want Doze. Meaning, if the phone is stationery, not doing anything, it should kick Doze in (which will periodically check for stuff, temporarily turning on/off the WiFi). Is this thinking wrong? If I have "WiFi: Always On" disabled, will Doze work properly and I'll still be notified of any push notifications and whatnot?
What am I missing here?
First off, there are no screenshots. Doze mode is supposed to remove wifi scans and wifi connection regardless if wifi is on. You will get a periodically sync with emails and push notifications( they will be delayed). You will also still recieve sms and mms. How steong is the network connection? Maybe with a weak connection that is what is draining battery.
schmeggy929 said:
First off, there are no screenshots. Doze mode is supposed to remove wifi scans and wifi connection regardless if wifi is on. You will get a periodically sync with emails and push notifications( they will be delayed). You will also still recieve sms and mms. How steong is the network connection? Maybe with a weak connection that is what is draining battery.
Click to expand...
Click to collapse
Sorry, just keep forgetting attachments... Please check the first post again. No, I don't think my connection at home is a weak one. I am connected to a 5GHz network instead of 2.4GHz one. Not sure if that's relevant.
Nazgulled said:
Sorry, just keep forgetting attachments... Please check the first post again. No, I don't think my connection at home is a weak one. I am connected to a 5GHz network instead of 2.4GHz one. Not sure if that's relevant.
Click to expand...
Click to collapse
i think wifi on does prevent from doze and gives wake locks for many... tried by turning off wifi for a night to narrow down the issue?
i might be wrong here but that was afeedback from many users the battery leak/wake locks with wifi always on
SacredDeviL666 said:
i think wifi on does prevent from doze and gives wake locks for many... tried by turning off wifi for a night to narrow down the issue?
Click to expand...
Click to collapse
Not yet, I'll have to try that... However, it doesn't make much sense to me to have it off. I mean, if it's off, even in the doze open windows, wifi will be off, and I won't get any notifications at all unless I turn the screen on. Not a very good user experience. But I'll test it nonetheless to narrow down possible issues.
You may be suffering from the bug discussed here: http://forum.xda-developers.com/htc-10/how-to/wifi-constant-suspend-resume-leading-to-t3392562
At the last page is a kernel that has a fix that seems to be working.
Try out GSam Battery Monitor for some stats.
tkoreaper said:
You may be suffering from the bug discussed here: http://forum.xda-developers.com/htc-10/how-to/wifi-constant-suspend-resume-leading-to-t3392562
At the last page is a kernel that has a fix that seems to be working.
Click to expand...
Click to collapse
Based on your post these seem are most likely the same issue. I just flashed the fix from that thread and it helped TONS. It is still being tweaked before it goes to elementalx officially, but it is working great for me so far!
Yeah, it might be that issue, or not, I'm not really sure. But I used the GSam Battery Monitor app suggested above and I don't think the problem is Doze.
I used that app and start monitoring just before I went to sleep. I've also used ForceDoze just to be sure Doze kicks in (this app will force Doze immediately on screen off instead of just stationery and waiting 30mins). Look at the screenshots. Something is not right, my phone doesn't deep sleep, it's awake all the time.
schmeggy929 said:
..... Doze mode is supposed to remove wifi scans and wifi connection regardless if wifi is on. You will get a periodically sync with emails and push notifications( they will be delayed). You will also still recieve sms and mms.
Click to expand...
Click to collapse
What? Doze is supposed to remove wifi Scans?
If you take a look at the blue "WiFi Scan" line you see the same pause between intervals before doze kicks in as while doze is active.
Doze Mode hasn't really helped me getting less Wakelocks or less battery drain on this device. I just get the feeling there are way to many system/kernel related wakelocks due to HTC's crappy software which ignore doze mode
Oh yeah, the Wifi signal strength was really bad there.... simply because the phone decided NOT to switch to the stronger Network with the same SSID.... well thank you android....
I've used Greenify (which has a notification for Doze mode statistics) and other battery stats apps and I've realized that Doze is in fact working... So, my battery problems are something else.
I just don't get that flat battery graph when doze mode is active, but it must be due to something else...
Thanks everyone that pitched in Save
Nazgulled said:
I've used Greenify (which has a notification for Doze mode statistics) and other battery stats apps and I've realized that Doze is in fact working... So, my battery problems are something else.
I just don't get that flat battery graph when doze mode is active, but it must be due to something else...
Thanks everyone that pitched in Save
Click to expand...
Click to collapse
To me it look as though a rouge app could be the culprit.
Have you tried a removing all apps, or doing a clean flash of whatever ROM your on, and if not rooted, an RUU flash and then see if the phone works as should, then this sucks, but you install apps 1 but 1 until you find out which on is the bad apple.
Your phone is def being held awake though by that Gsam battery chart.
I haven't done that and I'm not going to. I don't have time for debugging this issue like that, I need a working phone with the apps I use.
Not trying to sound rude or anything, I know you're just trying to help and I appreciate that. But I just can't do what you're suggesting.
Anyway, shouldn't some battery app help with that. I'm now using BetterBatteryStats. If there's a rogue app, that should allow me to pinpoint the sucker...
i am having crazy active (27%) and idle (5%) battery drain. using ex kernel manager i can see different wakelocks. i hsve been screwing around with them and haven't made any real progress. is the flash 2.05 still very battery efficient? id my problem isn't solved will ex kernel manager still work for this kernel to set wakelocks, governors, etc? do you recommend another kernel manager instead. i downloaded the wake locks detector app and every time i opened it it just said "failed to complete task at this time." it had SU rights. idk whst the problem was. im having a hard time finding whats all of a sudden doing this to my battery. i did flash some launcher mods. this started right after that. last night i reflashed the developers stock launcher and things looked great. now theyre back at being bad. would a factory reset in twrp allow me to save my data and maybe fix the issue? please help
What apps can I use without wake lock dector functioning. Could I have a virus stopping it from functioning?
Check your cpu consumption. Use exkernel manager or some other tool for the same.
Sent from my Pixel 2 XL using Tapatalk
Here's what I'm seeing. Google photos looks to be the culprit. I need that app. What should I do? Uninstall updates and reinstall them? I cleaned the cache for the app but they still stayed at the same levels shown here. Cpu is usually running at 300MHz. It's not shown in the screen shot, but most the of the other cpu consumption is at 1.9GHz. it's like 9% or something. What do I do with google photos?
Schroeder09 said:
Here's what I'm seeing. Google photos looks to be the culprit. I need that app. What should I do? Uninstall updates and reinstall them? I cleaned the cache for the app but they still stayed at the same levels shown here. Cpu is usually running at 300MHz. It's not shown in the screen shot, but most the of the other cpu consumption is at 1.9GHz. it's like 9% or something. What do I do with google photos?
Click to expand...
Click to collapse
Edit: i stopped a backup of some stuff on Google photos and the drain is still the same. It's not backup causing the issue. Something else with the app is doing this.
Have you tried clearing its data and cache so you get a fresh start, so to speak?
Sent from my Pixel 2 XL using XDA Labs
Did last night and it didn't seem to help.
So better battery stats seems to be telling me that google photos is the problem. I use the app so this sucks. Otherwise I would have just uninstalled it. Can I use adb shell commands to disable its wake lock? If I do that, I'm guessing it will not upload pics and videos to Google drive UNLESS my screen is ON, right?
TK has this (
) YouTube video showing what I am asking. Keep in mind I actually AM rooted. I don't see any options in batter battery stats to disable wakelocks. It just detects them.
I would again ask To check cpu consumption
Sent from my Pixel 2 XL using Tapatalk
Here is a pic of the cpu stats. Everything above it is very small or 0% cpu seems to be where it should
Schroeder09 said:
Here is a pic of the cpu stats. Everything above it is very small or 0% cpu seems to be where it should
Click to expand...
Click to collapse
Thanks, is it for small or bigcluster.
Sent from my ONEPLUS A3003 using Tapatalk
Guess what!? It appears that the photos app was just trying to upload stuff to my Google drive. Since my internet is so horrible it took literally days. Once the uploads completed my battery drain returned to normal!!
Now I'm seeing this. What is going on. Seems like after every update or the littlest thing, or even out of the blue, battery drain occurs. I just flashed EX kernel 1.01,did some various updates in the playstore, and flashed some launcher mods.
I was seeing like 8% active drain and .5-.7% idle drain on EX 1.0 and only sharkie launcher mods. Now SOT sucks and so does my battery.
I had the same problem till I turned off instant tethering. Helped my battery life significantly for some reason. Doesn't really make sense.
(Settings -> Google -> Instant Tethering)
shadowster said:
I had the same problem till I turned off instant tethering. Helped my battery life significantly for some reason. Doesn't really make sense.
(Settings -> Google -> Instant Tethering)
Click to expand...
Click to collapse
I didn't make any changes there before or after updating though. Here's what I have in my tethering settings.
I had this tethering acceleration on,but it was on when I was getting awesome battery life too.
And what about these kernel wake locks? Is there actually an app that blocks wake locks? Wake lock detector would never work for me for whatever reason. Better battery stats seems to identify wake locks but it doesnt give you any way to actually do anything about the wake locks.
By instant tethering, I didn't mean the tethering in the Network and Internet part. I attached a few images that might make it clearer. (Settings->Google->Instant Tethering). I think this helped cause I keep bluetooth on a lot.
If I recall correctly, powermanagerservice wakelock is the catch all for all the partial wakelocks, and power manager display is just however long the display has been on.
Wifi scanning and BT scanning were both back on(previously turned off) for me after the JAN update.
shadowster said:
By instant tethering, I didn't mean the tethering in the Network and Internet part. I attached a few images that might make it clearer. (Settings->Google->Instant Tethering). I think this helped cause I keep bluetooth on a lot.
If I recall correctly, powermanagerservice wakelock is the catch all for all the partial wakelocks, and power manager display is just however long the display has been on.
Click to expand...
Click to collapse
Thanks for the reply. I found what u we're talking about with those pictures. Instant tethering under google was not on. I want wifi scanning on but I don't want the BT scanning on, and it didn't turn back on after the January update for me.
Without wifi scanning will wifi work with only the toggle button in the notification drop down menu? I thought they both had to be on
My battery is **** since 8.1, glad I found these options thanks to you guys.
I lose 20% battery life for 1 hr of SOT, super bad. I'll let you know if it improves.
Schroeder09 said:
Thanks for the reply. I found what u we're talking about with those pictures. Instant tethering under google was not on. I want wifi scanning on but I don't want the BT scanning on, and it didn't turn back on after the January update for me.
Without wifi scanning will wifi work with only the toggle button in the notification drop down menu? I thought they both had to be on
Click to expand...
Click to collapse
It always has for me and I have disabled this on every phone i've had that has this option. Its more location services.
Hello everybody,
sorry to bother this community, but I have a weird issue with the phone. My nephew gave me the Motorola G7 Play and when I am under any wifi (tried many) I do not received any notification. This does not happen immediately, but after the screen remains off for at least 30 minutes.
As advised from the assistance we have reset the phone at least twice and nothing has changed.
Do you have any idea if there are any tricky setting or application that are causing the issue?
Please, let me know if there is a quick fix, otherwise I will keep using 4G only as I am doing at the moment, this way there are no issues at all.
Have a nice day,
Cosetta
It might be memory management or there is a battery optimization setting that sends the phone to sleep when using wifi to conserve battery... Take a look deeper in the settings and perhaps turn off battery optimisation for apps that you need to keep receiving notifications for.