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
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?
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
Hello there! So, I have been using my Moto 360 gen 1 with my Lg G4 (CM14 12-05-16 nightly) for a while now, and it just recently started doing this. Everything says my watch is connected to my phone, I can even send texts from my watch and turn on do not disturb from my watch (but I can't turn it off from my phone), but no notifications are pushing through to my watch. The only thing that fixes it is a factory reset on the watch, but that only allows notifications for a few days, then it just goes back to broken again. Any ideas? I love my watch, but it doesn't do me any good over a regular watch if I can't get notifications on it. Thanks!
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.
Hi Folks,
I try to keep my remarks / questions as brief/straight as possible.
Some days ago a huge German electronic-chain called Media Markt offered the Axon 7 for only 229€, for only a couple of hours. I could not resist although I was very satisfied with my Alcatel Idol 3 (4.7) with Android MM.
Now I installed the exact same Apps that I have been using on my Alcatel on the Axon 7 (Android 7.1.1, B04). I do not have the problems that some are mentioning on various fora like connectivity issues (Wi-Fi, Bluetooth, cell). My settings are Wi-Fi (always on), Cell on (but not data on so far, not in the need to do it), GPS sometimes on, Bluetooth sometimes on, Display very low, no automatic.
I have some weird notification issues with various apps installed by myself and strange behaviour with system apps.
Wherever it was possible, I've chosen the same settings (Energy, Apps) as with my Alcatel on Android 6.0.1.
But, I rarely get notifications (for example AquaMail, WhatsApp, eBay, etc.) or, I hear the notification sound (when my phone was on stand-by) but the symbols are not shown in the status bar, notifications bar?!?!?
Another strange behaviour is that of my podcast app, called Podcast Addict:
I listen to a downloaded audio podcast, pause the playback, for example to get a coffee in the meantime, go back to my phone, unlock the screensaver and the pause symbol that was shown in the notification, status bar on the device before I left the phone, is not there any more!?!?! I have to open the app again to continue listening to the audio file. The exact same applies for the stock music player.
Or, for example I receive a notification for an incoming WhatsApp message, shown on the notification bar, I do not open WhatsApp, the notification symbol should/is still visible, but after the screensaver has been activated (set it to 1 minute) and I have to reactivate the phone (be it by fingerprint or by pattern), the symbol is no longer there.
Another strange thing. The phone was in stand-by, I heard a notification sound, activated the phone, there was no notification symbol on the bar. I knew what App it was, so I opened it and yes, there has been something going on (the App is called Quizduell).
All these bugs (?), problems have never occurred running the Alcatel smartphone.
This is pretty annoying.
I already switched off the phone, wiped data cache, without success.
Maybe some of you can help me out, give me advice on where to look for the problems to be solved.
Thanks a lot in advance.
Cheers Christian
Change the power policy of each app to off which u use mostly in power manager in settings.... It will most certainly help you out..
@germanyandroid Do what the other guy said, that's really impoetant. Also what system are you on? A2017G B02?
I don't know what the Axons are shipping with right now. Be sure to update at least manually to 1.2.0 B02 (that's Nougat), to rule out any system problems. Welcome to ZTE's horrible OTA system...
Hi! Thanks so far for your help. Most notifications are now coming in without changes to the Battery Optimization settings. There is something wrong with these settings, which I will report in a separate thread.
Again, thanks for your help thus far.