New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 664654 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Jun 2017
Cc:
█ mariakho...@chromium.org
Components:
EstimatedDays: ----
NextAction: 2018-01-09
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

Add aqs to voice queries

Project Member Reported by mariakho...@chromium.org, Nov 11 2016 
Currently java sends voice queries autocomplete URLs without adding an aqs parameter since it doesn't go through the native autocomplete code.

Consider adding AQS in java for those queries.

Comment 1 by mpear...@chromium.org, Jun 22 2017

Labels: Needs-Feedback
Do we have any metrics for voice search usage?  I don't see anything in UMA, and if we don't have this on the search side (aqs), then do we have any idea of usage?

Comment 2 by mpear...@chromium.org, Jun 22 2017

Labels: -Needs-Feedback
NextAction: 2018-01-09
Nevermind, I found the user action MobileOmniboxVoiceSearch.

That said, I'm not sure what value this would have.  Most of the aqs fields we cannot fill in because the user isn't presented with a list of suggestions.  Perhaps the only purpose would be to help annotate in Google's Search logs which queries come from voice?  That doesn't seem that critical to me.

Comment 3 by mpear...@chromium.org, Jun 22 2017

Cc: mariakho...@chromium.org
Owner: ----
Status: Available (was: Assigned)
Opening up this bug to anyone.

Comment 4 by mariakho...@chromium.org, Jun 22 2017 

Yeah, having some classification data for the queries was the thought behind it. Definitely low priority to the level of where it might make sense to just close it until we actually need this data for something.

Comment 5 by mpear...@chromium.org, Jun 22 2017

Status: WontFix (was: Available)
I'm going to close it.  I cannot think of a problem this solves.

Comment 6 by monor...@bugs.chromium.org, Jan 9 2018 

The NextAction date has arrived: 2018-01-09
►

Sign in to add a comment