Bluesleep Wakelocks drain battery on Oreo - Nexus 6P Q&A, Help & Troubleshooting

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.

Related

[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

Bluetooth causing wakelock?

Just noticed yesterday that my battery life has been pretty poor on my new Nexus 6P. It took me a while to narrow it down, but I finally noticed that Bluetooth appears to be keeping the phone awake.
Whenever Bluetooth is on, regardless of whether it's connected or paired to anything (I normally use Android Wear, but I completely unpaired all bluetooth devices on the phone), "Android OS" in the battery info screen appears to be stuck awake. Its "Keep awake" time grows continuously as long as Bluetooth is turned on.
Has anyone else ran into this issue, and have any idea how to fix it? I really can't be leaving Bluetooth turned off, and the phone is not really going to make it through the day like this.
Yes it's been happening to me. I didn't know what was causing it until I saw your post. It seems to be a glitch with Marshmallow and not the phone itself. My Nexus 9 was also stuck awake until I turned off Bluetooth.
Sent from my Nexus 6P using Tapatalk
Hmm. Maybe that's why my battery drained so fast. I'll have to turn off Bluetooth and see if it makes any difference
Sent from my Nexus 6P using XDA Free mobile app
Have you disabled the bluetooth scanning under locations --> settings (the 3 dots) --> scanning.
You can also disable the wifi scanning in there too.
No, I have disabled Bluetooth scanning and it is still occurring. As long as Bluetooth is turned on, the device stays awake. There's something more serious at issue here.
That's disappointing if true. I use BT all the time and leave it on 24/7.
Aw man, bummer hearing that as I keep my Bluetooth on all the time, and am waiting on my 6P. I actually had this same issue on my Note 4 a week ago, but I was able to narrow it down to a 3rd party app called "Gas Buddy" by using Greenify and CPU Spy. And this only happened whenever Bluetooth was enabled.
I know you said Android OS looks to be the culprit, but if you happen to have this app, try uninstalling it (or blocking Bluetooth permissions for the app). Otherwise, there might be another app pinging Bluetooth to keep the phone awake.
Sent from my SM-N910V using Tapatalk
I was seeing the same issue, if BT was on, there was a 100% bluesleep wakelock. Lots of searching later, turns out the Gasbuddy app was the culprit. I still don't understand why, but that was the problem for me.
B
I turned off BT and got significantly bettery battery life. I only use it when driving in my car so it's not a huge deal for me to have to turn it on/off, but there should be a fix for this.
Man, I'm glad I found this thread. It seems to be the only discussion about this issue on the entire internet! After two nights of 20%+ battery drain, and waking up to a completely dead phone one morning, I'll try turning off Bluetooth instead of returning the phone. Here's hoping for a fix soon. This is a pretty unacceptable problem.
Damn, sucks for those of us with smartwatches
10SE said:
Man, I'm glad I found this thread. It seems to be the only discussion about this issue on the entire internet! After two nights of 20%+ battery drain, and waking up to a completely dead phone one morning, I'll try turning off Bluetooth instead of returning the phone. Here's hoping for a fix soon. This is a pretty unacceptable problem.
Click to expand...
Click to collapse
Do you have gasbuddy app installed?
d1ez3 said:
Do you have gasbuddy app installed?
Click to expand...
Click to collapse
I don't.
i had just posted my (poor) battery life on the battery life thread, and then read this. I did have the gasbuddy app installed, and was keeping BT on 100% of the time. I have since removed the gasbuddy app, and disabled BT for now to see if makes a difference. Maybe its the placebo effect, but my drive from home to work seemed to have killed very little battery since i did this. Ill know better as the day progresses. While it would be annoying to know this is what is causing the wakelock, id just be happy knowing how to manage it until a fix is determined.
love you xda....thanks guy..i had the same issue and drained battery 20% overnight during 7 hours sleep. Crazy drain..... I had bluetooth and gasbuddy app.
So I disabled both and will keep you guys posted.
Thanks guys!
By the way / FWIW I've reported the correlation between GasBuddy and Bluetooth to the GasBuddy devs, and actually got a reply from them. They say they'll have it fixed in the app's next update.
Hello supertoast,
I have forwarded this feedback along to our development team for review to be fixed. They're aware of the problem and it should corrected in the near future. Thank you for bringing this to our attention.
Regards,
John
GasBuddy.com
Click to expand...
Click to collapse
Sent from my SM-N910V using Tapatalk
supertoast92 said:
By the way / FWIW I've reported the correlation between GasBuddy and Bluetooth to the GasBuddy devs, and actually got a reply from them. They say they'll have it fixed in the app's next update.
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
Nice to know. I also sent something to them as well.
Hopefully they fix it, it saves me money when finding cheapest gas...
Is there a way without root to determine what app may be wakelocking BT? I don't have GB installed and I get pretty bad battery life with BT on.
mgorman said:
Is there a way without root to determine what app may be wakelocking BT? I don't have GB installed and I get pretty bad battery life with BT on.
Click to expand...
Click to collapse
Well besides Gas Buddy, it seems that from the above posts that its a fundamental bluetooth issue in marshmallow. So it doesn't matter which app uses it.
It could be, but the GasBuddy correlation for my Note 4 was on 5.0.1. It may very well be some 3rd party app going rogue. That's from my experience though - it could be Marshmallow in general causing it, for all I know! Still waiting on my 6P to experience it. [emoji14]
Sent from my SM-N910V using Tapatalk

Does GasBuddy still cause a battery drain problem for nexus 6p users?

So I noticed that the newest version of GasBuddy says they fixed the battery drain problem that was affecting certain phone models. I decided to test this the last two nights. I Uninstalled GasBuddy and left my phone unplugged while I slept. I lost 2 percent from 100 percent. Then last night I tried with GasBuddy installed. I lost 20 percent and the keep awake time for android os was more than 8 hours. Is this still an issue for other people? I love GasBuddy and I hate to keep it off my phone.
Sent from my Nexus 6P using Tapatalk
same - the update didn't fix it.
it did cause mad wakes for me, uninstalled it last week, i will wait longer until i know its fixed for sure
going to mobile version of the site from chrome and adding to homescreen for the time being seems to be better option instead of installing the app. Also this seems to be fast.
I haven't seen any battery drain at all, I read somewhere that it had something to do with bluetooth, which I don't use
Well I sent then an email hopefully they can fix the 2nd time around
Sent from my Nexus 6P using Tapatalk
Yes, problem still here, had to uninstall GasBuddy. Strange that it needs bluetooth and then GB doesn't even show up in BBS as holding a wakelock.
Just Greenify it.
jejb said:
Just Greenify it.
Click to expand...
Click to collapse
Does that fix it? Have you tried it? I'm afraid that once it triggers bluetooth to keep the phone awake it may not go away even if you Greenify it. It feels like something wrong in the bluetooth stack that GB may trigger. I can't explain why GB doesn't show up in BBS or the Android battery monitor.
sirxdroid said:
Does that fix it? Have you tried it? I'm afraid that once it triggers bluetooth to keep the phone awake it may not go away even if you Greenify it. It feels like something wrong in the bluetooth stack that GB may trigger. I can't explain why GB doesn't show up in BBS or the Android battery monitor.
Click to expand...
Click to collapse
No, apparently not. After reading this thread, I started GasBuddy for the first time on my new phone and put it right on the Greenify list. Constant wakelocks anyway, and battery took a steep downhill trend for the next few hours.
jejb said:
No, apparently not. After reading this thread, I started GasBuddy for the first time on my new phone and put it right on the Greenify list. Constant wakelocks anyway, and battery took a steep downhill trend for the next few hours.
Click to expand...
Click to collapse
Yeah, this may point to a Bluetooth stack problem and not really a GasBuddy problem, though the app triggers it. I'm sure there are other apps out there that trigger the same.
Wow thank you people... I noticed in the last weeks that, as soon as I use the bluetooth and then stop using it (I disconnect my device), if I let the bluetooth activated, my phone was awake all the time. I couldn't find WHY !!
Then I saw a post from someone who said that the fix was to remove gasbuddy. I couldn't believe it, but I did the test and it's true !!
Gasbuddy is the culprit
It seems to be fixed now, in the latest release. I'm running it and have actually uninstalled Greenify. I never turn BT off. Battery life is excellent.
jejb said:
It seems to be fixed now, in the latest release. I'm running it and have actually uninstalled Greenify. I never turn BT off. Battery life is excellent.
Click to expand...
Click to collapse
I did the test this morning and it's not fixed
All I can say is that is working great for me. Stock Rom, Kylo Kernel, system level root, 6.0.1.
jejb said:
All I can say is that is working great for me. Stock Rom, Kylo Kernel, system level root, 6.0.1.
Click to expand...
Click to collapse
Stock only for me.
I just did it again :
I installed GasBuddy, I turn bluetooth ON, I connect my headphone.
I start TuneIn and start playing anything for a few seconds. Then I stop it and I disconnect my headphone and I let the bluetooth on
here is the wakelock again.
I only connect to my vehicles and laptop with BT, which I've done several times since loading GasBuddy's fixed release. No issues. Ended the day yesterday with 92%, including a couple of BT phone calls from my truck.
I'm also using NapTime, using the Aggressive mode.
jejb said:
I only connect to my vehicles and laptop with BT, which I've done several times since loading GasBuddy's fixed release. No issues. Ended the day yesterday with 92%, including a couple of BT phone calls from my truck.
I'm also using NapTime, using the Aggressive mode.
Click to expand...
Click to collapse
Are you stock rooted with the stock kernel as well?
geoff5093 said:
Are you stock rooted with the stock kernel as well?
Click to expand...
Click to collapse
See post #15

NlpCollectorWakelock - 10hrs awake!?

This is garbage, my 6P will not sleep anymore on 6.0.1. I am stock, rooted, ElementalX, and Xposed.
Not running anything to crazy but this wakelock is destroying my battery. Anything I can do short of a factory reset?
It's related to your location services. Do you have high accuracy for all apps? Maybe have location history enabled on Google Maps
I have both enabled. Prior to 6.0.1 this was a non issue. I have the same settings on my Nexus 9 on 6.0.1 and the device will not be held awake :/
This has been driving me nuts lately too. 6.0.1 stock rooted. The only solution I've found so far is Amplify to limit the wakelock but I'd like to keep Android Pay working... At least until they change root detection methods.
Probably a little late to this thread but I have a possible reason for this issue... I am not a developer so this is only based on my practical experiments..
I used to face this problem till very recently on my Nexus 6p.. no matter which kernel or ROM I use... some nights the phone doesn't sleep at all and then I see the culprit is nlpcollector wakelock. If I restart, the problem goes away for a day or two but then comes back again...
Then I noticed that every post I have seen with this issue on the internet has related to people with rooted phones (else you wouldn't be able to use BBS ) and most had made modifications to the doze parameters (using whichever app).. So I reset my doze parameters to default.. Since the last 2 weeks I haven't seen this issue anymore..
My guess is that one of my customized doze parameters is breaking the functionality but I can't figure out which one.. Tried resetting only the location based parameters but the wakelock returns.. My only solution is to reset all the doze settings..
Obviously the other solution is to set up xposed and download amplify or other such apps to block the wakelock.. I haven't tried it but should work..
PS - I still have location history on and location set to high accuracy. So that is not the culprit.

Nexus 6P / mediaserver / audio on - battery drain

Nexus 6P users with GSam Battery Monitor and Root Companion, do you notice the one of the highest battery drainers is under "System (mediaserver) and when you click into it is shows "Audio On" for a very long time?
I did not play any music or anything with much sound except normal apps notification. I also tried uninstalling updates of Youtube/Google Music etc and cleared data and cache, and uninstalling a few possible apps such as apps relates to "sounds and music" and the "Audio On" time just keeps going.
Is it normal? If not, any solution or suggsetions? Some users suggested it's Ok Google always on. Thanks.
schizophrenia said:
Nexus 6P users with GSam Battery Monitor and Root Companion, do you notice the one of the highest battery drainers is under "System (mediaserver) and when you click into it is shows "Audio On" for a very long time?
I did not play any music or anything with much sound except normal apps notification. I also tried uninstalling updates of Youtube/Google Music etc and cleared data and cache, and uninstalling a few possible apps such as apps relates to "sounds and music" and the "Audio On" time just keeps going.
Is it normal? If not, any solution or suggsetions? Some users suggested it's Ok Google always on. Thanks.
Click to expand...
Click to collapse
I have the same, but never managed to find out if it was normal or not. Audio on time was generally a bit more than the Screen on Time. OK Google was completely turned off.
I'm still to establish if it is a GSAM reporting issue, or a real problem.
Are you on the stock factory image but rooted? Is your OK Google set to always on, within the Google app, or never? I had the same problem when reverting back to stock, but switched to PureNexus and started using Amplify and Naptime and it has improved significantly. It does go up when I play music/podcasts though but that's normal I think.
Azarin said:
I have the same, but never managed to find out if it was normal or not. Audio on time was generally a bit more than the Screen on Time. OK Google was completely turned off.
I'm still to establish if it is a GSAM reporting issue, or a real problem.
Click to expand...
Click to collapse
Yeah, I kinda hope it's a GSam reporting issue as I dont really seem to be able to find out the real problem is.
geoff5093 said:
Are you on the stock factory image but rooted? Is your OK Google set to always on, within the Google app, or never? I had the same problem when reverting back to stock, but switched to PureNexus and started using Amplify and Naptime and it has improved significantly. It does go up when I play music/podcasts though but that's normal I think.
Click to expand...
Click to collapse
I am on everything stock except rooted. My OK Google is always on but i tried to disable it and still see the "Audio On" time counting. But I do notice the Audio On time does not always count. I failed to find any sorts of co-relation of the time to any apps though. It feels so random. I have already tried uninstalling Music App, some apps with notification time and now disabling Google OK always on, but still the time counts on.
I am having the same issue since few days now.. The mediaserver (especially audio on) usage is really really high.
Do you guys use spotify by any chance? I didn't install it for a while and today after Spotify installation it's like drain time babe.
VnnAmed said:
Do you guys use spotify by any chance? I didn't install it for a while and today after Spotify installation it's like drain time babe.
Click to expand...
Click to collapse
i don't use spotify. the drain comes out of nowhere and unpredictable. that's the problem.
It looks like wechat draining bro, after receiving any notification from wechat or idleing it will cause it drain on audioon bugs.
If you force close wechat and recheck it stop at the value.
I've been having this issue too. I've been switching back and forth between Chroma and Pure Nexus and it hasn't changed. I always get at least 25% drain due to mediaserver audio on. It's driving me crazy :/
squallkns said:
It looks like wechat draining bro, after receiving any notification from wechat or idleing it will cause it drain on audioon bugs.
If you force close wechat and recheck it stop at the value.
Click to expand...
Click to collapse
just tried what you suggested and let's see
i have always been skeptical about these kinds of mainland Chinese apps but i have to use it because of business.
Today I got angry and just disabled mediaserver. Will report if it helps or not.
squallkns said:
It looks like wechat draining bro, after receiving any notification from wechat or idleing it will cause it drain on audioon bugs.
If you force close wechat and recheck it stop at the value.
Click to expand...
Click to collapse
tried this and didn't help at all. hmm..
I have the same problem! I will give some stats: Ok Google always on, no local music only play music, no spotify, pocket casts, I tried to only scan with notification, 2 clean installs, my kernel often keeps the device awake.
Running Kylo on Ubermallow with Amplify. I think this drain is real, because when I did not have it my battery lasted longer.
absolutly same issue here :/
it seems started with February security patch, no media file change (not added, not moved of folder, nothing!). I've not played music/video while testing this.... :/
OkGoogle everywhere is OFF
i've no music streming app/services, any chat (just hangouts), any other change on my setup these days.... :/
Has anybody figured this out yet? I had skipped January and February's security patches and was still on MMB29M. This only started about 4 days ago for me. I upgraded to the latest patch, MMB29Q, and... the glitch was fixed for a day hours but has now come back. :\
MultiKoopa said:
Has anybody figured this out yet? I had skipped January and February's security patches and was still on MMB29M. This only started about 4 days ago for me. I upgraded to the latest patch, MMB29Q, and... the glitch was fixed for a day hours but has now come back. :\
Click to expand...
Click to collapse
it seems to be a mystery that no one has a real fix. :crying:
...and all of a sudden it's gone...
????????????????
what
is this phone screwing with me???
@schizophrenia
i'm trying to investigate this issue....
do you use lighmanager (https://play.google.com/store/apps/details?id=com.koo.lightmanager) ?
sweetpiggy said:
@schizophrenia
i'm trying to investigate this issue....
do you use lighmanager (https://play.google.com/store/apps/details?id=com.koo.lightmanager) ?
Click to expand...
Click to collapse
I do use LED Blinker. You think it's causing this?
Interesting. I use gravity box notification light control. Are you suggesting that when an app controls the led it could cause this issue?

Categories

Resources