7 Support for a new Device

vanous edited this page 2020-07-28 10:20:33 +02:00

Table of Contents

• For users or device support enthusiasts
• For device or firmware makers

For users or device support enthusiasts

In theory we want to support all good and wide-spread devices.

In practice, someone needs to have the time and the information to implement support for it. If the communication protocol is open, or at least documented somewhere, adding support is rather easy. Ideally, devices would even use standard bluetooth services that we could support in a generic way, with few device specific additions.

We do encourage and support the implementation for new devices.

When requesting support for a new device, please add the label device request to it. If you found documentation or even a specification about the protocol, please reference it. Such documentation very much increases the probability of supporting the device in question with Gadgetbridge.

If you want to learn how to add support for a new device into Gadgetbridge, head over to https://codeberg.org/Freeyourgadget/Gadgetbridge/wiki/New-Device-Tutorial

For device or firmware makers

If you are looking for an existing "standard Gadgetbridge protocol", to be used inside your gadget, it doesn't exist. For some inspiration, you can look for example at the implementation of Bangle.js. Even better, first study the official Bluetooth GATT services specification. Some of these services are automatically detected by phones and other devices, and might not require a companion app, for example in order to display things like battery status or push music metadata. Then, follow the https://codeberg.org/Freeyourgadget/Gadgetbridge/wiki/New-Device-Tutorial

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
  • Casio GB-5600B
  • Casio GB-6900B
  • Casio GB-X6900B
  • Casio GBD-200
  • Casio GBD-H1000
  • Casio GBX-100
  • Casio STB-1000
• 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
  • InfiniTime
• Sony Wena 3
• SMA
• WithingsSteel

Wireless Earbuds

• Galaxy Buds
• Nothing Ear (1)
• Sony Headphones

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

• Brainstorming new UI
• Activity Analysis

FAQ

• Frequently asked questions
• Log Files
• Data Export, Import and Processing
• Multiple devices
• When will a new release appear on f-droid
• SMS notifications are lost somewhere
• Incoming call notification on Lineage OS
• Failed to start background service

Download Donate Homepage Blog Wiki