Hi, so I've disabled BT on the watch. I'll start the download process and it will show it starting but then it stalls. I've left it overnight but wake up to it in the same state as when I started the download.
I'm on version 2.20 on the watch.
Is there a fix for getting the Wifi to at least work properly so I can finish the downloads onto the watch?
Related
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
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
does anyone know how to block the forced update of Google play services on the watch? (you can tell when it's pushing hard to come in because your Wi-Fi will mysteriously start turning itself on ... not kidding ... but it will slowly sneak in over Bluetooth if no Wi-Fi network)
When my watch invisibly updates Google play services (on the watch) to 9.0.83 from 8.6.98 then 'android wear on the phone' says "Trying to connect" for 3-10 minutes every time instead of the 5-10 seconds it used to take with 8.6.98. it also randomly disconnects a lot more too, and after running a few hours performance gets laggy.
basically, on both my huawei watches this update is 'malware' and I'd like to know how to block this 'worm,' because it degrades all other Google products I love.
any help appreciated.
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.
Hey,
I have a ticwatch pro 3 and one of the reasons i bought it were the long battery life and for alarms so i wouldnt wake my partner with an alarm in the morning.
After setting up the watch and configuring essential mode to start and end automatically when i am asleep i have noticed that when essential mode ends in the morning wear OS does not actually start unless i unlock the watch screen which is not ideal as the alarm will not go off unless i unlock screen first.
Is there some way around this? I basically still want essential mode to start and stop but also have my alarm go off without having to unlock the watch to start wear OS.
Appreciate any help
GrimEire said:
Hey,
I have a ticwatch pro 3 and one of the reasons i bought it were the long battery life and for alarms so i wouldnt wake my partner with an alarm in the morning.
After setting up the watch and configuring essential mode to start and end automatically when i am asleep i have noticed that when essential mode ends in the morning wear OS does not actually start unless i unlock the watch screen which is not ideal as the alarm will not go off unless i unlock screen first.
Is there some way around this? I basically still want essential mode to start and stop but also have my alarm go off without having to unlock the watch to start wear OS.
Appreciate any help
Click to expand...
Click to collapse
I read this on another forum, so please consider bringing watch up from essential mode after your alarm wakes you:
"I've tested this and already work on TicWatch Pro 3
Seriously, I've recorded it
All set alarms ring normally on ESSENTIAL MODE, waking me up as usual"
toncheee said:
I read this on another forum, so please consider bringing watch up from essential mode after your alarm wakes you:
"I've tested this and already work on TicWatch Pro 3
Seriously, I've recorded it
All set alarms ring normally on ESSENTIAL MODE, waking me up as usual"
Click to expand...
Click to collapse
Ok weird looks like i have some testing to do why it doesnt work for me.
thanks for the help and video.
I have the same issue...
i tested and no luck. I tried the exact same thing @toncheee video does and the alarm does not go off when in essential mode and instead goes off about a minute after i take the watch out of essential mode.
@toncheee @quack3d may i ask what version your watch is on mine is on
Code:
wear: OS 2.31
Home app: 2.51.0.398500942
Google Play store services: 21.36.14
system version: H MR2
Android Security Patch Level: March 5, 2021
@toncheee if you set an alarm and you go into essentials mode and then out of essential mode what happens if you have screen lock enabled. As that my main issue. watch comes out of essentials mode about 30 mins before alarm goes off but i need to unlock watch for wearOS to start and alarm to go off.
here is a video of me. sorry about the moving of the camera.
ticwatch-alarm
Watch "ticwatch-alarm" on Streamable.
streamable.com
Same versions as you except for: Google Play services: 21.36.55. Thread on the issue here too: https://forum.mobvoi.com/viewtopic.php?f=76&t=57963
quack3d said:
Same versions as you except for: Google Play services: 21.36.55. Thread on the issue here too: https://forum.mobvoi.com/viewtopic.php?f=76&t=57963
Click to expand...
Click to collapse
thanks it looks like its not just us with the issue, hopefully they will fix it soon as this is essential for me and other.