Are you experiencing the following Kernel wakelocks on your phone?
msm_serial_hs_dma
BTLowPower
It hapepns both with an LG G Watch R (5.0.2) and a regular BT headset.
If we take the second device, I do expect a Kernel wakelock while speaking or streaming music. The phone is active any way while performing this task.
What is strange is that even if there is no activity the wakelocks avoid deep sleep.
What is strange is that if I move away from the headset (and the BT icon goes the "non connected" status), the wakelocks are always there.
The effect is that my phone (both on 4.4.4 and 5.0.2) almost never ever sleeps, and sometimes get warm.
If I switch BT off, everything goes back to normal.
Any solution?
I'm rooted, so I can do further tests researches (I'm using BBS to spot the wakelock).
Is it possible that this is an hardware problem? I'm asking as it looks like I'm the only one with this issue!
Thanks.
I can imagine Android Wear as an issue but the Bluetooth headset is mind boggling.... I have a Sony SRS X7 Bluetooth speaker and that never causes this issue as far as I am aware.
abhinav.tella said:
I can imagine Android Wear as an issue but the Bluetooth headset is mind boggling.... I have a Sony SRS X7 Bluetooth speaker and that never causes this issue as far as I am aware.
Click to expand...
Click to collapse
I was pointing to Wear as well.
Then I noticed it just connecting to a BT headset.
Can you please connect to the speaker and play music for a minute or so. Then stop but keep the Z3 connected and report if you notice the wakelocks (provided you are rooted)? 10 minutes will be enough.
Could it be an hardware problem?
Thanks a lot.
Yeah, I checked again as you asked, still have not noticed any impact on battery life. Mind you I am still on KitKAt and I noticed you are on Lollipop. Have you tried restarting? Maybe it's like the old camera big on Nexus Kitkat release where camera app sometimes ran in the background till restarted.
I thought im the only one having this bluetooth issues..
If you are rooted, can you please check if you have the same wakelock as myself? Tx.
Inviato dal mio Nexus 10 utilizzando Tapatalk
abhinav.tella said:
Yeah, I checked again as you asked, still have not noticed any impact on battery life. Mind you I am still on KitKAt and I noticed you are on Lollipop. Have you tried restarting? Maybe it's like the old camera big on Nexus Kitkat release where camera app sometimes ran in the background till restarted.
Click to expand...
Click to collapse
Thanks for it.
Did you check wakelocks via Battery stats? It could be that a direct impact on battery life is not visible.
I did a test pairing my watch with a 5.1 Nexus 10. The wakelocks are there (with a slightly different name) but they are way less intrusive. They wake the phone up only when needed and the counted 4 minutes over a usage of 10 hours.
My conclusion is that the BT implementation on Z3 (regardless 4.4.4 or 5.0.2) is defective, from a wakelocks and battery perspective.
The fact that I'm one of the few noticing it, could also lead to an hw defect.
What's the expert view?
I have the same problem. Took me a while to figure out it is BT. Since turning off BT did not work (turns out it takes a restart of BT). Odd thing is it does not always happen. Over the past few days I have experimented on different apps (Beyondpod, Audible, Kugou), stopping at different situation (from app, stop from device then turn off, turn off device without first stopping), and on different BT devices (Plantronic Backbeat 903, Nissan Leaf, some no-name car kit (amazon.com/dp/B00L1VT5KS). So far I've ruled out the apps and Plantronic. But between the car and car kit I am not certain. Sometime I connects to both and it would have no problem. Some days (e.g. today) BT will keep the phone awake). Am I'm running more or less the same apps.
In all cases, reboot will fix the issue. But I don't always have luck with simply restarting BT.
I'm able to locate a few threads on the topic. looks like it is not limited to Z3. Z1/s and compact suffer from the same
community.o2.co.uk/t5/Android-Devices-Samsung-HTC-Sony/Z1-Compact-doesn-t-go-to-Deep-Sleep/td-p/648801/page/3
talk.sonymobile.com/t5/Xperia-Z1-Z1s/KitKat-757-Bluetooth-draining-the-battery/m-p/652237#U652237
Both referencing this link for the "workaround":
talk.sonymobile.com/t5/Xperia-Z1-Z1s/Z1-KitKat-687-Toyota-Touch-amp-Go-No-Deep-Sleep/m-p/640793#M22841
(I can't post link, so sorry about the non-linked text)
colonelheero said:
I have the same problem. Took me a while to figure out it is BT. Since turning off BT did not work (turns out it takes a restart of BT). Odd thing is it does not always happen. Over the past few days I have experimented on different apps (Beyondpod, Audible, Kugou), stopping at different situation (from app, stop from device then turn off, turn off device without first stopping), and on different BT devices (Plantronic Backbeat 903, Nissan Leaf, some no-name car kit (amazon.com/dp/B00L1VT5KS). So far I've ruled out the apps and Plantronic. But between the car and car kit I am not certain. Sometime I connects to both and it would have no problem. Some days (e.g. today) BT will keep the phone awake). Am I'm running more or less the same apps.
In all cases, reboot will fix the issue. But I don't always have luck with simply restarting BT.
I'm able to locate a few threads on the topic. looks like it is not limited to Z3. Z1/s and compact suffer from the same
community.o2.co.uk/t5/Android-Devices-Samsung-HTC-Sony/Z1-Compact-doesn-t-go-to-Deep-Sleep/td-p/648801/page/3
talk.sonymobile.com/t5/Xperia-Z1-Z1s/KitKat-757-Bluetooth-draining-the-battery/m-p/652237#U652237
Both referencing this link for the "workaround":
talk.sonymobile.com/t5/Xperia-Z1-Z1s/Z1-KitKat-687-Toyota-Touch-amp-Go-No-Deep-Sleep/m-p/640793#M22841
(I can't post link, so sorry about the non-linked text)
Click to expand...
Click to collapse
Thanks a lot for reporting your experience.
The main difference is that if I disconnect the BT device the drain and wakelocks continue, but if I switch BT off they stop.
Then I do not have BT listed in battery stats as a drain.
Here are your links in a click friendly form!
http://talk.sonymobile.com/t5/Xperi...tooth-draining-the-battery/m-p/652237#U652237
http://talk.sonymobile.com/t5/Xperi...-Touch-amp-Go-No-Deep-Sleep/m-p/640793#M22841
Unfortunately the workaround of turning off + wait + on BT is not a usable solution in a scenario where you use a smartwatch, that has to be connected the all day!!
I'm tempted to try an AOSP based rom to see if the problem is HW related or just SW.
I'll keep you posted.
Thanks.
I did a further test, in the below sequence:
- BT ON + connected to a Plantronics headset => wakelock + device always on
- BT ON + disconnected to a Plantronics headset => wakelock + device always on
- BT OFF + disconnected to a Plantronics headset => no wakelock + device sleep
- BT ON + disconnected to a Plantronics headset => wakelock + device always on
This thing is driving me crazy!!!!!
vittogn said:
Are you experiencing the following Kernel wakelocks on your phone?
msm_serial_hs_dma
BTLowPower
It hapepns both with an LG G Watch R (5.0.2) and a regular BT headset.
If we take the second device, I do expect a Kernel wakelock while speaking or streaming music. The phone is active any way while performing this task.
What is strange is that even if there is no activity the wakelocks avoid deep sleep.
What is strange is that if I move away from the headset (and the BT icon goes the "non connected" status), the wakelocks are always there.
The effect is that my phone (both on 4.4.4 and 5.0.2) almost never ever sleeps, and sometimes get warm.
If I switch BT off, everything goes back to normal.
Any solution?
I'm rooted, so I can do further tests researches (I'm using BBS to spot the wakelock).
Is it possible that this is an hardware problem? I'm asking as it looks like I'm the only one with this issue!
Thanks.
Click to expand...
Click to collapse
I've NEVER seen this happen on stock. I've only seen it happen on Sony AOSP, which currently has a broken BT LPM config.
Entropy512 said:
I've NEVER seen this happen on stock. I've only seen it happen on Sony AOSP, which currently has a broken BT LPM config.
Click to expand...
Click to collapse
Hi Andrew, that's great to have @Entropy512 input for what appears to be a very "personal" problem!!
I had some further investigation and discovered that:
In wakelock detector under kernel wakelocks I can notice that:
ipc000000ef_sensors.qcom has the highest number (7387 in 3h).
ipc0000008c_sensors.qcom (649 in 3h).
Under CPU WL I have UID [Type: System (Bluetooth) - bluedroid_timer] is the biggest WL. This looks to be a Lollipop general issue, as I had the same in KK I'm not pretty sure it is related.
In Sony talk forum I got a reply from a moderator: "That item you listed is known to prevent sleep from back in 2012 and to fix you need to decompile and rebuild the item with amended code - However you still could have an app hence why I mentioned the app to check."
It's strange to me to be asked, as a customer, to decompile and rebuild system stuff!!
Any chance there is an app causing my issue? Any suggestion on how I can root cause it?
Is there a chance it is an hw problem?
Thanks a lot.
vittogn said:
This looks to be a Lollipop general issue, as I had the same in KK I'm not pretty sure it is related.
Click to expand...
Click to collapse
By the way, I'm on Sony Store stock Kit Kat 23.0.1.A.5.77.
colonelheero said:
By the way, I'm on Sony Store stock Kit Kat 23.0.1.A.5.77.
Click to expand...
Click to collapse
Hi, my reference to Lollipop was only related to UID [Type: System (Bluetooth) - bluedroid_timer] CPU WakeLock.
All the rest of my findings where exactly the same in KK.
I got to Sony support forum and a very kind Sony guy promised to look after this issue.
I provided some system dump log taken via PC C after recreating the issue.
I'll keep you updated about the progress.
vittogn said:
Hi Andrew, that's great to have @Entropy512 input for what appears to be a very "personal" problem!!
I had some further investigation and discovered that:
In wakelock detector under kernel wakelocks I can notice that:
ipc000000ef_sensors.qcom has the highest number (7387 in 3h).
ipc0000008c_sensors.qcom (649 in 3h).
Under CPU WL I have UID [Type: System (Bluetooth) - bluedroid_timer] is the biggest WL. This looks to be a Lollipop general issue, as I had the same in KK I'm not pretty sure it is related.
In Sony talk forum I got a reply from a moderator: "That item you listed is known to prevent sleep from back in 2012 and to fix you need to decompile and rebuild the item with amended code - However you still could have an app hence why I mentioned the app to check."
It's strange to me to be asked, as a customer, to decompile and rebuild system stuff!!
Any chance there is an app causing my issue? Any suggestion on how I can root cause it?
Is there a chance it is an hw problem?
Thanks a lot.
Click to expand...
Click to collapse
That moderator had no clue... Something that happened on a 2012 device is of no relevance to a device released in late 2014. He's probably talking about the Xperia S which was a totally different device.
I'm not sure what's causing your problem - as I said, I've never seen it on stock, and only saw it on sony AOSP where the current Bluetooth LPM configuration is completely broken. (Planning on pushing patches for that tonight - but sony AOSP is pretty much independent from production builds right now.)
Entropy512 said:
That moderator had no clue... Something that happened on a 2012 device is of no relevance to a device released in late 2014. He's probably talking about the Xperia S which was a totally different device.
I'm not sure what's causing your problem - as I said, I've never seen it on stock, and only saw it on sony AOSP where the current Bluetooth LPM configuration is completely broken. (Planning on pushing patches for that tonight - but sony AOSP is pretty much independent from production builds right now.)
Click to expand...
Click to collapse
Thanks.
Any advice on how to discover if this a system/rom issue or caused by an app? Any system log I can take?
Entropy512 said:
That moderator had no clue... Something that happened on a 2012 device is of no relevance to a device released in late 2014. He's probably talking about the Xperia S which was a totally different device.
I'm not sure what's causing your problem - as I said, I've never seen it on stock, and only saw it on sony AOSP where the current Bluetooth LPM configuration is completely broken. (Planning on pushing patches for that tonight - but sony AOSP is pretty much independent from production builds right now.)
Click to expand...
Click to collapse
Hi Andrew, did Sony fix it in their recent AOSP 5.1?
OT ON: are u working on Omni for the Z3? OT OFF
Here a self explanatory comparison in between two very simalar days.
The first is with a BT device connected (just connected not streaming or talking).
The second (NO BT - ....) is without. The deep sleep attitude is very different!!
I was on KK yes, but the situation with 5.0.2 is exactly the same.
Hi!
Im on exynos version of S7 and i have a little problem.
On apeq stock firmware (i didnt noticed this before), when locking device / turning off screen, phone is activating Bluetooth on its own! Ive noticed Bluetooth icon disappearing moments after turning screen on. There is battery drain from Bluetooth sharing (or someting simmilar, i have non-english version of android set).
Bluetooth is disabled in options and Bluetooth scanning is turned off. I do not use any kind of Bluetooth hardware /dongles.
Is this a common bug?
I haven't seen or heard of this before, but just thinking about it...Do you have any location based apps running that night trigger your bluetooth like IFTTT or My Places?
No, i've got no such things besides standard google apps. No new apps since last rom update.
Well, i think i have found a guilty app.
I tried factory reset, then i have downgraded to APC8 firmware and still, after app installation bluetooth started to show up.
By trial & error method i started to delete apps one by one and found out that SwiftKey was the "bad apple". Unfortunately for me - it's my favorite keyboard...
Well, after uninstalling and replacing it with google keyboard all is fine for now.
Well I just upgraded to new Oreo and guess what? I can't use my Bluetooth headset anymore (Blue Tiger Elite). The audio gets distorted or breaking up. Failing to connect or disconnect to/from the phone. Was working fine before update. Tinkering Bluetooth settings in developer mode didn't help since they will stay unchanged after you open the menu again.
Have anyone encountered same problem?
When im paired up with the stereo in my work truck i noticed a pop every now and then.
stefilie said:
Well I just upgraded to new Oreo and guess what? I can't use my Bluetooth headset anymore (Blue Tiger Elite). The audio gets distorted or breaking up. Failing to connect or disconnect to/from the phone. Was working fine before update. Tinkering Bluetooth settings in developer mode didn't help since they will stay unchanged after you open the menu again.
Have anyone encountered same problem?
Click to expand...
Click to collapse
Audio streaming on Nougat for me was perfect all the time, now since my Oreo update I've experienced constant stuttering and/or growly distortion for a moment at least every ten seconds. Also 'Settings' keeps closing whenever I'm accessing any of my apps when changing permissions for example. It couldn't even pull up my app list, so I've done a backup and deleted at least 300 of my apps, and only now things are slightly better. I don't understand why everything is lagging so much now when before the update, all was perfect.. Help?
ScottOverly said:
Audio streaming on Nougat for me was perfect all the time, now since my Oreo update I've experienced constant stuttering and/or growly distortion for a moment at least every ten seconds. Also 'Settings' keeps closing whenever I'm accessing any of my apps when changing permissions for example. It couldn't even pull up my app list, so I've done a backup and deleted at least 300 of my apps, and only now things are slightly better. I don't understand why everything is lagging so much now when before the update, all was perfect.. Help?
Click to expand...
Click to collapse
Try factory reset, it worked for me. Good luck!
Yes, I'm having the same issue with bluetooth connection and the same Blue Tiger Elite. Just got off the phone with Verizon tech person he is thinking my headset is old enough technology that it won't stay connected.
Steve Phillips
Hi,
I want to ask if someone else has the problem that if the bluetooth is enabled
it automatically disabley if you put your phone to standby and wake it up again?
It happens with my phone even if a device is connected or not :/
- My device is locked and Stock 5.1.5
// EDIT: The Solution was to uninstall FireChat. Don't know why but this programm was the reason for the disconnects.
Maybe not the same issue, but mine has been disabling bluetooth every 5 minutes. Been driving me crazy and I'm currently troubleshooting it now. As far as I've been able to tell something is calling disable() on the bluetooth adapter (in catlog at least).
EDIT: Turning off bluetooth scanning in location settings seems to have fixed my issue.
I had the same problem on Oneplus 6. Indeed, uninstalling firechat helped.
Engelm said:
Hi,
I want to ask if someone else has the problem that if the bluetooth is enabled
it automatically disabley if you put your phone to standby and wake it up again?
It happens with my phone even if a device is connected or not :/
- My device is locked and Stock 5.1.5
// EDIT: The Solution was to uninstall FireChat. Don't know why but this programm was the reason for the disconnects.
Click to expand...
Click to collapse
Recently on my Note 10+ (SM-N975U1) running stock Pie and Dec 1 2019 update, I have been experience 2 issues.
Notifications for some apps are delayed
App updates hang on Google Play Store
For the app updates, they stall with "Download Pending" or the download stalls with <100% complete.
Resolution steps that have NOT worked
Clearing cache and data for Google Play Store
Rebooting phone
Rebooting into Safe Mode
Changing from Wifi to Cell Network Data and vice versa
Stop/starting app updates
Current Workaround
Closing/swiping the Google Play Store and opening it again. It will eventually complete downloading after multiple attempts and install/update an app - you will have to repeat this continuously for every app you want to install or update.
Is there anyway to debug this without doing a complete reset?
This is a problem I've had on many phones over the last few years. It took me a while to figure it out but it's bluetooth related. More specifically, I had the "Dynamic Lock" option enabled on my Windows 10 work laptop (which basically just locks my pc when my phone gets far enough away). I disabled this and now all my notifications come immediately and play store updates work as they should. I realize that you may not have that enabled and if that is the case then turn off your bluetooth for a while and see what happens. It worked for me and several others on the samsung community forum.
mtweisenbarger777 said:
This is a problem I've had on many phones over the last few years. It took me a while to figure it out but it's bluetooth related. More specifically, I had the "Dynamic Lock" option enabled on my Windows 10 work laptop (which basically just locks my pc when my phone gets far enough away). I disabled this and now all my notifications come immediately and play store updates work as they should. I realize that you may not have that enabled and if that is the case then turn off your bluetooth for a while and see what happens. It worked for me and several others on the samsung community forum.
Click to expand...
Click to collapse
Thank you! I turned off Bluetooth but nothing happened but after I rebooted with Bluetooth off everything started to work again. Is there a permanent fix for this? I am assuming turning back on Bluetooth will cause this to happen again? The strange thing this never happened to my Note 8.
selector said:
Thank you! I turned off Bluetooth but nothing happened but after I rebooted with Bluetooth off everything started to work again. Is there a permanent fix for this? I am assuming turning back on Bluetooth will cause this to happen again? The strange thing this never happened to my Note 8.
Click to expand...
Click to collapse
I have no idea why this happens. What I do know I have had this issue on LG phones, Pixels, and Motorola's. It isn't a Samsung thing. I think it's an Android Bluetooth issue.
This is an old thread - but in case someone else finds it, I came across someone's suspicions in another thread that their Plantronics headset was causing some kind of problem with their Bluetooth. I began unplugging my Savi headset when not in use and it seems to help... YMMV.
This has been going on since Pie; made me upgrade from my Note 8 to Note 10 and it came right back. Infuriating.
You may also want to try to rub a lucky stone and do some chanting as well, because it's about as effective as hoping for a fix after all this time.