Related
Hello all,
Something funny happened today with my Atrix today in that bluetooth just stopped working. Seems like the entire stack is corrupted. In using Extended Controls, the bluetooth widget is in permanent half green colour. Settings will try to turn on, but no luck. Reboot does nothing.
Using stock AT&T, which is unlocked and rooted.
Any ideas?
Regards.
Sent from my Atrix using Tapatalk.
dude i am having the same problem....did u find a way to switch it on
Afraid not. Very odd.
Sent from my Atrix using Tapatalk.
Having the same issue here. Reboot fix it temporarily (for one time use only). Can't find any related thread...
Issue resolved after update
Ok. Good to know. Will update after upgrading.
Thanks.
Sent from my Atrix using Tapatalk.
Flashed with Gingerblur on 1.57, now bluetooth stopped working again.
Well this is an interesting issue that crept up on me a few days ago. If I go to switch on my Bluetooth, the switch will move to on position but the Bluetooth will remain off. Reboot does nothing.
So after poking around here and there I noticed in tibackup that Bluetooth share 4.2.2 is uninstalled. As soon as I restore it, Bluetooth works again. However somehow it keeps uninstalling itself and I need to repeat the process again before it lets me switch on Bluetooth. I can't figure out the cause of this problem and how it's u installing on its own. Any help and guidance would be appreciated! Thanks
Well I've found that the Bluetooth share uninstalls after a reboot. What is causing this? Permissions issue? Anyone?
Sent from my Galaxy Nexus using Tapatalk 2
Not sure what's causing your issue. More info would help. Such as what ROM you are using if any etc
Sent from my Nexus 10 using XDA Premium HD app
I'm stock and rooted with an extended power menu mod.
I might have found to problem, still testing. There was an update to that Bluetooth app that I uninstalled and it seems to be working now.
If I don't encounter the problem for a few more days I'll call it solved Lol.
Sent from my Galaxy Nexus using Tapatalk 2
How do I stop this? My phone has not been able to deep sleep all morning. Battery is draining hard. Any tips? I tried searching for this online and I wasn't able to come up with a proper solution other than disabling this service, which might have repercussions I don't want.
Sent from my Nexus 4 using Tapatalk
I have the exact same problem, and I don't think our setups have anything in common
Sent from my Nexus 4 using Tapatalk
there is a thread one one of our N4 subsections to fix that. i dont know the link
I and oane friend had this wired bug his morning!
Also started for me could be its the same as the 4.2 data drain when it was trying to update to 4.3.
It got sorted after I restarted but it happens again I'll try applying the same fix and see if it works.
I had that same wakelock and it was cutting my battery in half.
I downloaded this aplication https://play.google.com/store/apps/details?id=cn.wq.disableservice
Then navigate to system apps/google play services/show full name and uncheck this first option on my SS
That worked for me,no more battery draining from cacheupdateservice
You must be rooted offcourse.
I have the same problem, any solution to unrooted devices? This is very annoying, when a service wakelock seems to disappear, another one appears.
Tapatalking from Desire
Hi guys, clearing the cache for google play services (+rebooting phone) solved the problem in my case.
Im rooted, but this should also work on unrooted phones
http://www.androidpolice.com/2013/1...lay-services-seems-to-be-a-battery-hog-today/
hansgagel said:
Hi guys, clearing the cache for google play services (+rebooting phone) solved the problem in my case.
Im rooted, but this should also work on unrooted phones
Click to expand...
Click to collapse
Same here. Noticed this yesterday as my battery was draining like crazy. I just went to the Google Services app and cleared all data and have not seen this wakelock anymore. Galaxy S4...not rooted.
Hello everyone
This is my first post here, and I need help with a rather bizarre issue that I am facing
I have a galaxy S4 i337m, it was rooted at ofw 4.3, then I decided to update, using kies, to 4.4.2, then after restart the wifi, and wifi hotspot doesn't turn on at all, I already did a backup using TWRP of the 4.3 state, but before I revert back, I was wondering if there is anything I can do to get rid of this affliction
Regards,
Nas Makkiya
Maybe you should restore, i want to update with kies too but now i read this.
Sent from my GT-I9505 using xda app-developers app
woldtom said:
Maybe you should restore, i want to update with kies too but now i read this.
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
That is what I am trying to avoid doing here, see I still have to 4.3 backup image, I can just revert to it, but I don't want to do a restore since I will lose all the app settings that are stored in the Data, System, etc Folders
Anything I can do to reset WiFi settings?
nasiraod said:
Anything I can do to reset WiFi settings?
Click to expand...
Click to collapse
Ya... I had the same prob a couple days ago. You have to do a restore with kies.
dahunt said:
Ya... I had the same prob a couple days ago. You have to do a restore with kies.
Click to expand...
Click to collapse
It's seems that way, but do you have any idea what's causing it?
Same issue here
Hello all. After upgrading to 4.4.2 (OTA) wi-fi worked for a couple of weeks and then went kaput. It will work momentarily after a restore and then won't turn on again. Kies can only restore to 4.3 at the moment and I like 4.4, any other solutions? I also tried the tar.md5 image from another thread and this keeps on keeping on
Possibly related, sometimes the phone will not wake, I'll let it alone for 30 sec and it will respond again. Wake issues?
Anyone around XDA have any suggestions as to what the issue is or a possible fix? Might it be a modem issue? Could the wake from sleep issues be related to waking wifi and bluetooth? Heeeelp!!
This might or might not be relevent to the issues in this thread:
http://www.androidpolice.com/2014/0...-here-is-what-you-should-expect-to-see-fixed/
According to that article, when 4.4.3 is released it will address known issues:
"What's New?
With the introduction out of the way, let's take a look at the list of fixes, prioritized by me in order of importance. The list may not be complete, but this is what we've been told so far:
frequent data connection dropout fix
mm-qcamera-daemon crash and optimization fixes
camera focus in regular and HDR modes fixes
Power Manager display wakelock fix
multiple Bluetooth fixes
fix for a random reboot
app shortcuts sometimes got removed from launcher after update
USB debugging security fix
app shortcuts security fix
Wi-Fi auto-connect fix
other camera fixes
MMS, Email/Exchange, Calendar, People/Dialer/Contacts, DSP, IPv6, VPN fixes
stuck in activation screen fix
missed call LED fix
subtitle fixes
data usage graph fix
Internet telephony fix
FCC compliance fix
miscellaneous fixes"
Of course AT&T will take their time to customize the update as they see fit so it may or may not include all, less, or more. AND NOBODY KNOWS WHEN AT&T WILL RELEASE 4.4.3...SO DON"T ASK.
Hopefully, it will help to fix some of the issues people on 4.4.2 are experiencing.
Solved
scott14719 said:
"What's New?
[...]
Power Manager display wakelock fix
multiple Bluetooth fixes
fix for a random reboot
[...]
Wi-Fi auto-connect fix
[...]
miscellaneous fixes"
Click to expand...
Click to collapse
Wow, thank you sir! Looks like 4.4.3 is going to fix what 4.4.2 broke. :good:
Ever since I flashed 5.0 to my 900V, my battery life has gone significantly down. Now this can be expected to some extent as I can no longer use Amplify to control NlpCollectorWakeLock (which is one of a few wakelocks going to town on my battery). One of the others is bluedroid_timer, which is part of bluetooth. I did some searching and I saw some other people with the same issue, but no answers. I use a Moto 360 on a daily basis, use bluetooth streaming in my car, and use bluetooth headphones at the gym, so turning off bluetooth isn't really an option. Bluesleep is another one that is spending a lot of time running. Anyone have any ideas? I've read a few threads where people mention this problem, but no one has posted any answers yet. Here is an album of my wakelocks.
Did you ever figure this out? I'm experiencing a very similar issue.
I'm not rooted, so I can't see the specific wakelocks but it's absolutely Bluetooth related, even with all device profiles deleted. If I have the BT radio on, my battery gets hammered and the phone never goes into deep sleep, turn the radio off and all is normal.
MattE303 said:
Did you ever figure this out? I'm experiencing a very similar issue.
I'm not rooted, so I can't see the specific wakelocks but it's absolutely Bluetooth related, even with all device profiles deleted. If I have the BT radio on, my battery gets hammered and the phone never goes into deep sleep, turn the radio off and all is normal.
Click to expand...
Click to collapse
I just started experiencing this as well. I'm on a T-Mobile S4, running a GPE rom. It started happening in the last month, not exactly sure when. I ran a rooted TouchWiz stock rom before that and I don't recall ever seeing it.
So you're running fully stock? I was curious if I installed some weird app or software package that messed with things, but if you're running stock that would seem to rule that out..
dirkdigles said:
I just started experiencing this as well. I'm on a T-Mobile S4, running a GPE rom. It started happening in the last month, not exactly sure when. I ran a rooted TouchWiz stock rom before that and I don't recall ever seeing it.
So you're running fully stock? I was curious if I installed some weird app or software package that messed with things, but if you're running stock that would seem to rule that out..
Click to expand...
Click to collapse
yup, Galaxy S5 with current Verizon build of Lollipop, not rooted, just Nova launcher and my usual apps. Since the bluetooth battery issue, I've tried reboots, clearing cache partition, deleting all BT device profiles, etc. Everything short of an FDR, which I don't have time for right now.
MattE303 said:
yup, Galaxy S5 with current Verizon build of Lollipop, not rooted, just Nova launcher and my usual apps. Since the bluetooth battery issue, I've tried reboots, clearing cache partition, deleting all BT device profiles, etc. Everything short of an FDR, which I don't have time for right now.
Click to expand...
Click to collapse
Thanks for the reply.
In lots of google searches, seems like many have this issue, but i couldn't find a solution anywhere, nor any consistency among devices. Seems that some custom kernels fix the issue.
But if you want to submit bug reports here, there's an official Google bug report thread on the issue that is alive:
https://code.google.com/p/android/issues/detail?id=87778
dirkdigles said:
I just started experiencing this as well. I'm on a T-Mobile S4, running a GPE rom. It started happening in the last month, not exactly sure when. I ran a rooted TouchWiz stock rom before that and I don't recall ever seeing it.
So you're running fully stock? I was curious if I installed some weird app or software package that messed with things, but if you're running stock that would seem to rule that out..
Click to expand...
Click to collapse
dirkdigles said:
Thanks for the reply.
In lots of google searches, seems like many have this issue, but i couldn't find a solution anywhere, nor any consistency among devices. Seems that some custom kernels fix the issue.
But if you want to submit bug reports here, there's an official Google bug report thread on the issue that is alive:
Click to expand...
Click to collapse
Thanks! the Google bug report is an interesting read, we're definitely not alone in this. I'm gonna try a few things based on what I read there and report my findings.
MattE303 said:
Thanks! the Google bug report is an interesting read, we're definitely not alone in this. I'm gonna try a few things based on what I read there and report my findings.
Click to expand...
Click to collapse
My solution was a particular app was causing it. Same for another user if you read the thread.
The app for me was MyRadar. Another user had a problem with Gas Buddy.
Both of these apps were recently updated to add bluetooth permissions.
dirkdigles said:
My solution was a particular app was causing it. Same for another user if you read the thread.
The app for me was MyRadar. Another user had a problem with Gas Buddy.
Both of these apps were recently updated to add bluetooth permissions.
Click to expand...
Click to collapse
I did see that and I am a GasBuddy user. There was also mention of NFC, that was the first thing I looked at. Experimenting now with GasBuddy removed.
I'm not rooted so I can't check for individual wakelocks, I have to just run it for a while, then look at the "Awake" bar graph in the stock Battery app, so it takes while to see if anything changed. I really wish Google would give us the choice whether to let 3rd party apps see the detailed battery stats, locking that down made it so much harder to diagnose this kind of thing without root.
Glad you got yours sorted out!
dirkdigles said:
My solution was a particular app was causing it. Same for another user if you read the thread.
The app for me was MyRadar. Another user had a problem with Gas Buddy.
Both of these apps were recently updated to add bluetooth permissions.
Click to expand...
Click to collapse
I understand your issue completely, but why in the world does gas buddy need bt permissions? ? ?
Sent from my SM-G900V using Tapatalk
ldeveraux said:
I understand your issue completely, but why in the world does gas buddy need bt permissions? ? ?
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
No idea, but it's mentioned on their Playstore page in a recent app update:
4.6.6
Get deals while you are filling up by turning on Bluetooth.
Click to expand...
Click to collapse
---------- Post added at 12:14 PM ---------- Previous post was at 11:43 AM ----------
so far it's looking like GasBuddy was the culprit in my case. I've been running several hours with GasBuddy removed, both NFC and Bluetooth are on, and battery usage/wakelocks appear normal.
I'm gonna give it a day or so to see if the problem spontaneously returns, then re-install GasBuddy and see what happens.
MattE303 said:
No idea, but it's mentioned on their Playstore page in a recent app update:
---------- Post added at 12:14 PM ---------- Previous post was at 11:43 AM ----------
so far it's looking like GasBuddy was the culprit in my case. I've been running several hours with GasBuddy removed, both NFC and Bluetooth are on, and battery usage/wakelocks appear normal.
I'm gonna give it a day or so to see if the problem spontaneously returns, then re-install GasBuddy and see what happens.
Click to expand...
Click to collapse
Definitely a GasBuddy issue on my phone, "Awake" bar graph becomes a solid block soon after installing GasBuddy, and returns to normal after uninstalling it. I've repeated this test a few times.
MattE303 said:
Definitely a GasBuddy issue on my phone, "Awake" bar graph becomes a solid block soon after installing GasBuddy, and returns to normal after uninstalling it. I've repeated this test a few times.
Click to expand...
Click to collapse
I started experiencing the issue with excessive wakelocks from Bluedroid_timer on my stock Nexus 6 about a month ago. Noticed my battery life dropped significantly as a result. Used Permission Friendly Apps to see which apps were using BT and if I happened to install any around the time this problem began. Only new apps indicating BT connectivity were GasBuddy and Netflix. No idea why GasBuddy needs BT but I'm pretty sure I installed it about the same time the wakelock issue began. Good to know someone else saw the same thing. Just uninstalled it and waiting to see if the wakelocks stop.