I have too many NETLINK and alarmtimer wakelocks. Can someone help me? I have latest nougat and I have installed Blu spark kernel but it didn't help.
When I am on bad wifi I can have over a half million NETLINK wakelocks!! When I am with cellular data I still have thousands.. What's the problem?
When I am with wifi and data off I have low NETLINK wakelocks. Also when I delete alarm cache I have low alarmtimer wakelocks.. Why? Can Google play services cause the problem?
Sent from my ONEPLUS A5000 using Tapatalk
lazostat said:
I have too many NETLINK and alarmtimer wakelocks. Can someone help me? I have latest nougat and I have installed Blu spark kernel but it didn't help.
When I am on bad wifi I can have over a half million NETLINK wakelocks!! When I am with cellular data I still have thousands.. What's the problem?
When I am with wifi and data off I have low NETLINK wakelocks. Also when I delete alarm cache I have low alarmtimer wakelocks.. Why? Can Google play services cause the problem?
Click to expand...
Click to collapse
I'm using Blu Spark kernel as well. Use ElementalEx as your kernel control app if you aren't already. Under Miscellaneous if you scroll down there is a Block Wakelocks option. When you click that there is a small list of wakelocks you can choose to block on reboot including the specific one you are having issues with. I block all the listed wakelocks and have never come across anything on my phone not working properly as a result.
And I have too many android alarms, without any particular reason...
Related
Hello everyone!
I've been having excessive wakelocks from "wakelockmanager", check out Wakelock Detector stats on the attached image. I'm using CleanROM 1.5 with Galaxy Gear connected all the time. Anyone else experiencing this problem?
Thanks!
XanoZuke said:
Hello everyone!
I've been having excessive wakelocks from "wakelockmanager", check out Wakelock Detector stats on the attached image. I'm using CleanROM 1.5 with Galaxy Gear connected all the time. Anyone else experiencing this problem?
Thanks!
Click to expand...
Click to collapse
I've done some other tests and I only see the wakelocks when I'm connected to the mobile network (with or without data). I use my Verizon Note 3 on GSM/WCDMA.
Sent from my SM-N900V using xda app-developers app
Any follow up on this? Having the same problem all of a sudden
Do you have Android Firewall and/or XPrivacy XPosed module?
I have T-Mobile Note 3 with stock ROM and I noticed this battery drain also when I have both installed. I actually have these wakelocks within 3 hours after rebooting.
- WakelockManagertimeout (runs 808 times)
- WakeLockManager (runs 1107 times)
So maybe it is something that is universal rather than restricted to a particular model (Verizon, T-Mobile, etc.)
I actually just installed xprivacy and rebooted. So far I don't have the wakelock anymore but has it within 6 hours or so after the first reboot... Frigging strange I can't pinpoint what it is even in BBS.
fookea said:
I actually just installed xprivacy and rebooted. So far I don't have the wakelock anymore but has it within 6 hours or so after the first reboot... Frigging strange I can't pinpoint what it is even in BBS.
Click to expand...
Click to collapse
Probably the Android Firewall then. Some networking related process must be running in the background that intercept network request from the application.
However, if OP doesn't have these 2 apps, I am not sure what caused the excessive wakelocks...
Wakelock Detector quit working for me on 4.4.2. It crashes shortly after opening the app and giving it SU permissions.
i don't have Android firewall at all. I did deny some location and wakelock permissions in AppOps and it's better now. I'll post some pictures with the apps i have maybe we can compare them and find the culprit this way.
https://mega.co.nz/#!dIl3mRoa!XK4Yg1Dh-9E-AXgoA5BAIJm9qV-Y6QA2ewGU_JMuDUk
https://mega.co.nz/#!JZFm0RLY!V4Pu8elpJJN8Ufk8_k3qj-P1yoY_zruuv07wV84EM8A
https://mega.co.nz/#!tEUwVT4T!-UQPZdIGhCHgbvRvSe57l2i4ccPegRmUjDtr2OlCXoM
https://mega.co.nz/#!dF9jDDBY!sLRsk5b_Nur22gADlKx6vG7NcJ9T81lU5E0QpQXkOhA
Ignore the obvious ones like facebook and games.
I solved my issue. I ran Catlog and found that the csc was causing me a lot of wake locks. I have ORO CSC and flashed a SIN CSC. Somehow it was constantly trying something in the background. I deleted all the CSC folders except the common one and everything is back to normal. Also my Android OS and Android system are low now. The folders are located in /system/csc. I do advise backing them up in case something goes wrong.
Hope this helps
Hello,
I'm almost unable to use my LG G Watch further cause my phone stays awake for almost 50% caused by bluesleep and msm_serial_hs_dma wakelocks.
I've already factory resetted my watch and phone and still getting an enormous amount of wakelocks :/
If I disconnected my watch and only keep bluetooth on, the wakelocks go down to 1-2%.
Has anyone else experienced such problems with the bluetooth connection and a hint how to get rid of them?
I'm using a Nexus with with Cataclysm and Code_Blue kernel (already tested with stock ROM + kernel and ElementalX, not much difference between them)
Any help is highly appreciated!
I am having the same issue on stock 6.0. Have you had any success in fixing this?
Hey, I am testing stock EU 6.0 battery life, for now not so good, DOZE doesn't do anything for me, same %/h as on lollipop, but questions is another. On Amplify I noticed "ICING" wakelock. It stands for Google Play Services and have some business with SMS. I cant find what causes to start this wakelock, but on stock 5.1.1 this wakelock had smaller wakeup time. Maybe someone can explain me? Why does this shows up?
BooBzi said:
Hey, I am testing stock EU 6.0 battery life, for now not so good, DOZE doesn't do anything for me, same %/h as on lollipop, but questions is another. On Amplify I noticed "ICING" wakelock. It stands for Google Play Services and have some business with SMS. I cant find what causes to start this wakelock, but on stock 5.1.1 this wakelock had smaller wakeup time. Maybe someone can explain me? Why does this shows up?
Click to expand...
Click to collapse
I always wondered this also. Amplify shows a lot of wakelocks but don't know enough about how to use app properly other than limiting the safe to limit wakelocks maybe change default 240 seconds to a greater number. Wonder what ill effects this has. I know I tried screwing with the alarms wakelocks and had issues.
jmileti said:
I always wondered this also. Amplify shows a lot of wakelocks but don't know enough about how to use app properly other than limiting the safe to limit wakelocks maybe change default 240 seconds to a greater number. Wonder what ill effects this has. I know I tried screwing with the alarms wakelocks and had issues.
Click to expand...
Click to collapse
You can limit icing wakelock (I did) I set like 14240 seconds
I could never do anything to stop com.android.gms wakelocks but I finally managed too. I had over 800 wakelocks on full battery today I had 11
Don't worry about it. Icing barely effects battery.
slicetwo said:
Don't worry about it. Icing barely effects battery.
Click to expand...
Click to collapse
I am not sure, but will agree with you, but I cant figure out what does this wakelock to appear, why on lollipop I havent this issue?
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.
There is a BT wakelock related issue on my Nexus 6P running Oreo, Build OPR6.170623.019.
As soon as BT is switched on, massive Bluesleep wakelocks occur. This happens even without any paired device or when all BT related services from other installed Apps are stopped except the system Bluetooth services.
At the end, these wakelocks prevent the phone from going into sleep mode which drains the battery quickly.
It seems this is a general issue on the 6P with BT on Oreo .
Any ideas how to fix this?
I've tried to get a BT HCI-Snoop Log recorded using related switch in developer options, but this seems no longer working under Oreo.
tomte28 said:
There is a BT wakelock related issue on my Nexus 6P running Oreo, Build OPR6.170623.019.
As soon as BT is switched on, massive Bluesleep wakelocks occur. This happens even without any paired device or when all BT related services from other installed Apps are stopped except the system Bluetooth services.
At the end, these wakelocks prevent the phone from going into sleep mode which drains the battery quickly.
It seems this is a general issue on the 6P with BT on Oreo .
Any ideas how to fix this?
I've tried to get a BT HCI-Snoop Log recorded using related switch in developer options, but this seems no longer working under Oreo.
Click to expand...
Click to collapse
That's an odd and isolated one. Have you reset network settings? wiped cache and dalvik partitions? If these don't work you may need to factory reset.
tomte28 said:
There is a BT wakelock related issue on my Nexus 6P running Oreo, Build OPR6.170623.019.
As soon as BT is switched on, massive Bluesleep wakelocks occur. This happens even without any paired device or when all BT related services from other installed Apps are stopped except the system Bluetooth services.
At the end, these wakelocks prevent the phone from going into sleep mode which drains the battery quickly.
It seems this is a general issue on the 6P with BT on Oreo .
Any ideas how to fix this?
I've tried to get a BT HCI-Snoop Log recorded using related switch in developer options, but this seems no longer working under Oreo.
Click to expand...
Click to collapse
I'm having the same issue, but haven't found a way to fix it yet.
Mdknight said:
I'm having the same issue, but haven't found a way to fix it yet.
Click to expand...
Click to collapse
So it is persistent after a factory reset?
v12xke said:
So it is persistent after a factory reset?
Click to expand...
Click to collapse
...and kernel changes. It must be affected by a core change in the code. Then again, everyone's mileage varies. I could just be having some bad luck.