"okay Google always on" turns itself back off, lollipop - Sprint Galaxy Note 4 Q&A, Help & Troubleshooting

I've tried it with s voice both on and off. when I first turn it on after a reboot, it doesn't train the voice model, but it says it's on but doesn't work. It then turns itself off, and trying to turn it on results in the voice model training opening , then saying it completed successfully, then turning its self back off.
Help?

No one else has experienced this?

To shut it off...i think thats what u looking for?
Go to Google. .sertings...voice, then turn off voice detection
Sent from my SM-N910P using Tapatalk

same thing on mine, its grayed out and I've heard there is no fix for it yet.

Bloodgroup said:
same thing on mine, its grayed out and I've heard there is no fix for it yet.
Click to expand...
Click to collapse
Mine looks gray to me..but it still slides to shut off.

Mine too. Is anyone on stock kernel?

Gotta disable S voice

fatboypup said:
Gotta disable S voice
Click to expand...
Click to collapse
I disabled it. Works now thanks

ibcenu said:
To shut it off...i think thats what u looking for?
Go to Google. .sertings...voice, then turn off voice detection
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I'm trying to turn it on, but it turns it's self back off with no explanation. physically moves the slider back to the off position before my eyes. It's gone back to just being grey now, though
fatboypup said:
Gotta disable S voice
Click to expand...
Click to collapse
If you read the original post, it says I've tried with s voice and without

This really isn't unique to Lollipop, as it does this exact thing on mine which is still on kitkat. Sometimes I will hear the tone acknowledging the ok google, but will immediately hear another tone. Often the screen doesn't even turn on. Even more often it just never works, although it works pretty perfectly with the screen on.
It has nothing to do with disabling svoice, although it probably is related to Samsung's implementation of svoice. Once in a while, thE phone will fail to even acknowledge an ok google request, only to sometime later say, "if you're trying to say something I didn't get that." This seems to imply the microphone is locked in the listen position, but isn't working.

Related

Galaxy Nexus notification light with light flow

