Related
So, for some reason, my Bluetooth doesn't function properly as it should, which is weird, since my phone is still on stock, and the only modifications I've made are unlocking the bootloader and rooting the device. I also installed Power Toggles, but I don't think that's the issue at hand.
Pretty much, whenever I turn the bluetooth on, it tries for a while to turn it on, then gives up and won't let me turn it on. At that point, I have to restart the phone, and when it reboots back up, the bluetooth is on without me having to start it up. Then it works properly, but if I wish to use the bluetooth again the next day, I have to repeat the process of rebooting the device. Any ideas?
I had this issue when I Downloaded a FM radio app from the Play store to see if it would work. I just deleted the app. Went into safe mode then into normal mode and it fixed it.
Don't know what you case can be. But you can try going into safe mode and back to normal and see if there are any different results.
Sent from my Nexus 4 using Tapatalk 2
I had this same problem after installing Torque, and using it with default settings that auto-enabled/disabled bluetooth. After turning all that crap off it is back to normal.
I use bluetooth for audio playback and an hf/A2DP headset dialing via Motospeak, as well as Torque with a bluetooth odb2 interface, and it all works perfectly since disabling Torque's auto-bluetooth settings. My only issue is that it takes Motospeak a bit long to restore audio playback after a hf call command.
I would look for an app that you have that is the controlling bluetooth on/off.
I wonder if it isn't a software bug. I have the same issue but I don't have any apps that are causing the issue of atleast from what I can tell. I'm also unlocked and rooted.
I removed Bluetooth from Power Toggles. It's been two days and all seems well. Now we wait.
yahoowizard said:
So, for some reason, my Bluetooth doesn't function properly as it should, which is weird, since my phone is still on stock, and the only modifications I've made are unlocking the bootloader and rooting the device. I also installed Power Toggles, but I don't think that's the issue at hand.
Pretty much, whenever I turn the bluetooth on, it tries for a while to turn it on, then gives up and won't let me turn it on. At that point, I have to restart the phone, and when it reboots back up, the bluetooth is on without me having to start it up. Then it works properly, but if I wish to use the bluetooth again the next day, I have to repeat the process of rebooting the device. Any ideas?
Click to expand...
Click to collapse
This happened to me as well
Sent from my Nexus 4 using xda app-developers app
strobex said:
This happened to me as well
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Similar problems here, the weirdest thing is idk which app causes that. Because I didnt install that much. Only thing I notice is it happened when the wifi is on.. Does anyone have similar problem??
Same problem here. I have a lot of apps but none I can think of that do anything with Bluetooth.
Sent from my Nexus 4 using xda app-developers app
yahoowizard said:
I removed Bluetooth from Power Toggles. It's been two days and all seems well. Now we wait.
Click to expand...
Click to collapse
Nope, still doesn't work.
Try going into safe mode.. See if it works, and then go back to normal mode.
Sent from my Nexus 4 using Tapatalk 2
Nothing yet? I'm just curious as to whether it's just a few people experiencing this, or a lot, since there doesn't seem to be that much talk about it.
I use Bluetooth everyday on my way home from work just to connect to my Bluetooth headset. Out of 14 days I may get one day where I turn Bluetooth on that I don't have to reboot for it to work.
Sent from my Nexus 4 using xda app-developers app
So we're on 4.2.2, I've went through safe mode and back a few times, and I've uninstalled and installed applications having to do with the Wi-Fi. Problem still seems to be there. It's just somewhat of a hassle to have to power down my phone completely, then start it back up, everytime I get into my car. I feel a hard reset mighttt fix the issue, but just looking for another way as of now.
My phone also have the same problem.. the bluetooth won't turn on.. stock 4.2.2 locked bootloader and not root yet.. anyone has a solution..
I have a gear live from io2014.
I've paired it with a galaxy tab 10.1 (p4wifi) running 4.4.4.
After a couple days I'm noticing the bluetooth between the tablet and the watch is "not connected".
I can toggle the watch connection on the tablet gear app, and the gear app will try to reconnect to the watch but fail.
(The gear app on the tablet/phone does an exponential back off which I think is odd cuz it will end up waiting a long time to reconnect if it fails a few times.)
In order to get it to reconnect I have to reboot the watch. Annoying.
Anyone see this? Maybe its an issue with the tablet?
The
-jeff
jeffcrilly said:
I have a gear live from io2014.
I've paired it with a galaxy tab 10.1 (p4wifi) running 4.4.4.
After a couple days I'm noticing the bluetooth between the tablet and the watch is "not connected".
I can toggle the watch connection on the tablet gear app, and the gear app will try to reconnect to the watch but fail.
(The gear app on the tablet/phone does an exponential back off which I think is odd cuz it will end up waiting a long time to reconnect if it fails a few times.)
In order to get it to reconnect I have to reboot the watch. Annoying.
Anyone see this? Maybe its an issue with the tablet?
The
-jeff
Click to expand...
Click to collapse
I have weird issues with mine and my Nexus 5. The watch and the app will both think they are connected but then sometimes I go to do something and it doesn't work. When this happens, timeouts inevitably occur and either the watch or the app realize somethings not connected right and will sit there and try to reconnect to no avail. The only thing that gets the connection back again is to flip the bluetooth on my phone off and back on again. This happens several times a day for me.
I suspect bluetooth problems on my Nexus 5 though because I had the same problem with my Pebble before I got the Gear Live at I/O.
v0rtex said:
I suspect bluetooth problems on my Nexus 5 though because I had the same problem with my Pebble before I got the Gear Live at I/O.
Click to expand...
Click to collapse
Another data point... its been working fine for quite a while... then late this afternoon, no connect.
Rebooted the tablet.. rebooted the watch.. still no connect... then on one of the watch restarts, it did "recovery mode"... i re-paired the watch and it all worked after that. Hmmm...
having same problem as yours
I've "upgraded" the io2011 tab to a nexus 7 32gb WiFi.
Again worked for a while but iirc was intermittent to connect at first.
I read a rumor on g+ that the BT issue might be related to wear watchfaces that aren't doing the right thing..
So I uninstalled all the faces, reset everything, .. even reinstalled android wear...
Now I'm not getting any pairing.
i all
I have a LG G watch R, i have had this around 10 months, its paired with my Nexus 5.
Over the past year there has been a few occasions where suddenly the "mute phone alerts and calls" option has suddenly stopped working! *Half way through the day all of a sudden id still get the message on my watch but my phone would make a noise too!
Usually i fixed this by uni stalling android wear, resetting the watch back to factory setting and re pairing them..this usually solved the issue until next time....however!
This time it happened again and no matter what i do it wont work! i have the option to mute phone call and alerts but the phone still makes a noise and is not muted! when i toggle the volume bar it used to say before "muted by android wear" but now it does not.
My phone was updated to android 6.0 last week but for the past week its been fine so i doubt it related to that as like i said its done this before on lollipop.
Few more things to note that may be related, if i swipe down in my notifications box it used to say "android wear connected" but thats no longer there, and if i go into the watch and go into settings and bluetooth devices it does not say anything it just says scanning for nearby devices, and i notced once it said nexus 5 disconcerted??
I must stress that i am connected to my phone as all my notifications come through on my watch fine.
Anyone had this or know a fix?
Thanks
Chris*
Did you find a solution?
Same problem here. I have moto x play (no developer edition) unlocked bootloader/rooted/lollipop 5.1 and LG G watch R.
In my case it seems related to Moto Display (Motorola'app similar to ambient display). If I disable it, mute comes back.
I tried to uninstall android wear app, and then installing 1.3 version. No fix.
On reddit I read that it should be the last update of Google play service instead: user restored his phone fixing the problem. I tried to uninstall play service (no factory reset)...no fix
EDIT: Ok I have just found a middle-solution. I downloaded a module for Xposed (True silent Mode), after activation you will not able to receive any vibrations or sounds on your phone, but you'll receive a vibration on your watch instead. It's similar to android wear function, the difference is if you disconnect your watch you have to disable the silent mode on your phone manually. Hoping Google (or Motorola in my case) fixes it soon in the meantime...
Looks like we are not alone: https://productforums.google.com/forum/#!topicsearchin/android-wear/mute
https://productforums.google.com/fo...context-place=topicsearchin/android-wear/mute
I see other reports and see the issue myself where android wear often says that the watch isn't connected anymore while the watch says it is. And voice commands etc. on the watch still works (I guess they go directly through GMS not involving the android wear app itself).
Maybe there is a bug between android wear and the detection of the connected watch that keeps thinking android wear that no watch is connected and then not muting the notifications on the phone.
Do you have the cloud sync enabled? It's in "privacy & personal data". I have.
Hi still have the same issue, and yes my watch thinks it's not connected also
I have tried both cloud synced and un synced
Try putting your watch on charge, then taking it off
It worked for me, you will notice when on charge the ph is connected but notifications are not muted
I think the ph must think the watch is charging...
The latest wear app version fixed it for me.
http://www.apkmirror.com/apk/google...-wear-1-4-0-2470307-gms-android-apk-download/
Hasn't for me
So I seem to be having issues with bluetooth. Most of the BT devices work, but my TomTom Raider 400 does not seem to want to work.
I was able to pair it to the device, but thats all I get, the TomTom says it won't connect or anything, It was working great nougat now it does not work anymore. I cleared out all network settings, still no go.
Anyone having issues with devices that perhaps require data? anyone have any ideas?
eatonjb said:
So I seem to be having issues with bluetooth. Most of the BT devices work, but my TomTom Raider 400 does not seem to want to work.
I was able to pair it to the device, but thats all I get, the TomTom says it won't connect or anything, It was working great nougat now it does not work anymore. I cleared out all network settings, still no go.
Anyone having issues with devices that perhaps require data? anyone have any ideas?
Click to expand...
Click to collapse
I'm having similar BT problems since the update. Sometimes my car doesn't connect. Quite often my Gear S3 disconnects when the phone is still well within range. My Sat Nav will only connect via BT if I search for it. There is definitely a glitch but I haven't found a fix
Sent from my SM-G950F using Tapatalk
Same issues here, with Tomtom GO 510 and with asus Chromebook too (via Bluetooth only)
I've updated to CRC7 today using the SD card update method described here.
https://forum.xda-developers.com/showthread.php?t=3746561
The BT is much more stable this afternoon and a persistent problem that I had with my home Wi-Fi seems to be gone too. Early days, but it does seem better [emoji106]
Sent from my SM-G950F using Tapatalk
I updated to Oreo 8.0 on my S8 today and have had bluetooth connectivity issues ever since. Listening to music in the car, it will randomly drop connection. Also, some track information is no longer showing on the headunit (the playback time and the overall song length). Everything worked perfect before update. Seems to have been a known problem that may have been addressed with the 8.1 update on Pixel and Nexus phones. Unfortunately my carrier (ATT) just rolled out the 8.0 update today for my S8. I'm at a loss for what to do.
It's failing left and right.
I turn it on and it turns off apprx 1 min later.
I turn it back on and it does the same thing (each time).
removing and re-setting up everything fails.
rebooting fails (same as turning on and off)
safe mode does not help.
So far, Oreo has made Bluetooth useless on my S8
thecolor said:
It's failing left and right.
I turn it on and it turns off apprx 1 min later.
I turn it back on and it does the same thing (each time).
removing and re-setting up everything fails.
rebooting fails (same as turning on and off)
safe mode does not help.
So far, Oreo has made Bluetooth useless on my S8
Click to expand...
Click to collapse
So glad I'm not the only one. It's driving me mad
Sent from my SM-G955F using Tapatalk
STandy469 said:
So glad I'm not the only one. It's driving me mad
Sent from my SM-G955F using Tapatalk
Click to expand...
Click to collapse
After Oreo update my S8's BT became spotty working 20% of the time on calls in the car. So i searched & read that resetting network connections would do the trick. It wasn't under connections->more settings - instead i found it in about phone-at the bottom under Looking for something else-> Reset->Reset Network Settings . Yehey i found it & reset my network settings!
Now my BT won't turn ON! From 20% to 0% function!!!
What a what!
Fix this Samsung!
Sent from my SM-G950F using Tapatalk
Same issue here. My S8+ was rock solid on Nougat, but since the update to Oreo yesterday my Bluetooth does not connect 19 out of 20 tries in my car. I factory reset my phone thinking it may have been an issue with the update process, but that did nothing to fix the issue. I really need a solution as I need to talk while in my car.
Haven't tried using Bluetooth on anything else, but my phone stays consistently connected to my Gear watch.
Anyone have any solutions to this? I'm experiencing the same issues. Won't connect consistently with my gear s2, drops certain speakers all the time, although it seems to stay connected more consistently to my car. Really frustrating and don't want to wait for the glacial pace of Verizon update rollouts.
bstarr3 said:
Anyone have any solutions to this? I'm experiencing the same issues. Won't connect consistently with my gear s2, drops certain speakers all the time, although it seems to stay connected more consistently to my car. Really frustrating and don't want to wait for the glacial pace of Verizon update rollouts.
Click to expand...
Click to collapse
Did you do a fresh install ( download, install, clear cache, wipe phone, rebuild or restore backup) or just install the update and go from there?
Sent from my SM-G950U1 using Tapatalk
A0425A said:
Did you do a fresh install ( download, install, clear cache, wipe phone, rebuild or restore backup) or just install the update and go from there?
Sent from my SM-G950U1 using Tapatalk
Click to expand...
Click to collapse
I just installed the update, but up the thread above several people say that factory reset didn't fix this issue for them.
It won't make a difference. I factory reset my phone after the update to Oreo and reconfigured everything from scratch, no restore, and it made no difference. My Bluetooth still does not work with my car. It works with my Pebble, my Sony Bluetooth headset, and a Marley speaker with no issues. Why is it that only my car fails? It is the most important one.
I am having the same issue when listening to music with Bluetooth in my car. The music gets choppy and does not play back the way it should. I have been looking everywhere online for a fix and I haven't come up with anything. If anyone has any suggestions it would be greatly appreciated.
Same issue with Sony XAV-68BT headunit. Music plays through Bluetooth, then drops rendomly, then manually have to reconnect. Very distracting while driving. Phone calls do not seem to be affected though, so... There's another little tidbit.
Actually I did notice the other day that my Gear Sport was on standalone mode instead of Bluetooth, so I was missing texts from people. Really annoying. Samsung better address this.. going to take ages for Verizon to get the update though, I'm sure.
Any chance that the Bluetooth apk file for the Galaxy S9 would work on our phones? Maybe it would help?
I'm having similar issues here too. I was on Nougat with zero problems. Did an OTA update to Oreo and suddenly my Kenwood car stereo keeps losing bluetooth connectdion. Used ODIN to flash back to Nougat and it's rock solid. Decided to flash Oreo instead of doing it OTA, and suddenly the bluetooth is flakey again. Flashed back to Nougat, and it's rock solid. I've also tried factory resetting and reconfiguring the car stereo, did a factory reset of the Galaxy S8, cleared the cache, and nothing works. The only way of getting Bluetooth to maintain a connection to the car stereo is to be on Nougat.
Interestingly though, I have no problems with my Gear S3 maintaining a bluetooth connection.
It appears it's only some devices that have the issue. I don't hold out much hope that Samsung will fix it though. Weren't people complaining about the same thing during the betas?
I guess this can solve your problems too, I had an issue since the oreo update, cant select anything but SBC reverting to default, even with the level u app not showing UHQ, I started a chat with samsungs members app and they told me that is an error in the update, not all devices are presenting this problem. well, the solution: 1. back up your data with smartswitch app(I backed up with a sd card, 10Gb info) if you have whatsapp do a chat backup because they dont backup with smartswitch. 2. delete your samsung and google account. 3. Do a hard reset(witch the phone powered off press volume+, bixby and power, until you see the recovery menu), wiping cache and then wipe data/factory reset(move trough the menu with volume+- and select with power). 4. start the phone and add your google and samsung account, then restore your data with smarwitch app. this will let you select the BT codec again.
worked for me and the bluetooth conection is more stable
Hey guys, I have a new OP8 Pro and tried to connect it to my Fossil Sport smartwatch. The problem is that I am not even able to connect it. I did a factory reset on my watch and started the linking process in the wearOS app. Everything works fine until I select the my watch to connect. My phone asks me the check the code (it matches to the one on my watch) and after pressing pair, the phone continues with the process but the watch keeps telling me that my phone wants to connect and shows me the bt connect code. After 1/6 of the "getting informations from your watch" the app doesnt do sh*t anymore. I noticed that that the bt connection to my watch is disconnecting and connecting again and again but doesnt stay connected.
My troubleshooting is exactly Pike this redet post: https://amp.reddit.com/r/WearOS/comments/f20lxm/oneplus_7t_and_fossil_sport_not_connecting_help/
Unfortunely there isnt a solution to the problem. So maybe here is someone who had the same issue
I tried connecting my watch to another phone and it works perfectly so it is definitely a problem with my OP8.
Glad about any help. Thanks a lot!
Greetings
Marcel
I use a Fossil Sport, and had this same issue when I originally set mine up. I wish I had a better answer, but I just tried and tried again until it worked. Between each attempt I cleared everything I could think of. Reset the watch, cleared google play services cache, cleared wear os app cache, reinstalled the wear os app, manually removed the watch from bluetooth settings, reset network settings, I'm probably forgetting some things, but it did eventually connect. Frustrating, and I'm sorry I don't remember exactly what fixed it, but the good news is it will eventually work.
I don't have a sport but I have a gen 5 and there was no issue and I have had to reset and reconnect a couple times.
Best of luck!
I have a gen 5 and the devices are connect because i receive the notify but on the top of the smartwatch there is the cloud of the no connection... I think therr are some problem with the bluetooth of this phone
Wingdom said:
I use a Fossil Sport, and had this same issue when I originally set mine up. I wish I had a better answer, but I just tried and tried again until it worked. Between each attempt I cleared everything I could think of. Reset the watch, cleared google play services cache, cleared wear os app cache, reinstalled the wear os app, manually removed the watch from bluetooth settings, reset network settings, I'm probably forgetting some things, but it did eventually connect. Frustrating, and I'm sorry I don't remember exactly what fixed it, but the good news is it will eventually work.
Click to expand...
Click to collapse
Thank you very mich for the reply. I've already done that at least 20 times, but at least there is hope that it will eventually work one time/day. Really frustrating and I hope they will fix this soon so when I have to reset my phone someday I will at least not have this problem again. :silly:
Okay guys it finally worked. Im not sure why, didnt do anything else but reinstalling, deleting chache and data of WearOS and Google play Services and resetting my watch. I can only imagine that it was because the languages of my phone and my watch didnt match. My phone is in english and I set my watch to german. It worked when I set up my watch in english (GB). I really dont know if that really was the solution or if it was just luck this time because i tried english (US) before that and it didnt work. So to anyone who is having the same problem I hope I can help you with this and hang on... I'll work sometime
vuoshino said:
I have a gen 5 and the devices are connect because i receive the notify but on the top of the smartwatch there is the cloud of the no connection... I think therr are some problem with the bluetooth of this phone
Click to expand...
Click to collapse
I have the same problem with my Huawei watch gen 1. I need to reboot my phone every time if I want that cloud-icon disappear on my watch.
Eremitus said:
I have the same problem with my Huawei watch gen 1. I need to reboot my phone every time if I want that cloud-icon disappear on my watch.
Click to expand...
Click to collapse
Did you try changing the WearOS App's battery setting to not optimise and lock it in the background?
PaterProx said:
Did you try changing the WearOS App's battery setting to not optimise and lock it in the background?
Click to expand...
Click to collapse
Yes i tried. Everything works good but there is the same icon on the top...
PaterProx said:
Did you try changing the WearOS App's battery setting to not optimise and lock it in the background?
Click to expand...
Click to collapse
I have changed it already to "not optimized", but haven't locked it in the background tho.. need to try that too. Quite annoying.