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