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

Issue 702810 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
User never visited
Closed: Apr 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Feature

Blocked on:
issue 702772



Sign in to add a comment

Get Help app: configure "device type" signal

Project Member Reported by morsed@google.com, Mar 17 2017

Issue description

Similarly to how the managed device ( crbug.com/682837 ) and playstore ( crbug.com/644432 ) signals were added recently for use by the Get Help app, also add a new parameter to chromeosInfoPrivate for device type ("chromebook", "chromebit", "chromebox", etc).

Once signal added to chromeInfoPrivate ( crbug.com/702772 ), configure Get Help app to pass this new parameter to gKMS/Redwood/Support API in calls for data. 


 

Comment 1 by morsed@google.com, Mar 21 2017

Status: Assigned (was: Untriaged)

Comment 2 by morsed@google.com, Mar 27 2017

Status: Started (was: Assigned)
"deviceType" chromeInfoPrivate signal is ready with values of chromebox, chromebase, chromebit, chromebook, and chromedevice (chromedevice is the default for "unknown").

change landed in M59 (9399.0.0/59.0.3050.0)
Project Member

Comment 3 by bugdroid1@chromium.org, Apr 4 2017

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/chromeos-assets/+/d660ac6c2631d600e608401b0a348ea41ac7cd0b

commit d660ac6c2631d600e608401b0a348ea41ac7cd0b
Author: David Morse <morsed@google.com>
Date: Tue Apr 04 21:08:15 2017

Comment 4 by morsed@google.com, Apr 6 2017

Status: Fixed (was: Started)
Get Help app configurations for new deviceType signal landed in 9432.0.0/59.0.3055.0

Sign in to add a comment