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 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
Is anyone else having problems with their recent apps not showing up? Today marks the second time that my recent apps has remained empty no matter how many times I pressed the button. The screen was never turned off...it's not the built in task killer. Eventually it will work and show the long list of apps I've used so they weren't killed they just wouldn't show up. Any ideas? You can imagine how frustrating it is not being able to jump between apps.
As a bonus, in my frustration I pressed and held the recent apps button and discovered this phone (EMUI 4) has a split screen which I haven't seen advertised anywhere else. I've actually read complaints about its lack of a slit screen so if there's a tips and tricks forum someone should post that for me.
I don't know the solution for this, but I suggest a factory reset, and thank you for the tip (split screen)
@brad7529
If you enabled developer options, try disabling it and use it for sometime to check on the recents.
DigiGoon said:
@brad7529
If you enabled developer options, try disabling it and use it for sometime to check on the recents.
Click to expand...
Click to collapse
Thanks. They are enabled and I also rooted and deleted attentitle. I don't see a connection there but I'm no expert, obviously, as I never would have considered dev options. But that's all I've done after rooting and I'll give this a try.
brad7529 said:
Thanks. They are enabled and I also rooted and deleted attentitle. I don't see a connection there but I'm no expert, obviously, as I never would have considered dev options. But that's all I've done after rooting and I'll give this a try.
Click to expand...
Click to collapse
Okay, report back after trying it.
DigiGoon said:
Okay, report back after trying it.
Click to expand...
Click to collapse
Looks like this worked. Thanks for the help. Still confused as to why it worked though. Was that a direct side effect of developer options being on or is there a specific setting in dev opt that just needed turned off?
In developer options in last section, there is an option Don't keep activities it might be enabled so.
Sent from my Huawei Honor 7 using Tapatalk
Ok, so heres my problem. Ill try and be as specific as possible without acting like a crazy person, because i am at my wits end with this.
I bought this tablet cheap at a pawn shop. They said it was locked and they 100% could not contact the original owner of it. Me, being somewhat learned with android stuffs, said ok, i will reset it from the recovery menu, NO PROBLEM. yea right. Get home, reset it and now I am introduced to this new Google factory reset protection business.
Now I have researched all possible ways to bypass this. The #1 solution is to get into the settings menu and enable developer options and go from there. I have enabled developer options on every android i have ever owned. Somehow, with this p.o.s. tablet....it will not work. I have tried every which way to tap build number 1, 000 times and nothing. For some reason, I cant get it to work.
Another solution that i found was to download and sideload this app to bypass it for you. Technically, its for Samsung devices, but i tried it anywho. All good until i plug the tablet into my pc. The PC wont recongnize the stupid tablet.
I am asking EVERYONE and ANYONE. Is there some other way for me to get past this crap? It is a RCA Viking Pro 10" tablet Android version 6.0 Model Number-RCT6303W87M7
PLEASE HALP!
Thanks in advance peoples,
-Jess
Same exact tablet and problem too.
My neighbor got it at an auction and I've done the Wipe Data/Factory Reset and then the trick to get into settings but tapping on Build doesn't work. Someone mentioned that 4 long taps worked for them so I tried that too with no luck. Not sure what else to do but send the neighbor to a cellphone repair store but it's for his grandson so I wanted to help out. Any advice/instructions would be great.
Thanks,
Roger
Successfully bypassed google account verification
RCT6303W87M7-Android 6.0-V-21-V1. 15. 80
I think I may have solved this problem. I also may have been the first to do this since I haven't found the answer anywhere else and I successfully accomplished it very easily actually after weeks of trying every available method out there. I hope this helps everyone. Let me know how it goes. Here goes: after getting to the page asking for the previous owners info, I hit the back button. I hit add network and typed in several random letters. I then long pressed those letters and clicked assist. I then clicked on gmail and was taken to the permissions and such page. I clicked on the 3 dots in the upper right and clicked manage apps. From there it took me to the settings page. Once in settings, I simply just added another user account and entered my current google information and went through all the steps. After I made it to the home screen I powered off the tablet and then restarted it. It asked for my info again and I entered my google information and it took me to the home screen after answering a few more questions. I then went to settings and deleted the user account I set up and that made me owner. I even did a complete reset and it no longer had the previous owners info. It only needed mine. FINALLY, I can use this tablet after weeks and frustration of trying to bypass this. Please let me know if this works for anyone. I may have left out something on accident if it doesn't. I'll redo it if I have to and possibly make a video if so. Thanks. I hope this does the trick. It would be nice to be the first at something for once if this is the case. Lol
Android Recovery v1.2
RCT6303W87M7-Android 6.0-V-21-V1. 15. 80
th674 said:
RCT6303W87M7-Android 6.0-V-21-V1. 15. 80
I think I may have solved this problem. I also may have been the first to do this since I haven't found the answer anywhere else and I successfully accomplished it very easily actually after weeks of trying every available method out there. I hope this helps everyone. Let me know how it goes. Here goes: after getting to the page asking for the previous owners info, I hit the back button. I hit add network and typed in several random letters. I then long pressed those letters and clicked assist. I then clicked on gmail and was taken to the permissions and such page. I clicked on the 3 dots in the upper right and clicked manage apps. From there it took me to the settings page. Once in settings, I simply just added another user account and entered my current google information and went through all the steps. After I made it to the home screen I powered off the tablet and then restarted it. It asked for my info again and I entered my google information and it took me to the home screen after answering a few more questions. I then went to settings and deleted the user account I set up and that made me owner. I even did a complete reset and it no longer had the previous owners info. It only needed mine. FINALLY, I can use this tablet after weeks and frustration of trying to bypass this. Please let me know if this works for anyone. I may have left out something on accident if it doesn't. I'll redo it if I have to and possibly make a video if so. Thanks. I hope this does the trick. It would be nice to be the first at something for once if this is the case. Lol
Android Recovery v1.2
RCT6303W87M7-Android 6.0-V-21-V1. 15. 80
Click to expand...
Click to collapse
Thanks for the work! I am going to see if my neighbor still has it and if so I'll get it from him and test out your procedure. Glad it worked for you! I'll report back as soon as I get it from him.
Roger
RogerMialkowski said:
Thanks for the work! I am going to see if my neighbor still has it and if so I'll get it from him and test out your procedure. Glad it worked for you! I'll report back as soon as I get it from him.
Roger
Click to expand...
Click to collapse
Please do. I'm anxious to see if it works for others as well.
th674 said:
Please do. I'm anxious to see if it works for others as well.
Click to expand...
Click to collapse
Well, turns out this tablet is a RCT6603 with the last patch date being June 2016. It wouldn't let me enter a Google account - it would go straight to the screen where it said this tablet was reset and to enter the previous owner's account information. Google must have really patched that version tight as a drum...
Glad it's at least working for you though.
Roger
RogerMialkowski said:
Well, turns out this tablet is a RCT6603 with the last patch date being June 2016. It wouldn't let me enter a Google account - it would go straight to the screen where it said this tablet was reset and to enter the previous owner's account information. Google must have really patched that version tight as a drum...
Glad it's at least working for you though.
Roger
Click to expand...
Click to collapse
Mine was RTC6303 with an earlier date than yours , I used the 4 long presses to get into developers mode and it worked.... Russ
an old thread but figured id add a note in case anyone comes looking later :
go through setup, enter wifi and when it comes up asking for previous owners info, hit back till you get to wifi screen, click on 'add wifi' then hit a few random characters, click and hold on the characters and then select 'ASSIST'.
When new window opens up, type chrome and select the chrome app when it shows in the dropdown menu, download and install google account manager 6.0.1 apk, then download and install quick shortcut maker, open quick shortcut maker and then type 'google account manager' in search bar. click on this and then from the options that open, select the 1 that ends with 'loginactivity' and then select 'Try IT', from the new screen that opens up, click the 3 dots at top right of screen and select 'Browser Sign-in'. Log in with your Google credentials, once it goes back to the quick shortcut maker screen, use power button to restart tablet, proceed through setup as per normal and instead of going to the google login screen, itll come up stating that your new accounts are ready for use.
once you have went through setup fully, goto settings and factory reset the tablet, this will get the tablet to a 'brand new out of the box' state and remove those previous credentials from your legally purchased 2nd hand tablet
It worked!
Thank you your instructions worked perfectly.
Hi there! So happy to see that this post was updated!!
I found a bit of a quicker way to get through the FRP issue thanks to everyones comments.
1. Connect to wifi
2. Back out and click add new network. Type some letters and highlight, click on Assist.
3. In the search box start typing Settings and wait for the settings app to appear. Click that.
4. Go to Back up and Reset. Click Factory Reset which will delete the connected google account.
Thanks guys! Also plugging in a mouse made it way easier to zip through all the steps.
So I do everything that all of you have tried and it wont work. I got the tablet from my grandmother who passed away. I am getting more irritated with the device as I do not have the money to buy a new one. I do as everyone says to do however there is no assist button at all when I highlight everything.... help please.... Im pulling my hair out over this
I found the easiest way to get into settings, theres a button on the keyboard with the settings icon, press it and it takes you straight to the settings menu.
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