Log File Contents
Please keep in mind Gadgetbridge log files may contain lots of personal information, including but not limited to health data, unique identifiers (such as a device MAC address), music preferences, etc. Consider editing the file and removing this information before sending the file to a public issue report.
When sharing a log file, please try to make it as short as possible. If you already had logging enabled, disable and reenable it before doing the things that you want to get logged. Disable logging when you're done with that. That way, we will not have to wade through huge log files looking for the actual relevant lines.
Log File Location
If you enable Gadgetbridge's logging in the "Settings" screen (under "Developer Options"/"Write Log Files"), the log file will be stored on your external sdcard in
Note: Up to version 0.9.4, you needed to quit and restart Gadgetbridge to make the log setting work.
Android's Bluetooth Logging (BT Snoop)
In order to capture the Bluetooth traffic, open Android's "Settings" -> "Developer options" and check "Enable Bluetooth HCI snoop log". Then perform the action that you want to capture. After doing that, uncheck the option again.
You will find the logfile at
Note: On some devices/Android versions the Bluetooth snoop log might be stored in a different location (e.g.
/sdcard/Android/data/btsnoop_hci.log for a Samsung Galaxy S5). If you cannot find the log file, you can find out the correct path with (ADB must be installed):
adb shell cat /etc/bluetooth/bt_stack.conf | grep BtSnoop
See here for further details.
Getting bt_snoop on LOS
While the above explanations are correct, getting the bt_snoop easily is a critical skill and should be as fast as possible. Pulling data with
adb bugreport, extracting the bt_snoop or even generating it with
pybtsnooz.py takes a very long time and can often result in files which actually do not contain required data. Getting the bt_snoop is super easy on a rooted phone or an open ROM, like LOS, which actually provides rooted adb access directly (no installation of super su needed) in the Developer options in settings:
- enable Developer options
- enable Android debugging
- enable Rooted debugging
- enable root adb with
adb rooton the computer
- get the log with
adb pull /data/misc/bluetooth/logs/btsnoop_hci.log btsnoop.log
To reset the log, simple erase it on the phone
adb shell rm /data/misc/bluetooth/logs/btsnoop_hci.log
- disable/enable bluetooth and then pull a new log
- Data Backup
- Permissions Explained
- Sports Activities Workouts
- Activity Sessions List
- Activity and Sleep Charts
- Heartrate measurement
- GPS recording of sports activities
- Integrating Sports Tracking apps with Gadgetbridge Sports Activities/Workouts
- Huami devices
- MyKronoz ZeTime
- Casio devices
- Fossil Hybrid HR
- How to Release
- Developer Documentation
- BT Protocol Reverse Engineering
- Support for a new Device
- New Device Tutorial
- Translating Gadgetbridge