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

Issue 862798 link

Starred by 1 user
Status: Available
Owner: ----
Cc:
█ jlklein@chromium.org
khorimoto@chromium.org
█ jhawkins@chromium.org
hansberry@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Remove newly invalid hosts from Mobile Data list

Project Member Reported by hansberry@chromium.org, Jul 11 
Context: b/80411125

If the phone initially tells the Chromebook that it can serve as a Tether host (i.e., it returns TetherAvailabilityResponse.TETHER_AVAILABLE [1]), and then for some reason in a later host scan, tells the Chromebook that it can no longer serve as a Tether host (case in point, it returns TetherAvailabilityResponse.NO_RECEPTION [2]), the Chromebook currently does not remove that host from the list of potential hosts in the Mobile Data list.

Comment 1 by khorimoto@chromium.org, Jul 11 

This already does occur: https://cs.chromium.org/chromium/src/chromeos/components/tether/host_scanner_operation.cc?q=IsTetheringAvailableWithValidDeviceStatus

However, the "active" host (i.e., the one being connected) is *never* removed, since it is shown in the UI as connecting. So, if a connection is in progress and during that connection attempt, NO_RECEPTION is returned, it stays in the list. This is probably what occurred in this situation.

Comment 2 by hansberry@chromium.org, Jul 11 

That is not what I'm observing. The device is not the active host, I see in the logs "Received TetherAvailabilityResponse from device ... which indicated that tethering is not available", and the device remains in the Mobile Data list.

Comment 3 by hansberry@chromium.org, Jul 11

Cc: hansberry@chromium.org
Owner: ----
Status: Available (was: Assigned)

Comment 4 by marcuskoehler@chromium.org, Jan 15

Labels: Enterprise-Triaged
►

Sign in to add a comment