Database Users

Phone won't mute anymore!

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

Bluetooth issues & restarts - time for LineageOS?

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.

Android Auto - issues and workarounds

Installed Blackball's fRomFuture ROM, working well and it's fast but the AA bugs are still there.
Bugs are:
- Phone calls go to the handset instead of showing on the HU. This prevents the HU from being able to control calls and I have to answer and end them with the phone itself. The workaround is to either stop the Dialer process before plugging into the HU, or install Google Phone 7.0.140861421-nonnexus (noarch) (nodpi) (Android 6.0+) and set it as default dialer. Only bug then is the clock/timer on calls shows system time or something like 422031:23:59. No big deal there.
- Waze works one time, but as soon as the phone is rebooted it will halt the maps process on the HU. App still works fine when unplugged. Once this happens you have to either; clear cache and data from AA, enable developer mode in AA and start Maps from the "Back to Sync" icon (developer mode adds options here - Ford Sync), or uninstall Waze. I have not found another reliable workaround and it seems like this is a very common Huawei issue, not just P10 Plus.
Wondering if anyone else has found workarounds for these?

Bluetooth issues after Oreo Update

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

Wear OS watch will not maintain bluetooth connection to Mi9T

My Casio Pro Trek WSD-F20 always loses Bluetooth connection to my Mi9T after something like 30-90 minutes. The phone still thinks it is connected to the watch (eg, still successfully sends notifications) but the watch says it is not connected to the phone (eg, "disconnected symbol" is displayed, Play store on watch will not open as "you are not connected"). Restarting watch does not restore the connection. Turning watch or phone Bluetooth off and on does not restore the connection.
However, restarting the phone does reliably restore the connection.
Watch and phone (MIUI Global 10.3.12 Stable) are both current on all software. I have done a factory reset on the watch, and repaired after forgetting watch on phone, removing Wear OS app and reinstalling. Problem remains. I am confident, but not completely certain, that I have turned off battery optimisation for everything that matters, even installing MIUI Hidden Settings which appeared to let me do this for Bluetooth. My phone is not rooted, and I need it that way for a couple of apps I use regularly.
What can I do to keep watch and phone fully connected? Thanks in advance.

