Anyone else having this come up? Previously I was getting the msm_hsic_host wakelock, but now its this? Github seems to suggest its Chrome related so I've removed that and its still the same after rebooting and leaving it for awhile. WiFi is on, no mobile data or any bizarre apps installed.
Any help? Thanks!
Sent from my Nexus 4 using xda app-developers app
Done a factory reset this morning to no avail, still coming up. There must be someone who knows a little more!
It still shows without any app installed?
Try Franco kernel
Yup.
Even with Franco kernel, still shows up the same error.
Is nobody else getting this? Seems absurd!
same issue
Had the same issue.
i deactivated chrome and wakelock was gone.
cyberfrog77 said:
Had the same issue.
i deactivated chrome and wakelock was gone.
Click to expand...
Click to collapse
How does one do that?
upgraded to kitkat from reverting to stock and taking all the updates..
now my bluetooth is gone rogue..keeping the phone awake and killing the battery..anyone face the isuse or know how to fix..??
phone is not connected to any nearby bluetooth..
I have the same problem.
Sent from my LG-D800 using xda app-developers app
same problem currently faced by me have you found any solution till yet ????
its a false reading plenty of threads on this install wakelock detector and you will see also read this http://forum.xda-developers.com/showthread.php?t=2681205 read the bug fix part
Im having a similar issue...
http://forum.xda-developers.com/nexus-6p/help/bluesleep-100-wakelock-t3273565
My phone has recently gotten a huge wakelock: cdmainboundsmshandler. It keeps my phone awake basically all the time. Anyone have any ideas on how how to fix this wakelock?
I'm running Slimkat 4.4.4 on LS980.
VertzxD said:
My phone has recently gotten a huge wakelock: cdmainboundsmshandler. It keeps my phone awake basically all the time. Anyone have any ideas on how how to fix this wakelock?
I'm running Slimkat 4.4.4 on LS980.
Click to expand...
Click to collapse
I'm not sure but maybe the kernel is causing this?..try another kernel and see if it's fixed
Ever since I flashed 5.0 to my 900V, my battery life has gone significantly down. Now this can be expected to some extent as I can no longer use Amplify to control NlpCollectorWakeLock (which is one of a few wakelocks going to town on my battery). One of the others is bluedroid_timer, which is part of bluetooth. I did some searching and I saw some other people with the same issue, but no answers. I use a Moto 360 on a daily basis, use bluetooth streaming in my car, and use bluetooth headphones at the gym, so turning off bluetooth isn't really an option. Bluesleep is another one that is spending a lot of time running. Anyone have any ideas? I've read a few threads where people mention this problem, but no one has posted any answers yet. Here is an album of my wakelocks.
Did you ever figure this out? I'm experiencing a very similar issue.
I'm not rooted, so I can't see the specific wakelocks but it's absolutely Bluetooth related, even with all device profiles deleted. If I have the BT radio on, my battery gets hammered and the phone never goes into deep sleep, turn the radio off and all is normal.
MattE303 said:
Did you ever figure this out? I'm experiencing a very similar issue.
I'm not rooted, so I can't see the specific wakelocks but it's absolutely Bluetooth related, even with all device profiles deleted. If I have the BT radio on, my battery gets hammered and the phone never goes into deep sleep, turn the radio off and all is normal.
Click to expand...
Click to collapse
I just started experiencing this as well. I'm on a T-Mobile S4, running a GPE rom. It started happening in the last month, not exactly sure when. I ran a rooted TouchWiz stock rom before that and I don't recall ever seeing it.
So you're running fully stock? I was curious if I installed some weird app or software package that messed with things, but if you're running stock that would seem to rule that out..
dirkdigles said:
I just started experiencing this as well. I'm on a T-Mobile S4, running a GPE rom. It started happening in the last month, not exactly sure when. I ran a rooted TouchWiz stock rom before that and I don't recall ever seeing it.
So you're running fully stock? I was curious if I installed some weird app or software package that messed with things, but if you're running stock that would seem to rule that out..
Click to expand...
Click to collapse
yup, Galaxy S5 with current Verizon build of Lollipop, not rooted, just Nova launcher and my usual apps. Since the bluetooth battery issue, I've tried reboots, clearing cache partition, deleting all BT device profiles, etc. Everything short of an FDR, which I don't have time for right now.
MattE303 said:
yup, Galaxy S5 with current Verizon build of Lollipop, not rooted, just Nova launcher and my usual apps. Since the bluetooth battery issue, I've tried reboots, clearing cache partition, deleting all BT device profiles, etc. Everything short of an FDR, which I don't have time for right now.
Click to expand...
Click to collapse
Thanks for the reply.
In lots of google searches, seems like many have this issue, but i couldn't find a solution anywhere, nor any consistency among devices. Seems that some custom kernels fix the issue.
But if you want to submit bug reports here, there's an official Google bug report thread on the issue that is alive:
https://code.google.com/p/android/issues/detail?id=87778
dirkdigles said:
I just started experiencing this as well. I'm on a T-Mobile S4, running a GPE rom. It started happening in the last month, not exactly sure when. I ran a rooted TouchWiz stock rom before that and I don't recall ever seeing it.
So you're running fully stock? I was curious if I installed some weird app or software package that messed with things, but if you're running stock that would seem to rule that out..
Click to expand...
Click to collapse
dirkdigles said:
Thanks for the reply.
In lots of google searches, seems like many have this issue, but i couldn't find a solution anywhere, nor any consistency among devices. Seems that some custom kernels fix the issue.
But if you want to submit bug reports here, there's an official Google bug report thread on the issue that is alive:
Click to expand...
Click to collapse
Thanks! the Google bug report is an interesting read, we're definitely not alone in this. I'm gonna try a few things based on what I read there and report my findings.
MattE303 said:
Thanks! the Google bug report is an interesting read, we're definitely not alone in this. I'm gonna try a few things based on what I read there and report my findings.
Click to expand...
Click to collapse
My solution was a particular app was causing it. Same for another user if you read the thread.
The app for me was MyRadar. Another user had a problem with Gas Buddy.
Both of these apps were recently updated to add bluetooth permissions.
dirkdigles said:
My solution was a particular app was causing it. Same for another user if you read the thread.
The app for me was MyRadar. Another user had a problem with Gas Buddy.
Both of these apps were recently updated to add bluetooth permissions.
Click to expand...
Click to collapse
I did see that and I am a GasBuddy user. There was also mention of NFC, that was the first thing I looked at. Experimenting now with GasBuddy removed.
I'm not rooted so I can't check for individual wakelocks, I have to just run it for a while, then look at the "Awake" bar graph in the stock Battery app, so it takes while to see if anything changed. I really wish Google would give us the choice whether to let 3rd party apps see the detailed battery stats, locking that down made it so much harder to diagnose this kind of thing without root.
Glad you got yours sorted out!
dirkdigles said:
My solution was a particular app was causing it. Same for another user if you read the thread.
The app for me was MyRadar. Another user had a problem with Gas Buddy.
Both of these apps were recently updated to add bluetooth permissions.
Click to expand...
Click to collapse
I understand your issue completely, but why in the world does gas buddy need bt permissions? ? ?
Sent from my SM-G900V using Tapatalk
ldeveraux said:
I understand your issue completely, but why in the world does gas buddy need bt permissions? ? ?
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
No idea, but it's mentioned on their Playstore page in a recent app update:
4.6.6
Get deals while you are filling up by turning on Bluetooth.
Click to expand...
Click to collapse
---------- Post added at 12:14 PM ---------- Previous post was at 11:43 AM ----------
so far it's looking like GasBuddy was the culprit in my case. I've been running several hours with GasBuddy removed, both NFC and Bluetooth are on, and battery usage/wakelocks appear normal.
I'm gonna give it a day or so to see if the problem spontaneously returns, then re-install GasBuddy and see what happens.
MattE303 said:
No idea, but it's mentioned on their Playstore page in a recent app update:
---------- Post added at 12:14 PM ---------- Previous post was at 11:43 AM ----------
so far it's looking like GasBuddy was the culprit in my case. I've been running several hours with GasBuddy removed, both NFC and Bluetooth are on, and battery usage/wakelocks appear normal.
I'm gonna give it a day or so to see if the problem spontaneously returns, then re-install GasBuddy and see what happens.
Click to expand...
Click to collapse
Definitely a GasBuddy issue on my phone, "Awake" bar graph becomes a solid block soon after installing GasBuddy, and returns to normal after uninstalling it. I've repeated this test a few times.
MattE303 said:
Definitely a GasBuddy issue on my phone, "Awake" bar graph becomes a solid block soon after installing GasBuddy, and returns to normal after uninstalling it. I've repeated this test a few times.
Click to expand...
Click to collapse
I started experiencing the issue with excessive wakelocks from Bluedroid_timer on my stock Nexus 6 about a month ago. Noticed my battery life dropped significantly as a result. Used Permission Friendly Apps to see which apps were using BT and if I happened to install any around the time this problem began. Only new apps indicating BT connectivity were GasBuddy and Netflix. No idea why GasBuddy needs BT but I'm pretty sure I installed it about the same time the wakelock issue began. Good to know someone else saw the same thing. Just uninstalled it and waiting to see if the wakelocks stop.
Hello guys.
I have N910C version of note 4 running on stock rooted lollipop but I'm facing with strange wakelock problem.
It's ProximitySensorManager and I can't figure out how to solve the problem.
Can someone from you help me with this?
I have the same issue on S4 i9500 running 5.0.1. BetterBatteryStats says that ProximitySensorManager is 17.8% Never had anything above 10% before this... Any suggestions would be greatly appreciated
Same here, can't figure out how to remove the wakelock
pigstacho said:
Same here, can't figure out how to remove the wakelock
Click to expand...
Click to collapse
really odd i have the same problem.
---------- Post added at 04:11 PM ---------- Previous post was at 04:07 PM ----------
So when you guys are in phone calls... there's this thing called a proximity sensor that tells the phone to keep the screen off when it's next to your face.
Velimere said:
So when you guys are in phone calls... there's this thing called a proximity sensor that tells the phone to keep the screen off when it's next to your face.
Click to expand...
Click to collapse
That's always been there. But why is it an issue now? It's kept my phone awake 1 hour out of 10 hr.
Galaxy S6 Edge
Sent from my SM-G925F using Tapatalk
Has anyone got the solution for this ?
i am having a G variant, & have the proximitysensormanager wakelock for hours..
pratik_193 said:
Has anyone got the solution for this ?
i am having a G variant, & have the proximitysensormanager wakelock for hours..
Click to expand...
Click to collapse
proximitysensormanager wakelock keeps the phone awake whenever the user is on a live call & the screen is pressed with the ear. The proximity sensor detects object proxmity thereby turning off the screen but keeping the phone awake since a live call is there. Most of the time, if everything is ok, the "keep awake" time of this wakelock will be equal or slightly less than user's total on-call time (if user doesn't use headset to answer call). See if this helps... peace :good:
Problem with the wake lock is that this keeps running even after the call. And drains the battery fast. Only way to fix is to reboot the phone