This page has moved
⚠ The wiki has been replaced by the new website - this page has been moved: https://gadgetbridge.org/basics/pairing/companion-device/
On phones running Android 8.0 (API level 26) and higher, it's possible to use companion device pairing. It is recommended to use this setting, especially on Android 10 and higher as without it for example the Find phone feature cannot work correctly.
After the device is paired using this method, the device can leverage the REQUEST_COMPANION_RUN_IN_BACKGROUND permission to start the app from the background. This provides a better way for Gadgetbridge to keep its service running, read more about background service stability here.
In the future there might be a possibility to use companion device pairing to perform a Bluetooth (or Wi-Fi) scan of nearby devices, without requiring the ACCESS_FINE_LOCATION or BLUETOOTH_ADMIN permission. This would minimize the number of permissions needed. Currently, these permissions are still required. See more details here: https://developer.android.com/guide/topics/connectivity/companion-device-pairing
To utilize this in Gadgetbridge, enable "CompanionDevice Pairing" in the settings:
Settings > Developer Options > Discovery and Pairing options > CompanionDevice Pairing
and add your new device via the 
icon.
Pairing existing devices as companion
For devices already in Gadgetbridge, you must re-pair (re-bond) them:
- Connect to the device:
- Go to the Debug activity:
- Click the "Pair current device as companion" button:
- Select OK on the Link question:
NEW WEBSITE
General
- Home
- FAQ
- ReadMe
- Configuration
- Notifications
- ChangeLog
- Widget
- Weather
- Data Backup
- Pairing
- Find phone
- Music info
- Permissions Explained
- Firmware Update
- Automation via Intents
Sports/Activities
- Sports Activities Workouts
- Activity Sessions List
- Activity and Sleep Charts
- Heartrate measurement
- Integrating Sports Tracking apps with Gadgetbridge Sports Activities/Workouts
Smart Device Related
- Bangle.js
- Casio devices
- FitPro
- Fossil Hybrid HR
- Garmin devices
- HPlus
- Huami devices
- Amazfit Active
- Amazfit Active Edge
- Amazfit Balance
- Amazfit Band 5
- Amazfit Band 7
- Amazfit Bip
- Amazfit Bip Lite
- Amazfit Bip S
- Amazfit Bip U
- Amazfit Bip 3 Pro
- Amazfit Bip 5
- Amazfit Cheetah
- Amazfit Cheetah Pro
- Amazfit Cor
- Amazfit Cor 2
- Amazfit Falcon
- Amazfit GTR
- Amazfit GTR 3
- Amazfit GTR 3 Pro
- Amazfit GTR 4
- Amazfit GTR Mini
- Amazfit GTS
- Amazfit GTS 3
- Amazfit GTS 4
- Amazfit GTS 4 Mini
- Amazfit Neo
- Amazfit T-Rex
- Amazfit T-Rex 2
- Amazfit T-Rex Ultra
- Mi Band 1
- Mi Band 2
- Mi Band 3
- Mi Band 4
- Mi Band 5
- Mi Band 6
- Mi Band 7
- MyKronoz ZeTime
- Pebble
- PineTime
- Sony Wena 3
- SMA
- WithingsSteel
Wireless Earbuds
Others
- iTag Keyring trackers
- Nut Keyring trackers
- UM25 USB Voltage meter
- VESC BLDC controller VESC
- Flipper Zero Multi-tool Device for Geeks
- Roidmi Roidmi/Mojietu FM Trans.
- Vibratissimo Private toy
- Shell Racing Toy RC cars
- Femometer Vinca II
Full list of supported devices
Development
- How to Release
- Developer Documentation
- BT Protocol Reverse Engineering
- Support for a new Device
- New Device Tutorial
- Translating Gadgetbridge
- OpenTracks-API
- Intent-API
Feature Discussion
FAQ
