I have an issue, Ok Google keyword is activated in the options of wear 2.0 but the keyword does nothing. if i long press the button the assistant come in but the keyword don't work. Is there a workaround? Am i the only one with this issue?
On my watch it works well.
Settings-presonalization-ok google.
Mike
sp5it said:
Settings-presonalization-ok google.
Mike
Click to expand...
Click to collapse
Already activated but no effect, trying factory reset
Ok, just pinpointed the issue, "ok google" works only if the language is set to english, don't work in french...
Problem was here too. I do reset/wipe my watch and now all work. And now battery is better. Yesterday in 12 hours 80%, today after reset in 6 hours 10%
Working now after 3 factory reset and changing language to english and to french thereafter.
Same problem after the OTA : Ok google doesn't work ! long press the button works fine !
After factory reset all works perfectly !
I have the same problem. I also noticed that instead of using assistant on push held it defaults to google search. That's why the keywords aren't working. I have factory reset my watch at least four times and the problem comes back after a couple of days. I am in English US and have switched it back and forth just for kicks. Has anyone had any luck?
edit: I also noticed my Talkback services are buggy and don't provide and example when I tap on the icon under the settings
joeanca said:
I have the same problem. I also noticed that instead of using assistant on push held it defaults to google search. That's why the keywords aren't working. I have factory reset my watch at least four times and the problem comes back after a couple of days. I am in English US and have switched it back and forth just for kicks. Has anyone had any luck?
edit: I also noticed my Talkback services are buggy and don't provide and example when I tap on the icon under the settings
Click to expand...
Click to collapse
Hello everybody,
As i've said it in my post above, a factory reset has resolved the problem and now Ok Google works perfectly !
BillalS3 said:
Hello everybody,
As i've said it in my post above, a factory reset has resolved the problem and now Ok Google works perfectly !
Click to expand...
Click to collapse
Did you actually take the time to read my post? I mentioned I have done that several times and the problem keeps coming back.
Hello joeanca
Yes I've taken time to read your post, and I don't understand why a factory reset don't resolve your problem. Because, for myself it resolves it.
Perhaps somebody else could have a new idea to help you
I have the same issue. Factory reset only fixes the issue for a few hours then it happens again (I think once they lose the connection between them (for example because of distance) and reconnect again. Factory reset also enables wi-fi again. The issue is that if the watch is connected only through Bluetooth with wi-fi closed, google assistant and play don't work , if you go in watch settings it says disconnected in Bluetooth but no "cloud" icon pops up at the screen and on phone Bluetooth settings it says connected furthermore the watch works perfectly like receiving notifications changes song track etc. Oh also the silence phone setting from android wear app doesn't work
I just had this problem and resolved it by dumb luck.
I originally synced two Google Accounts to my watch. After updating apps on the watch, OK Google detection hasn't worked.
I found that my default account in Google Assistant on my phone had changed from my primary account. I removed all but my primary account from the watch, and selected my primary account in Google Assistant. OK Google now works again on the watch.
Darkmage40 said:
[..]if you go in watch settings it says disconnected in Bluetooth but no "cloud" icon pops up at the screen and on phone Bluetooth settings it says connected furthermore the watch works perfectly like receiving notifications changes song track etc.[..]
Click to expand...
Click to collapse
This exactly my problem. The phone says it is connected and the watch works, but the Assistant only says it is offline and cannot understand me. That drives me crazy. I have only one account synced. This Thread is the only thread so far that has my exact problem in it. I know it is a little older, but is there anyone with an idea?
thx and regards
My issue is the Ok Google gets locked into a loop. Whatever the first command I speak to it after Ok Google.. it just loops. Be it What is the time, what day is, send a message, etc. it keeps looping on that command. only seems to affect my Huawei watch 2 classic. phone doesn't have the same issue. have rebooted watch. If i swipe the google assistant away and execute another command, it loops on that one. I have both Facer and Watchmaker watchface apps installed. an issue like this should not have been present in a beta stage so I have to wonder.. what could I have on my watch causing this?
--edit--
Well... it seems Wear 2.0 does NOT like more than one account on a watch. I had three accounts hooked to the watch. My phone's private account. My professional email account, and a purchases account. 3 accounts. Seems that just wasn't how it wanted to work things. As soon as I cut out the pro and purch accounts it starts acting right. I have one account that my android devices get to access for uniformity of data but nothing else gets to use it. I have several emails for various purposes.
So if you have more than one account, as others have found.. remove them down to a single account. Things will probably start working right.
And its back to looping. basically.. if I say Ok Google, then wait for the ready prompt and give it a command "Set an alarm" it will process that command, ask when I want the alarm for, but feed itself the "Set an Alarm" command, ask when, feed command back to itself, ask when... on and on.
Had the same problem. Deleting cache and data of Google app on the watch worked for me. OK google finally works, but I cannot send WhatsApp messages via ok Google, what worked a few days ago with manually starting google by press and hold the upper button.
With Google even talking back works now
i solved the ok googlo hotword problem by deleting chache and data of google app on my huawei watch 2 and it started working again
Related
My Nexus 7 2013 or FHD or whatever has been working great since day one. I was just now listing to some music, and put it on pause to speak with a co-worker. I just came back to my desk with the Nexus boot up logo showing. It took a very long time (3-5 minutes) for it to finish booting up.
After unlocking the tablet I'm greeted with "Google Play Services stopped working." Instead of loading NovaLauncher right away it it asks me if I want to launch the default launcher or NovaLauncher. Selecting Nova greets me with the default NovaLauncher layout--all of my icons and folders have been lost to the default. And I no longer have a PIN set or anything.
Poking around further it seems several other things have lost data. Swiftkey wants me to re-download the English layout and complete setup. All of the stock system apps want updates. And I keep getting pop ups saying Google Play Services has crashed.
What's really odd is when I want to bring this up on another forum someone else posted a very similar experience:
The Nexus 7 is great but my experience was short lived.
I don't know if it was a bad tablet or bad encryption but something seriously broke. I wanted to add my company email to my tablet and part of that process involves enabling encryption on my device. Everything was fine and running well, until I plugged it in for the night. At some point my Nexus rebooted and it was at the pre OS screen asking for encryption credentials. I thought that was weird but entered my info. It chugs along fine until it loads my lock screen where I immediately notice it no longer was asking for a PIN and my background changed back to the default. I go to my home screen and noticed my widgets weren't loading and I started getting error messages saying Currents and Play Store stopped responding. I try and access those apps but they go straight to a crash message.
I go ahead and factory reset it and when I tried to reapply the encryption it would go through the motions but it would never encrypt. I thought it was a bad reset and reset it again. Now it just hangs where it says Google and never boots up.
I ended up calling Google Support and I'm getting my Nexus replaced. Has anyone else experienced anything like this before?
Click to expand...
Click to collapse
I don't have encryption but I do have an exchange account added. There wasn't any remote wipe or anything. I haven't tried a factory reset yet but we'll see if I have the same issues the other person was having.
It's a little concerning to see someone else have almost the exact same thing happen. Makes me worried there's some defective memory out there. Has anyone else heard of this happening?
I've had some really strange experiences the last couple of days with my N7 as well. Bear with me as i try to explain.
I picked up my N7 after work yesterday and noticed the Fandango app had an update waiting. I tapped 'Update', and then went to check something in the Play app settings, and noticed the version was 4.2.9. When the Fandango app finished updating, i opened it up to check out some showtimes. After that i went back to the Play app, into the settings again, and noticed that the app version had been bumped up to 4.3.1. When i tapped the home button, the N7 locked up, and i couldn't do anything at all. I powered it down and attempted to reboot, but no luck. I could get as far as the boot animation, but no further, no matter how long i let it run, or how many times i attempted to reboot. The only thing that worked was to completely wipe everything via fastboot, reinstall 4.3, and start from scratch. I thought my problems were solved, as everything seemed to work fine once i got everything re-installed and configured again.
Until i came home from work today, that is.
Upon arriving home, i unlocked my N7 and was greeted by several dialog boxes indicating that both the stock calendar app and Currents had crashed. Neither app could be opened, as they'd immediately crash, and the stock launcher would also crash, even though i use Nova Launcher. I thought maybe uninstalling/reinstalling updates for Calendar, would help, but the Play Store would crash immediately and could not be launched. I went into settings>apps and tried uninstalling updates and clearing data for all three apps, but only the Play Store app seemed to benefit from this. Nothing seems to help Calendar or Currents. They won't sync or open, and i've also just noticed that the Gallery immediately force closes when i try to launch that, too. My Google Voice app, which i used last night with no problems whatsoever, had lost all its data and had to be reconfigured from scratch. I'm still going through the rest of my apps one at a time to see if there are problems with any of them, but so far all other Google apps are working properly.
I'm perplexed as to what the problem is. Software issue? Hardware issue? In any case, i'm calling Google Support to ask for a replacement, just to be safe. I'm hoping that the N7 i have now is just a lemon, and not indicative of more widespread problems.
I bought two, one works flawlessly (knock on wood) and the other one **** the bed after three days of use. I am returning it for a new one.
Sent from my Nexus 7 using xda app-developers app
I'm all setup to return this one, and not a moment too soon as it's acting even wonkier now. DashClock force closes, and i'm finding some apps have had their data erased, while others are working normally. Hopefully the replacement works as it's supposed to, because i'll be really annoyed if i have to go through three or four tablets before i get one that works.
I just had almost the exact same issue, opened SoundHound premium and the nexus 7(2103) crashed.
After like 5mins it boots up, with my google account deleted (with it all my paid apps), all the google apps updates and google services crashing.
and above all extremely slow.
I'm now re-registering my account, to see if ir returns to normal.
Sent from my Nexus 4 using xda premium
roy8000 said:
I just had almost the exact same issue, opened SoundHound premium and the nexus 7(2103) crashed.
After like 5mins it boots up, with my google account deleted (with it all my paid apps), all the google apps updates and google services crashing.
and above all extremely slow.
I'm now re-registering my account, to see if ir returns to normal.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Did you have an exchange account set up on the Nexus?
After this happened to me I wiped everything (I wanted to unlock the bootloader anyways) and things are going fine. If it happens again I'm going to exchange it.
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
Seem to come across a few few bugs since updating OTA yesterday.
1. Play Store just not opening on the watch. Previously it would say no network. After factory resetting again it says: error while retrieving information from server rh-01
2. Google assistant. Trying to message people in my contacts by saying their name not working very well. The same contacts that worked flawlessly previously don't work anymore. As I say my request, it all gets typed out word for word, just as I said. These match up to the way the contacts are written out, but google assistant repeatedly just asks: To Whom?
3. Watch vibrates but no notification seen till I swipe up. Otherwise I have no idea that there has been a notification.
4. On incoming notifications such as whatsapp, I don't always have a reply button available. Sometimes it decides I can reply, sometimes there's just no option at all.
Any solutions?
Thanks in advance
Does your google assistant speak? I can't seem to make it speak when talking to it. It does reply only on screen with text.
I noticed today that my Google Feed isn't updating. If I swipe left on my home screen I see my feed with cards but they are the same ones that been there for a long time. If I pull down to update I get a "Can't reach your feed at the moment" message and no cards show. If I lock the phone and unlock it I get the old out of date cards back but still nothing new.
I have also noticed that the weather isn't showing in the "At A Glance" widget on the home screen.
Anyone else seeing this? Any ideas on how to fix? I have restarted and cleared the cache of the Google app and neither have worked. The only other thing I can think of is going to Apps > Google > Storage > Manage Space > Clear All Data but clears search data, search history and feed settings which are used to populate the feed with relevant data. It would have to be set up again(sports teams, stocks, etc) and have rebuild search data which takes time. If that will fix the issue I'll do it but I'd hate to have it not fix the issue and have to start over for no reason.
Same issue here all day on my P2XL and on my wife's Pixel XL.
I found that If I disable the weather updates, my feed starts working again. So it looks like it has to do with the news and weather app. I tried to uninstall/reinstall it, didn't help.
I'm having the same issue. Interestingly though, if you uninstall the updates for the Google app, it works just fine.
Same issue with me too. Tried everything yet ain't working. Running 8.1 in pixel 2 xl
Seems like it's something related to weather updates from within google app, turns out if you disable it from "customize feed" your cards will be back to normal at the loss of weather info on the app and launcher. Glad I'm not alone tho
xtc_24 said:
Seems like it's something related to weather updates from within google app, turns out if you disable it from "customize feed" your cards will be back to normal at the loss of weather info on the app and launcher. Glad I'm not alone tho
Click to expand...
Click to collapse
Yeah glad that I'm not alone too. Let's see what happens.
I was also having this issue but it started working fine 5-10 min ago.
Sent from my Pixel 2 XL using XDA Labs
I ran into this exact issue with my regular pixel 2 about 1 hour ago. When i connected to my wifi i got a system notification saying my streaming service stopped for google (was confused what that meant) but after that my feed did not work. Weather was not showing up in the "at a glance" app as well. I tried to uninstall google app updates, deleted all data google app data, removed my google account and then re added it, and did multiple reboots while on mobile data and wifi. All efforts was not successful. I also was getting the error message "we cannot reach your feed right now" on the google app while the updates were uninstalled.
Having the same issue. Can't reach the feed since yesterday!
Same here, on Pixel 2XL for me and Pixel 2 for two of my friends. Weather doesn't show up in At A Glance widget, disabling it in the feed does nothing to the feed, and the phone doesn't react to "Hey Google", but only "Ok Google" despite retraining the voice model. There's a Reddit thread going on this https://www.reddit.com/r/GooglePixe...able_right_now_cant_reach_your_feed/?sort=new and I also spoke to Google Support at length, they've escalated this to their engineering team, since they have lots of reports of this today. They are asking everyone to send feedback from the Google Now app/feed with the screenshot -- that way they can determine the scope of who's affected
Uninstalled the updates and restarted... Now it works fine.
AZJeep4X4 said:
I'm having the same issue. Interestingly though, if you uninstall the updates for the Google app, it works just fine.
Click to expand...
Click to collapse
Yes, I noticed the same thing. Uninstalled the latest version and went back to the factory version and it works. Although, I did notice all the cards were very old items ( 7+ hours old) but I'm not sure if that's just because there really is nothing recent.
Of everyone who is having this issue how many are in the western United States (New Mexico, Nevada, Arizona)?
Hi all,
I have started experiencing the similar issue from today. Def has something to do with Google App update as in "What's New" section it does refer to changes to feed notification etc.
Things I have tried since I first started noticing the issue:
1. Phone restart.
2. Shut down phone, wait and restart
3. Clear data of Google App along side disabled/enabled app. (Ended up losing Google assistant setup and had to redo it)
4. Uninstalled Google App updates and restarted.
Only thing that has worked is that I have selected weather from feed settings and feed is back.
I have also sent feedback to Google with screenshots.
Cheers.
BeardedFaisal said:
Hi all,
I have started experiencing the similar issue from today. Def has something to do with Google App update as in "What's New" section it does refer to changes to feed notification etc.
Things I have tried since I first started noticing the issue:
1. Phone restart.
2. Shut down phone, wait and restart
3. Clear data of Google App along side disabled/enabled app. (Ended up losing Google assistant setup and had to redo it)
4. Uninstalled Google App updates and restarted.
Only thing that has worked is that I have U selected weather from feed settings and feed is back.
I have also sent feedback to Google with screenshots.
Cheers.
Click to expand...
Click to collapse
Let's see how'll Google solve this.
Same here. Moto x play
Oops...they did it again...Google has mastered the art of breaking what's working very well! They keep updating apps that only break many other dependent apps...I'm on the Pixel XL and it's feed seem to work when I remove the weather feed from it...looks like google messed up the weather service...
Back in business...
Is it fixed yet or still onn with the bug
9:45 PST and it's still not fixed. I believe there is a wide spread problem with Google and also PlayStation Network.
PSN has been wonky since Friday and Google in my area has been wonky since Saturday.
Hey folks,
at first i am really pleased with this phone but there is one problem that is giving me some headache.
At first startup i logged in with my google account and everything worked fine. now i have some apps that want me to grant in app authorization (eg pokemon adveture sync, bixby log in with google acc).
I can select my account in the window that opens and it goes to the next screen and then loads forever (see picture attached). I tried to delete and register my google account again, but the problem still exists. So it tried another google account and it works fine with it. I don't know what to try to fix this. Hope someone can help me with this.
Thanks in advance!
Have you disabled any packages?
I have only disabled "game launcher" and "one drive". Just tried if reenabling it solves the problem; it doesn't. Problem is still there.
Did you mean this by "packages" or do you mean something in my google account?
heildnix said:
I have only disabled "game launcher" and "one drive". Just tried if reenabling it solves the problem; it doesn't. Problem is still there.
Did you mean this by "packages" or do you mean something in my google account?
Click to expand...
Click to collapse
That's what I meant. Try making sure all second factor authentication methods are turned off for the account, at least temporarily.
rcobourn said:
That's what I meant. Try making sure all second factor authentication methods are turned off for the account, at least temporarily.
Click to expand...
Click to collapse
Tried to deactivate the second factor authentication. Still no change.
Tried the authorization thing on an older huawei a few days ago an it worked. Today tried again, the same problem on the huawei. Seems to me like the problem is on google's side.