Database Develop

[Q] Google Now reminders gone crazy for anyone else?

Starting last night, setting Google Now reminders is no longer working correctly. I'll issue a command to set a reminder at some time in the future (like "remind me to do something at 9am tomorrow"), the screen that comes up has the right date/time, then when I say "yes" to confirm, the confirmation screen that comes up has the reminder for three hours earlier than I asked for (6am). I can reproduce this 100%. This was working fine earlier in the week. If I issue a command to set up a reminder in 15 minutes from now, same thing, it gets set for three hours in the past on the final confirmation screen and says "this reminder is in the past". I'm on an unlocked Moto X, 4.4.3.
Thought it was just me, but it's now happening to my wife as well, she's on a locked Moto X (AT&T), 4.4.2.
I Googled around as much as I could and couldn't find anyone else having this specific problem. Can anyone confirm that this is/is not happening to them?

Make sure your date and time settings are set to automatic or, if not, make sure the correct date, time, and time zone are correct. I think may have a problem there. I just used google now to set an alarm in 15 minutes and set a reminder for 8:00 am tomorrow and they are both correct. (T-Mo, 4.4.3, unlocked)

Groid said:
Make sure your date and time settings are set to automatic or, if not, make sure the correct date, time, and time zone are correct. I think may have a problem there. I just used google now to set an alarm in 15 minutes and set a reminder for 8:00 am tomorrow and they are both correct. (T-Mo, 4.4.3, unlocked)
Click to expand...
Click to collapse
That's the first thing I checked, on both affected phones, settings are correct. Thanks for the tip though. The strange thing is that the first GN screen shows the correct date/time, but the confirmation screen that comes up after you confirm the reminder has the wrong time.

rsage said:
That's the first thing I checked, on both affected phones, settings are correct. Thanks for the tip though. The strange thing is that the first GN screen shows the correct date/time, but the confirmation screen that comes up after you confirm the reminder has the wrong time.
Click to expand...
Click to collapse
Wipe cache and data for google search under settings->apps then log back in to Google Now, see if anything changes.
I can't reproduce the behavior you described unfortunately so I have no way of troubleshooting it on my end.

scorpion667 said:
Wipe cache and data for google search under settings->apps then log back in to Google Now, see if anything changes.
I can't reproduce the behavior you described unfortunately so I have no way of troubleshooting it on my end.
Click to expand...
Click to collapse
Just tried it, no luck.
Another interesting find: when it asks for confirmation of the reminder date/time, if I say "yes", it sets it for three hours earlier which is then displayed on the confirmation screen. However, if I click the on-screen button to confirm the reminder date/time (instead of saying "yes"), then the alert is set for the correct time.
And again, this is happening on two different Moto X's running two different versions of Android...

Did you move recently?
Sent from my XT1060 using XDA Premium 4 mobile app

bqw371 said:
Did you move recently?
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No, been in the same house for over 10 years. Haven't been out of my time zone in over a year...

If your rooted try uninstalling google search, reboot, then reinstall google search from play store.
Also check your calendar apps (stock any any 3rd party) to see if any manual time zone issues are there. Since no one else can reproduce it, its probably something on your device.
Sent from my XT1060 using XDA Premium 4 mobile app

sfetaz said:
If your rooted try uninstalling google search, reboot, then reinstall google search from play store.
Also check your calendar apps (stock any any 3rd party) to see if any manual time zone issues are there. Since no one else can reproduce it, its probably something on your device.
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tend to agree with you, except that the same problem started affecting my wife's phone on the same day. Other than both being on AT&T, she's stock 4.4.2 and I have an unlocked DE with 4.4.3. Both using stock calendar, time zones are correct. I'll try uninstalling GS but that won't be an option for her.

Same Issue
I have the same issue, reminder is getting set 3 hours prior to the time I specified.

Even worse
mine is same but worse...it sets the reminder 12:30 hrs before the mentioned time...i tried at 11:00 p.m. ..it gets set at 10:30 a.m. :crying:

same here...
I have pretty much the same problem and I think I kind of understand what is happening...
Ok, when I set the reminder by voice on Google Now, say "remind me to check the oven in 20 minutes" he will do just that, until now everything is going smoothly, but then it asks me "do you want to set it?" and when I reply "yes" it reloads the screen and then, for some reason I can't understand, the clock now shows 4 hrs late... It will even show me a message "this reminder is in the past"...
So, it happens on the reload, every time it reloads the remainder's clock is set back 4 hours. If I say just "remind me in two hours" it will set the clock correctly, but as soon as it asks me "what is the reminder?" and I say "check my pizza" it will reload the clock back 4 hrs, and finally when it asks me if I want to set it and I say "yes" it reloads again and sets me back another 4 hours for a total of 8 hours...
Note that if after you ask google to set it, you just click "remind me at this time" (set it manually with your thumb) it will not reaload and therefore never get a chance to alter the time of the reminder...
It is a very weird problem.... I wonder if anyone will be able to shed some light on it.
My device is a Galaxy Nexus running android 4.3, and it is rooted.
Thanks in advance

