"Ok Google" reenables on Android after restart
Reported by
mahe...@googlemail.com,
Dec 13 2016
|
|||||
Issue descriptionSteps to reproduce the problem: 1. Click Google Apps/google 2. Click settings-->Voice-->"Ok Google" detection 3. Turn *everything* off. STOP LISTENING 4. Reboot your phone 5. Wait a while/ open google mail/ just put the phone to sleep for 30 secs 6 open the home screen with Google search and that bloody "Ok Google" is there again :-( What is the expected behavior? I should be able to get rid of the intrusive "Ok Google" and if there is any justice in the world you'll stop listening. What went wrong? The OFF button(s) are not honoured :-( Did this work before? Yes The one before this Chrome version: 54.0.2840.85 Channel: n/a OS Version: 6.0.1 Flash Version:
,
Dec 13 2016
This would be an Android OS (or perhaps Google Search App) bug, not a Chrome bug. But, on Android 7.1.1, I can't reproduce it. I turned voice search off, rebooted, and found that indeed it stayed off.
,
Dec 13 2016
Ok, good be wrong forum but thanks for the response. I too reboot and see it still disabled but put the phone to sleep for a min or open GMAIL and exit and I see "Ok, Google" again not you? Same versions?
,
Dec 13 2016
,
Dec 13 2016
Does this need to be restricted ? This is a privacy bug and doesn't seem like it needs restricted visibility.
,
Dec 14 2016
Re: #5 The answer is no but it's useful for garnering interest in a topic when you post a link and someone is prevented from seeing it :-) It's probably a simple regression bug but IT News may spin it as "Google eavesdrops on the world". "Won't take no for an answer" "Big Brother is alive and his name is Google" yadda, yadda, yadda
,
Dec 14 2016
BTW. I don't have to turn the phone off to reproduce behaviour. Just reboot go to homescreen with Google search and in 30secs "Ok Google" re-appears.
,
Dec 14 2016
I'm going to mark this public since it's not an exploit subject to time sensitivity of the fix. This bug is also in the Android OS or Launcher and not with Chrome. The bug should probably be reported to Android instead: https://code.google.com/p/android/issues/entry?template=User%20bug%20report But since you already reported it here perhaps klobag@ can route this to the Android team for us. Then we should probably mark this WontFix in the Chromium tracker once it's tracked by android elsewhere.
,
Dec 14 2016
Thank-you.
,
Dec 14 2016
,
Dec 14 2016
This is actually Google Search issue. We have reported it internally. Close this here.
,
Apr 7 2017
I know it's not your (chrome) problem but it's still happening :-( |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by elawrence@chromium.org
, Dec 13 2016