Hi,
I have an S9+ with Rogers in Canada, which was recently upgraded to Android pie. Ever Since I have not been able to use Google assistant when the phone is in sleep mode. Prior to the update, I was able to say "OK Google: set the timer for xxx minutes", when the phone was in sleep mode. But now it doesn't work anymore, other than vibrating. It still works on other screens, just not when the phone is asleep.
I called Samsung but they were useless telling me that I need to press the home button and that it has always been so and that nothing changed with Android Pie but that is BS.
Can other Pie users please verify, that OK Google works on your phone when it is in sleep mode and if anyone else has the same issue as I and if you have a solution.
Thanks,
Roli
Sleep mode? as in while screen is off? or another mode?
skygear said:
Sleep mode? as in while screen is off? or another mode?
Click to expand...
Click to collapse
Yes. When the screen is locked.
My phone was like that at one point, I am on Pie now and I had to go into the settings and make sure it was set to work even when the screen was off. Took a minute to find, have you checked there?
Settings/Google/Search, Assistant and Voice/Voice/Voice Match
I have. The phone vibrates when the screen is off and I say "OK Google" but is the screen remains black until I press the home button.
I'm thinking now that perhaps it has something to do with security and not with Google Assistant. I'm going to check my security settings. Maybe there's something there.
Come to think of it, I've had that happen before, not now but some time ago. I never sound effects, never really tried, somehow it just seemed to resolve itself after a while I guess. Good luck and keep us posted, you might be right in that it has to do with some security setting or something.
This? Access with voice match?
There is also that one underneath that says 'unlock with voice match', for use if you have a screen lock set up I guess. Did you try that one as well?
YrrchSebor said:
There is also that one underneath that says 'unlock with voice match', for use if you have a screen lock set up I guess. Did you try that one as well?
Click to expand...
Click to collapse
I’m sure that’s the option the OP needs to use.
I think it's a common problem with Google assistant and potentially the same as the 'voice unlock paused' issue, I've seen people complaining about both on pixel forums as well as on here (if Google can't get it right with their own phone what hope do we have!!). There were a few steps around deleting the voice model and resetting the smart lock agent (see screenshot). I did this and retrained the voice model in absolute silence which seemed to work for a bit but has since stopped. Annoyingly it doesn't seem to take into account when I'm at home and the phone is unlocked with smart lock!
xc rider said:
I’m sure that’s the option the OP needs to use.
Click to expand...
Click to collapse
OK. Here is my screenshot of the settings that I have on my phone. Access and Unlock with Voice Match are turned on.
Let me reiterate. The phone is reacting to "OK Google" on every screen so the voice match is working.
The problem is that when when I am on the lock screen and I say "OK Google" the phone vibrates, acknowledging that it heard the prompt but it does nothing until I press the home button or power button.
Have a look at this video. (I distorted for privacy reasons the audio because my phone and tablet were reacting when I was playing back the video):
https://youtu.be/fO3nsJ215eo
I have the S9+ on Rogers and thankfully, this feature continues to work flawlessly after the upgrade as I use it often in my daily work..It actually seems to be more responsive after the update.
It can be very frustrating when the feature randomly stops working but it is usually due to an update on Google's end that causes it as I can usually fix it by going through the voice setup steps after an update..
In extreme situations you may want to uninstall and then reinstall the Google app..
Had the same problem myself and fixed it, just go to app info for Google and clear the cache and clear data, worked a treat for me
Roli001 said:
Hi,
I have an S9+ with Rogers in Canada, which was recently upgraded to Android pie. Ever Since I have not been able to use Google assistant when the phone is in sleep mode. Prior to the update, I was able to say "OK Google: set the timer for xxx minutes", when the phone was in sleep mode. But now it doesn't work anymore, other than vibrating. It still works on other screens, just not when the phone is asleep.
I called Samsung but they were useless telling me that I need to press the home button and that it has always been so and that nothing changed with Android Pie but that is BS.
Can other Pie users please verify, that OK Google works on your phone when it is in sleep mode and if anyone else has the same issue as I and if you have a solution.
Thanks,
Roli
Click to expand...
Click to collapse
I'm on an S9+ with Bell in Canada and I can still unlock my device with voice when it's sleeping even though it gave me a notice that I would no longer be able to.
For some reason I've lost the ability to voice control any of my smart devices through Google Home. Seems like a related but different problem.
That, the lack of pro video mode and the brutal battery life have really turned Pie into a nightmare for me..
Hope they release fixes for these issues or I'll have to look at flashing..
Related
I need a way to be able to voice dial at any time even with the phone locked or with some other app the Voice Talk open via Bluetooth, I know this is possible on Android since my old Motorola Milestone could do it and would be legal under the new laws.
My province is now getting distracted driving laws which will make using my phone illegal with how many steps it takes currently.
I refuse to give up locking my phone since I have private info on it but I need to be able to make calls by pressing the button on my Bluetooth even with the phone locked since it could even be in my jeans pocket with no way to get at it when sitting.
Currently on my GS2 I have to unlock the phone then double click the home button to bring up voice dialing or even open the voice talk app if I am in a different app.
Compared to my Milestone where I never touched it and at any time even pattern locked or in a different app I could just press the button on my Bluetooth and say "call jane" or something and it always worked.
How can I get this back? Considering the laws are coming into effect next month for me.
I would like to keep the stock Samsung voice for most time but would be willing to have a second one that works even if the phone is locked.
I also have people that want this phone but willn't buy it until I get this fixed.
Use Tasker to disable the lock pattern when connected to a bluetooth device - therefore when you disconnect from your car bluetooth, your lock pattern will re-activate.
Problem solved!
OK I have that and think I am close to setting it up but can't totally figure it out how to disable the lock screen.
All I have figured out is a profile that runs if a mic headset is connected but when I try to figure out the task it does I get stuck.
I have never used Tasker before.
This is suddenly going to be to expensive since I found out the SGS2 requires extra work to disable the pattern lock which is a extra $10 plugin and I am not even sure if I want to pay for Tasker itself after the 7 day trial.
I might try and find out how it was done on my old phone when locked.
For others that may want to kn ow here is the thread for this on a GS2
http://forum.xda-developers.com/showthread.php?t=1110307
Nope, you don't need the plugin - there's a keyguard action that you would disable, which also disables the lockscreen.
I'm trying to set this up myself, but for some stupid reason, it's not responding when I press my bluetooth button at all...
Fricken Vlingo - you suck!
k1sr said:
Nope, you don't need the plugin - there's a keyguard action that you would disable, which also disables the lockscreen.
I'm trying to set this up myself, but for some stupid reason, it's not responding when I press my bluetooth button at all...
Fricken Vlingo - you suck!
Click to expand...
Click to collapse
Are you sure that would work on our Samsung phones since they modified the locking system to use the /efs partition?
If you do get it working make sure to tell me how.
Hello guys,
I am having this issue with my device - sometimes when I press the home button the Voice talk / command powered by Vlingo starts. I always press the button just once (I understand that it should happen when one double-presses the home button) and it is very annoying :-(
Note, that I have Settings/Motion/Double tap turned off as well. Is there any way to fix this or do you have any idea what may be wrong??
Thanks in advance!
Sent from my GT-I9100 using XDA App
while in the motion settings, you can see the tutorial clip and that double tap has nothing to do with the home button, but with double tapping the top side of the device to start voice control instead of saying "hi galaxy". so even with that switched off, your device will react to hitting the home button twice and does not really help diagnose the initial problem.
either you have a slight hardware defect in the home button, a software issue (or maybe user error). since hardware would be more severe, let's see the software side first. what exact rom do you have? device rooted or not? anything that could mess with voice input (connected bluetooth hands free, market vlingo or other tts or stt software installed...)?
also, just to exclude user error, let another person try.
P.S. are there special circumstances when this happens? like only from deep sleep, only when charging, with a connected headset, running certain apps or whatever?
Chef_Tony said:
while in the motion settings, you can see the tutorial clip and that double tap has nothing to do with the home button, but with double tapping the top side of the device to start voice control instead of saying "hi galaxy". so even with that switched off, your device will react to hitting the home button twice and does not really help diagnose the initial problem.
either you have a slight hardware defect in the home button, a software issue (or maybe user error). since hardware would be more severe, let's see the software side first. what exact rom do you have? device rooted or not? anything that could mess with voice input (connected bluetooth hands free, market vlingo or other tts or stt software installed...)?
also, just to exclude user error, let another person try.
P.S. are there special circumstances when this happens? like only from deep sleep, only when charging, with a connected headset, running certain apps or whatever?
Click to expand...
Click to collapse
Hello, thanks for your reply. I am running the device with an unmodified SW i.e. stock rom (having a branded phone from orange slovakia), no rooted just some apps installed from the android market. It is XXKE4/XWKE7, running android 2.3.3. I dont use bluetooth or handset nor dock or anything like that.
The issue seems to be completely random to me, while I usually notice it during browsing web with opera, but it happens with more apps. I don't know what is tts or stt sw, nor market vlingo. If you would like to know some more details please let me know what would be relevant for you.
I already thought about the hw issue, but I am not sure if they would accept the warranty claim as it is quite random. I thought there would be some way to completely disable voice talk as I dont expect to use it anytime in the future anyway...
As of the user error, it happens both to me as well as to my gf while using the phone for common internet use.
Sent from my GT-I9100 using XDA App
ok, that gave us something to work with. for future reference, when asking a question like this, it might speed up the process by giving as much information in the initial post as possible and let me explain why:
the fact that you use your unrooted stock rom tells me, that it is not a common and maybe reported bug that comes with a custom rom, and with an unrooted device, it is rather unlikely, that you screwed up a system component like this.
bluetooth, docks and handfrees could influence the voice input and its triggering by having their own triggers, but that is not the case.
if it happens to other people with your phone as well, it excludes your personal behaviour, tremors or whatever (no offense, you never know, just to cover everything, some people are shaky).
if it happened only in a special state, like only while sleeping for a minute or while charging, it would ensure, that it has something to do with deep sleep.
about the other things: with tts i was referring to text to speech, the engine that reads out display content, like incoming calls, text messages or navigation instructions, stt refers to speech to text, like voice input, saying hi galaxy, telling where to navigate or dictating notes...
vlingo is the engine that is used for voice talk and voice command and there is also a 3rd version, that can be downloaded on the android market, coming with yet other features and having them all present and maybe screwed up settings might have influenced anything there, however, this doesn't seem to be the case either.
so this leaves few options for how to proceed. in your place i would start off with reading this thread: http://forum.xda-developers.com/showthread.php?t=1097153
it deals with home button issues and a theory on how the home button sometimes might react as much as 15-30 minutes later than initially pressed, which might coincide with an actual press and being registered as a double press (although that's a stretch at best).
and when it comes to a next step, if you made sure, that does not apply to you, i would be uncertain, which way to go. a factory reset might help, but if, after hours of setting the device up again, you realize there has not been any change, it was nothing but work. then there are 2 things left:
either flash a newer rom using odin and any rom from here: http://forum.xda-developers.com/showthread.php?t=1075278 (full guide and download links included)
OR decide to send it in for warranty first and see what's what.
flashing a rom might solve your problems but influence your warranty state, if not done correctly and cautiously, which would make sending it in risky.
sending it in first and not getting that bug recognized or repaired for free would mean you might end up with weeks without your phone and/or a huge bill and the same issue as before.
i guess i would get a usb jig, read up on flashing, try several stock roms, not root the device and see if the bug is gone, if not, flash back to stock, make sure the flashing is not traceable and then try a local store or your carrier for a hardware replacement or repair.
Hey Guys in germany the Ota rolled out,
yesterday i got my update and i was happy to see the changelog because since smarthome i use google assistent a lot
And they are right, now it works when the screen is off - what dosnt work is the smartunlock. It asks me everytime for the Password....
I reinstalled google, delted my voice match and started over again. Same error.
Anyone else have this problem?
(Also battery drain - but i read it before with this rom - so no suprise i guess)
OT:
When i tell my google: Ok google, turn on the Light in my office, it always says "I turned on the Light in the office" I ****ING KNOW THAT CUZ I SEE IT MATE!! Gosh google you annoy me.
Is there anyway that it shuts up after the command "turn on / turn off" ?
EGOiST1991 said:
.
Is there anyway that it shuts up after the command "turn on / turn off" ?
Click to expand...
Click to collapse
No, but you can turn off media volume.
For the other issue: go to settings -> lock screen -> smart unlock -> voice match
Turn it off then on again and it should work.
If it doesn't, you need to go to the google app in the play store and hit delete. it will ask you if you want to factory reset the app since u cannot delete it. do it and then hit the three dots in the top right corner and disable auto update fot this app. This is because google recently updated google app and voice unlock doesn't work anymore with mate 10 pro (again)
0alfred0 said:
For the other issue: go to settings -> lock screen -> smart unlock -> voice match
Turn it off then on again and it should work.
If it doesn't, you need to go to the google app in the play store and hit delete. it will ask you if you want to factory reset the app since u cannot delete it. do it and then hit the three dots in the top right corner and disable auto update fot this app. This is because google recently updated google app and voice unlock doesn't work anymore with mate 10 pro (again)
Click to expand...
Click to collapse
Problem stays. i think i have to factory reset my mate 10 that it works.... but meh -.-
I also got the . 137,and now my AOD is a complete mess. The clock almost always displays wrong time. Last nite the display showed like 3:05am, while in fact it was like 4:50 (woke up had to pee :l).
With AoD on, my fingerprint reacts slower... I don't know how such a premium device cannot be sorted out in order for such a simple function such as AoD to work without problems. Seems that for some reason Huawei puts battery life above functionality.
Oh and I don't even want to go to the issue of scrolling widgets...
Maybe someone can help me, i updated last week my phone. to 137. (ota) i reseted my phone to get a fresh rom
about a hour ago i was in my car , and my radio dosnt show titels anymore and i cant forward tracks via radio. only on my phone.
My radio says "BT AUDIO" and its just playing. not more. .... that kinda sucks on the version before it was all okey.
Yes i delted car and phone bluetooth and reconnect. same issue.
updated to 137 too. battery same as before. little youtube, little gaming and some browsing and im on 55% with 4.10h sot.I did do a full upgrade trough " download full upgrade package" witch was 2.9gb if that materes
I bought an S9+ on launch day long story short it lasted 2 weeks before it would just shut down itself anytime you put it to sleep (screen off). I figured out after doing some tests and research that it would only do it when the fingerprint scanner was turned on. I sent it to Samsung which if anyone has had the pleasure of dealing with their customer service knows it's a nightmare to say the least. At least 2 week turnaround time but in the end they did come through and send me a brand new in box s9+.
Fast forward about a month later the new one is doing the EXACT same thing. If I turn the fingerprint scanner off and just use facial unlock it works fine. I really don't want to go through their customer service again and be without a phone for 2 weeks. I think this very well could be a software issue though factory reset does not solve the issue neither does erasing fingerprint and re entering them.
Has anyone else experienced this? I saw searching google that it is actually an issue others have had and like me, their replacements have all done the same thing. I am yet to find a thread with a solution though. What do you guys think? I'm actually wondering if perhaps rooting it and putting a custom rom on it would help.
Honestly, I have not heard of this before. After you try with fingerprint can you turn the device on at all?
Do you have any apps that may in the background that captures button inputs or fingerprint apps that capture slide movements or anything?
Scott said:
Honestly, I have not heard of this before. After you try with fingerprint can you turn the device on at all?
Do you have any apps that may in the background that captures button inputs or fingerprint apps that capture slide movements or anything?
Click to expand...
Click to collapse
Nope it seems to go off within seconds with the fingerprint scanner enabled. Even if I try to wake it up with the power button it seems to be dead. I've had the phone for about a month now and haven't recently added any new apps. I don't believe I have any apps that would be capturing anything. Is there any app I could use to check and see if perhaps I have something app related thats causing this?
I do believe it's gotta be software related.
You can type *#0*# in the dialer, then go to sensor and scroll down to find fingerprint test
Alright, so at first, google was working fine. while the phone was locked, screen off and it was in my pocket, I could say "Hey google, start a timer for 5 minutes" and it would confirm and start the timer.
Then I updated... and for a while it was saying "Sorry, I can't do that while the device is locked, go ahead and unlock the device". I followed about a dozen suggestions online and one of the suggestions (I'm still not sure which one) worked.
BUT: There's now this problem of: if the screen is off and I say "hey google, start a timer for 5 minutes": The screen will turn on and show the pattern unlock screen (as if it wants me to put in the pattern). If I leave it alone, the screen eventually turns off and google finally responds with "ok, starting the timer"... but then it never actually starts the timer until I pull the device out and unlock it.
Another strange thing is that it won't use the google assistant voice I selected (I selected a natural-sounding male voice but it still uses this robotic-sounding female voice).
I've been through countless forum posts, suggested fixes, have tried everything from restarting to the phone to clearing cache, uninstalling/reinstalling google assistant, changing security settings and even went as far as to factory reset the entire phone... nothing has worked so far. The problem I think is that all of those are solutions to problems that are SIMILAR to, but not exactly like, this. I'm wondering if anyone else has run into this specific problem and if you have: were you able to fix it? How?
It's just really annoying :/ This used to work so well. I used
PHP:
it for EVERYTHING. Now it doesn't really work at all unless I have my phone out and unlocked
Darn, it IS actually still telling me "actually, I can't do that while the device is locked. To keep going, go ahead and unlock the device". SO yeah... still just doesn't do anything at all if the device is locked. Only way I can get it to work is to uninstall all updates... but then it it reinstall those updates whenever I tell google play to update all. If I want to avoid that I guess I just have to go install updates individually/manually?... :/ This stinks. Just want my google assistant back to how it was working before (aka actually working - while the device is locked).