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

Issue 921766 link

Starred by 2 users
Status: Started
Owner:
hansberry@chromium.org
Cc:
jessejames@google.com
█ jlklein@chromium.org
hsuregan@chromium.org
khorimoto@chromium.org
█ jhawkins@chromium.org
hansberry@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Jarring flickering from "can't find phone" to "select photo to unlock"

Project Member Reported by hansberry@chromium.org, Jan 14 
About 25% to 30% of time I've been using Smart Lock the past couple days, it takes a fair amount of time to communicate if the connection succeeded or not (~10 seconds?), then says "can't find phone". However, approximately 1 second later, it then displays the success text "select your photo to unlock".

The UX is jarring and weird. Needs investigation.

Comment 1 by hansberry@chromium.org, Jan 15

Status: Started (was: Assigned)
I suspect this bug is also artificially driving up our observed failures in the SmartLock.GetRemoteStatus.Unlock metric [1]. It only has a 13% success rate, with most failures caused by reason: "Timed out could not establish authenticated channel"

Smart Lock feels pretty broken with this issue. I'm going to start actively looking into it.

1) https://uma.googleplex.com/p/chrome/histograms?endDate=20181217&dayCount=7&histograms=SmartLock.GetRemoteStatus.Unlock%2CSmartLock.GetRemoteStatus.Unlock.Failure&fixupData=true&showMax=true&filters=platform%2Ceq%2CC%2Cchannel%2Cone_of%2C4%7C3%7C2%2Chw_class%2Cregex%2C%5EEVE%2Cisofficial%2Ceq%2CTrue&implicitFilters=isofficial
►

Sign in to add a comment