Database Info

[Q] BT wakelock - Z3 never deep sleep

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.

Please Help: HP Pro Slate 21 AiO Touch 2 Closing App & Returning to Desktop (Reboot?)

Please Help: HP Pro Slate 21 AiO Touch 2 Closing App & Returning to Desktop (Reboot?)
I've got a unique situation as I use two of these AiO devices as security camera monitors and this has worked fine for months now. I bought two of these and have them in two different rooms and I have IP Cam Viewer set up on each one to display the cameras that I want to view from that room. I also have installed IP Webcam on each one so that I may use the camera built into each one to monitor the area in front of of the monitors. This worked fine for months and I hadn't updated any firmware or anything on them because they worked fine as they were so I had no need to change anything. Within the last couple of weeks I would wake up and both of the monitors would be on the home screen with the apps both closed. I don't know if it's rebooting the entire unit or if just the apps are crashing or what but it's a real PITA since they're mounted up high and require getting a step stool out to reach them each time. Since I started having issues I upgraded the device's firmware since there was an update available thinking it might fix my issue but it did not. I thought maybe a notification was causing the issue (even none of my other Android devices close out the apps when I have a notification) so I disabled the notifications for some apps that default to have them enabled since I'm not using them but it's still happening.
I dunno what to think here.
Anyone have any suggestions to fix this?