Had a similar issue with my Gear Fit2 Pro. MIUI kills the process maintaining the connection between the watch and the phone.
I ended up disabling the MIUI optimizations in the Developer settings and change the autostart settings for the "Samsung Galaxy Gear Fit Plugin" (that's the app maintaining the connection between my watch and the phone) to enable and enabled the option to let the app run in the background without any restrictions.
Here is a good information about this stupid MIUI background process killing and how to prevent it: https://www.quora.com/How-do-I-keep-an-app-running-in-the-background-in-MIUI
Good luck

I had that problem when I was running Global ROM. When I switched to Xiaomi.eu, the problem seemed to have gone away.

grantem2000 said:
My Casio Pro Trek WSD-F20 always loses Bluetooth connection to my Mi9T after something like 30-90 minutes. The phone still thinks it is connected to the watch (eg, still successfully sends notifications) but the watch says it is not connected to the phone (eg, "disconnected symbol" is displayed, Play store on watch will not open as "you are not connected"). Restarting watch does not restore the connection. Turning watch or phone Bluetooth off and on does not restore the connection.
However, restarting the phone does reliably restore the connection.
Watch and phone (MIUI Global 10.3.12 Stable) are both current on all software. I have done a factory reset on the watch, and repaired after forgetting watch on phone, removing Wear OS app and reinstalling. Problem remains. I am confident, but not completely certain, that I have turned off battery optimisation for everything that matters, even installing MIUI Hidden Settings which appeared to let me do this for Bluetooth. My phone is not rooted, and I need it that way for a couple of apps I use regularly.
What can I do to keep watch and phone fully connected? Thanks in advance.
Click to expand...
Click to collapse
+1 to this, facing the same exact issue and fixing it temporarily using the exact method i.e. restarting the phone.
PS: I am using Huawei Watch (Classic/Original)

Same here with my Fenix 3HR.
I actually returned the phone due to this. Too many issues with too many apps being killed. And yes I did all the things that should/needed to be done to prevent apps from being killed. Too much work involved per app just to get things to maybe work properly.

Same issue for me using the eu rom. Clearing all data works without restarting the phone. Starting to get annoying.

I have the same problem as OP.
I had it with my Ticwatch E when paired with Redmi Note 4, while my girlfriend's Ticwatch E connected with ASUS Zenfone works great.
Now with Fossil Gen 5 paired with Redmi Note 7 I keep having the same problem.
Does anyone know if the problem happens with Xaiomi Wear OS watches or Amazfit watches?

I fixed it by accepting all permissions on the wearos phone app.

borofanuk said:
I fixed it by accepting all permissions on the wearos phone app.
Click to expand...
Click to collapse
What else have you done? I also have a Xiaomi Mi 9T Pro with stock 10.3.4.0 and I have the same issues. It is becoming increasingly annoying... I am desperate. Wear OS is battery deoptimized in both menus, set to autostart and still the Bluetooth disconnects after a few hours. It is pretty clear that the issue is after Wear OS, as Wear OS app is running , but the phone somehow cuts Wear OS from the internet.
PS: Also have tried custom ROMS... Evolution X does not have the issue, but has other issues (like the fact that Android Auto does not work).

It's fixed! I hoped the move to Android 10 would solve the bluetooth connectivity issues with my Casio Pro Trek watch but did not expect that it would. But it did!
I now have a Pro Trek WSD-F30 in place of the F20 I had when I first made this post. Prior to the Android 10 upgrade, the F30 connectivity to the 9T was just the same as the F20. Bluetooth connection helped for 30 mins or so after restarting the phone then 'dropped' (the phone continued to send notifications etc to the watch, but the watch displayed the 'cloud with a line through it' symbol to indicate it was not connected and would not connect back to the phone.)
The Android upgrade alone did not fix the problem; I also had to 'factory reset' the Mi 9T which is now at 'MIUI Global 11.0.4 Stable 11.0.4.0 (QFJEUXM)` based on Android 10 with the 2020-01-01 Android security patch level. My phone is standard and unrooted though after the factory reset I removed many of the pre-installed apps with Xiaomi ADB Fastboot Tools. The Wear OS app on the phone is set to have 'no restrictions' in Battery Saver and Autostart On. Otherwise everything is just 'as installed' and it all works well.
My F30 has remained fully connected to my phone for 3 days. WiFi on the F30 is set to Automatic and I get 2 days plus battery life (I only got this previously if I had Wifi Off). The watch is now behaving as I hoped it would when I first got it. What a delight.

grantem2000 said:
It's fixed! I hoped the move to Android 10 would solve the bluetooth connectivity issues with my Casio Pro Trek watch but did not expect that it would. But it did!
I now have a Pro Trek WSD-F30 in place of the F20 I had when I first made this post. Prior to the Android 10 upgrade, the F30 connectivity to the 9T was just the same as the F20. Bluetooth connection helped for 30 mins or so after restarting the phone then 'dropped' (the phone continued to send notifications etc to the watch, but the watch displayed the 'cloud with a line through it' symbol to indicate it was not connected and would not connect back to the phone.)
The Android upgrade alone did not fix the problem; I also had to 'factory reset' the Mi 9T which is now at 'MIUI Global 11.0.4 Stable 11.0.4.0 (QFJEUXM)` based on Android 10 with the 2020-01-01 Android security patch level. My phone is standard and unrooted though after the factory reset I removed many of the pre-installed apps with Xiaomi ADB Fastboot Tools. The Wear OS app on the phone is set to have 'no restrictions' in Battery Saver and Autostart On. Otherwise everything is just 'as installed' and it all works well.
My F30 has remained fully connected to my phone for 3 days. WiFi on the F30 is set to Automatic and I get 2 days plus battery life (I only got this previously if I had Wifi Off). The watch is now behaving as I hoped it would when I first got it. What a delight.
Click to expand...
Click to collapse
I can confirm MIUI 11 fixes the issue (I am on EEA version of 11.0.6.0). Normally I never upgrade unless I have very good reasons so for the last couple of months I was using a partial workaround using Tasker to reopen WearOS and reset the bluetooth connection. But I am happy to report this does indeed fix the issue.... so for all of you reading this thread and having a Xiaomi phone -> upgrade to MIUI 11.
Many thanks grantem2000!