New issue
Advanced search Search tips

Issue 726096 link

Starred by 0 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: iOS
Pri: 2
Type: Bug



Sign in to add a comment

Whispering into GLIF voice search is not performing search.

Project Member Reported by srikanthg@chromium.org, May 24 2017

Issue description

App Version: 59.0.3071.71 beta
iOS Version:  10.3.3, 10.3.2
Device: iPhone, iPad
URL: 
  
Steps to reproduce:
  1. Launch Google Chrome
  2. Tap on Mic icon in omnibox and search for any query (This is only to make sure voice search is working)
  3. Now tap the mic icon again and whisper softly same query
 
Observed results: Observe that the search query is displayed correctly on the screen, but search is not performed. Stuck at this screen for long time with the GLIF animation playing at the bottom of the screen.
Chrome waits in this screen for long time and then voice search is dismissed automatically after sometime.
 
Expected results: Voice Search should be performed soon after finished speaking. 
 
Note: iGSA is handling it correctly. Also note, if I clear throat at the end of it, then voice search is performing :)
 
 
Number of times you were able to reproduce: 5/5
Bug reproducible after clean install: Yes/No
Bug reproducible after clearing cache and cookies: Yes/No
Bug reproducible on Chrome Mobile on Android: Not tested
Bug reproducible on Safari/Firefox: Firefox: NA, Safari: NA
Bug reproducible on current stable build (App Version, iOS Version): M58 YES
Bug reproducible on the current beta channel build (App Version, iOS Version): M59 YES
 
 
Link to video/image: https://drive.google.com/file/d/0B-xmXLQhjeKuZGh0enlURTkxRDQ/view 
 
Status: ExternalDependency (was: Untriaged)
This is due to S3Kit and the speech recognition backend.  The volume differential between speech and quiet is small enough that it's not recognized that the query has ended.  I've created a buganizer bug to reflect this issue: b/62065667
Owner: kkhorimoto@chromium.org
Status: Assigned (was: ExternalDependency)
According to the buganizer bug, this can be fixed on our end.

Sign in to add a comment