I am really really happy that the galaxy nexus has a notification light. That was the thing preventing me from moving on from my nexus one.
Of course I wish Google would make the notification light more customizable because as it stands its really worthless by default.
I'm using light flow to help but its not perfect. Maybe its just not ready for ics yet or I'm doing something wrong but these r the problems I'm encountering:
In Google talk when I type a message and the screen goes off, the notification light comes on as if the person has responded but its being triggered by my own message. The only way I've been able to help with this is to hit menu>end chat after typing my message.
The other issue is with Google voice. I don't see a notification light up for it. Do any of you know if the paid version of the app will do it for Google voice?
Thirdly it doesn't seem to stop the sounds from the notifications in the night time mode...it turns off the light, but even though in that option I have it set to do the sound as well, it doesn't do it. I had to go into the sound settings and just turn off the notification sound (which actually didn't help, I had to go into each apps settings and turn it off there).
Sent from my Galaxy Nexus using XDA App
The Light Flow developer is here on XDA. He's replied in a thread on the app forum. Perhaps your answers lie there:
http://forum.xda-developers.com/showthread.php?t=1360090
Personally, I have the paid app and it has been hit and miss for me on ICS... sometimes I can't get the light to go away unless I FC the app. I uninstalled it for now until the niggles get smoothed out.
souja9 said:
sometimes I can't get the light to go away unless I FC the app. I uninstalled it for now until the niggles get smoothed out.
Click to expand...
Click to collapse
I was having same problems - light won`t stop flashing even after I checked received sms or missed phone call. Had to uninstall app But once its fixed, I will be first to install it - fantastic!
Anyone else know if there's any other app that can configure the lights?
I've bought a few over the years for my other devices but haven't tried any for Galaxy Nexus yet.
I've noticed though in Google Voice, when I get a text, the light is green.
I used light flow for a bit. but killed at after a day or so. Its still a little buggy in ICS as others have said
i had the proble with the light not turning off too. I had to turn off the notification light for no signal and low battery, and its been perfect since then.
I guess knock on wood, but I have never had a problem with the light staying on with Lightflow paid version.. I feel like if you swipe to dismiss a text message, it will stay on, but if you just open the Messaging app, it will stop blinking. Also, if you use the "x" on the notifications window, it will stop blinking without opening Messaging.
Edit:
With regards to the above post, I have never had the "no signal" light on, but I do have "low battery" and it works fine.
Strange, my problem is actually the opposite to you guys. With light flow my notifications clear just fine, every time. However, it seems like about half the time it refuses to notify me at all. Drains a bit of battery too.
ksc6000 said:
I am really really happy that the galaxy nexus has a notification light. That was the thing preventing me from moving on from my nexus one.
Of course I wish Google would make the notification light more customizable because as it stands its really worthless by default.
I'm using light flow to help but its not perfect. Maybe its just not ready for ics yet or I'm doing something wrong but these r the problems I'm encountering:
In Google talk when I type a message and the screen goes off, the notification light comes on as if the person has responded but its being triggered by my own message. The only way I've been able to help with this is to hit menu>end chat after typing my message.
The other issue is with Google voice. I don't see a notification light up for it. Do any of you know if the paid version of the app will do it for Google voice?
Thirdly it doesn't seem to stop the sounds from the notifications in the night time mode...it turns off the light, but even though in that option I have it set to do the sound as well, it doesn't do it. I had to go into the sound settings and just turn off the notification sound (which actually didn't help, I had to go into each apps settings and turn it off there).
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
I'm working on improvements for ICS. There's a few things I'm working on for a release in the next few days.
Firstly, at the moment gtalk just doesn't work correctly for identifying notifications due to changes in the gtalk app. I've pretty much rewritten the notification detection for gtalk now and it seems to be working fine in the test builds.
There's a bug I've fixed where for some people the app won't work after a reboot.
As for swiping away notificatons, that won't clear them. It's really frustrating that the accessibility service is so limited in this regard and won't report anything useful back on what's happened. Because of this, I'm adding a new option to clear notifications additionally when you pull down the notification bar as this is something I've managed to hook into. Therefore it'll clear when you either open the app, or pull the notification bar down (but will then be off even if you don't actually view the notification)
I've had a few crash reports (thanks to those who send them in) that I've been trying to fix also, but some of these can take a few iterations to completely stop.
As for battery use, after the next market release adding the above, I'm going to try and add a new feature to just display the most recent notification that's come in. Although it wouldn't be my personal choice, it'll use less battery than the notifications where it's changing in succession around all the notification colors.
---------- Post added at 01:14 PM ---------- Previous post was at 01:12 PM ----------
As for the sounds not stopping, have you set the native app to "silent" for it's notifications. Just want to see if it could actually be the main app that's triggering the sound.
---------- Post added at 01:15 PM ---------- Previous post was at 01:14 PM ----------
The paid version of the app also supports google voice.
I'm having a really bad issue where once the screen is off, I can't get it to turn back on. The only way to get it on is to reboot the phone via ADB. Then, once I turn it off, it stays off again. If I press the power button SOMETIMES it will flash my lock screen for a 10th of a second, but then turn back on. This started when I installed the app. I was able to test the LED colors, and it did that during the test, too. Hopefully it's an easy fix!
agreenbhm said:
I'm having a really bad issue where once the screen is off, I can't get it to turn back on. The only way to get it on is to reboot the phone via ADB. Then, once I turn it off, it stays off again. If I press the power button SOMETIMES it will flash my lock screen for a 10th of a second, but then turn back on. This started when I installed the app. I was able to test the LED colors, and it did that during the test, too. Hopefully it's an easy fix!
Click to expand...
Click to collapse
i got this problem too, turn off foreground, uninstall, install, turn off foreground, turn on. You should be good to go then. App is a bit buggy, but better than what google is currently offering us.
No dice
The good news though is that I can get my phone to work again by entering an ADB shell, entering "su", running a "ps" to list the running processes, then running "kill (proc number here)" to end the process, allowing me to turn my screen back on.
EDIT: Ok, so after killing the process using the method listed above, I re-entered the app, turned the "run in foreground" off, then turned it back on, then rebooted. Phone seems to be ok now.
agreenbhm said:
No dice
The good news though is that I can get my phone to work again by entering an ADB shell, entering "su", running a "ps" to list the running processes, then running "kill (proc number here)" to end the process, allowing me to turn my screen back on.
Click to expand...
Click to collapse
hmmm i have the app running almost perfectly on my phone right now too...thats what I did...are you rooted running stock 4.0.2?
agreenbhm said:
I'm having a really bad issue where once the screen is off, I can't get it to turn back on. The only way to get it on is to reboot the phone via ADB. Then, once I turn it off, it stays off again. If I press the power button SOMETIMES it will flash my lock screen for a 10th of a second, but then turn back on. This started when I installed the app. I was able to test the LED colors, and it did that during the test, too. Hopefully it's an easy fix!
Click to expand...
Click to collapse
You can also pull the battery if you want. There are several of us that have had this issue with light flow. The developer has stated that he is working on a fix. I would suggest removing the app until there is a confirmed solution.
Smokeey said:
hmmm i have the app running almost perfectly on my phone right now too...thats what I did...are you rooted running stock 4.0.2?
Click to expand...
Click to collapse
Yes, stock 4.0.2 rooted...for now.
cam30era said:
You can also pull the battery if you want. There are several of us that have had this issue with light flow. The developer has stated that he is working on a fix. I would suggest removing the app until there is a confirmed solution.
Click to expand...
Click to collapse
Yea, battery pull works too, but considering how finicky the battery cover of the GN is, plus the case i have, it's easier to adb reboot or kill the process.
See my above edit, though. I seem to have gotten it to work.
Guessing root is needed for this to work?
JaydenR said:
Guessing root is needed for this to work?
Click to expand...
Click to collapse
Yup, that's correct.
agreenbhm said:
Yup, that's correct.
Click to expand...
Click to collapse
Was wondering why it wouldn't work for me.
agreenbhm said:
Yup, that's correct.
Click to expand...
Click to collapse
Its working fine for me, and im not rooted yet.
artemis92 said:
Its working fine for me, and im not rooted yet.
Click to expand...
Click to collapse
I stand corrected; app description says root is not needed. I was thinking of another app I saw that does similar functions that requires root.

[Q] anyone having problems during calls like i am?

so pretty much im laying down talking on the phone and during the call all of a sudden the other person cant hear me, i can hear them but they cant hear me. so at first i thought its the signal, but i have full bars. then i turned off the option where if you place your phone facing down that itll mute, but the problem continues. so today i noticed that when that happens, i leave the phone where it is, press the speaker option and it works! so it isnt the signal! can any body tell me if its a setting im missing or is it something i should take it back to the att store?
are you sure the screen is shutting off? perhaps your cheek is hitting the mute/unmute icon (speaker icon)?
Ive had this exact problem for the last year with my s4. Always assumed it was something with the gyro inside. Its really annoying
m_reyna_16 said:
so pretty much im laying down talking on the phone and during the call all of a sudden the other person cant hear me, i can hear them but they cant hear me. so at first i thought its the signal, but i have full bars. then i turned off the option where if you place your phone facing down that itll mute, but the problem continues. so today i noticed that when that happens, i leave the phone where it is, press the speaker option and it works! so it isnt the signal! can any body tell me if its a setting im missing or is it something i should take it back to the att store?
Click to expand...
Click to collapse
I faced the same problem once, last week. But I just ignored it, imagining it would be something to do with bad network. I should try to simulate the issue again and see if it's persistent..
Maybe try turning off the motion options in the settings? I turned those off right when I got the phone and I haven't had this issue.
xlr8shun said:
are you sure the screen is shutting off? perhaps your cheek is hitting the mute/unmute icon (speaker icon)?
Click to expand...
Click to collapse
To be honest ive wondered that myself, but even tho i havent checked, last night when it occurredto me to try and press the speaker button to see if it will work (which it did) it did not have the mute button pressed... so because of last night, id have to go with no, it isnt pressed and the screen is black
blastedbilly said:
Ive had this exact problem for the last year with my s4. Always assumed it was something with the gyro inside. Its really annoying
Click to expand...
Click to collapse
Did u investigate for any issues like that online?
phoenix2241987 said:
I faced the same problem once, last week. But I just ignored it, imagining it would be something to do with bad network. I should try to simulate the issue again and see if it's persistent..
Click to expand...
Click to collapse
Let me know if it happens again
whoamanwtf said:
Maybe try turning off the motion options in the settings? I turned those off right when I got the phone and I haven't had this issue.
Click to expand...
Click to collapse
No, loke i said... that feature was turned on then i turned it off having the same effect
So anyone know a fix or know if i should take it to att for a replacement ?
issue I'm having is odd...I think it correlates to Bluetooth, but still working with advanced tech support. when I change towers, whether I receive or make a call, the phone drops all connection and says "out of service area". then comes right back. seems better without Bluetooth, but still happens. tech has no answers yet. already replaced sim twice and registered phone several times.
EDIT: I turned on the UTMS HD Voice using the hidden diagnostic menu and after 5 test calls today, no drops. Not sure if it is coincidence or something else...
Experiencing call issues too
m_reyna_16 said:
so pretty much im laying down talking on the phone and during the call all of a sudden the other person cant hear me, i can hear them but they cant hear me. so at first i thought its the signal, but i have full bars. then i turned off the option where if you place your phone facing down that itll mute, but the problem continues. so today i noticed that when that happens, i leave the phone where it is, press the speaker option and it works! so it isnt the signal! can any body tell me if its a setting im missing or is it something i should take it back to the att store?
Click to expand...
Click to collapse
I've also been experiencing similar issues, 2 issues in particular
1. During a call, I suddenly can't hear the other person or they suddenly can't hear me and I have to end the call and call back
2. I attempt to place a call, it rings and then when the other party picks up I hear nothing, they hear nothing. I sometimes have to call twice or three times before there's a successful call and I hear them and them hear me.
These issues occur randomly, with and without bluetooth. I've tried factory resetting the phone but the problem has continued.
I purchased my phone from Amazon.
IT Rider said:
issue I'm having is odd...I think it correlates to Bluetooth, but still working with advanced tech support. when I change towers, whether I receive or make a call, the phone drops all connection and says "out of service area". then comes right back. seems better without Bluetooth, but still happens. tech has no answers yet. already replaced sim twice and registered phone several times.
EDIT: I turned on the UTMS HD Voice using the hidden diagnostic menu and after 5 test calls today, no drops. Not sure if it is coincidence or something else...
Click to expand...
Click to collapse
I've used that menu but when clicking on the UMTS option nothing happens? How'd you select anything? Thanks
brittoking said:
I've used that menu but when clicking on the UMTS option nothing happens? How'd you select anything? Thanks
Click to expand...
Click to collapse
I didn't notice any sound difference when setting the UTMS HD Voice to "enabled". Did you see the two options for "enable/disable"?
IT Rider said:
I didn't notice any sound difference when setting the UTMS HD Voice to "enabled". Did you see the two options for "enable/disable"?
Click to expand...
Click to collapse
Yea I found them last night, I'd missed them somehow before. I have it enabled but haven't noticed anything as far as being more clear or a specific icon on the screen. I remember having seen another thread on this, maybe it was in the Verizon forum, that stated the UTMS was not even the right network option to enable the HD though? Does anybody know for sure?

Butt Dialing Sister

Purchase an OP3 for my sister when they were 1st released. For some reason, her phone frequently butt calls me. I can never get a straight answer from her what she is doing when it happens, but today she said her phone was just sitting in her purse. Can anybody think of what feature/setting/option she may have toggled on or off that is causing this? I believe she is on unrooted stock 3.2.7. Thanks
singlebyte said:
Purchase an OP3 for my sister when they were 1st released. For some reason, her phone frequently butt calls me. I can never get a straight answer from her what she is doing when it happens, but today she said her phone was just sitting in her purse. Can anybody think of what feature/setting/option she may have toggled on or off that is causing this? I believe she is on unrooted stock 3.2.7. Thanks
Click to expand...
Click to collapse
Turn on the pocket mode and probably ask her to put a password on her phone.
bonham1988 said:
Turn on the pocket mode and probably ask her to put a password on her phone.
Click to expand...
Click to collapse
To top it off, I think she has "Proximity Wake" also turned on. That will really cause issues in a purse...LOL
singlebyte said:
To top it off, I think she has "Proximity Wake" also turned on. That will really cause issues in a purse...LOL
Click to expand...
Click to collapse
Haha yes. Its a useful feature if your phone is usually on a desk otherwise it can be pretty annoying feature.
Sent from my OnePlus3 using XDA Labs
I just ran a styrofoam cup over my phone with proximity wake enabled and it woke up my phone, so depending on if it's stored during commuting around like pocket or purse, it's quite likely that's the culprit. Other user's suggestions would be a good call
Well, I tried the solutions recommended here but they did not work.
To recap,
1. Turned on Pocket Mode
2. Turned off Proximity Wake
These two setting did not solve problem. Any other suggestions to keep OP3 from Butt dialing?
Finger print lock screen security
daviss101 said:
Finger print lock screen security
Click to expand...
Click to collapse
Yes, we have that turned on.

Screen won't turn on for incoming calls

Hi. I bought the Note 8 (Verizon) last week, and everything seemed fine, but then 2 days ago the screen simply won't turn on when I have an incoming call. The phone rings, but the screen won't come on. I have to unlock the phone, and swipe down the notification bar just to answer the call. I've googled around but can't find an answer to this issue for this particular phone. Any suggestions/ideas?
Maybe give a factory reset a go.
moralesd66 said:
Maybe give a factory reset a go.
Click to expand...
Click to collapse
I was actually forced to do a hard reset this morning. The phone would NOT come on, no matter what I tried, couldn't even go into Safe Mode. Problem still persists. I'm actually thinking of exchanging it since I'm within the 14 day period.
tdetroit said:
I was actually forced to do a hard reset this morning. The phone would NOT come on, no matter what I tried, couldn't even go into Safe Mode. Problem still persists. I'm actually thinking of exchanging it since I'm within the 14 day period.
Click to expand...
Click to collapse
Hard reset....As in power off and on right? Try booting into recovery mode and deleting cache and data.
tdetroit said:
Hi. I bought the Note 8 (Verizon) last week, and everything seemed fine, but then 2 days ago the screen simply won't turn on when I have an incoming call. The phone rings, but the screen won't come on. I have to unlock the phone, and swipe down the notification bar just to answer the call. I've googled around but can't find an answer to this issue for this particular phone. Any suggestions/ideas?
Click to expand...
Click to collapse
My TMO one did that today, heard it ringing but screen remained off.
Sent from my SM-N950U using Tapatalk
I've now performed 2 factory resets, disabled AOD (for testing) and kept it on for other tests...same outcome. The screen will not come on when I have an Incoming call.
tdetroit said:
I've now performed 2 factory resets, disabled AOD (for testing) and kept it on for other tests...same outcome. The screen will not come on when I have an Incoming call.
Click to expand...
Click to collapse
You tried removing the screen protector and case?
Sent from my SM-N950U using Tapatalk
Maybe the setting for proximity...in pocket...turn off
Limeybastard said:
You tried removing the screen protector and case?
Sent from my SM-N950U using Tapatalk
Click to expand...
Click to collapse
I've tossed the screen protector after 1 day because it kept making a clicking sound on the top corner. No case on it.
BlueFox721 said:
Maybe the setting for proximity...in pocket...turn off
Click to expand...
Click to collapse
Tried that-no change. It's hard to believe that this phone has pretty much everything going for it...except turning on the screen for an incoming call.
tdetroit said:
Tried that-no change. It's hard to believe that this phone has pretty much everything going for it...except turning on the screen for an incoming call.
Click to expand...
Click to collapse
Factory reset , if no go , replacement.
Sent from my SM-N950U using Tapatalk
3 Factory Resets later, booting into Safe Mode, not downloading ANYTHING else, same scenario. Verizon is shipping a replacement to my house, I should have it by Tuesday. The Tech at the Verizon Store actually called my phone so I could show him the lack of screen activation. He said he's never seen this before either.
FIGURED IT OUT! Settings--Display&Lights--Turn off double tap to wake-up to solve issue! ...
This was set somehow, I disabled that and now my phone properly lights up for calls and I can actually answer them.
tdetroit said:
3 Factory Resets later, booting into Safe Mode, not downloading ANYTHING else, same scenario. Verizon is shipping a replacement to my house, I should have it by Tuesday. The Tech at the Verizon Store actually called my phone so I could show him the lack of screen activation. He said he's never seen this before either.
Click to expand...
Click to collapse
they know absolutely **** about anything
I never use retail store
Another way to fix this is to call yourself on another phone while your Note 8 screen is on. When the call comes in, don't answer but slide down the notification bar and you will see your call. Adjust notifications to not block/be silent.
tdetroit said:
FIGURED IT OUT! Settings--Display&Lights--Turn off double tap to wake-up to solve issue! ...
This was set somehow, I disabled that and now my phone properly lights up for calls and I can actually answer them.
Click to expand...
Click to collapse
I went into Settings, Display, but nothing about double tap to wake-up. Samsung runs on AMOLED and that function is on other screens like Sony Xperias.
I do notice another thing going into Notifications settings and I see that the Phone app is Muted. I don't know how to get out of it.
The solution is the person who posted above. You call yourself, and swipe to unblock Silence notifications for your phone app. It's weird how it was set that way, but that's the best solution!
How do I unmute phone call notifications?
Thanks! My incomimg calls now appear on my screen!
I tired the unblock silence notifications and that still has not fixed it as well as a hard reset. Anyone else got any suggestions?
Thanks
Ian
Fix to dark screen on incoming call
Step 1: call youself
Step 2: swipe down on notification bar to view the call(usually how you would answer while dealing with this issue)
Step 3: swipe the call to the right and click the setting wheel.
Step 4: select "do not hide notifications"
Step 5: test call after doing this with the screen off, its should work.
BlueFox721 said:
Maybe the setting for proximity...in pocket...turn off
Click to expand...
Click to collapse
I turned "block accidental touches" off.
That worked for me!
THANKS

Google assistant is basically useless.

I don't know if this is just me but I cant seem to get this damn feature to work. I've trained my voice to this thing a hundred times and still it won't recognize it. I have to say it 3 or 4 times and finally, once I scream it, it might work. I look like a damn fool. Is this how it's supposed to work? By the time it does work, I could have picked the phone up and done what i was asking manually. What about when youre driving, you ask?
More than not, in the unlikely event that it will work, the phone remains locked until I enter my password. I've set the unlock-by-voice to "on" and still it will never work. What's the point if I'm driving and when it finally does recognize me, I have to pick it up and unlock it?
Has anyone else had these issues?
I'm left thinking that if Google was really pushing Google Assistant as the next big thing, they've got A LOT of work to do.
Nah. It even recognize my voice in noisy room. Although not every command would heard perfectly if its too noisy. But in a normal siatuation, it pick up 95-99% of my command and do it properly
otonieru said:
Nah. It even recognize my voice in noisy room. Although not every command would heard perfectly if its too noisy. But in a normal siatuation, it pick up 95-99% of my command and do it properly
Click to expand...
Click to collapse
Any ideas?
try saying "OK GOOGOO"
redddog said:
I don't know if this is just me but I cant seem to get this damn feature to work. I've trained my voice to this thing a hundred times and still it won't recognize it. I have to say it 3 or 4 times and finally, once I scream it, it might work. I look like a damn fool. Is this how it's supposed to work? By the time it does work, I could have picked the phone up and done what i was asking manually. What about when youre driving, you ask?
More than not, in the unlikely event that it will work, the phone remains locked until I enter my password. I've set the unlock-by-voice to "on" and still it will never work. What's the point if I'm driving and when it finally does recognize me, I have to pick it up and unlock it?
Has anyone else had these issues?
I'm left thinking that if Google was really pushing Google Assistant as the next big thing, they've got A LOT of work to do.
Click to expand...
Click to collapse
Never had an issue with the Assistant. Works in 98% of cases. Could it be that the microphone on the phone is defect?
I don't think so. It seems like once it's woken up, it acts better. The super annoying part is when the phone hears me but requires me to input my unlock code. why wouldn't it just wake up?
jbr05ki said:
try saying "ok googoo"
Click to expand...
Click to collapse
"hey goooogo" "Hey! Ok!" Lol
Also using "Hey Google" which works a treat, by passes lock screen, and has a sweet voice!
I have the same problem. Sometimes it takes forever to activate, and sometimes it doesn't listen when it does. I'm also having constant gps issues. May rma soon
Sent from my Pixel 2 XL using Tapatalk
redddog said:
I don't think so. It seems like once it's woken up, it acts better. The super annoying part is when the phone hears me but requires me to input my unlock code. why wouldn't it just wake up?
Click to expand...
Click to collapse
Try add trusted voice to smart unlock
jbr05ki said:
try saying "OK GOOGOO"
Click to expand...
Click to collapse
You're a genius, this worked for me, I've been trying to use Google Assistant with screen off and this seems to work for now
redddog said:
I don't think so. It seems like once it's woken up, it acts better. The super annoying part is when the phone hears me but requires me to input my unlock code. why wouldn't it just wake up?
Click to expand...
Click to collapse
You have to go into Google Now>Settings>Devices>Phone>Unlock With Voice Match
That should take care of the issue.
Juansegovia20 said:
You're a genius, this worked for me, I've been trying to use Google Assistant with screen off and this seems to work for now
Click to expand...
Click to collapse
Wait seriously? I thought we were poking fun at the Italian grandmother trying to talk to the Google home...well, glad it worked for you lol.
PS if you don't know what I'm talking about, look it up on YouTube.

Categories

Resources