Database Users

Android OS stay awake time very long

My Android OS is showing a stay always time of over 17 hours (out of a 20 hour run time where my battery is completely depleted). Is there anyway I can find out what cause it?
I am already on 4.2.2

elty123 said:
My Android OS is showing a stay always time of over 17 hours (out of a 20 hour run time where my battery is completely depleted). Is there anyway I can find out what cause it?
I am already on 4.2.2
Click to expand...
Click to collapse
Android os = apps . Facebook maybe ?

You're experiencing wakelocks. Might wanna do some research on the forum so that you can post logs for people to analyze what's really eating your battery.

Sfkn2 said:
You're experiencing wakelocks. Might wanna do some research on the forum so that you can post logs for people to analyze what's really eating your battery.
Click to expand...
Click to collapse
THIS. I was having problems with wakelocks and traced them back to these few things below which got my battery life to greatly increase once disabled.
1) using dashclock extensions like FB and gmail
2) leaving google sync on in settings for the various google services
3) corporate email exchange servers
4) setting a long time variable for the phone to lock after the screen turns off (i did this to prevent putting in a pin to unlock but it kept the phone awake after the screen turned off)
5) live wall papers
There is also a known issue in the stock kernel that causes the phone to stay awake when it is supposed to go into sleep mode during extended periods of inactivity. This can be solved by using a custom kernel just as Franco r90 which has implemented patches in order to allow the phone to go into sleep to preserve battery. It is expected to be fixed in the next official OTA from google although this was also expected to be in 4.2.2 and was not fixed fully.

Same issue here. 4.2.2 stock kernel+rom, rooted
BBS shows "suspend_backoff" is at 45% no idea what's causing that.
Disabled pretty much all of the sync services but no improvement.
Interestingly right after the 4.2.2 update, the battery life was good.

Download this app and it will keep your applications from running in the background.
https://play.google.com/store/apps/...GwsMSwxLDMsImNvbS5vYXNpc2ZlbmcuZ3JlZW5pZnkiXQ..
Here's the forum for the application.
http://forum.xda-developers.com/showthread.php?t=2155737

scream4cheese said:
Download this app and it will keep your applications from running in the background.
https://play.google.com/store/apps/...GwsMSwxLDMsImNvbS5vYXNpc2ZlbmcuZ3JlZW5pZnkiXQ..
Here's the forum for the application.
http://forum.xda-developers.com/showthread.php?t=2155737
Click to expand...
Click to collapse
So far so good! totally eliminated the suspend_backoff wakeup

akiv said:
So far so good! totally eliminated the suspend_backoff wakeup
Click to expand...
Click to collapse
Update: Worked for a day now suspend_backoff is back. Happened after a recharge.
Could it be that afther the phone is charged something gets changed.
Edit: Runnig franco r90 kernel

I'm having the same problem with the Android OS draining lots of battery. When I reboot it sometimes helps but not consistently unfortunately.

Jester23 said:
I'm having the same problem with the Android OS draining lots of battery. When I reboot it sometimes helps but not consistently unfortunately.
Click to expand...
Click to collapse
I have narrowed my problem down to places where I use wifi transmitted by a lot of routers (Office wifi)

akiv said:
I have narrowed my problem down to places where I use wifi transmitted by a lot of routers (Office wifi)
Click to expand...
Click to collapse
I turn off my wifi when not home so I don't think that's the issue here.. I've tried removing a few apps like dash clock and my live wallpaper to see if it helps my issue. Will report back.
Sent from my Nexus 4 using Tapatalk 2

Google play services has something to do with the high usage. Yesterday I was near 20% usage today I disabled it and android os is at 7%. It only affects YouTube app for me, but the browser version is fine. I haven't seen any adverse affects other than maybe losing updates to the play store and ota updates which I don't care about because that's what xda and Roms are for. Now it may be placebo, but it also seems like the ui is smoother. Battery has improved greatly with sot of 3 hours with 57% left.

