Skip to content

Blog

  • in Releases
  • 2 min read

Move to codeberg.org complete, Gadgetbridge 0.40.0: Bangle.js Fossil Q Hybrid

As announced almost a year ago, we finally completely to Codeberg on 10th December 2019. Our GitHub repo is archived now, but we will resync it from time to time, so we stay visible there, no interaction will be possible on GitHub though. Please create a Codeberg account, if you want to continue interacting with us. We imported all old issues and PRs. And also assigned comments of GitHub users to their codeberg.org account where known. If you create your codeberg.org account later, we can still re-assign these to your account.

Donations via Liberapay re-opened

You can finally donate to Gadgetbridge again!

After more than a year we bit the bullet and re-enabled donations on liberapay by complying with what had to be done to make that work. We were already almost dried up and were unable to buy devices we wanted to support. To make Gadgetbridge even better please consider to donate!

  • in Releases
  • 2 min read

Gadgetbridge 0.38.0 has been released and will appear on F-Droid soon!

We added initial support the Amazfit GTR, but just like with the Mi Band 4 and Amazfit Bip Lite support, unfortunately this sounds better than it is.

WE CANNOT RECOMMEND THIS DEVICE TO OUR USERS, SINCE YOU HAVE TO INSTALL MI FIT SOMEWHERE, CREATE AN ACCOUNT AND GET A DEVICE SPECIFIC AUTH KEY FROM MI FIT ON A ROOTED PHONE

Other methods then the above might exist, but in the end you need Mi Fit with an account once, then get hold of your secret auth key, and input that in Gadgetbridge.

  • in Releases
  • 3 min read

Gadgetbridge 0.37.0 has been released and will appear on F-Droid soon!

One highlight is Makibes HR3 support was contributed by Lukas Schwichtenberg. Thank you Lukas for the great work.

We also managed to support the Amazfit Bip Lite, but just like with the Mi Band 4 support, unfortunately this sounds better than it is.

WE CANNOT RECOMMEND THIS DEVICE TO OUR USERS, SINCE YOU HAVE TO INSTALL MI FIT SOMEWHERE, CREATE AN ACCOUNT AND GET A DEVICE SPECIFIC AUTH KEY FROM MI FIT ON A ROOTED PHONE

Other methods then the above might exist, but in the end you need Mi Fit with an account once, then get hold of your secret auth key, and input that in Gadgetbridge.

  • in Releases
  • 3 min read

Gadgetbridge 0.36.0: Many small fixes and improvements and a new device!

Gadgetbridge 0.36.0 has been released and will appear on F-Droid soon!

This release accumulates a lot of fixes and small improvements and a few minor new features. Many of which came in with the help of community contributions, special thanks to @vanous who really took a deep dive into Gadgetbridge! There are some contributions which did not make it into 0.36.0 but will be in 0.36.1 which will follow soon.

Also LineageOS 16 weather provider support is back. We lost support after LineageOS had to change some internal naming from cyanogenmod. But integrating their SDK by copying a jar (their recommended way) was never an option for us. Now we bit the bullet and used some dirty tricks like reflection and copying parts of the SDK source files. Not beautiful - but it works without the jar.

Gadgetbridge 0.35.0 has been released and will appear on F-Droid soon!

The only change in the major release is Mi Band 4 support, unfortunately this sounds better than it is.

WE CANNOT RECOMMEND THIS DEVICE TO OUR USERS, SINCE YOU HAVE TO INSTALL MI FIT SOMEWHERE, CREATE AN ACCOUNT AND GET A DEVICE SPECIFIC AUTH KEY FROM MI FIT ON A ROOTED PHONE

Other methods then the above might exist, but in the end you need Mi Fit with an account once, then get hold of your secret auth key, and input that in Gadgetbridge.

Gadgetbridge 0.34.0: Per-device settings, finally

Gadgetbridge 0.34.0 has been released and will appear on F-Droid soon!

The highlight of this release is a big refactoring of device settings for Mi Band/Amazfit devices.

Since we support an increasing number of Mi Band/Amazfit devices which almost all have unique feature, it became increasingly confusing how to configure them. Take the Amazfit Cor for example. Some of the settings were in "Mi Band / Amazfit settings", others in "Amazfit Cor settings", and finally some in "Amazfit Bip" settings (historically,because the Bip introduced new features which the later released "Amazfit Cor" also has).

Gadgetbridge 0.33.0: Amazfit Cor 2 and a security fix

Gadgetbridge 0.33.0 has been released and will appear on F-Droid soon!

The highlight of this release is that we finally have per-device settings, which are currently used for storing per-device security keys on all Mi Band, Bip and Cor models. This in turn fixes a long-standing security issue, where all devices used the same security key. If you want to be sure that no one else who knows that you are a Gadgetbridge user connects to your device, change your security key by re-paring your device with Gadgetbridge (forget the device in Androids settings and press the + button in Gadgetbridge again to re-pair, data will be preserved). Per-device settings will be used for many settings in the future. This release only laid the groundwork.

  • in Releases
  • 2 min read

Gadgetbridge 0.32.0: Casio GB-6900B and per-device alarms

Gadgetbridge 0.32.0 has been released and is already on F-Droid!

The highlight of this release are are initial support for Casio GB-6900B (contributed by Andreas Böhler) and per-device alarms.

Per-device alarms also means that you can use the maximum number of alarms you device supports, no longer limited to three.

The rest of changes are mainly bugfixes and minor improvements.

This release took a bit longer than usual, since some core members where busy with other projects, like working on Codeberg, a new non-profit hosting and collaboration platform, where Gadgetbridge also moved to.

  • in Releases
  • 2 min read

Gadgetbridge 0.31.0: No more duplicate notifications

Gadgetbridge 0.31.0 has been tagged today and will show up on F-Droid (hopefully) soon.

The highlight of this release are countermeasures against duplicate and re-occurring notifications. This happened with modern chat applications when having multiple conversations at once. For some Gadgetbridge even became unusable because of that.

On the Pebble front, we also have some good news: Wearable actions that are attached to notifications are now all sent to the pebble (not only reply actions). That means you can interact better from your Pebble with some Apps.