I went into google now search settings and performed the voice training and enabled the option for hot word detection from lock screen and power off but it doesn't work. the only time it works is when i'm at the home screen UNlocked OR at the google now search area. Screen off or from lock screen detection simply does not work.
does anyone else notice this?
I don't have the nexus 9 but I did install the latest google now search and launcher from apkmirror .com and there was an always listening option in 'hotword detection' in voice settings of the google now. There was also the screen off detection option but it was greyed out. I had the always listening in all apps option enabled and it was working greatly but the next day I woke up and the feature wasn't working so I went into settings and discovered that both of those options had disappeared (not greyed out but freaking disappeared), its some kind of google restriction, they are remotely restricting users from using these features for some unexplained reason.
Maybe its the same for u or it might be something else.
Same here, bit worked arter reboot
It works for a while after a reboot, but eventually stops working after a couple hours.
Looks like a common bug, I've seen some threads about this same issue (and I'm experiencing the same problem, too)
Ok, let's hope Google is on it
borchgrevink said:
Ok, let's hope Google is on it
Click to expand...
Click to collapse
OK Google... get on it RIGHT NOW! same issue on the Nexus 4 AOSP build too...
mackendw said:
OK Google... get on it RIGHT NOW! same issue on the Nexus 4 AOSP build too...
Click to expand...
Click to collapse
Is it supposed to work on the N4? (I mean when screen off).
borchgrevink said:
Is it supposed to work on the N4? (I mean when screen off).
Click to expand...
Click to collapse
think about it...you're in your car, the screen times out and you want to make a call using voice recognition....so you have to unlock the screen and then use the voice recognition... sounds like a dangerous bug to me....serious liability IMHO
mackendw said:
think about it...you're in your car, the screen times out and you want to make a call using voice recognition....so you have to unlock the screen and then use the voice recognition... sounds like a dangerous bug to me....serious liability IMHO
Click to expand...
Click to collapse
I know, but the N4 doesn't support the neccessary hardware for this feature. Only the N6 and N9 does.
borchgrevink said:
I know, but the N4 doesn't support the neccessary hardware for this feature. Only the N6 and N9 does.
Click to expand...
Click to collapse
when I initially set it up, IT DID WORK....but then after a few hours, days (dunno for sure) it stopped. voice recognition works from google now screen, or the home page fine. something not right somewhere...
Hmm. From locked screen? Strange. Absolutely sure?
borchgrevink said:
Hmm. From locked screen? Strange. Absolutely sure?
Click to expand...
Click to collapse
there is an option in Google Now -> Settings -> Voice -> OK google detection ....a check box exists here stating:
When Locked
Allow "OK Google" to start a voice search or action from a secure lock screen
so, it would seem that this is what was intended. perhaps what they meant here was that the screen has to be on and not timed out. dunno.
Yes, but screen has to be on. Only nexus 6 and 9 support GN with screen locked and off
Google search from locked screen works for a while and then stops. It's done this on my s4 and note 3. It is defenetly supposed to work from secure lock screen. In Google now settings there is a 3rd check box and you even get a warning stating anyone may be able to unlock your phone.
Google needs to fix this issue. I'm not sure what's up with these companies making screwed up software. Where are the devs, and why are they getting paid if they can't make flawless software. When I crash My car into a tree trying to unlock my phone and I press a law suit against google I'll bet they will fix it. Always takes a law suit to fix ****.
Oh. Anyone notice every app you've ever paid for or downloaded is under my apps "all" what's up with "all" I'll file my documents in my office under the "all" folder and see how quickly I get fired...Thanks for allowing me to rant.
Happy new year!
https://productforums.google.com/forum/#!topic/websearch/xGiV6D4PMS8/discussion[1-25]
Major issue
Related
I updated to jelly bean last week. It came with talk back. trying everything I can think of, I have come to the conclusion that if anything else in accessibility is on, talk back come on too. I have a pebble watch, an love it. But when either it, or pebble notifier, it light wave is on, then the blasted voice tells me everything I am doing. It's very annoying. I tried stopping talkback with system tuner, which led to even worse problems. (like no touch screen function except with the s-pen.) Does anyone know how to get rid of talk back? Thanks in advance.
chainmaileguy said:
I updated to jelly bean last week. It came with talk back. trying everything I can think of, I have come to the conclusion that if anything else in accessibility is on, talk back come on too. I have a pebble watch, an love it. But when either it, or pebble notifier, it light wave is on, then the blasted voice tells me everything I am doing. It's very annoying. I tried stopping talkback with system tuner, which led to even worse problems. (like no touch screen function except with the s-pen.) Does anyone know how to get rid of talk back? Thanks in advance.
Click to expand...
Click to collapse
Root your phone, download an app for deleting system apps. delete it.
You can find how to root your phone in the development forums. Make sure you do it for the correct version of andriod ie:4.1.2
chainmaileguy said:
I updated to jelly bean last week. It came with talk back. trying everything I can think of, I have come to the conclusion that if anything else in accessibility is on, talk back come on too. I have a pebble watch, an love it. But when either it, or pebble notifier, it light wave is on, then the blasted voice tells me everything I am doing. It's very annoying. I tried stopping talkback with system tuner, which led to even worse problems. (like no touch screen function except with the s-pen.) Does anyone know how to get rid of talk back? Thanks in advance.
Click to expand...
Click to collapse
Disable it in settings/application manager/all applications. Find talkback and select uninstall updates. After updates are uninstalled go back into talkback from application manager, select force stop, then disable.
Right! Never delete a system app until you have disabled it or froze it with TiBU, then tested your phone fir a day or so. You never know how or what those apps are connected to.
chainmaileguy said:
I updated to jelly bean last week. It came with talk back. trying everything I can think of, I have come to the conclusion that if anything else in accessibility is on, talk back come on too. I have a pebble watch, an love it. But when either it, or pebble notifier, it light wave is on, then the blasted voice tells me everything I am doing. It's very annoying. I tried stopping talkback with system tuner, which led to even worse problems. (like no touch screen function except with the s-pen.) Does anyone know how to get rid of talk back? Thanks in advance.
Click to expand...
Click to collapse
Settings/accessibility/talkback/turn off or configure options from there.
rangercaptain said:
Right! Never delete a system app until you have disabled it or froze it with TiBU, then tested your phone fir a day or so. You never know how or what those apps are connected to.
Click to expand...
Click to collapse
True. Thats why I tried to disable it. And google text to speech. And Samsung text to speech. Each one stops it for a while. Then it comes back on even though it shows it is disabled. Its enough to make you start pulling out your hair.
If it says it is off then you are experiencing something else. What speech are you getting?
Agoattamer said:
If it says it is off then you are experiencing something else. What speech are you getting?
Click to expand...
Click to collapse
Whenever I turn a page. Which page of apps or widgets I am on.ect. I disabled all three. Then powered down the pbone. When it came back up, it has the talkback hand up I the top bar. Says it is on. Yet it doesn't even show up in settings/accasabilities menu. I'm stumped.
chainmaileguy said:
Whenever I turn a page. Which page of apps or widgets I am on.ect. I disabled all three. Then powered down the pbone. When it came back up, it has the talkback hand up I the top bar. Says it is on. Yet it doesn't even show up in settings/accasabilities menu. I'm stumped.
Click to expand...
Click to collapse
For me the issue was being caused by that fact that I have NoLED turned on in Accessibility. And it's a known issue with the developer of NoLED because he has a FAQ item about it. The best I've been able to do is get the talkback completely silent by disabling Talkback, Google Text to Speech and Samsung TTS. NoLED still works, and the nagging voice is gone, the only unwanted artifact is the HAND icon of Talkback that continues to show up in the Notification bar even though it's not running. I can live with that way easier than hearing that silly voice telling me everything I was doing.
For what it's worth I think the guides provided concerning rooting and rom upgrades for this phone are not as explicit or clearly written as they could be. Kudos to those who took time to do and provide what's there, and I realize that they've most likely moved on to newer devices, but even though I've rooted most of my devices in the past and am not a complete noob I did not feel comfortable using the provided instructions on this device. I haven't bricked a device yet, and don't want to start with this one.
Well, I'm not running no led. Whenever any of the services I use are active (pebble, or pepple notifier) are activated, talkback is activated. Like you, I have rpoted every device up to this one. Not really scared of bricking it. Just not sure a new rom would help. Contacted samsung, and was told it was a hardware problem. Like I'm an idiot. Obviously its in the software. Just not sure if it is samsung specific. Guess I'll just keep bumbling along with this work around.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Tref said:
... the only unwanted artifact is the HAND icon of Talkback that continues to show up in the Notification bar even though it's not running ...
Click to expand...
Click to collapse
FYI. You can get rid of the Talkback icon after each reboot by opening the notification bar, touch and hold Talkback, pick App Info, this will open into Settings App Info (for some reason), pick force stop and then the icon is gone until the next reboot.
holmanm said:
FYI. You can get rid of the Talkback icon after each reboot by opening the notification bar, touch and hold Talkback, pick App Info, this will open into Settings App Info (for some reason), pick force stop and then the icon is gone until the next reboot.
Click to expand...
Click to collapse
Thanks. However, every time I have force stoped it, my touch screen will only work with the stylus. Touch input goes dead. And sometimes the touch alignment goes so that when you touch in one place, it refesters somewhere else. Guess I'll just live with the hand.
holmanm said:
FYI. You can get rid of the Talkback icon after each reboot by opening the notification bar, touch and hold Talkback, pick App Info, this will open into Settings App Info (for some reason), pick force stop and then the icon is gone until the next reboot.
Click to expand...
Click to collapse
chainmaileguy said:
Thanks. However, every time I have force stoped it, my touch screen will only work with the stylus. Touch input goes dead. And sometimes the touch alignment goes so that when you touch in one place, it refesters somewhere else. Guess I'll just live with the hand.
Click to expand...
Click to collapse
This whole Talkback feature appears to be filled with issues. I think I'll live with the hand (and not talk to it, lol), rather than risk more complications and further issue. So far I like Jellybean, but I hope that the next version of Android on Samsung devices fixes these issues.
As an aside, another thing that took me by surprise was the use of a new mountpoint for the external SD card. It took me a bit to figure out why /sdcard/external_sd was empty of files, but Music and other apps were able to see the data I had on the card. It's been awhile since my days as a UNIX SA and it dawned on me, literally in the middle of the night that perhaps the OS was using a different mountpoint. I was very relieved to find it under /storage/extSdCard and that my data was both there and able to be used.
chainmaileguy said:
Thanks. However, every time I have force stoped it, my touch screen will only work with the stylus. Touch input goes dead. And sometimes the touch alignment goes so that when you touch in one place, it refesters somewhere else. Guess I'll just live with the hand.
Click to expand...
Click to collapse
Did you uninstall TalkBack (using something like Titanium BackUp) and not just disable it? If so, when you pick App Info from the Talkback notification does it open up the "Settings Version 4.1.2-I717UCMD3" app? If not It might be that we have different apps installed causing a different app to come up. If this is the case, would you mind trying going into Settings, Application Manager, All, Settings (the one with "Version 4.1.2-I717UCMD3", I have 2 Settings apps) and force stop that and see if that works.
I never uninstalled talkback. Since i haven't bothered rooting. forced stop defiantly gave me headaches, so I settled for stopping the text to speech of google and samsung. Running android 4.1.2. Ive seen on other posts where this is a samsung issue, and hopefully they are working on it. Looks like we have the same versions. Baseband i717ucmd3 with android version 4.1.2 \. Build # JZO54k.i717ucmd3. Force stopping just screws up my touchscreen, so I'll leave it enabled for now. Maybe Samsung will fix it, but I won't be holding my breath....
rangercaptain said:
Right! Never delete a system app until you have disabled it or froze it with TiBU, then tested your phone fir a day or so. You never know how or what those apps are connected to.
Click to expand...
Click to collapse
<<<<<<Well unless you know what your doing <<<<
I run my ROMs tight and bare minimum
™
Did you mean 'you're' ?
Don't quote, reply. If you quote, edit.
Yup
™
I too have a Pebble, and have had the issue with talkback showing up on every reboot. I had seen that it was a Samsung issue, so all I do is get rid of it on reboots. Just turn your Pebble Notifier, or I think any other accessibility app, off then back on. This will get rid of the hand, and thus far I have not had it talk to me at all. But I am running Padawan currently, so YMMV. To turn things off and on, just select the talkback notification from the bar to get into accessibility settings.
I ended up rooting for a couple of reasons. I had already frozen Google Text to Speech, Samsung Text to Speech, or whatever it's called, and the Talkback app but still had the hand. After rooting I was able to tap on Talkback in the pull down notification screen and turn off notifications of it. Strange that is was still there, but it worked and the hand hasn't been back.
I had this issue where i sounded like a mouse and you could not understand what i was saying on the other end of a hangouts call. I tried everything to resolve it and it turned out to be the google now (search) settings ok google hotword detection allowing ok google to work from any screen. No clue why, as my sons galaxy nexus has the same setting and it works fine.
Just wanted to post in case anyone else ran into this.
JewRican said:
I had this issue where i sounded like a mouse and you could not understand what i was saying on the other end of a hangouts call. I tried everything to resolve it and it turned out to be the google now (search) settings ok google hotword detection allowing ok google to work from any screen. No clue why, as my sons galaxy nexus has the same setting and it works fine.
Just wanted to post in case anyone else ran into this.
Click to expand...
Click to collapse
I'm going to have to try this out. Me and my wife are having this same exact issue where I sound like a robot.
JewRican said:
I had this issue where i sounded like a mouse and you could not understand what i was saying on the other end of a hangouts call. I tried everything to resolve it and it turned out to be the google now (search) settings ok google hotword detection allowing ok google to work from any screen. No clue why, as my sons galaxy nexus has the same setting and it works fine.
Just wanted to post in case anyone else ran into this.
Click to expand...
Click to collapse
I have the same problem, but still trying to figure out a solution
dgmoodey said:
I have the same problem, but still trying to figure out a solution
Click to expand...
Click to collapse
so did you try disabling the setting that I posted?
workaround
But what if one wants to have the ok google functionality turned on? Isn't this issue/bug supposed to be addressed by samsung?
MimKoRn said:
But what if one wants to have the ok google functionality turned on? Isn't this issue/bug supposed to be addressed by samsung?
Click to expand...
Click to collapse
Sure is, but who knows when that will happen
http://forum.xda-developers.com/galaxy-s4-verizon/help/video-call-audio-kit-kit-upgrade-t2856743
I started a whole other thread on this.
Is not just a Hangouts issue, but it's a Skype and any other video chat issue.
Are you guys on 4.4? This might be it, but since hot word detection on any page was a Kit Kat function.
I tried turning off Google Now, but but I didn't turn off the hot word on any page function. I'll try it and let you know if it's the issue.
JewRican said:
I had this issue where i sounded like a mouse and you could not understand what i was saying on the other end of a hangouts call. I tried everything to resolve it and it turned out to be the google now (search) settings ok google hotword detection allowing ok google to work from any screen. No clue why, as my sons galaxy nexus has the same setting and it works fine.
Just wanted to post in case anyone else ran into this.
Click to expand...
Click to collapse
Thank you sir. After a week and a half of trouble shooting, you found the answer.
The problem is indeed, and Google Search's new "anytime /any screen" hotword section function..
Go to Google Search, Settings, Voice, Uncheck hotword detection from any screen.
Why this breaks the wifi audio when using a video chat service is a mystery.
I now realize that this wasn't an issue under 4.3, because Hotword detection from any screen is a Kitkat only feature.
I don't know if this a Samsung, possibly or Google Search issue. But I'll submit a ticket to Google under in the play store.
Hopefully, everyone else will too.
I'm on the galaxy s4 from tmobile. I was also having this problem, but I turned off the hotword from any screen and it worked. I first noticed this trying to make a google voice call from hangouts, which is audio only, but it did it with video chats as well. I'll definitely report this.
Thanks for figuring it out!
Delete
I can also verify that this fix works. I'm going home for Thanksgiving & we wanted to set it up so the gf and stepson can video chat with me while I'm gone. She was trying to set it up on her PC & having issues, which I've never even tried.
I asked her why she didn't just use her phone like a normal person & she said she'd tried it with her mom & had the high pitched noise. We tried it & confirmed & a Google search brought me here.
I disabled hotword detection from any screen & it went away (she doesn't use it all the time like I do).
This is weird though, because this is the vzw s4 that I used to video with her on her s3 thriugh hangouts before & I've had Google now set to detect from any screen since I could.
Not that I think it matters, but her mom has an s5 & I assume she's got hotword detection off. I'm on the Note 4 & have it on with no issue.
I know the OP is a little old, but I'm wondering if the latest OTA for the s4 has something do to with it? I swear I videoed her from the s4 with detection on.
In any case, after my long rambling, thanks for posting the fix!
Sent from my Note 4
Jonny Kansas said:
I can also verify that this fix works. I'm going home for Thanksgiving & we wanted to set it up so the gf and stepson can video chat with me while I'm gone. She was trying to set it up on her PC & having issues, which I've never even tried.
I asked her why she didn't just use her phone like a normal person & she said she'd tried it with her mom & had the high pitched noise. We tried it & confirmed & a Google search brought me here.
I disabled hotword detection from any screen & it went away (she doesn't use it all the time like I do).
This is weird though, because this is the vzw s4 that I used to video with her on her s3 thriugh hangouts before & I've had Google now set to detect from any screen since I could.
Not that I think it matters, but her mom has an s5 & I assume she's got hotword detection off. I'm on the Note 4 & have it on with no issue.
I know the OP is a little old, but I'm wondering if the latest OTA for the s4 has something do to with it? I swear I videoed her from the s4 with detection on.
In any case, after my long rambling, thanks for posting the fix!
Sent from my Note 4
Click to expand...
Click to collapse
Its strictly a kit Kat 4.4 issue. That Google has dropped a serious ball on. But they can care less now, since they are on to lollipop 5.0
Maybe it will be fixed in 5.0
Looks like the issue wasn't fixed in Lollipop either. I'm running Dan's GPE ROM, and I had to disable any-screen hotword detection to return the normal voice.
Just wondering if anyone has Google Everywhere enabled and could speak to how well it can be implemented on the XU.
I realize it won't be as good as phone with a dedicated mic and chip but is it usable on your phone?
Asking to help me decide in purchasing this phone.
Thank you for your time.
It works quite well for for me. Since my system language is German I had to set the default language to English (U.S.) and German as secondary. But now "OK Google" works everywhere, even on the lockscreen and with commands in both languages. Only when the device is in standby, it doesn't react. Listening to music while the display is off? It works...
The phone itself is a steal here in Germany. Compared to a Samsung Galaxy S5, the specs aren't so much different (the size is rather a personal preference than a pro or con). Nevertheless the Z Ultra costs half (222€).
unidentifier said:
Just wondering if anyone has Google Everywhere enabled and could speak to how well it can be implemented on the XU.
I realize it won't be as good as phone with a dedicated mic and chip but is it usable on your phone?
Asking to help me decide in purchasing this phone.
Thank you for your time.
Click to expand...
Click to collapse
For me it's not sensitive enough. My voice could be in a whisper and the Nexus 5 could still pick it up, but for the Xperia Z Ultra I have to raise my voice a bit or hold it closer to my face.
OK Google works from everywhere except for when the screen is off. You can enable it in Google Now under Settings > Voice > "OK Google" Detection > From Any Screen
Works great for me
It seems to work everywhere, my only bicker is I wish I could hold a conversation with it only because it gets compared to siri. So I chose to go with my assistant from the play store best app ever.
H. E. Pennypacker said:
OK Google works from everywhere except for when the screen is off. You can enable it in Google Now under Settings > Voice > "OK Google" Detection > From Any Screen
Click to expand...
Click to collapse
haven't been on stock rom for a while, but in slimroms, "OK GOOGLE" can be setup to work when the device is sleeping while charging
ShadowVlican said:
haven't been on stock rom for a while, but in slimroms, "OK GOOGLE" can be setup to work when the device is sleeping while charging
Click to expand...
Click to collapse
Yeah, that's probably some kernel tweak or something. I don't know :silly:
ShadowVlican said:
haven't been on stock rom for a while, but in slimroms, "OK GOOGLE" can be setup to work when the device is sleeping while charging
Click to expand...
Click to collapse
H. E. Pennypacker said:
Yeah, that's probably some kernel tweak or something. I don't know :silly:
Click to expand...
Click to collapse
No, that's a feature of Google Search for all KitKat and up phones. It will always listen while charging if you have "Ok Google" detection from lock screen checked.
ApertureAndroid said:
No, that's a feature of Google Search for all KitKat and up phones. It will always listen while charging if you have "Ok Google" detection from lock screen checked.
Click to expand...
Click to collapse
Ohh, yes of course. That's a stock feature. I just haven't used it.
Hey guys!!
Just got my S6 Edge and loving everything about it so far except...
My Ok Google anywhere isn't working. It's not even presenting me an option to turn it on. Also "enable audio history" option is missing which I know is necessary to get it all working.
I have done a factory reset, enabled and disabled S Voice, primary language English US, and deleted app data etc! I am running a stock Telus Samsunf S edge. I don't know if it's firmware dependent or not.
If anyone can suggest anything else, I'm all ears!!
Thanks in advance!
nvict said:
Hey guys!!
Just got my S6 Edge and loving everything about it so far except...
My Ok Google anywhere isn't working. It's not even presenting me an option to turn it on. Also "enable audio history" option is missing which I know is necessary to get it all working.
I have done a factory reset, enabled and disabled S Voice, primary language English US, and deleted app data etc! I am running a stock Telus Samsunf S edge. I don't know if it's firmware dependent or not.
If anyone can suggest anything else, I'm all ears!!
Thanks in advance!
Click to expand...
Click to collapse
Looks like they removed it I had it yesterday now it's gone there was a update last night
Ah, that's a shame. At least I'm not the only one!!
Hope they come to their senses and come out with an update to enable it again!
Yep was there yesterday and gone now.
Perhaps it was sucking too much battery? Can't say I really used it that much but it was a cool feature. Will just have to press and hold home button to use it! A bit of a pain!
Found a work around for now...
Using an app called "Now Gesture Tweaks" which allows me to press and hold the home button to activate Voice Search and Nova Launcher gesture "Swipe Up" for Google.
Gives us a similar effect.
voice your disapproval: @S6NoOKGoogle https://twitter.com/S6NoOKGoogle
Don't you guys have "google settings" in your app drawer? All "OK Google" settings are right there.
EDIT: My bad.. deep down to the detection settings, it is gone!! How!? So is this Samsung's fault or Google's fault?
Yup. It's global and it's just all the variants of the S6 & S6 Edge. Some Nexus devices seem to be broken but still have their options.
https://productforums.google.com/forum/#!topic/websearch/xGiV6D4PMS8[201-225]
I used it on a regular daily basis. Very frustrating for them to pull it without notice...
What is even more frustrating is that neither Google or Samsung is taking the heat for this,,,both are referring us to each other LOL,,,classic tactic.
SuperSport said:
I used it on a regular daily basis. Very frustrating for them to pull it without notice...
Click to expand...
Click to collapse
What if you use the Google now launcher?
jasonbiggs said:
What if you use the Google now launcher?
Click to expand...
Click to collapse
Unfortunately same, not working.
It doesn't work on my Note 2, my wife's S3, and even my coworker's Walmart Alcatel phone alll running Kitkat and all did the latest update.
Its a bigger issue and Google doesn't seem to be too concerned
I got an update yesterday and it is working now, well at least from the homescreen.
Sprint S6 Edge w/Nova Launcher, OK Google works from any screen.
Does the widget need to be on the home screen for it to work
Sent from my SM-G925F using XDA Free mobile app
Not for me
Wow, just realized I don't need the widget at all for hotword to work. Cool
supposedly the 5.1.1 update will bring the OK Google functionality back.
Is your S-Voice App activated? Or did you disable that? I've read that either having it on or off might enable OK GOOGLE from any screen to work.
rank78 said:
Sprint S6 Edge w/Nova Launcher, OK Google works from any screen.
Click to expand...
Click to collapse
Hi,
As you may have known, ok Google issue has been solved in recent miui 10 stable update. Now it offers to unlock the device using voice match even when the display is turned off.
Now even I say ok Google when the screen is turned off, it does wake the device but it's still locked and it shows me pattern unlock.
How to unlock the device so that I can pass an actual command to Google assistant?
Thanks
My phone just updated to MIUI Global 10.0 (10.0.4.0 OEJMIFH) and it was fixed.
Now I can say 'Ok Goolge' and it opens assistant.
Phone unlocking by voice command is disabled by miui and afaik even Google is removing this feature from assistant, security reasons probably
lipaum said:
My phone just updated to MIUI Global 10.0 (10.0.4.0 OEJMIFH) and it was fixed.
Now I can say 'Ok Goolge' and it opens assistant.
Click to expand...
Click to collapse
Yes that works but I was talking about unlocking the phone.
OK google works on miui 10 Global stable?
I didnt know that, i thought it just work on stock base android roms.
pack21 said:
OK google works on miui 10 Global stable?
I didnt know that, i thought it just work on stock base android roms.
Click to expand...
Click to collapse
It was broken when the device came out. Now they fixed it on popular demand. [emoji16]
lockhrt999 said:
Yes that works but I was talking about unlocking the phone.
Click to expand...
Click to collapse
Did you try 'Voice Match Unlock' (or something because mine is in portuguese) in settings? Here (again) is working.
Sent from my Poco F1 using XDA Labs
lipaum said:
Did you try 'Voice Match Unlock' (or something because mine is in portuguese) in settings? Here (again) is working.
Sent from my Poco F1 using XDA Labs
Click to expand...
Click to collapse
Yes, I did that. It does wake up the device but doesn't unlock it.
Edit: Sorry. I wasn't facing the same issue. I was facing the issue where the Google Assistant wasn't working properly, and it would show me the error "unable to open microphone".
I found the solution on the MIUI forums. Here's what I did...
You have to go to the Google app in "Installed Apps" and clear the cache and the data and reboot, and it'll start working fine.
It was a little tricky to find the Google app as it wouldn't show in the Installed Apps. You have to click on the 3 dots on the upper right side corner and select "Show all apps" and then it'll show up. After that, you just clear the cache and the data and reboot phone, and it'll start working properly
Nevertheless, I tried your solution and it didn't work either way.
Ok Google straight up doesn't work for me
Delete data, clear cache, udpate app. This worked for me
muham47 said:
Delete data, clear cache, udpate app. This worked for me
Click to expand...
Click to collapse
There are lots of different places where I can delete Google data. Could you walk me through it?
muham47 said:
Delete data, clear cache, udpate app. This worked for me
Click to expand...
Click to collapse
you are saying you can wake and unlock the sleeping phone by saying ok Google, right?
I have tried deleting cache and data, updating but it didn't work for me.
What exactly did you do?
Google's quietly removes Voice Unlock on Pixel 3
lockhrt999 said:
Nevertheless, I tried your solution and it didn't work either way.
Click to expand...
Click to collapse
Don't get your hopes high about this feature's implementation on OEMs. Google were already silently phasing-out this feature and the OEMs will soon to follow.
Refer to these links:
https://www.theverge.com/2018/10/19/18001460/google-pixel-3-xl-google-assistant-voice-match-removed
https://9to5google.com/2018/10/26/google-killing-android-voice-unlock/
lockhrt999 said:
you are saying you can wake and unlock the sleeping phone by saying ok Google, right?
I have tried deleting cache and data, updating but it didn't work for me.
What exactly did you do?
Click to expand...
Click to collapse
Yep, i just cleared cache, data then udpated the google app and it worked.
---------- Post added at 03:09 AM ---------- Previous post was at 03:04 AM ----------
raydialseeker113 said:
There are lots of different places where I can delete Google data. Could you walk me through it?
Click to expand...
Click to collapse
Go to settings -> installed apps -> search for google, tap on google app -> tap clear data, clear cache, uninstall updates, then update your google app.
muham47 said:
Go to settings -> installed apps -> search for google, tap on google app -> tap clear data, clear cache, uninstall updates, then update your google app.
Click to expand...
Click to collapse
Tried this as per instructions but still no avail. Are you using stable MIUI version?
lockhrt999 said:
Tried this as per instructions but still no avail. Are you using stable MIUI version?
Click to expand...
Click to collapse
It sort of works for me (Stable 10.0.6.0). However, following those instructions it only wakes the phone, but doesn't unlock. But - after getting to that point, I went into the Google assistant, settings, voice, voice match and it let me select the slider - gave me a warning about being less secure, and then it woke up AND unlocked via voice.
Unfortunately, it then failed to do it the next time I tried it and asked for my pattern/face. Not sure if it requires log in sometimes and not others, or if the first time was just luck!
At one point it would wake up and let me ask a question, but only read or show me the answer when I unlocked, but now it won't even do that, so basically it's completely inconsistent! hurrah!
Clearly some sort of security issue - whether it's Xiaomi or Google's fault is up for debate, but if Google are removing it from their flagship then I wouldn't be surprised if it never works properly on anything else.
If they would only get Trusted Places working properly (Google that is) or even allow trusted Wifi (I know the security implications but I'm prepared to accept them!) then it would probably not be necessary.
I could keep it unlocked with my watch, but then I find that (despite pocket mode) my phone regularly does random things while in my pocket!
I had similar issues with my Mate 10 Pro, that I've just changed from, so it's not solely Xiaomi's fault, but is it really too much to ask to expect Android features that are offered to actually work out of the box?!
gonzo99 said:
It sort of works for me (Stable 10.0.6.0). However, following those instructions it only wakes the phone, but doesn't unlock. But - after getting to that point, I went into the Google assistant, settings, voice, voice match and it let me select the slider - gave me a warning about being less secure, and then it woke up AND unlocked via voice.
Unfortunately, it then failed to do it the next time I tried it and asked for my pattern/face. Not sure if it requires log in sometimes and not others, or if the first time was just luck!
At one point it would wake up and let me ask a question, but only read or show me the answer when I unlocked, but now it won't even do that, so basically it's completely inconsistent! hurrah!
Clearly some sort of security issue - whether it's Xiaomi or Google's fault is up for debate, but if Google are removing it from their flagship then I wouldn't be surprised if it never works properly on anything else.
If they would only get Trusted Places working properly (Google that is) or even allow trusted Wifi (I know the security implications but I'm prepared to accept them!) then it would probably not be necessary.
I could keep it unlocked with my watch, but then I find that (despite pocket mode) my phone regularly does random things while in my pocket!
I had similar issues with my Mate 10 Pro, that I've just changed from, so it's not solely Xiaomi's fault, but is it really too much to ask to expect Android features that are offered to actually work out of the box?!
Click to expand...
Click to collapse
You're right. But if it had worked then it would have been a great party trick. I never had a phone which could wake up with an audio command.
lockhrt999 said:
You're right. But if it had worked then it would have been a great party trick. I never had a phone which could wake up with an audio command.
Click to expand...
Click to collapse
The irony is that I've just switched from a Huawei Mate 10 Pro (Various reasons, but flaky bluetooth top of the list) and that did do it after the last update. That's because they have their own voice recognition baked in to the Kirin chipset though I think, so it's not using just Google's voice match - and even that took a lot of fiddling to get working. No idea how secure it was, but it was handy for finding the phone by asking it where it was! I refuse to talk to my phone in public anyway, so it's something I can live without I think