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

Issue 828511 link

Starred by 3 users

Issue metadata

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



Sign in to add a comment

Minnie : Unable to connect fitbit zip from the fitbit app

Project Member Reported by pbath...@chromium.org, Apr 3 2018

Issue description

Chrome Version: 65.0.3325.184 / 10323.62.0

What steps will reproduce the problem?
(1)Open fitbit arc++ app
(2)Try to add fitbit zip device from the app


What is the expected result?

The device should connect and sync with the app

What happens instead?

The zip device is shown as found and but unable to connect with the app.

Please use labels and text to provide additional information.

Attached all the logs from the machine


 
dmesg.log
82.8 KB View Download
chrome
137 KB View Download
bt_messages
3.1 MB View Download
user_chrome.log
211 KB View Download
ui.LATEST
11.2 KB Download
messages
3.8 MB View Download
Screenshot 2018-04-03 at 11.00.38 AM.png
49.8 KB View Download
Screenshot 2018-04-03 at 10.59.06 AM.png
105 KB View Download
btsnoop.log
285 KB View Download
Status: Assigned (was: Untriaged)
Thanks Pramod for the logs!

The connection failure was caused by the same "Unknown Connection Identifier" error. However, Since Minnie uses Broadcom BCM4354, we may need to conduct more experiments before we make sure it is a firmware issue.

Pramod, I will provide you with a new Minnie test image in which the supervision timeout would be lengthened from 2 seconds to 4 seconds. And let's see if this mitigate the issue.
Hi Pramod, Miao has a patch (https://chromium-review.googlesource.com/#/c/chromiumos/third_party/kernel/+/1000097/)
landed on "10568.0.0" which is supposed to mitigate the issue.

Could you test fitbit again with a version newer than "10568.0.0"? Thanks!

Hi Joseph,

I checked on 10569.0.0 build on minnie and faced the same connection issue as in #0.
Hi Pramod, thanks for your prompt action! Would you please also capture logs so that I could double check? Thanks!
Hi Pramod, I know the reason now. The patch in C#3 is for kernel 4.4 only while Minnie uses kernel 3.14.

Please wait until the patch lands on kernel 3.14. Thanks!
Hi Pramod, Miao's CL has landed to kernel 3.14 on R68-10582.0.0. Could you please help test again? Thanks very much!
Hi Joseph,

I checked on 10585.0.0 build on minnie and found the connection error.

PFA the logs
bt_messages
3.8 MB View Download
user_chrome.log
201 KB View Download
ui.LATEST
4.1 KB Download
messages
4.3 MB View Download
dmesg.log
85.4 KB View Download
chrome
90.4 KB View Download
btsnoop.txt
873 KB View Download
Hi Pramod, thank you for the logs. The btsnoop.txt log is what I need to look at. However, its did not capture the time interval that the connection/disconnection was happening. Could you please capture the log again? Thanks!
Hi Joseph,

PFA the btsnoop.txt file.
btsnoop.txt
617 KB View Download
Hi Pramod, I am sorry that I did not explain clearly. I would need the logs captured when Minnie connects and disconnects the fitbit device. In the log above, I only saw scanning data.

BTW, I need both the btsnoop log and the messages log. Thanks!
Hi Joseph,

On 10585.0.0 / 68.0.3397.0 build, the fitbit app doesn't detect that we have a fitbit device nearby. Even though we have the fitbit zip device on and next time to chromebook we see same error message ( refer attached screenshot)
Screenshot 2018-04-19 at 4.27.39 PM.png
250 KB View Download
btsnoop.txt
839 KB View Download
messages
1.8 MB View Download

Sign in to add a comment