kth7 said:
I have pretty much the same problem and I think I kind of understand what is happening...
Ok, when I set the reminder by voice on Google Now, say "remind me to check the oven in 20 minutes" he will do just that, until now everything is going smoothly, but then it asks me "do you want to set it?" and when I reply "yes" it reloads the screen and then, for some reason I can't understand, the clock now shows 4 hrs late... It will even show me a message "this reminder is in the past"...
So, it happens on the reload, every time it reloads the remainder's clock is set back 4 hours. If I say just "remind me in two hours" it will set the clock correctly, but as soon as it asks me "what is the reminder?" and I say "check my pizza" it will reload the clock back 4 hrs, and finally when it asks me if I want to set it and I say "yes" it reloads again and sets me back another 4 hours for a total of 8 hours...
Note that if after you ask google to set it, you just click "remind me at this time" (set it manually with your thumb) it will not reaload and therefore never get a chance to alter the time of the reminder...
It is a very weird problem.... I wonder if anyone will be able to shed some light on it.
My device is a Galaxy Nexus running android 4.3, and it is rooted.
Thanks in advance
Click to expand...
Click to collapse
Well, sorry it's happening to you, but I now know I'm not the only one (I was starting to question my own sanity).
Yes, what you describe is exactly what I described in the first page of this thread - confirming with voice causes the problem which is then evidenced on the reload of the confirmation screen, but confirming by clicking the on-screen button sets the time appropriately. Thanks for confirming. Unfortunately, I have no idea how to correct the problem. I reported it on the Moto X users forum on Motorola.com, but you confirmed it's not specific to the Moto X, which is useful information.
Also, this does seem to be a fairly recent problem, at least for me - this was working fine earlier last week.

Same issue as well
Got the same thing happening on both my Moto X and Nexus 7. -3 hour time difference.

i have confirmed the same issue with Moto G...me and my friend both have this issue on X and G...the reminder sets 12 hours/12 and half hours in the past...so it seems to be a Google problem and i guess it has something to do with the time zone..

Me too have this problem on moto x. Mine is an Indian one.
When i say - remind me to check game in 20 mins, lets say the time is 7 40 pm, it displays correctly the time as 8 00 pm.. But when i say yes as confirmation, the page reloads with time as 7 20 am.
Tried with time setting as network and manual time.. Both has this issue..
Sent from my XT1052 using XDA Free mobile app

I was able to create the problem with the voice confirmation of a reminder. My reminders step back one hour. I'm in the Mountain time zone, so it resets my time to Pacific time. If you are in Central time do you reset 2 hours? East time zone resetting 3 hours?
Edit: 'Set alarm for 1 pm today' works fine. It looks like just the reminders are messed up.

problem is...
Yes, the time is "set back" only once it reloads, and every time "google voice" has to reload it is "set back" again.
To me it is clear it is a google problem, likely a problem in the integration between "google voice" and "google calendar". Maybe?
---------- Post added at 04:29 PM ---------- Previous post was at 04:24 PM ----------
Groid said:
I was able to create the problem with the voice confirmation of a reminder. My reminders step back one hour. I'm in the Mountain time zone,
so it resets my time to Pacific time. If you are in Central time do you reset 2 hours? East time zone resetting 3 hours?
Click to expand...
Click to collapse
UTC -3 here and the time is reset 4 hours.
And yes, the problem occurs after voice confirmation, but more precisely after google now refreshes the page.

Exact same issue
I believe this is a Google now issue and not specific to the device model.
I tested it out on my brother's Moto-X and also on two other Nexus 5 phones and the result was same, the reminder was set back by 12 hours and got set in the past.
From India, GMT +5:30.
Hopefully google resolves this bug soon.

It's also happening on my Galaxy S5. I have to add 3 hours to any spoken reminder request (EDT). Hopefully it gets resolved soon.

"Ok Google" Toast

Does everyone get the "Ok Google" toast every time they wake their watch up? Mine never used to do it until a few hours ago.

czonin said:
Does everyone get the "Ok Google" toast every time they wake their watch up? Mine never used to do it until a few hours ago.
Click to expand...
Click to collapse
mine shows it as well, i don't remember it ever not being there though, but maybe because i've been using the x firmware since i got the watch?

czonin said:
Does everyone get the "Ok Google" toast every time they wake their watch up? Mine never used to do it until a few hours ago.
Click to expand...
Click to collapse
Mine has stopped doing it. First, it didn't do it. Then I had to do a reset and after repairing I did get the toast. Now it's stopped doing again!
Who knows?

