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.
Related
I have had this problem even from android 3. My xoom will randomly open to lock screen, and if I don't see it it will stay there and drain it's battery. Is there a way to make it close the screen again automatically, or even prevent it from opening? I have tried everything, shutting down wifi completely (for notifications) among others.
i have same issue
Do you have a bluetooth headset connected to your device. Mine would turn on by itself if I left and active bluetooth device attached. Once I started turning of the bluetooth antenta regularly this stopped happening for me.
To tell you the truth I do have my iphone connected to my xoom via bluetooth but the bluetooth feature is off at all times except for when I need it (for teathering purposes). I just checked again and it is off (since months that I opened it last time) both on mobile andxoom. I will delete the pairing though and hope for the best.
Any other suggestions?
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.
So... searched pretty much a month now for a solution, so don't flame me if I missed it ..
About 2 months with OPT, and pretty much a working phone on Oxygen 2.1.2 but it is unparallel to my OPO when it comes to OS with Cyanogen, in terms of beauty and speed. Yes, my OPO with less power under the hood works better than my OPT.
Tries Exodus ROM (CM12.1) and it is the one I like, but.. my BT doing all sort of funny stuff.. It turn itself off (symbol disappears from top of the phone) at random times. Events that kill BT are a phone call, deep sleep, and probably other events.
Rebooting the phone fixes it for up to 10 minutes. But obviously I am not going to boot the phone every time I need to use BT. I have a Moto 360 , a car audio , a headset, and a radar detector in the car connecting to my phone over BT. So pretty much I need BT on and up all day long...
What I discovered is if I clear data from Bluetooth share (setting->apps->all-> Bluetooth Share) my BT comes alive for a while again, so something in CM12.1 is messing it up. Obviously , I can't clear data every 10 minutes either... Not manually, anyways..
Just think every time I am getting to the car i need to clear data to hook the phone to the car. As soon as I do, the connection will stay on until I am done driving... and then drops again when BT in the car turns of, in few minutes. Really annoying.
The main problem is the Moto 360. It became a useless smart watch without the BT on the phone. Running it on wi-fi just kills the watch's battery, so that is not an option either...
Anyone else is in the same situation, or better, found a work around ? Somehow i can't seem to find anyone else with this issue.
Thanks,
BigE
Yes I have the same BT problem on my op2 with OOS 2.1.2 in car.
Nearly unusable audio (only phone function connects), audio (if it sometime works) don't stop during incoming call, phone book is not probably synced...
Impossible to fix it on my own! Oneplus must do that.
I hope with marshmallow will something fixed.
Regards Peterle
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.
please delete this post
Hi,
Recently I bought Coolpad R116. It run on default EUI system it was shipped with.
Everything seems fine, but after time is starts to turn on bluetooth by itself.
Sometimes it's on after screen unlock and gone few seconds after, sometimes it keeps being on - but I never turned it on myself.
It seems to be main battery eater for this device.. First time I kind a solved it by factory resetting, but it just returned.
As far as I remember location scanning is disabled (both wifi and bluetooth)
appreciate any suggestions on this