Related
I just purchased the Smartwatch 3. I like the watch but have a problem. Not all of the wear apps are loading on the watch. For instance, I've downloaded Ghostracer, Runtastic and Endomondo and while they appear on my phone; they do not appear on the watch. However, other apps I have downloaded are on there and I can install new watch faces. Oddly enough Spotify and Skype are on the watch and I didn't attempt to put them on my watch. It seems to be hit or miss.
I sent an email to the manufacturer of one of the apps and they said it may be due to Google Play Services not being the most recent. I am currently on version 9.4.52.
Any help would be appreciated.
hardwirk1 said:
I just purchased the Smartwatch 3. I like the watch but have a problem. Not all of the wear apps are loading on the watch. For instance, I've downloaded Ghostracer, Runtastic and Endomondo and while they appear on my phone; they do not appear on the watch. However, other apps I have downloaded are on there and I can install new watch faces. Oddly enough Spotify and Skype are on the watch and I didn't attempt to put them on my watch. It seems to be hit or miss.
I sent an email to the manufacturer of one of the apps and they said it may be due to Google Play Services not being the most recent. I am currently on version 9.4.52.
Any help would be appreciated.
Click to expand...
Click to collapse
I had the same problem at the beginning of my adventure with SW3.
Google Play Services is too old.
Try force-updating it on your phone (use this link) or else just wait a couple hours, it should update itself both on phone and on the watch. Anyway AFAIK Android Wear app shows an information when Google Play Services are out of date but I'm not sure.
Or try force-syncing the apps in the watch settings in Android Wear app.
Or, as I've already told, just wait a couple of hours and make sure you have your watch paired and connected to the phone during that time
Or if nothing happens, try unpairing the watch. It will reset to the factory settings (you won't lose any data connected with the watch from your phone except the watch that was paired), pair the watch again and wait for the setup to complete, it will sync all the necessary apps with the phone.
romcio47 said:
I had the same problem at the beginning of my adventure with SW3.
Google Play Services is too old.
Try force-updating it on your phone (use this link) or else just wait a couple hours, it should update itself both on phone and on the watch. Anyway AFAIK Android Wear app shows an information when Google Play Services are out of date but I'm not sure.
Or try force-syncing the apps in the watch settings in Android Wear app.
Or, as I've already told, just wait a couple of hours and make sure you have your watch paired and connected to the phone during that time
Or if nothing happens, try unpairing the watch. It will reset to the factory settings (you won't lose any data connected with the watch from your phone except the watch that was paired), pair the watch again and wait for the setup to complete, it will sync all the necessary apps with the phone.
Click to expand...
Click to collapse
Thanks for replying. You were right. I tapped on the version and it updated like 4 times during the night. When I woke all of the apps were on the watch.
Hi all!
I do not recieve any Messages on my Huawei Watch (neither WhatsApp, nor SMS or Telegram) from my HTC One M7 (rooted). Calendar notifications and phone calls are working without any problems.
I realized that problem since i did a full wipe and reinstalled VipeOne 9.0 ROM.
This steps also did not help and i did a reset and new pairing multiple times without any success.
Could there be any settings which are set wrong?
How can i detect and solve this problem to get my notifications back?
Because i do not know if the problem is Android or Android Wear related or has something to do with the Huawei Watch or ViperOne ROM, i did a post in this Forum...
Thank you for helping in advance,
Florian
it could be related to this sort of thing http://forum.xda-developers.com/huawei-watch/general/bad-battery-life-read-factory-reset-t3474948
go to apkmirror.com and download the latest version of Google Play Services for your phone then double reboot phone and watch twice (could take a day for Google play services on watch AND phone to sync their versions)
since you wiped your rom I'd bet your version of Google Play Services is out of sync with what's on the watch (probably would fix itself after a week off trickling the updates)
pablo71 said:
it could be related to this sort of thing http://forum.xda-developers.com/huawei-watch/general/bad-battery-life-read-factory-reset-t3474948
go to apkmirror.com and download the latest version of Google Play Services for your phone then double reboot phone and watch twice (could take a day for Google play services on watch AND phone to sync their versions)
since you wiped your rom I'd bet your version of Google Play Services is out of sync with what's on the watch (probably would fix itself after a week off trickling the updates)
Click to expand...
Click to collapse
Hi pablo71,
thank you for your answer.
I downloaded the newest Google Play Services apk from apkmirror.com, installed it and restartet Watch and Phone multiple times.
But after over 24h there is still the same problem...
What can i do? Reset the phone another time or sync Google Play Services manually or something else?
htcdesire-hd said:
Hi pablo71,
thank you for your answer.
I downloaded the newest Google Play Services apk from apkmirror.com, installed it and restartet Watch and Phone multiple times.
But after over 24h there is still the same problem...
What can i do? Reset the phone another time or sync Google Play Services manually or something else?
Click to expand...
Click to collapse
my apologies for late reply ... I don't know what could be done, but if your watch was rooted I'd say to install the app Advanced Settings, then open it ON THE WATCH and go to Apps > System > Google Play Services > CLEAR DATA ... THEN go to Android Wear on the phone and FORGET THE WATCH ... THEN Reboot the watch, open Advanced Settings on watch go to Bluetooth > check the Discovery Mode Box and RE-PAIR the watch with Android Wear .. when I have the problem 'that sounds like what you're describing' this procedure fixes it for me.
sorry you're having problems with your watch .. if it's because of data-cross-contamination between different versions of Google Play Services updates that is causing this then I hope Google takes some action and stops doing this ... non-functioning watches does NOT make people want to buy smartwatches
pablo71 said:
my apologies for late reply ... I don't know what could be done, but if your watch was rooted I'd say to install the app Advanced Settings, then open it ON THE WATCH and go to Apps > System > Google Play Services > CLEAR DATA ... THEN go to Android Wear on the phone and FORGET THE WATCH ... THEN Reboot the watch, open Advanced Settings on watch go to Bluetooth > check the Discovery Mode Box and RE-PAIR the watch with Android Wear .. when I have the problem 'that sounds like what you're describing' this procedure fixes it for me.
sorry you're having problems with your watch .. if it's because of data-cross-contamination between different versions of Google Play Services updates that is causing this then I hope Google takes some action and stops doing this ... non-functioning watches does NOT make people want to buy smartwatches
Click to expand...
Click to collapse
No Problem!
Today i unlocked my Watch and installed Advanced Settings. Then i deleted the data from Google Play Services and did a Reset and tried everything you described, but untill now no messages arrived on the watch... Could there be something else wrong or settings on my phone?
The Google Play Service Version on the phone and on the watch are nearly the same (10.0.84) but the number after the bracket are different (238-... on phone and 530-... on watch)...
Thank you, yes its very annoying having a Smartwatch which isn't recieving any messages ... hope it can be fixed, but because its only software related it should be viable.
htcdesire-hd said:
No Problem!
Today i unlocked my Watch and installed Advanced Settings. Then i deleted the data from Google Play Services and did a Reset and tried everything you described, but untill now no messages arrived on the watch... Could there be something else wrong or settings on my phone?
The Google Play Service Version on the phone and on the watch are nearly the same (10.0.84) but the number after the bracket are different (238-... on phone and 530-... on watch)...
Thank you, yes its very annoying having a Smartwatch which isn't recieving any messages ... hope it can be fixed, but because its only software related it should be viable.
Click to expand...
Click to collapse
wow that would drive me crazy .. all I can think of would be to try the earlier version of Android Wear on the phone you used to have ... apkmirror would have it .. wow good luck I hope it gets fixed
I tried to install an older version of Android Wear but it did not help.
So i don't know what to do anymore...
Solved!
I just got the solution for my problem!!
It was a very stupid mistake: Android Wear was not set as device administrator... There was even a notification on my Wear app,
but i didn't recognized it because normally there is a notification to activate locations and it looks exactly the same
htcdesire-hd said:
I just got the solution for my problem!!
It was a very stupid mistake: Android Wear was not set as device administrator... There was even a notification on my Wear app,
but i didn't recognized it because normally there is a notification to activate locations and it looks exactly the same
Click to expand...
Click to collapse
How did you check to make sure that it was? I too am having a similar problem where my SMS notifications would sometimes take over 2 minutes to get to my watch.
rimz808 said:
How did you check to make sure that it was? I too am having a similar problem where my SMS notifications would sometimes take over 2 minutes to get to my watch.
Click to expand...
Click to collapse
Because all system related notifications arrived on my watch without any problems and all notifications of third party apps didn't, it could only be Phone related...
You have an other problem, because the SMS notification is system related.
Do you sync via cloud (wifi) or via Bluetooth?
Did you try to reset your watch or reinstall the wear app (and delete app data)?
^good to know!
htcdesire-hd said:
Because all system related notifications arrived on my watch without any problems and all notifications of third party apps didn't, it could only be Phone related...
You have an other problem, because the SMS notification is system related.
Do you sync via cloud (wifi) or via Bluetooth?
Did you try to reset your watch or reinstall the wear app (and delete app data)?
Click to expand...
Click to collapse
I meant how did you check to see that Android Wear was set as device Admin? I looked in my device admin and did not see Android Wear in the list.
But I did do a reset of my watch and re-paired, and that seem to have fixed the notifications delayed.
rimz808 said:
I meant how did you check to see that Android Wear was set as device Admin? I looked in my device admin and did not see Android Wear in the list.
But I did do a reset of my watch and re-paired, and that seem to have fixed the notifications delayed.
Click to expand...
Click to collapse
Sorry it was not the device admin query, but the notification access query (Preferences -> Apps -> Settings -> something like "Special access" -> Notification access).
Good to hear, that your problem is also resolved!
Not resolved. Same problem. Notification would arrive much later than on phone, and even calls are now not going to my watch. I performed another watch factory reset again, but why am I having to keep doing this?
I have a Huawei watch with a Huawei Mate 9. I would expect both to work seamlessly together. I had no problems when my watch was synced with my Axon ZTE 7.
So this is what I believe is causing the problem. When the phone and watch gets out of range (walking away from my desk without my phone), for some reason the phone and watch does not ask to be paired. It looks as though they are both still connected. With my Axon 7, whenever both got out of range and wanted to connect again, I would get a notification asking if I wanted to pair the watch with my phone. I would then accept. In this case, with the Mate 9, I do not get that pairing notification and I believe that is why i do not get notifications to my watch after it has lost its connection. I had to manually unpair the watch from my phone, then pair it up again.
Any insights?
rimz808 said:
So this is what I believe is causing the problem. When the phone and watch gets out of range (walking away from my desk without my phone), for some reason the phone and watch does not ask to be paired. It looks as though they are both still connected. With my Axon 7, whenever both got out of range and wanted to connect again, I would get a notification asking if I wanted to pair the watch with my phone. I would then accept. In this case, with the Mate 9, I do not get that pairing notification and I believe that is why i do not get notifications to my watch after it has lost its connection. I had to manually unpair the watch from my phone, then pair it up again.
Any insights?
Click to expand...
Click to collapse
I do also have a Huawei Mate 9 and i dont have any problems... I did never get a re-pair notification (on my HTC One M7 also). It re-paired automatically when i was in range!
htcdesire-hd said:
I do also have a Huawei Mate 9 and i dont have any problems... I did never get a re-pair notification (on my HTC One M7 also). It re-paired automatically when i was in range!
Click to expand...
Click to collapse
And your notifications come to your watch the same time it comes to your phone? Just to clarify, mine does automatically re-pair when it gets in range again, but I was thinking that maybe somehow it doesn't fully re-pair, which was the cause of my delayed/missed notifications? So I wanted to manually re-pair to make sure it did.
Still trying to figure out when my notifications sometime shows up, and sometime does not. Baffled.
The messages arrive about 1-2s later (i disabled vibration on my phone) and since i set Wear for special access everything works without problems, like before...
If i understand right, your notifications arrive after a couple of seconds or sometimes they do not arrive? Is there a coherence when they arrive and when not? (for example always when you re-pair it don't work and when it's constantly paired it works, but delayed?)
And are you syncing with Bluetooth or Wifi (cloud)?
htcdesire-hd said:
The messages arrive about 1-2s later (i disabled vibration on my phone) and since i set Wear for special access everything works without problems, like before...
If i understand right, your notifications arrive after a couple of seconds or sometimes they do not arrive? Is there a coherence when they arrive and when not? (for example always when you re-pair it don't work and when it's constantly paired it works, but delayed?)
And are you syncing with Bluetooth or Wifi (cloud)?
Click to expand...
Click to collapse
I am going to keep monitoring and see if I notice any patterns to when I do receive notifications instantly, and when I do not. Yes, sometimes my notifications, i.e SMS, or my CNN notifications, I will hear that it arrive on my phone, but then look at my watch and do not see the notifications. Sometimes, it would eventually go on my watch a few minutes afterwards.
When I re-paired it, I did notice that my notifications appeared instantly. I did not try to walk away from my phone and come back to have it re-paired automatically. I can try that today and see what happens. I just turned on wi-fi sync yesterday. But would i still be getting text SMS through wi-fi?
When you say that you set Wear for special access, where about did you check that?
Yes, try to find out what commonly happens when it does not work...
I haven't been trying wifi sync but i think all notifications should work like using bluetooth.
htcdesire-hd said:
Sorry it was not the device admin query, but the notification access query (Preferences -> Apps -> Settings -> something like "Special access" -> Notification access).
Click to expand...
Click to collapse
Hi,
I have a OP3 running OxygenOS 4.0.3.
The phone has been running without issues, but now I have one.
A couple of days ago I turned the battery saver on. Ever since then, for notifications, it is behaving like if it was in battery saving mode. So, I don't get gmail, outlook, facebook, ... notifications. Telegram is working tough.
In parallel, I've tried to set-up Google Prompt as 2nd step authentication and I'm getting the following error:
"It looks like you have a compatible phone, but it's not online. "
I can confirm that my phone is online and that I can browse the internet. Probably this has the same root cause as the notifications problem.
Any help?
Do a factory reset and setup your Google account again. Looks like the phone is not able to contact the Google servers.
Thanks for the answer,
The phone is capable of reaching google servers. If I open the Gmail app for example and refresh, it fetches my mails.
I think that somehow the problem is that applications are not accessing data in the background.
I have a similar problem. When I'm connected to wifi I miss and not receive some notifications. Even got me in a bind a few times with work. Uugh
Hi
Just bought the watch from Amazon Uk and bought a charger and got it working. Followed all the instructions and synched the watch with my phone (one plus one on RR Rom).
Also change it to developer options and also checked unknown sources. Also downloaded the android wear app onto phone.
However I don't have the Play app store on my phone and it looks like not all contacts have synched and only certain apps fed in. Did all the power off etc and also unpaired phone and same issue. Also updated to latest Android Wear
Cannot find anything on web and just found this forum and trying to find if I am missing something etc as it states in manual it does support facebook, twitter etc but I cannot get these apps loaded onto watch.
Any help appreciated
Cheers
Maybe flash AW 2.0 DP5? It will be a complete replacement of the OS.
Pretty sure it just means supports "All" app notifications including facebook, twitter etc etc. These are just standard android notifications. Facebook itself does not have a wear app, thats something facebook would need to release.
Any ideas what this could mean¿?
I've been getting that all day today as well, wonder if it means theres a bug with the date or something?
I m guessing it has something to do with an update of Google App. I get the same error when opening it.
OMG, this has been happening to me all day as well and it's been driving me nuts. I've tried everything to fix it; reverted to the non-beta Google app, cleared the Google app cache/data, cleared Google Play Services data, and eventually reset my watch (twice). The Google app starts working again (though no feed cards) but then the watch installs "Your feed" and the problems begin again.
I'm on a Pixel with Oreo, for what it's worth.
Facing the exact same problem, reset twice as well, once the "your feed" is installed on the watch, i keep getting the error, i think the your feed is the app that pushes the google card to the watch? coz i don't see any of the google card appearing on the watch after getting those error, and i don't know how to disable the app as well
I have the same problem! for 3 days in a row this notification is appearing every minute! any solution?
I'm having this too...
Someone has to get a logat to see what app is doing this...
muldy said:
I'm having this too...
Someone has to get a logat to see what app is doing this...
Click to expand...
Click to collapse
It's the Google app. Try opening it, you'll get the same error...
I'm hearing this is from the beta version of the Google application. Is everyone here opted into the beta version?
I am, yes. Uninstalling the beta version updates didn't help though, presumably because the watch hadn't synchronised any changes.
Same Story...
I've also had this same error for about three days, ever since the latest Google app update. Did a factory reset, and the error started again once the Google app installed fresh. My wife has a Moto 360 Sport, and the Google app on her watch now has 'Your Feed' by the G logo. I'm wondering if they made some Wear 2.0 specific change that's not compatible with Wear 1.0? I am using a Pixel XL with my SW3, for what it's worth.
Can confirm that the Google app is broken on AW. Everytime I manually start the app out crashes. Looks like Google has some more work to do. But hey, that's what betas are for ¯\_(ツ)_/¯
Opting out of the Beta program for the Google app, uninstalling the beta version, and then waiting a little while for the changes to sync to my SW3 appears to have fixed this for me and I can now open the Google app on my watch without getting the error. Unfortunately, this has also reset my home screen layouts and removed all my widgets
skimble said:
I am, yes. Uninstalling the beta version updates didn't help though, presumably because the watch hadn't synchronised any changes.
Click to expand...
Click to collapse
I'm using the beta as well. Haven't tried downgrading yet.
Finally found people with the same problem!
My Samsung Gear Live has been just permanently on a white screen saying my feed has stopped and the whole thing is literally unusable. It's been like this for about a week, and i've unpaired, resetup, cleared cache, rebooted and even uninstalled as many apps as I could via debugging. I did not uninstall "google search", but if it's not a root app I will try that now!
My ASUS Zenwatch is doing the same thing!
RcktsRGr8 said:
I've also had this same error for about three days, ever since the latest Google app update. Did a factory reset, and the error started again once the Google app installed fresh. My wife has a Moto 360 Sport, and the Google app on her watch now has 'Your Feed' by the G logo. I'm wondering if they made some Wear 2.0 specific change that's not compatible with Wear 1.0? I am using a Pixel XL with my SW3, for what it's worth.
Click to expand...
Click to collapse
The beta Google app on my Pixel XL updated last night, and since the update the white screen "your feed has stopped" hasn't come back, but if I try and run the Google app on my SW3, it immediately kicks to the error screen. So the Google app still won't run on my watch, but the constant error screen has gone away. Looks like the Wear 1.0 version of the app still needs some polish.
LG G
RcktsRGr8 said:
The beta Google app on my Pixel XL updated last night, and since the update the white screen "your feed has stopped" hasn't come back, but if I try and run the Google app on my SW3, it immediately kicks to the error screen. So the Google app still won't run on my watch, but the constant error screen has gone away. Looks like the Wear 1.0 version of the app still needs some polish.
Click to expand...
Click to collapse
Same problem. I switched watch faces to something from a company called HuskeyDEV. Prior I had a face that came from Android Wear. Since then it's only happened 1 time. Before it was every few minutes. No idea the switch might work, but it seems to. Just sayin
OK, so the very latest (23rd) Google app update seems to have resolved it for me. I uninstalled the Google app from the watch via adb and it didn't crash, then I let the google update go through and my watch then said that "feed" was installed and it hasn't crashed in 24 hours. Previously it would ONLY display the crash screen and was completely unusable.
steve.rand said:
OK, so the very latest (23rd) Google app update seems to have resolved it for me. I uninstalled the Google app from the watch via adb and it didn't crash, then I let the google update go through and my watch then said that "feed" was installed and it hasn't crashed in 24 hours. Previously it would ONLY display the crash screen and was completely unusable.
Click to expand...
Click to collapse
Well it crashed again today, in an endless crash loop. I have uninstalled Google Search via adb again and it's fine for now.
Opting out of the Beta for the Google app might be the only permanent solution. I don't mind the bugs that come with beta's, but this one is making the watch useless. =-[