Mine did it when I first got the watch, but now it's stopped showing the toast.
OK Google still works, just no toast as a reminder.
I think it shows the toast to explain how to use it, but only for a while before assuming that you know it by then
Sent from my XT1039 using Tapatalk

[Q] Any Way To Stop "OK Google" Showing On Screen?

Is there any way to stop "OK Google" showing up on the watch face? I don't use the "Speak" function and would really like to have a clean watch face.
Cheers.
Si

http://forum.xda-developers.com/showthread.php?t=2972318

Tonio78370 said:
http://forum.xda-developers.com/showthread.php?t=2972318
Click to expand...
Click to collapse
Don't know how I missed that. I tried doing what it said but it reappears when I bring the watch out of dimmed mode.
Many thanks.

Managed to get rid of it by saying "OK Google" a few times. I guess it hangs around initially as a reminder just until you get used to it.

[Q] Ok Google activates on random spoken sounds

After the recent update of the "Google" app version to v4.1.24.1672412.arm I was presented with new settings within Google Now and I decided to activate the "Ok Google" hotword detection on any screen on or off. Since then I noticed that the hot word activation occurs at random times when I am just talking normally to someone and it will start recognizing what I am saying (no mention of "ok google") or if I am in subway (NYC) listening to music or just using my phone and the subway stop announcement comes on and it will activate (this has been happening fairly consistently). Any random spoken voices of other people.
I am not sure why this is occuring, I even re-trained my voice a few times but it still continues to occur. Anyone else experience something similar ?
Note: Nexus 6 is completely stock not rooted or even bootloader unlocked.

intothevoid said:
After the recent update of the "Google" app version to v4.1.24.1672412.arm I was presented with new settings within Google Now and I decided to activate the "Ok Google" hotword detection on any screen on or off. Since then I noticed that the hot word activation occurs at random times when I am just talking normally to someone and it will start recognizing what I am saying (no mention of "ok google") or if I am in subway (NYC) listening to music or just using my phone and the subway stop announcement comes on and it will activate (this has been happening fairly consistently). Any random spoken voices of other people.
I am not sure why this is occuring, I even re-trained my voice a few times but it still continues to occur. Anyone else experience something similar ?
Note: Nexus 6 is completely stock not rooted or even bootloader unlocked.
Click to expand...
Click to collapse
I've been experiencing this to but only when I'm driving in my truck with the radio on.

neopolotin75 said:
I've been experiencing this to but only when I'm driving in my truck with the radio on.
Click to expand...
Click to collapse
Good to know I am not the only one!

Delete the app Data , start fresh.

Dxtra said:
Delete the app Data , start fresh.
Click to expand...
Click to collapse
Yeah I did that this morning to see if it happens again. It has been ok so far.

Happens to me a lot while I am giving training and the training was in Arabic ?
Sent from my Nexus 6 using Tapatalk

OK Google - very poor functionality

I've just upgraded from Pixel XL to Note8 and mostly I am very pleased, but for the very disappointing lack of proper implementation of Google Now/Assistant.
When the screen is off, I say OK Google, and the screen comes on ready for my command. Then I ask something and I get "Can't reach Google at the moment." This is absolute nonsense. I am sitting at my desk, 1m from my fibre optic router and I get 60mb download speeds. I am also connected to 4g from my desk, and if I run any app using the net, it works fine. I always get my emails, WhatsApp, Duo, Allo etc... so no problem there.
Other variations, things that sometimes happen:
1/ "OK Google" with screen off - the phone makes it's listening sound, but the screen stays off, then a minute later when I switch the screen on manually, I get the answer to my question!
2/ "OK Google" with screen off - the phone makes two sounds, the listening one then the cancelling one almost simultaneously
3/ "OK Google" with screen of - no response at all.
Anyone know what is going on here?
Thanks,
Mark.

fredphoesh said:
I've just upgraded from Pixel XL to Note8 and mostly I am very pleased, but for the very disappointing lack of proper implementation of Google Now/Assistant.
When the screen is off, I say OK Google, and the screen comes on ready for my command. Then I ask something and I get "Can't reach Google at the moment." This is absolute nonsense. I am sitting at my desk, 1m from my fibre optic router and I get 60mb download speeds. I am also connected to 4g from my desk, and if I run any app using the net, it works fine. I always get my emails, WhatsApp, Duo, Allo etc... so no problem there.
Other variations, things that sometimes happen:
1/ "OK Google" with screen off - the phone makes it's listening sound, but the screen stays off, then a minute later when I switch the screen on manually, I get the answer to my question!
2/ "OK Google" with screen off - the phone makes two sounds, the listening one then the cancelling one almost simultaneously
3/ "OK Google" with screen of - no response at all.
Anyone know what is going on here?
Thanks,
Mark.
Click to expand...
Click to collapse
they broke ok google about a year ago, very sad.