Hi,
how do you disable Google play services?

Try using the app greenify if your rooted.. It's been helping my battery life. Use it on maps and that will help. If maps is set as a system app, move it or just install banks minimal gapps so you can download from play store.
Sent from my Nexus 4 using xda app-developers app

[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

[Q][I9505] No deep sleep - msm_hsic_host

Hi everyone. I managed to get my hands on a beautiful blue I9505, had some issues while SIM unlocking it, but that's done and I am enjoying the phone very much.
Now, I do have a problem with it. The thing is, it simply will NOT go to deep sleep. Constantly hovering on 384 MHz with msm_hsic_host using a massive 90+ percent of awake time. It is driving me nuts. Our colleagues and friends over at Nexus 4 forums had an identical issue, and I read 57 pages of posts and used all their tips and tricks. Nothing helped.
Attached to this post you can see:
- the original Nexus 4 forum topic - [Q] msm_hsic_host - Nexus 4 forums
- The Google Code page where people complained about this - Google Code - Issue 41855 - "msm_hsic_wakelock" process on Nexus 4 causes severe battery drain
- my battery usage and BBS stats - attached to this post
- Qualcomm's fix for the issue - link 1 and link 2 at Code Aurora
I can't make heads or tails of any of this. The only thing that remains to do today (which I will do) is to flash a custom ROM and kernel for my I9505.
Thanks to anyone who will chime in to this discussion.

Bump - nobody else has this problem? Can you at least share your configurations so I can experiment a bit?

robogo1982 said:
Bump - nobody else has this problem? Can you at least share your configurations so I can experiment a bit?
Click to expand...
Click to collapse
99% chance that some app you installed is causing the wakelock. Install BetterBatteryStatts to determine wich app causes deep sleep/wakelock issues.

gee2012 said:
99% chance that some app you installed is causing the wakelock. Install BetterBatteryStatts to determine wich app causes deep sleep/wakelock issues.
Click to expand...
Click to collapse
I do have BBS as can be seen on the screenshots. I can't find the culprit since I believe it's the system itself.

I had this problem and it turned out to be avg pro app keeping it awake
Sent from my GT-I9505 using xda app-developers app

steveharris87 said:
I had this problem and it turned out to be avg pro app keeping it awake
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
I don't have such an app. Wakelock detector reports no odd stuff.

robogo1982 said:
I don't have such an app. Wakelock detector reports no odd stuff.
Click to expand...
Click to collapse
Wakelock couldnt find anything on mine either I just had a feeling it was that app so I removed it and it started going in to deepsleep I also had a problem with maps keeping my phone awake.
Sent from my GT-I9505 using xda app-developers app

robogo1982 said:
I don't have such an app. Wakelock detector reports no odd stuff.
Click to expand...
Click to collapse
clear dalvik cache and see again if it does enter Deep sleep or not, as everyone said its an application if not it must be a setting like sync, scan, or even that damn old wifi advanced settings that kept usual phones awake... reconfigure.

Insomnia
My phone won't sleep, won't time out and tapping the power button won't shut off the display. This happened just after deleting bootsamsung.qng, samsungloop.qng and shutdown.qng.
I'd replace the three deleted files, but they just grew and replaced themselves minus the carrier logo. The Baseband version now says: unknown. I stopped and installed google maps, that didn't help.
The good news is, those pink blocks are gone. The bad, I did a factory reset and noticed my cell network connectivity is gone. Maybe that's the sloppy work cutting down the SIM, or maybe something else? I've reinserted that sucker a dozen times and no joy. Do you know if the phone will stay awake without cell service? Putting it in airplane mode doesn't help.
Any suggestions? Thanks for your consideration.
Build number: JDQ39.I9505XXUAMDC

REVERSiN said:
clear dalvik cache and see again if it does enter Deep sleep or not, as everyone said its an application if not it must be a setting like sync, scan, or even that damn old wifi advanced settings that kept usual phones awake... reconfigure.
Click to expand...
Click to collapse
Cleared Dalvik, will keep an eye out (though I don't know how can it help)...

Wiping Dalvik did not help. I will try a factory reset later this afternoon and let the phone be for an hour or so without any apps installed.

robogo1982 said:
Wiping Dalvik did not help. I will try a factory reset later this afternoon and let the phone be for an hour or so without any apps installed.
Click to expand...
Click to collapse
Same problem here, my msm_hsic_host accounts for ~99% of the wakelocks according to BBS, even when the phone is in airplane mode and Wifi is off.
I'm running stock MDC firmware & kernel, rooted though.

fizzefazze said:
Same problem here, my msm_hsic_host accounts for ~99% of the wakelocks according to BBS, even when the phone is in airplane mode and Wifi is off.
I'm running stock MDC firmware & kernel, rooted though.
Click to expand...
Click to collapse
Read this about the wakelock, has to do with bad/lower 3g connections:
http://www.google.nl/url?sa=t&rct=j...3jjunrjohBvz3zaNvrYSO5g&bvm=bv.46751780,d.d2k

Thanks for the link.
This seems to be a logical explanation, but I've disabled 3G, and it still happens.
Plus it happens when in airplane mode, without any (cell) activity. I'm pretty sure that the kernel isn't configured properly.
Is there a known kernel / stock firmware version where this problem is fixed?

It appears that I have solved my problem.
I reset the device to factory settings and then restored apps, 5 by 5 in 30 min intervals. I still haven't restored all my apps, but so far I restored some 80%, here is the current state of things.

Very interesting.
Please keep us posted once you find out which app caused the problems, or if the factory reset fixed it.
Did you freeze or uninstall any apps?
Did you remove the T-Mobile bloatware?

fizzefazze said:
Very interesting.
Please keep us posted once you find out which app caused the problems, or if the factory reset fixed it.
Did you freeze or uninstall any apps?
Did you remove the T-Mobile bloatware?
Click to expand...
Click to collapse
I froze the same apps I had frozen before. If I find the app that caused the problems, I will report back. So far it's all good, 6h of use and I'm at 87% battery, wifi and 3G always on
P.S. I have Wanam's 1.0 installed
EDIT: 22h30 min, 2h4min screen on time, 48% battery.
I'd say that's an okay result.

robogo1982 said:
I froze the same apps I had frozen before. If I find the app that caused the problems, I will report back. So far it's all good, 6h of use and I'm at 87% battery, wifi and 3G always on
P.S. I have Wanam's 1.0 installed
EDIT: 22h30 min, 2h4min screen on time, 48% battery.
I'd say that's an okay result.
Click to expand...
Click to collapse
What app was the problem?
I have a problem with this wakelock, use about 10-25% of battery time

Napalm Candy said:
What app was the problem?
I have a problem with this wakelock, use about 10-25% of battery time
Click to expand...
Click to collapse
You know what, I can't really say. Since the factory reset I restored all my apps and never had the problem since. Really weird issue. 25% can be bad. I had 99.4%

robogo1982 said:
You know what, I can't really say. Since the factory reset I restored all my apps and never had the problem since. Really weird issue. 25% can be bad. I had 99.4%
Click to expand...
Click to collapse
So, if I give you my app list, can you identificate what you used before wipe?
Maybe can will know what apps are potentially to reproduce the problem

Latest Google play services update is pissing me off

This is what I'm getting now since it updated just after Google i/o. I don't even know how to stop it. My battery has gone from 1+ days of usage to just about 16 hours with no other change. No new apps nothing. And these screenshots were taken after a reboot so I would imagine I'd have well over 1000 wakelocks from this thing. What's more look at the time stamps on the second and third images. Taken 7 minutes apart but I have 21 wakelocks in that short space of time.
Compare that to the wakelock crazy Facebook with only 11 in that same space of time. I don't even know what to do about this. Has never been this bad in my 2 months of owning the phone.
Any advice or recommendations to fix this? It's driving me crazy.
Also:
No I have no new apps.
No I didn't flash anything else.
My kernel was the same this entire time.
The phone gets mad hot for no reason.
Tried wakelock terminator on it but it only made it not want enter deep sleep all together.
Sent from my SM-N9005 using XDA Premium 4 mobile app

If you have a look around the forum and the internet, you'll notice every device from every brand has this issue. Sony has it worse, they dont even last 7 hours.
Turn off Google data backup, opt out of personalized apps and turn off location services.
You could always just disable Gplay services for now. I'm not rooted and I've done it.
Sent from my SM-N9005 using Tapatalk 2

ShadowLea said:
If you have a look around the forum and the internet, you'll notice every device from every brand has this issue. Sony has it worse, they dont even last 7 hours.
Turn off Google data backup, opt out of personalized apps and turn off location services.
You could always just disable Gplay services for now. I'm not rooted and I've done it.
Sent from my SM-N9005 using Tapatalk 2
Click to expand...
Click to collapse
How did you disable it ?

JJbdoggg said:
How did you disable it ?
Click to expand...
Click to collapse
Settings --> General --> Application Manager --> All --> Google Play Services --> Disable.

Google Play Services draining battery in 3G/4G

Under WiFi, my OnePlus 5 makes 5 or 5 hours and half of active screen. Under 3G instead, battery leasts really less (about 3 or 3 hours and half) because Google Play Services spends a lot of battery: the same of Display in percentage. I tried to reset my phone and to reinstall software from adb too. Any solution for this problem?

rirri said:
Under WiFi, my OnePlus 5 makes 5 or 5 hours and half of active screen. Under 3G instead, battery leasts really less (about 3 or 3 hours and half) because Google Play Services spends a lot of battery: the same of Display in percentage. I tried to reset my phone and to reinstall software from adb too. Any solution for this problem?
Click to expand...
Click to collapse
Get Wakelock Detector Lite from the playstore and figure out exactly what function of the Google Services rip your battery apart.
I would recommend rooting the phone and disabling your culprits (for me it was net scheduling, safe to turn off).
Sent from my ONEPLUS A5000 using Tapatalk

ipredatorv said:
Get Wakelock Detector Lite from the playstore and figure out exactly what function of the Google Services rip your battery apart.
I would recommend rooting the phone and disabling your culprits (for me it was net scheduling, safe to turn off).
Click to expand...
Click to collapse
I rooted my device and installed Wakelock Detector. Opening the app a toast message always says: "Failed ti perform this task at the moment, please try again". What can i do to make this app working?

rirri said:
I rooted my device and installed Wakelock Detector. Opening the app a toast message always says: "Failed ti perform this task at the moment, please try again". What can i do to make this app working?
Click to expand...
Click to collapse
I said Wakelock Detector LITE and not the rooted version. The rooted version is broken as the dev didn't update it yet.
Sent from my ONEPLUS A5000 using Tapatalk

If you rooted your device with Magisk there's a module that allows Google Play Services to go into doze mode--normally it's exempt. You can also install the Greenify module which allows more aggressive doze than stock Android. Or you could go the route of identifying and blocking specific wakelocks as the earlier poster suggested.

Ok, this is the report form Wakelock Detector (phone battery was at 22%). What should I do now?

rirri said:
Ok, this is the report form Wakelock Detector (phone battery was at 22%). What should I do now?
Click to expand...
Click to collapse
You got the same wakelocks as me. Luckily I got the perfect link for you. Follow the guide and you'll be good.
https://forum.xda-developers.com/oneplus-3/how-to/guide-stop-google-play-services-t3549760
Sent from my ONEPLUS A5000 using Tapatalk