Anyone else having inconsistent results with saying "OK Google" while the screen is off?
It seems to work fine when actively using the phone, but if I hit the power button to turn off the screen then it may (or may not) turn the screen on with the Assistant after saying "OK Google" (nothing happens).
I tried turning on fingerprint/pin security, but this will still sometimes not respond to the command. Additionally, it will also still sometimes ask me for a pin even though I have "Trusted Voice" enabled.
Not sure if it's a hardware issue or software related (again, everything works perfectly if the phone screen is already on and in use).
Always works for me. Maybe you can try to redo the voice recognition step that was done when the phone was set up.
Yea, I've tried retraining my voice but still with the same results. It will at times always work perfectly and other times will be as if it doesn't hear my voice at all. I don't have any new apps installed and I even did a factory reset. Leaning towards getting an exchange but part of me thinks it's software related.
I think I've run into this issue a few times, but may need to see if it keeps happening.
I think most of the time that it has happened to me is when signal is low. I think signal definitely plays a role since the server has to translate your voice (maybe). At least that's how I think software listens to your voice and recognizes it was you and what you were saying.
Were you in an area with weaker signal when trying to say ok google?
kinetic758 said:
Yea, I've tried retraining my voice but still with the same results. It will at times always work perfectly and other times will be as if it doesn't hear my voice at all. I don't have any new apps installed and I even did a factory reset. Leaning towards getting an exchange but part of me thinks it's software related.
Click to expand...
Click to collapse
I had the issue a couple times when I was experimenting with the feature. I think it is software related.
I think it is quite sensitive because as the warning goes "it can be a less secure method"
If I spam the fingerprint scanner it will say "too fast" and then require pin.
Sent from my sailfish using XDA Labs
ryken229 said:
Always works for me. Maybe you can try to redo the voice recognition step that was done when the phone was set up.
Click to expand...
Click to collapse
xShadoWxDrifTx said:
I think I've run into this issue a few times, but may need to see if it keeps happening.
I think most of the time that it has happened to me is when signal is low. I think signal definitely plays a role since the server has to translate your voice (maybe). At least that's how I think software listens to your voice and recognizes it was you and what you were saying.
Were you in an area with weaker signal when trying to say ok google?
Click to expand...
Click to collapse
I was not connected to wifi but the signal seemed fine. I'll keep an eye on it next time.
nednednerb said:
I had the issue a couple times when I was experimenting with the feature. I think it is software related.
I think it is quite sensitive because as the warning goes "it can be a less secure method"
If I spam the fingerprint scanner it will say "too fast" and then require pin.
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
The interesting thing is that it would also not work when I had no lock screen security on at all. In this case it just failed to turn on the screen and initiate the Assistant.
kinetic758 said:
The interesting thing is that it would also not work when I had no lock screen security on at all. In this case it just failed to turn on the screen and initiate the Assistant.
Click to expand...
Click to collapse
Hmm looking here
https://www.google.ca/search?q=ok+google+trusted+voice+not+working
It appears it is definitely a software issue that isn't singled out in the Pixel
Sent from my sailfish using XDA Labs
nednednerb said:
Hmm looking here
https://www.google.ca/search?q=ok+google+trusted+voice+not+working
It appears it is definitely a software issue that isn't singled out in the Pixel
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
Hm. But does "trusted voice" even matter if I've disabled all lock screen options? I thought it was only relevant if you had a pin/fingerprint set up (it was flaky with and without fingerprint for me).
kinetic758 said:
Hm. But does "trusted voice" even matter if I've disabled all lock screen options? I thought it was only relevant if you had a pin/fingerprint set up (it was flaky with and without fingerprint for me).
Click to expand...
Click to collapse
In my settings in appears "Trusted Voice" is about waking the screen when it is off and "unlocking" to home screen and assistant EVEN IF other security features are off.
In OK Google settings is where I see trusted voice and the settings to voice wake device. Security settings are a different section.
What happens when you turn all security off and decrypt your device so there is no pin or password whatsoever?
Sent from my sailfish using XDA Labs
nednednerb said:
In my settings in appears "Trusted Voice" is about waking the screen when it is off and "unlocking" to home screen and assistant EVEN IF other security features are off.
In OK Google settings is where I see trusted voice and the settings to voice wake device. Security settings are a different section.
What happens when you turn all security off and decrypt your device so there is no pin or password whatsoever?
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
I've added my work location as a "Trusted Location" (this is the place where OK Google seems to fail most of the time). It seems to be working better this way, but it's still a little too early to tell. If this doesn't work, then I'll try the tips you mentioned. Thanks again.
What is scary for me, is any time there is a Pixel commercial on TV and the guy says "OK Google", my phone wakes up. So quite the opposite from the OP experience. Actually scary from a security standpoint. The old Motos used to allow limited functionality via voice but not full unlock (smart idea). There should be a way to remotely disable voice detection if you lose your phone.
kinetic758 said:
I've added my work location as a "Trusted Location" (this is the place where OK Google seems to fail most of the time). It seems to be working better this way, but it's still a little too early to tell. If this doesn't work, then I'll try the tips you mentioned. Thanks again.
Click to expand...
Click to collapse
I did this and am still having sporadic issues with it not waking after "OK Google". It fails probably 1 in 10 times which was the same rate as before it was added as a Trusted Location.
dispatch said:
I did this and am still having sporadic issues with it not waking after "OK Google". It fails probably 1 in 10 times which was the same rate as before it was added as a Trusted Location.
Click to expand...
Click to collapse
I'm sorry to hear that. A little comforting to know I'm not the only one with this issue
A buddy of mine has a Pixel as well, and his responds to "OK Google" from sleep 99% of the time, so not sure if there's a difference in hardware tolerance with the mic (or whatever low power hardware they're using for "always on" listening), software, or if his voice is just easier for the phone to recognize.
Besides this issue, the phone is perfect (no scratches, no dead/stuck pixels etc), so I'm really on the fence about asking for an exchange.
I would consider a non-functioning "Hello Google" to be a benefit. The first thing I do on any Android device is remove as much as possible of Google's nasty Spyware, starting with the Google Now launcher and the "Hello Google" search.
Sent from my LG-D801 using Tapatalk
kinetic758 said:
I'm sorry to hear that. A little comforting to know I'm not the only one with this issue
A buddy of mine has a Pixel as well, and his responds to "OK Google" from sleep 99% of the time, so not sure if there's a difference in hardware tolerance with the mic (or whatever low power hardware they're using for "always on" listening), software, or if his voice is just easier for the phone to recognize.
Besides this issue, the phone is perfect (no scratches, no dead/stuck pixels etc), so I'm really on the fence about asking for an exchange.
Click to expand...
Click to collapse
I really don't think it's the hardware, but you never know. I don't yet have a large enough sample size to say if 1 in 10 is accurate in the long run or if it is truly closer to 1 in 100 that it fails to wake. I always assume we're beta testers for Google anyway so I have come to expect things like this.
aquatarkus said:
I would consider a non-functioning "Hello Google" to be a benefit. The first thing I do on any Android device is remove as much as possible of Google's nasty Spyware, starting with the Google Now launcher and the "Hello Google" search.
Click to expand...
Click to collapse
I waffle back and forth on immersing myself (and my data) with Google to get the benefits of their products. However, if you buy a Pixel, you should damn well know what you're getting yourself into, and I find that your device will be much less useful if you do what you say you do. As always though, to each their own.
dispatch said:
I waffle back and forth on immersing myself (and my data) with Google to get the benefits of their products. However, if you buy a Pixel, you should damn well know what you're getting yourself into, and I find that your device will be much less useful if you do what you say you do. As always though, to each their own.
Click to expand...
Click to collapse
This. I've embraced (at least for now) the fact that Google is collecting information about me. I've bought into it (also purchased a Google Home) with the hope that this will make my life easier (if slightly). A double-edged sword, for sure.
dispatch said:
However, if you buy a Pixel, you should damn well know what you're getting yourself into, and I find that your device will be much less useful if you do what you say you do.
Click to expand...
Click to collapse
I figure I'm smart enough not to need Google to run my life for me. I will first root the Pixel and remove the stuff I don't want. When a suitable version of CyanogenMod becomes available, I'll flash that into it, as it provides additional security/privacy controls.
Anyway, I hadn't meant to highjack this thread....
Sent from my LG-D801 using Tapatalk
kinetic758 said:
I've added my work location as a "Trusted Location" (this is the place where OK Google seems to fail most of the time). It seems to be working better this way, but it's still a little too early to tell. If this doesn't work, then I'll try the tips you mentioned. Thanks again.
Click to expand...
Click to collapse
Also try training the voice by saying Ok Google at 3 slightly different volumes and with varied pace. Do say it clearly each time. I found voice recognition doesn't work as well if I train it with a forced or monotone rhythm. Cos real voice is more fluid and not always the same.
Good luck
Sent from my sailfish using XDA Labs
Mine works every time.
This was never the case on the Nexus 6P.
The only time the Pixel DIDN'T wake up is when it was on low battery and save mode got enabled. I believe this disables the always listening feature of this app.
Sent from my Pixel using XDA-Developers mobile app
Related
ok so... with the phone on the table and the screen is off (standby). if i say "ok google" and do a search for anything. once im done i can hit the home button and it takes me right into home screen without inputting my finger print or password. So that means anyone can now say "ok google" and bypass any of the securities. come you guys confirm this as this is a major problem for me. I have the verizon edition pixel.
Audigy187 said:
ok so... with the phone on the table and the screen is off (standby). if i say "ok google" and do a search for anything. once im done i can hit the home button and it takes me right into home screen without inputting my finger print or password. So that means anyone can now say "ok google" and bypass any of the securities. come you guys confirm this as this is a major problem for me. I have the verizon edition pixel.
Click to expand...
Click to collapse
Settings>>Google>>Search & Now>>Voice>>OK Google Detection - In here you can set options to secure this feature to your liking. Notice the 'Trusted Voice' Option which detects its YOU before unlocking. There of course is room for error where someone sounding similar to you in might be able to get it. That's why these features are there to disable if it matters to you.
I personally don't care much..
Cheers!
(There might be a faster way to get to those settings. That's just how I always remember to do it)
And it also makes you acknowledge everything you just said before enabling trusted voice.... you must've missed that part.
i had a couple different people try this out. all the girls didnt allow access but some of the guys could gain access. i tried it on a friends lg v20 and it wouldnt allow access. i guess i have to deal with it. doesn't feel too good knowing someone can gain access with little to no effort. ill just turn that feature off if its even possible.
Audigy187 said:
i had a couple different people try this out. all the girls didnt allow access but some of the guys could gain access. i tried it on a friends lg v20 and it wouldnt allow access. i guess i have to deal with it. doesn't feel too good knowing someone can gain access with little to no effort. ill just turn that feature off if its even possible.
Click to expand...
Click to collapse
How long has your friend been using their V20? I know they become much more accurate the longer you use it, similar to the fingerprint scanner. Google has you train it to understand you with 3 sets of 'ok google' but that doesn't mean it's done learning. Give it some more time maybe? Just thinking...
hes been using it for 4 about a week now. the v20 is a nice. i feel it is noticeably faster than the note 7 i had. only issues are the screen it average. Its sharp but color is average. the hole phone vibrates from the speakers which is a downside for me.
Ill give the pixel some time to learn my voice and report back. hopefully i cant fool it lol
Try this
Audigy187 said:
i had a couple different people try this out. all the girls didnt allow access but some of the guys could gain access. i tried it on a friends lg v20 and it wouldnt allow access. i guess i have to deal with it. doesn't feel too good knowing someone can gain access with little to no effort. ill just turn that feature off if its even possible.
Click to expand...
Click to collapse
Press power button while Pixel is in sleep mode. That will bring up the lock screen. At the bottom of the screen you will notice a fingerprint icon. Tap that and you will get the message "Device will remain locked until you manually unlock."
No amount of saying "OK, Google" will allow access now until you either use the fingerprint scanner or enter your pass code.
Yea I pointed this out here: http://forum.xda-developers.com/showpost.php?p=69303648&postcount=12
It is a big issue. It should allow limited assistant functionality, but not entire phone.
as always, if you are so concerned about security on your phone, dont keep anything on it that you are afraid of someone else accessing..
very simple solution
wase4711 said:
as always, if you are so concerned about security on your phone, dont keep anything on it that you are afraid of someone else accessing..
very simple solution
Click to expand...
Click to collapse
Thats horrible.
Audigy187 said:
i had a couple different people try this out. all the girls didnt allow access but some of the guys could gain access. i tried it on a friends lg v20 and it wouldnt allow access. i guess i have to deal with it. doesn't feel too good knowing someone can gain access with little to no effort. ill just turn that feature off if its even possible.
Click to expand...
Click to collapse
km8j said:
Yea I pointed this out here: http://forum.xda-developers.com/showpost.php?p=69303648&postcount=12
It is a big issue. It should allow limited assistant functionality, but not entire phone.
Click to expand...
Click to collapse
Both of you! Turn "trusted voice" off
It is a setting in Google -> Search and Now -> voice -> and OK Google detection.
Turn off "trusted voice"
No more "GLARING SECURITY HOLES" in... Your knowledge of your phone.
Because, asking for limited functionality of Assistant when trusted voice is off doesn't sound right to me.... Like asking for AI to know which questions are answerable while screen is locked seems too tricky at this time.
The design is to use a lock or leave it off, currently.
Sent from my sailfish using XDA Labs
nednednerb said:
Both of you! Turn "trusted voice" off
It is a setting in Google -> Search and Now -> voice -> and OK Google detection.
Turn off "trusted voice"
No more "GLARING SECURITY HOLES" in... Your knowledge of your phone.
Because, asking for limited functionality of Assistant when trusted voice is off doesn't sound right to me.... Like asking for AI to know which questions are answerable while screen is locked seems too tricky at this time.
The design is to use a lock or leave it off, currently.
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
Well 1) the voice recognition isn't good 2) we want the functionality 3) the assistant could act on limited functionality: weather, reminders, send texts, make a phone call. If someone gets my phone and wants to manipulate a voice to send texts, whatever. This is how moto handled their voice assistant and it was perfect.
Oh this thread is now a feature request? It was about a security issue. Things can change.
Give Google feedback through "about phone" in settings! Maybe they will add the feature.
Sent from my sailfish using XDA Labs
Turn off trusted voice in Smart Unlock.
HeCareth said:
Turn off trusted voice in Smart Unlock.
Click to expand...
Click to collapse
Finally somebody with a smart answer...this controversy could all be avoided by a simple google search telling you how to disable the the trusted voice in smart lock, as the person states above. Im all about helping newbs out but research before you post...especially security stuff...... the title of you post makes it sounds as if there has been a security breach or major security flaw in the firmware.
Sounds about like the guy I sold a Gear 2 Neo too. I was showing him how to use some things and he freaked out when the Trusted Device feature left his phone without a passcode. So we disabled it, then he wanted to add a passcode to the watch to get get into it which really only works if it's disconnected from the phone. He was pretty honest about his reason. He's cheating on his wife and didn't want her to find out.
Sent from my Pixel using Tapatalk
Janker5050 said:
Finally somebody with a smart answer...this controversy could all be avoided by a simple google search telling you how to disable the the trusted voice in smart lock, as the person states above. Im all about helping newbs out but research before you post...especially security stuff...... the title of you post makes it sounds as if there has been a security breach or major security flaw in the firmware.
Click to expand...
Click to collapse
It is a security flaw if you can get through it with someone else's voice easily.
km8j said:
It is a security flaw if you can get through it with someone else's voice easily.
Click to expand...
Click to collapse
When I click on it in settings it tells me directly that it can be "less secure."
Yep. So it is not a flaw. It is a feature.
You should feel informed by the warning in settings, not like "it doesn't work.."
It is a fact more voices are similar and voices are easier to mimic than... Fingerprints. Rhythm and pitch are easy to steal. Ever hear of a cover band? Or confuse yourself which band you're listening to because of singer? If never... Wow dude.
Sent from my sailfish using XDA Labs
Maybe I am missing a setting somewhere or something, but the Google Assistant on my XZP only responds when the screen is on. I have it set to "any time" in the Assistant settings. Is this normal? I'm pretty sure it worked whenever (screen off/locked/charging/etc.) on my last couple of phones. I'd like it to at least work while the phone is charging.
Any ideas?
well yeah I had the same problem, apparently, Google changed the settings of the program, and it was only working while the phone is charging, so whenever u upgrade the application to its latest version you will lose this privilege. my advice and that's what I'm doing is to uninstall the updates from the google app and then give it all the permissions it needs and you will have it to work anytime the phone is charging no matter if the screen is on or off !!
btw my Google app version is 7.2.26.21.arm64
This is something that I absolutely hate about the Google assistant. Google should allow the assistant to be used regardless of the device being locked or charging like you can with Siri and Cortana (on WM). It's so irritating to have to actually turn my screen on to use the Google assistant.
Sent from my SGP511 using Tapatalk
Jake_09 said:
This is something that I absolutely hate about the Google assistant. Google should allow the assistant to be used regardless of the device being locked or charging like you can with Siri and Cortana (on WM). It's so irritating to have to actually turn my screen on to use the Google assistant.
Sent from my SGP511 using Tapatalk
Click to expand...
Click to collapse
Yeah, once the phone is in my hand I don't really need the assistant. I can do it myself...
Heinous said:
Yeah, once the phone is in my hand I don't really need the assistant. I can do it myself...
Click to expand...
Click to collapse
Exactly. It's really pointless to have an assistant that requires me to interact with the phone. It's like Google doesn't understand what an assistant is for. I really wish they would also implement what Cortana does in terms of how she handles text messages when connected to Bluetooth devices. I love that she would ask if I want her to read it to me and then after reading it will ask me if I want to dictate a reply and send it.
Honestly, for some of the flak that I've seen Cortana getting lately, she's a much better and much more useful assistant than Google or Sri and she's probably the thing I miss the most from WM10.
Sent from my G8141 using Tapatalk
Jake_09 said:
Exactly. It's really pointless to have an assistant that requires me to interact with the phone. It's like Google doesn't understand what an assistant is for.
Click to expand...
Click to collapse
It's not sure it's entirely Google's fault. It worked properly on previous android phones that I've owned.
I just noticed that it seems to work now with the Oreo update. My phone now wakes up and responds to "ok, Google" while the screen is off/locked. ?
This is by far the best part of the Oreo update. Google Assistant is at least 800x more useful now that it is actually hands-free.
Doesn't work wih mine. It blinks like I could say somehing, but stays closed. When I unlock it, nothing happens. My old phone then went into the assistant mode.
Which options do i have to set?
Like in title, my screen, sometimes is being white fors a while(like less than 1 sec),like opening an app, but nothing opens and then phone work fine. What to do, what it is? Is it virus?
Fadamaka7 said:
Like in title, my screen, sometimes is being white fors a while(like less than 1 sec),like opening an app, but nothing opens and then phone work fine. What to do, what it is? Is it virus?
Click to expand...
Click to collapse
I'm getting the same thing, mostly when playing a game. Will flash for a split second. Not sure what's causing it.
I don't think it's a virus tho.
Maybe its problem with system or launcher? I haven't found anything like that on internet or how to slove this
Mine is doing the same thing as well. I think at least for me it's because my RAM is getting close to making out.
Same problem
I have the same problem. Has anyone got any hints at least? It's very annoying and no other phone seems to have it.
kikikakakuku said:
I have the same problem. Has anyone got any hints at least? It's very annoying and no other phone seems to have it.
Click to expand...
Click to collapse
I'm having the same issue. Screen goes kinda white for half a second and looks as it would start an app, but then goes back to what app you just had opened.
It is not a constant flickering or flashing, as reported from Samsung and other Devices and which is documented via Videos on the Net.
It would be hard to film it, as I haven't been able to reproduce thus behaviour.
When I play a game (King of Avalon) and when I'm just typing and that issue occurs, the typed text is gone. Luckily it doesn't happen while typing on WhatsApp or other apps with text features.
A while back it was almost gone, but then came back, without me having changed the app Setup.
I will reset the phone and see, if it comes back.
I still think it's an issue brought up from apps that use the GPU a lot.
Have tried different settings the Developer Options from Android (Disable HW-Overlay,...) but it didn't help.
Will report, once I have resetted, but will take a while, until I have time for testing.
Sent from my HTC U11 life using Alien Technology
Hey, I also had this problem, it helped me change the language in voice search to English and turn off "ok google". I use the phone in a different language and I also had it in voice search.
Hello fellow HTC u11 life friends -
I found this thread by Googling, so hopefully others will find it too. I have also been having this very annoying problem for several weeks. Can't remember when exactly it started. Was it after an Android update?
This problem appears to be related to the Google app settings on the phone, as the previous poster suggested. When I read his post, I went to the Google app settings (Setting --> Apps --> Google) and didn't see anything out of the ordinary, but I noticed that there is a setting called Display over other apps. This was set to "yes" by default, so I changed it to "no". Since I made this change yesterday, I have not had the white screen flash once.
It seems like the Google app is being triggered briefly for whatever reason and then closing. By not allowing the app to display over others, if the app is triggered, you won't get that brief white screen like the app is about to open. At least, that's what I think. Fingers crossed the fix holds. I hope this works for others. Let me know!
jdanisse said:
Hello fellow HTC u11 life friends -
I found this thread by Googling, so hopefully others will find it too. I have also been having this very annoying problem for several weeks. Can't remember when exactly it started. Was it after an Android update?
This problem appears to be related to the Google app settings on the phone, as the previous poster suggested. When I read his post, I went to the Google app settings (Setting --> Apps --> Google) and didn't see anything out of the ordinary, but I noticed that there is a setting called Display over other apps. This was set to "yes" by default, so I changed it to "no". Since I made this change yesterday, I have not had the white screen flash once.
It seems like the Google app is being triggered briefly for whatever reason and then closing. By not allowing the app to display over others, if the app is triggered, you won't get that brief white screen like the app is about to open. At least, that's what I think. Fingers crossed the fix holds. I hope this works for others. Let me know!
Click to expand...
Click to collapse
Before I call you a genius, I still have to wait a bit (and of course hoping)
I just turned off different things in the Google App "show notification for ***"
In this case *** was for Price Alert, stocks alert, sports alert and so on.
Furthermore I disabled the "display over other Apps" as well.
I could imagine that this latter feature doesn't have to be turned off completely, rather than turning off all those useless alerts for stuff I've never even looked for.
Will try to go the next days to see, if that blinking is gone and if soy trying to activate the feature with almost no alerts in order to determine, what the exact culprit is.
Disabling the feature totally might do it, but if for example some alerts were useful, then it would be nice, if at least they worked out as supposed to.
Will keep you guys posted.
Fingers crossed ^^
Sent from my HTC U11 life using Alien Technology
ucomix said:
Before I call you a genius, I still have to wait a bit (and of course hoping)
I just turned off different things in the Google App "show notification for ***"
In this case *** was for Price Alert, stocks alert, sports alert and so on.
Furthermore I disabled the "display over other Apps" as well.
I could imagine that this latter feature doesn't have to be turned off completely, rather than turning off all those useless alerts for stuff I've never even looked for.
Will try to go the next days to see, if that blinking is gone and if soy trying to activate the feature with almost no alerts in order to determine, what the exact culprit is.
Disabling the feature totally might do it, but if for example some alerts were useful, then it would be nice, if at least they worked out as supposed to.
Will keep you guys posted.
Fingers crossed ^^
Sent from my HTC U11 life using Alien Technology
Click to expand...
Click to collapse
Did turn off not only for Google but silenced many other apps as well, but still flashes.
Just deactivated "Display over other Apps" in YouTube. Maybe that helps.
Will report, if that helped.
Sent from my HTC U11 life using Alien Technology
If any of you are using Dark Knight, it's specific to that room. I'm using twin famous sick Oreo and I don't get the flash
Hi, after google update flashing comback, so i disable "OK Google enrollment" in applications system and it helped. Maybe you can just turn off the notifications, i dont know, you can try
Popakawe said:
Hey, I also had this problem, it helped me change the language in voice search to English and turn off "ok google". I use the phone in a different language and I also had it in voice search.
Click to expand...
Click to collapse
Tried this method and so far (1h) no flashes. Sounds reasonable, that Google is trying to send some notices to the screen and that functionality is somehow bugged. I'm fine with turning off ok, Google. Have never used it anyway. [emoji28]
Sent from my HTC U11 life using Alien Technology
---------- Post added at 12:41 PM ---------- Previous post was at 12:32 PM ----------
ardaz87 said:
If any of you are using Dark Knight, it's specific to that room. I'm using twin famous sick Oreo and I don't get the flash
Click to expand...
Click to collapse
Had to think at least 3 times which kinda "room" you meant, and why a room should affect a smartphone [emoji848] Then I got it rom != room [emoji16]
Sent from my HTC U11 life using Alien Technology
The white screens interval increesed and taking foto's was sometimes difficult because white screens passed by a few times per taking a foto.
Now I received 8.1 and no white screens till now (20h)
EugeneP1969 said:
The white screens interval increesed and taking foto's was sometimes difficult because white screens passed by a few times per taking a foto.
Now I received 8.1 and no white screens till now (20h)
Click to expand...
Click to collapse
Are you using the built in Camera, or some app?
I got 8.1 too but no changes. Have to admit I'm using Google Cam Port. Might be that, because otherwise I've turned off kinda all notifications, but it's still flashing.
As mentioned earlier, I should do a full wipe and use the built in cam and such, but I don't really like it.
I'll see, when I find the time to wipe and set it up again...
Sent from my HTC U11 life using Alien Technology
ucomix said:
Are you using the built in Camera, or some app?
I got 8.1 too but no changes. Have to admit I'm using Google Cam Port. Might be that, because otherwise I've turned off kinda all notifications, but it's still flashing.
As mentioned earlier, I should do a full wipe and use the built in cam and such, but I don't really like it.
I'll see, when I find the time to wipe and set it up again...
Sent from my HTC U11 life using Alien Technology
Click to expand...
Click to collapse
I am using the built in Camera. Two days 8.1 and not a single white flash. Before the update 8.1 I had it not only with the camera app but very random. I hope you will find a solution. I found it very annoying.
EugeneP1969 said:
I am using the built in Camera. Two days 8.1 and not a single white flash. Before the update 8.1 I had it not only with the camera app but very random. I hope you will find a solution. I found it very annoying.
Click to expand...
Click to collapse
I really have no clue, which app causes those issues. Will try the built-in cam for testing.
If it still persists, I really have to reset the phone.
Thx. I'll find a way and yes, it's pretty much annoying
Sent from my HTC U11 life using Alien Technology
ucomix said:
I really have no clue, which app causes those issues. Will try the built-in cam for testing.
If it still persists, I really have to reset the phone.
Thx. I'll find a way and yes, it's pretty much annoying
Sent from my HTC U11 life using Alien Technology
Click to expand...
Click to collapse
Please, go to setting - apps and notifications - see all - show system, and find "Ok google enrollment" then disable it, please tell me if its help i'm very curious
Popakawe said:
Please, go to setting - apps and notifications - see all - show system, and find "Ok google enrollment" then disable it, please tell me if its help i'm very curious
Click to expand...
Click to collapse
After 4 days a minor white flash returns during scrolling for apps in the app store. I immidiately implemented the above quoted solution and since then no white flash. :fingers-crossed: :fingers-crossed:
Popakawe said:
Please, go to setting - apps and notifications - see all - show system, and find "Ok google enrollment" then disable it, please tell me if its help i'm very curious
Click to expand...
Click to collapse
Just turned it off. Didn't think about the system processes before.
Will report, if anything changed. Thx for that hint so far, sounds promising
Sent from my HTC U11 life using Alien Technology
My wife and I both have a pixel 3 and there are numbers times when the assistant is not triggered by saying "ok Google" or "hey Google" while the screen is off. There have even been a few times when it won't respond when the screen is on. Does anyone else have this issue?
And yes, we have retrained the voice recognition.
Yes I've had the same issue. Not sure what helped in the end. Maybe a phone restart? or reinstalling the google search app?
PuffDaddy_d said:
My wife and I both have a pixel 3 and there are numbers times when the assistant is not triggered by saying "ok Google" or "hey Google" while the screen is off. There have even been a few times when it won't respond when the screen is on. Does anyone else have this issue?
And yes, we have retrained the voice recognition.
Click to expand...
Click to collapse
georgs_town said:
Yes I've had the same issue. Not sure what helped in the end. Maybe a phone restart? or reinstalling the google search app?
Click to expand...
Click to collapse
Had the same issue 2 days ago on my P2XL. A cache and data wipe of the google app fixed it :good:
Badger50 said:
Had the same issue 2 days ago on my P2XL. A cache and data wipe of the google app fixed it :good:
Click to expand...
Click to collapse
Thanks, that worked for now....
PuffDaddy_d said:
My wife and I both have a pixel 3 and there are numbers times when the assistant is not triggered by saying "ok Google" or "hey Google" while the screen is off. There have even been a few times when it won't respond when the screen is on. Does anyone else have this issue?
And yes, we have retrained the voice recognition.
Click to expand...
Click to collapse
Personnaly I've noticed I have to yell the word in order for the phone to wake up. I first thought it was wrongly configurated and wiped the app data several time, until I figured the pixel was a bit deaf..
Aanze said:
Personnaly I've noticed I have to yell the word in order for the phone to wake up. I first thought it was wrongly configurated and wiped the app data several time, until I figured the pixel was a bit deaf..
Click to expand...
Click to collapse
I have noticed that Google Assistant been buggy during last few days. Clearing storage and cache does help but even when its back working sometimes it has issues making the registered action. For, example, setting alarm/timer gets registered (the text appears in google assistant but google assistant is sometimes slow to read the registered command + even after google assistant repeats the command and says its done the actual action does not following, meaning the alarm/timer is not set and only on second try it gets through. Never had similar issues before. Not sure if its google app or December update, but I did not have any issues before.
No issues with things like Weather reports and reminders though..
PuffDaddy_d said:
My wife and I both have a pixel 3 and there are numbers times when the assistant is not triggered by saying "ok Google" or "hey Google" while the screen is off. There have even been a few times when it won't respond when the screen is on. Does anyone else have this issue?
And yes, we have retrained the voice recognition.
Click to expand...
Click to collapse
This kept happening to me last week. My phone was on battery saver which did not turn off automatically after charging. Had to toggle the battery saver and do a restart to have OK Google work somewhat reliably.
jemeljsh said:
I have noticed that Google Assistant been buggy during last few days. Clearing storage and cache does help but even when its back working sometimes it has issues making the registered action. For, example, setting alarm/timer gets registered (the text appears in google assistant but google assistant is sometimes slow to read the registered command + even after google assistant repeats the command and says its done the actual action does not following, meaning the alarm/timer is not set and only on second try it gets through. Never had similar issues before. Not sure if its google app or December update, but I did not have any issues before.
No issues with things like Weather reports and reminders though..
Click to expand...
Click to collapse
I thought this was just a glitch, but my wife's old phone did this right before we upgraded to the Pixel 3. She burned the food in the oven because the timer didn't get set even though the assistant confirmed the command.
Maybe we should start saying please and thank you before the machines rise against us.
I was able to use accessibility settings on my OG Pixel and Pixel 3 to enable a confirmation beep when Google Assistant has been activated (after I say "OK Google") but I can't seem to find a way to do that on my Pixel 7 Pro. Can anyone help?
You have to enable "switch access" in accessibility settings.
lsirg said:
You have to enable "switch access" in accessibility settings.
Click to expand...
Click to collapse
I've done this on my OG Pixel and Pixel 3 but it doesn't seem too be working on my Pixel 7 Pro.
I've done it twice now, first setup, and again after a factory reset. Worked both times. Strange.
lsirg said:
I've done it twice now, first setup, and again after a factory reset. Worked both times. Strange.
Click to expand...
Click to collapse
I'm using a Verizon P7 Pro. How about you?
bobo-the-drunk said:
I'm using a Verizon P7 Pro. How about you?
Click to expand...
Click to collapse
Unlocked P7 Pro.
Also here it is not working to enable switch access...
In Google Assistant settings through the Google app you go to accessibility and the options are there and working for me. Not sure if they've recently moved or been changed but I've never used whatever switch access is.
Can confirm that you have to have both of the settings enabled in the screenshot above in order to hear a beep. I don't even have voice active enabled.
JakeDHS07 said:
In Google Assistant settings through the Google app you go to accessibility and the options are there and working for me. Not sure if they've recently moved or been changed but I've never used whatever switch access is.
Click to expand...
Click to collapse
bobbarker2 said:
Can confirm that you have to have both of the settings enabled in the screenshot above in order to hear a beep. I don't even have voice active enabled.
Click to expand...
Click to collapse
Nobody's ever mentioned that setting before but I already had that enabled. I get a confirmation beep when I'm using Bluetooth or Android Auto but not when it's just my phone.
I screwed mine up recently. The above settings were set before, and I've gotten a beep since I got it. Post-screwup, I tried accessibility settings to no avail. Things that were changed beforehand (perhaps - new P7P and I've been both tinkering around and busy - plus I sometimes plug in a DAC and use Neutron Player, which is very possessive. So I can't recall when I noticed the lack of a beep precisely within a day's usage).
So, things that might have affected it:
I allowed Google Assistant to access my screen, and I enabled flash screen when it does so.
I upgraded from the December to January patch.
I upgraded, afterwards, with the small Play Store patch.
I enabled... what's it called - verbal shortcuts like "Answer" that don't require "Hey Google" first. <- Given that Google's reason for zapping the beep was to save response time, I'm suspicious of this, but I've changed quite a bit, so further testing is required.
I'll post if I get the beep back.
***What follows isn't necessary to the topic.***
It's daft that this is even an issue that can't be solved simply with a toggle. Or better, actually asking Assistant to reply when summoned with a beep or phrase, perhaps "Yes, Sir?" In an era with ChatGPT, we ought to be able to at least choose efficient or chummy. Google knows more about me than most friends, they could at least be friendly about it.
[I'm using an unlocked P7P from Google. I'm on Verizon with an eSIM. I have Assistant set so that it's constantly listening. And I've generally got things set to try out everything no matter how intrusive. Hey - it's the first phone I've actively chosen since my Note 4; I wanted to see what we've been given for all that's been taken away. I'm disappointed at all the features that ought to be helpful to my aged father, but are too difficult to use for someone intelligent that can't learn new things well. I'm also seeing just how vastly intrusive it is while saying, carefully, that it isn't. GrapheneOS may be in my future - perhaps because I simply can (goodbye forever, dedicated Verizon phones).]
Just tried Hey Google and ok Google. Both produced the same result, the Google Assistant pops up without a beep.
schmeggy929 said:
Just tried Hey Google and ok Google. Both produced the same result, the Google Assistant pops up without a beep.
Click to expand...
Click to collapse
Yeah mine's been that way for awhile