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?
Related
I'm using CF's rooted kernel and nothing else on my KLA4 Note. No other alternative kernels, just the stock one. And yet I keep seeing strange issues with the kernel. Is anyone getting any of these two?
1) gps causing a wakelock in betterbatterystats in kernel section
2) fuelgauge also causing a wakelock in betterybattery states in kernel section
It doesn't happen often, but it has happened out of the blue. And before you ask, no, GPS was never enabled, no apps I have in my phone are using GPS too. Happened over the weekend with no other activity on the phone other than some calls. A reboot fixed it.
As for the fuelgauge thing, I have no idea either. It happened after removing my phone from a charger, and noticed that the battery was draining fast. Sure enough looking at BBS, I see fuelgauge wakelocking in kernel, whatever that is. A reboot fixed it.
Anyone else facing these strange issues?
If it helps to know, I have it too. I seem to be able to trigger the GPS wakelock issue when the Browser attempts to fix my location but is somehow unable to. But not always.
Fuel gauge. Seems random, but it might be related to the battery being too stressed and the level "rising" a bit when relaxed.
I've tried the stock android kernel and now am CFRoot kernel with Checkrom v5. If anything the gps issue has increased.
I had a high Android OS usage with CF kernel and LA4. I switched to Abyss Kernel and the OS usage is next to none now. No wakelocks except those for sync. Phone has deep sleep now and the battery life is outstanding.
Blue1k said:
I had a high Android OS usage with CF kernel and LA4. I switched to Abyss Kernel and the OS usage is next to none now
Click to expand...
Click to collapse
I had the same with stock kernel. On low-use days my kernel was using 40% of the battery!
It finally forced me to flash a kernel, and I chose Abyss. Kernel is now less than 5% pretty much all the time. Deep sleep is also most of the time, although I did not check well before that.
My phone randomly reboots. This happened over a few weeks ago, I wiped cache and monitored it, it fixed it.
Today, it just rebooted.
I think its more a software problem rather than hardware.
Any suggestions.
P.S. Not to threadjack, but I am also on LA4 CF Root with CheckROM
There's a separate thread in the Q&A section about the GPS Wakelock problem.
http://forum.xda-developers.com/showthread.php?t=1419087
Some ideas to try and avoid it, but unfortunately nothing definitive yet.
Just as an aside, personally I've been using the 'wake up lag' characteristic of the exynos when coming out of Deep Sleep as a clue to these wakelocks. If the screen comes on immediately, I suspect a wakelock of some sort and check BetterBatteryStats and CPUSpy.
Hello everyone I hope I got the right forum
I have a problem with the new system update released
The new update did not help at all to my nexus
I ran out of battery really fast, before the update it was fine
Battery had stayed a long time
What should I do?
1headshot said:
Hello everyone I hope I got the right forum
I have a problem with the new system update released
The new update did not help at all to my nexus
I ran out of battery really fast, before the update it was fine
Battery had stayed a long time
What should I do?
Click to expand...
Click to collapse
Read this:
http://forum.xda-developers.com/showthread.php?t=2385843
To get battery like this:
http://forum.xda-developers.com/showpost.php?p=44364085&postcount=5089
:cyclops:
Galaxo60 said:
Read this:
http://forum.xda-developers.com/showthread.php?t=2385843
To get battery like this:
http://forum.xda-developers.com/showpost.php?p=44364085&postcount=5089
:cyclops:
Click to expand...
Click to collapse
A quick look through that thread shows that it is focused on problems relating to Google Services. Since the update, I too am having issues with the battery draining more quickly than it ever did before. However, it appears to be msm_hsic_host wakelock causing the problem. Google services are a very small part of my battery usage.
I have posted a couple times about it in various threads, but I haven't seen a fix that applies to 4.3.
The battery drain is out of hand. I love my N4, but this is a big turn off for me.
I have tried these configurations to make sure it wasn't an oddball app causing the problem -
Stock 4.3 with stock Kernel - no root/stock recovery - Only apps being the ones that load on a factory reset
Wiped all partitions and reloaded stock 4.3/gapps/no root/stock recovery
Stock 4.3/rooted/TWRP/Stock gapps
Stock 4.3/rooted/TWRP/gapps+ a handful of other apps (photobucket/es file explorer/bbs - essentially, my normal config)
Added note - I also have cell broadcasts of all types turned off.
All of the above combinations respond the same way in regard to battery drain overnight. 7-9 hours off the charger/no screen time nets me 25-30% loss of battery from a full charge. msm_hsic shows up in BBS with 1.75 to 2.5 hours of wake time and is the highest power consumer. Putting the phone in flight mode reduces power consumption to ~2% over the same 7-9 hour timeframe. Just turning wifi off doesn't change anything.
Ideas anyone?
Calebz said:
A quick look through that thread shows that it is focused on problems relating to Google Services. Since the update, I too am having issues with the battery draining more quickly than it ever did before. However, it appears to be msm_hsic_host wakelock causing the problem. Google services are a very small part of my battery usage.
I have posted a couple times about it in various threads, but I haven't seen a fix that applies to 4.3.
The battery drain is out of hand. I love my N4, but this is a big turn off for me.
I have tried these configurations to make sure it wasn't an oddball app causing the problem -
Stock 4.3 with stock Kernel - no root/stock recovery - Only apps being the ones that load on a factory reset
Wiped all partitions and reloaded stock 4.3/gapps/no root/stock recovery
Stock 4.3/rooted/TWRP/Stock gapps
Stock 4.3/rooted/TWRP/gapps+ a handful of other apps (photobucket/es file explorer/bbs - essentially, my normal config)
Added note - I also have cell broadcasts of all types turned off.
All of the above combinations respond the same way in regard to battery drain overnight. 7-9 hours off the charger/no screen time nets me 25-30% loss of battery from a full charge. msm_hsic shows up in BBS with 1.75 to 2.5 hours of wake time and is the highest power consumer. Putting the phone in flight mode reduces power consumption to ~2% over the same 7-9 hour timeframe. Just turning wifi off doesn't change anything.
Ideas anyone?
Click to expand...
Click to collapse
As far as I know, this wakelock is caused because of the usage of 3G, like browsing, syncing, or any other thing that consumes data. This drain for me is usually between 10%-15%. There is no way t completely get rid of it, because it is part of the Android system.
There are many kernels that tried to fix this, about stock image and JW branch I don´t know, but maybe you should try to install an AOSP variant, because AOSP has many bugs fixed.
Also I remember I read somewhere that also bad radio could be causing this kind of issues, so try to get latest radio/bootloader for 4.3.
Hope it helps.
:highfive:
Galaxo60 said:
As far as I know, this wakelock is caused because of the usage of 3G, like browsing, syncing, or any other thing that consumes data. This drain for me is usually between 10%-15%. There is no way t completely get rid of it, because it is part of the Android system.
There are many kernels that tried to fix this, about stock image and JW branch I don´t know, but maybe you should try to install an AOSP variant, because AOSP has many bugs fixed.
Also I remember I read somewhere that also bad radio could be causing this kind of issues, so try to get latest radio/bootloader for 4.3.
Hope it helps.
:highfive:
Click to expand...
Click to collapse
To avoid having loose ends out there (in case anyone finds this thread during a search) - The problem turned out to be the latest radio. Not my lack of it :lol:
After flashing back to the .48 radio, from the .84 radio - everything is back to normal. No more weird Android OS wakelocks. ~3-4% battery drain overnight instead of 20-30%
There are more and more people popping up on XDA with this problem. So far, all of them that I have seen are outside the US. A few have even discovered the same fix.
So - future person that finds this thread during a search, look into the possibility of flashing back to version .48 of the radio. Hopefully this saves someone the trouble of experimenting with a bunch of different ROMs and kernels.
Calebz said:
To avoid having loose ends out there (in case anyone finds this thread during a search) - The problem turned out to be the latest radio. Not my lack of it :lol:
After flashing back to the .48 radio, from the .84 radio - everything is back to normal. No more weird Android OS wakelocks. ~3-4% battery drain overnight instead of 20-30%
There are more and more people popping up on XDA with this problem. So far, all of them that I have seen are outside the US. A few have even discovered the same fix.
So - future person that finds this thread during a search, look into the possibility of flashing back to version .48 of the radio. Hopefully this saves someone the trouble of experimenting with a bunch of different ROMs and kernels.
Click to expand...
Click to collapse
I put your post into my thread for people looking for an answer to this wakelock. Hope you don´t mind. Credits to you are there.
http://forum.xda-developers.com/showthread.php?p=44122105
:fingers-crossed:
Hi, I have installed Quarx's awesome 4.4.2 kitkat build and I am very impressed with its performance so far. I read up on the recent comments saying that the build from 6-11 is pretty stable and I believe it's true. I'm also running the 2.6 kernel along with the aerokernel app by blechd0se.
as you can see from the attached screen shot, my defy isn't entering deep sleep... I've frozen a lot of unnecessary apps and turned airplane mode on while leaving the defy alone for some time but it's still draining really fast. there is no deep sleep happening.
does anybody know how I can improve this phone?
thanks!
UPDATE: It seems I fixed my own issue by looking into every running app that looked like they were trying to collect data or keep the defy awake. from there I stopped/unchecked the services and then rebooted into recovery to wipe dalvic/cache, fixed permissions
only until then did it start deep sleep! hope this helps others as well
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.
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.