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

Issue 734152 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Create crosh command to enable advanced Bluetooth logging.

Project Member Reported by r...@chromium.org, Jun 16 2017

Issue description

We should have a crosh command that allows us to do the following,
a.) Turn on complete debug logging in BlueZ (this will require some changes to BlueZ)
b.) Start btmon and write to a file (we will need to ensure that the size of this log file is limited and doesn't take up a significant amount of space. We could rotate the logs or use a tmpfs?)
c.) *maybe* turn on Bluetooth logging for Chrome

This will allow us to gather Bluetooth logs from the field versus requiring folks to go to dev mode and run a bunch of commands.


As a good first step, we could create this command to work only in dev mode (this will be considerably simpler since we can just modify the .conf files and run btmon) without any size checks, expecting some user expertise.
 

Comment 1 by mcchou@chromium.org, Apr 20 2018

Labels: -M-61 M-68

Comment 2 by mcchou@chromium.org, Apr 20 2018

Owner: lepton@chromium.org

Comment 3 by mcchou@chromium.org, Apr 20 2018

Labels: -Pri-2 Pri-1
Owner: ----
Status: Available (was: Assigned)
Cc: shijinabraham@chromium.org

Sign in to add a comment