Related
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
Hi all,
I'm running out of ideas and could use another opinion please:
N6 running 5.0.2 (this is the second one incidentally, I sent the first one back for this same problem) - the phone will shutdown under certain circumstances. When this happens it does not restart, you have to press the power button to restart it. Mostly this happens when I use the Google Camera stock application to take a photo but only ever when the phone is not connected to WiFi. I have had it happen when I open the camera app as well (without taking a picture), if you put your ear to the upper speaker as soon as the camera app is opened you can here a cell location signal (similar to the sound you hear when you put your phone near a speaker) and then the phone turns off. I can stop this happening by using a third party camera app. I can also stop this happening if I disable Google location.
Yesterday I wiped the phone, signed in with my Gmail, and took 25 pictures, all OK. I then turned on Google Now, took one photo and the phone turned off. This is definitely something to do with location data but I don't understand why nobody else is experiencing this ? Maybe the phone is faulty but I'm going to have a hard to explaining that as I sent the last one back for the same reason.
Any suggestions are greatly appreciated.
Thanks,
Simon.
Glad I'm not the only one having this issue. I've seen this happen on my N6 too, both on 5.0.x as well as on 5.1. I've seen this happen even while unlocking the phone (I have face unlock enabled), and yes this happens mostly when using the camera. Never knew it has to do something with location services.
I'm running completely stock and unrooted by the way. I guess I should try flashing the factory image
Yes same with me, stock phone unrooted and although using the camera is the best way to get this to happen you are right, it sometimes happens at other times as well. If I go to an area with no WiFi and poor phone signal I can get it to happen everytime the Google Camera app is opened, so I have to resort to taking pictures in Airplane mode.
This has happened to me since I have had this phone and its replacement and I am curious to know why, when you open the Google camera app, if you immediately put your ear to the upper speaker it becomes active for about 3 seconds ? After that three second burst of sound the phone will turn off. To me, it sounds like a location signal is being sent when the camera is opened.
Yet turning off geolocation?
Sent from my Nexus 6 using Xparent Skyblue Tapatalk 2
same thing happening here,i was out today and when i tried to open the camera app phone kept crashing,soon as i was home on wifi camera app worked fine,i've switched off the location thing to see if that helps
I've had my new Seat Leon for a week now and have been using Android Auto a little in this time. I really like it but it seems buggy. For example when using maps, the images will freeze, only updating every couple of minutes. When you are trying to follow an on screen map while travelling at 60mph, this can be very annoying. The other bug I seem to have is that my car seems picky when connecting to my phone (Nexus 5) sometimes. It will say 'not compatible' and will refuse to connect. The only way to solve these two issues is to restart my phone and sometimes to also toggle the USB debugging check box.
Is there anywhere to report bugs to Google? I'd like to help the community in ironing out these issues.
nimdy said:
Is there anywhere to report bugs to Google? I'd like to help the community in ironing out these issues.
Click to expand...
Click to collapse
Open the Android Auto app.
Tap the 3 dots at top right.
Select "Help & Feedback" and then select Feedback at the bottom.
I'm honestly not sure it will help too much though. There are no idle employees waiting for problem reports who spring into action at a new report.
But if Google sees 100 reports of Problem X, it might move X a bit higher in their priority list.
The freeze problem is actually new to Android Auto, and it started for me on July 31th. Google changed something server-side because even two clean installs didn't solve the issue, and it was working flawlessy until that day. No solutions found so far, had to switch to an iPhone to navigate. Read my report here:
http://forums.androidcentral.com/as...-5-android-auto-lags-when-using-gps-maps.html
themcfly said:
The freeze problem is actually new to Android Auto, and it started for me on July 31th. Google changed something server-side because even two clean installs didn't solve the issue, and it was working flawlessy until that day. No solutions found so far, had to switch to an iPhone to navigate. Read my report here:
http://forums.androidcentral.com/as...-5-android-auto-lags-when-using-gps-maps.html
Click to expand...
Click to collapse
That seems to be the same issue I'm getting. But strangely this isn't happening all the time. The pattern seems to be when I connect the phone to the car, set up the Google maps navigation, stop and disconnect the phone (for example getting lunch on my way into work), then connect again and continue the navigation. When connecting for the second time I get the issue whereby the refreshing doesn't seem to happen. As you say in your other forum post, this seems to update when you touch the screen.
Hopefully if this bug has only appeared in the last few days, hopefully someone will spot it and report back to get a fix. I've written a brief feedback note saying that I have found a bug and am interested to help them get it fixed!
I see a lot of people having problems with certain phones. I have Note Edge and never a problem. My wife has a s6 and used to have problems about 10 minutes into a drive (Black Screen, no control, most other probs mentioned here). Read somewhere if you load the "Android Auto App" on the phone first and then plug in. She has never had a problem Since. Something happens on App load that is not happening on "Auto Launch on detection" (My gut feeling is something to do with bluetooth). Just wanted to pass it along for those people having issues. I am sure google will fix at some point but give it a try and see if it solves your issues. It did ours.
nimdy said:
That seems to be the same issue I'm getting. But strangely this isn't happening all the time. The pattern seems to be when I connect the phone to the car, set up the Google maps navigation, stop and disconnect the phone (for example getting lunch on my way into work), then connect again and continue the navigation. When connecting for the second time I get the issue whereby the refreshing doesn't seem to happen. As you say in your other forum post, this seems to update when you touch the screen.
Hopefully if this bug has only appeared in the last few days, hopefully someone will spot it and report back to get a fix. I've written a brief feedback note saying that I have found a bug and am interested to help them get it fixed!
Click to expand...
Click to collapse
BPryde said:
My gut feeling is something to do with bluetooth.
Click to expand...
Click to collapse
Yes! If something fails with Bluetooth, then the AA connection disconnects. I hope Google fix this soon.
Hello there, I have a frustration with my Nexus 6 running 6.0.1
While there is similar probs around, none seem to explain mine.
When using Google Music on Bluetooth/Headset I get normal operation and then randomly (sometimes immediately, sometimes up to about 5 minutes) the volume drops down. The Volume slider still shows 100% volume.
I thought at first it was the ear-saftey thing we used to have where it does this, but then allows you to change it back to full volume. But I didn't get any message around that or cannot find a way to override it.
Then I thought it was another system process stealing focus and the phone getting confused, eg dropping volume for a notification and then just not returning it.
Tried rotating phone to see if it was a portrait/landscape bug
Everytime. I restart the phone, it's fine again before the random volume drop occurs 1 sec-5 mins after playing a song. Once it does it, it gets stuck that way.
I've lived with it for a long time but it's doing my head in now so hopefully someone can help it advise?
Not even sure if a factory reset will fix.
Cheers
Jansy said:
Hello there, I have a frustration with my Nexus 6 running 6.0.1
While there is similar probs around, none seem to explain mine.
When using Google Music on Bluetooth/Headset I get normal operation and then randomly (sometimes immediately, sometimes up to about 5 minutes) the volume drops down. The Volume slider still shows 100% volume.
I thought at first it was the ear-saftey thing we used to have where it does this, but then allows you to change it back to full volume. But I didn't get any message around that or cannot find a way to override it.
Then I thought it was another system process stealing focus and the phone getting confused, eg dropping volume for a notification and then just not returning it.
Tried rotating phone to see if it was a portrait/landscape bug
Everytime. I restart the phone, it's fine again before the random volume drop occurs 1 sec-5 mins after playing a song. Once it does it, it gets stuck that way.
I've lived with it for a long time but it's doing my head in now so hopefully someone can help it advise?
Not even sure if a factory reset will fix.
Cheers
Click to expand...
Click to collapse
Try a factory reset. Ive had it fix many a strange bug before.
Jansy said:
Hello there, I have a frustration with my Nexus 6 running 6.0.1
While there is similar probs around, none seem to explain mine.
When using Google Music on Bluetooth/Headset I get normal operation and then randomly (sometimes immediately, sometimes up to about 5 minutes) the volume drops down. The Volume slider still shows 100% volume.
I thought at first it was the ear-saftey thing we used to have where it does this, but then allows you to change it back to full volume. But I didn't get any message around that or cannot find a way to override it.
Then I thought it was another system process stealing focus and the phone getting confused, eg dropping volume for a notification and then just not returning it.
Tried rotating phone to see if it was a portrait/landscape bug
Everytime. I restart the phone, it's fine again before the random volume drop occurs 1 sec-5 mins after playing a song. Once it does it, it gets stuck that way.
I've lived with it for a long time but it's doing my head in now so hopefully someone can help it advise?
Not even sure if a factory reset will fix.
Cheers
Click to expand...
Click to collapse
I've had the same problem, running N developer preview 1 listening with wired headphones. I've learned that I just kind of have to wait for it to pass, try force stopping play music, or restart the phone.
Are you streaming your music, or is it downloaded onto your device? I manually copy music onto my phone from my computer, and this is when I've got the issue, as I stream with Spotify fairly often and never have the problem. I've always thought it was just some bug reading all of these crazy 3rd party audio files in the storage.
Hasn't been much of a problem for me... Just jumped at the opportunity to share when I saw this thread. If it bothers you that much, try a full wipe of internal storage and reinstall everything. Cheers! Hope I helped.
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?