Related
Using a Nesux 5 on 5.0 when I enable 'mute connected phone' in Android Wear it does not work.
If I press Vol + or - 'Muted by Android Wear' is displayed in the Interruptions menu (if that's what its called?) but the phone still beeps for notifications and rings for call.
I have tried reinstalling Wear as well as clearing the cache.
Has anyone else had this issue? Is there a work around?
finalbillybong said:
Using a Nesux 5 on 5.0 when I enable 'mute connected phone' in Android Wear it does not work.
If I press Vol + or - 'Muted by Android Wear' is displayed in the Interruptions menu (if that's what its called?) but the phone still beeps for notifications and rings for call.
I have tried reinstalling Wear as well as clearing the cache.
Has anyone else had this issue? Is there a work around?
Click to expand...
Click to collapse
I have same problem. It's bug?
finalbillybong said:
Using a Nesux 5 on 5.0 when I enable 'mute connected phone' in Android Wear it does not work.
If I press Vol + or - 'Muted by Android Wear' is displayed in the Interruptions menu (if that's what its called?) but the phone still beeps for notifications and rings for call.
I have tried reinstalling Wear as well as clearing the cache.
Has anyone else had this issue? Is there a work around?
Click to expand...
Click to collapse
Yes. I am facing this problem too! Seems like a compatibility bug with Android Lollipop. Might be due to the implementation of the 'Notification Priorities'.
Hope some updates come up soon to fix them!!
I'm running 5.0.1 on my HTC One M7 GE. The mute works with 5.0.1. It's a "priority" mode setting. Where the phone does not ring, but certain notifications may make a sound if they are priority and could be lowered.
Glad it's not just me then. Hopefully it'll be address in 5.1/5.0.1
Fixed in the latest Android Wear app. Version 1.0.5
Also seems to be OK on Lollipop 5.0.1 on the watch! Yay
Hum ... I still have the problem. Mute seems alright for notifications but not for phone ring.
I have Nexus 5 on 5.0 (LRX21O), Gear Live on 5.0.1 (LWX48P) and Wear App 1.0.5..1630507.
Also, I'm using Wear Aware app for being notified on watch if phone is missing, but starting with Lollipop, I have 5 ou 6 false alert each day.
I was working perfectly with KitKat.
May be it is the Wear aware app. I'll try another one.
Maybe 5.0.1 on phone will fix this when it will be available.
For now, our nexus 5 only have 5.0 (https://developers.google.com/android/nexus/images)
Anybody found a solution for this?
I have a possible work around but need help with tasker.
I set up a profile for when connected by bluetooth so that the ringer is off and vibrate is off but because off lollipop it does not work. Think it's the do not disturb option.
In my phones setting-lg g3- i can create a vibrating pattern that is a split second long and really weak.
What i need help with is how to recreate this in tasker. I.e is there a way of changing vibration strength in tasker and pattern.
If so we will be able to create this work around until a offical option is available.
Merry Christmas
Phil
Update;
Couldn't find a way of doing it through tasker despite asking on the relevant forums and hours messing around. Think tasker needs a few tweaks to allow these options to work on lollipop.
Although i found a app that works. I can set a rule to put my phone on silent but the watch still vibrates and visa versa when not connected.
https://play.google.com/store/apps/details?id=com.fancy01.myprofiles
Hope this helps, I'm going to do a few more rules for Wi-Fi, location etc using this app.
Cheers
Phil
I got the watch for Christmas and I have the same issue. My Gmail is muted, but the phone rings and all the other notifications sound off. I have a Nexus 5 running Lollipop 5.01 with the newest version of Wear and 5.01 on the watch. I'll be monitoring this thread for updates...
Firefyter said:
I got the watch for Christmas and I have the same issue. My Gmail is muted, but the phone rings and all the other notifications sound off. I have a Nexus 5 running Lollipop 5.01 with the newest version of Wear and 5.01 on the watch. I'll be monitoring this thread for updates...
Click to expand...
Click to collapse
The link in my post above yours is to a profile managing app that does what is required. I'm not sure if the free version works as i can't remember but paid one does.
I created a profile that mutes ringtone, no vibrate with a rule that activates the profile when connected to bluetooth device.
It switches notifications on the watch to priority so don't change that as it will make the phone start ringing/vibrate.
Work around that works
I have the same issue. Here what I do.
Android watch is connected and set to mute apps
Tap the volume rocker (for me nexus 6) and you'll see it says muted. For my work day I leave it on all.
Tap the bell icon and the phone will be put on vibrate. It's working great for the moment.
Best work around I have found.
The issues has returned for me on the latest version of the Wear app....
Let me preface this by saying that after changing this setting and 20 hours later with multiple separations of phone and watch, I have yet to miss a notification and battery life is much much better. My specific problems were: Watch would randomly stop receiving notifications. I would realize this after a few hours go by without any notifications and pull my phone out and see what I've missed. This would happen despite the Wear app showing 'connected' status. Another issue I had was giving a voice command and after a few seconds the watch would return a 'disconnected'message, again the Wear app showed connected. All of this under known working network connections, whether Wi-Fi or cellular. I was also experiencing what I feel is short battery life at about 14 hours per day. I've had and used the watch for two weeks now and have restarted it many many times.
The following is the ONLY thing I have changed since the major improvement in performance. I don't have the depth of knowledge to prove or describe why this worked for me, and maybe it wasn't the cause, but I (knock wood) have a perfectly operating watch now with the battery life indicating about 2 days remaining at noon today.
Go to Settings> Bluetooth> and select the settings icon on your connected device. Then select 'connection access' and choose 'automatic'. Mine defaulted to 'always ask'.. I'm guessing this caused a hangup with the connection between Wear app and watch leading to my problems.
Edit: I'll add that my phone is an LG G2 on 4.4.2 , rooted and running xdabbeb's Rom.
Edit 2: I reset my watch, synced the watch via the Wear app on phone and NOT the Bluetooth screen and now I'm running strong after two days. Made sure automatic was checked as well.
Bugger
I don't have that option in my bluetooth settings
I don't have any problems with mine so far but just checked my settings and it was on always ask.
Could anyone confirm what it should be set as? I have changed mine to automatic anyways.
Thanks for the heads up.
Phil
Not seeing that option in Android 5.0.1 on my HTC One GE. But I have not been having any of the issues mentioned in the OP.
Sent from my Nexus 10 using Tapatalk
Here is a pic of the screen where you make selection. Always Ask is NOT what you want, which is what is pictured. Select Automatic. Sounds like this isn't available on Android 5.0 from what I see in responses so far.
I don't think I saw this option on any of the ROMs I ran, but there may be devices out there that have it and default to it, and this one would really break wear connectivity - so it may help someone someday.
I'm on 5.0, lg g3 and have both options.
Although i havnt had a problem with always ask and only switched it to automatic tonight.
Judging from the description, it will work as long as the watch stays connected, but a reconnect from the watch side would ask for confirmation (and could be possibly even silently denied under some circumstances).
Phone -> Watch = no problem
Watch -> Phone = problem
and it's possible (and likely) there are more connections going on than just the primary one, and if the connection is flaky there might be a dead one and a new one from either side...
you could just have been lucky, so far
My issues returned last night. I left my watch at home and went to dinner and out with friends, came back home after several hours. I left the watch in theater mode while I was out and over night. I woke up this morning, put watch on and realized the battery had tanked overnight and I was no longer receiving notifications, again, wear app showing connected. I looked at the battery graph for the watch and it is totally flat while I was out last night and appears to tank fast as soon as I got home and my phone was in proximity to the watch again. It's like it is constantly trying to handshake with the phone or something. The only thing that fixes this problem is a reboot of the Watch itself. I still think the connection setting was helpful because I have yet to see battery life like that or a solid link for that long. I would love to know what exactly is going on here. Bad hardware?
For the sake of comparison, I have android wear in my pull down bar saying 'connected, running sync loop' 100% of the time. It never goes away. Is this what everyone else sees?
That's what I have also since I own the watch.
Stbrightman said:
For the sake of comparison, I have android wear in my pull down bar saying 'connected, running sync loop' 100% of the time. It never goes away. Is this what everyone else sees?
Click to expand...
Click to collapse
That would be because you have Android Debugging turned on in the phone settings.. Means nothing..
mic18u said:
That would be because you have Android Debugging turned on in the phone settings.. Means nothing..
Click to expand...
Click to collapse
Nope, shows also when out of the box so without android debugging.
Just a normal operation notification
I just discovered another possible contributor to connectivity issues: I just tried to use my watch to voice dial and after multiple attempts I got the disconnected message. I took my phone out and Wear app says connected and I had full 4G signal. My phone is set with a pattern lock. After unlocking it and checking the above mentioned, I tried the watch again and it worked. Could locking your phone have something to do with these problems?
I bought the Watch R a week or so ago and I've been trying to work out why the Google Now notifications are so unreliable.
At first, I thought it was just me - I never really embraced Google Now and actually had it turned off on my phone (Galaxy S6 Edge). A few days ago I turned it on, configured it and was expecting to see the odd card popup on my watch every now and then but I've had zip.
So, I thought I'd test the notifications on the watch, from the Android Wear app, but the only notification that works all the time is the phone call. Most of the other notifications just don't pop up on screen and the only way I see them is to swipe the face from above and then they're there. Is this normal behaviour? I thought that notifications were supposed to popup on the screen, like on my phone!
I've reset the phone a couple of times in desparation but it's made no difference. I've unpaired the watch from the phone and re-paired it after forgetting the device. No difference. Removed all the custom watch faces and used only the once that came with the watch and once again, no difference.
I do get notified of text messages and emails with no problem, but nothing from Google Now.
Can anyone please suggest anything?
I have the s6 and I don't receive any notifications except the test phone call. I believe it to be a samsung problem with it killing the wear app from running in the background. watch worked fine with my other phones.
It's ridiculous, my s6 / gwr doing the same thing. Reboot both and things work for a little while, then gradually peters away to nothing. Except for sometimes I'll tap the watch for the time, and some random google now cards will be there, which I dismissed days before! Swipe them away but the same few keep coming back! As for the weather reports, well they've not worked for over a month now. And all this without me touching any settings whatsoever. I've exempted the android wear app from battery optimisation in the s6 too, incase they were that dense they'd overlooked that core app, but doesn't seem to have sorted it. Seems every time these companies update stuff they break it, and don't care about fixing it.!
Hi all
Had my watch nearly a year and every now and then the mute phone alerts and call feature stops working. I usually have to factory reset watch and delete android wear app on phone to fix the problem. However this time even thats not working?
I am running nexus 5 on marshmallow and had marshmallow a week and today its only just decided half way through day to stop working and all of a sudden my phone is sounding alerts.
anyone know a way to fix this?
Just manually flashed the Android Wear 2.0 on my LG watch urbane at first it was slow and laggy and but then a day or two later it straightened itself out and it was like butter.
And the purpose of this topic is?
Mine is still really laggy after about 4 days.
Mind is unusabley lethargic.
Same here. A great smartwatch has become effectively useless since 2.0. Can't even answer calls on it anymore for cryin' out loud!
My watch was incredibly laggy and had terrible battery drain too. Today I did nothing different besides turning WiFi off and the lag is gone and the battery is similar to 1.5. (Which sucks since I used WiFi quite a bit, but at least the watch is usable.) I'm going to reenable WiFi tomorrow to see if the lag returns.
jde984 said:
My watch was incredibly laggy and had terrible battery drain too. Today I did nothing different besides turning WiFi off and the lag is gone and the battery is similar to 1.5. (Which sucks since I used WiFi quite a bit, but at least the watch is usable.) I'm going to reenable WiFi tomorrow to see if the lag returns.
Click to expand...
Click to collapse
I just turned wifi off and the difference is night and day. Thanks, because I thought I was going to have to find a way to get 1.x back.
The UI is fluid most of the time, notifications come without delay but functionality seems to be down. I think Google has messed up Android Wear. Needs another major update imo.
TheSanitarium said:
The UI is fluid most of the time, notifications come without delay but functionality seems to be down. I think Google has messed up Android Wear. Needs another major update imo.
Click to expand...
Click to collapse
Weird that it's seemingly such a randomly different experience for each user. My UI is laggy as hell, and the notifications only seem to show when they want to! It does vibrate when receiving them but either shows nothing (leaving me to swipe up to see what it is) or auto-pops up and takes up my whole watch face! Yet if I receive a phonecall, I'm lucky if my watch acknowledges it at all! Maybe, in 2 out of 10 tries?!
... Which leads me into completely agreeing with the downturn in functionality. On the couple of occasions my watch had picked up that I'm receiving a call, it only gives me the option to hang up! (Making my paid for Wear Speaker app effectively useless.) No way to answer from the watch at all. Same goes for notifications. Email for example, I can delete, archive or reply (all on the watch only) but I can't just tap to open it on my phone like I used to be able to! YouTube video subscription notifications are just that... Notifications! As the only option is to add to the watch later list. No option to open on the phone. Nothing!
Basically, it's great that they've added functionality that enables you to use the watch without the phone... But not at the expense of cutting out the phone completely! It still needs the phone to function fully, and is STILL only a companion product to go with a phone! I seriously don't understand how they've managed to screw this up so badly even after all the delays??! ?
It is weird because enough people report your experience for it to be just in your head. My was slow for a few hours but then sped up and is nice and at least as fluid as 1.5.
I did reboot and that didn't help. Factory reset made a huge difference.
Any ideas how to downgrade? My watch is practically usless... I hate the new update they've removed every single thing that made this watch remotely usefull
Yeah this update sucks on the urbane, everything takes much longer and isn't smooth... Good timing for me since I'm getting back into shape I bought a Fitbit charge 2 and will sell the urbane if it's worth anything.. I would like the Movado Wear watch but I'll make sure it's also not underpowered before purchase..
Thanks Google!
Sent from my SM-G935P using Tapatalk
How can I install an apk in the watch? Untill now installing it on the phone was enough, but with 2.0 release it seems that you can only install programs with the play store installed on the watch. I suppose with adb I will able to install apks but does anyone know an easier method?
Thanks
Sent from my SM-G935F using Tapatalk
chomi7 said:
How can I install an apk in the watch? Untill now installing it on the phone was enough, but with 2.0 release it seems that you can only install programs with the play store installed on the watch. I suppose with adb I will able to install apks but does anyone know an easier method?
Thanks
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
In the settings on the watch there is an option for something like 'apps on phone' where you can select which apps you want to be installed from the phone instead of automatically like in 1.5. It may be an option in the Play store on the watch. I don't have 2.0 yet, waiting for my Urbane 2nd Edition update, but I've read about it.
mward1995 said:
In the settings on the watch there is an option for something like 'apps on phone' where you can select which apps you want to be installed from the phone instead of automatically like in 1.5. It may be an option in the Play store on the watch. I don't have 2.0 yet, waiting for my Urbane 2nd Edition update, but I've read about it.
Click to expand...
Click to collapse
Exactly!!! You can find an option in the watch Play Store called apps on phone where you can download into the watch the apps you need.
Thank you very much!!
Sent from my SM-G935F using Tapatalk
Used to be able to press the button twice and turn the screen off too
radiotecha1234 said:
Used to be able to press the button twice and turn the screen off too
Click to expand...
Click to collapse
Yeah, that option is missing now. Currently swiping down, tapping the sun symbol and then the watch-sysbol in the middle below seems to be the only way.
But at least after I did a factory reset of the watch yesterday and paired it again with my LG V10 the watch runs much smoother than before. Truth be told I have not installed all applications yet I was running on the Urbane before (like Watchmaker for example) but I will install one after another and check if the lags I had before reappear.
Mine had AW 1.1 out of the box. Upgraded to 2.0 and it was unusably laggy. Even tilt-to-wake was very delayed. "OK Google" would take over 10 seconds for assistant to come up.
My watch too has become barely useable. Google assistant can sometimes take upwards of 20 seconds to load. And there is a huge delay on my notifications, I don't even receive notifications for calls. Android wear 2.0 has definitely ruined my watch, which is sad because I love using assistant on my phone to control my Philips hue lights.
Did anyone contact LG or Google about this problem? Android Wear 2 made my device useless after just 1,5 years. That's unacceptable!