Bumping this up & hoping to get some help. The problem still persists and I haven't been able to get any closer to a solution. I've noticed a couple of times now that I will get an error that may or may not be related. The error says:
"unfortunately, com.wolo.service has stopped"
Now, I don't know if this is the causation of the issue because there has been times that the screen going black (from basically a security monitor) has caught my eye and when it comes back on to the home screen (about a second or so) there is no error message. My guess is that this is the behavior most of the time. I just thought that it might be related or help to solve the problem.
To recap, HP Pro Slate 21 running whatever version of Android came on it and I quite literally have two apps installed and ONLY two apps installed: IP Cam Viewer & IP Webcam which I run exclusively 24/7 and nothing more. It worked fine for months where IP Webcam would allow me to access the webcam on the monitors as an extra security camera and then use the display to display 9 of the security cameras as a monitor. Then, without any notice or any changes from me (I wasn't even updating any apps or anything since I had no issues) the monitor crashes several times a day. This requires me to launch IP Webcam again to allow access to the camera and then launch IP Cam Viewer to display the security cameras as a monitor. This works fine for about 1/4 or so of the day/night but then, inevitably, it will occur again.
This is SO annoying from a device that should just work w/o any input.

Sensors (Gyro, ACC, Mag) work in an erratic way on my new K1 Shield

Last days I started to setup my new Nvidia Shield K1. I like to use tis for flying a DJI Mavic Pro and rely on functioning sensors. I also have installed AndroSensor and GPS Status. If I start one of this Apps the ACC sensor is working for a seconds and then the signals are completely freezing. After this I only get it back to work after and complete reboot of the Tablet. Also the Gyro and the Mag sensor does not look to be working at all. I have never seen any data on this. AndroSensor is waiting for an event for this two sensors and GPS Status shows some initial movement on the level sensor but never any reaction on the compass. Sometimes I even seen the orientation is not working anymore and the screen will not adjust anymore. In most of the cases the orientation is still working even with the frozen sensor output in the two Apps. Im using this two apps with a few of my other Android devices without having issues. My actual version is Android 6.0.1 with Shield software 1.5(24.3.70.8). I already have done a complete factory reset but after this the problem is the same. Any feedback is appreciated. I may need to RMA the device.

I got an replacement K1 yesterday and set it up again. With stock Android version all sensors are working fine for a day. Than i made the OTA update to latest (same as above). Now ACC and Gyro is still working but not the MAG. The problem looks to be at least partial related to the firmware. Mag sensor problems are reported also in the past for the K1 already. Also MAG calibration will not make any change. Androsensor is reporting "waiting for event" and GPS Status shows and wrong compass direction (was fine with the initial firmware before OTA). Not sure what can be done here. I was expecting when i invest in an tablet of an reputable vendor (which is also not very cheap) i get something working well. Now i either have a second bad tablet or there is still something wrong with the firmware. It would be good if someone with the latest OTA update can confirm this behavior or can confirm that everything is working as expected. Many thanks.

Here is some more information for the case: _https://forums.geforce.com/default/topic/986542/shield-tablet/sensors-gyro-acc-mag-work-in-an-erratic-way-on-my-new-k1-shield/?offset=7

GPS not working well

Anybody seem to be having problems with their XZ Premium GPS not working as they should be? Mine is intermittent, sometimes when it works, it works well. But the moment I took a wrong turn and quickly fired up my Google Map navigator, it have problems detecting where I'm at. The Map will show the route, but my location is all over the place. It would pause and stay in that spot for a while, then move me on a lake or off road. I tried "GPS status" app to pin point where I'm at. It doesn't always want to work.
It's getting really annoying, I want it to be reliable when I need it. Lucky I still have my Z3 as backup. So far, seems like the Z3 is the best Sony ever made.

Same problem here...It is hard to start GPS....it shows current position, it lose it. I have to fight for 10 minutes until its stable.

the same issue here. OK after reboot, but problem is back again a after

I had that problem once while downtown... the buildings in that area are all old and packed pretty closely together. It just did not want to update for the life of me. Rebooting it did not seem to help it at all. Especially using the walking directions... forget it. I didn't have time to fuss with a gps app to see if I just wasn't getting any sat connections, but if it happens again I will.

Wow, so it's a known common problem. I hope it's software related so it can be fix by updates. Now I have to open two programs to make sure it always working all the time. Run "GPS Status" app and then open Google Map. Cumbersome.

Dial *#*#7378423#*#*, service test, GPS, Purge Assistance Data
This worked for me!

My use of Purge Assistance Data seemed to help, but I've had a couple of episodes of the problem since then where it didn't help. However, in the past three days the problem has not appeared. I cannot determine what has changed; many apps have updated as usual, and in order to try to determine if this is a hardware problem I ran phone in Safe mode during which problem did not appear. Interestingly (or not) the problem has not occurred during subsequently use of the phone in normal mode. BTW, I'm running the July 1st security update (45.0.A.7.90); the August 1st version has not been offered to me yet by the Software Update).

CyNoob said:
Dial *#*#7378423#*#*, service test, GPS, Purge Assistance Data
This worked for me!
Click to expand...
Click to collapse
Very nice. Seem to be working very well. Although I have not put it to full use yet since I'm working at home today. Let's see how it run when I go to work in the office tomorrow.

This won't help? - - https://forum.xda-developers.com/showthread.php?p=73337848

My XZ premium is 4 weeks old and had problems with the GPS since day one. The GPS was very unreliable taking me in the wrong direction and sometimes delays in giving instructions until after passing my turns. Using google Maps and high accuracy settings. Contacted Sony today and they have asked me to contact google first to make sure there is no software issues from their side before they can look at it. Meanwhile I will download a different navigation app and see if the same problem happens.
I did GPS location test but it seems everytime I attempt it the phone seems to take forever in finding anything so I give up normally after 10 mins.
If any one has found a solution to this problem please let me know (other than changing the phone of course)

My GPS problems went away with 45.0.A.7.120

You're not alone!! I always end up going wrong directions. Compass is very way off.
Sent from my G8142 using XDA-Developers Legacy app

+1 here. it's really frustrating as i use my GPS a lot.

I have the same issue. Second time I sent my phone to Sony. I will update the forum.

Was having this issue as well. Purned GPS Assistance data seemed to help. also did the battery trick. maybe sony should give us an update that will not allow gps to "turn off" when using apps that require it.
i searched on my phone some where on the hidden settings. The Destination was 30mins and about 20miles or so. Said the gps was only on for around 10. Cellular data was used too. This has to be a software issue. why it shuts off gps at times.

Is Galileo enabled as Sony's promise?

Stefanos1999 said:
Is Galileo enabled as Sony's promise?
Click to expand...
Click to collapse
What is Galileo? never heard of this. Is it a GPS feature or improvement? Such a fancy name.

CKkio23 said:
What is Galileo? never heard of this. Is it a GPS feature or improvement? Such a fancy name.
Click to expand...
Click to collapse
Galileo is a new GPS system developed by the EU, like GLONASS is the russian GPS and Beidou the chinese GPS.
And to answer the question, yes, our phone supports Galileo.

Artyomska said:
Galileo is a new GPS system developed by the EU, like GLONASS is the russian GPS and Beidou the chinese GPS.
And to answer the question, yes, our phone supports Galileo.
Click to expand...
Click to collapse
Yes, XZP supports Galileo. But it has not been enabled yet. :/

Had the same problem, gps not locking until I purged assistance data and rebooted the device, then it worked fine for about 48 hours until I had to repeat the process.
I completely solved this problem by uninstalling Google play services updates. This was a known issue for other phones some years ago.
Can anyone else confirm this solution?

Health logging issues

Hi All,
I have had a non-4G Watch 2 now for about 6 months.
Has worked really well especially as a GPS run tracker with music.
About a week ago I noticed that the watch had stopped tracking my steps.
Then I went for a run using the Huawei workout tracking app and it only recorded the time. No GPS distance, no heartrate...nothing.
I have since factory reset the watch about 5 times.
On my phone I've data cleared or uninstalled Google Play services, Services framework, Google Fit, Google App, Huawei Health, Android Wear, Huawei Wear.
Everything pairs up again properly, the phone updates apps no issues at all...then still no tracking.
The heartrate app on its own can do a heartrate measurement, so it doesn't appear to be a hardware issue. GPS map will also show my track, but the app records no distance data.
So it seems like some strange software issue.
Has anyone else experienced anything similar or have any other suggestions for what to try?
Thanks

So this looks like its a hardware issue.
I enabled developer options and found down the bottom there is a manufacturer test suite that steps through tests of the screen, NFC, vibration motor, screen, magnetometer, accelerometer etc.
It failed the accelerometer and barometric pressure sensor tests.
I unlocked the bootloader and flashed the stock image just to make sure everything was properly refreshed, then I was able to download the Wear 8.0 update as well.
Ran the test suite and it again fails the acceleromoter and barometric pressure sensor tests. They just don't respond at all.
Have logged a warranty case with Huawei who are good enough to generate a con note to have the device couriered to their repair agent.
I highly doubt that any repair will take place, they will just confirm it doesn't work (I relocked the bootloader and factory reset it) and then hopefully replace it.