So, haven't had much time to play and learn yet, and this is my first smart watch. But I did try sending emails and text via the watch. If my screen is on, it works, if it is off it fails.
My phone is a Note 4, with an MM Rom. I'm wondering if Doze or something is the problem.
When I was setting up the app, it did go through an option to let the Zen software run in the background, and I allowed that.
Any thoughts?
ewingr said:
So, haven't had much time to play and learn yet, and this is my first smart watch. But I did try sending emails and text via the watch. If my screen is on, it works, if it is off it fails.
My phone is a Note 4, with an MM Rom. I'm wondering if Doze or something is the problem.
When I was setting up the app, it did go through an option to let the Zen software run in the background, and I allowed that.
Any thoughts?
Click to expand...
Click to collapse
I am not sure if I really understand your question.. are you talking about phone screen or watch screen?
Also for notifications like text you don't need to have Zenwatch app at all, its a core feature of AW. I am using it (& Moto 360 gen 1 before) with my S7 on MM and doze shouldn't cause any issue.
Ah, I just read the thread title, it gives more info
I would say factory reset your watch from the Android Wear app on the phone and try to pair again. I have done it a bunch of times with my Moto 360 but haven't tried with this one yet. It should work though, I'll try on mine and report back.
jainanshal said:
I am not sure if I really understand your question.. are you talking about phone screen or watch screen?
Also for notifications like text you don't need to have Zenwatch app at all, its a core feature of AW. I am using it (& Moto 360 gen 1 before) with my S7 on MM and doze shouldn't cause any issue.
Ah, I just read the thread title, it gives more info
I would say factory reset your watch from the Android Wear app on the phone and try to pair again. I have done it a bunch of times with my Moto 360 but haven't tried with this one yet. It should work though, I'll try on mine and report back.
Click to expand...
Click to collapse
Well, I reset my watch. I still get the message "Try again on your phone" . But, I found that the email in fact did send. So not sure what's up with that. Will be interesting to see what you find.
Oh, another thing. I find quite a delay between my phone ringing and it ringing at the watch. I'll have to do some experimentation, but I'm not sure it will ring long enough for me to answer it at the watch. Not that I plan to do that much, but, anyway...seems like maybe the interaction time between the watch and phone is not very good.
Hey sorry for replying so late, but as expected, calls and texts work just as they should. Were you able to sort out issues on your end?
About the delay, I think there has always been a little delay for calls to show up on watch (at least that was the case with my moto 360), delay on this is the same. It does vary a little bit from time to time, sometimes it very little sometimes a bit longer but that's just wireless connectivity imo. But in no case its long enough that call would stop ringing and go to voicemail.
jainanshal said:
Hey sorry for replying so late, but as expected, calls and texts work just as they should. Were you able to sort out issues on your end?
About the delay, I think there has always been a little delay for calls to show up on watch (at least that was the case with my moto 360), delay on this is the same. It does vary a little bit from time to time, sometimes it very little sometimes a bit longer but that's just wireless connectivity imo. But in no case its long enough that call would stop ringing and go to voicemail.
Click to expand...
Click to collapse
I need to do some testing with calls. I don't even know for sure how to answer at the watch.
I find that the watch gives me the error message, but does send the text.
I'm having real problems with my phone when hooked to the watch. I'm going to open a thread on that topic now.
I just got Android Wear 2.0 on my Zenwatch 3 and I'm sorry to say Assistant and gestures are lot worst now.
First of all, i'm italian, and Assistant poorly recognise italian lenguage.
I use to use smartwatch especially when i'm driving or when i'm on my work bike (i'm a pony express) so I need a device I can use touchless.
Wear 2.0 lost some gestures as the on to go ahead to funcion like "reply" or "delete" in messages (the ones used pushing down or pulling app your wirst) so now i must to touch the screen for everything.
About Assistant: i often use it to send Telegram messages just by telling Google Now (obviously in italian) "send Telegram message to SomeoneX" followed by the message instead.
Now, if i tell "Ok Google. Send a Message to (ex.) Mark" assistant shows me "to whom?"... anda I say "Mark"... "to whom?"... "MARK!"... "to Whom?"... IN A FU****G LOOP!
jUST i CAN'T USE MY SMARTWATCH WITHOUT MY HANDS ANYMORE!
Related
So my dad just picked up a Moto X today on Verizon, I've had my DE edition on VZW for about 2 weeks now. Well, I was over at his house today showing him some stuff, and I noticed his phone announced calls and texts all the time, even when not driving, and asked him if he wants to answer. I of course turned off Moto Assist, but it still announced calls and asked if he wanted texts read back. (It would announce who texted and ask if he wanted to listen, or ignore. Not sure if mine does this, I had Assist off before today) I went through every single option on his phone. I'm guessing the Moto Assist is bugged into thinking he's always driving, but the little icon never shows up in his notifications, and I actually turned off Assist and it was still doing it. Cleared data too. I tried everything. Reboots, turned on and off GPS, etc.
The rub is, we both actually LIKE it on all the time. It's nice to just have the phone on the desk and hear who's texting and the message without having to touch the phone. It's nice to be able to answer the phone on the coffee table without grabbing the phone, or even moving.
Is there anyway to enable this functionality all the time? (Or disable it on my dad's phone for that matter) Has anyone else run into this 'issue'? (If my dad hadn't seen my phone, he would have never known it wasn't supposed to be like that all the time.) Any ideas?
I too would like to see this 'feature' as a option, and I hope it can be enabled [on purpose] in the future. (If Motorola doesn't have sense enough to make it an option, maybe a ROM developer can.)
I searched and found this:
We're aware of a rare condition when calls and text will be announced even when you can't see the "drive mode" notification on the status curtain. We're fixing this in the next upgrade. (The simplest way to get out of this situation -- and it's not that simple -- is to leave Assist's drive mode settings on, get in a vehicle, allow drive mode to kick in again. When you do that, Assist will get back to the correct state. After the issue is fixed, you should rarely encounter the issue again. Yeah, I know. Not something anyone is eager to do but we wanted to put it out there.)
Click to expand...
Click to collapse
http://forums.androidcentral.com/motorola-droid-maxx/314715-assist-driving-problem.html#post3072243
FWIW I first thought your dad's phone might be stuck in "car mode" as thought it was in a car cradle, but that would have a steering wheel icon in the notification area. I actually tried car mode by using the "car mode on" app to force it on. It seemed to put my phone in car mode, but that alone did not cause the phone to announce calls, etc.
Thanks man! I actually found that post as well earlier today, it looks like it is indeed a bug with Moto Assist. Funny thing is, my dad has it left on and I called him this morning after he drove to work, and it's still working. IDK lol, but he likes it so whatever.
I would LOVE to be able to do this while playing video games, or working, or whatever though. Motorola better just make a toggle switch... it's not like it's hard.
Is anyone experiencing their phone waking up and waiting for you to ask it something? It's happened just sitting on the counter, my pocket or streaming music/podcasts. It happens at least one or more times a day, I tried retraining it for my voice a few times but still happens.
FSRBIKER said:
Is anyone experiencing their phone waking up and waiting for you to ask it something? It's happened just sitting on the counter, my pocket or streaming music/podcasts. It happens at least one or more times a day, I tried retraining it for my voice a few times but still happens.
Click to expand...
Click to collapse
Go retrain it once more in a completely silent room. You should be able to hear nothing except air moving (fan, a/c, etc.). Then report back.
FSRBIKER said:
Is anyone experiencing their phone waking up and waiting for you to ask it something? It's happened just sitting on the counter, my pocket or streaming music/podcasts. It happens at least one or more times a day, I tried retraining it for my voice a few times but still happens.
Click to expand...
Click to collapse
Biggest thing is keep it at arm's length. Like really, extend your arm to the fullest, and then speak normally. Try it.
natezire71 said:
Go retrain it once more in a completely silent room. You should be able to hear nothing except air moving (fan, a/c, etc.). Then report back.
Click to expand...
Click to collapse
jhnl33 said:
Biggest thing is keep it at arm's length. Like really, extend your arm to the fullest, and then speak normally. Try it.
Click to expand...
Click to collapse
The last time I walked out to my garage to be away from any noise, I'll try again today and make sure I hold it at arm's length(tried that on initial setup)
FSRBIKER said:
The last time I walked out to my garage to be away from any noise, I'll try again today and make sure I hold it at arm's length(tried that on initial setup)
Click to expand...
Click to collapse
Good luck! I had the same issue as you in the beginning. I uninstalled updates and reinstalled to try to make sure previous cache and settings were cleared and re-trained at arms length and now it works pretty well!
FSRBIKER said:
The last time I walked out to my garage to be away from any noise, I'll try again today and make sure I hold it at arm's length(tried that on initial setup)
Click to expand...
Click to collapse
also, make sure you use the same pitch and cadence when saying it. If i want the phone to pick up my voice easier, i can say ok google now when training it in slightly different ways. But then my phone also comes on and thinks im saying it when no one has said anything close to ok google now. If you make sure everything sounds the exact same when saying it, i didn't run into any problems. But i can't wake the phone up when i first wake up in the morning lol. I always try but i apparently sound like death whenever i first wake up.
jayboyyyy said:
also, make sure you use the same pitch and cadence when saying it. If i want the phone to pick up my voice easier, i can say ok google now when training it in slightly different ways. But then my phone also comes on and thinks im saying it when no one has said anything close to ok google now. If you make sure everything sounds the exact same when saying it, i didn't run into any problems. But i can't wake the phone up when i first wake up in the morning lol. I always try but i apparently sound like death whenever i first wake up.
Click to expand...
Click to collapse
I agree, try using the same voice for all three samples. I know that early on people were suggesting you say it with slightly different speed etc but I have found it is best to try to say it the same all three times and let the software in the Moto X handle slightly variations automatically.
Mine wakes up all day sitting on my desk at work. I do talk about Google a lot, but I never say my phrase. It's funny some of the stuff I see it type...
Sent from my XT1060 using Tapatalk
This is an interesting thread for me. I had the Note 3 (hi galaxy) and Nexus 5 (ok google). Both of them would think I was talking to them when I wasn't, and I have almost the opposite problem with the Moto X. I have a hard time to get it to listen. I re-trained, re-trained, re-trained.. My wife's phone works flawlessly. I do love that we train our voices because she uses here touchless control all the time right next to me and my phone has yet to mistake mine for hers.
Maybe I need shorter arms.
OK quick update, I uninstalled the Touchless Control update and retrained my Moto X again in my garage this morning. It's been about 7 hours and it hasn't once yet turned itself on. I streamed music, have been in congested areas with people, a business meeting and it's working perfectly now.
I'm going to wait for 24 hours to make sure it's still working correctly and then install the update to the app.
About ready to scream!
The touchless control on my Moto X Developer Edition is extremely sensitive. Anytime anyone talks in the office that I work in, the dang phone comes on and waits for someone to give it a command. All anyone has to do is say "OK" and it does this even when I don't want it to. I've tried retraining the phone multiple times and it doesn't seem to help me out at all. I'm going to be so glad when the Lollipop update finally rolls out for this phone so I can get retrain this with a different launch phrase that will not be so easy to trigger on my phone. In the meantime, has anyone been able to get the sensitivity adjusted on this phone? If so, how? I'm thinking of going to Cyanogenmod 12.1 until Lollipop rolls out for the XT1060,
Any help that I can get on this would be greatly appreciated.
Cindy
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.!
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!
Well, this seems to be a common issue that Asus support knows nothing about. I have learned that Asus support is worthless, but I will leave that rant for another post. Anyway, I am having the same issue that many other people seem to have, but I haven't been able to find a solution for it. I have a 6P, latest Android Wear on the phone, latest Android Wear on the watch, and it usually takes 15-30 seconds for the watch to "ring" when I get a phone call. Additional details below.
Here is, in detail, what I have noticed. If I have used the watch recently (sorry, can't provide an accurate, or even estimate time fraim) it seems to work fine, however if it hasn't been used in a while, it can take 15-30 seconds for the watch to notify me of an incoming call. I am used to my pebble, where notifications that take 2 seconds are VERY long delays, usually its instant with the pebble. This also appears to be an issue when an alarm goes off. Alarm, as in set an alarm in the clock app, it takes forever to get the notification on my watch. As far as phone calls, it also seems as though if I answer the phone before the watch starts ringing, the watch can start ringing after I have answered the phone, and am talking on the phone, and the watch won't shut up until the call has ended.
I assume there is a simple fox for this, but I can't find it anywhere. For details, the watch is running 2.8.0.182823779 (Latest at the time of writing) the phone is running 8.0.0 rooted, android wear 2.9.0.185084575.gms (Latest at time of writing)
Practically begging for help here, thanks in advance.
I assume you are using stock AW 2. Everyone of us has had problems with the speed of the watch. The snapdragon 1200 seems to be to slow and old for AW 2. But if you try the ROM available here in the forum made by @janjan , it get's a little bit better.
You have to disable ZenWatch Manager on the watch and uninstall on your phone.
The Zenwatch manager actually processes lots of data before notifying the watch. Hence the lag.