been struggling to get some "normal" battery life on my #nexus4 since 4.2.1 and now I heard from everyone about 4.2.2 gives improved battery life but not to me.
is there anyone that can help me with analyzing how I can improve my battery life?
the current 4.2.2 battery life shows no improvement at all comparing to my 4.2.1 battery life (was on MiNCO and Faux 123 kernel with the same kernel setup during 4.2.1)
Current 4.2.2 setup:
PA 3.0+
Faux 123, 07b1 (for 4.2.2), Intellidemand. Eco Mode off, Max1512 Min384, UV-150 across
battery dropped from 100% to 80%
7h50m (while I sleep) on battery on 3G data connection ONLY (screen cap attached, please ignore the subsequent charging time)
2 minutes screen on time
Deep sleep 86% as shown on CPU Spy (screen cap attached)
Partial wakelocks kind of minor as shown on BetterBatteryStat (screen cap attached)
Kernel wakelocks msm_hsic_host wakelock 42m, improved from 4.2.1 (screen cap attached)
Good signal (screen cap attached)
All Syncs on, Google Locations everything off except Location History
This is mainly a test comparing to previous 4.2.1 setup and battery consumption seems no improvement at all from 4.2.1 to now 4.2.2, as opposed to everyone's comment out there.
Anyone care to comment? Why I can't see any decent battery life as compared to 4.2.1? and as compared to users who have the same setup PA+Faux?
After comparing the CPU Spy screenshot (over 50m not sleeping) and Betterbatterystat (Other) screenshot (awake 59m), it seems like most of these wakelock came from msm_hsic_host (42m). Is it true that this msm_hsic_host wakelock will keep the phone awake independent from any app's wakelock? In other words, even if I have nothing installed, the phone will still wake up if I have this msm_hsic_host wakelock?
schizophrenia said:
been struggling to get some "normal" battery life on my #nexus4 since 4.2.1 and now I heard from everyone about 4.2.2 gives improved battery life but not to me.
is there anyone that can help me with analyzing how I can improve my battery life?
the current 4.2.2 battery life shows no improvement at all comparing to my 4.2.1 battery life (was on MiNCO and Faux 123 kernel with the same kernel setup during 4.2.1)
Current 4.2.2 setup:
PA 3.0+
Faux 123, 07b1 (for 4.2.2), Intellidemand. Eco Mode off, Max1512 Min384, UV-150 across
battery dropped from 100% to 80%
7h50m (while I sleep) on battery on 3G data connection ONLY (screen cap attached, please ignore the subsequent charging time)
2 minutes screen on time
Deep sleep 86% as shown on CPU Spy (screen cap attached)
Partial wakelocks kind of minor as shown on BetterBatteryStat (screen cap attached)
Kernel wakelocks msm_hsic_host wakelock 42m, improved from 4.2.1 (screen cap attached)
Good signal (screen cap attached)
All Syncs on, Google Locations everything off except Location History
This is mainly a test comparing to previous 4.2.1 setup and battery consumption seems no improvement at all from 4.2.1 to now 4.2.2, as opposed to everyone's comment out there.
Anyone care to comment? Why I can't see any decent battery life as compared to 4.2.1? and as compared to users who have the same setup PA+Faux?
After comparing the CPU Spy screenshot (over 50m not sleeping) and Betterbatterystat (Other) screenshot (awake 59m), it seems like most of these wakelock came from msm_hsic_host (42m). Is it true that this msm_hsic_host wakelock will keep the phone awake independent from any app's wakelock? In other words, even if I have nothing installed, the phone will still wake up if I have this msm_hsic_host wakelock?
Click to expand...
Click to collapse
Give Harsh's Kernel a try
It seems you have android apps running in the background. That could be your main battery life issue.
Sent from my Nexus 7 using Tapatalk HD
schizophrenia said:
Is it true that this msm_hsic_host wakelock will keep the phone awake independent from any app's wakelock? In other words, even if I have nothing installed, the phone will still wake up if I have this msm_hsic_host wakelock?
Click to expand...
Click to collapse
Yes, AFAIK it's a bug in the baseband (even with 4.2.2). That wakelock is much reduced when on wifi. My msm_hsic_host is often 20% when on 3G :/
as I said, after trying different roms and kernels, it's come down to almost a conclusion that my bad battery life comes from the darn msm_hsic_host wakelock which prevent my phone from sleeping.
Wifi battery life has been very reasonable.
thanks everyone.
Conclusion is, even if I uninstall all possible culprit apps, as long as I have such msm_hsic_host wakelock going on my phone won't deep sleep
I still haven't got a clue how to remove such wakelock.
battery drain investigation
did some testings with [email protected]
Test:
- ran both phones (under different carriers, different roms, same kernel) Nexus 4 on 3G data for a certain window of idle time and we both got around 2.4% an hour battery drain.
- we both got minimal app wakelocks (not 0, but negilgible) but our phones were not deep sleeping the whole time. Why? we both got 1/8 to 1/10 time of msm_hsic_host wakelock
preliminary conclusion:
- even if we install minimal amount of apps which do not cause anyway wakelock, the phone won't go 100% deep sleep as long as we have this signal/radio related kernel wakelock msm_hsic_host wakelock. we also do not know how to get rid of it
- unsolvable atm. seems like a radio/kernel issue that no one can fix (region specific?)
- so it was never about rogue apps that caused my battery drain.
Try others combo's with fresh installs
The msm_hsic_host wakelock is because the 3G modem is connected to the phone as an external USB device controlled by the hsic host controller. When the modem wakes up for any reason (apps sync, location, tower ping, etc...) the wakelock is requested. The problem is that the hsic host controller doesn't go back into suspend mode properly, this is a problem with the kernel. The result is that because the hsic host controller isn't asleep the phone wont enter deep sleep while it waits for the hsic host to suspend.
There is the additional issue that if your signal is poor the operations that caused the wakelock in the first place take longer to complete thus lengthening the time the wakelock is held.
The issue is significantly reduced on WiFi for obvious reasons, all the data is transmitted via WiFi so the 3G modem doesn't need to wake up nearly as often, it still wakes up to deal with tower checks and that sort of thing to ensure that it has voice connectivity, but those events are much rarer.
There are kernels available that attempt to solve this problem, Harsh kernel as suggested by another user has fixes in it along with a lot of other changes, the fixed kernel I'm working on is stock with these changes as well, either should help, it's not possible to eliminate this wakelock completely without shutting down the 3G modem which would of course prevent data and voice use of the phone, but they will reduce the wakelock and may help with your battery life.
thracemerin said:
The msm_hsic_host wakelock is because the 3G modem is connected to the phone as an external USB device controlled by the hsic host controller. When the modem wakes up for any reason (apps sync, location, tower ping, etc...) the wakelock is requested. The problem is that the hsic host controller doesn't go back into suspend mode properly, this is a problem with the kernel. The result is that because the hsic host controller isn't asleep the phone wont enter deep sleep while it waits for the hsic host to suspend.
There is the additional issue that if your signal is poor the operations that caused the wakelock in the first place take longer to complete thus lengthening the time the wakelock is held.
The issue is significantly reduced on WiFi for obvious reasons, all the data is transmitted via WiFi so the 3G modem doesn't need to wake up nearly as often, it still wakes up to deal with tower checks and that sort of thing to ensure that it has voice connectivity, but those events are much rarer.
There are kernels available that attempt to solve this problem, Harsh kernel as suggested by another user has fixes in it along with a lot of other changes, the fixed kernel I'm working on is stock with these changes as well, either should help, it's not possible to eliminate this wakelock completely without shutting down the 3G modem which would of course prevent data and voice use of the phone, but they will reduce the wakelock and may help with your battery life.
Click to expand...
Click to collapse
thanks a lot... these are really helpful information.
thracemerin said:
The msm_hsic_host wakelock is because the 3G modem is connected to the phone as an external USB device controlled by the hsic host controller. When the modem wakes up for any reason (apps sync, location, tower ping, etc...) the wakelock is requested. The problem is that the hsic host controller doesn't go back into suspend mode properly, this is a problem with the kernel. The result is that because the hsic host controller isn't asleep the phone wont enter deep sleep while it waits for the hsic host to suspend.
There is the additional issue that if your signal is poor the operations that caused the wakelock in the first place take longer to complete thus lengthening the time the wakelock is held.
The issue is significantly reduced on WiFi for obvious reasons, all the data is transmitted via WiFi so the 3G modem doesn't need to wake up nearly as often, it still wakes up to deal with tower checks and that sort of thing to ensure that it has voice connectivity, but those events are much rarer.
There are kernels available that attempt to solve this problem, Harsh kernel as suggested by another user has fixes in it along with a lot of other changes, the fixed kernel I'm working on is stock with these changes as well, either should help, it's not possible to eliminate this wakelock completely without shutting down the 3G modem which would of course prevent data and voice use of the phone, but they will reduce the wakelock and may help with your battery life.
Click to expand...
Click to collapse
by the way, would you happen to know if franco kernel has such fix?
I use his kernel because i do feel the fluidity and smoothness of the kernel plus I have his app for the customizations (including color controls).
I tried Faux but I just can't get the same speed.
EDIT: trying Harsh kernel at the moment
schizophrenia said:
I have tried removing almost all apps except the normal google ones ....
and coinciding with this, another user from US also reported that his hsic wakelocks are a lot higher when he travelled to Taiwan and Hong Kong and his thought is it may be due to the fact of highly congested data traffic
Click to expand...
Click to collapse
I decided to respond here instead of cluttering franco's kernel thread... because many of the possible culprits are not kernel related.
Unless congestion is causing re-transmissions, other ppl's traffic shouldn't affect your phone -- certainly not waking it up. Even with retransmits, you would think that there would only be one single but longer wakelock. (The phone really shouldn't wake every 12 seconds on average.)
However, you do have a high concentration of towers there. Perhaps there is more handshaking with towers? I use llama to automate tasks based on cell towers, and sometimes I see a -1:-1:-1 tower -- followed 1 second later by a real tower. So I assume that would have been 2 back to back wakelocks for me. (I'm going to try St. Murray Cell Connectivity Tracker to have a look.)
If it helps, I can tell you that I disable notification/checking on apps such as Play Store and I freeze many pre-loaded gapps -- currents, play books/mags etc., google+, network location, talk, news&weather and I don't use FB/xda apps. And I use gmail servers to poll my imap and then have any mail pushed to my phone.
From your prev screen caps, the one app I would freeze as a test is your VoIP / texting app (line.jp?)
schizophrenia said:
by the way, would you happen to know if franco kernel has such fix?
I use his kernel because i do feel the fluidity and smoothness of the kernel plus I have his app for the customizations (including color controls).
I tried Faux but I just can't get the same speed.
EDIT: trying Harsh kernel at the moment
Click to expand...
Click to collapse
hows harsh?
iammudd said:
I decided to respond here instead of cluttering franco's kernel thread... because many of the possible culprits are not kernel related.
Unless congestion is causing re-transmissions, other ppl's traffic shouldn't affect your phone -- certainly not waking it up. Even with retransmits, you would think that there would only be one single but longer wakelock. (The phone really shouldn't wake every 12 seconds on average.)
However, you do have a high concentration of towers there. Perhaps there is more handshaking with towers? I use llama to automate tasks based on cell towers, and sometimes I see a -1:-1:-1 tower -- followed 1 second later by a real tower. So I assume that would have been 2 back to back wakelocks for me. (I'm going to try St. Murray Cell Connectivity Tracker to have a look.)
If it helps, I can tell you that I disable notification/checking on apps such as Play Store and I freeze many pre-loaded gapps -- currents, play books/mags etc., google+, network location, talk, news&weather and I don't use FB/xda apps. And I use gmail servers to poll my imap and then have any mail pushed to my phone.
From your prev screen caps, the one app I would freeze as a test is your VoIP / texting app (line.jp?)
Click to expand...
Click to collapse
I did a very simple test about tower handshaking by turning off GPS and go to map and i can see my location, under 3G data, jumps back and forth every 10s to 20s. Does that mean the handshaking is not good?
LINE is one app that I have to live with even though it is one of the drainer because i need this app.
anyway I will revisit this later a bit as it's kind of late now. thanks a lot for your analysis and it's very beneficial to me
calanizzle said:
hows harsh?
Click to expand...
Click to collapse
Harsh yields low hsic wakelock
and after franco merged the fix, now r85/r86 yields as few as Harsh.
schizophrenia said:
I did a very simple test about tower handshaking by turning off GPS and go to map and i can see my location, under 3G data, jumps back and forth every 10s to 20s. Does that mean the handshaking is not good?
Click to expand...
Click to collapse
Unlikely that it indicated anything related to your battery.
Llama learned about 12 towers within my cell. I would expect much more in HK so I was only exploring what happens when you have so many towers within range -- whether the phone constantly have to handshake with every tower in range or only react to changes with the current tower. St Murray shows many changes (e.g. signal strength or location changes) but that doesn't cause an usually high wakelock count for me. So maybe there is only a wakelock on a handoff.
schizophrenia said:
LINE is one app that I have to live with even though it is one of the drainer because i need this app.
Click to expand...
Click to collapse
That's what I assumed... but it's worthwhile freezing it for 20 minutes and decide what to do if it turns out to be the culprit.
iammudd said:
Unlikely that it indicated anything related to your battery.
Llama learned about 12 towers within my cell. I would expect much more in HK so I was only exploring what happens when you have so many towers within range -- whether the phone constantly have to handshake with every tower in range or only react to changes with the current tower. St Murray shows many changes (e.g. signal strength or location changes) but that doesn't cause an usually high wakelock count for me. So maybe there is only a wakelock on a handoff.
That's what I assumed... but it's worthwhile freezing it for 20 minutes and decide what to do if it turns out to be the culprit.
Click to expand...
Click to collapse
i will try freezing a few apps and see
man. thanks a lot for the constant help.. although some of them i do not understand but i can see you are trying to help
appreciate it
schizophrenia said:
i will try freezing a few apps and see
man. thanks a lot for the constant help.. although some of them i do not understand but i can see you are trying to help
appreciate it
Click to expand...
Click to collapse
iammudd, check this out
freezed: LINE, Whatsapp, all Sync, Zooper Widget (different time frame as I did not have 7 hours for that)
Yes sure the battery got better a bit
it's quite likely it's LINE which caused the difference
let me try one more time by just freezing LINE maybe tomorrow or something
thoughts?
schizophrenia said:
freezed: LINE, Whatsapp, all Sync, Zooper Widget (different time frame as I did not have 7 hours for that)
Click to expand...
Click to collapse
Yes, those apps had some effect but not as much as I had hope. You're still getting 1357 msm_hsic (1 in 15 sec).
In the kernel wakelock screen, PowerManagerService shows you the total of partial wakelocks. You want to google the top items in partial wakelocks screen and see what's causing them. During sleep, I DON'T have sidekick_trafficintentservce, signalcollector nor rilj
Did a quick search and it seems like sidekick is related GoogleNow (which have been reported as a power hog since it uses gps and then keeps searching for nearby stores, etc.) The other 2 seem to be from location reporting. I don't have any of these 3 enabled if that helps so try disabling gps and location reporting in settings (and freezing gNow, latitude, fb reporting, etc)... You can decide what you want to keep later. (FB has also been reported to be bad for batt. Ppl use the web interface instead.)
You may also want to check out this tutorial on BBS http://www.alliance-rom.com/community/wiki/better-battery-stats-guide/ Also, I was referring to these apps to check cell towers:
https://play.google.com/store/search?q=llama and https://play.google.com/store/apps/details?id=org.stmurray.CellConnectivityTracker
iammudd said:
Yes, those apps had some effect but not as much as I had hope. You're still getting 1357 msm_hsic (1 in 15 sec).
In the kernel wakelock screen, PowerManagerService shows you the total of partial wakelocks. You want to google the top items in partial wakelocks screen and see what's causing them. During sleep, I DON'T have sidekick_trafficintentservce, signalcollector nor rilj
Did a quick search and it seems like sidekick is related GoogleNow (which have been reported as a power hog since it uses gps and then keeps searching for nearby stores, etc.) The other 2 seem to be from location reporting. I don't have any of these 3 enabled if that helps so try disabling gps and location reporting in settings (and freezing gNow, latitude, fb reporting, etc)... You can decide what you want to keep later. (FB has also been reported to be bad for batt. Ppl use the web interface instead.)
You may also want to check out this tutorial on BBS
http://www.alliance-rom.com/community/wiki/better-battery-stats-guide/
Click to expand...
Click to collapse
thanks for the info
I have freezed FB when screen off already. and I have turned off "all" location reporting/history etc. but I did have Google Now enabled.
Well, with you help at least I know I can achieve close to perfect idle drain IF I disable LINE and Google Now etc. But nevermind as I need these 2 apps to run. Still, as I assumed, my wakelocks would still be somewhat higher than in other countries.
i am undervolting 1 step at this moment. it helps a tiny bit. ha
Did you see a reduction in idle drain when you switched to Franco r85/86? I saw a reduction in msm_hsic_host wakelock but no reduction in battery drain (still 3%/hour).
zouden said:
Did you see a reduction in idle drain when you switched to Franco r85/86? I saw a reduction in msm_hsic_host wakelock but no reduction in battery drain (still 3%/hour).
Click to expand...
Click to collapse
on r85/86, for me personally, the hsic wakelock has been reduced together with battery drain.
but r90 the battery drain came back even though the hsic wakelock is still low
Google services is to battery consumer because it keeps phone awake. Something to do with location services causing it based on screenshot below. I'm latest nightly CM and seems to be the only one affected by this issue since nobody else complained about it
Sent from my SGH-I337 using Tapatalk 4 Beta
Same crap here as well. As u can see I'm on a totally different device. There was another thread on it with no solution I think.
---Sent from a viperx-ed OneX
Turn network location off. You really don't need it on all the time. That's the only way I know of getting rid of that wake lock.
I just realized. Location reporting turned itself back on, on maps app
I turned it back off. Will see if that helps.
When it was off I'd probably get 1min of that wakelock for the entire day.
---Sent from a viperx-ed OneX
mibtnt said:
I just realized. Location reporting turned itself back on, on maps app
I turned it back off. Will see if that helps.
When it was off I'd probably get 1min of that wakelock for the entire day.
---Sent from a viperx-ed OneX
Click to expand...
Click to collapse
If its of from boot, I don't get any.
jd1639 said:
Turn network location off. You really don't need it on all the time. That's the only way I know of getting rid of that wake lock.
Click to expand...
Click to collapse
x-actly.
NLP stands for Network Location Provider I would guess as it appeared to me first when Google Location Services asked me to switch on the WLAN location detection for "more accurate results".
Might be helpful if in some building where you don't get GPS locked but isn't really needed that much otherwise.
i have location access OFF and have HUGE DRAIN on Nlpwakelock
I had a similar problem on my Nexus4 - after I turned location services on and off again, the NlpWakelock would keep my phone awake and not go to deep sleep.
However, I found a fix for this issue. The culprit service is called GoogleLocationManagerService, and the solution is to disable this service only (I have no idea what other complications may arise from this, but at least my phone now goes to deep sleep). This service can be disabled with ROM Toolbox or a similar app.
In ROM Toolbox you go to App Manager, find Google Play Services and select Advanced Freeze. Now find the service (has a red border) called GoogleLocationManagerService and disable it. Now I can switch on and off location and still go to deep sleep, and location IS working.
ameinild said:
I had a similar problem on my Nexus4 - after I turned location services on and off again, the NlpWakelock would keep my phone awake and not go to deep sleep.
However, I found a fix for this issue. The culprit service is called GoogleLocationManagerService, and the solution is to disable this service only (I have no idea what other complications may arise from this, but at least my phone now goes to deep sleep). This service can be disabled with ROM Toolbox or a similar app.
In ROM Toolbox you go to App Manager, find Google Play Services and select Advanced Freeze. Now find the service (has a red border) called GoogleLocationManagerService and disable it. Now I can switch on and off location and still go to deep sleep, and location IS working.
Click to expand...
Click to collapse
i've been searching for a solution for ages and even followed the advice of another thread to disable location finding on both maps and google now and for some reason the nlpwakelock is still showing up. i'm going to try your fix but i was wondering if you've encountered any issues ever since disable googlelocationmanagerservice?
I often noticed nlpwakelock being the main culprit for Google Services battery usage. I even saw that it kept my phone awake for hours some days...
I tested some fixes and found that disabling the "use wireless networks" in the location services settings completely removed that wakelock.
Personally, I'd rather have that feature than save the little battery it uses. Despite keeping my phone awake for 1-2 hours on most days, as reported by GSAM Battery Monitor and Wakelock Detector, it uses a pretty small amount of battery:
Typically my phone's battery monitor will report about 20-30% of the battery used by Google Services. GSAM Battery Monitor seems to break that down into two parts: about 10% Google Services and 15% kernel, on average. However, these numbers are deceiving. That 10% that Google Services is only 10% of "App Usage" as reported by GSAM. Furthermore, App Usage is often only about 50% of my battery usage.
If my battery is at 50%, that means Apps only usage 50% * 50% = 25% of my 100% battery. Then, Google Services only used 10% of that 25%...so 2.5% of my overall battery capacity. I found this quite surprising considering the report that the wakelock keeps my phone awake for 1-2 hours...
So while Google Services is often shown as my #1 or #2 battery user in the App Sucker page, at 10-15% usually, that's only like 2-5% of the total 100% battery capacity each day. If I'm really going to be pushing my battery limits I might disable it to save some juice, but generally I find it's not worth disabling the feature to save such a small portion of my battery.
ender127 said:
i've been searching for a solution for ages and even followed the advice of another thread to disable location finding on both maps and google now and for some reason the nlpwakelock is still showing up. i'm going to try your fix but i was wondering if you've encountered any issues ever since disable googlelocationmanagerservice?
Click to expand...
Click to collapse
Hi. No, I've not had any issues,*but unfortunately the fix doesn't always work - but if the wakelock still persists, shutting down the service or location service again removes the wakelock, but it takes the manuel action of re-disabling the service again. Still better than having a wakelock though..
Hi everyone,
most of the time, my Axon 7 eats the battery absurdly fast, when only lying around (Standby). I opened a different thread that I caught it once discharging the battery even when turned off, but several other times, it did not do that again.
I noticed that BetterBatteryStats tells me that there is almost 0 time for "Deep Sleep" (3s) while it is "Awake (Screen Off)" almost all the time. Since I have no root, I do not know how reliable the data is (100% Awake + 21% Screen On + 0% Deep Sleep = 121% = lol).
I have checked the power management for all apps. All have "Allow deep sleep" activated.
The battery discharging is so heavy that one charge is not enough for one day of usage (with some hours screen on time).
Do you have experienced something like this, even with a different phone? Any ideas are welcome.
Regards,
Puni
You must have some app eating your battery. Try to remove some latest apps and reboot. If that doesn't work clear cache.. After that is only factory reset left...
FATPunisher said:
I noticed that BetterBatteryStats tells me that there is almost 0 time for "Deep Sleep" (3s) while it is "Awake (Screen Off)" almost all the time.
Click to expand...
Click to collapse
Okay, this is not really specific to the Axon 7, but it will work anyway. I precise I'm NOT ROOTED as well.
First :
- you better also install Gsam Battery Monitor, you'll have access to a better looking stats for Doze Mode. However, under Battery Manager (sorry, doesn't know how it is in english) / Battery Usage / Time battery used, you should have "Awake time" and monitor it here as well
- install Greenify as well, to try to apply Doze mode asap.
Second:
- Wifi on the axon, even when "turned off while screen is off", isn't. Manually switch the wifi off if needed.
- The same is for the GPS/Location services. Even when the toggle is OFF, you are still being tracked. Long-clic on the toggle, and make sure location is disabled (unless you need it). It will reset if you 'allow' Google Maps to enable location for yourself. Don't do it.
Third :
- Fiddle with Energy management, and learn about the 4 available toggles (disallow at startup, force close when screen is off, delay wake up, do not allow wakeup when in doze mode). Be careful about notifications tho, activating some switches might remove or delay them
- Go to security, administrators : do you have an app that shouldn't be there (which can wake up the phone)?
- Go to acessibility, same
- Do a reboot
- Watch what happens next
- Please report back here with BBStats + Gsam + Energy manager screenshots at least
Thanks a lot!
I will try your hints.
But disabling Wifi and GPS/Location is not really useful for me, because I need both all of the time. Could try it for seeing if it helps though.
Activating Air Plane mode allows Deep Sleep. Not useful, but nevertheless interesting.
I noticed that my Medion tablet with Android 4.4.2 (!) has the same issue. Must be an app installed on both I guess.
Wakelock Detector says it's Android System, AlarmManager. That is not too helpful.
On my Axon 7, Bluetooth triggers the Wakelock. It's 100% reproducible. Cannot be the whole story though, there must be more. The battery lasts at least twice as long without Bluetooth.
Solved!
Solved it!
It was the app MeinVodafone. It causes Wakelocks when Bluetooth is enabled.
I found a forum posting by somebody else confirming that.
Very nasty.
Thanks everybody!
P.S.: My tablet is a different story. Bluetooth is never active there. The wakelock vanished, but I have no idea what happened. Doesn't matter, unrelated.