I use a few weeks the "CM-11-20140308-Snapshot-M4" on my samsung relay, and I saw that msm_otg this prevents the phone from sleeping.
OTG function does not interest me, I can delete it to solve the problem in any way?
There are 4 folders in memory with the name "msm_otg" if I remove them I solve the problem?
Thanks for the replies.
Balthasar85 said:
I use a few weeks the "CM-11-20140308-Snapshot-M4" on my samsung relay, and I saw that msm_otg this prevents the phone from sleeping.
OTG function does not interest me, I can delete it to solve the problem in any way?
There are 4 folders in memory with the name "msm_otg" if I remove them I solve the problem?
Thanks for the replies.
Click to expand...
Click to collapse
Why don't you try disabling the app?? Or download greenify and wakelock detector and greenify the app. SHould stop all the wakelocks related to the otg app without causing any problems i'm guessing
Hi guys,
I have installed both Pushbullet and Light Flow on my Nexus 5. However it seems that these apps sometimes don't work as well as they should. For example I don't get all my notifications mirrored to my Chromebook, and the notification LED does not always blink when these notifications appear on my Nexus.
So my question is whether there is a possibility that because you have to allow both apps to have notification access to your phone that they interrupt each other when you get a notification?
Not sure about that but have you tried removing lighflow temporarily?
rootSU said:
Not sure about that but have you tried removing lighflow temporarily?
Click to expand...
Click to collapse
I did not try this. However I did reinstall Light Flow yesterday, it wasn't for this particular reason but it did solve some other problems I had with Light Flow. Also I have been using Pushbullet before I got Light Flow, and it seemed to work fine before that. The problems also seemed to occur most with Google Hangouts which I also have the extention from on my Chromebook. Could this be the problem then?
To clarify: I do not mean to find a solution for this, only if it is a simple one (which does not involve deleting one of the two apps) I am willing to try it. It is just for me to know that it indeed can (or can't) give problems so I don't have to worry about this.
Rikrr said:
I did not try this. However I did reinstall Light Flow yesterday, it wasn't for this particular reason but it did solve some other problems I had with Light Flow. Also I have been using Pushbullet before I got Light Flow, and it seemed to work fine before that. The problems also seemed to occur most with Google Hangouts which I also have the extention from on my Chromebook. Could this be the problem then?
To clarify: I do not mean to find a solution for this, only if it is a simple one (which does not involve deleting one of the two apps) I am willing to try it. It is just for me to know that it indeed can (or can't) give problems so I don't have to worry about this.
Click to expand...
Click to collapse
Well, we can't know a solution until we know the cause. If temporarily disabling / uninstalling lightflow lets pushbullet work correctly, we know it is a conflict. Otherwise, we're left guessing. This is just basic troubleshooting.
rootSU said:
Well, we can't know a solution until we know the cause. If temporarily disabling / uninstalling lightflow lets pushbullet work correctly, we know it is a conflict. Otherwise, we're left guessing. This is just basic troubleshooting.
Click to expand...
Click to collapse
Ok, so after disabling Light Flow I checked whether it worked properly again or not. And it still did not work as I hoped it would with Google Hangouts. So it must be the case that it has to do with the synchronisation or so which makes the notifications work buggy with Pushbullet and the extention on my Chromebook combined. I will leave it at this and try to live with it
Thanks for the help kind sir!
No probs. Might be worth contacting pushbullet developer.
Sent from my Nexus 5 using Tapatalk
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.
After updating my Gear S3 to Tizen 3.0 I haven´t been able to get my Endomondo app on my watch to save or sync my workouts. I´ve got the latest app versions on both my phone and watch and have tried uninstalling and installing again with no luck. I suppose it has got something to do with the Tizen update as there were no problems before the update.
Anyone got a workaround for this problem?
Same here...and also there was an update few days ago. But it did not solve the issue.
Have you written to endomondo team about it?
moffe said:
Same here...and also there was an update few days ago. But it did not solve the issue.
Have you written to endomondo team about it?
Click to expand...
Click to collapse
Yeah, but no answer yet
This morning I tried Uninstalling and then installing the Endomondo app on both my S7 and Gear S3 and now there are no problems saving my workouts.
Endomondo support wrote to me that there are several users having troubles saving workouts and that they have contacted Samsung about this problem.
I removed Endomondo from my Gear S3 and added it again...it seems to be working now.
I followed your guys, reinstall and it works now !!!.
I've just tried Endomondo on my Gear S3 to record a kayaking activity. It worked, but the battery drained so fast from 98% to 15% for 4 hours. I must stop Endomondo in S3 to save battery, since I still had a few hours in the activity. It could only record half of the trip impractically. Wifi and bluetooth had been switch off previously, and audio alert of the app was disabled. The outdoor screen brightness was forced to 8 by this app in S3 that couldn't be decreased during the activity to save battery power.
I dare not to use this app for my outdoor activity again such as hiking and kayaking, unless there's another workaround to let me use it to record a trip for about 6 to 8.5 hours.
Hello
Sometimes I force stop WhatsApp to stay off the app while I'm connected to the Internet but busy
I just got the Samsung a13 4G. However WhatsApp autorestarts even after force stop on this device and it's really frustrating. Didn't happen on my previous devices
Anybody who experienced this before?
Anyone with an idea please?
Damy399 said:
Anyone with an idea please?
Click to expand...
Click to collapse
Damy399 said:
Hello
Sometimes I force stop WhatsApp to stay off the app while I'm connected to the Internet but busy
I just got the Samsung a13 4G. However WhatsApp autorestarts even after force stop on this device and it's really frustrating. Didn't happen on my previous devices
Anybody who experienced this before?
Click to expand...
Click to collapse
It automatically restarts because it is designed to run in the background to monitor for updates and send you notifications related to WhatsApp. All social media apps do this.
Droidriven said:
It automatically restarts because it is designed to run in the background to monitor for updates and send you notifications related to WhatsApp. All social media apps do this.
Click to expand...
Click to collapse
Well, it didn't happen on my last Samsung. It was my perfect way of staying offline