Hello XDA,
i got an Issue with my Nexus 5 and Moto 360.
Both do run the latest Lollipop Versions.
In the past i had a constant notification which is also often discussed here and in other forums. "Android Wear Connected. Running sync loop..."
But my current problem is that my android wear watch is connected and also does talk to the smartphone, e.g. shows notifications.
But if i install or deinstall a watchface for example this does not get synchronized with my watch.
If i do want it to i need to manually go to the android wear app and within the setttings hit the button "Apps erneut synchronisieren" which translates to possibly "Resync apps".
I tried to understand why this happens and since when, in this moment i realized that i no longer have the notification "Android Wear Connected. Running sync loop...".
Has anybody the same issue, or if not has anyone ideas what could be the problem.
Restarting of device, watch, toggling of bluetooth etc. have not helped.
Greetings Marco
Related
Hi folks, Have my watch about 36 hours now. Out of the gate the timer function simply does not work. I say "Set a Timer for 5 minutes" it just brings up the alarm dialogue, where I can select an alarm time. The timer itself DOES work when I double tap, swipe up and then manually select timer.
Every other function, voice or not, seems to work fine.
But the fact that the timer doesn't work is baffling and a big hinderance to me, not to be able to use it by voice. I relied heavily on the multi timer app on my Pebble.
Don't know yet if it is an LG issue, an Android Wear issue or the fact that my phone is a Samsung Note 3, running 4.3.
I've rebooted it a couple of times, but timer simply doesn't work by voice on my unit.
Any advice appreciated?!
weareborg said:
Hi folks, Have my watch about 36 hours now. Out of the gate the timer function simply does not work. I say "Set a Timer for 5 minutes" it just brings up the alarm dialogue, where I can select an alarm time. The timer itself DOES work when I double tap, swipe up and then manually select timer.
Every other function, voice or not, seems to work fine.
But the fact that the timer doesn't work is baffling and a big hinderance to me, not to be able to use it by voice. I relied heavily on the multi timer app on my Pebble.
Don't know yet if it is an LG issue, an Android Wear issue or the fact that my phone is a Samsung Note 3, running 4.3.
I've rebooted it a couple of times, but timer simply doesn't work by voice on my unit.
Any advice appreciated?!
Click to expand...
Click to collapse
I have a Moto X with 4.4.3 and it works fine. Wish I could be of more help but it does work fine on mine. You're not running a custom ROM by chance?
weareborg said:
Hi folks, Have my watch about 36 hours now. Out of the gate the timer function simply does not work. I say "Set a Timer for 5 minutes" it just brings up the alarm dialogue, where I can select an alarm time.
....
Don't know yet if it is an LG issue, an Android Wear issue or the fact that my phone is a Samsung Note 3, running 4.3.
I've rebooted it a couple of times, but timer simply doesn't work by voice on my unit.
Any advice appreciated?!
Click to expand...
Click to collapse
I'm having the same problem. I have the Samsung Gear Live paired with a Galaxy Nexus. I believe it is actually a problem with the phone. I paired the watch with my 2012 Nexus 7 and the "set a timer" function works fine. Also, I can't set a timer on the phone itself using Google Now voice commands -- it tries to set an alarm there, also.
Same issue for me... Samsung Gear Live and a Nexus 5. It worked fine some hours ago, now everything like "set a timer to ..." or "set stopwatch to ..." brings up the alarm dialog. Restarting the phone and watch didn't help, neither did syncing the wear apps.
Really annoying since this is one of the features I actually use often.
I asked a friend to check if it works if he tries it with Google Now on his phone, since it DOES work on his Gear Live. Funnily, this broke the functionality on his watch too, so better don't tell your friends, seems to be a Virus distributed by chat
(this is for the german version "Setze einen Timer auf X Minuten", like it is suggested in the watch itself)
Edit:
http://www.androidcentral.com/ok-google-set-timer-now-actually-sets-timer
It seems like this is actually controlled server-side at Google - maybe its just an issue with some of their server nodes?
Wubdidu said:
Same issue for me... Samsung Gear Live and a Nexus 5. It worked fine some hours ago, now everything like "set a timer to ..." or "set stopwatch to ..." brings up the alarm dialog. Restarting the phone and watch didn't help, neither did syncing the wear apps.
Really annoying since this is one of the features I actually use often.
I asked a friend to check if it works if he tries it with Google Now on his phone, since it DOES work on his Gear Live. Funnily, this broke the functionality on his watch too, so better don't tell your friends, seems to be a Virus distributed by chat
(this is for the german version "Setze einen Timer auf X Minuten", like it is suggested in the watch itself)
Edit:
http://www.androidcentral.com/ok-google-set-timer-now-actually-sets-timer
It seems like this is actually controlled server-side at Google - maybe its just an issue with some of their server nodes?
Click to expand...
Click to collapse
As seen by that androidcentral article they FINALLY fixed that idiocy not too long back, but it's a bit hit-and-miss. For one thing, Android-L dev preview bugwatch has a bug (with a reasonable amount of stars iirc) that says that in L-dev-preview this behaviour is reversed, leading me to believe it at least is SOMEWHAT controlled by the phone/OS version etc?
Not sure though...all you guys who are facing this issue on the WATCH, do you also consistently face same issue on the PHONE that it's tethered to? (I'm guessing this is a yes), are any of you using android-L dev-preview?
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
I have a Wear24 running on Android wear 2.20 and AndroidOS 7.1.1. my phone is Nokia 6.1, runnung on android one Pie 9. everything is updated.
Bluetooth connection is fine, google assistant is also working, big tick was showed after the message was sent but no recordof this message found on my phone's whatsapp. occasionally it crashes whatapp.
Seems GA fails to wake up whatsapp and execute the instruction.
please help, thank you very much
solved! I have to dig deeper into setting and disable battery optimisation for whatsapp
Hello,
recently I decided to update my Mi A1 to Android 9.0. Unfortunately it turns out that I have a big problem with notifications. Sometimes they come "normally", at the time they should. However, it often happens that notifications appear with a delay of 10-30 minutes. Sometimes they don't even come at all until I turn on the screen. In this case of course I am talking about the lack of notifications when the phone is unused. However, I once had a case when notifications from Facebook Messenger did not come for more than 3 hours, despite the use of the phone - car navigation, browsing the Internet, notes, etc. Messenger didn't show notifications of new messages until I opened it. I've tried to turn off the adaptive battery mode, but it did not help. Does anyone know how to solve this problem? Everything worked well on Android 8.0, but I do not feel like going back to it again.
szerwony said:
Hello,
recently I decided to update my Mi A1 to Android 9.0. Unfortunately it turns out that I have a big problem with notifications. Sometimes they come "normally", at the time they should. However, it often happens that notifications appear with a delay of 10-30 minutes. Sometimes they don't even come at all until I turn on the screen. In this case of course I am talking about the lack of notifications when the phone is unused. However, I once had a case when notifications from Facebook Messenger did not come for more than 3 hours, despite the use of the phone - car navigation, browsing the Internet, notes, etc. Messenger didn't show notifications of new messages until I opened it. I've tried to turn off the adaptive battery mode, but it did not help. Does anyone know how to solve this problem? Everything worked well on Android 8.0, but I do not feel like going back to it again.
Click to expand...
Click to collapse
Try This
- Open settings
- Type battery optimization in search bar and enter and wait loading
- Click on Not optimized on the top and select All apps
- Scroll to messenger an Click on it and select Don't optimize
you can do this with any app
hope this help u
I will try this, hope it helps. However on Android 8.0 I had optimization turned on and notifications were working fine.
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!