My bluetooth worked perfectly for a while, then, it start to automatically turn it off (I wear a smartwatch so this is quite apparent). Then one day, i couldn't turn it on anymore.
In settings >> about phone >> Status
Bluetooth physical address is simply missing as if my bluetooth is either off or simply not there (see attached)
If I boot to BP Mode (sp?), there is a thing called CQATest app. Using that App, I can see bluetooth's mac address(see attached #3). But When I tried to do a bluetooth scan, it asked me to allow bluetooth to be turned on. And it simply tried to turn on for MINUTES, then failed to turn it on (see attached #4).
What could possibly goes wrong? could it be hardware? I have only flashed the stock ROM so far so I sincerely doubt I did something wrong.
I tried to flash the stock BTFM.bin a couple times, it didn't help. I am tempted to flash XT1572's bluetooth and give it a try (my model is XT1570).
Any ideas?
Mine had the Same same issue develop about 2 months ago. I have seen it outlined to be updated in the March security patch, but I don't know when we will see it. Vanilla android was supposed to receive quicker updates....so I don't know.
Related
Using a T-Mobile (USA) MDA, HTC Wizard, with the last official T-Mobile ROM, version 2.26.
Just very recently, Bluetooth often stops working, and I cannot get it back on again.
I try various ways of turning it back on. For instance:
1) The BT icon in the tray using the "Battery Status Today plug-in. (Actually I have the newest one, now called "Home Screen Plus Plus".)
2) An app called "Bluetooth Toggle, an icon to click that should switch BT ON and Off.
3) Comm Manager
4) Settings, Connections Tab, Bluetooth settings.
None of those work. In any of them, when I click where ever one should to turn on BT, the screen freezes there, only to be resolved by a soft reboot.
Sometimes on rebooting, BT is working again, but other times not. In fact, for the last several hours today, I have not been able to turn BT on again at all, despite reboots.
Does this sound like a hardware problem, or could it be something that could be resolved through software?
Any suggestions, registry tweaks, etc.?
I guess I could try a hard reset or reflash. But before trying something that drastic, which would require reinstalling all my apps, reconfiguring, etc., I'm wondering if there is something else I can try.
Or, if it's an irrepairable hardware problem, then I should perhaps look for another phone as soon as possible, as I want to have BT. I was waiting though, for a good new 3G WM phone to come out on T-Mobile in the next months. So, I would rather fix the MDA to use for a couple more months, rather than getting a Dash or Shadow now. (Wouldn't get the Wing, as I would prefer my next phone to be smaller and lighter than the MDA.)
Any suggestions on what to try, to see if I can get BT working again?
The change often seems to occur on re-booting. BT is working fine. On re-booting the MDA, BT is off, and I cannot turn it back on, as described above.
However, sometimes on rebooting again, it turns back on.
Any explanation for this?
Folks whose devices fit the criteria of what I have (see attached screenshot of my "About Phone" screen), please read on. I say this only so I can figure out what is common between us to be having the following Bluetooth issue:
1) Bluetooth toggle switch is OFF.
2) You slide the switch to "on". The phone sits there for approximately 10-15 seconds, but Bluetooth doesn't come on at any point, eventually the toggle switch in settings slides back to OFF.
3) There is no setting/method in the device that will turn Bluetooth on.
From when I received the phone from Google Play store, the only thing I have done to it is root it following this method.
Clearly, something with the rooting process did this (I am also having one other issue, but that one is less annoying than this Bluetooth one). But everything in my phone points to me still having the stock ROM but just having root access.
If I can just see the common thread between my phone and others having the same issue, maybe I can figure it out.
I don't want to flash my ROM or start from scratch for the fear of making matters worst for myself; the device appears to be working fine otherwise.
If I am completely unable to fix this, my only hope is that the eventual release of 4.4 KitKat would fix it on its own (and probably break my root at that point, haha).
After searching high and low for an answer to this, I ended up doing a factory reset (Menu-->Settings-->Backup & Reset-->Factory Data Reset) and that resolved the issue (while wiping my phone).
Thanks to the Android OS, I let my phone charge overnight while on WiFi and by the morning all the apps were reinstalled and updated, including the OS itself. My Kernal/Baseband/Build versions are all back to the ones I had when I got the phone from the Google Store, so that's comforting.
Now, I just have to find the absolute least intrusive way to root my phone without any ROMs or system-level updates that could screw up stuff like Bluetooth or USB Connectivity for me.
I know that this question belong in the relevant development forums, but I'm too new to post there.
Bell Canada S4 and after running TW 4.2.2 decided that I wanted to try Kitkat.
Started with the "Gummy" rom and install was fine. Worked well as a daily driver except for Bluetooth with my car (a 2012 Golf TDI). Every 5 minutes or so I will see the car display telling me the phone has been disconnected and then a minute later it reconnects. It would also disconnect mid-call. After some random time of doing this, the Bluetooth will "lock" in the turning on stage. By that I mean that if you go to the Bluetooth settings, it will say Bluetooth is turning on, and never go anywhere or connect. The only way to reset it was to restart the phone. If I was sitting in the car and working with it when it disconnected, I would see a message "Bluetooth Share has stopped" on the phone
Similar experience with Dandriod. Except that instead of locking up trying to turn on Bluetooth, the phone will reboot.
Anybody have any suggestions on where to look? And yes I clean flashed the ROMs, with a wipe cache/davlik after install. I'm liking 4.4 overall, but I need Bluetooth working consistently. The fine for driving with a phone in your hand is something I don't want to pay for.
I'm having the same problem outlined here:
https://forum.xda-developers.com/showpost.php?p=68864374&postcount=3
Basically, Bluetooth will work fine for a while but my Fitbit will drop out, usually overnight, sometimes throughout the day. This is annoying because it receives notifications like a smart watch. The only solid way to get it to reconnect is to forget the device in Bluetooth settings, turn Bluetooth off and restart the phone. When it comes back up, I open the Fitbit app, it turns on Bluetooth and re-pairs automatically and works great until a few to several hours later whenever it drops off again.
Additional info: When I got this Fitbit, it required a firmware update that failed probably 2 dozen times in a row from my Moto G4. I paired it to an old Samsung phone and the update went through quick and flawlessly the first time.
Aside from that, I've had issues with random restarts. Less so since I've reset the device but they still happen occasionally. Seems to me like I'll wake up and sometimes my Bluetooth is off, an indication that the phone reset during the night. Perhaps my need to restart the phone for Bluetooth issues has mostly eliminated the crash & restart issue, I can't recall the last time I had that problem but it was pretty frustrating, almost every day before I did a factory wipe & reset.
Aside from this, the phone works great. Stable through hour-long calls, loading up many apps at once, it does everything I need. My question is this: Should I hold out for the Nougat update , void my warranty and go with LineageOS or send the phone in to Motorola?
Using the nightly build of LineageOS (March 28) and seeing the same issue with my garmin watch. It took me multiple attempts to install an update via bluetooth yesterday. I thought it was the watch because the sync log said that the watch was disconnecting. This morning, I caught my phone's bluetooth restarting, or what I think is restarting. Specifically, the bluetooth is turning off then immediately turning back on. This is enough to disconnect my watch, and I also think this is what is causing my bluetooth headphones to disconnect periodically. From what I can tell, the bluetooth restart is happening about every two hours. The headphones will reconnect (but I have to restart my music), but the watch will not. I thought that perhaps the bluetooth is turning off to save power. Thus, I disabled battery optimization last week for Bluetooth Exptensions, Bluetooth MIDI Service, and Bluetooth Share, but the bluetooth restart issue persists. Not sure if this is a hardware issue in the G4, or a software issue. I'm really hoping it is a software issue that will be resolved in the Nougat update.
--------------------
Updated to the latest nightly build (April 4), which should be Nougat (Android version 7.1.1). Still having problems with bluetooth. The event log shows this output at the time that my phone last dropped bluetooth:
am_proc_died( 1188): [0,2084, com.android.bluetooth]
Click to expand...
Click to collapse
Log then shows that the service scheduler restarts bluetooth and the process is started. This stop and restart lasts less than 1 second, but it's enough to disconnect my bluetooth devices. Any idea on how to continue troubleshooting why bluetooth is stopping?
Something that you can try, is to go into settings, go to location, tap the three dots, tap scanning, turn off Bluetooth scanning.
I have the same problem with LineageOS 16 Android Pie, I solved it by navigating into the "Settings" and search for "Bluetooth Scanning" then turn it off.
Its description is "Allow apps and services to scan for nearby devices at any time even when Bluetooth is off. This can be used, for example, to improve location-based features and services"
I'm not sure how that really helps with location-based features and services but since it's taking an issue with my Bluetooth, I did not hesitate to turn it off.
Hello!
This has happened on multiple occasions:
When I flash stock, I have a routine that I go though, and one of the steps is to flash kevtweaks, found in one of the first few posts here:https://forum.xda-developers.com/ve...od-performance-memory-battery-kevp75-t3638524
When I flash, it usually breaks my Bluetooth and Wi-Fi by stopping their ability to turn on. One time while flashing I found that turning on Wi-Fi and Bluetooth before flashing makes it invulnerable to this... but only once. As of now my Wi-Fi does turn on, but sometimes it takes a few tries and takes about 30 seconds. And my Bluetooth doesn't even act like it's going to turn on.
This is happening on G935A & G935U. The weird thing is some have reported this, and others have had absolutely no problems, including the developer, kevp75.
Inside the tweaks, the dev and I have both looked and can't find anything that would break this (though obviously it's something)
I REALLY like his tweaks, they really help on this crappy eng boot. So I'd like to be able to use my Bluetooth and his tweaks.
Any help would be greatly appreciated