Related
Hey,
I'm running stock nexus 4. I have been having terrible 8 hour battery life with "Android OS" taking up all the battery in battery status. BetterBatteryStats tells me that "sns_perioidic_wakelock" and "sns_async_ev_wakelock" is using up most of the battery. See attached. Any idea what apps are causing this?
http://i.imgur.com/t1gAr.png
thegreyspot said:
Hey,
I'm running stock nexus 4. I have been having terrible 8 hour battery life with "Android OS" taking up all the battery in battery status. BetterBatteryStats tells me that "sns_perioidic_wakelock" and "sns_async_ev_wakelock" is using up most of the battery. See attached. Any idea what apps are causing this?
Click to expand...
Click to collapse
I'm pretty sure I've seen those wakelocks when making a lot of phone calls. Seems likely related to cell radio use some how, but that's just a guess.
mattb3 said:
I'm pretty sure I've seen those wakelocks when making a lot of phone calls. Seems likely related to cell radio use some how, but that's just a guess.
Click to expand...
Click to collapse
Actually the crazy thing is that i have airplane mode with wifi on most of the day cause I have really bad service. And I only have 100 minutes of talk, so I never talk on the phone.
thegreyspot said:
Actually the crazy thing is that i have airplane mode with wifi on most of the day cause I have really bad service. And I only have 100 minutes of talk, so I never talk on the phone.
Click to expand...
Click to collapse
Just checked mine and those wakelocks are really low today despite several phone calls, I've been on wifi all day though. The right way to figure those wakelocks out is to download the kernel source from one of the devs github and do some searches through the source to see where those wakelocks are logged. You might also search the battery impression thread in general, some smart folks have dissected many kernel wakelocks in there. Seems weird that you would have them in airplane mode.
thegreyspot said:
Actually the crazy thing is that i have airplane mode with wifi on most of the day cause I have really bad service. And I only have 100 minutes of talk, so I never talk on the phone.
Click to expand...
Click to collapse
I have the exact same issue. Wakelocks/Android OS killing my battery (Android OS usually 45% or higher when it should be my screen that is the biggest battery sucker).
I barely use my phone to make phone calls as well. I'd say 1 call every 2 or 3 days.
Same exact wakelocks here. I made 0 phone calls. There is defiantly something up.
I had these two wakelocks too and it turned out to be my live wallpaper that was causing it
http://forum.xda-developers.com/showpost.php?p=35277041&postcount=20
Same wakelocks on my N4....
Solution in my case, delete widget locker....... My Nexy sleeps again:angel:
exact same situation: N4, sns wakelocks killing battery, phone not deep sleeping. culprit? Shake 'n Rotate! app. so add that one to the blacklist as well!
Are any of you running stock kernel and ROM?
Sent from my Nexus 7 using Tapatalk 2
Im Running stock kernal and Rom and i still get sns_periodic_wakelock and sns_async_ev_wakelock Does anyone have any idea what they are or what causes them or how to fix? They seem to be on the whole time my phone is on and they suck battery crazy not as bad as most but my android os is always 2nd battery use to my screen or more depending on how i use it and it sucks cause i know i would have pretty awesome battery life if these were fixed or gone. I appreciate any help!
Apparently you can also add: lightflow vibrate on pickup feature and adding a widget to the lock screen..
PowerManagerService and sns periodic wakelock are my main culprits but I'm not sure these numbers mean there's an issue or not...
I just checked BBS for todays use and I have on 9h use 4h on sns_periodic_wakelock. I have been using DashClock on my lockscreen. I will remove that and post back later to see if that helped.:cyclops:
Hmm can anyone say if this looks problematic?
Sent from my Nexus 4 using xda premium
Yes it does look problematic.
Basically sns_periodic_wakelock kept the device from sleeping for almost three hours.
I have the same issue and don't know what's causing it.
EDIT: Apparently live wallpapers do.
Just writing back to tell you guys how it went. I removed DashClock from my lockscreen and that wakelock seemed to be gone for a few days.
I then later updated the app, and just by updating it, I think it caused the wakelock. This time I'm uninstalling and checking if it comes back again.
Is there a known list of apps suspected of causing this?
dohkoxar said:
Just writing back to tell you guys how it went. I removed DashClock from my lockscreen and that wakelock seemed to be gone for a few days.
I then later updated the app, and just by updating it, I think it caused the wakelock. This time I'm uninstalling and checking if it comes back again.
Click to expand...
Click to collapse
I've had dashclock for the past two days.. Not seeing any wake locks. I have all the extensions from the app enabled.
Sns is related to facebook. If you use Titanium backup, go to apps and you can see a blue icon with a letter f on it that looks like facebook letter and labelled sns. Uninstall that and your lovely nexus 4 will enjoy its sleeeeep....
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
So after updating facebook and messenger (facebook) I've found huge wakelocks in bbs. Anyone else having this issue? It's related to some kind of bug reporting?
======================================================
Wakelocks (requires root / system app on Android 4.4+)
======================================================
*job*/com.facebook.orca/com.facebook.bugreporter.scheduler.LollipopService (com.facebook.orca.Messenger): 37 m 20 s Count:10 22.2%
*job*/com.facebook.katana/com.facebook.bugreporter.scheduler.LollipopService (com.facebook.katana.Facebook): 30 m 2 s Count:6 17.8%
Same here........I'm locking it down using the Amplify Xposed module.
Prey521 said:
Same here!
Click to expand...
Click to collapse
It's causing massive wake time if left alone for a few hours. I went ahead and limited the wakelocks in amplify. Set it to allow them every 10th hour on trial. We'll see if that causes any problem.
I noticed this too. I watch battery like a hawk but this is the first time Facebook had shown much drain in the last few months. This was build still 59.0.0.3.313
Looks like tonight's build still has the issue.
I recommend reporting in the Facebook app itself.
Sent from my A0001 using Tapatalk
dmo580 said:
I noticed this too. I watch battery like a hawk but this is the first time Facebook had shown much drain in the last few months. This was build still 59.0.0.3.313
Looks like tonight's build still has the issue.
I recommend reporting in the Facebook app itself.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I've disabled them both in amplify. I don't feel I want battery every spent on uploading any form of reports. I've also limited facebook wakelocks apart from this to every 15th minute. It's spending too much battery on something irrelevant.
Reported it already.
Even my fiancee's Galaxy S5 (which can usually get through to the end of the day with 65+% battery left) was saying that her battery has been draining very quickly.
So I know Facebook in general gets a bad reputation, but as someone who watches wakelocks on a daily basis and the battery page, this is really the first instance of Facebook misbehaving in at least 2-3 years.
Anyway, is this something like you guys are seeing? https://imgur.com/a/rpO0j
The background drain isn't TOO Terrible. It's around ~2.5% / hour screen off on LTE (honestly that's what I got on a OnePlus One on Lollipop anyway), while the screen on drain was around 25% / hr
BTW, are you using Facebook/Messenger beta? I'm only in the Facebook beta program, so I don't see any issues for Messenger on my side yet.
are you using Facebook/Messenger beta?
Not using betas. I can't agree regarding facebook and battery life. It'd suppose to use cgm but still it had a heap of timers going off and the app is ever high in wakelock detector. I've had enough and now limited most of its alarms and wakelocks in amplify to no more often than every 15 mins. This has lowered facebooks position in the wakelock list to a much more acceptable level. No problems arise either apart from not getting notifications as expected but that's been a problem for years over multiple handsets.
I can even confirm it, the same wakelocks and drain have been appearing on my OnePlus One too.
I use amplify and prevent wakelocks to everything pertaining to Facebook to 86400s. That's once per day and haven't had any detrimental effects from the app. All still works as it should.
TigerSoul925 said:
Not using betas. I can't agree regarding facebook and battery life. It'd suppose to use cgm but still it had a heap of timers going off and the app is ever high in wakelock detector. I've had enough and now limited most of its alarms and wakelocks in amplify to no more often than every 15 mins. This has lowered facebooks position in the wakelock list to a much more acceptable level. No problems arise either apart from not getting notifications as expected but that's been a problem for years over multiple handsets.
Click to expand...
Click to collapse
What version of Facebook are you on?
BTW Facebook does use GCM. IT only uses MQTT when you are actively in the Messenger app. I'm not entirely certain what's going on here. The wakelock is com.facebook.bugreporter.scheduler.LollipopService so it seems to be bug reporting related and not notification related.
dmo580 said:
What version of Facebook are you on?
BTW Facebook does use GCM. IT only uses MQTT when you are actively in the Messenger app. I'm not entirely certain what's going on here. The wakelock is com.facebook.bugreporter.scheduler.LollipopService so it seems to be bug reporting related and not notification related.
Click to expand...
Click to collapse
Oh! Funny thing is, I've limited the mqtt stuff and I've had zero issues getting messages right away when screen is on or off in messenger but thanks to the mods facebook stuff is now farther down on the list of wakelocks rather than high. If those mqtts were only used when active, why use wakelocks for it at all? And why do they creep up in count when the screen is off? 60.0.0.2.76
Sent from my Nexus 6P using Tapatalk
TigerSoul925 said:
Oh! Funny thing is, I've limited the mqtt stuff and I've had zero issues getting messages right away when screen is on or off in messenger but thanks to the mods facebook stuff is now farther down on the list of wakelocks rather than high. If those mqtts were only used when active, why use wakelocks for it at all? And why do they creep up in count when the screen is off? 60.0.0.2.76
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
MQTT is only used when the app is in the foreground meaning its being actively used and screen on. Therefore it shouldn't cause wakelocks. I'm guessing MQTT is used because GCM can see delayed notifications sometimes. MQTT is probably better suited for real time chat.
What wakelock are you seeing? Is it the one I posted earlier? If so I'm not sure if that sure it has anything to do with the actual chatting and communication portion of the app. The wakelock has to do with a bugreporter, which is misbehaving when your screen is off.
I think I know the answer, but no way to help this without root right?
I can confirm, same problem on Nexus 5x (not rooted) latest version of Facebook... Updated this morning, caused wakelocks, uninstalled, problem solved. Shame I have to uninstall it to fix...
I have 60.0.0.5 now... Facebook simply minimizes itself automatically now. Anyone else seeing this behavior? I have greenify on Facebook as well as amplify to limit some wakelock. Might be the cause...
I am seeing this issue as well with com.facebook.bugreporter.scheduler.LollipopService causing massive drain.
I just have Messenger 53.0.0.17.308.
Since I do not want to install Xposed + Amplify to address the issue, is there a way to block this Job? I am digging into MyAndroidTools, but I can't find anything like that in Messenger services or Activities.
EDIT: According to BetterBatteryStats, it's a Service, but I can't find it.
EDIT2: By changing display mode in MyAdroidTools, I was able to find the service, the normal display name is Lollipop Service. However, if disabled, the app does not work properly, closes as soon it's opened.
same here guys!nexus 5 with cm13. huge wakelock with facebook and messenger. I tryed to greenify it but it doesn't work and after few minutes they come back again. I have to hybernate them with SDMaid app and it works well, but of course once hybernate i can't use them anymore until i dishybernate. Any solution?i don't use xposed..:crying:
Confirm this wakelock on 1+1 with CM 13.
So not sure if this has already been posted and / or discussed elsewhere. Did a quick search and didn't find anything.
I was having pretty decent battery life on my s7 edge, but still getting random wakelocks that were only stopped by a restart. I was using package disabler to disable bloatware etc.
Usually it would show up as Android OS which was causing the stay awake. Device would not go into deep sleep when this was happening.
A bit of playing around and I noticed once the wakelock started I could get it to stop by restarting the phone or turning off bluetooth. I use android wear so turning off bluetooth wasn't an option.
Some googling led me to this thread http://forum.xda-developers.com/nexus-6p/help/bluetooth-causing-wakelock-t3237226
Mentions gas buddy app causing wakelock due to polling location via bluetooth (beacons...?), and some sort of bug or bad programming being the main culprit. Anyway, point being once I removed gas buddy everything was great and I had no more extended wakelocks for no reason.
I hadn't seen anyone post it in here, and clearly it does have the same issues on our phones. I see a lot of people talking about bad battery life, so hopefully this helps.
Keep in mind that gas buddy isn't the only app which has issues like this - it just seems to be the most common one. Check your apps as while it might not report it that way, but could be the root caused of wakelocks and subsequent bad battery life.
mrja22 said:
So not sure if this has already been posted and / or discussed elsewhere. Did a quick search and didn't find anything.
I was having pretty decent battery life on my s7 edge, but still getting random wakelocks that were only stopped by a restart. I was using package disabler to disable bloatware etc.
Usually it would show up as Android OS which was causing the stay awake. Device would not go into deep sleep when this was happening.
A bit of playing around and I noticed once the wakelock started I could get it to stop by restarting the phone or turning off bluetooth. I use android wear so turning off bluetooth wasn't an option.
Some googling led me to this thread http://forum.xda-developers.com/nexus-6p/help/bluetooth-causing-wakelock-t3237226
Mentions gas buddy app causing wakelock due to polling location via bluetooth (beacons...?), and some sort of bug or bad programming being the main culprit. Anyway, point being once I removed gas buddy everything was great and I had no more extended wakelocks for no reason.
I hadn't seen anyone post it in here, and clearly it does have the same issues on our phones. I see a lot of people talking about bad battery life, so hopefully this helps.
Keep in mind that gas buddy isn't the only app which has issues like this - it just seems to be the most common one. Check your apps as while it might not report it that way, but could be the root caused of wakelocks and subsequent bad battery life.
Click to expand...
Click to collapse
Related question: How are you determining wakelocks? Are you rooted?
Sent from my SM-G935T using Tapatalk
GiancarloMorr24 said:
Related question: How are you determining wakelocks? Are you rooted?
Sent from my SM-G935T using Tapatalk
Click to expand...
Click to collapse
I am not rooted. This makes the whole wakelock detecting a whole lot harder.
I simply use cpuspy and watch when the phone isn't going into deep sleep, but rather idling at the lowest cpu speed. This usually means a wakelock so I head over to the battery section in settings and look at what is listed there for stay awake times. this is what lead me to android os, and then bluetooth (as android os aggregates a lot of different services into it's stats)
Lately I have been struggling with some very bad battery drain. I'm a very light user. Before the Oreo update by the end of the day I would have 80% battery left. Now I'd be happy to have 40% left. I tried everything including greenify to no avail. Something keeps my phone awake. I found that a partial wakelock caused by LgeGnssLocationProvider is the culprit.
The fun part is when you google it.
Any ideas what the hell I'm supposed to do? I'm considering rooting my phone to get rid of all the bloatware. Would that also allow me to get a better insight of what is causing this wakelock?
I'm also have notice this, but the wakelock seems to be related with some LG bloatware. I have disabled multiple GNSS LG apps running in background, and that solve the issue. (i have root)
DJPRMF said:
I'm also have notice this, but the wakelock seems to be related with some LG bloatware. I have disabled multiple GNSS LG apps running in background, and that solve the issue. (i have root)
Click to expand...
Click to collapse
Which applications did you disable? I listed all the packages that contained gnss and disabled those without any luck. Worst part is, it does not always happen. Sometimes I can go the entire day without the wakelock.
I can not believe I am the only one who is experiencing this issue.
You are not the only one, I am having the same problem on my V30. Any ideas how to solve that problem??
I'm still working on figuring out what is causing the wakelock. Can't seem to find it though
I'm going to bump this again in the hope that someone sees it and know's what is going on.
Is there a way to find what triggered a wakelock?
Ortix92 said:
I'm going to bump this again in the hope that someone sees it and know's what is going on.
Is there a way to find what triggered a wakelock?
Click to expand...
Click to collapse
https://www.xda-developers.com/stop-wakelocks-android-without-root/
Flashing_Expert said:
https://www.xda-developers.com/stop-wakelocks-android-without-root/
Click to expand...
Click to collapse
I've come across this many many times but it doesn't help me. The wakelock is caused by Android System, but I want to know what exactly triggered it. Because it does not occur all the time.
Ortix92 said:
I've come across this many many times but it doesn't help me. The wakelock is caused by Android System, but I want to know what exactly triggered it. Because it does not occur all the time.
Click to expand...
Click to collapse
it's not system itself it's always some app using system interface...
posibly even some LG bloatware that uses location...
weather and so on...
Has anyone managed to solve this absurd wakelock?