SOLUTION!
Hello again all.
After much searching, I tired something suggested back in 2015 by someone... an obvious suggestion, but not something EE tech support or Samsung had suggested.
Go to Settings>Apps>Google
Then go to Storage
Clear Cache
Clear Data
Reboot.
The suggestion was to try force close Google app, but that would not work, I tried a few times, but then just cleared Cache and Data, rebooted and it works perfectly, just like my Pixel XL
Woo hoo!!
Mark.

fredphoesh said:
Hello again all.
After much searching, I tired something suggested back in 2015 by someone... an obvious suggestion, but not something EE tech support or Samsung had suggested.
Go to Settings>Apps>Google
Then go to Storage
Clear Cache
Clear Data
Reboot.
The suggestion was to try force close Google app, but that would not work, I tried a few times, but then just cleared Cache and Data, rebooted and it works perfectly, just like my Pixel XL
Woo hoo!!
Mark.
Click to expand...
Click to collapse
This doesn't work for me. Even after clearing cache and data, rebooting, starting Assistant and running through the setup again, I get the same behavior with the screen off, a message that says "Can't reach Google at the moment."

I had this problem, disabled Bixby, works properly now.
Sent from my SM-N950U using Tapatalk

Liface said:
This doesn't work for me. Even after clearing cache and data, rebooting, starting Assistant and running through the setup again, I get the same behavior with the screen off, a message that says "Can't reach Google at the moment."
Click to expand...
Click to collapse
Check that your battery saving modes are not killing the Google app from running in the background. This is the most likely scenario, that the app isn't running at all.

Mine get borked every time I toggle between power saving modes. I like to use Extreme power saver for overnight and Medium mode at work.
Medium mode straight up breaks OK Google. Not sure if this is by design or a bug, but it just will not hear me.
Coming out of either mode (and extreme is the worst) and neither "Hi Bixby" or "OK Google" work until I do another full reboot. Sometimes I have to reboot then go back into Google voice setting to switch the option back on manually. If I try to do this before the reboot the option is greyed out and I can't move it. Sometimes just the reboot is enough.
It's random as hell and extremely annoying. I have submitted the bug to Samsung via the feature in the Samsung Members app, but that was over two weeks ago and has seen no response.

Interesting post. My wife's OK Google voice doesn't work but mine does. Both USA T MO version. With works I'm referring to having the Google widget on home screen and saying the sentence OK Google. Mine responds and hers doesn't. With screen ON.
Sent from my SM-N950U using Tapatalk

fredphoesh said:
Check that your battery saving modes are not killing the Google app from running in the background. This is the most likely scenario, that the app isn't running at all.
Click to expand...
Click to collapse
That's not it, I rarely use battery saving mode and this happens 100% of the time.

Ok google for me just does not work.

Anyone get a fix for this?
"Ok Google" works when screen is on, but if I say it while the screen is off, it makes the noise and I get edge lighting indicating it's listening, however it doesn't respond and when I manually turn on the screen assistant is open saying "can't reach Google at the moment."
Power saving mode is off, tried disabling Bixby, clearing cache, nothing.

Hellothere37 said:
clearing cache, nothing.
Click to expand...
Click to collapse
so clearing cache of Google app and rebooting did not help at all?
bizarre, that fixed it for me...
I have a UK version.
I'd phone Samsung!

I'm frustrated too because I can't figure out how to use it while in power saving mode. I thought I added it correctly in the optimized battery usage apps (disabled google, ok google enrollment and voice assitant there). I can't see it as an option to select under unmonitored apps. Any idea what I'm missing?
Thanks for any help

This is strange to hear. Mine has worked flawlessly, as good as my pixel XL. Screen off and locked or not. I say ok Google, phone unlocks, and then I ask it whatever. Only thing ive done is disabled bixby by way of BK disabler.
Sent from my SM-N950U using Tapatalk

May be coincidental but I have not the slightest problem, and yeah, I uninstalled the Bixter. One thing I have read somewhere or other is that the OK Goog command is also subject to the level you set for Bix. In other words with sensitivity turned down for Bix it's also turned down for Goog. I never tested that one but might be worth looking at...

gingi999 said:
they broke ok google about a year ago, very sad.
Click to expand...
Click to collapse
So two things I wanted to mention the first one was my old phone case actually covered one of the microphone holes. Meaning the cut-out wasn't there so I used a drill and made a hole and it fixed part of the problem.
I have to be honest with you the Note 8 solved all the OK Google problems that I was having the past. For example the lockscreen didn't used to work and it works now I mean it was really a piece of trash with my Galaxy S7 Edge and now I can't imagine living without it.

Having problems like the first post where google assistant/ok google is non responsive all around. I've noticed that if I clear cache and data it falls back to just "ok google" and it work all the time. If I activate the google assitant with ok google it fails immediately. Who can fix this?