So now, thx to AW2.0, we can change the name of this watch, it's no more a "smart watch" but a simple "alert watch".the watch primarily serves as an alert device for me and not some multifunctional do it all
CooL
So now, thx to AW2.0, we can change the name of this watch, it's no more a "smart watch" but a simple "alert watch".the watch primarily serves as an alert device for me and not some multifunctional do it all
Reply to sms missing? Are you sure?May the "not remembering time after shut down" be the hardware thing, but its a fail. It can be done but isnt.
The phone call handling is a bad design on 2.0. Accepting it on watch and starting it on phone was a perfectly fine thing in 1.5.
However, on Huawei Watch with 2.0, the phone call can be accepted ONLY if you allow phone audio over bluetooth = talking to your watch. Once you do that, you have 2 circles on incoming call screen. I see someone at Google thought that if the watch is going to be more independent, then lets do it thouroughly.
But the purest fail is that reply with sms is missing. Unacceptable and totally contradictory with "independence" of watch, in my opinion.
Don't know about that but that's how I've treated all my AW devices all this while as no matter what, I'd still refer to my phone for most of my work although I do appreciate the Fit functions and the fact i can quick reply (busy and stuff) especially when am driving or in a meeting, and also a decent remote for spotify and play music while I'm drivingSo now, thx to AW2.0, we can change the name of this watch, it's no more a "smart watch" but a simple "alert watch".
CooL
Me too. The "quick reply or quick reject with SMS" is one of the key wear feature I'm using many times per day....I do appreciate the Fit functions and the fact i can quick reply (busy and stuff) especially when am driving or in a meeting...
Unfortunately that's abit of a downside but it's not a deal breaker for me anyway as otherwise it's been serving me well AW 2.0 wise to be livableMe too. The "quick reply or quick reject with SMS" is one of the key wear feature I'm using many times per day.
This is why we are so disapointed with the Google decision to remove it with AW2.0.
The other key feature is also the very efficient "double click" on the button to switch off the screen in less than one second. So cool during the night.
Anyway... Rendez-vous with the AW2.1
No, not TO. WITH. Reply with sms when you decline a call. Thats what I meant.Reply to sms missing? Are you sure?
me. I've repaired device and now it's working. Generally there's a problem with notifications, as there's a dedicated page about it:Not getting notifications anymore on the watch, did a factory reset of the watch and it was working again. Just updated some apps on the watch and now it's not working again. Last update was the Google app and I installed puji black. Anybody else problems with the notifications?
Sent from my bla bla bla bla bla
No such thing unfortunately. Not even in the settings. The button just got dumb. Fk Googlehow can i turn on the sunlight mode? it use to be triple tap on the power button in AW1.5 but now in AW2.0 it does nothing... without the auto brightness this watch is useless under the sun.
Did you read that:well the watch was working great on 2.0 just upgraded my phone to the s8 now I am unable to sync my google account to the watch, it just gets stuck on the accounts screen where it tries to find the account on the phone to sync to the watch. anyone else faced this issue and have a solution? I have factory reset the watch like 4 or 5 times and also removed android wear and installed it again no luck.
yes but there was no concrete resolution in that thread for the issue. I only have 1 google account setup on the phone. Considering going back to 1.5 and using the watch which seems to be the only solution.Did you read that:
Google Android Wear Help forum
Correct. As we have the choice (chance) with our watch to go back to 1.5, I think it's better to wait for the new android wear release (2.1 or 3.0) which could (perhaps) solve a part of all the bugs and regressions, by using the AW 1.5 than AW 2.0.yes but there was no concrete resolution in that thread for the issue. I only have 1 google account setup on the phone. Considering going back to 1.5 and using the watch which seems to be the only solution.
yes i really liked wear 2.0 and didnt have many issues, guess i have no choice but to flash back to 1.5Correct. As we have the choice (chance) with our watch to go back to 1.5, I think it's better to wait for the new android wear release (2.1 or 3.0) which could (perhaps) solve a part of all the bugs and regressions, by using the AW 1.5 than AW 2.0.
I have had this problem too. I think that removing watch from bluetooth settings on the phone was the solution. And turn the visibility on in the bluetooth...yes i really liked wear 2.0 and didnt have many issues, guess i have no choice but to flash back to 1.5
could you elaborate this a bit for me please, i removed the watch from bluetooth settings on the phone but now the wear app does not connect to it at all. It just says connecting and does not move forward.I have had this problem too. I think that removing watch from bluetooth settings on the phone was the solution. And turn the visibility on in the bluetooth...
P. S.
You need to be careful with pairing pin confirmation, because I got two requests - one as standard bluetooth device and one from Wear app. If you add your watch as a standard Bluetooth device, copying Google account will not work
Sent from my SM-N910C using Tapatalk