Gadgetbridge

Gadgetbridge 0.90.0: New devices, stronger sync, and workout fixes

José Rebelo — Sun, 22 Mar 2026 00:00:00 +0000

Gadgetbridge 0.90.0: New devices, stronger sync, and workout fixes¶

This release adds support for several new watches and trackers, improves workout and chart handling across multiple devices, and delivers a large batch of Health Connect and stability fixes.

It also contains many reliability and day-to-day usability improvements: fewer sync edge cases, better activity summaries, and many targeted fixes for Garmin, Huawei/Honor, Zepp OS, Pebble, CMF, and Xiaomi devices.

New devices¶

This release adds initial support for 7 new devices:

Garmin Forerunner 935, Instinct 2S Surf, and Instinct Solar Tactical
Honor Magic Watch
Huawei Band 11
Laxasfit devices
Y6 (brandless GloryFit watch)

Health Connect improvements¶

Health Connect integration gets some bugfixes:

Fixed calories unit handling.
Fixed duplicate and truncated sleep records.
Fixed duplicate records caused by workout syncer overlap with activity sync.
Fixed sync skipping some records.
Fixed first sync of SpO2 to Xiaomi-protobuf devices

Other improvements and fixes¶

The dashboard received a new PAI widget, an option to disable dimming in the Today widget, and a weekday display
Database access performance was improved
Garmin activity summaries now include recovery heart rate and rate of perceived exertion, timezone-related activity over-counting was fixed, and resting heart rate now uses the current-day value from the watch
Huawei and Honor devices gain VO2 Max support where available, along with workout-processing fixes
Xiaomi-protobuf calorie charts were fixed.
Xiaomi Smart Band 9 Active activity fetching was fixed
Zepp OS has improved notification pictures, and can now parse swimming details and water temperature. Chart handling was refined as well, including a better VO2 Max range and fixes for

The entire list of changes and fixes can be found in the CHANGELOG file in our repository.

Get It Now¶

You can get the latest release from F-Droid, IzzyOnDroid and on our releases page.

If you install Gadgetbridge directly from our releases page you will need to track updates manually! To be sure that you're running an updated version we recommend the use of an app repository like F-Droid or IzzyOnDroid. Another alternative is to use Obtainium to download and update directly from Codeberg.

Thanks to our community and contributors for keeping Gadgetbridge growing!

The Gadgetbridge Team

Gadgetbridge 0.89.0: Two big new features

Arjan Schrijver — Tue, 10 Feb 2026 00:00:00 +0000

Gadgetbridge 0.89.0: Two big new features¶

This release introduces two big new features: Health Connect and internet access! Wait... Sharing health data?!? Internet access?!? Isn't Gadgetbridge fully private and offline? Yes it is! Now, however, you can opt in to allowing your devices to access the internet in a way that is fully under your control. Read on for more details!

As usual, this release also contains support for many new devices, varying from smartwatches and bike computers to another solar energy storage system, and several smaller features and bug fixes.

Health Connect¶

In response to increasing questions from our community to be able to sync health data with external apps/systems, we actively worked together with a few contributors (mostly Merow and LLan) to make this integration a reality.

Health Connect is Android's own health data middleman that can connect providers and consumers of health data in a privacy preserving way. It has been open source and integrated into Android itself since Android 14. Still, we have been extra careful to make sure all required code is inactive when the integration is disabled.

One example of what can be done with this integration is something that has been requested a lot: sync steps with Home Assistant. With Gadgetbridge as data provider and the Home Assistant app as data consumer, no extra tools or scripts are needed to sync your steps with your Home Assistant instance.

More information can be found on the dedicated page on our website.

Internet access¶

This is another big new feature that seems somewhat out of place in Gadgetbridge. Ever since the first commit of the Gadgetbridge code in early 2015, the single biggest privacy measure has been the complete lack of internet connectivity by the means of not requesting the Internet access permission from Android. This is not changing with this release and it's not planned to ever happen.

For a few years, we've been hearing from some Gadgetbridge users who, while not trusting big tech providers or their device vendors with full access to their health data, lacked the convenience of accessing the internet.

Although it took us a long time, we strongly believe that our current internet access solution has been designed in such a way that it will keep everyone happy. The feature has been implemented in an optional separate add-on app. If you don't want or need internet, just don't install the add-on app and nothing changes. However, if you'd like to have access to an app store for installing watch apps, or want watch apps to be able to have internet access, that's possible now too. These new possibilities are now available for Pebble and Bangle.js devices.

With the basics in place to provide fully optional internet access to Gadgetbridge and devices, we have also made sure to make every internet connected feature opt-in by default. We even have a 'firewall' in place for devices like Garmins to be able to have a domain-level allowlist for the URLs they request. In the future, further features like syncing with self-hosted fitness trackers might be added using these building blocks.

More information can be found on the dedicated page on our website.

New devices¶

In this release we added support for almost 25 new devices. As usual several watches from Garmin are newly supported, and there many others like the CMF Watch Pro 3, several GloryFit watches and the Mi Band 4C. In the headphones category we now support the CMF Buds 2 and the Samsung Galaxy Buds 3 Pro.

And we have even more for Garmin fans: support for several Edge bike computers was also added, and the GPSMAP 66s handheld GPS computer.

Perhaps more interesting for some are the more special devices we now support, like the Sanitas SBM67 / SilverCrest SBM67 blood pressure meter and OneTouch blood glucose meters. But the biggest outlier in this release is the Zendure SolarFlow, a solar energy storage system.

Other improvements and fixes¶

Apart from the big features and new devices, we have also been busy with several smaller improvements and of course bug fixes. This section mentions some noteworthy changes.

For Amazfit/Huami, third-party real-time heart rate support was restored on several models, workout charts were improved for non-GPS activities, and Helio Strap detection can now be fine-tuned. Garmin devices benefit from better connection reliability, improved handling of activity and health metrics like VO₂ Max and sleep, and many fixes when processing activity files.

For CMF and GloryFit, activity parsing and settings were improved, several long-standing bugs were fixed, and GloryFit gained experimental SOS contact support. Pebble received weather fixes, app and watchface previews, and support for newer icons and additional watchfaces. Zepp OS adds new activity types such as e-bike and jump rope, along with fixes for weather, HRV, notifications, and barcode handling.

Other device improvements include fixes for Huawei Watch Fit syncing, added raw ECG data syncing, sunrise/sunset and resource upload support for InfiniTime, chart cleanup for Polar devices, and new settings for Marstek solar panels.

This release also includes many UI and charting improvements, such as new workout list filters, clearer and more accurate charts, better dashboard behavior, and faster, more reliable zip exports. Several long-standing UI glitches and stability issues were resolved. For developers and advanced users, our Debug screen has been completely revamped.

The entire list of changes and fixes can be found in the CHANGELOG file in our repository.

Get It Now¶

You can get the latest release from F-Droid, IzzyOnDroid and on our releases page.

Our Internet Helper add-on app can be downloaded from the releases page (manually or with Obtainium) and soon also from F-Droid and IzzyOnDroid.

Thanks to our community and contributors for keeping Gadgetbridge growing!

The Gadgetbridge Team

Gadgetbridge 0.88.0: New devices and key fixes

Gadgetbridge — Fri, 12 Dec 2025 00:00:00 +0000

Gadgetbridge 0.88.0: New devices and key fixes¶

The latest Gadgetbridge release, version 0.88.0, brings a number of improvements, new device support, and some important bug fixes. While the update isn't a game-changer, it certainly enhances the app's reliability and broadens its compatibility with wearables and fitness devices. If you're a regular user of Gadgetbridge, this update will improve your experience with smoother connections, better functionality, and expanded device support.

Expanded Device Support¶

The biggest takeaway from Gadgetbridge 0.88.0 is the increased device compatibility. This release introduces initial support for several new devices, allowing users to connect with even more smartwatches and fitness trackers.

Amazfit GTS 4 Mini New, T-Rex 3 Pro, and Pebble 2 Duo/Time 2 are now supported.
Several Garmin devices are also included, such as the Edge Explore, Descent G2, Forerunner series, and Fenix 6 Pro models.
New support for FitPro devices and the Sony WH-CH720N headphones.
If you're using Huawei wearables, you'll now find support for the Huawei FreeArc and Watch GT 6 Pro.
Lesser known devices like IMIKI Frame 2 and S52 (GloryFit) are also supported.

Bug Fixes and Stability Enhancements¶

Alongside the added support for new devices, this release also tackles a number of bug fixes to improve device connectivity and stability.

Amazfit GTS and T-Rex 3 Pro device discovery issues are fixed.
Coospo HW807, Even Realities G1, and C20 also benefit from improved device discovery and better connection reliability.
Several Bluetooth adjustments reduce pairing failures and dropped connections.

These changes won't be noticeable to all users, but they should remove some frustrations for those affected.

Garmin Updates: New Features and Bug Fixes¶

For users with Garmin devices, this update brings several useful enhancements:

New charts for respiratory rate, temperature, and diving depth provide clearer activity insights.
Added debug support for fetching DEVICE_XML, which helps with troubleshooting.
Improved handling of training load, plus a fix for the real-time settings crash.
Additional fixes cover feels-like temperature, diving activity maps, notifications on recent firmware, and legacy fit file decoding.

Huawei-Specific Features: Health and Fitness Improvements¶

Huawei users see a notable set of changes:

Arterial Stiffness Detection and ECG are now active (though not yet synced).
More detailed health metrics—HRV, sleep stats, resting HR, and emotions—are now accessible.
Added support for step-by-step navigation and notification pictures.
Weather data issues for wind, UV index, and speed have been fixed.
Workout parsing for swimming and jump rope is improved.

Miscellaneous Fixes and Enhancements¶

Several smaller improvements help polish the experience:

Maps now offer biker, dark, and indigo themes.
Better GPX parsing and improvements to workout detail reprocessing.
Reduced notification spam from Microsoft Teams and WhatsApp.
Fixes for crashes, icon mapping, and issues like sending GPS/time data on Huawei devices.

Get It Now¶

As always, you can get the latest release from F-Droid. In addition, since the previous release (0.87.0) you'll also find binaries on our releases page and on IzzyOnDroid.

Thanks to our community and contributors for keeping Gadgetbridge growing!

The Gadgetbridge Team

Gadgetbridge 0.87.1: A Small Regression Fixed and Double the Fun!

Daniele Gobbetti — Sun, 05 Oct 2025 00:00:00 +0000

Gadgetbridge 0.87.1: A Small Regression Fixed and Double the Fun!¶

This minor update resolved an issue with parsing weightlifting workouts on Garmin watches. It also marks the first release where users of the main F-Droid repository can install our self-signed build.

As announced in the previous blog post, we worked on adding our self-signed builds to the main F-Droid repository, and we achieved that goal in time for this release.

Starting with version 0.87.1, you should see two cards for each release when accessing F-Droid, and the "Suggested" card should be the one signed by us. Please note that you will not receive updates any faster in the main F-Droid repository because the publishing process still depends on their infrastructure to build and verify each release.

Installing our signed build allows you to switch to other repositories that publish updated releases faster, such as IzzyOnDroid without needing to reinstall the application.

In recent months, the functionality of exporting all your data from Gadgetbridge has been significantly improved and should work flawlessly for most setups. If you want to migrate from the F-Droid signed build to our own, we advise you to use the zip file export functionality. Verify the contents of the archive on your phone or computer. It should contain "database," "files," and "preferences" folders, as well as a "gadgetbridge.json" file in the base path. The database file should be the largest file in the archive. If you are confident that the contents of the ZIP file are correct, you can uninstall the application and install the suggested version from the main F-Droid archive. You don't have to (and shouldn't) delete any of your Bluetooth devices!

If you have any questions, feel free to ask for advice in our Matrix channel. Remember that the exported archive contains a lot of your personal information, so keep it private!

Gadgetbridge 0.87.0: Many new devices, improvements and official builds

Gadgetbridge — Sun, 21 Sep 2025 00:00:00 +0000

Gadgetbridge 0.87.0: Many new devices, improvements and official builds¶

Highlights¶

New device support: Amazfit Active 2, Garmin (multiple models + diving), Xiaomi, Polar, Nothing Ear (a), Shokz, Soundcore, and more
New workout charts: cadence, elevation, HR, power, speed
Huawei: TruSleep sync support on newer devices
Garmin: New sync protocol, improved activity/workout handling
New pairing flow, automatic ZIP export, and easier GPX track naming
Official Gadgetbridge-signed builds, alongside F-Droid

New Device Support¶

Gadgetbridge 0.87.0 introduces initial support for a wide range of wearables, smart bands, headphones, sensors, printers and scales. Some highlights include:

Amazfit Active 2 Square, Helio Strap & Ring, Amazfit Balance 2 (experimental)
Garmin: Descent Mk3, Fenix 3/6X Pro, Forerunner 165 Music & 945, Instinct Tactical, Venu X1, Vívoactive 6, Vivomove Sport, Vivosmart 3, Edge 540, eTrex SE, inReach Mini 2, HRM 200 — plus initial diving support
Xiaomi / Redmi: Smart Band 9 Active, Band 10, Watch S4, Watch 5, Smart Band 3 (experimental)
Other wearables and sensors: Colmi R07/P76/P80/V76, Coospo H6/HW9/HW807, Polar H9, Haylou Watch 2 Pro, Shokz OpenSwim Pro, Soundcore AeroFit 2, Nothing Ear (a), Yawell rings R10 & R11, and more
Generic device support: heart rate sensors, thermal printers, and weight scales

Better Health & Fitness Monitoring¶

Several improvements make workout tracking and health monitoring more useful:

New workout charts: cadence, elevation, heart rate, power, speed
Huawei: TruSleep support on newer devices (HarmonyOS 5+), improved workout parsing, recovery heart rate, better activity syncing
Garmin: New sync protocol, activity fetch progress, split FIT files by type/year, alarms from phone on older watches
Charts: Sleep stage overlays (HR, SpO₂, temperature, respiratory rate), training load, improved averages

Internal Changes and Fixes¶

New pairing flow: Auth key activity during setup
GPX improvements: Rename track before uploading, save OpenTracks recordings
Automatic ZIP export for easier backups
UI improvements: Settings search, simplified permissions, faster workout list
Bluetooth: More reliable connections and reconnections for BLE, BTBR, and BT Classic
Fixes: Crashes (calendar, firmware, maps), disconnections, music player issues, translations, and more

Distribution Changes¶

For a long time, Gadgetbridge has been fully reproducible: anyone could rebuild our app from source and verify that the result matched the official F-Droid releases.

With this release, we have taken the next step and introduced our own signing keys, after finally defining a clear process that allows Gadgetbridge core developers to securely handle these keys in a robust way which also ensures the needed resilience.

What this means for you:

We now publish official builds signed by the Gadgetbridge team on Codeberg in addition to the F-Droid builds which continue to be signed with their keys.
You can install and update Gadgetbridge directly from our signed APKs, knowing they are verified and backed by our team.
Reproducibility remains: anyone can still build from source and check that the APKs match.
IzzyOnDroid has already added support for our official build and published it.
Additionally, other third-party stores may start offering Gadgetbridge using this mechanism, which ensures that their users are running a safe binary. If you were previously using a third-party build, we warmly invite you to switch to our own signed build for safety reasons, and we ask that you notify your store to update their sources.

In short, this gives users faster updates, more flexibility and trust — without compromising the openness and transparency Gadgetbridge is built on.

Important note for users currently using Gadgetbridge installed from F-Droid: Due to Android's signature system, you cannot directly update the F-Droid version with the Gadgetbridge-signed APKs. F-Droid will keep providing you with updates just as it always has done.

Work is already in progress to add our own builds to the main F-Droid repository beside the existing version, but please note that the availability of new versions in the main F-Droid repository will still follow their release process and that builds signed by us will be available when their own builds are complete and signed.

At the moment we advise F-Droid users to keep using the version distributed via F-Droid. We will share instructions for switching (which remains optional!) as soon as our official builds are distributed via F-Droid.

Android version compatibility¶

All good things come to an end, eventually. For us, the time has come to say goodbye to Android 5 (SDK/API level 21/22. This will be our last release supporting it. We try to stay compatible with Android versions that are up to 10 years old. Android 5 was first released in 2014, making it 11 years old by now. Several of our dependencies have dropped support for Android 5, which means we can't upgrade those anymore unless we do the same. All in all, we feel the time is right for increasing our minSdk to 23 after this release.

Get It Now¶

As always, you can get the latest release from F-Droid. Starting with this version you'll find binaries also on our releases page and on IzzyOnDroid. If you install Gadgetbridge directly from our releases page you will need to track updates manually! To be sure that you're running an updated version we recommend the use of an app repository like F-Droid or IzzyOnDroid.

Thanks to our community and contributors for keeping Gadgetbridge growing!

The Gadgetbridge Team

Gadgetbridge 0.86.0 and 0.86.1

Daniele Gobbetti — Sat, 28 Jun 2025 00:00:00 +0000

Gadgetbridge 0.86.0 and 0.86.1¶

We are happy to announce the release of Gadgetbridge 0.86.0 and the follow-up bugfix release 0.86.1!

This release brings initial support for a wide range of new devices, including wearables, headphones, and fitness trackers. Users of Da Fit-based smartwatches will be pleased to see first-class support for popular models such as the Colmi V72 and V89. We have also added support for several new Garmin devices, Amazfit Active 2 NFC, and the Polar H10 heart rate monitor.

On the audio front, this release introduces support for various earbuds including the Huawei Freebuds 6, Realme Buds Air 5 Pro, Oppo Enco Buds2, and more.

Our work on Zepp OS continues, with improvements to workout parsing, moon phase icons, watchface uploads, and better time setting across time zones. Huawei device integration also sees several improvements, such as firmware update handling and better error reporting during workout sync.

Notably, the Bangle.js integration has been enhanced with improved network handling and support for version 2 weather APIs.

This release also adds experimental support for AAWireless and Huawei Watch Fit 4 / 4 Pro.

0.86.0 Highlights¶

New device support:
- Amazfit Active 2 NFC
- Colmi R12 with display
- Da Fit / Moyoung-based models: Colmi V72, Colmi V89, Colmi i28 Ultra, Advan Watch SE1 AI, C20, KT80, R50Pro, Fire-Boltt Talk, KSIX Venture, Misirun C17, Rainbuvvy T97, Viran C29
- Polar H10
- Garmin bike computers: Edge 130 Plus, Edge Explore 2
- Garmin Fenix 7X Pro, Forerunner 630, Forerunner 645 Music, Instinct 2X/3 Tactical, Vívoactive HR, Vívosmart 4
- Huawei Freebuds 6
- Huawei Watch 5
- Oppo Enco Buds2
- Pixel Buds A
- Realme Buds Air 5 Pro, Buds T100, Buds T300
- Redmi Buds 6 Pro
- Sony WF-C710N
Experimental support:
- AAWireless 1 and 2
- Huawei Watch Fit 4 / 4 Pro
- Zepp OS btrfcomm
Zepp OS:
- Better workout data parsing (pace, cadence, strength sets)
- Fixes for watchface uploads, music info, and moon icons
- Disable realtime steps to reduce sync issues
- Improved time handling with DST and UTC support
Bangle.js:
- Support for insecure TLS/HTTP requests
- Support for version 2 weather
- Improved HTTP timeout handling and XPath parsing
Huawei:
- Improved firmware update handling
- Added goal reminders and app icon uploads
- Better error handling during workout sync
Garmin:
- Improved activity renaming and file parsing
- Swimming interval parsing
- Fix for infinite loop during sync
BLE improvements:
- Fix for race conditions and pairing issues
- New option for low-power connections
- Reconnect on gadget-initiated connections
Charts & Dashboard:
- Weekly/monthly calorie and stress views
- Average day display for body energy
- Resting metabolic rate visualization
- Fix for resting calories when using multiple devices
Other notable changes:
- New icons for preferences and activities
- Ultrahuman breathing exercise support
- Improved Even Realities G1 handling
- Various fixes across Garmin, Huawei, Zepp OS, and Bangle.js

0.86.1 Bugfix¶

Fossil/Skagen Hybrids:
- Fixed a connection failure affecting these devices

As always, you can get the latest release from F-Droid.

We would like to thank all contributors, testers, and users for their continued support and feedback.

— The Gadgetbridge Team

Managing a Public End to End Room on Matrix: Lessons Learned

Daniele Gobbetti — Fri, 09 May 2025 00:00:00 +0000

Managing a Public End to End Room on Matrix: Lessons Learned¶

As you can imagine, the team behind Gadgetbridge is motivated to use and spread the use of Free Software even in areas that are only tangential to the main scope of the project. Just to name a few examples, we are using Liberapay to collect donations (to all our donors: Thank you!), and the project's initiator even created the probably most widely known publicly available free software Git (and more!) hosting in Europe run by a collective.

It is in this spirit that we share our experience in managing and running a large public end-to-end encrypted (e2ee) room on matrix.org. Please be aware that this post is primarily intended for a technical audience and not for Gadgetbridge users.

Our Room¶

A Bit of History¶

The Gadgetbridge chat on matrix.org was created as an e2ee room in November 2016.

By early 2025, there were about 1700 users in the room. Periodically we were experiencing some errors related to e2ee - "Unable to Decrypt" or UTD in matrix jargon - mostly related to users' settings ("only send encrypted messages to verified sessions" being one of the most common issues) but also depending on the protocol itself (see the Resources section for a link to the Matrix.org github issue collecting those).

Digging Deeper (also: Being Kind to Your Hosts)¶

Besides the bugs, we wanted to make sure that our room would not be a burden on the matrix.org infrastructure: an e2ee room is inherently more resource-intensive than a normal room, due to the additional (meta)data and message exchange required to enable encryption, so we reached out to some members of the encryption spec team to understand their point of view on the matter.

We've gotten confirmation that our e2ee room is in line with their whole ethos as an "encrypted communications platform", and that our room is not the cause of any problems on Matrix's part: on the contrary, feedback on how e2ee scales is useful.

Admittedly, being (one of?) the largest e2ee rooms we're somewhat on the bleeding edge and more likely to suffer from UTD messages than most.

Over time Matrix deployed several new "room versions" (cfr. Resources section). Our room has been at version 1 up until May 2025 when it was upgraded to version 11 (current default).

The little pruning (April 2025)¶

With the information collected so far, we knew that the best way to approach the e2ee issues would be to remove as much inactive users from the channel as possible, unfortunately we did not find a way to do so for every user, but we thought of an alternative approach.

The Matrix protocol allows (and encourages) federation of multiple homeservers. It should come as no surprise that in our channel we had users from 150 homeservers (i.e. not matrix.org).

Suspecting that unreachable homeservers were contributing to the problems, we performed a manual check of each participating homeserver in the room using the Matrix Federation Tester. 50 servers were found to be out of the federation, hosting 55 users (~30% of the servers and ~3% of the users). Only two of these servers had more than one user (5 and 2, respectively).

With this list of servers, we checked the last activity of their users to confirm that they were long in the past.

Finally, we removed all these stale users by entering the reason "Your homeserver is not reachable according to the matrix federation tester."

This whole process was a bit cumbersome to do by hand, and we wonder if it could be automated and made part of either /devtools or an external utility, as it would be really helpful for (e2ee) rooms admins.

Commands Used in This Section¶

check homeservers: /devtools -> view servers in room
check activity of a member by homeserver: /devtools -> Explore room state -> m.room.member -> enter the server url in the search box
remove user from room: room info -> people -> enter the server in the search box -> choose user -> Remove from room

The Room Upgrade (May 2025)¶

Pruning helped reduce the errors, so it was clear that dormant accounts were the culprit. Unfortunately, we could not find a working approach to (quickly) identify these accounts, so we decided to do a room upgrade, as it would achieve the same result.

Unfortunately - as with killing a mosquito with a cannon - there are some side effects, and we have done our best to identify and work around them as much as possible. The fact that you are reading this document is our attempt to share our findings with other interested parties so that they can focus on improving the process without reinventing the wheel.

One thing you cannot avoid is that users will lose visibility to some messages from the moment the room is destroyed until the moment they join the new room (combination of points 1 and 4 listed in the Facts section below). What we did was to announce the upgrade a few hours in advance and schedule it for an evening (in our time zones) on a festive day (in our countries), hoping that most people would be able to join the new room quickly. In our case, about 50 people joined the upgraded room before the first message was posted..

Of course, when planning the upgrade, you should coordinate with the admin/mods teams and the people who run any bots you have in your room, as they may need manual intervention to enter the upgraded room.

How To (Effectively) Announce the Upgrade¶

We decided to proceed with a combination of @room mention (to reach all the users that were already in the room when we sent the message) and adding the information in the room description which can be seen by users when they join the room.

This is the message we posted 12 hours in advance (the notice added to the room description was very similar):

This evening, at approximately 20:00 CEST this room will be "upgraded". Practically this means that a new one will be created in which all participants will be automatically invited to enter. Because of the way e2ee works each user will not be able to read the messages posted in the new room until they have joined it. We have decided to give a few hours notice so that everyone can act promptly. Please note: It is NOT necessary to send a message to the new room, you just need to enter by following the link the system will show you!

Warning

You cannot use pinned message as they cannot be read by users joining the room after they are posted (cfr. point 1 in the Facts section).

Room Upgrade Task List¶

When the time comes, you can follow our upgrade script:

Make sure that a mod/admin user is connected through a client other than Element Web.
Clean up the room description if you have customized it to announce the upgrade.
Open developer tools (/devtools) and enable "Developer mode"
Use the command /upgraderoom <desired room version>
In the NEW room: get the link to the room (open "Room info", click "Copy link")
In the OLD room: rename the room to indicate that it is an old version (we added "archived on YYYY-MM-DD" to the name), consider changing the description as well (we set it to a link to the upgraded room)
In the OLD room: the mod/admin who is not connected via Element Web should post a link to the new room for clients that do not show the upgrade message with link automatically (you need to be a mod because normal users cannot post to archived rooms, and you need to use a client different than Element Web as it will prevent you from sending messages in archived rooms, regardless of your power level)
If you had bots that are not automatically following room upgrades, invite them in the new room. They will retain their power levels.

Questions and Answers about Room Upgrade (as Experienced in May 2025):¶

What happens to room encryption?

An encrypted room will remain encrypted when upgraded.

What happens to banned users? Does the list persist?

Users that were banned in the previous version of the room remain banned.

What happens to admins (generally speaking to users with power level different than default?)

Users keep their power levels. (please be aware that different room versions might introduce different requirements for power levels)

What happens to permissions?

As we never customized permissions in our room, we have no information to share.

How long will it take to upgrade the room?

In our case upgrading an e2ee room with ~ 1700 members took a little bit less than 2 minutes (clock time).

Are there further issues to be aware of?

We experienced a problem in the Element Web Client when performing the room upgrade. The errors shown were "Server Error: fetch failed: NetworkError when attempting to fetch resource." followed by "Error upgrading room: Double check that your server supports the room version chosen and try again.". In the background, we could see that the message "This room has been replaced and is no longer active." was already posted in the room, and we were afraid that we would be stuck between the old and the new status. In fact, the server processed the request correctly, and after another admin confirmed that the new room was accessible, a page refresh in the Element Web client that initiated the upgrade was sufficient to proceed.

What happens to the room alias(es)?

The upgrade process will remove the room alias(es) from the old room and point them to the new one. (cfr. https://spec.matrix.org/v1.14/client-server-api/#server-behaviour-19)

Which target room version should I choose?

When migrating, it is recommended to migrate to the current "default" room version (see the room specifications in the Resources section). Note that although the action is called upgraderoom, it is technically possible to upgrade from one room version to any other, including the same (or a lower) one.

Why do you recommend renaming the old room and posting the link to the new one?

Some clients (including Element X at the time of this writing) will show both rooms in the users' roster. Renaming the old one allows the user to visually distinguish them. Element X also has a known issue, that is preventing users to see the link to the new room (https://github.com/element-hq/element-x-android/issues/4504 ).

Facts¶

The Room History Visibility setting is ineffective for e2ee rooms because users only have the keys to decrypt messages from the moment they join the room, and all previous messages are undecipherable to them. (This might change in the future for invited users, see Resources section).
Later room versions have various improvements or features, but improved encryption is not one of them. Changing the room version won't directly help with UTD or other e2ee quirks.
The larger the room (read: the more users in it), the more likely there are to be e2ee quirks.
Upgrading the room (see the Resources section) means that the old room is deactivated, a new room is created, and the two are linked so that clients can access the new room from the old one. The new room is initially empty because users must explicitly join it.
The room upgrade procedure does not expose an encryption toggle, an encrypted room will be upgraded to an encrypted room.

Resources¶

"unable to decrypt" github issue with instructions for users on how to report (and a list of known/solved) e2ee issues: https://github.com/element-hq/element-meta/issues/245
e2ee matrix room: https://matrix.to/#/#e2e:matrix.org
matrix rooms versions (and more): https://spec.matrix.org/latest/rooms/
Sharing room keys when inviting new users issue (proposal): https://github.com/element-hq/element-meta/issues/39
Room upgrades spec: https://spec.matrix.org/v1.14/client-server-api/#room-upgrades
Matrix federation tester: https://federationtester.matrix.org/

Bonus Chapter: Simulating the Room Upgrade Process¶

If you made it this far, congratulations! In case you prefer to double check our findings (maybe some time has passed from this article to when you are performing an e2ee room upgrade), you can create a "guinea pig" room to test. Here is how we did it.

When creating a public room (through element web) its version will be the homeserver's room default version. Activate encryption (Room settings, "security and privacy") and "upgrade" the room to your original room's server version
1. Open developer tools (/devtools) and enable "Developer mode"
2. Use the command /roomupgrade <the_room_version_you_are_migrating_from>
3. The old room should be archived and you should be in the new one. There should be a link on top that brings you to the old room.
4. Try to replicate the rest of your room status (power levels, including custom ones), ban some users just to check if ban persist, custom permissions, add any bot you are using in the main room, ...
Perform a second room upgrade to the current default version.
1. As previously the old room should be archived and you should be in the new one. There should be a link on top that brings you to the old room.
2. Check that everything is working as expected/described in this document (e.g. check the power levels, banned user list, bots etc.)
3. Verify if the limitations we mentioned still apply. E.g. that the new room's history is not visible to users that were in the old room until they actively join the new one.
You now should have all the information needed to successfully perform a room upgrade. If you found discrepancies between your experience and this document, please let us know!

Gadgetbridge 0.85.0: Offline maps, new devices and lots of fixes

Daniele Gobbetti — Fri, 18 Apr 2025 00:00:00 +0000

Gadgetbridge 0.85.0: Offline maps, new devices and lots of fixes¶

We're excited to roll out version 0.85.0 with fresh device support, new features, feature improvements and bug fixes. Of special note are the addition of offline maps in workout GPX tracks, and the support for generic unsupported headphones.

Feature highlights¶

Offline maps¶

Workouts that contain GPX tracks have for a long time shown the track without any context. This was fine and relatively useful, but what if the track would be plotted on an actual map? That would make it much more useful and would remove the need to display it in an external app.

This release adds this awesome feature, leveraging freely available downloadable maps. No internet connection needed so you keep your privacy. Just put the maps in the right directory on your phone (configurable in the preferences) and the workouts will automatically show the tracks on them. Tap on the small map to show it full screen and zoom in and out to view more details or surroundings.

And as we all know, a picture says more than a thousand words, so here are the before and after screenshots:

Generic headphones support¶

Starting with this release we support unsupported headphones! Confused yet? We understand! That's what this highlight is for, to explain the feature.

Until now, we weren't able to support older headphones and other audio devices (think for instance car Bluetooth audio) that don't have an app or even any settings. In addition, there are many headphones that aren't supported yet but could be in the future.

By adding generic support for all Bluetooth audio devices, we take a shortcut that proves useful. Any Bluetooth audio device that is already connected to your Android device can now be added to Gadgetbridge, allowing features like automatic read-aloud notifications, automatic call pickup and even battery level tracking. All without specific device support!

New Devices¶

New wearables and audio devices:

1MORE SonoFlow headphones
Amazfit Bip 6
EarFun Air S and Air Pro 4
Garmin Instinct 3
Generic Audio Bluetooth Devices
Honor Watch 4 / 4 Pro
Huawei Band 10 and FreeBuds Pro
Redmi Buds 3 Pro
Experimental support for the Ultrahuman Air smart ring

Feature Enhancements & Fixes for Existing Devices¶

Amazfit¶

Amazfit Active 2: Discovery issues fixed and support polished.
Amazfit Bip 3: Now includes GPS settings for workouts.
GTR2e: PAI (Personal Activity Intelligence) is now supported.

Bangle.js¶

Music volume sync, missed call notifications, and message handling are now more reliable.

CMF Watch Pro¶

You can now enable Bluetooth calls.

Fossil / Skagen Hybrids¶

Fixed a bug hiding the upload button in the app manager.

Garmin¶

Nap tracking, manual activity file imports, extended workout parsing, and better handling of strength training metrics.
Several FIT file fixes and improved device communication.

Huawei¶

Stress calibration, trail run activity, real-time heart rate alerts, and support for finding your device.
Improved stability, crash fixes, faster database, and more accurate workout metrics.

Mi Band 8¶

Added parsing for elliptical and rowing workouts.

Pebble¶

Fixed timezone handling for all-day events.

Zepp OS (3.0+ to 4.0)¶

Updates to: Body temperature, sleep respiratory rate, HR stats, music uploads (experimental), audio sync, maps upload, notification fixes, and much more.
Added: AGPS support, calendar sync, and extended activity mapping.

General Fixes & Improvements¶

Added open-source licenses page.
Sleep charts now show average heart rate.
Fixed crashes when switching Android profiles.
Improved media session handling, battery notifications, and preference updates.
Offline maps are now available in the Workouts section.
More responsive notifications and better app performance all around.

Gadgetbridge 0.84.0: Big Updates & New Device Support!

Daniele Gobbetti — Thu, 27 Feb 2025 00:00:00 +0000

Gadgetbridge 0.84.0: Big Updates & New Device Support!¶

Hey Gadgetbridge users!

We’re excited to announce Gadgetbridge 0.84.0, packed with new features, bug fixes, and expanded device support! Whether you’re using smartwatches, headphones, fitness trackers, or even smart glasses, this update brings more compatibility and better functionality to your favorite gadgets.

🔥 What’s New?¶

🚀 New Device Support¶

Smart Glasses: Initial support for Even G1 Smart Glasses.
Garmin Watches: Added support for Fenix 7S Pro, Forerunner 45 / 735XT, Instinct E, and Lily 2 Active.
Headphones & Earbuds: Now works with Sony WH-ULT900N, WF-C510, Soundcore Q30, and Redmi Buds 6 Active.
Smart Home: Initial support for Gree Air Conditioner units.
Experimental: Early support for the Amazfit Active 2.

📊 Charts & Tracking Improvements¶

Added weekly and monthly heart rate tabs.
New option to hide sleep and step balance.
Restored steps balance for weekly and monthly charts.

🏋 Garmin Enhancements¶

Basic FIT file viewer for workouts.
Added custom notification actions and support for PRG file uploads.
Improved workout parsing and better connectivity for newer firmware versions.

⌚ Huawei Watch Upgrades¶

Firmware updates & screenshots support.
Canned replies for quick responses.
Fixed sleep phases, calendar event updates, and time zones for all-day events.
Improved reconnection and workout parsing.

🎧 Better Headphone Integration¶

Sony Headphones: More customization, better battery tracking, and improved initialization.
Oppo Headphones: Fixed missing battery info on some models.

🔧 Other Fixes & Improvements¶

Pebble: Fixed pairing issues on Android 14+.
Colmi R0x: Added real-time heart rate and live activity tracking.
Zepp OS: Fixed activity detail parsing issues.
Bug Fixes: Resolved notification time logic, phone call issues, and media session crashes.

🔄 How to Update?¶

You can grab the latest version from: 📥 F-Droid

Got feedback or issues? Join our community discussions on Codeberg and let us know!

Thanks for being part of the Gadgetbridge journey! 🚀

Gadgetbridge 0.83.0: Merry Christmas! Here is your present!

Andreas Shimokawa — Mon, 23 Dec 2024 00:00:00 +0000

Gadgetbridge 0.83.0: Merry Christmas! Here is your present!¶

Merry Christmas! Gadgetbridge 0.83.0 has been released and should hit F-Droid soon. Even if you do not celebrate Christmas, let's celebrate this release together!😊

We have some new features, device improvements, a lot of new devices supported and of course some bugfixes.

This release adds a first start onboarding screen, to help new users to get started with our App and grant necessary permissions easily. We also added a calories charts and widgets. Additionally 0.83.0 marks the first release that supports a whole new device category, a solar battery: The Marstek B2500.

This battery can now be used without the vendor app, and allows you to configure various charge and discharge parameters and timers, without the need to extract a pairing key from anywhere. There is also a nice screen that shows the current incoming and outgoing power and of course the battery level. Support is not perfect but quite usable, and covers all essential features that need to be set-up for such an equipment.

Since we did not post about Gadgetbridge 0.82.x at all, here is a list of new device support introduced in 0.82.0:

Anker Soundcore Liberty 4 NC
CMF Buds Pro 2 / Watch Pro 2
Colmi R02/R03/R06/R10 smart rings
Garmin Enduro 3, Fenix 5/5 Plus/5X Plus/6/6S Sapphire/7/8, Forerunner 165/255/255S Music/245 Music/265S/955/965, Venu/Venu Sq/Venu Sq 2/V
Huawei Watch 3 / 3 Pro / 4 Pro / D2 / GT 3 SE / GT 5 / GT 5 Pro / GT Cyber / GT Runner
Honor Watch GS 3 / Watch GS Pro
IKEA desk controller
Moondrop Space Travel
Mijia XMWSDJ04MMC
Mi Smart Scale 2
Sony WF-C500 / WF-C700N
Soundcore Motion 300
Vivitar HR & BP Monitor Activity Tracker

0.83.0 adds support for the following devices:

Bowers and Wilkins P Series
Casio ECB-S100
Colmi R09
Freebuds 5i
Garmin Fenix 6S Pro / 7X, Forerunner 55 / 235 / 620, Instinct 2
Huawei Band 2 / 2 Pro / 3 Pro
Oppo Enco Air / Air2
Realme Buds T110
Redmi Buds 5 Pro
Xiaomi Smart Band 9 Pro
Marstek B2500

We want to thank all the contributor to this release! And also our generous donors who support us via Liberapay. Keep it going!

Donate at Liberapay

Merry Christmas everyone, we are looking forward to more exciting releases next year :)

Changelogs for since the last blog post¶

0.83.0¶

Add first start onboarding screen
Initial support for Bowers and Wilkins P Series
Initial support for Casio ECB-S100
Initial support for Colmi R09
Initial support for Freebuds 5i
Initial support for Garmin Fenix 6S Pro / 7X, Forerunner 55 / 235 / 620, Instinct 2
Initial support for Huawei Band 2 / 2 Pro / 3 Pro
Initial support for Oppo Enco Air / Air2
Initial support for Realme Buds T110
Initial support for Redmi Buds 5 Pro
Initial support for Xiaomi Smart Band 9 Pro
Initial support for Marstek B2500
Add calories charts and widgets
Add more workout icons
About screen: Copy build details on tap
Amazfit Bip 3 Pro: Fix title and sender on some notifications
Bangle.js: Fix calendar sync
Bangle.js: Fix call notification in Turkish locale
Bangle.js: Support sending activity type from Bangle
Casio GBX-100: Fix notification title
Charts: Display HR measurement gaps
Colmi R0x: Fix occasional crash on disconnection
Fix crash in some chart pages
Fix heart rate charts average and maximum value
Fix imperial unit on steps charts
Fix notifications after a notification is received with a time in the future
Fossil/Skagen Hybrids: Add SpO2 support
Fossil/Skagen Hybrids: Fix erroneous watchface downgrade
Garmin: Add intensity minutes, respiratory rate, sleep score
Garmin: Display AGPS age
Garmin: Fix weather temperature conversion to celsius
Garmin: Persist sleep score and metabolic rate
Garmin: Send notification pictures
Huawei Band 3 pro: Fix notifications
Huawei: Add HR zones configuration for non-P2P devices
Huawei: Add temperature chart
Huawei: Allow more languages to be set on the watch
Huawei: Display active calories
Huawei: Display high-resolution heart rate
Huawei: Fix watchface upload for some watches
Huawei: Improve activity parsing
Huawei: Music management
Huawei: Send weather error if there is no data
Huawei: Sync blood pressure if supported
Huawei: Sync skin temperature
Restore sleep balance on weekly and monthly charts
Test device: Add dummy activities
Workout page: Add colors to HR zones
Xiaomi Smart Band 8 Active: Fix freestyle and walking workout parsing
Xiaomi Smart Band 9: Fix outdoor cycling parsing
Xiaomi SPPv2: Fix message processing getting stuck after exception
Xiaomi-protobuf: Add resting heart rate
Xiaomi-protobuf: Fix activity sync stuck on duplicated or invalid files
Xiaomi-protobuf: Improve workout parsing
Xiaomi-protobuf: Persist RR intervals during sleep
Zepp OS: Add sleep respiratory rate chart
Zepp OS: Send notification pictures

0.82.1¶

Huawei: Improve activity parsing
Huawei Watch GT: Fix connection failure
Withings: Fix crash on connection
Improve Armenian transliterator for mixed-case words

0.82.0¶

Initial support for Anker Soundcore Liberty 4 NC
Initial support for CMF Buds Pro 2 / Watch Pro 2
Initial support for Colmi R02/R03/R06/R10 smart rings
Initial support for Garmin Enduro 3, Fenix 5/5 Plus/5X Plus/6/6S Sapphire/7/8, Forerunner 165/255/255S Music/245 Music/265S/955/965, Venu/Venu Sq/Venu Sq 2/Venu 2S, Vivoactive 3, Vivomove Trend, Vivosport
Initial support for Huawei Watch 3 / 3 Pro / 4 Pro / D2 / GT 3 SE / GT 5 / GT 5 Pro / GT Cyber / GT Runner
Initial support for Honor Watch GS 3 / Watch GS Pro
Initial support for IKEA desk controller
Initial support for Moondrop Space Travel
Initial support for Mijia XMWSDJ04MMC
Initial support for Mi Smart Scale 2
Initial support for Sony WF-C500 / WF-C700N
Initial support for Soundcore Motion 300
Initial support for Vivitar HR & BP Monitor Activity Tracker
Experimental support for Amazfit T-Rex 3
Experimental support for Redmi Watch 5 Active
Experimental support for Xiaomi Smart Band 9
Experimental support for Xiaomi Watch S3
Add all languages supported in weblate
Add BLE intent API
Add configuration for calendar lookahead
Add month and day to date of birth
Add more activity types (CMF, Garmin, Huawei, Zepp OS)
Allow configuration of notification times
Allow syncing birthdays with calendar events
Amazfit GTR 2: Enable PAI support
AsteroidOS: Fix missing weather day and set-time on connection
Bangle.js: Add canned responses
Bangle.js: Fix calendar sync setting
Bangle.js: Fix distance in activity details
Bluetooth Intent API: Add disconnect action
Casio GW-B5600: Alarms, find phone, reminders, watch settings
Casio: Fix notifications on long messages
Change device icons to use theme colors
Charts: Add button to pick date
Charts: Add charts for HRV, body energy, heart rate, steps, VO2 max, weight
Charts: Fix heart rate charts when min is set to 0
Charts: Re-design sleep, stress, PAI, workout details
Charts: Use HR from workout track file if available
CMF Watch Pro 2: Negotiate authentication key
CMF Watch Pro: Fix activity transfer
Cycling sensor: added live data view
Cycling sensor: Improve cycling data display
Dashboard: Add new widgets for stress, HRV, body energy
Dashboard: Add option to show yesterday's data in Today widget
Dashboard: Improve widget gauge resolution
Data Management: Add file manager
Data Management: Allow browse folders, open and share files
Data Management: Allow full backup/restore from a zip file
Data Management: Fix import of some preference from a backup
Fix activity charts generation for devices that do not report intensity
Fix crash when companion pairing
Fix discovery of connected devices
Fix emoji when some connected device does not support them
Fix language not being respected in some situations
Fix media controls not working for some apps
Fix notification text not being sent for some apps
Fix reconnection when device connects back during BLE scan
Fossil HR: Fix crash on disconnection
Fossil HR: Minor watchface fixes
Garmin: Display awake time during sleep
Garmin: Display HRV and body energy
Garmin: Display resting heart rate
Garmin: Fetch SKIP_TEMP files
Garmin: Fix agps upload for some URLs
Garmin: Fix all-day events
Garmin: Fix auto-activity fetch on some devices
Garmin: Fix canned replies reset to defaults
Garmin: Fix crash on call with privacy mode on
Garmin: Fix crash on timezones without DST
Garmin: Fix daily weather missing current day
Garmin: Fix weather temperature and speed units
Garmin: Improve activity, sleep and workout parsing
Garmin: Infer sleep time for devices that do not send sleep stages
Garmin: Manual HR measurements and live activity
Garmin: Map some unknown realtime settings
Garmin: Parse workout physiological metrics, strength training workout sets
Garmin: Re-parse workout summary when opening details page
Garmin: Upload gpx and workout fit files to watch
Garmin: Use distance and calories provided by the watch
Garmin: View and share gpx files
Huami: Fetch workouts during normal sync
Huami: Migrate all device settings to sub-screens
Huawei Band 9: Improved support
Huawei: Add battery polling
Huawei: Basic support for the installation of the applications
Huawei: Calendar sync support
Huawei: Contacts uploading support
Huawei: Continuous skin temperature measurement switch
Huawei: Enable emoji for HarmonyOS watches
Huawei: Fix crash when notification has no text
Huawei: Fix initialization issues on some watches
Huawei: Fix notifications for Huawei Band 4e
Huawei: Fix some reconnection issues
Huawei: Fix watchface upload, activity sync, event alarms, weather for some devices
Huawei: Fix workout altitude, pace, workout re-parsing
Huawei: Improve device initialization
Huawei: Improve watchface install support
Huawei: Improve weather support
Huawei: Initial ephemeris update support
Huawei: Map more workout types
Huawei: Music upload support
Huawei: Provide an activity sample every minute
Huawei: Re-parse workout details when opening details
Huawei: Send default HR zones
Huawei: Workout GPS synchronization
Huawei: Simple TruSleep support
Huawei: Use distance and calories provided by the watch
Improve calendar change detection
Mi Band: Migrate global preferences to device-specific
Mi Composition Scale: Add alternative bluetooth name
Mi Composition Scale: Persist and display weight samples
Mijia LYWSD/XMWSDJ: Add comfort level preference
Pebble: Migrate global preferences to device-specific
Redmi Smart Band Pro: Fix crash on connection and activity sync issues
Sony Headphones: Enable read aloud incoming notifications and auto call pickup
UI: Add new activity icons
UI: Fix changelog on device rotation
UI: Fix HR samples displayed on wrong device
UI: Fix light navbar buttons on light themes for Android 8+
UI: Fix pull-down to refresh for some devices
UI: Improvements for large screen resolutions, font sizes, landscape
UI: Reduce stutters on device changes / data fetch / scrolling
UI: Refactor preferences screen
UM25C: Fix some disconnection issues
Use default system TTS language
Xiaomi Protobuf: Allow re-parse activity from storage
Xiaomi Protobuf: Enable watchface upload for all devices
Xiaomi Protobuf: Show watchface preview
Xiaomi Protobuf: Fix watchface install on some watches
Xiaomi Protobuf: Fix deleting first widget screen
Xiaomi Protobuf: Fix naps
Xiaomi Protobuf: Improve workout parsing for some devices
Zepp OS 3: Fix file transfer (notification icons, gpx upload, agps updates)
Zepp OS 3.5 / 4: Fix shortcuts, shortcut cards, menu items
Zepp OS: Add VO2 Max support
Zepp OS: Display resting heart rate
Zepp OS: Fix reminder creation in some cases
ZeTime: Migrate global preferences to device-specific

Gadgetbridge 0.81.0: Introducing the dashboard view

Andreas Shimokawa — Fri, 05 Jul 2024 00:00:00 +0000

Gadgetbridge 0.81.0: Introducing the dashboard view¶

Gadgetbridge 0.81.0 has been released and is available on F-Droid already. This release took more than 3 month, but the wait is finally over!

The highlight of this release is the newly introduced dashboard view, which will work for all devices that somehow measure steps and/or sleep. The dashboard view will give you a nice daily overview about, steps, distance, active time, sleep, activity and exercises. Please check it out :)

0.81.0 adds support for the following devices:

Amazfit Bip 5 Unity (experimental)
Redmi Watch 4 (experimental
Cycling sensor
More Garmin watches
for Hama Fit6900
Huawei Watch Fit 2, Watch Fit 3, Watch 4 Pro
Soundcore Liberty 3 Pro

Also the existing devices received a lot of improvements and fixes, most notably Huawei, Bangle.js and Xiaomi devies, the list is too long, so please refer to the changelog below.

Changelog¶

0.81.0¶

Experimental support for Amazfit Bip 5 Unity
Experimental support for Redmi Watch 4
Initial support for cycling sensor
Initial support for more Garmin watches
Initial support for Hama Fit6900
Initial support for Huawei Watch Fit 2, Watch Fit 3, Watch 4 Pro
Initial support for Soundcore Liberty 3 Pro
Introduce new Dashboard view
AsteroidOS: Added icons to the notifications
Bangle.js: Add Sleep as Android support
Bangle.js: Add screenshot support
Bangle.js: Add setting to disable notifications
Bangle.js: Allow wake phone when opening notification response from watch
Bangle.js: Fix activity intensity normalization
Bangle.js: Fix message reply
Bangle.js: Improve text rendering
Fossil/Skagen Hybrids: Update device settings to new structure
Galaxy Buds Live: Update device settings to new structure
Galaxy Buds 2: Fix recognition of some versions
HPlus: Migrate global preferences to device-specific
Huami: Fix reminder message encoding
Huawei: Add cycling workout type
Huawei: Add enable HeartRate and SpO2 force option
Huawei: Add huawei account support (pair without resetting watch)
Huawei: Add support for workout calories and cycling power
Huawei: Add remote camera shutter
Huawei: Ask pincode only on first connection
Huawei: Enable sleep detection
Huawei: File upload and watchface management
Huawei: Fix force DND support
Huawei: Fix long notification
Huawei: Fix TimeZone offset calculation
Huawei: Improve connection and reconnection
Huawei: Improve music controls
Huawei: Improve notification icons
Huawei: Improve weather, HR and SpO2 support
Huawei: Improve workout parsing
Huawei: Rework settings menu with sub-screens
Huawei: Send user info to device
Huawei: Support sending GPS to band
Huawei Watch GT4: Add HR and SpO support
Huawei Watch Ultimate: Add HR and SpO support
Intent API: Add broadcast on activity sync finish
Intent API: Added debug end call
Mi Band 6: Add menu items for NFC shortcuts
Nothing CMF Watch Pro: Add weather support
Nothing Earbuds: Add adjustable delay for auto-pick-up of calls
Nothing Earbuds: Add option to auto-reply to incoming phone calls
Nothing Earbuds: Add option to read aloud incoming notifications
Sony LinkBuds S: Enable some missing features
Xiaomi Smart Band 8 Active: Fix discovery
Xiaomi: Add swimming workout type
Xiaomi: Allow transliteration
Xiaomi: Fix barometer
Xiaomi: Fix notification for apps in work profile
Xiaomi: Fix some crashes
Xiaomi: Improve reconnection
Xiaomi: Improve sleep and activity parsing
Xiaomi: Improve weather support, add multiple locations
Xiaomi: Sync calendar event reminders
Zepp OS: Add support for Sleep as Android
Zepp OS: Sync calendar event reminders
Add Armenian and Serbian transliterators
Add GENERIC_PHONE and GENERIC_CALENDAR NotificationType handling
Add support for scannable-only devices
Fix crash when connecting on some phones
Fix crash when enabling bluetooth
Fix receiving shared gpx files
Fix text cutoff on all checkbox preferences
Format pace as mm:ss
Make battery threshold notifications configurable
Prevent some bluetooth events from starting Gadgetbridge
Recognize "Delta Chat" as generic chat
Remove deprecated general auto-reconnect preference
Refactor location service
Set navbar color to match theme
Simplify pairing of bonded and companion devices

Gadgetbridge 0.79.0/0.79.1/0.80.0

Andreas Shimokawa — Mon, 25 Mar 2024 00:00:00 +0000

Gadgetbridge 0.79.0/0.79.1/0.80.0¶

Gadgetbridge 0.80.0 has been tagged (waiting for F-Droid to build).

After about a month after the 0.79.0/0.79.1 releases we are happy to announce the release of 0.80.0.

There is currently a steady stream of contributions, that it seems to make sense to aim for monthly releases while still having a lot to announce. Unfortunately, we did not find time to do a proper 0.79.0/0.79.1 announcement, so this blog post will mainly about 0.80.0, but still list the full changelog of 0.79.0/0.79.1.

0.80.0 adds support for the following devices:

Amazfit Bip 3
Huawei Band 8
Huawei Watch GT 4
Huawei Watch Ultimate
Sony LinkBuds
Xiaomi Smart Band 8 Active

For 0.79.0/0.79.1 the following devices were newly supported:

Huawei Watch Fit
Xiaomi Redmi Watch 3
Honor Magic Watch 2
Mijia MHO-C303
Nothing CMF Watch Pro
Sony WI-SP600N
Redmi Watch 2 (experimental)
Xiaomi Smart Band 8 Pro (experimental)
Xiaomi Watch S1 Pro (experimental)
Xiaomi Watch S1 (experimental)
Xiaomi Watch S3 (experimental)

While this is an impressive list, there are a lot of under-the-hood changes that bring improvements and bug fixes to various (or all) supported devices.

For 0.80.0 there are a lot of Bangle.js fixes and improvements and the ability to sync activity tracks. Also an important PR was finally merged, which scans for Bluetooth devices in the background and only try re-connecting to devices that were actually discovered. This also fixes problems with devices that cannot be paired in android, and therefore needed to trigger an annoying manual scan from the android settings. This feature is experimental, and therefore disabled by default. Please test it and let us know if you have any problems using it!

As always, thank you for your support, your code contributions, donations and feedback!

For more details please refer to the following changelog for the releases since the last blog post on 0.78.0

0.80.0¶

Initial support for Amazfit Bip 3
Initial support for Huawei Band 8
Initial support for Huawei Watch GT 4
Initial support for Huawei Watch Ultimate
Initial support for Sony LinkBuds
Initial support for Xiaomi Smart Band 8 Active
Bangle.js: Allow saving files on phone from watch
Bangle.js: Fix crash when file save is cancelled
Bangle.js: Set filename on save file dialogs
Bangle.js: Improve communication stability
Bangle.js: Sync activity tracks
Bangle.js: remove unwanted charaters from calendar events
Femometer Vinca II: Add temperature charts
Fossil/Skagen Hybrids: Remove activity fetching toasts and add finished signal
Fossil/Skagen Hybrids: Use steps instead of calories for activity intensity
Fossil/Skagen Hybrids: Mark device busy and show transfer notification while syncing
Huami/Zepp OS: Fix activity sync getting stuck sometimes
Mi Band 1/2: Fix vibration settings preference screens
Huawei: Add cycling workout type
Huawei: Add smart wakeup interval
Pebble: Fix pairing with LE counterpart
Xiaomi Watch S1 Pro: Add temperature charts
Xiaomi: Fix sleep sync failing when sleep stages are not found
Xiaomi: Improve activity sync
Nothing CMF Watch Pro: Fix music playback status
Allow for device settings sub-screens
Device connection: Add support for scan before BLE connection
Misc UI improvements (alarms, chart settings)

0.79.1¶

Initial support for Huawei Watch Fit
Initial support for Xiaomi Redmi Watch 3
Fossil/Skagen Hybrids: Fix crash on multi-byte unicode characters in menu
Huawei: Add weather support
Bangle.js: Support higher MTU
Test Device: Add fake features and data
Periodically (around every 2 days) synchronize time on connected devices
Set alarm as used and enabled if time has changed

0.79.0¶

Initial support for Honor Magic Watch 2
Initial support for Mijia MHO-C303
Initial support for Nothing CMF Watch Pro
Initial support for Sony WI-SP600N
Experimental support for Redmi Watch 2
Experimental support for Xiaomi Smart Band 8 Pro
Experimental support for Xiaomi Watch S1 Pro
Experimental support for Xiaomi Watch S1
Experimental support for Xiaomi Watch S3
Galaxy Buds2 Pro: Fix recognition of some versions
Huawei Watch GT 2: Fix pairing
Redmi Smart Band Pro: Fix password digits
Pebble: Fix app configuration page
Pebble 2: Fix pairing issue
PineTime: Fix weather forecast on InfiniTime's new simple weather
Xiaomi: Fix sleep sometimes extending past the wakeup time
Xiaomi: Request battery level and charging state periodically
Xiaomi: Fix sleep stage parsing for some devices
Zepp OS: Improve device discovery
Zepp OS: Fix weather not working on some devices
Zepp OS: Prevent crash when installing large firmware updates
Fix sport activity summary group order
Fix reconnection to devices failing occasionally

Gadgetbridge 0.78.0: Huawei/Honor device support!

Andreas Shimokawa — Mon, 15 Jan 2024 00:00:00 +0000

Gadgetbridge 0.78.0: Huawei/Honor device support!¶

Gadgetbridge 0.78.0 has been tagged (waiting for F-Droid to build).

This time we only had one month in between releases, but it is still a big one, since support for Huawei/Honor devices finally got merged. Many thanks to Damien Gaignon and Martin.JM for their amazing work!

This currently covers the following Huawei/Honor devices:

Honor Band 3,4,5,6
Honor Band 7 (experimental)
Huawei Band 4, 4 Pro, 6, 7, 3e, 4e
Huawei Talk Band B6
Huawei Watch GT, GT 2

Gadgetbridge 0.78.0 also adds support for two new Xiaomi devices (in addition to the many devices that were already supported since the last release:

Redmi Watch 2 Lite (experimental)
Redmi Smart Band Pro (experimental)

And last but not least, we have two new variants of Nothing Ear headphones and one new variant of the Mijia humidity and temperature sensors supported:

Nothing Ear (2)
Nothing Ear (Stick)
Mijia LYWSD03MMC

While this release concentrated on new device support, we still have some bug fixes and improvements for already supported devices. Please check the full changelog since the last release at the end of this blog post.

Thank you for your continued support and donations!

The Gadgetbrige Team

Changelog¶

0.78.0¶

Initial support for Honor Band 3,4,5,6
Initial support for Huawei Band 4, 4 Pro, 6, 7, 3e, 4e
Initial support for Huawei Talk Band B6
Initial support for Huawei Watch GT, GT 2
Initial support for Mijia LYWSD03MMC
Initial support for Nothing Ear (2)
Initial support for Nothing Ear (Stick)
Experimental support for Honor Band 7
Experimental support for Redmi Watch 2 Lite
Experimental support for Redmi Smart Band Pro
Casio GBX100: Add support for snooze alarm
Fossil/Skagen Hybrids: Update navigationApp to 1.1
Huami: Fetch SpO2 on devices that support it
Pebble: Attempt to fix app configuration webview
PineTime: Add support for InfiniTime's new simple weather
PineTime: Fix freeze and reboot when upgrading firmware
Pixoo: Enable sending images (non-persistent)
Pixoo: Get and send alarms
Pixoo: Set custom device name
Pixoo: support "clap hands to turn off screen" and "sleep after silence" settings
Xiaomi: Improve activity and workout parsing
Xiaomi: Improve stability and fix some crashes
Xiaomi: Improve weather
Xiaomi: Parse sleep stages
Add a notifications channel for connection status notifications
Improve automatic connection to all or previous devices
Fix devices sometimes staying stuck in a "Connecting" state
Map some missing Google Maps navigation actions

gadgetbridge.org website relaunch

Andreas Shimokawa — Sat, 23 Dec 2023 00:00:00 +0000

gadgetbridge.org website relaunch¶

We are very excited to announce our completely revamped website!

For a long time gadgetbridge.org was just generated from the README.md in our main Gadgetbridge repository. That was all.

Real documentation was only found in our wiki, which was not exactly easy to navigate or pretty. In addition it was tedious for outside contributors to change the contents of the wiki because it was just not editable for everyone.

This all changed now, thanks to Yusuf Cihan, please check it out!

Yusuf has opened an Issue three months ago, describing the current situation, the shortcomings, and a proposal to use mkdoks to generate a static site, which should be maintained in a new git repo, which is not a wiki and therefore supports pull requests.

He also implemented the proposal while constantly listening to feedback and really make it something, which in the end not only looks really great, but also is much more usable and maintainable.

Finally our DNS records were updated, and gadgetbrige.org is now served though codeberg pages, which is continuously generated though Codeberg's CI.

Thanks to everyone who gave feedback during these three months, and thanks again to Yusuf for pulling this off :)

Your Gadgetbridge Team

Gadgetbridge 0.77.0: Biggest. Release. Ever. Merry Christmas

Andreas Shimokawa — Sun, 17 Dec 2023 00:00:00 +0000

Gadgetbridge 0.77.0: Biggest. Release. Ever. Merry Christmas¶

Gadgetbridge 0.77.0 has been tagged (waiting for F-Droid to build), it marks the biggest release ever, in terms of changes and new device support.

Okay, that sounds great, but, honestly part of the reason is that we never had such a long time between releases. :)

First the list of new devices supported:

Amazfit: Balance, Active, Active edge (experimental)
FitPro: ColaCao 2021, ColaCao 2023
Sony Wena 3 (A watch band with an integrated smartwatch)
Femometer Vinca II (fertility thermometer)
Mijia LYWSD02MMC variant (epaper clock/thermometer/hygrometer)
Sony WF-1000XM5 (headphone, experimental)
Divoom Pixoo (LED Matrix, experimental)
Xiaomi Devices (experimental, see next paragraph)

Xiaomi? But we had already Xiaomi Mi Band support? Yes, thanks true but it seems that Huami(Amazfit) and Xiaomi which shared a common protocol since the Mi Band 2/Amazfit Bip time parted ways. While the Xiaomi Smart Band ("Mi Band") series continued to be Huami devices, there were some confusing devices like the "Mi Band 4C" which were incompatible with the regular Mi Band/Huami protocol. Also Xiaomi branded smart watches were never compatible with the protocol we observed with Huami/Amazfit devices. Gadgetbridge never supported those device. Until... now.

When the latest Mi Band 8 was released as the first mainstream Mi Band which uses the new protocol, we realized that it is really time to finally tackle that. Our journey opened the door for a lot of new devices, of which a few are supported now - although in an experimental state. So your millage may vary. The first round of seven devices we were able to get working are: Mi Band 7 Pro, Mi Band 8, Mi Watch Lite, Mi Watch Color Sport, Remi Smart Band 2, Redmi Watch 3 Active, Xiaomi Watch S1 Active. More will follow.

Another exciting class of devices are the Divoom devices. Right now we only support the Pixoo, but support for others should be doable. Those devices are RGB (16x16 pixel or more) matrices which can display animations, static images, weather and notifications. Gadgetbridge support is incomplete, right now only setting the time and date, weather conditions and displaying the firmware-included notification icons works. Support for more features will come in the near future.

As usual there are also a ton of new features and fixes for existing devices in the ChangeLog. One thing we would like to highlight (because it is just so cool) is support for fullscreen graphical OsmAnd navigation notifications on the Fossil/Skagen Hybrid HR. This is something the official app cannot do, and which we archived by creating our own on-device watch app which in bundled with Gadgetbridge and can be installed though the App manager. Sometimes Gadgetbridge not only protects your privacy, it enables you do do more.

For a complete list, as always, please refer the the Changelog, which list all user facing changes since the last release

Thank you for your continuous support, and we hope you will like Gadgetbridge 0.77.0!

Merry Christmas, and a happy new year from the Gadgebridge team :)

Changelog¶

0.77.0¶

Initial support for Amazfit Balance
Initial support for Amazfit Active
Initial support for ColaCao 2021
Initial support for ColaCao 2023
Initial support for Femometer Vinca II
Initial support for Mijia LYWSD02MMC variant
Initial support for Sony Wena 3
Experimental support for Divoom Pixoo
Experimental support for Sony WF-1000XM5
Experimental support for Amazfit Active Edge
Experimental support for Mi Band 7 Pro (Xiaomi Smart Band 7 Pro)
Experimental support for Mi Band 8 (Xiaomi Smart Band 8)
Experimental support for Mi Watch Lite
Experimental support for Mi Watch Color Sport
Experimental support for Redmi Smart Band 2
Experimental support for Redmi Watch 3 Active
Experimental support for Xiaomi Watch S1 Active
Amazfit Band 7: Add alexa menu entries
Amazfit GTR 3 Pro: Fix firmware and watchface upload
Amazfit T-Rex: Fix activity summary parsing
Amazfit T-Rex Pro: Add activate display on lift sensitivity
AsteroidOS: Add more supported watch models
AsteroidOS: Fix media info
AsteroidOS: Fix notification dismissal
Bangle.js: Add loyalty cards integration with Catima
Bangle.js: Ensure SMS messages have src field set to "SMS Message"
Bangle.js: Fix GPS speed
Bangle.js: Improve handling of chinese characters
Bangle.js: Lower threshold for low battery warning
Bangle.js: Recover from device initialization failure
Casio GBX100/GBD-200: Fix first connect
Casio GB5600/6900/STB-1000: Fix pairing
Casio GDB-200: Fix notification timestamp
Casio GDB-200: Fixed notification categories and default category
Casio GDB-200: Allow preview of notification message alongside title
Casio GDB-200: Fixed find my phone feature
Intent API: Add debug action for test new function
Fossil/Skagen Hybrids: Add new navigation app
Fossil/Skagen Hybrids: Allow configuring call rejection method
Fossil/Skagen Hybrids: Fix some preference crashes on the nightly
Fossil/Skagen Hybrids: Reduce toasts on release builds
Fossil/Skagen Hybrids: Show device specific settings in more logical order
Huami: Toggle phone silent mode from band
Message privacy: Add mode Hide only body
Mijia LYWSD02: Add battery
Mijia LYWSD02: Add low battery notification
Mijia LYWSD02: Set temperature unit
Mijia LYWSD02: Fix battery drain while connected
PineTime: Display app name for VoIP app calls
PineTime: Honor Sync time setting on connect
PineTime: Improve notification handling
PineTime: Reduce weather memory usage
Withings Steel HR: Fix crash when calibrating hands on the nightly
Zepp OS: Add blood oxygen graph
Zepp OS: Add workout codes for hiking and outdoor swimming
Zepp OS: Allow disabling app notifications per device
Zepp OS: Attempt to fix activity fetch operation getting stuck
Zepp OS: Display swimming activity data
Zepp OS: Fix health settings on older Zepp OS versions
Zepp OS: Fix setting of unknown button press apps
Zepp OS: Fix sunrise and moon dates being off by local time + UTC offset
Zepp OS: Map hiking, outdoor swimming, climbing and table tennis activity types
Zepp OS: Toggle phone silent mode from band
Add transliteration for Latvian, Hungarian, Common Symbols
Allow multiple device actions to be triggered for the same event
Allow toggling DND through device actions
Autodetect OsmAnd package name and make it configurable
Improve ASCII transliterator
Make GMaps navigation handler follow the "navigation forwarding" setting
Support selecting enabled navigation apps
Allow ignore notifications from work profile apps
Display alias in low battery notification
Fix crash when pairing current device as companion
Fix emoji when a transliterator is enabled
Fix UV Index and rain probability for some weather apps
Improve device discovery stability and fix freezes
Improve Telegram and COL Reminder notifications
Replace old-style preference switch with Material 3 switch

Gadgetbridge 0.76.0/0.76.1: Material 3, and a lot of new devices supported

Andreas Shimokawa — Wed, 27 Sep 2023 00:00:00 +0000

Gadgetbridge 0.76.0/0.76.1: Material 3, and a lot of new devices supported¶

Almost two month between major releases, but the wait is over, and Gadgetbridge 0.76.0 (and 0.76.1 which mostly fixes regression) has been released!

This time we did not only add support for new Amazfit devices (Bip 3 Pro, Bip 5, Cheetah, Cheetah Pro, Bip 5, Falcon, GTR Mini, T-Rex Ultra) and a new Casio watch (GW-B5600), but also multiple completely new devices from previously unsupported manufacturers:

Bohemic Smart Bracelet
Garmin Vivomove HR
Withings Steel HR

You might also notice that we switched the UI to Material 3, which also adds support for dynamic color themes. We hope you like the new fresh look of Gadgetbridge.

Another cool addition is Catima support! Gadgetbridge can now communicate with Catima and send Loyalty card straight to Zepp OS devices (Bangle.js support will be in the next release). This feature was created in collaboration wit Sylvia from Catima! If you haven't yet, please check out Catima from F-Droid.

The well-supported Huami/Zepp OS devices received a lot of bug fixes, and as a notable new feature, charts for PAI.

But it is not only Huami, Bangle.js, Inifitime, Fossil/Skagen, Sony Headphones and LeFun device also received fixes and improvements.

For a complete list, as always, please refer the the Changelog, which list all user facing changes since the last release

Thank you for your continuous support, and we hope you will like Gadgetbridge 0.76!

Changelog¶

0.76.1¶

Amazfit GTR Mini: Mark as not experimental
Bangle.js: Improve file downloads
Bangle.js: Fix app interfaces
Allow text to be shared to devices
Fix connection to some Amazfit devices

0.76.0¶

Upgrade UI to Material 3 and add dynamic colors theme
Initial support for Amazfit Bip 3 Pro
Initial support for Amazfit Cheetah Pro
Initial support for Bohemic Smart Bracelet
Initial support for Casio GW-B5600
Initial support for Garmin Vivomove HR
Initial support for Withings Steel HR
Experimental support for Amazfit Bip 5
Experimental support for Amazfit Falcon
Experimental support for Amazfit GTR Mini
Experimental support for Amazfit Cheetah (Round/Square)
Experimental support for Amazfit T-Rex Ultra
Amazfit GTS 2e: Add activate display on lift sensitivity
Amazfit GTR 3 / GTS 3: Enable AGPS Updates
Amazfit Neo: Enable PAI support
Bangle.js: Allow enable/disable of alarms
Bangle.js: Fetch activity data
Bangle.js: Fix GB integration when watch is not programmable
Bangle.js: Put JSON keys in quotes
Bangle.js: Reorganize device settings
Fossil/Skagen Hybrids: Embed custom menu in watchface, fixes lost menu on reset
Fossil/Skagen Hybrids: Fix unused alarms being pushed to the device
Fossil/Skagen Hybrids: Strip unicode characters that the watch can't display
Fossil/Skagen Hybrids: Sunrise/sunset follows weather location
Huami/Zepp OS: Add PAI charts
Huami/Zepp OS: Improve music info stability
Huami/Zepp OS: Improve reconnection and device initialization
Huami: Persist workout raw details even if gpx has no points
InfiniTime: Add heart rate measurement support
Mi Band 5: Fix activity fetch error toast when stress monitoring is enabled
Mi Band 6: Enable PAI and stress support
LeFun: Fix heart rate popup when measurement is triggered from phone
Sony WH-1000XM3/WF-SP800N: Add volume setting
Sony WH-1000XM5: Fix speak-to-chat enable/disable
Zepp OS: Add loyalty cards integration with Catima
Zepp OS: Enable AGPS updates for all devices
Zepp OS: Fix calendar sync on Zepp OS 2, send event location
Zepp OS: Fix reminder creation
Zepp OS: Fix shortcut cards setting on Zepp OS 2.1
Zepp OS: Fix weather, add hourly information
Zepp OS: Map barcode types for ITF, PDF_417 and DATA_MATRIX
Add preference to display changelog on startup
Add Termux RUN_COMMAND permission
Allow filtering notifications from work profile apps
Fix daylight saving time not being transmitted to the watch
Fix media button control for some applications
Fix notification filters by title if notification does not contain a body
Fix opening screenshots from notification on external apps
Fix reconnect delay reset after all devices are initialized
Fix some security error crashes when permissions are not granted
Fix transliteration of emoji
Fix transliteration of non-ASCII accented characters
Force gps speed calculation on some phones that do not report it correctly
Make application list sorting case-insensitive
Introduce native app shortcuts for android > 30
Update device settings action bar title depending on current screen

Gadgetbridge 0.75.0: Native OsmAnd support

Andreas Shimokawa — Wed, 05 Jul 2023 00:00:00 +0000

Gadgetbridge 0.75.0: Native OsmAnd support¶

Again after more than 1.5 month, a new Gadgetbridge release finally is ready! The F-Droid black box is still black though. :P

Traditionally we bump the release by a non-point release when support for a new device gets added or a big new code feature gets added, this time the latter is the case! We finally merged native OsmAnd support, a branch was started by me nearly two years ago but only recently picked up and fixed by José. PineTime/InfiniTime and bangle.js are the first watches that add support for making use of navigation instructions passed to devices by Gadgetbridge. There could be potential support for Pebble and Fossil/Skagen HR via watchapps in the future.

Of course, Gadgetbridge 0.75 also includes the usual fixes and improvements.

On the Bangje.js front, Gordon and contributors contributed a lot of small but important fixes (see Changelog), for the Fossil/Skagen HR, Arjan mainly improved weather support to potentially show UV index and chance of rain (given weather apps provide this info to Gadgetbridge.

ZeppOS support, mainly maintained by José also saw a lot of improvements. Much more than we can write about, again, please see the Changelog below, also to know about other generic changes and improvements not mentioned here.

Thank you for your continuous support, and we hope you will like Gadgetbridge 0.75!

This blog post was written by a human :)

Andreas

Changelog¶

0.75.0¶

Bangle.js: Add message size limitation to Calendar and Messages
Bangle.js: Add switch to control if the GPS chip should be used to locate the location
Bangle.js: Send more weather data to watch
Bangle.js: Allow an activity sample to have a timestamp
Bangle.js: Send last received activity timestamp on connect (to allow sync of activity samples)
Bangle.js: Allow connecting HW keyboard without closing app loader
Bangle.js: Bump flavor target SDK version to 31
Bangle.js: Fix convertion of emoji/unicode to bitmap without width/height
Bangle.js: Fix location listener not being cleaned up when waiting for reconnect
Bangle.js: Fix memory leak from HTTP requests
Bangle.js: Fix orientation changes closing app loader
Bangle.js: Fix return to applications management activity after having opened another window
Bangle.js: Set default value for GPS event interval to 1 second
Bangle.js: Support navigation instructions
Bangle.js: Escape characters that fall in the Unicode codepoint area (for Espruino ~2v18.20 and later)
Bangle.js: HTTP request XPath can now return Arrays
Fossil/Skagen Hybrids: Add support for ultraviolet index and rain probability
Fossil/Skagen Hybrids: Add UV index and chance of rain widgets
Fossil/Skagen Hybrids: Allow launching the calibration activity on any Gadgetbridge variant
Fossil/Skagen Hybrids: Increase accuracy of workout distance calculation
Fossil/Skagen Hybrids: Fix weather icons day/night status
InfiniTime: Fix weather expiry time
InfiniTime: Support navigation instructions
Mi Band 6: Allow making device discoverable via Bluetooth when connected
Mi Band 7: Add preference to display call contact information
Zepp OS: Add gpx route file upload
Zepp OS: Add screenshot support
Zepp OS: Add stress charts
Zepp OS: Add watch app logs developer option
Zepp OS: Display watchface and app preview on install
Zepp OS: Fix update operations on Zepp OS 2.1+
Zepp OS: Manage contacts on watch
Zepp OS: Start new GPX segments on pause/resume
Zepp OS: Support flashing zab files
App Manager: Fix cached apps sorting
App Manager: Hide drag handle if app reorder is not supported
App Manager: Add confirmation before deleting app
Add menus to share GPX, raw summary, raw details
Debug Activity: Allow pairing current device as companion
Fix some null pointer exception crashes
Intent API: Add command to set device mac address
Intent API: Add dataTypes parameter for activity sync
Intent API: Add debug actions for notifications and incoming calls
OsmAnd: Add support for navigation instructions
Scrape navigation instructions from Google Maps notifications
Fix lag when a folder has a lot of devices
Fix transliteration returning non-ASCII characters
Enable "allow high MTU" setting by default
Make some hardcoded english strings translatable

Gadgetbridge 0.74.0: Amazfit GTR 3 Pro, Sony WH-1000XM5, and a lot of improvements!

Andreas Shimokawa — Wed, 10 May 2023 00:00:00 +0000

Gadgetbridge 0.74.0: Amazfit GTR 3 Pro, Sony WH-1000XM5, and a lot of improvements!¶

After more than 1.5 month, finally a new Gadgetbridge release is ready!

On the new device front we have support for one new Huami device, the Amazfit GTR 3 Pro and another Sony Headphone, the WH-1000XM5.

Mostly contributed by José, who also did the Sony WH-1000XM5 support, we have tons of new features and improvements for various Zepp OS based devices (the newer Huami devices). For example The GTR4/GTS4 devices can now do bluetooth based phone calls though the watch. There is just too much new stuff, so please just read the ChangeLog at the end of this blog post.

For the Fossil/Skagen Hybrids, Arjan finally solved a long standing issue, where the watch asked for a confirmation on every single connection attempt. If you transferred your secret pairing key from one phone to another, this one likely annoyed you - but no longer :)

Arjan also contributed the big new feature for Gadgetbridge 0.74.0: Cached notification. This feature will allow you to get "old" notifications delivered when you come back into range of your phone, after you walked out of range and missed a notification. This feature is still considered experimental, so it need needs to be enabled explicitly.

For other changes please consult the following ChangeLog. Since we did not have a blog post for 0.73.0 make sure to also read it's impressive ChangeLog :)

Changelog¶

0.74.0¶

Initial support for Amazfit GTR 3 Pro
Initial support for Sony WH-1000XM5
Amazfit Bip U: Remove alarm snooze option
Amazfit GTR 4 / GTS 4: Add watch Wi-Fi Hotspot and FTP Server
Amazfit GTR 4 / GTS 4: Perform and receive phone calls on watch
Amazfit GTS 2 Mini: Add missing alexa menu item
Bangle.js: Fix updating timezone in settings.json if the timezone is zero
Fossil/Skagen Hybrids: Pair watch to phone, fixes repeating confirmation request
Huami: Implement repeated activity fetching
Sony WH-1000XM4: Add speak-to-chat
Sony Headphones: Add button modes help
Zepp OS: Add shortcut cards preference
Zepp OS: Add support for morning updates
Zepp OS: Add preference to keep screen on during workout
Zepp OS: Add preference for camera remote
Zepp OS: Fix activate display upon lift wrist smart mode
Zepp OS: Fix Cards and MI AI display item and shortcuts
Zepp OS: Fix setting of control center
Zepp OS: Fix setting of unknown configuration values
Zepp OS: Set watchface from phone
Add Croatian transliterator
Fix restoring app notification/pebble blacklist preferences on import
Cache notifications while devices are out of range (opt-in)

0.73.0¶

Initial support for Amazfit T-Rex 2
Initial support for AsteroidOS watches
Initial support for Sony LinkBuds S
Initial support for Galaxy Buds2 Pro
Initial support for SoFlow S06(just for lock and unlock, needs key)
Fossil/Skagen Hybrids: Fix truncation of notifications
Fossil/Skagen Hybrids: Fix washed out colors in imported watchfaces
Fossil/Skagen Hybrids: Allow launching watch apps from app manager
Fossil/Skagen Hybrids: Fix activity parser
Fossil/Skagen Hybrids: Add app/watchface downloading from watch to app manager
Fossil/Skagen Hybrids: Fix crash on empty or multi-byte unicode alarm texts
Fossil/Skagen Hybrids: Implement inactivity warnings
Fossil/Skagen Hybrids: Remove obsolete debug message
Mi Band 6: Add NFC display item
Zepp OS: Fix Alipay and WeChat Pay display item and shortcuts
Amazfit GTR 4/GTS 4: Support for AGPS Updates
Bangle.js: Stop sending bitmaps for common characters that already have good enough equivalents on the watch
Bangle.js: Stop toast warning message appearing when starting the app loader
Bangle.js: Increase default realtime HRM/step interval to 10 seconds
Bangle.js: Support additional values for GPS event
Sony WF-1000XM4: Fix battery updates while connected
Sony WF-1000XM4: Fix audio codec
Add Georgian Transliteration

Gadgetbridge 0.72.0: Lot of new devices and rewritten device discovery

Andreas Shimokawa — Fri, 23 Dec 2022 00:00:00 +0000

Gadgetbridge 0.72.0: Lot of new devices and rewritten device discovery¶

It took unusually long to get this out, but we tried to make it before Christmas, so here it is: Gadgetbridge 0.72.0

And since it is already out on F-Droid, today's blog post will be written by ChatGPT to save time. :O

Q: Can you please write a blog post about a gadgetbridge release? Here is the Changelog...¶

Gadgetbridge is a free, open-source application that allows users to communicate with and manage their wearable devices. The latest release, version 0.72.0, brings a host of new features and improvements to the application.

One of the major highlights of this release is the initial support for a number of new devices, including the Amazfit GTR 4/GTS 4/GTS 4 Mini, Amazfit Band 7, Samsung Galaxy Buds 2, and Sony WH-1000XM2/WF-1000XM4 headphones. This means that users of these devices can now take advantage of Gadgetbridge's features and functionality to manage their wearables.

In addition to supporting new devices, Gadgetbridge 0.72.0 also includes a number of improvements to existing device support. For example, the application now includes a fix for pause when taken off for Sony headphones, and a fix for setting surround mode. There are also a number of improvements to Zepp OS support, including the addition of world clocks and fixes for notification icons, app and watchface installs, and weather data.

Other notable changes in this release include a complete rewrite of the new device discovery process, the addition of an Intent API to trigger activity sync and database exports, and the ability to allow media notifications to bypass the app list. There is also a Debug Activity feature that includes a confirmation dialog before removing device preferences.

Overall, Gadgetbridge 0.72.0 is a solid release that brings a number of new features and improvements to the application. If you're a Gadgetbridge user, be sure to update to the latest version to take advantage of these new features and enhancements.

Phew, this was ChatGPT. Completely as is, un-edited. Too bad it is not open source, we promise this will be hand-written again next time. We do not intent to make this an advertisement for ChatGPT, but maybe it is interesting too see how capable this is, and that it actually knows what Gadgetbridge is.

For all user-facing changes of this release, check the following list:

Changelog¶

0.72.0¶

Initial support for Amazfit GTR 4/GTS 4/GTS 4 Mini
Initial support for Amazfit Band 7
Initial support for Galaxy Buds 2
Initial Support for Sony WH-1000XM2/WF-1000XM4
Sony headphones: Fix pause when taken off
Sony Headphones: Fix setting surround mode
Zepp OS: Map strength training, basketball and cricket activity types
Zepp OS: Add World Clocks
Zepp OS: Fix notification icons larger than 56x56px
Zepp OS: Fix notification icons for work profile apps
Zepp OS: Fix notification icon for SMS
Zepp OS: Fix app and watchface install
Zepp OS: Fix NPE when no weather data is available
Amazfit GTR 2: Fix activate display upon lift only working when scheduled
Bangle.js: Fix calendar sync
InfiniTime: Fix weather
InfiniTime: Add support for local time service
InfiniTime: Add world clock support
Skagen Gen 6 Hybrid HR: Add support for 38mm watches
Complete rewrite of new device discovery
Add Intent API to trigger activity sync and DB export
Allow media notifications to bypass app list
Debug Activity: Add confirmation dialog before removing device preferences

Gadgetbridge 0.71.x: Initial support for Amazfit GTR 3 and SuperCars (Shell Racing Cars)

Andreas Shimokawa — Sat, 22 Oct 2022 00:00:00 +0000

Gadgetbridge 0.71.x: Initial support for Amazfit GTR 3 and SuperCars (Shell Racing Cars)¶

After some delays and fine-tuning of the release, next version of Gadgetbridge is now out with whole lot of changes. Interestingly, it is not 0.71 but already 0.71.3 as of the writing of this blog post.

Initial support for Amazfit GTR 3 and SuperCars (Shell Racing Cars)¶

Initial support for Amazfit GTR 3 was added, which is very similar to GTS 3, and Mi Band 7 see the wiki page here for more information.

@vanous has added support for an entirely new class of devices - a Bluetooth remote controlled car models! If you own a Shell Racing Car, please give it a try ;)

Bye-bye Android 4.4 (KitKat)¶

Like we announced in our last blog post, Android 5.0 is now the minimum requirement for Gadgetbridge. This allowed us to clean up some code and ugly workarounds. Even the F-Droid client no longer supports Android 4.4, and we were not aware of users who are still on KitKat. Time to move on!

Bye-bye NDK!¶

@ashimokawa has ported the ECDH C library to pure java, a very straight-forward and simple port, basically fighting with the absence of pointers and unsigned integers was the only real work to do.

No NDK means faster build times and less build dependencies - also for our CI. Last but not least it also makes reproducible builds easier - we are probably already (almost?) there.

Device support improvements¶

@joserebelo continued with his quest to implement first class support for Zepp OS based devices (MiBand 7, Amazfit GTR 3, GTS 3...) with their activities, sleep and workouts fetching, firmware updates and more.

The Bangle.js team has been improving the Bangle.js device support and capabilities and added the ability to start services via intents, or to wake and unlock the Android device.

Huami devices (MiBands and Amazfits) can now choose whether device preferences as set in Gadgetbridge should be sent to the device on start of each connection which until now has been the case. This new setting can allow to have a watch or a band be configured in the original vendor's app and then connect it to Gadgetbridge, without overwriting settings in the device during the connection. Many other improvements have been added - like improved "Find device", which is now not dependent on the "Do not disturb" setting.

Fossil HR, InfiniTime, Flipper Zero, Mi Band 6... have also gained several improvements, see change log below. Many thanks to @arjan5, @Ganblejs, @dakhnod, @gfwilliams and others for all the contributions!

General app improvements¶

We have fixed several crashes. One, when opening Gadgetbridge from the notifications and another crash on some older Android versions.

More automation is now possible thanks to new Intents which allow to set device settings or can send information about a device being connected/disconnected. See a dedicated Wiki page for the Intent API.

These have been just the highlights, see more details below.

Many thanks to everyone for their contributions and support!

For all user-facing changes of this release, check the following list:

Changelog¶

0.71.3¶

Fossil/Skagen Hybrids: Update known watch app versions
Skagen Hybrids: Allow firmware installation
Fossil Hybrid HR: Request menu config upon app connection
Amazfit GTS3: Fix crash when fetching workouts
Zepp OS: Fix fetching workouts shorter than 1 minute
Zepp OS: Decode workout elevation and altitude
Huami: Do not crash when failing to parse activity summary
Re-connect after update, especially useful for users of nightly releases
Make number of not scrollable sleep sessions lines configurable

0.71.2¶

Zepp OS: Display HR zones and Training Effect in Activity Details
Remove shortcut feature due to non-free dependencies (#2918)

0.71.1¶

Try to exclude non-free stuff from shortcuts library (#2918)
SuperCars: fix periodicDataSender, add tricks
Zepp OS: Fix crash when user attempts to disable Settings display item
Fix crash when opening Gadgetbridge from the notification

0.71.0¶

Remove KitKat support, Gadgetbridge now requires Android 5.0
Initial support for Amazfit GTR 3
Initial support for SuperCars (Shell Racing Cars)
Huami: Add preference to overwrite band settings on connection
Huami: Fix crash when selecting automatic Always On Display
Huami: Set OpenTracks track category and icon
Huami: Implement proper find device
Huami: Change default find band vibration pattern
Flipper Zero: added duration to Intent API
Flipper Zero: fixed crash due to unregistered boradcast receiver
Flipper Zero: fetch firmware version from flipper
Fossil Hybrid HR: Correctly initialize watchface after reset or crash
Fossil Hybrid HR: Set OpenTracks track category and icon to workout type selected on watch
Fossil Hybrid HR: Allow flick_away as custom event and add move_hands event
InfiniTime: Add weather support
Amazfit Neo: Fix world clock
Amazfit Neo: Fix long caller name display
Amazfit Neo: Remove activity tracks (unsupported)
Amazfit GTS 3: Fix battery drain due to unanswered weather requests
Mi Band 7: Fix Weather
Mi Band 6: Add support for workout activity types
Mi Band 6: Enable adding workout activity types to the "more" section
Amazfit GTR: Enable button actions
Zepp OS: Implement activity, sleep and workout fetching
Zepp OS: Improve firmware upgrades
Bangle.js: Add PATCH HTTP request type, and fix for VolleyError UnsupportedOperationException when supplying custom headers.
Bangle.js: Add ability to start services on the Android device via intents.
Bangle.js: Flags and multiple categories can now be specified for intents initiated on the watch.
Bangle.js: Add ability to wake and unlock the Android device via a special intent.
Allow 3rd party apps to set device settings
Re-implement C code in Java and remove Android NDK dependency entirely
Fix crashes on older Android versions when using some devices
Add support for REM sleep
App shortcuts support (long press on the launcher icon for directly connecting a device)

Gadgetbridge 0.70.0: Initial support for Amazfit GTS 3, for Fossil Hybrid Gen6 and for Flipper Zero

Petr Vaněk — Sun, 11 Sep 2022 00:00:00 +0000

Gadgetbridge 0.70.0: Initial support for Amazfit GTS 3, for Fossil Hybrid Gen6 and for Flipper Zero¶

Initial support for Amazfit GTS 3, for Fossil Hybrid Gen6 and for Flipper Zero¶

Initial support for Amazfit GTS 3 has been provided by Codeberg user sedy89. This is based on the recent addition of support for the Mi Band 7 and thus has similar set of features and limitations, see the wiki page here.

Daniel Dakhnod has provided support for the Fossil Hybrid Gen6 watches, extending the list of supported Fossil Hybrid devices even more. Daniel has also worked on support for the Flipper Zero, an open source multi-tool for pentesters and geeks.

This is absolutely awesome, many thanks! Such contributions are unlocking the door for others with these devices to poke deeper and to further improve the initial device support.

A note to Android 4.4 users of Gadgetbridge - this is our last release with KitKat support¶

We have tried to keep support for Android 4.4 KitKat for a very long time. This required some extra work and code sometimes, and it also kept us from using Java 1.8 language and library features. But until nowm we have felt that we should not stop supporting it, as there might still be some KitKat users out there (according to Wikipedia, 1.47% of Android devices still run KitKat). We have however realized recently that we (unintentionally) broke KitKat supportin our 0.68 release in July 2022 and that there has not been a single report about this from the Gadgetbridge user base. Based on this, we have decided to end support for KitKat and make Android 5.9 (Lollipop) the oldest Android version supported by Gadgetbridge. If you are a KitKat user, we are sorry. It is time to move on.

Device support improvements¶

Huami device users who experienced issues with notifications vibration since last update can rejoice, the issue is fixed in this release and their wrists can now vibrate to their heart content. :)

Mi Band 7 support has been getting additional fixes and improvements, like preventing crashing when transmitting data with non-ascii characters, adding support for watchapps and so on.

Bangle.js has gained the possibility to use calendar names and color.s

Fossil Hybrid HR with latest firmware allows to set custom shortcut also for the middle button.

InfiniTime users should now be able to experience more stable firmware updates.

General app improvements¶

Heart rate measurement intervals can now be configured individually for each connected device. Skype notifications should again be sent to the watch (even though the app indicates opposite). Notification settings allow to set notification text to be send to the device in full length (if available). Notifications are now also left with line-breaks and with spaces and tabs (white space characters), to keep formatting as it was.

Many thanks to everyone for their contributions and support!

For all user-facing changes of this release, check the following list:

0.70.0¶

Initial support for Amazfit GTS 3
Initial support for Fossil Hybrid Gen6
Initial support for Flipper Zero
Huami: fix default vibration pattern
Huami: Enable vibration patterns for all compatible devices
Huami: Improve large firmware zip file handling
Bangle.js: Fix null pointer issue if headers not supplied for HTTP request
Bangle.js: Support calendar color and name
Mi Band 7: Fix crash if reminder, calendar or canned messages contain non-ascii characters
Mi Band 7: Fix NPE when acknowledging that icon was sent
Mi Band 7: Fix and enable firmware upgrades
Mi Band 7: Support for watchapps
Amazfit Neo: remove 1 hour heartrate interval (not supported)
Fossil Hybrid HR: Fix watchface redraw after powersave and after wrist flick
Fossil Hybrid HR: Enable configuring middle long press on FW 3.0 and newer
InfiniTime: Fix firmware update
Make heart rate measurement intervals configurable per-device
Add option to ignore low priority notifications
Fix Skype notifications
Prefer long notification text by default
Prefer big text when scraping gmail notifications
Do not remove newline and whitespace characters from notification content
Debug: Add companion device list to debug activity

Gadgetbridge 0.69.0: Initial support for Mi Band 7, Binary Sensor Service and for Fossil 38mm

Petr Vaněk — Fri, 26 Aug 2022 00:00:00 +0000

Gadgetbridge 0.69.0: Initial support for Mi Band 7, Binary Sensor Service and for Fossil 38mm¶

Our small group of Gadgetbridge contributors has been very busy in the past several weeks and the changelog of this new release really shows it. Today, Gadgetbridge is bringing support for some new devices together with features, bug fixes and improvements to existing devices and the app itself.

Initial support for Mi Band 7, for devices that use Binary Sensor Service and for Fossil/Skagen Hybrid HR 38mm watches¶

Mi Band 7 has been out and José Rebelo has worked hard to bring initial support for this new smart band. The device support is at the moment still somewhat limited but it is getting better over time. See this wiki page for details about currently supported features and also for list of known issues.

Daniel Dakhnod has provided support for devices that use Binary Sensor Service, for example for his firmware for nRF51.

And last but not least, hackoder (thank you very much!) has brought in support for yet another group of Fossil/Skagen Hybrid HR 38mm watches.

Active re-connection¶

In this release we have fixed few issues related to automatic re-connection. This is related to all devices supported by Gadgetbridge.

Notable improvements¶

Amazfit Bip U fitness tracking with GPS data from the phone has been tested and is now enabled. Amazfit Neo and Mi Band 4 device implementations have received wave of adjustments and improvements.

Fossil Hybrid HR widgets (complications) can now be toggled with a physical button and can also have circle background.

Bangle.js can now start Android Activities via Android Intents.

InfiniTime for PineTime should handle step fetching and counting a bit better from now on.

If you are paying attention to your daily step goals, the Steps per month screen now provides an icon to open Steps Streaks - a new screen that allows you to see your current and longest series of days without interruption with the daily steps goal reached, as well as your total achievement rate. See more details in our wiki.

For all user-facing changes since the previous blog post, check the following list :)

Thank you to José, Daniel, Arjan and Andreas for all the ongoing work and involvement and many thanks to all others for their contributions and support!

0.69.0¶

Initial Support for Mi Band 7
Initial support for devices using Binary Sensor Service
Mi Band 4: Enable heartrate activity monitoring support
Mi Band 4: Enable activate display on lift sensitivity setting
Mi Band 6: Enable password support
Mi Band 4/6, Amazfit Bip U: Enable sending GPS coordinates to band during workout
Mi Band 4/6, Amazfit Bip U: Enable start fitness tracking on phone when workout starts on band setting
Amazfit Neo: Support hourly chime which was added in firmware 1.1.2.46
Amazfit Neo: Fix daily steps goal and notification
Amazfit Neo: Fix heartrate sleep detection setting
Amazfit Neo: Enable heartrate activity monitoring support
Amazfit Neo: Fix alarms setting to "unused" on connect.
Bangle.js: Make text as bitmaps have transparent background, and allow font size to be specified
Bangle.js: Allow starting Activities on the Android device
Fossil Hybrid HR: Add support for Hybrid HR 38mm watches
Fossil Hybrid HR: Add optional circle backgrounds to widgets
Fossil Hybrid HR: Add toggling of widgets with physical button event
Fossil Hybrid HR: Add missing physical button options
Fossil Q Hybrid: Fix config activity after multi-device merge
InfiniTime: Fixes for steps count sync
Add steps/sleep streaks screen
Add French transliteration
Refactor file logging initialization logic
Add alert to Log Sharing if logging has not been enabled yet
Fix crash on some phones for find android device (add fallback tone)
Fix regression since 0.68.0 with active auto connect

Gadgetbridge 0.68.0: Multiple device connections - a huge release!

Andreas Shimokawa — Wed, 27 Jul 2022 00:00:00 +0000

Gadgetbridge 0.68.0: Multiple device connections - a huge release!¶

After almost two months of work since the last version, we finally released one of the biggest releases of all time!

Multiple device connections¶

Gadgetbridge could traditionally only connect to one device at one moment. That was mostly enough since not many people would need to connect to two smart watches at the same time. But Gadgetbridge has expanded, and there are a lot of non-smartwatch devices supported by now. For example smart headphones with various settings or the Mijia e-paper watch. If you wanted to connect to those devices, you always needed to disconnect your daily driver smart band/watch first. Thanks to Daniel Dakhnod who worked on multiple device connection support for over a month, we finally felt that it was time to merge his branch. We assume there are still some problems and regressions when more than one device is connected at a time - so consider this experimental and please report bugs into our bug tracker.

Vast device improvements¶

Huami¶

José Rebelo did a lot of further improvements for Huami devices, most notably tethered GPS support (sending GPS data from the phone to the device after a workout has been started from the band). This is only enabled for the Mi Band 5 right now but it will be expanded to other devices as we test them.

Fossil Hybrid HR¶

The Fossil Hybrid HR also received a lot of bug fixes and improvements, mainly thanks to code contributed by Arjan Schrijver who also did a lot of work on the Fossil front in the past. One highlight here is definitely the much improved watch app manager which now shows versions and watchface previews. Another great addition is an integration between the Workout app on the watch and OpenTracks - when you start a Workout on the watch, OpenTracks will start a GPS recording of your workout.

Bangle.js¶

Bangle.js got improvements thanks to multiple contributors. One big new feature is the webview based app-loader for the internet enabled builds. Also, among other changes and fixes, calendar sync and sending emoji as images is supported now.

Other notable changes¶

There actually have been very many general non-device specific improvements in this release - too much for writing about everything. Refining of the UI and reorganizing some per-device settings, making more formally global settings per-device settings, bug fixes, icons etc.

As we always write:

For all user-facing changes since the previous blog post, check the following list :)

Many thanks to everyone for their contributions and support!

0.68.0¶

Multi device support (experimental), allows connecting to multiple devices simultaneously
Fossil Hybrid HR: Allow installation of newer watch apps
Fossil Hybrid HR: Allow workout app the be added as a shortcut
Fossil Hybrid HR: Generate watchface preview image and show it in the app manager
Fossil Hybrid HR: Request custom menu config on watchface initialization
Fossil Hybrid HR: Invert widgets color when the background image is inverted
Fossil Hybrid HR: Show app versions in app manager
Fossil Hybrid HR: Make 2nd TZ widget clock duration configurable and fix wrong offset
Fossil Hybrid HR: Add option to share a cached watchface/app to another app
Fossil Hybrid HR: Allow switching already uploaded watchfaces with Intent
Mi Band 6: Fix night mode on latest firmware
Mi Band 6: add sleep menu item (also to shortcuts)
Mi Band 5: Send GPS location to band during workout
Mi Band 5: Start fitness tracking on phone when workout starts on band
Mi Band 5: Fix missing Portuguese language
Mi Band 5: Add missing breathing shortcut
Mi Band 4: Add password support
Huami: Fix setting heart rate measurement interval on connection
Huami: Fix track name being replaced by album
Huami: Display native alarm notification
Huami: Fix MTU update on device connection
Roidmi 3: Recognize "Roidmi C BLE" as Roidmi 3
Bangle.js fix message REPLY option
Bangle.js: Keep a log of data sent from the watch, and allow it to be saved with from the debug menu
Bangle.js: Support for color dithered bitmaps, and converting emoji->bitmaps
Bangle.js: Adding built-in app-loader view. (Only available on internet-enabled builds)
Bangle.js: fix null pointer issue for debug messages
Bangle.js: Enable calendar sync for bangle
Bangle.js: Add icon
Pebble: fix configuration of some watchfaces (might break other again)
FitPro: add MTU based chunking, add more device names (Sunset 6, Watch7)
UM25: fix missing firmware version
Support for incoming call notification delay
Make calendar blacklist configurable per device
Support folders in device list
Separate device settings which are specific to the application into Set preferences in device card
When pairing devices with auth key requirements, only show Auth key menu related items on long press
Provide access to the FW/App Installer via Set preferences in device card
Animate card movement in device list
Make transliteration configurable per-language
Widget: do not show sleep if not recorded
Pop up a dialog asking about Location permissions
Fix sharing log files on newer android versions
Allow to set Bluetooth discovery scanning level to prevent freezing
Various UI tweaks and fixes
Add monochrome themed icon
Add device menu item to get to the FW/App Installer via an explanation activity

0.67.1¶

Huami: Fix long music track names not displaying
Amazfit Bip U/Pro/Band 5: Enable extended HR/stress monitoring setting
Pebble: Fix calendar blacklist, view and storage
FitPro: Fix crash, inactivity warning preference to string

Gadgetbridge 0.67.0: Initial Support for Sony WF-1000XM3 and Galaxy Buds Pro

Andreas Shimokawa — Sat, 21 May 2022 00:00:00 +0000

Gadgetbridge 0.67.0: Initial Support for Sony WF-1000XM3 and Galaxy Buds Pro¶

After two months of development since the last version, we have yet another very interesting feature rich release to talk about. Development felt a bit slow at the beginning but looking at the changelog, there are many additions, improvements and also some newly supported devices.

New devices¶

Lets start with new support for another two headphones - Sony WF-1000XM3 and Galaxy Buds Pro. While it may feel like "yet another very similar device(s)", each of them required careful work on dissecting and implementing the communication protocols. Big thanks to José R. for work on the Sony headphones and in the case of the Galaxy Buds Pro, also big thank you to two very helpful users - owners of the headphones - who were able to gather the data and help with providing the necessary low level communication info that was required for implementing support for this device.

Bangle.js¶

We have added another gradle product flavor for Bangle.js specific release. This particular custom flavor will make use of some extra features, together with added permission for networking. Do note that this permission is not enabled for our normal Gadgetbridge releases and is only available on the Bangle.js specific build, as the Bangle.js watch is built around their online application repository and it requires internet connectivity for proper function. We believe that this cooperation with the Bangle project is very useful for both sides and that communities around both Bangle.js and Gadgetbridge can benefit from this connection. We can already see some contributions that help to clarify for example requests for permissions, making Gadgetbridge more user friendly during the initial onboarding experience. Bangle implementation also got new communication intents to be able to share data from/to other Android apps.

Mi Band 5/Amazfit Band 5 enhancements and other improvements¶

Users of Mi Band 5, Amazfit Band 5 (and several other Huami devices) can now enjoy new features like world clock configuration, workout menu configuration, vibration patter selection, wrist flick sensitivity settings, extended heart rate activity monitoring and alerts and few other improvements.

Thanks to José for all these improvements! We will continue to unlock features on more Huami devices after testing.

The OpenTracks API controller newly supports stop and toggle functions, now after the API itself has been finalized.

The Fossil Hybrid HR now supports a flexible custom menu on the watch as well as the possibility to honor native do not disturb settings. See the much improved wiki page.

Various fixes and enhancements have been done in several places, together with some visual improvements like a few new icons.

Nightly builds¶

During the Christmas holidays we started utilizing Codeberg's Woodpecker CI (Woodpecker.org) for automatic Nightly release of Gadgetbridge into our own F-Droid repository. This release is automatically built and released every night when new commits have been done to our repository. The nightly release comes in two build types: "normal" nightly release and "No Pebble provider" nightly release. The "No Pebble provider" release was created due to the fact that if you have either the official Gadgetbridge F-Droid release or the original Pebble app installed, you cannot install another app (for example the Gadgetbridge Nightly release) which provides something called "Pebble provider" (com.getpebble.android.provider). The "No Pebble provider" version allows to be installed alongside existing Gadgetbridge or Pebble app. If you are planning to use the Nightly release and want to migrate your data from the official release, make sure to be careful when exporting and backing up your data. See detailed explanation in our wiki here. Big kudos to the Codeberg and Woodpecker teams for providing us with these great tools for hosting and maintaining of our FLOSS project!

Many thanks to everyone for their contributions and support!

For all user-facing changes since the previous blog post, check the following list:

0.67.0¶

Initial Support for Sony WF-1000XM3
Initial Support for Galaxy Buds Pro
Huami: Add Toggle function for Open Tracks tracking to button actions
Huami: Move inactivity warnings, goal notification and HR monitoring to device-specific settings
Mi Band 6: set time on connect
Mi Band 5/6, Amazfit Bip S/U/Pro: Add world clock configuration
Mi Band 5/6: support sensitivity setting for lift wrist configuration
Mi Band 5: Add support for configuring workout menu on device
Mi Band 4/5/6, Amazfit Bip U/Pro: Add support for vibration patterns
Mi Band 5: Increase number of reminder slots to 50
Mi Band 5/6: Add setting for HR activity monitoring, HR alerts, stress monitoring
Amazfit Neo: Allow to disable beeps for email notifications
Bangle.js: Fix incoming calls in release builds
Bangle.js build: Add option for enabling/disabling internet access
Bangle.js: Add ability to receive intents to com.banglejs.uart.tx
Fossil Hybrid HR: Support flexible custom menu on watch
Fossil Hybrid HR: Add support for native DND Call/SMS functionality
VESC: added battery indicator
UM25: Add reset option to current accumulation
UM25: Add notification on below current threshold
Fix crash when calendar is accessed but permission is denied
Add com.asus.asusincallui and com.samsung.android.incallui to blacklist
New icons for Sony overhead headphones, Sony WF 800n and Mi Band 6
When Gadgetbridge needs permissions, pop up a dialog asking nicely and explaining why

Gadgetbridge 0.66.0: Initial support for Casio GBD-H1000 and Hama Fit Track 1900

Andreas Shimokawa — Sun, 27 Mar 2022 00:00:00 +0000

Gadgetbridge 0.66.0: Initial support for Casio GBD-H1000 and Hama Fit Track 1900¶

Support for two new devices has been added - the Casio GBD-H1000 and Hama Fit Track 1900. Both of these additions use existing device implementations and add a new name of the device as chosen by the vendor, allowing more people to use their devices with Gadgetbridge.

Arjan Schrijver worked on a new OpenTracks Controller which allows tight integration between Gadgetbridge and OpenTracks. The main idea is to be able to use OpenTracks as a source of data during workouts (running, walking...). OpenTracks can be started from a device (watch) connected to Gadgetbridge, activity is tracked in OpenTracks and OpenTracks provides information about activity duration, speed and so on to Gadgetbridge, who sends it back to the watch. At the moment, only the Fossil Hybrid HR provides full integration into it's Workout app. Huami devices (Mibands, Amazfit) with a button that allows usage of the Button actions can use this via a new Action: Fitness app tracking start. Current limitations of this OpenTracks Controller are:

OpenTracks can only be started at the moment
data about workout is not used for Huami Activities/Workouts in the watch/band

Fossil Hybrid HR implementation has received additional improvements which allows better support for button customization (allow to disable the button) and for widget editing (try to guess position of the widget).

Mi Band 6 now allows syncing alarm details from the watch to Gadgetbridge. If you change the alarm time on-device (even while being disconnected), Gadgetbridge will also reflect the changes. This was previously already done for Amazfit Bip U and others, but the implementation was more difficult for the Mi Band 6.

The improved XWatch support now supports calls, messages and apps notifications.

Improvements have also been done to the Bangle.js implementation - Gadgetbridge now handles battery charging status and some battery chart issues were fixed. Fix for "no incoming call notification" has been added but it seems that this fix is not final, see more details here.

Many thanks to everyone for their contributions and support!

For all user-facing changes since the previous blog post, check the following list:

0.66.0¶

Add basic support for Casio GBD-H1000
Add support for Hama Fit Track 1900 - via FitPro device support
Add OpenTracksController for interactions with OpenTracks
Fossil Hybrid HR: Start/stop track in OpenTracks from GPS workout on watch
Fossil Hybrid HR: Try guessing new widget position
Fossil Hybrid HR: Allow assigning no function to a button
Add Huami button/device action to control fitness tracking via OpenTracksController
Mi Band 6: Sync alarms set on the watch like on Amazfit Bip U and others
Bangle.js: Handle battery charging status and fix battery chart.
Bangle.js: Prevent exception in case UART RX line is empty
Bangle.js: Add repetitions in alarm JSON
WaspOS: Fix battery chart.
WaspOS: Add condition code to weather JSON
XWatch: Add notifications and calls support
UM-25: Make cumulative values resettable
VESC: Fixed crash when loading a saved value
Allow to open Android notification settings from Notification settings
AutoExporter changes for better operation and troubleshooting
Change Nightly icons background color

Gadgetbridge 0.65.0: Initial support for Amazfit Pop/Pro watch and for Sony WH-1000XM4 headphones

Andreas Shimokawa — Thu, 27 Jan 2022 00:00:00 +0000

Gadgetbridge 0.65.0: Initial support for Amazfit Pop/Pro watch and for Sony WH-1000XM4 headphones¶

Support for Amazfit Pop/Pro has been added. This watch seems to be almost identical to Amazfit Bip U/Pro but it has different firmware so we have separated the device support to make sure things work correctly in the future. Another new device are the over the ear wireless headphones Sony WH-1000XM4.

The overall Sony Headphones implementation has been worked on a lot and got improvements to initialization, noise canceling and more.

Fossil Hybrid HR support has also received several updates and improvements.

In order to keep alarms between Gadgetbridge and Amazfit Bip U in sync, reading alarm details from the watch has been implemented. This fixed the problem that Gadgetbridge overwrote changes done on the watch UI. This should also work on other Huami devices, but we could only test it on the Bip U so far. Mi Band 6 needs some additional data decryption which will come in the next release.

Many thanks to everyone for their contributions and support!

For all user-facing changes since the previous blog post, check the following list:

0.65.0¶

Amazfit Pop/Pro: Initial Support (probably the same as Bip U but has a different firmware)
Sony WH-1000XM4: Initial Support
Sony WH-1000XM3: Disable equalizer, surround and sound position while in SBC codec
Sony Headphones: Improve initialization on connection
Sony Headphones: Implement Noise Cancelling Optimizer
Casio: Fix accidentally disabled time synchronization and pairing of new Casio GBX/GBD-series watches
Fossil Hybrid HR: Improve Device Applications List handling
Fossil Hybrid HR: Added ability to change activity recognition settings on the watch
Fossil Hybrid HR: Make width of custom widget configurable
Fossil Hybrid HR: Disable non-configurable buttons preferences
Amazfit Bip U: Read alarm from the watch on connect and update in Gadgetbridge when changing alarms on the watch (might work on other Huami devices)
Add icon for VESC devices
Add commit id into About screen
Make debug activity notification test to persist text while switching apps
Add Portuguese to the list of language options
Update configuration button icon in app notification settings

Gadgetbridge 0.64.0: Initial support for VESC NRF/HM10 devices, Bose QC35 and for Sony WF-SP800N

Andreas Shimokawa — Fri, 31 Dec 2021 00:00:00 +0000

Gadgetbridge 0.64.0: Initial support for VESC NRF/HM10 devices, Bose QC35 and for Sony WF-SP800N¶

Quite unexpectedly, we have tagged and F-Droid has already published one more update: 0.64.0, making it the 24th release of this year. Besides many "small" additions and improvements, this release also adds support for three new devices: two new earphones, Bose QC35 and Sony WF-SP800N, plus there is now also support for VESC NRF/HM10 devices - Speed Controllers. Adding device support is always a lot of work so we are grateful for every single device support, allowing everyone to use their devices in a libre way.

Together with our army of wonderful contributors, we have been working on improving various aspects of interactions with the supported devices. One could tend to think about these as about some "small" additions, but each contribution means a lot of investigation, work and testing. Thanks everyone for helping Gadgetbridge to get better.

To pick a few enhancements... the InfiniTime steps synchronization has been adjusted to have lesser impact on the device battery. Sony headphones communication has been improved to not only send data to the device but also to read settings from the headphones. The car FM transmitter Roidmi support has been enhanced to be able to control a new rebrand called Mojietu. Bangle.js weather data and music control has been improved. Many of the Huami gadgets (the Mi Bands and Amazfit devices) have received improvements in communication protocol, notifications handling, menu settings, Reminders (an alarm like notification with a text label) and many more enhancements.

Device pairing and discovery settings have been made available directly from the Discovery screen which now also allows adding test device directly from the discovery screen (previously possible only from the Debug screen).

Many thanks to everyone for their contributions and support!

For all user-facing changes since the previous blog post, check the following list:

0.64.0¶

Initial support for VESC NRF/HM10 devices
Initial support for Bose QC35
Initial support for Sony WF-SP800N
Fossil Hybrid HR: Fix on-device confirmation for older firmwares
Sony WH-1000XM3: Fix Ambient Sound Control commands, potentially improving ANC quality
Sony WH-1000XM3: Read configuration from device
InfiniTime: Remove debug Toast and subscription to UUID_CHARACTERISTIC_MOTION_RAW_XYZ_VALUES
Roidmi: Fix frequency configuration on some non-english languages
Roidmi 3: Add support for Mojietu 3 rebrand
Huami: Support hiking and climbing activities, decode some more activity details
Amazfit GTS 2 mini: Fix notification title not appearing for non-chat apps
Amazfit Bip U/Pro: Disable event reminder feature, it is not supported by the device.
Amazfit Bip U/Pro: Allow enabling Todo List menu (feature still not supported)
Bangle.js: send weather condition code to device
Allow adding test device directly from the discovery screen
Keep device info on the correct device during reordering

0.63.1¶

Huami: Support native reminders
InfiniTime: Initial support for step counting (currently very limited by the device firmware)
Bangle.js: Fix Gadgetbridge crashes when playing music with some players
Fossil Hybrid HR: Add support for on-device paring confirmation, for watches that are in a state which makes this neccessary
Fossil Hybrid HR: Fix widget configuration bug
Mi Band 3: Support lift wrist during DND setting
Amazfit GTS 2 Mini: Fix language setting
Amazfit GTS 2 Mini: Fix setting menu items on the watch
Activity card: Open specific Charts tab for each activity
Activity Card: React to User settings, unify step length
Activity card: simplify the layout and only show each chart if there is data (Cleaner layout for users with multiple devices)

Gadgetbridge 0.63.0: Initial support for Galaxy Buds Live, Sony WH-1000XM3

Andreas Shimokawa — Fri, 03 Dec 2021 00:00:00 +0000

Gadgetbridge 0.63.0: Initial support for Galaxy Buds Live, Sony WH-1000XM3¶

This might be the last release for 2021, but it is a big one!

This release adds support for two new earphones, the Sony WH-100XM3 and Galaxy Buds Live and also for two another watches of the Casio family, the GBD-200 and for GBD-100 (support of the GBD-100 is untested at the moment).

Apart from that there are several new features and bug fixes across many different devices.

Most notably for everyone with a device supporting step counting, there is a big visual change in the main activity: The device cards will now show steps, distance and sleep data, which eliminates the need to enter the Charts screen when an overview it enough.

The Fossil HR got support for a new custom widget which can be set to display various configurable information. This widget comes bundled with Gadgetbridge and was made for the Gadgetbridge native watchface. Also support for more than one timezone widgets has been added.

Gadgetbridge got support for displaying status and charts of multiple batteries which is useful for earphones, Nothing Ear(1) and Galaxy Buds are the ones which leverage this feature.

For all user-facing changes since the previous blog post, check the following list:

0.63.0¶

Galaxy Buds Live: Initial Support
Sony WH-1000XM3: Initial Support
Add support for Casio GBD-200 and untested support for GBD-100
Casio: Fix alarm handling on all devices
Fossil Hybrid HR: Add button for removing the watchface background image
Fossil Hybrid HR: Support multiple 2nd-TZ and Custom widgets
Fossil Hybrid HR: Add support for native DND functionality
Nothing Ear (1): Add multiple batteries support
Galaxy Buds: Add multiple batteries support
Roidmi: New FM Frequency selector with presets
Mi Band 6: Try to add Alipay to menu settings, untested
FitPro: Support more bands with different bluetooth names
Add activity info to device cards
Add Nekogram X to Telegram notifications
Move location settings out of Pebble menu
Sort devices by alias, if available

Gadgetbridge 0.62.0: Bug fix release to fix steps syncing. Plus, initial support for Casio STB-1000 and Galaxy Buds 2019

Petr Vaněk — Fri, 05 Nov 2021 00:00:00 +0000

Gadgetbridge 0.62.0: Bug fix release to fix steps syncing. Plus, initial support for Casio STB-1000 and Galaxy Buds 2019¶

During this year's summer, in August, a long-standing issue was being dealt with of how time and time-zones are handled in Gadgetbridge for Huami devices. This resulted in a (finally) correct time to be sent to the watches, without time-zone related work around and guessing. Unfortunately, after the switch from daylight saving time (DST) back to normal time, one other place with an issue was discovered, which caused steps being not synchronized. We have fixed this issue and quickly made a release. After you update Gadgetbridge, all previously unsynchronized data will get synchronized automatically. As a result, world clocks and time zone indicators should show correct time, as well as GPS which might get a slightly faster position fix due to having correct initial time to start from. This fix is also fixing time-zone being sent to InfiniTime. Props to Andreas for the fast action on this!

We have received another contribution by Andy Böhler in the form of support for Casio STB-1000. Limitations of GB-5600B/GB-6900B apply. Many thanks!

On the true wireless earbuds front, in this Gadgetbridge version, we have added initial support for another new device, this time it is the original 2019 version of Samsung Galaxy Buds. Be aware that you should not have the Wear app running on the same device while trying to add these earbuds to Gadgetbridge, as these two apps may collide with each other. Adding support for this device would not have been possible without having the example of Nothing Ear (1) in Gadgetbridge codebase. <3

Owners of Amazfit Bip U Pro can now enjoy added support for flashing AGPS updates. And this release is also eliminating a crash when receiving broken weather data from TinyWeatherForecastGermany.

For all user-facing changes since the previous blog post, check the following list:

0.62.0¶

Initial support for Galaxy Buds 2019
Huami: Fix syncing of data in non-DST time
InfiniTime: Fix wrong time zone being sent in non-DST mode
Amazfit Bip U Pro: Support flashing AGPS updates
FitPro: recognize LH716 devices
Add support for Casio STB-1000. Limitations of GB-5600B/GB-6900B apply
Prevent crash when receiving broken weather data from TinyWeatherForecastGermany

Gadgetbridge 0.61.0: Initial support for true wireless earbuds Nothing Ear(1)

Petr Vaněk — Fri, 22 Oct 2021 00:00:00 +0000

Gadgetbridge 0.61.0: Initial support for true wireless earbuds Nothing Ear(1)¶

One of the core team members has provided an initial support for true wireless earbuds Nothing Ear(1). This is the first support of this kind of device in our codebase and it is a perfect fit for an app like Gadgetbridge. Many thanks to Daniele!

Special maintenance tender loving care of this release was devoted to Amazfit Bip U/Pro, with fixes targeting firmware and watchface flashing, Unicode emoji support and language settings (this fixed language settings for many Huami devices).

The Bluetooth enabled USB multimeter UM25 now displays more measured data and the editor for Fossil Hybrid HR watchfaces got the possibility to rotate images, making the user interaction simpler.

Notification management has been moved into a separate settings category and newly allows defining the notification filter to either allow or deny notifications from selected applications. New "Message privacy mode" allows to receive discrete notification with just an icon of the application, which prevents leaking the sender name and/or notification text to your surrounding. On Android 10 and up, the "Hide notification icon" is no longer present in the settings, as it had no effect there.

We also thank to all supporters and translators for their continuous help!

For all user-facing changes since the previous blog post, check the following list:

0.61.0¶

Initial support for Nothing Ear(1)
Amazfit Bip U/Pro: Fix flashing firmware and watchfaces
Amazfit Bip U/Pro: Fix language setting
Amazfit Bip U/Pro: allow unicode emoji
Huami: fix supported languages list on many devices
UM25: show more measured data
Improved notification management including blacklist or whitelist apps settings or discrete notifications with removed text
Fix default daily target distance from 5 to 5000 meters

Gadgetbridge 0.60.0: Initial support for FitPro devices

Andreas Shimokawa — Sat, 25 Sep 2021 00:00:00 +0000

Gadgetbridge 0.60.0: Initial support for FitPro devices¶

Gadgetbridge 0.60.0 has been tagged and should hit F-Droid in a few days!

As the biggest feature, this release adds support for FitPro devices, which has been implemented by Petr Vaněk. The implementation was tested using an M6 band, but other devices which also work with the FitPro app could now also work with Gadgetbridge. For more details please have a look at the wiki

Noteworthy bugfixes include a fix for a wrong log directory named GB_LOGFILES_DIR_IS_UNDEFINED which confused developers and users for some years now, a connection fix for Casio GBX-100 devices, and a fix for weather on the new Mi Band 6 firmware, which introduced many breaking protocol changes. Implementing the new protocol started with Gadgetbridge 0.59.2, was completed with 0.59.3, and probably completely fixed with 0.60.0.

Thanks to all contributors during this release cycle! And to all the people who continuously provide valuable information and test results.

For all user-facing changes since the previous blog post, check the following list:

0.60.0¶

Initial support for FitPro bands
Mi Band 6: really fix weather on new firmware
Casio GBX-100: Fix connection
Fossil Hybrid HR: Lower battery level warning threshold to 10%
Add ringtone preference setting for find your phone feature
Fix a bug where GB_LOGFILES_DIR_IS_UNDEFINED is used as a logfile directory
Remove per-device preferences upon device removal (backup your keys if you do that)
Exclude not worn sleep times from sleep sessions
Add Icelandic and Czech transliteration

0.59.3¶

Mi Band 6: Properly support firmware 1.0.4.38
Mi Band 6: Add Flashlight to menu items
ZeTime: Fix corruption on long notifications

0.59.2¶

Mi Band 6: Support firmware 1.0.4.38 (experimental, still missing features)
InfiniTime: Fix null being displayed as notification title

0.59.1¶

Fossil Hybrid HR: Add power saving feature and many new widgets for the official Gadgetbridge watchface (battery, calories, 2nd TZ, chance of rain)
Fossil Hybrid HR: Support setting metric/imperial mode
Amazfit T-Rex Pro: Try to fix some menu items
Huami: Re-enable setting the timezone correctly with included DST (fixes world time)
Bangle.js: Add functions for pushing bitmaps
Bangle.js: Aadd configurable MTU
Add Heart Rate measurement screen, accessible via heart icon in device action icons

Gadgetbridge 0.59.0: Initial support for SMA Q2 (OSS Firmware), Fossil Hybrid HR improvements

Andreas Shimokawa — Mon, 26 Jul 2021 00:00:00 +0000

Gadgetbridge 0.59.0: Initial support for SMA Q2 (OSS Firmware), Fossil Hybrid HR improvements¶

Thanks to x29a, Gadgetbridge 0.59.0 now supports the open source custom firmware for the SMA Q2 done by Emeryth over at github.com. The devices features an always on reflective display and four buttons. For those who want a fully open source experience including the the firmware on the watch, this could be an option, along with the bangle.js and PineTime.

For Fossil Hybrid HR users, thanks to Arjan Schrijver (again!!) Gadgetbridge 0.59.0 also has a really cool watchface designer for new firmware versions. Without using the official app, it is now possible to create new watchfaces with a custom background and freely positioned widgets (weather, date, steps, HR implemented so far).

For all user-facing changes since the previous blog post, check the following list:

0.59.0¶

Initial support for SMA Q2 OSS firmware (Emeryth)
Fix broken UM25 support
Fossil Hybrid HR: Add watchface designer
use '_' instead ':' in exported and imported file names to fix problems with some Android versions
Fix applying theme as set by the system
Try to improve behavior when quitting Gadgetbridge

0.58.2¶

InfiniTime: Support notification for battery level
Allow importing GPX tracks via Android Intent/Share system
Add option for black background to dark theme
BangleJS, WaspOS: Support for transliteration
Add missing icons to settings items

0.58.1¶

Pebble: Fix broken app manager (regression from 0.57.1)
Bangle.js: Try to fix crash when attempting to load activity chart
Amazfit T-Rex Pro: Add barometer to menu items
Remove battery data when device is being removed
Add transliteration to PineTime
Debug: Allow adding fake testing devices manually
Reduce margin of icons in device_item to keep one row for typical amount of icons

Add GPS track to any recorded sports activity

Petr Vaněk — Sun, 18 Jul 2021 00:00:00 +0000

Add GPS track to any recorded sports activity¶

One of the most missing and wanted features of Gadgetbridge for sports enthusiasts with a Miband (or other Huami device) is to track a sports activity which requests a connection to the original app, to provide GPS tracking. At this point, Gadgetbridge does not have this possibility and as a work around, the 3rd party Heart Rate sensor sharing has been the best option. This works quite well, but has a downside of some activities/data being tracked only in Gadgetbridge while some other data are only in other apps.

Import and link a GPS track¶

With the release of version 0.58.2 we have added the ability to import a GPS track in the form of a GPX file (a file with a GPS recording) and link it to a recorded sports activity inside Gadgetbridge. While this still requires an extra GPS recording app, it allows us to have at least a single place where activities live.

At the same time, this now offers a new possibility to link a GPX file to a sports activity that did not even allow to have a GPS recording in the first place - like outdoor rowing while using the rowing machine recording or pool swimming (if you have a waterproof phone). And, it opens up a door for other devices to provide some sports activity recording info and then link the GPS externally... for example the WaspOS just added a first raw version of a SportsApp which is essentially a stopwatch and a step counter.

Gadgetbridge Sports Activity detail

How does it work¶

In your band/watch, you start recording an activity and you also start recording tracking in your sports tracking app like Open Tracks or FitoTrack. As an extra bonus, you can also set your device to provide Heart Rate to the sports tracking app, like documented here. After you are done with your sports activity and stop the recording on both the band and in the tracking app, you sync the Sports Activities with Gadgetbridge and you take the recording from tracking app and share it with Gadgetbridge - we newly provide a dedicated GPX Receiver, so you can share a GPX from any app in Android. Gadgetbridge will receive the GPX track and will copy it to it's files folder. Then, looking at the details of the recorded activity in the Sports Activities section of Gadgetbridge, you can tap the "edit GPX" icon and select the required GPX track.

Gadgetbridge GPX Receiver and Editing GPX track

What does it provide¶

This gives you a chance to have a single place for all records of activities you have done with your band and also have the associated GPS data with it. Often, the activity recorded by the band will have some extra details like averages of steps and heart rate, number of steps and for some activities like swimming or rowing you can also see the number of stokes and so on. Besides creating a picture of the track to better identify the activity, we do not do any extra data extraction from the GPX, since similarly to the GPS recording, this is a very niche domain and we let those who are already doing a great job with the tracking and mapping apps to calculate and show you some stats of the recorded GPS data.

To see the track in more detail, you can of course use the "Show GPS Track" to export or view the recording in another app - like in Open Tracks, FitoTrack, OsmAnd~, AAT Another Activity Tracker or others.

Visit our wiki to see a full step by step manual with screenshots.

OsmAnd screenshots

Gadgetbridge 0.58.0: Initial Amazfit T-Rex Pro support

Andreas Shimokawa — Tue, 15 Jun 2021 00:00:00 +0000

Gadgetbridge 0.58.0: Initial Amazfit T-Rex Pro support¶

Amazfit T-Rex Pro has been added to list of supported devices, thanks to a PR by GeekosaurusR3x who added the initial support for this device. Thanks!

We have fixed an issue which was causing incorrect step and sleep count for people in countries who use timezones with 30 minutes off the global timezone grid, for example Afghanistan, Burma, India, Iran, Sri Lanka and Venezuela. Users with Android 10 and higher can now utilize separate notification channel for low battery warnings. And, some PineTime owners with InfiniTime firmware who might have encountered an issue with firmware flashing should not experience this problem any more thanks to improvements.

The previous 0.57.1 release has also included some great additions like enhancements the recently added Mi Band 6, including firmware and watchface flashing, Emoji support plus more and also Fossil Hybrid HR improvements.

Thanks everyone for your contributions!

For all user-facing changes since the previous blog post, check the following list:

0.58.0¶

Initial experimental support for Amazfit T-Rex Pro
InfiniTime: Try to fix firmware upgrade by fiddling with optimization rules
Huami: Fix lost samples bug with timezones that are have a 30 minute offset
Fossil Hybrid HR: Block dangerous intents by default and move some settings to developer settings submenu
Improved logging in bonding and tried to recover from weirdness
Use a separate notification channel for low battery warnings

0.57.1¶

Mi Band 6: Add Pomodoro to menu items
Mi Band 6: Support flashing firmware, res and watchfaces
Mi Band 6: Enable Unicode Emoji support
Fossil Hybrid HR: Move commute actions to device specific settings
Fossil Hybrid HR: Use Gadgetbridge App Manager (same as Pebble), allowing quick switching of watchfaces and caching apps for later re-(installation)
Huami: Send changed weight, birthday and height data to watch immediately
Use flexbox layout for icons in device cards, allowing line breaks for small phones

Gadgetbridge 0.57.0: Initial limited Mi Band 6 support, Huami fixes

Andreas Shimokawa — Tue, 18 May 2021 00:00:00 +0000

Gadgetbridge 0.57.0: Initial limited Mi Band 6 support, Huami fixes¶

Thanks to a PR, we recently merged, Gadgetbridge 0.57.0 is the first release which supports the new Mi Band 6. We call support limited, since it does not yet support flashing the firmware or watchfaces and not everything is tested yet. But thanks to your donations we were able to order one, which will (once it arrives) enable us to test and improve device support!

This release also fixes flashing watchfaces on GTR2/GTS2 and probably other newer Huami devices, and adds support for flashing the new AGPS bundles which seem to be mandatory for GTR/GTS/GTR2/GTS2/Bip S with updated firmware versions. While you previously had to flash the GPS almanac and CEP files, with the new bundle format (UIHH), it is possible to flash all needed AGPS files in one go. To obtain the files, we recommend using huafetcher. If you want to play with alternative solutions, we also published code which packs UUIH AGPS bundles here.

Since Gadgetbridge 0.56.2 also was a huge release without blog post, we would like to mention the changes regarding the Fossil Hybrid HR in the last release!

Arjan Schrijver contributed two huge additions for the Fossil Hybrid HR: The possibility to reject incoming calls via SMS, a feature previously only available for the Pebble. Arjan also added support for syncing application icons to the watch - meaning that the watch will actually show a down-scaled gray-scale icon of any app (which looks fantastic for the Element app).

Thanks everyone for your contributions!

For all user-facing changes since the previous blog post, check the following list:

0.57.0¶

Initial limited support for Mi Band 6
Amazfit GTR2/GTS2: Fix for flashing watchfaces
Amazfit GTR/GTS/GTR2/GTS2/Bip S: Allow flashing AGPS bundles
Amazfit Neo: Add lift wrist setting
Fossil Hybrid HR: Restructure settings menus for calibration, file management and physical buttons
Fossil Hybrid HR: Hide old settings on newer firmwares
Improved PineTime/InfiniTime firmware DFU metadata parsing and checks

0.56.2¶

Amazfit GTR2: Improve firmware update support (still partly broken)
Amazfit GTR2/GTS2: Prevent emoji transliterating (Seems to support emoji)
Amazfit GTS2/GTR2: Fixes for setting menu items (Probably still partly broken)
Amazfit GTS2/GTR2: Send wind speed and sunrise/sunset
Fossil Hybrid HR: Send actual application icons for notification on the watch
Fossil Hybrid HR: Support dismissing incoming calls with a quick SMS reply
Huami: Remove unused calendar slots
Huami: Send wind speed in Beaufort for some devices
InfiniTime: Add support for battery info
InfiniTime: Support title for notifications on firmware 0.15
InfiniTime: Implement find device by simulating a phone call
Adjust Steps Charts steps values offset to account for large phone screen sizes
Make Activity Charts dates move as calendar months and to go to now if jumping past today
Make Battery Info time span jump as calendar months and not as days

Gadgetbridge 0.56.1: Many improvements in support for Amazfit Neo and an official Mastodon account

Petr Vaněk — Wed, 07 Apr 2021 00:00:00 +0000

Gadgetbridge 0.56.1: Many improvements in support for Amazfit Neo and an official Mastodon account¶

This release is mainly containing culmination of work done on support for the Amazfit Neo. That includes support for firmware updating, notifications and also settings. Do note, that after updating the device to 1.1.2.52 with Gadgetbridge, there might be a strange connection issue. What you can do is: keep the watch in Gadgetbridge but remove it from paired devices in Android, then re-add again in Gadgetbridge (although it was still there).

We have enabled ongoing notifications for two popular FLOSS sports tracking apps, OpenTracks and FitoTrack. This allows you to observe notifications of an ongoing activity tracked by these apps right on your wrist. Normally, we block ongoing notifications because these could be emitted many times per second and thus cause fast battery drain and also other possible issues. It is therefore recommended to set the Settings → Minimum time between notifications to a few seconds. You can of course always block notifications of these apps completely via the regular Notification blacklist.

We have created an official mastodon account for Gadgetbridge, you can check it out and follow on https://social.anoxinon.de/@gadgetbridge.

For all user-facing changes since the previous blog post, check the following list:

0.56.1¶

Fossil Hybrid HR: Fix compatibility for older firmware revisions
Amazfit Neo: Implement firmware update
Amazfit Neo: Support setting all menu items and fix menu cycling bug
Amazfit Neo: Fix notifications
Amazfit Neo: Support sound settings
Allow OpenTracks and FitoTrack to send ongoing notifications
Make transliteration a per-device setting

Gadgetbridge 0.56: UM25 voltage meter support, Fossil Hybrid HR improvements and more!

Andreas Shimokawa — Wed, 17 Mar 2021 00:00:00 +0000

Gadgetbridge 0.56: UM25 voltage meter support, Fossil Hybrid HR improvements and more!¶

Only one week between releases - and again thanks to contributors, still an impressive changelog. We are currently waiting for F-Droid to sign and publish.

HM25 voltage meters¶

Daniel Dakhno has contributed initial support for HM25 voltage meters. This was a longstanding PR which we almost forgot about, sorry and thanks, Daniel!

Fossil Hybrid HR improvements¶

Arjan Schrijver has contributed various improvements for Fossil HR specific code, like fixing missing menu headers in Gadgetbridge and disabling feature that cannot be used on later firmware revisions.

One of the big improvements - tracking and syncing of dismissed notification was actually generic code which also became a feature for the pebble! We had that kind of feature long ago, but is was broken and disabled. Arjan's take seems to work much better. If it leads to problems or is not wanted, it can always be disabled - per device.

Work around permission problems¶

Many users could not install firmwares from some file managers, with this release many of those problems should be resolved by using requestLegacyExternalStorage. This is probably something that needs more proper fixing in the future, but a workaround is better than nothing ;)

For all user-facing changes since the previous blog post, check the following list:

0.56.0¶

Initial support for UM25 voltage meters
Pebble: Remove read/dismissed notifications on watch (can be disabled)
Fossil Hybrid HR: Remove read/dismissed notifications on watch (can be disabled)
Fossil Hybrid HR: Fixes for running firmware DN1.0.2.20 or newer (disable widget features, currently not supported)
Fossil Hybrid HR: Fix up/back navigation and add titles to Fossil specific menus
Huami: Fix displaying title for calendar events
Use requestLegacyExternalStorage in manifest to fix file access problems in some Android 10 roms
Add header and chart to each activity in Activity list

Gadgetbridge 0.55. Better InifiTime support, new features for all devices

Andreas Shimokawa — Thu, 11 Mar 2021 00:00:00 +0000

Gadgetbridge 0.55. Better InifiTime support, new features for all devices¶

This is the first in many releases without any new Huami/Xiaomi device supported, but still deserved a version bump from 0.54.x to 0.55.0, as we added multiple new device independent features!

Battery logging¶

People were wondering how their battery discharges over time, so we started logging it since release 0.54. There was just no finished graph to show the discharge over time. This is now ready for release and part of 0.55.0. Just tap on the battery icon in the main activity (aka "control center") and have a look!

Activity list dashboard summary calculation¶

In the activity list inside the charts activity, there is a new summary button, which shows aggregated statistics over a configurable time. You might find this useful to compare your activity over different time spans and keep you motivated to even improve ;)

InfiniTime¶

As the popular InfiniTime firmware for the PineTime matures and adds new features, we try to support those new features in a timely manner. This time we added Support for call control and incoming call notification. Make sure to update your PineTime firmware regularly, which is possible though Gadgetbridge ;)

For all user-facing changes since the previous blog post, check the following list:

0.55.0¶

InfiniTime: Fix music control for newer firmware releases
InfiniTime: Support call control and notification
Sony SWR12: Fix broken support since 0.53.0
Wasp-OS: Fix crash on Android 7 and lower
Add activity list dashboard summary calculations
Add battery level logging and graph activity
Use distinct icons for total step and distance values in widget
Flip and scale GPX canvas
Try to fix call notification on outgoing VoIP calls

Gadgetbridge releases 0.53.0, 0.54.0 and 0.54.1: Initial support for even more Amazfit devices, Zepp E and Wasp-os

Andreas Shimokawa — Thu, 25 Feb 2021 00:00:00 +0000

Gadgetbridge releases 0.53.0, 0.54.0 and 0.54.1: Initial support for even more Amazfit devices, Zepp E and Wasp-os¶

First month of the new year 2021 has delivered tons of new devices. We are happy to see new people stepping up and providing the initial support for these watches:

Wasp-os - Daniel Thompson
Amazfit Neo - xaos
Amazfit GTS 2 Mini - Andreas Shimokawa
Huami Zepp E - Andrew Watkins
Amazfit GTR 2e - Jochen S
Amazfit GTS 2e - Andreas Shimokawa
Amazfit X - Stefan Bora

Many thanks to all contributors!

While new devices' support is flowing in, this doesn't mean that all features and functions of these newly added devices are working, but the initial support typically already provides many important aspects required for day to day usage. It also offers a very convenient way to look at these devices in more detail and help to improve their support further. These Gadgetbridge releases (0.53.0, 0.54.0 and 0.54.1) also contain many small and big fixes and improvements all over the place :).

We are super happy to see a wasp-os in the list of supported devices, added by Daniel Thompson himself. Wasp-os (Watch Application System in Python) is an open-source firmware for smart watches that are based on the nRF52 family of micro controllers. Currently this includes the hacker friendly PineTime from Pine64, the Senbono K9 as well as the Colmi P8, which is a popular device with watch modders.

There have been many improvements done to the Fossil HR thanks to ongoing work by Daniel Dakhno. It is an interesting piece of hardware and software, which to some extend provides similar feature set known from the Pebble. Ongoing development has been focusing on support in Gadgetbridge but also on the recently introduced app ecosystem of this watch, which is now in early stage provided by the Fossil HR SDK.

For those tracking their sports results in Gadgetbridge, imperial units settings is now honored in the Widget, Activity list and Sports Workouts. We have also added a small improvement when exporting a GPX track recording, allowing OpenTracks to not duplicate these exports.

For all user-facing changes since the previous blog post, check the following list:

0.54.1¶

Amazfit GTS2e: Really fix broken support
Amazfit Bip S Lite: Fix broken support (probably)

0.54.0¶

Initial support for Amazfit X
Fix missing menu items for GTS 2 Mini (some improvements also for other GTR2/GTS2 models)
Amazfit GTS2e: Fix broken support

0.53.0¶

Initial support for wasp-os on nRF52 devices
Initial support for Zepp E
Initial support for Amazfit GTS 2 Mini
Initial support for Amazfit Neo
Initial support for Amazfit GTR/GTS 2e
Fossil Hybrid HR: Fix bug with unknown data
Fossil Hybrid HR: allow app management on watch from GB
Fossil Hybrid HR: enumerate apps on watch on every connect
Fossil Hybrid HR: Do not configure buttons in unauthenticated mode
Fossil Classic: Fix unknown wearing state
Fossil Classic: Allow synchronizing activity data
Amazfit Bip U: Fix sports activity summary
Huami: Add Strength Training activity type
Honor Imperial units settings in widget, Activity list and workouts
Show all eligible devices in Widget Configuration Activity
Also include step of not-worn samples in weekly step statistics

Adding battery info screen to Gadgetbridge

Petr Vaněk — Mon, 08 Feb 2021 00:00:00 +0000

Adding battery info screen to Gadgetbridge¶

This is a short article to document a process of adding a fairly simple feature to Gadgetbridge. This article is intended to newcomers wanting to participate in Gadgetbridge development who do have some understanding of programming in Java for Android (in Android Studio). Written by a fellow novice programmer in the Android Java ecosystem, it hopes to serve as a basic introduction to some of the concepts used in the Gadgetbridge codebase. There is more information in our wiki, like the Developer documentation and if you are looking for an advice how to add a new device support into Gadgetbridge, there is a comprehensive New device tutorial.

Introduction¶

Gadgetbridge has been showing the wearable device's battery level and low battery warning almost forever since it's beginning. What we want to add is a screen showing us a graph of battery level over time + maybe even some more known details about the battery itself if the device provides it.

First, we need to do some digging and find out how Gadgetbridge knows about device battery stats. This is the first biggest hold-up, because getting familiar with the codebase does take some time but is an essential part of the process. Do spend some time digging through the code to understand the patterns, packages and code layout.

Hooking into device events¶

Where do we begin... searching in files Ctrl-Shift-F for battery sounds like a good place to start for us, but it is a bit too vague, so we try searching for battery low, since we know this can come up in the notification. We get some strings in the strings.xml, so let's find a usage of one of them, notif_battery_low_title via same global search in files. One of the places where this is used is handleGBDeviceEvent(GBDeviceEventBatteryInfo deviceEvent) in AbstractDeviceSupport. This seems to be a good hit, because if we look at usage of this method via Ctrl-B, we can see it being used in most if not all of the implemented devices. This final method is a good place where we can catch the event of getting battery info as it is received from the device. Here, we can hook our routine to store this data into database. We can also note and explore a bit the GBDeviceEventBatteryInfo class used in the handleGBDeviceEvent(GBDeviceEventBatteryInfo deviceEvent), as it provides more details about the battery, if a particular device supports that, for example number of charges, last charge time and so on.

Database¶

To store the data, we need a database table. In Gadgetbridge, database access is provided via greenDAO - Object Relational Mapper for Android. Tables are defined in src/nodomain/freeyourgadget/gadgetbridge/daogen/GBDaoGenerator.java as entities. In the GBDaoGenerator we define our entity, containing properties, which are mapped to database columns. To store different data per device, we must ensure to add mapping to our devices with the addToOne(device, deviceId). The above defined entities will be auto-generated in the nodomain.freeyourgadget.gadgetbridge.entities package. Experiment as needed but make sure to test your object model well and check logcat for error messages, because the DAO can insert values to the database but still throw errors if for example indexes are not set correctly.

After the table definition is done, we must also bump the database schema version: Schema schema = new Schema(VERSION, MAIN_PACKAGE + ".entities");, this is important for database migrations.

Activity¶

At this point, we are getting our battery data, are storing it into database and would like to show a line chart showing battery level over time. To define a new activity (screen), it is important to extend the AbstractGBActivity because it will taking care of the theme (light and dark) language switching and so on.

Charts¶

Gadgetbridge has several places where charts are already used, for that the MPAndroidChart library is being utilized. Some convenience classes are already defined and should be reused, like the AbstractChartFragment, which is especially useful if you want to show activity data like steps or heart rate.

Logging¶

When displaying log messages, never use the e.printStacktrace(). Either use the predefined logger private static final Logger LOG = LoggerFactory.getLogger(Your.class);, or you can also use the toast GB.toast(getContext(), "Error doing xyz: " + e.getMessage(), Toast.LENGTH_LONG, GB.ERROR, e);, this will show the toast, log the stacktrace in logcat and write the logs (if enabled).

General advice¶

Make sure to auto-format the code you write, but leave existing code as is, even if not formatted well, because formatting it would break existing PRs and it also destroys information about the original author.
There are many convenience and utility classes already defined in Gadgetbridge which should be re-used instead of defining again (for example from the nodomain.freeyourgadget.gadgetbridge.util package).
Abstract classes definitions are very commonly used throughout and should also be used where useful.
Pay attention to the warnings and suggestion Android Studio provides, in general code and also in activity layouts.
Try and test your work diligently - there is no bug tracking code in Gadgetbridge and if the app has issues or randomly crashes on some user devices, there is no way to learn about it, unless people make the effort and report it. If you have multiple Android phones, ideally test on them, to see how different Android version behave, what different screen sizes and pixel densities look like.
Also, do not forget to test in both light and dark theme.

Conclusion¶

So this is it, a quick introduction to a very small portion of Gadgetbridge internals. And where is our Battery info screen? Well, the initial code is here and a picture is below, but it needs much more work, like better axis formatting, moving between days... because like always, the small fine details take 80% of the real work. I will keep working on it and it will be released when ready :)

Gadgetbridge 0.52.0: Initial support for Amazfit Bip U Pro

Andreas Shimokawa — Sun, 17 Jan 2021 00:00:00 +0000

Gadgetbridge 0.52.0: Initial support for Amazfit Bip U Pro¶

Christmas holidays was a good time to relax, recharge and take some time off. After that, commits and pull requests started flowing in with various fixes and improvements. One of the contributions has brought support for another variant of Amazfit watches:

Amazfit Bip U Pro contributed by DanialHanif - thank you!

Also the Amazfit GTS2, which was previously supported in theory but was practically unusable due to a pairing bug, should now work properly.

For some reason, data in Weather notification sometimes provides incomplete data, which resulted in weather updates not being sent at all to the smart device. This behavior is now handled properly in this Gadgetbridge release.

Do Not Disturb should now allow priority notifications to go through. Improvements have been done to the pairing flow for devices requiring a key during the bonding process, trying to be more verbose about potential errors, and similar clarification improvements have been done in the Data Management screen, making the data Export/Import process more obvious.

For all user-facing changes since the previous blog post, check the following list:

0.52.0¶

Amazfit Bip U Pro: Initial support
Amazfit GTS2: fix pairing
Amazfit GTS/GTR2: Fix incoming call display
Fossil Hybrid HR: avoid unnecessary widget rendering
A lot of Data(base) Management screen clarifications and improvements
Fix a crash when when forecastConditionType length is 0 in weather notification data
Change Do Not Disturb support to allow priority notifications
Fix problems when pairing some devices which require a pin to be entered

Gadgetbridge 2020: year in review and numbers

Petr Vaněk — Thu, 31 Dec 2020 00:00:00 +0000

Gadgetbridge 2020: year in review and numbers¶

This has been a very busy but good year for Gadgetbridge, with 21 releases since January 2020. It has been the first year after we have migrated to Codeberg. One of the possible concern of the move has been smaller visibility and loss of contributors, but opposite turned out to be true. The visible favorite "star" data is of course lower - the previously reached star numbers on the GitHub hosting went into several thousands (3600 stars), with 200 watchers and 627 forks and current data on Codeberg shows smaller numbers after the first year: 173 stars, 22 watchers and 86 forks, but we did have larger engagement and number of contributors. Big thank you to everybody being involved with Gadgetbridge now or any time before!

Commits, contributors and changed files¶

Here is a compiled table for numbers for all the years of the project:

Year	Files changed	Commits	Contributors
2020	1304	1395	121
2019	805	933	107
2018	615	848	120
2017	597	1005	67
2016	421	1138	30
2015	303	970	14

Table was generated with this script (click to see).

 #!/bin/bash   COMMITS="2020 71ab859c921a3352dc2ad17db2ddb187539510ab  2019 cf870bff8a94b006b4a12b075ba24a1015b865bd  2018 d570ee864d94d74a8b734a93f1abce3995a71569  2017 1722a6dc47aeb66fe7f1bb10c5cde931279eabb2  2016 50cd5b26294c38578077b6ad7e16b88b643711c1  2015 8dd67b146d09801ae2be20ae818daa92995ec6ad"  end="f9e6624646"    #files changed: git diff 20cf15d91f...master --shortstat | awk -F " " '{print $1}'  #commits: git rev-list 20cf15d91f...master | wc -l   echo "|Year|Files changed|Commits|Contributors|"  echo "|--|--|--|--|"  IFS=$'\n'  for LINE in $COMMITS  do  year=`echo $LINE | awk '{print $1}'`  start=`echo $LINE | awk '{print $2}'`  files=`git diff $start...$end --shortstat | awk -F " " '{print $1}'`  commits=`git rev-list $start...$end | wc -l`  commiters=`git log $start...$end --pretty=oneline --format='%aN' | sort | uniq | wc -l`  end=$start  echo "| $year | $files | $commits | $commiters |"  done

It takes some time to understand Gadgetbridge codebase but we are happy to see so many new people being able to do so. In order to make the process easier, documentation has gradually been improved and the new device tutorial has over time become a good guide for anyone with some coding skills, willing to add new device support into Gadgetbridge.

Pull requests¶

As for merge/pull requests it is a bit harder to compare, Codeberg shows us 149 merged pull requests this year. The data of contributors and commits between what the Gitea web interface shows for PRs and what git tells us are a bit different, but we go with what we have.

Issues¶

We have 515 currently opened issues in total and many of them stalled, but they contain interesting suggestions, ideas, research, device requests and more, and although "closed issue is still there", somehow we prefer not to close the stalled ones. About 294 of these issues are active. We have closed 162 issues with 132 new issues open in 2020, which is at least a positive trend, leading to a smaller number of open issues.

Contributors and active users¶

Contributors and active users are the main asset of any project and we are happy to see new people stepping up and contributing with code, which is the most lacking resource we have, as it is a bit easier to help with translations, documentation or bug reports. 132 people have contributed this year and these are people who made a contribution visible via git (code, translation and wiki), but there are also people helping with reporting bugs, managing issues and so on and we are thankful for all their help.

The Matrix chatroom available via Element has also been a nice addition, allowing questions, chats and interaction outside of the issue tracker, currently hosting 220 people. Some people do not prefer the "encryption on" by default, causing some limited visibility of past conversations, but given the history, we are happy with this approach.

One of our biggest concerns has been the gradual decline of contributions from some members of the core team, which has been a big loss. It seems, however, that over time we have been able to gain few permanent helpers and also some drive-by contributors. Hopefully some of them will stick with us for longer time :)

Documentation in wiki has seen many improvements and is a good entry way for any new potential contributors with their first commits.

To make sure we acknowledge all 132 contributors (including wiki editors) of the year 2020, here is a complete list, alphabetically sorted:

115ek, Abdullah Manaz, Adolfo Jayme Barrientos, AiLab, Ainārs, Alex, Allan Nordhøy, Andreas Böhler, Andreas Shimokawa, Andrzej Surowiec, Andy Yang, Anonymous, Artem, Asbesbopispa, Baka Gaijin, Bot, C0rn3j, CE4, Cristian Alfano, Daniel Dakhno, Deactivated Account, Deixondit, Deril, Dmitriy Bogdanov, Dmitry Markin, Dmytro Bielik, Fabio Parri, Florian Beuscher, FransM, Full Name, Gleb Chekushin, Gordon Williams, Hanhan Husna, HenRy, HugoGEORGET, Igor Polyakov, Izzy, J. Lavoie, JF, Jeannette L, Julian Lam, Kintu, KopfKrieg, License Bot, LizardWithHat, Louis-Marie Croisez, Luis zas, Maciej Kuśnierz, Mamut, Marco Alberto Diosdado Nava, Mario, Mario Rossi, Mattherix, Maxim Baz, Memiks, Michael, Michal L, Milo Ivir, Mirko Covizzi, Nathan, Nee Sorry, NicoBuntu, Nikita Epifanov, Nikolai Sinyov, Nur Aiman Fadel, Ondřej Sedláček, Oğuz Ersen, Pander, Pauli Salmenrinne, Pavel, Rafael Fontenelle, Rajesh Kumbhakar, Retew, Roxystar, Samuel Carvalho de Araújo, Saul Nunez, Sebastian Espinosa, Sebastian Obrusiewicz, SnowCat, Szylu, Taavi E, TaaviE, Ted Stein, TinfoilSubmarine, Toby Murray, Unixware, Vincèn PUJOL, Vladislav Glinsky, Vytenis, Yaron Shahrabani, Yukai Li, Zhong Jianxin, andyboeh, angelpup, anonaii, anonymous, bride_salon, ce4, chabotsi, cpfeiffer, dakhnod, fparri, frederic lesur LESUR　Frederic, hackoder, homocomputeris, ildar, izzy, ksiwczynski, luca sain, lucanomax, m-p{3}, mamutcho, marclaporte, marco.altomonte, mkusnierz, mondstern, nautilusx, odavo32nof, opavlov, pangwalla, postsorino, rababerladuseladim, rffontenelle, ssantos, t-m-w, taras3333, vanous, vishnu, xaos, zsolt3991, Étienne Deparis, 陈少举

List was generated with this command (click to see).

#in Gb repo: git log 71ab859c921a3352dc2ad17db2ddb187539510ab...master --pretty=oneline --format='%aN' | sort | uniq #in wiki repo: git log b735016...master --pretty=oneline --format='%aN' | sort | uniq

Past and the Future¶

Work in 2020 has brought support for 15 new devices: JYou Y5, iTag, Fossil Hybrid HR, WatchX(Plus), TLW64, Mi Band 5, Pinetime-JF Infinitime, Sony SWR12 bands, Lefun Smart Bands, Nut, Amazfit Bip S Lite, Amazfit GTR 2/GTS 2, Casio GBX-100, Amazfit Bip U and Amazfit Verge Lite. We are happy to see some open source, open hardware watches finally entering the market and gradually becoming more useful, starting to compete with commercial offerings. Several parts of Gadgetbridge have been reworked including Bluetooth pairing, Sports Activities parsing and displaying, Daily activities, user settings, we gained some more automation possibilities of reacting to button and device events, cleaned up and converted to vector format many icons, fixed many bugs... as per our regular blog posts.

As for the future and what are the plans for Gadgetbridge are, it would be best to hear from our users and even more from people who can contribute changes they would like to see implemented in Gadgetbridge. Also, there are several tasks that need to be tackled related to Android 10/11 changes in permissions so we would be happy to accept contribution in this direction.

We thank you for all your support and hope for another good year while keeping the main promises of Gadgetbridge: Your data about you stays yours. Your conversations forwarded as notifications aren't going anywhere else.

Gadgetbridge 0.51.0: Amazfit Bip U, Amazfit Verge Lite

Andreas Shimokawa — Tue, 22 Dec 2020 00:00:00 +0000

Gadgetbridge 0.51.0: Amazfit Bip U, Amazfit Verge Lite¶

We do not know why Huami releases so many new devices every year. These have become too much to buy all of them, but it is always nice to have pull requests from the community, which happened for the Bip U and Verge Lite during this cycle. Thank you!

But there is a lot more to this release!

Apart from the usual bug fixes and tweaks, we overhauled the daily stats widget completely which is now much better looking and more functional.

Also device code contributors have pushed improvements, most notably the Casio GBX-100 and Bangle.js which now support activity data recording.

We hope this release will be in F-Droid before Christmas.

Since this might be the last blog post for 2020:

The Gadgetbridge team wishes Merry Christmas and a better new year that 2020 was for most of us!

For all user-facing changes since the previous blog post, check the following list:

0.51.0¶

Amazfit Bip U: Initial support
Amazfit Verge Lite: Initial Support
Amazfit T-Rex: Add missing menu items, remove non-existent
Amazfit Bip S: Fix crash with notifications with only a title (GitNex does this)
Casio GBX-100: Add step count data and more device settings
Fossil Hybrid Q: Support firmware upgrade
Bangle.js: Support for HRM and steps activity recording
Huami: Add new option to properly distinguish connected advertising and 3rd party hr exposure
Huami: Use blue icon instead of rainbow color icon for Signal (the rainbow icon was blue in early days)
Complete overhaul of the daily stats widget
Better error message for invalid authentication keys

On building safe bridges

Petr Vaněk — Fri, 11 Dec 2020 00:00:00 +0000

On building safe bridges¶

Cool gadgets give us some really great possibilities, like tracking our activities, controlling music and smart home devices, receiving notifications and more. But in our strive for better, faster, lighter, smarter, cheaper... we often forget the down side of our endeavors. Apps providing connections to our devices do receive all our movement information, including precise location. We have written about it previously, in 2017. But maybe you do not care about the details of your whereabouts being shared and only care about your communication. And your communication with friends and family is surely safe with secure apps that have become widely popular, right? But unfortunately, every notification that is forwarded to your smart bracelet even though you received it from some very secure, end to end encrypted app like Matrix or Signal, has been seen by the bracelet's companion app. These are closed source applications provided mostly by the vendor of the gadget and it is only up to the vendor to decide if they send these conversations to their servers for further processing. It is now up to us to decide if we want to give them fully detailed view into our lives.

So this is where Gadgetbridge comes in, of course, but it is important to realize that it takes a substantial effort to keep things running correctly. To ensure stable Bluetooth connection. To provide reliable firmware update system. To collect and display daily activities in a user friendly way. To keep up with firmware updates of all those supported watches and make sure stuff does not break (too much). And also, to provide a safe bridge between the smart bracelet and the phone, so notifications are not observed by other applications. For these very reason, Gadgetbridge does not have any network access, in fact it does not have network permission, so the Android system does not allow it to have any network communication at all. And this is good - good for the safety, good for the clear mind. Nice, clean, safe bridge between your phone and your smart bracelet's app. Thanks to all currently active but also to all previously very active developers for all the hard work!

But we must have even higher goals. People would like to not only collect their own data, but they also want to use it, look at it, analyze it or share it - if they want. So we should not only collect all the steps, activities hear rates... we must also provide a way to export it to be able to use it on day to day bases, easily. To share for example GPS information recorded on some watches, Gadgetbridge does allow exporting GPX files of recorded sports activities as files or as intents that other applications can use. Gadgetbridge can also export full database of all collected stuff (steps, heart rate and so on), together with all user preferences. But we must ensure that there are also apps that can receive our data - we should build more connections between our apps. Recently, the good folks at Open Tracks improved their GPX input intent listener, providing yet another app that can directly receive recorded GPS track shared by Gadgetbridge. They also worked hard to navigate through the confusing landscape of Bluetooth Low Energy communication to be able to accept data from heart rate sensor, enabled on the bracelet via Gadgetbridge settings. Same heart rate data can now also be used with the FitoTrack. The InfiniTime developers improved music controls and firmware updates, making a nice connection to Gadgetbridge. And we all should keep looking around for improving things in our small islands of app created silos and connect them with nice bridges. I strongly advice you to be creative in your thinking, talk to the developers of your favorite apps and propose ways for apps to keep talking to each other. No ~~[hu]man~~ app should be an island.

Gadgetbridge 0.50.0: Initial support for Casio GBX-100

Andreas Shimokawa — Sat, 28 Nov 2020 00:00:00 +0000

Gadgetbridge 0.50.0: Initial support for Casio GBX-100¶

This release comes just two weeks after the previous version bump, but brings a support for a new device:

Casio GBX-100 contributed by Andreas Böhler.

Another important new feature in this release is support for flashing watchfaces for the Amazfit/Mi Band 5. These devices support up to three custom watch faces plus two factory ones. Even though it looks easy then you know how, it took a lot of time and effort to analyze and implement this correctly.

On the user interface side, the Sports Activities got their Dashboard view revamped to better match the design of the recently added Activity List Dashboard. And, utilizing all the work done on our new sortable type of preference widget, the Charts Tabs can now be selectively enabled/disabled and also arranged as preferred by each user, independently for each device.

Also, many important improvements, fixes and also translations have been constantly flowing in thanks to much appreciated help of many contributors!

For all user-facing changes since the previous blog post, check the following list:

0.50.0¶

Initial support for Casio GBX-100
Mi/Amazfit Band 5: Support watchface installation
Mi Band 5: Add missing NFC menu item
Casio GB-5600B/GB-6900B: Add configurable disconnect notification
Casio: Add support for synchronizing profile settings
Fossil Hybrid HR: Keep widget values after widget reload
Improve Sports Activities dashboard and Filter
Bug fixes for notification removal
Allow to clear activity labels.

Gadgetbridge 0.49.0: Lots of improvements - and even more Huami devices supported!

Andreas Shimokawa — Tue, 17 Nov 2020 00:00:00 +0000

Gadgetbridge 0.49.0: Lots of improvements - and even more Huami devices supported!¶

Notes from under the bridge

Gadgetbridge 0.49.0 has been released, closing up yet another interesting period of development.It is already available on F-Droid!

New supported devices¶

Initial support for few new Huami devices has been added:

Amazfit Bip S Lite
Amazfit GTR 2/GTS 2

Thanks to contributors who own these devices and were able test and integrate the required changes into Gadgetbridge. Adding a new without us having access to the physical device can be hard, so any effort is appreciated. To make new developer's lives easier, the New Device Tutorial has been improved a lot, providing good guidance in adding a new device, storing activity data and also providing preference interface and storage.

Improvements for Fossil Hybrid HR and InfiniTime¶

Thanks to contributor Daniel Dakhnod, the Fossil HR, among a lot of other small improvements, now supports rejecting calls on the latest firmware again (up tp DN1.0.2.19).

For PineTime(InfiniTime), Gadgetbridge 0.49.0 now also supports the latest 0.9.0 firmware.

One of the most requested feature has been the ability to sort menu items on the bracelet. For the longest, Gadgetbridge was able to enable/disable menu items, but did not provide sorting. The issue was not in the underlying device support, but rather in Android widget library, which does not really have any sortable list of items that can be toggled on/off and at the same time acted as a source of data for the Android's Preferences Settings model. After several research sessions, a suitable library was adopted. It is now very simple for Gadgetbridge developers to use this sortable list in device settings and by turn end users now have the ability to enjoy enabling and sorting menu items and shortcuts on all Huami devices (except Mi Band 2).

Activity views and charts¶

The Sports Activity detail view got a simple GPS track drawing, together with the ability to take a screenshot of the full page of this activity. Not only it is nice to be able to share the complete screen with detailed activity data, chart of activity and heart rate plus the GPS view, but at the same time, Android top bar menu icons are not included, adding slightly more privacy to the shared image.

Sports Activities are parts of the day that are explicitly recorded by the user, but many times, this recording is an extra effort. To be able to overcome this limitation, a new Activity List has been added to Gadgetbridge Charts . Under the hood it goes through the recorded data and searches for active periods from your day. Parameters for how these sessions are determined can be adjusted in Charts → Preferences → Activity list. Today, we are pushing out a dashboard view for each day, which is calculating a summary of all active parts of the day and also comparing it to your goals. These goals have been in the menu: Settings → About you for a very long time but have been used only occasionally throughout Gadgetbridge. It is always good to set these values, because some bands require them for their internal calculations. The Activity List makes use of data in this settings to draw charts of your active steps, active time and distance, compared to your daily goals. So make sure to adjust them.

Intensity of activity¶

One of the new items in Activity List but also in the Sleep charts is intensity. It is an interesting value which typically does not surface as a number, but in fact it has been used throughout Gadgetbridge charts a lot: the green spikes on axis Y in activity charts? Intensity. The light and dark blue spikes on axis Y in your sleep charts? Also intensity. It is a value (normalized to a decimal between 0 and 1) that is representing a strength or an intensity of your activity, as determined by the bracelet. At night, the more you move, the higher this intensity is. During an activity or walk, the more your arm moves, the number seems to go up. So it seems good to expose this number even more, to be able to observe it, typically labeling it as Movement intensity. The displayed result is not calculated as an average but rather as a total sum of the intensity of a particular activity in activity list or in your sleep. Hopefully you'll find it useful.

For all user-facing changes since the previous blog post, check the following list:

0.49.0¶

Initial support for Amazfit Bip S Lite
Initial support for Amazfit GTR/GTS 2
Huami: allow sorting of shortcuts and menus (all except Mi Band 2)
Amazfit Band 5: Allow enabling SpO2 menu
Mi/Amazfit Band 5: Support shortcuts (right/left swipe)
Amazfit GTS: Fix firmware flashing on Firmware >=0.1.1.16
Amazfit GTR: Fix firmware flashing on Firmware >=1.3.7.16 or >=1.7.0.10
Amazfit GTR/GTS: Add missing settings menu item in preferences
Fossil Hybrid HR: Remove Android notifications when deleting them from the watch
Fossil Hybrid HR: Enable rejecting calls on newer firmwares
Fossil Hybrid HR: Support hands calibration
Fossil Hybrid HR: Support factory reset
InfiniTime: Improve notification support for firmware >=0.9
Add version to About screen
Show GPS track in Sport Activity detail screen
Add Activity List Dashboard/Summary view to charts
Add heart rate average to Activity and Sleep charts
Add intensity to Sleep charts
Recognize Wire messenger as a chat application
Add confirmation dialog for find device button

Gadgetbridge 0.48.0: Three completely new devices supported

Andreas Shimokawa — Sun, 18 Oct 2020 00:00:00 +0000

Gadgetbridge 0.48.0: Three completely new devices supported¶

Gadgetbridge 0.48.0 has been tagged and will appear on F-Droid soon! As always, this can take a few days.

Six code contributors and twenty one translators have contributed more then 130 commits to the latest release of Gadgetbridge, bringing support for three new devices:

The Sony SWR12 bands
Lefun Smart Bands
Nut

The Nut devices use the Nordic firmware update protocol (DFU) by using the official nordic library. This enabled us to also use it for other devices like the like the PineTime (InfiniTime), and probably more devices in the future. PineTime InfitiTime firmware's music control, being recently improved, also got improved support in Gadgetbridge. All of the work mentioned in this paragraph was contributed by Taavi Eomäe. Thanks Taavie!

A last minute change also adds experimental and untested support for the Amazfit Band 5. If you have the device, please try it and report bugs!

On the Fossil Hybrid HR front, support for the latest firmware version was added. For testing and debugging there is now a new activity that allows to send and receive files from/to the watch, something you should only try if you know what you are doing, as it might damage your watch, break your fonts or even worse.

After recent regression, the Find your phone feature has been made working on Android 10 again, thanks to previous work on Companion Device Manager pairing support.

Sports Activities detailed view can now be shared as full screen picture, including the intensity and heart-rate chart view.

We have also added initial support for list of activities for each day. These are not based on recorded activities or GPS, but are detected by number of steps and intensity, as recorded. Parameters of the detection can be tweaked in the Charts Preferences. And, in order to calculate and display correct distance from collected steps, step length has been added to the About You menu.

For all user-facing changes since the previous blog post, check the following list:

0.48.0¶

Initial support for Sony SWR12
Initial support for Lefun Smart Bands
Initial support for Nut devices
InfiniTime: Improved music support for latest firmware
Fossil Hybrid HR: Fixes and better support for newer firmwares
Fossil Hybrid HR: Debug activity for dumping and sending resources to the watch
Huami: Improve style of sports activity lists
Add sport activity list tab in charts
Allow sharing of sports activity summaries as image (full scroll view)
Weather: Fix wind speed and direction not being passed properly
Fix find your phone feature on Android 10 (need companion device pairing)

0.47.2¶

Amazfit Bip S: Send sunrise and sunset on latest firmware if enabled
Huami: Support new firmware update protocol (fixes firmware flashing with firmware 2.1.1.50/4.1.5.55 on Amazfit Bip S)
Huami: Allow flashing latest GPS firmware
InfiniTime: Add support for music control
Pebble: Fix steps on home screen widget
Bangle.js: Fix issue where call state reporting was corrupted
Add charts to sport activity summary view
Add missing icons for new sport activity types

0.47.1¶

Huami: Add new activity types found in recent Bip S firmware
Huami: Many improvements to the activity summary view, including a global view for all devices, filtering per activity type and much more
Huami: Prevent generating broken elevation data when they are not sent by the device
Amazfit Bip S: Allow flashing more font files and GPS almanac (only cep worked before)
Pinetime-JF: Recognize device if it announces itself as InfiniTime
ZeTime: Fix weather forecast icons on older firmwares, try to send weather even if no firmware version was detected
HPlus: Improve Unicode, notification lenth and weather support
Fix warnings and colors for AboutScreen

Gadgetbridge 0.47.0: Pinetime-JF, big update for Huami devices

Andreas Shimokawa — Mon, 31 Aug 2020 00:00:00 +0000

Gadgetbridge 0.47.0: Pinetime-JF, big update for Huami devices¶

Gadgetbridge 0.47.0 has been tagged and will appear on F-Droid soon! As always, this can take a few days.

This release finally has initial support for Pinetime-JF (JF Firmware for the PineTime watch). You can check progress of the JF Firmware here. This initial support is not really usable, it only allows setting the time, displaying PineTime's software and hardware revisions, and seeing notification titles on the watch (without vibration). As the firmware improves, we plan to support new upstream feature as soon as we can.

Further work has been done on improving the Bluetooth pairing activity on all devices. On phones running Android 8.0 (API level 26) and higher, it’s possible to use companion device pairing. After the device is paired using this method, the device can leverage the REQUEST_COMPANION_RUN_IN_BACKGROUND and REQUEST_COMPANION_USE_DATA_IN_BACKGROUND permissions to start the app from the background. This might provide stability benefit to Gadgetbridge. To take advantage of this pairing method, you must pair the device again, see this wiki article for a step by step procedure.

Many device icons have been re-drawn into vectors, allowing nicer icon rendering, taking advantage of capabilities of modern phones. Also, new icons have been added for additional sports activities.

To be true of it's name, Gadgetbridge added device events, which is a way to utilize events detected on a band or a watch (for example when you fall asleep or wake up) and trigger a custom action on the phone. There are several included media actions, like Play and Pause. Even further, one can also choose to send an Android Broadcast message (this can be customized) and utilize other apps like Easer or Tasker to perform further actions based on this message. So here we have it - gadget events bridging :) This feature is available for all Xiaomi/Huami devices except the Mi Band 1 and 2.

For Sport enthusiasts, we now provide much more comprehensive set of information about sports activities and workouts due to enhanced decoding of data from Xiaomi/Huami devices which support workout modes (all except Mi Band 1 and 2). This allows us to retrieve more data for "Activity/Workout" modes, like biking and treadmill, but also for new activities like Yoga (yes, 🧘...), swimming, jumping rope and others (if supported on the watch/band). Detailed view of each sport activity is giving you very comprehensive set of data about timing, ascending, descending or swimming style, tempo, calories etc, depending on the type of workout. You can also set your own labels and use the Filter to slice and dice the view as needed and then see statistics summary calculation with total duration, distance or calories for the listed/filtered items. Wiki article with pictures here.

For all user-facing changes since the previous blog post, check the following list:

0.47.0¶

Initial experimental support for Pinetime-JF (not yet usable)
HPlus; Recognize Lemfo SG2
Huami: Support events forwarding via intents or direct triggering of certain actions (eg. stop music when fall asleep)
Huami: Add Sports Activity Detail screen from decoded sports summary values
Huami: Recognize and decode lot more activity (workout) types
Amazfit Cor/Cor2: Allow workout syncing
Add Sports Activity Summary filtering and statistics
Many icons have been re-drawn as vectors, also several new device and sports activity icons added
Many improvements to the Bluetooth discovery and scanning
Fix crash when opening GPX files

Gadgetbridge 0.46.0: Mi Band 5 and TLW64 support

Andreas Shimokawa — Tue, 11 Aug 2020 00:00:00 +0000

Gadgetbridge 0.46.0: Mi Band 5 and TLW64 support¶

Gadgetbridge 0.46.0 has been release and after a whole week of waiting it landed in F-Droid.

This release, which adds TLW64 support contributed by Erik Bloß, also has support for the new Mi Band 5, which is basically runnig on the Mi Band 4 code.

On the Huami front there are fixes for GTR/GTS activity data on newer firmware version. There seems to be extra data which we ignore for now to make the current code run with it. In the future we will look at making use of the new data which unfortunately would need a new database schema.

Another quite big changes was contributed by Taavi Eomäe, who refactored the device discovery activity which fixes tons of bugs and also new features, like displaying already paired devices an notes about devices needing a pairing key.

The release 0.45.0 did not have its own blog post, please refer to the list below for details on what changed with the 0.45.0 and 0.45.1 releases.

But there is one thing I would like to highlight. There is a new, experimental way of getting weather data from an new open source app developed by Pawel Dube, that directly supports Gadgetbridge. No need for API keys. The App is still alpha and work in progress, but we highly recommend trying it. TinyWeatherForecast Don't be fooled by the name it supports a lot of locations worldwide. If you like it please give it a star on Codeberg.org!

For all user-facing changes since the previous blog post, check the following list:

0.46.0¶

Initial support for Mi Band 5
Initial support for TLW64
Amazfit GTR/GTS: Fix broken activity data on newer firmwares
Big refactoring of the device discovery activity (See PR #1927 description for details)
Add about screen
New icon for Amazfit Bip
Avoid duplicated entries in preferred media player selection
Avoid a lot of crashes and improve error handling in various places

0.45.1¶

Amazfit GTR/GTS: Fix connection issue with latest firmwares (probably other Huami devices also affected)
Add experimental support for TinyWeatherForecastGermany

0.45.0¶

Initial support for Amazfit T-Rex
Amazfit Bip S: Support installation of latest .res
Amazfit Bip S: Support longer notification messages
Huami: Limit weather forecast to 7 days to fix problems with weather notification 0.3.11
Huami: Improve music playback information
Huami: Ensure cutting strings on UTF-8 border
Stop incoming call notification when VoIP calls are missed
Fix a crash when with Farsi translation

Gadgetbridge 0.44.0: Initial WatchX(Plus) support and much more

Andreas Shimokawa — Wed, 06 May 2020 00:00:00 +0000

Gadgetbridge 0.44.0: Initial WatchX(Plus) support and much more¶

Gadgetbridge 0.44.0 has been released! Let's play the F-Droid waiting game.

This release finally merges support for WatchX(Plus). Support for this watch has been contributed to "ksiwczynski", "mkusnierz" and finally "mamutcho", who also did the final polishing before official inclusion. We do not own the device ourselves, but we believe it works ;)

Thanks to a donation of a brand new ZeTime (THANK YOU!), I could finally test the state of ZeTime support and fix some long standing issues, plus add support for rejecting calls from the watch. There will be probably further fixes in the next release.

Further improvements and fixes were also done for Fossil Hybrid HR, most of them contributed by Daniel Dakhno again. Thanks! :)

For all user-facing changes since the last blog post, check the following list:

Version 0.44.0¶

Initial support for WatchX(Plus)
Add support for Amazfit GTR Lite (untested and incomplete)
Fossil Hybrid HR: Fix some issues with custom widgets
Fossil Hybrid HR: Allow setting alarm titles and descriptions
Fossil Hybrid HR: Fix step data parsing
Amazfit GTS: Fix setting menu items with low MTU
Amazfit GTR: Allow setting menu item like GTS
ZeTime: Support setting the watch language
ZeTime: Support rejecting calls
ZeTime: Try to fix weather conditions on newer firmware
ZeTime: Fix could not synchronize calendar on connect
ZeTime: Fix calendar event time and date
ZeTime: Send up to 16 upcoming calendar events on connect if option is enabled
Allow set light/dark theme according to system settings (new default)

Version 0.43.3¶

Fossil Hybrid HR: Initial support for activity tracking (no sleep yet)
Fossil Hybrid HR: Support setting alarms on newer firmware
Amazfit GTR/GTS: Fix flashing watchfaces and maybe firmware/res update (still untested)
Amazfit GTS: Support enabling/disabling menu items on the watch
Implement transliteration for Korean

Version 0.43.2¶

Fossil Hybrid HR: Allow choosing and cropping image to be set as watch background
Fossil Hybrid HR: Option to draw circles around widgets
Fossil Hybrid HR: Experimental firmware update support
Fossil Hybrid HR: Fix vibration strength setting
Huami: Do not display firmware information and whitelist information when flashing watchfaces
Huami: Disable air quality indicator on Huami devices instead of showing 0
Bangle.js: Change encoded char set to match Espruino's 8 bit fonts
Steps/Sleep averages: Skip days with zero data

Version 0.43.1¶

Initial support for Amazfit Bip S (incomplete, needs the official app once to obtain the pairing key)
Amazift Bip Lite: Allow relaxing firmware checks to allow flashing of the regular Bip firmware (for the brave)
Fossil Hybrid HR: Fix notification history on newer firmwares
Fossil Hybrid HR: Add option to disable widget circle
Bangle.js: Don't set time if the option is turned off in settings
Bangle.js: DST and time zone fixes
Add Arabic-style Eastern Arabic numerals to transliteration

Gadgetbridge 0.43.0: Fossil Hybrid HR

Andreas Shimokawa — Wed, 25 Mar 2020 00:00:00 +0000

Gadgetbridge 0.43.0: Fossil Hybrid HR¶

Gadgetbridge 0.43.0 has been released and will be in F-Droid, god knows when. If she exists.

This release adds initial support for Fossil Hybrid HR. Again most of the work was contributed by Daniel Dakhno. Thanks Daniel! Unfortunately this device needs server side pairing with the official Fossil app once. The procedure we used to obtain the device specific secret key is complicated and described briefly in our wiki. There might be other easier methods by "cracking" the app but we refrained from trying. Please the wiki read before you decide this otherwise very nice device.

For user-facing changes since the last blog post, check the following list:

Version 0.43.0¶

Initial support for Fossil Hybrid HR (needs complicated key extraction, read wiki)
Fossil: Allow switching off the Q Icon and use the default Gadgetbridge icon
Fix VoIP call handling during DND
Fix find-my-phone for Android 10
Huami: Fix crash when calendar event description or title was null
Huami: Ignore all-day events when syncing calendar events

Version 0.42.1¶

Fix accepting/rejecting calls on Android 9
Mi Band 3/4, Amazfit Bip/Cor/GTS/GTR: Option to sync calendar events as reminder

Gadgetbridge 0.42.0: iTag support

Andreas Shimokawa — Sun, 09 Feb 2020 00:00:00 +0000

Gadgetbridge 0.42.0: iTag support¶

Gadgetbridge 0.42.0 has been released and is already build by F-Droid.

This release adds initial support support for "iTag" devices, contributed by Taavi Eomäe. Lacking any compatible devices, we cannot really tell you anything about it though ;)

Apart from iTag support, Taavi also contributed various other small fixes and improvements to this release. Thanks!

For user-facing changes since the last blog post, check the following list:

Version 0.42.0¶

Initial iTag support
Fix indefinitely lasting bluetooth scans when location permission has not been granted
Try to stop incoming VoIP call notification when the call is answered
Vectorize some icons and add a new Mi Scale 2 icon
Mi Band 4: Make high MTU optional, fixes problems on some phones
ZeTime: Fix probably broken support (duplicate id used by Fossil)

Version 0.41.1¶

Huami: allow to have alarms without snooze feature
Mi Band 2: Properly stop a call notification when text notifications are disabled
VoIP calls: ignore notifications with only one action, assuming it is an outgoing call
Try to fix notifications from Business Calendar

Gadgetbridge 0.41.0: JYou Y5 Support

Andreas Shimokawa — Thu, 09 Jan 2020 00:00:00 +0000

Gadgetbridge 0.41.0: JYou Y5 Support¶

Gadgetbridge 0.41.0 has been released and will appear on F-Droid soon.

This release adds support for the JYou Y5 and improved button actions for Mi Band 2 And Amazfit Bip.

JYou Y5 support was contributed by Pavel Elagin in a very old PR we never merged. It was recently found and polished by Da Pa and finally merged! Thank you guys!

Improved button action support was contributed by vanous! It now much easier to setup this feature for music control, and long presses are also supported. Thanks you vanous!

Speaking of the Amazfit Bip, you should check out BipOS which is a patched version of the original firmware which adds the ability to create own apps! Unfortunately depends on non-free tools (free as in beer).

For user-facing changes since the last blog post, check the following list.

Version 0.41.0¶

JYou Y5: Initial support
Mi Band 2/Amazfit Bip: Redesign button actions for easy music control setup and support long presses on Bip
Amazfit Bip: Remove RES file limit (for BipOS)
Huami: Automatically toggle alarm switch when toggling on the Band/Watch while in Alarm settings in Gadetbridge
Recognize Pixart-Messenger as Chat App

Version 0.40.1¶

Mi Band/Amazfit: Recognize changes when toggling alarm on device (immediately when connected, else when connecting)
Mi Band/Amazfit: Fix some bugs with stuck connection when re-connecting
Mi Band 4: Support higher MTU for multiple times faster firmware transfer (probably also Amazfit GTR/GTS)
Amazfit Cor: Fix setting language to Chinese manually

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

Andreas Shimokawa — Sat, 21 Dec 2019 00:00:00 +0000

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.

And finally, Gadgetbridge 0.40.0 has been released and will appear on F-Droid soon!

This release adds support for the Fossil Q Hybrid and Bangle.js!

Fossil Q Hybrid support was contributed by Daniel Dakhno. Thanks Daniel!

Bangle.js support came directly from Gordon Williams of Espruino! And marks a special milestone for Gadgebridge. It is the first time that Gadetbridge support was contributed directly from the creators of a device! The Bangle.js is a fully hackable smartwatch with an open source firmware and apps written in JavaScript. For more information visit banglejs.com.

For user-facing changes since the last blog post, check the following list.

Version 0.40.0 (WIP)¶

Fossil Q Hybrid: Initial support
Bangle.js: Initial support
Reserve Alarm for Calendar feature restricted to Mi Band 1/2 and moved to per-device settings
New icon for App Manager

Version 0.39.1¶

Try to actively re-connect when a connection gets interrupted (interval grows up to 64 seconds)
Mi Band2/Amazfip Bip: Make button action settings per-device and enable for Amazfit Bip

Version 0.39.0¶

Amazfit GTS: Initial and incomplete support, mostly untested
Add forward/backward buttons to charts for faster navigation
Debug: allow to reset last fetch date for Huami devices

Donations via Liberapay re-opened

Andreas Shimokawa — Thu, 21 Nov 2019 00:00:00 +0000

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!

Gadgetbridge 0.38.0: Amazfit Bip GTR (NOT RECOMMENDED)

Andreas Shimokawa — Mon, 28 Oct 2019 00:00:00 +0000

Gadgetbridge 0.38.0: Amazfit Bip GTR (NOT RECOMMENDED)¶

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.

As always, we want to remind you that we will move completely to Codeberg this autumn. The wiki can already only be updated there, while all wiki changes will be mirrored to github. Please create a Codeberg account, if you want to modify the wiki or if you want your issues/PRs and comments to be properly assigned to you again on Codeberg.

The reason for the move in one sentence: A free project deserves a free home!

For user-facing changes since the last blog post, check the following list.

Version 0.38.0¶

Amazfit GTR: Initial and incomplete support, mostly untested
Amazfit Bip: add Portuguese to the list of selectable languages
Mi Band 4: Enable emoji font setting
Makibes HR3: Support the english version
Makibes HR3: Enable bluetooth pairing for working reconnection
Work around crash when trying to display changelog
Sleep detection settings: Rolling 24 hours (existing style) or Noon to noon
Add alternative color to heartrate in chart settings

Version 0.37.1¶

Amazfit Bip Lite: Support flashing firmware and watchfaces

Gadgetbridge 0.37.0: Makibes HR3 support, and finally Amazfit Bip Lite (NOT RECOMMENDED)

Andreas Shimokawa — Sat, 12 Oct 2019 00:00:00 +0000

Gadgetbridge 0.37.0: Makibes HR3 support, and finally Amazfit Bip Lite (NOT RECOMMENDED)¶

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.

There are some contradicting claims about the Bip Lite, so it might be possible to pair without a key. If that should be the case, we will release an update.

The reason for the move in one sentence: A free project deserves a free home!

For user-facing changes since the last blog post, check the following list.

Version 0.37.0¶

Initial Makibes HR3 support
Amazfit Bip Lite: Initial working support, firmware update is disabled for now (we do not have any firmware for testing)
Amazfit Cor 2: Enable Emoji Font setting and 3rd party HR access
Find Phone now also vibration in addition to playing the ring tone
ID115: All settings are now per-device
Time format settings are now per-device for all supported devices
Wrist location settings are now per-device for all supported devices
Work around broken layout in database management activity
Show toast in case no app is installed which can handle GPX files
Mi Band 4/Amazfit Bip Lite: Trim white spaces and new lines from auth key
Mi Band 4/Amazfit Bip Lite: Display a toast and do not try to pair if there was no auth key supplied
Skip service scan if supported device could be recognized without uuids during discovery

Version 0.36.2¶

Amazfit Bip: Untested support for Lite variant
Force Lineage OS to ask for permission when Trust is used to fix non-working incoming calls
Charts: List multiple sleep sessions per day

Version 0.36.1¶

Mi Band 2/3/4, Amazfit Bip/Cor: Add setting to expose the HR sensor to 3rd party apps
Mi Band 4: Really fix weather location not being updated on the Band
Mi Band 4: Fix call notification not stopping when call gets answered or rejected on the phone
Amazfit Bip/Cor: Support for custom emoji font
ZeTime: Enable emoji support
ZeTime: Make watch language the same as the phone language by default
New status and alarms widget
Fix crash when entering notification filter settings
Make diagram settings accessible from charts activity
Add option to hide the floating plus button in the main activity
Fix a potential crash on Android 4.4 KitKat

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

Andreas Shimokawa — Sun, 25 Aug 2019 00:00:00 +0000

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.

The version bump which usually happens after a major new feature landed or a new device is supported this time happened because we now support the Mijia LYWSD02 (Smart Clock with Humidity and Temperature Sensor). A very nice e-Paper device, but unfortunately without any pairing or security. Means everyone can read recorded humidity and temperature. The support only includes setting the time for now - but that saved me from installing Mi Home. And this is what our project is about. Freeing your devices.

As always, we want to remind you that we will move completely to Codeberg this summer/autumn. The wiki can already only be updated there, while all wiki changes will be mirrored to github. Please create a Codeberg account, if you want to modify the wiki or if you want your issues/PRs and comments to be properly assigned to you again on Codeberg.

The reason for the move in one sentence: A free project deserves a free home!

For user-facing changes since the last blog post, check the following list.

Version 0.36.0¶

Initial Mijia LYWSD02 support (Smart Clock with Humidity and Temperature Sensor), just for setting the time
Mi Band 3/4: Allow enabling the NFC menu where supported (useless for now)
Mi Band 3/4, Amazfit Cor/Bip: Set language immediately when changing it (not only on connect)
Mi Band 3/4, Amazfir Cor/Bip: Add icons for "swimming" and "exercise"
Mi Band 4: Support flashing the V2 font
Mi Band 4: Fix weather location not being updated on the Band
Mi Band 4: remove unsupported DND setting from settings menu
Amazfit Bip/Cor: Fix resetting of last fetched date for sports activities
Amazfit Bip: Fix sharing GPX files for some Apps
Pebble: Use Rebble Store URI
Support LineageOS 16.0 weather provider
Add Averages to Charts
Allow togging between weekly and monthly charts

Version 0.35.2¶

Mi Band 1/2: Crash when updating firmware while phone is set to Spanish
Mi Band 4: Enable music info support (displays now on the band)
Mi Band 4: Support setting date format (for built-in watchfaces)
Amazfit Cor 2: Try to fix empty menu on device

Version 0.35.1¶

Mi Band 4: Support flashing watchfaces, res and firmware (.ft untested)

Gadgetbridge 0.35.0: Mi Band 4 support (NOT A RECOMMENDED DEVICE)

Andreas Shimokawa — Wed, 24 Jul 2019 00:00:00 +0000

Gadgetbridge 0.35.0: Mi Band 4 support (NOT A RECOMMENDED DEVICE)¶

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.

This will probably not change in the future, since the initial pairing sequence has been changed by the firmware. Instead of us choosing a random secret key, now it seems that only Mi Fit servers are able to generate a working key. If the cryto behind this is done right, this is unbreakable.

We also want to remind you that we will move completely to Codeberg this summer. The wiki can already only be updated there, while all wiki changes will be mirrored to github. Please create a Codeberg account, if you want to modify the wiki or if you want your issues/PRs and comments to be properly assigned to you again on Codeberg.

The reason for the move in one sentence: A free project deserves a free home!

For user-facing changes since the last blog post, check the following list.

Version 0.35.0¶

Mi Band 4: Initial support (WARNING: INITIAL SETUP NEEDS MI FIT WITH ACCOUNT AND ROOT, NOT A RECOMMENDED DEVICE FOR GADGETBRIDGE)

Version 0.34.1¶

Mi Band 1: Fix crash when entering per-device settings
Mi Band 3: Allow setting date format in per-device settings
ZeTime: Fix timestamps
Fix a crash when flashing an non-whitelisted firmware while using Gadgetbridge in Spanish

Gadgetbridge 0.34.0: Per-device settings, finally

Andreas Shimokawa — Wed, 05 Jun 2019 00:00:00 +0000

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).

After the refactoring, the device specific sub menus for Mi Band 2, Mi Band 3, Amazfit Bip and Amazfit Cor vanished completely, instead there is a new settings (gear) icon on the device card in the main activity to enter the device specific settings. All changes done there will affect ONLY the single device where the settings are altered. The per-device settings will only show settings which are really supported by the device type. That means, you no longer have to wonder why "turn wrist to change display" does nothing on your Mi Band 3 - you wont even see that setting unless you have a Mi Band 2, and are configuring that.

In addition some of the settings in "Mi Band / Amazfit settings" were also moved to the per-device settings, but this step is not complete yet. I plan to finish that during the 0.34.x cycle.

The reason for the move in one sentence: A free project deserves a free home!

For user-facing changes since the last blog post, check the following list.

Version 0.34.0¶

Mi Band 1/2/3/Bip/Cor: Migrate many settings to per-device settings (new settings icon in device card in main activity)
Mi Band 3: Fix setting menu items with 2.4 firmware and add support for the new timer menu
Amazfit Bip/Cor, Casio: Add support for muting incoming calls
ZeTime: Remove endless recursion in ZeTime settings
Recognize FairEmail notifications as generic email notifications

Version 0.33.1¶

Mi Band 3: Recognize "Xiaomi Band 3"
Amazfit Bip: Add German, Italian, French and Turkish to language settings

Gadgetbridge 0.33.0: Amazfit Cor 2 and a security fix

Andreas Shimokawa — Thu, 09 May 2019 00:00:00 +0000

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.

We also have new initial experimental Amazfit Cor 2 and BFH-16 support, the latter contributed by Johannes Schmitt!

The rest of changes are mainly bugfixes and minor improvements.

This release took a really long time, since core members are still busy with other projects, work and family. We cannot promise that things get better. So if your PR did not merged, your Issue ignored, don't take it personally.

The reason for the move in one sentence: A free project deserves a free home!

For user-facing changes since the last blog post, check the following list.

Version 0.33.0¶

BFH-16: Initial support
Mi Band 2/3/Bip/Cor: Generate random per-device security keys when pairing, allow manual override to still support multiple android devices connecting to the same device
Mi Band 3: Add Indonesian, Thai, Arabic, Vietnamese, Portuguese, Dutch, Turkish and Ukrainian to language settings
Mi Band 3: Support flashing latest Japanese-Korean font
Amazfit Cor 2: Initial experimental support (untested)
Pebble: Add pebblekit extension for reopening last app
Casio: Bugfixes and improvements
Lookup contacts also in work profile
Fix searching in application name when blacklisting
Remove misleading title from database management activity when no legacy database is available

Version 0.32.4¶

Make voip call support optional (disabled by default)
Amazfit Bip: GPX export corrections
ZeTime: Fix setting alarms
ZeTime: Fix wrong activity timestamps
ZeTime: Set HR alarm limits when changed, not only on connect
ZeTime: Sync preferences from the watch to Gadgetbridge settings

Version 0.32.3¶

Fix a crash in charts due to a broken German translation
Fix a crash when transliterating emoji
Amazfit Bip/Cor: Support disconnect notification (must be configured in Bip settings for Cor also for now)

Version 0.32.2¶

Fix setting alarms under some circumstances
Support calls notifications for some VoIP apps
Mi Band 3: Enable fetching sports activities (currently only useful for flushing activities)
Casio: Improve stability
Casio: Add explicit support for GB-6900B, GB-X6900B and GB-5600B

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

Andreas Shimokawa — Sat, 19 Jan 2019 00:00:00 +0000

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.

Yep, github is now a mirror for us. We still use the Issue tracker on github and we are still accepting PRs on github - but prefer new PRs on codeberg.org.

Also the wiki is now a mirror on github, if you want to help working on documenting Gadgetbridge, please create an account on Codeberg and meet us here.

Version 0.32.1¶

Fix db deadlock on alarm migration

Version 0.32.0¶

Initial support for Casio GB-6900B
Increase number of alarms and store them per-device
Support factory reset in debug activity (Mi Band 1/2/3, Bip, Cor)
Filter out unicode control sequences (fixes problems with Telegram and probably others)
Fix endless loop resulting in OOM when RTL support is enabled
Recognize p≡p as an email app
No longer display Android paired devices in that were not a paired with Gadgetbridge
Amazfit Bip: Allow flashing latest GPS firmware
Pebble: Native support for M7S watch face
No1 F1: Support for a Chinese clone

Gadgetbridge 0.31.0: No more duplicate notifications

Andreas Shimokawa — Sun, 04 Nov 2018 00:00:00 +0000

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.

Since we did not publish a blog post for the 0.30.0 release, we have attached the changelog of both 0.30.0 and 0.31.0 below.

On a personal note: We have a broken Pebble 2 side buttons that we would like to use on a daily basis again. If anyone with a 3D printer which can print flexible filamet, and is willing to donate new printed side covers (available on thingiverse.com), please contact us (all at freeyourgadget dot org). ;)

Version 0.31.0¶

Pebble: Send all wearable notification actions (not only reply)
Pebble: Always allow reply action even if untested features are turned off
Pebble: Temporarily disable broken autoremove notification feature
Amazfit Bip: Allow flashing latest gps firmware (Mili_dth.gps)
Mi Band 3/Amazfit Bip/Amazfit Cor: Send Fahrenheit if units are set to imperial
Roidmi 3: Fix and enable support
Mi Band 3/Amazfit Bip: fix find phone crash
Prevent re-sending old notifications to the wearable
Enhancement and Fixes for Bengali Transliteration
Disable excessive logging in RTL support

Version 0.30.0¶

Amazfit Bip + Mi Band 3: Support for right to left display (configurable) (#976)
Add Arabic, Bengali Farsi, Persian, Scandinavian transliteration
Add support for some Roidmi FM receivers
Mi Band 3: Allow enabling the "Workout" menu item
Mi Band 3: Support for night mode configuration
Huami devices: fix seldom activity/sports synchronization problem (#1264)
Preferences: Make minimum heart rate configurable (lower values will be disregarded)
Preferences: Configure minimum time between notifications
Preferences: Group language settings
Attempt to fix BLE connection issues on Samsung S devices
Week sleep and steps charts: display balance (actual value vs. desired value)
Live Activity: show current/maximum heart rate, display minute steps and total steps and more improvements
Live Activity: fix discrepancy between number of steps in Gadgetbridge and wearable device
Fix missing caller ID for incoming calls on Android 9
Support for easy sharing of log files via the Debug screen
Misc small bugfixes

Gadgetbridge 0.29.0: Support for ID115 and Lenovo Watch 9!

Andreas Shimokawa — Sun, 12 Aug 2018 00:00:00 +0000

Gadgetbridge 0.29.0: Support for ID115 and Lenovo Watch 9!¶

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

The highlight of this release is initial support for the ID115 (Contributed by Vadim Kaushan) and Lenovo Watch 9 (contributed by "maxirnililan"). Many thanks to both of you!

We also fixed a lot of bugs and added new features for Mi Band 3, Amazfit Bip, Amazfit Cor and NO1 F11. Feature-wise, most notable is initial music control support for the Amazfit Cor. We expect that this will also become available on the Amazfit Bip later, but currently it seems to be unsupported by the current Bip firmware.

There are also some visual changes, like the new Mi Band 2/3 icon and a new splash screen.

Overall, outside (non core team) contributions were really great during this 0.29.0 cycle. Keep it coming ;)

Changelog for the 0.29.0 release¶

New Device: Initial support for ID115
New Device: Initial support for Lenovo Watch9
Show splash screen during startup
Vertically align device icon in main activity
Try to support the google clock application (untested)
Amazfit Cor: Allow to configure displayed menu items
Amazfit Cor: Support basic music control
Amazfit Cor: Fix flashing font files
Amazfit Bip: improved GPX export
Amazfit Bip: Fix exported GPX file names for *FAT storage
Amazfit Bip: Fix current weather not being displayed with later firmwares
Amazfit Bip/Cor: Try to fix device being sometimes stuck in connecting state
Mi Band 2: Put some device specific settings into its own settings category
Mi Band 3: Support disabling of on-device menu items
Mi Band 3: Support locking the Mi Band screen (swipe up to unlock)
Mi Band 2/3: New icon
NO1 F1: Set time during initialization

Gadgetbridge 0.28.0: ZeTime and Mi Band 3 support!

Andreas Shimokawa — Thu, 19 Jul 2018 00:00:00 +0000

Gadgetbridge 0.28.0: ZeTime and Mi Band 3 support!¶

Gadgetbridge 0.28.0 has just been tagged and will show up on F-Droid soon.

The highlight of this release is initial experimental support for the ZeTime which was contributed by Sebastian Kranz. Thanks Sebastian!

We also managed to make the Mi Band 3 working with Gadgetbridge starting with 0.28.0 and most features seem to work well already.

Further notable enhancements have been done to the firmware detection code for Bip and Cor to fix problems with the new version scheme.

There might be one point release for the 0.28.x series, but we expect to release 0.29.0 soon, since there is more new device support in the pipeline :)

Changelog for the 0.28.0 release¶

Initial support for ZeTime
Amazfit Bip/Cor: Rework firmware detection to cope with new version scheme
Amazfit Bip: Support setting language to Russian
Amazfit Cor: Support language switching on newer firmwares
Mi Band 3: support setting language (english and spanish tested)
Mi Band 3: Fix pairing
Mi Band 3: Send AQI to enable display of current temperature

2000 stars and counting

Daniele Gobbetti — Wed, 09 May 2018 00:00:00 +0000

2000 stars and counting¶

Initiated in 2015 with the aim of providing pebble users freedom from the vendor servers (it's ironic that at the time of this writings the pebble servers will be shutdown in a few weeks, but I digress..), Gadgetbridge as of today:

issued 129 releases (on f-droid.org)
supports more than 10 wearable devices by several vendors
is translated to more than 25 languages (on weblate.org)
successfully appealed one DMCA take-down notice
received more than 3300 commits to master branch and counts more than 330 forks (on github.com)
included (merged) more than 150 pull requests (on github.com)
has more than 100 contributors (committers, including translators)
receives donations by over 30 patrons (on liberapay.com)
last but not least: it reached 2000 stars (on github.com)

In the tech world lately everything seems to be about data and metrics, you might notice that one number is missing in the list above, namely the users' count. We don't have that number and as a free-software, community-driven project we are in the happy situation that we don't have to care for such an indicator either!

As you might have guessed from the title, this post is about celebrating the 2000th star on github.com, which might open interesting new opportunities for the project.

Thanks to an offer announced two years ago and still available - to the best of our knowledge - we will hopefully be able to get an instance of discourse to grow our community even stronger, and to ease the load of the github issue tracker. We are looking forward to having this additional communication channel toward our users and supporters, as well as a platform which is more accessible to non-developers than github.com

Meanwhile, if you want to start contributing but are unsure how to proceed, you can choose one of the issues marked as "help wanted", help us with the translations or become a patron. If your favorite device is not supported, why don't you add support for it?

Closing thoughts and thanks¶

Special thanks go to the projects f-droid.org, liberapay.com and weblate.org. We are proud to encourage the usage of free-libre software tools and platforms wherever possible, and bringing users in contact with projects they possibly weren't aware of.

Gadgetbridge 0.26.0: free your workouts on the amazfit bip

Andreas Shimokawa — Sun, 15 Apr 2018 00:00:00 +0000

Gadgetbridge 0.26.0: free your workouts on the amazfit bip¶

Gadgetbridge 0.26.0 has just been tagged and will show up on F-Droid soon.

The highlight of this release is the added feature that allows to export the activities (workouts) recorded with the Amazfit Bip.

This feature is not perfect yet, but already works quite well. The most notable limitation is that only one track can be synced at a time.

In Gadgetbridge, push the running man icon in the device card and then press the sync floating action button or swipe down. Please note that only one workout will be fetched, you have to sync again to get the next activity and so on, automatic fetching will be added in a later release. Please join our efforts if you can contribute.

All workout types are supported and for outside activities (like Walking, Running, Cycling, ...) that contain GPS data, a GPX file can be exported to your phone or shared with any android application. The GPX file also contains Heart Rate data, if it was recorded.

Please be aware that not every detail of the workout is currently being stored in Gadgetbridge, so if you care about additional information like the calories count, pace, etc. you should keep the activities on the watch.

Further enhancements are related to the weather, the wind speed and direction are now fetched from all the supported sources (Lineage OS weather provider, Omnirom and the Weather notification app) and are forwarded to connected gadgets (where supported).

Changelog for the 0.26.0 release¶

Amazfit Bip: Initial support for GPS tracks
Pebble: Wind speed/direction support and bugfixes for weather when using background javascript

Gadgetbridge 0.23.0 released with support for LineageOS weather provider

Andreas Shimokawa — Sun, 17 Dec 2017 00:00:00 +0000

Gadgetbridge 0.23.0 released with support for LineageOS weather provider¶

Gadgetbridge 0.23.0 has just been tagged and will show up on F-Droid soon.

The highlight of this release is the addition of CyanogenMod/LineageOS weather provider support. This means that you no longer need the "Weather Notification" app to be able to see weather information on your wearable if you a LineageOS or CyanogenMod user.

Simply install a weather provider from https://download.lineageos.org/extras and set the weather location withing Gadgetbridge's settings.

Changelog for the 0.23.0 release¶

Initial support for LineageOS/CyanogenMod weather provider
Amazfit Bip/Cor: Support for current weather temperature
Amazfit Bip/Cor: Display firmware version and type also for non-whitelisted firmware files

Gadgetbridge 0.22.0 finally merges Pebble background JS, supports new devices

Andreas Shimokawa — Wed, 25 Oct 2017 00:00:00 +0000

Gadgetbridge 0.22.0 finally merges Pebble background JS, supports new devices¶

Gadgetbridge 0.22.0 has just been tagged and will show up on F-Droid soon.

This is an exciting milestone, since finally our longstanding background javascript branch has been merged! When enabled, this allows pebble apps and watchfaces to execute the javascript code bundled with .pbw files to be executed on the phone. In practice this means that a lot of watchfaces will be able to display weather and phone battery status without Gadgetbridge needing special support for specific watchfaces.

In the future it might mean that watchfaces will also be able to fetch information from the internet by using an to-be-developed addon app for Gadgetbridge.

0.22.0 also adds experimental and mostly untested support for the following devices:

Amazfit Cor (firmware update completely untested)
Mi Band HRX (firmware update not supported yet)

In addition, the release contains bugfixes and improvements for our already supported devices,

Changelog for the 0.22.0 release¶

Pebble: Experimental support for background javascript, allows weather and other features for watchapps without special Gadgetbridge support
Add experimental support for Amazfit Cor and Mi Band HRX (no firmware update on the latter)
Mi Band 2: Support more icons and textual notifications for more apps
Add some quick action buttons to Gadgetbridge's notification
Add transliteration support for Ukrainian cyrillic characters
Fix annoying toast in Mi Band settings

Gadgetbridge 0.21.3/0.21.4 with exciting news for Mi2/Bip users

Andreas Shimokawa — Sun, 01 Oct 2017 00:00:00 +0000

Gadgetbridge 0.21.3/0.21.4 with exciting news for Mi2/Bip users¶

Gadgetbridge 0.21.3 has been released on F-Droid (0.21.4 is also ready and will appear on F-Droid after the build and indexing process has finished)

One day after we found out that the Amazfit Bip firmware 0.0.9.14 (included in Mifit 3.1.0) had an English translation inside, we implemented support for switching the language and tagged 0.21.3 right away, making that the only (but important) change in that release.

Then only about 24h later we finally found a solution for bringing activity data parsing for newer Mi Band 2/Amazfit Bip firmwares on par with older firmwares. Thanks to everyone commenting in the issue tracker and describing their observations regaining their activity data! While fixing the code, we found and fixed another ancient issue that resulted in wrong activity data under some circumstances and affected all firmwares,

TL;DR: You can finally update to the latest Mi Band 2 and Amazfit Bip firmwares without loosing sleep detection in Gadgetbridge! ;)

Oh and before I forget, you can now help Gadgetbridge and win a T-Shirt! For details head over to:

https://hacktoberfest.digitalocean.com/

Changelogs¶

Version 0.21.4¶

Mi2/Bip: Fix sleep detection for newer firmwares
Mi2/Bip: Fix ancient bug resulting in wrong activity data at the beginning in diagrams and aggregate data
No.1 F1: Support setting time format and distance units (metric/imperial)
Pebble: Support setting distance units to miles for Health (need to reactivate Health in App Manager after toggling)
HPlus: Make changing distance unit system effective immediately on toggling

Version 0.21.3¶

Amazfit Bip: Auto-switch language on connect (English, Simplified Chinese, Traditional Chinese), requires FW 0.0.9.14+

Gadgetbridge 0.21.0 adds support for two new devices

Andreas Shimokawa — Tue, 19 Sep 2017 00:00:00 +0000

Gadgetbridge 0.21.0 adds support for two new devices¶

Gadgetbridge 0.21.0 (and 0.21.1) have been released a a few days ago. So this blog post is a bit late.

Less then one month after our last version bump, we bumped again since we had the opportunity to add TWO new devices though pull request from new contributors:

NO.1 F1 support by Vitaly Svyastyn
Teclast H30 support by Sami Alaoui

In addition, the release contains a lot of bugfixes and improvements for our already supported devices, like the Pebble and the Amazfit Bip.

Changelogs for the 0.21.x releases¶

Version 0.21.1¶

Initial support for EXRIZU K8 (HPLus variant)
Amazfit Bip: fix long messages not being displayed at all
Mi Band 2: Support multiple button actions
NO.1 F1: Fetch sleep data
NO.1 F1: Heart rate support
Pebble: Support controlling the current active media playback application
Fix suspended activities coming to front when rotating the screen

Version 0.21.0¶

Initial NO.1 F1 support
Initial Teclast H30 support
Amazfit Bip: Display GPS firmware version
Amazfit Bip: Fix E-Mail notifications
Amazfit Bip: Fix call notification with unknown caller
Amazfit Bip: Fix crash when weather is updated and device reconnecting
Mi2/Bip: Fix crash when synchronizing calendar to alarms
Pebble: Fix crash when takeing screenshots on Android 8.0 (Oreo)
Pebble: Support some google app icons
Pebble: try to support spotify
Mi Band 2: Support configurable button actions
Fix language being reset to system default

Beware of unknown APKs online

Daniele Gobbetti — Sun, 03 Sep 2017 00:00:00 +0000

Beware of unknown APKs online¶

Il testo in italiano si trova in calce. Italian text follows.

It has been brought to our attention that several websites provide APKs of Gadgetbridge instead of linking to the official release on F-Droid¶

This is happening a lot lately thanks to Gadgetbridge being able to flash custom firmwares to the Amazfit Bip device.

We strongly advise against installing APKs that are not verifiably built from our sources and instead do the following:¶

Install f-droid and use it to install Gadgetbridge. This ensures that your device will get all new releases of Gadgetbridge
alternatively install the APK downloaded from the f-droid website.
If you are a developer and would like to build from source, you can clone our repository

Unverified apks are probably out-of-date, introduce bugs and might contain undesired anti-features such as malware, advertising, etc.

Know your rights¶

Gadgetbridge is released under the AGPLv3 License, this allows the distribution also in binary form (apk) but requires the corresponding sources to be distributed as well. If you notice a website that is hosting the apk, you have the right to receive the sources of that apk, and we invite you to request them from the website owners.

Support us on Liberapay:

Italian text¶

Ci è stato fatto notare che diversi siti web mettono a disposizione delle versioni di Gadgetbrige direttamente, anzichè linkare la release ufficiale su F-Droid¶

Questo succede molto spesso ultimamente dato che Gadgetbridge è in grado di installare firmware modificati sul dispositivo Amazfit Bip.

Noi sconsigliamo assolutamente l'installazione di APK la cui corrispondenza al codice sorgente non possa essere verificata, e procedere come segue:¶

Installare f-droid e usarlo per installare Gadgetbridge. In questo modo il dispositivo riceverà anche tutti gli aggiornamenti di Gadgetbridge
in alternativa installare l'apk scaricato direttamente dal sito di F-Droid.
Per gli sviluppatori che possono compilare da sorgenti, è possibile clonare il nostro repository

APK non verificati sono probabilmente obsoleti, possono introdurre bug così come contenere caratteristiche indesiderate quali ad esempio malware, pubblicità etc.

Conosci i tuoi diritti¶

La licenza AGPLv3 di Gadgetbridge consente la distribuzione sotto forma di binari (apk) solo se accompagnati dalla possibilità di accedere ai sorgenti corrispondenti. Se noti un sito che mette a disposizioneun apk di Gadgetbridge, hai il diritto di richiedere i sorgenti corrispondenti all'apk, e ti invitiamo a richiederlo ai responsabili del sito web in questione.

Gadgetbridge 0.20.0 adds Amazfit Bip support, project accepting donations now

Andreas Shimokawa — Tue, 22 Aug 2017 00:00:00 +0000

Gadgetbridge 0.20.0 adds Amazfit Bip support, project accepting donations now¶

Gadgetbridge 0.20.0 (and 0.20.1) have been tagged and will be on f-droid soon.

We are very excited about the release, since we now officially support the Amazfit Bip. Except for workout and importing GPS data, nearly all features are already working.

We also like to mention that we are accepting donations via Liberapay now. If you like Gadgetbridge, please consider donating in order to sustain Gadgetbridge's development.

Click on the Liberapay button below for more details!

Changelogs for the 0.20.x releases¶

Version 0.20.1¶

Amazfit Bip: Support icons and text body for notifications
Mi Band: Fix setting smart alarms

Version 0.20.0¶

Initial Amazfit Bip support (WIP)
Various theming fixes
Add workaround for blacklist not properly persisting
Handle resetting language to default properly
Pebble: Pass booleans from Javascript Appmessage correctly
Pebble: Make local configuration pages work on most recent webview implementation
Pebble: Allow to blacklist calendars
Add Greek and German transliteration support
Various visual improvements to charts

Please join us if like Gadgetbridge, help us improve it, add support for new devices, translate it or help with documentation.

Our DMCA takedown: a post-Mortem

Andreas Shimokawa — Wed, 12 Jul 2017 00:00:00 +0000

Our DMCA takedown: a post-Mortem¶

This is a post-Mortem of the DMCA takedown notice that hit Gadgetbridge in June 2017, written by two core developers of the project.

First things first: We would like to thank all the people who sent us their support via mail, social networks, chat and other means.

As everyone does in this case, let's start with the:

tl;dr: We were surprised to have been hit by a DMCA takedown notice on Github. We decided to file a counter notice because we stand firm in our belief that no content in our repository ever violated US or EU laws including but not limited to the DMCA. We are happy the project is back online and available for the community.

Reaching the conclusion of the story was an interesting journey that we would like to share with our supporters. We also learned a lot in the process, and we would like to share our experience in the spirit of open knowledge that always permeated Gadgetbridge.

About us¶

We are three persons spread across Europe: each with his own job, family and hobbies. We share a passion for solving problems and strive to keep our "digital footsteps" as private as possible: hence we never quite liked the fact of being forced to rely on services outside of our control to manage our personal devices. That's why Gadgetbridge was started in January 2015 and that's why it attracted two more core developers and many contributors to the source code, the graphical assets and the documentation (wiki).

We were not expecting this¶

The whole Gadgetbridge project - code, communication and documentation - has always been in the open and publicly accessible: hence we were assuming that also criticism would have been disclosed, discussed and solved in the open. Instead the copyright holder of a third party app (that supports a subset of the devices supported by Gadgetbridge) felt that our work was in violation of his IP and filed a DMCA takedown notice to Github. For reasons inexplicable to us, despite the takedown notice containing only references to content posted to our issue tracker, it included the main repository URL among the problematic URLs. This fact triggers a peculiar behavior in the way Github addresses the notice, namely the immediate shutdown of the whole repository (code, issues, wiki, etc.) for the public and for the owners. In other words the Github DMCA takedown process - if the notice targets the whole repository - leaves no place to confrontation: it's a sword of Damocles stealthily hanging over your head.

The Gadgetbridge repository was closed in the early morning of Saturday June 3rd.

Now what?!?¶

After the takedown notice hits, you can't do anything but file an official counter notice to Github. Some of us core developers and some of our users tried to contact Github support to signal that the takedown of the whole repository was possibly an error, receiving only standard replies back: we believe that once the takedown process is initiated, the "normal" support isn't able to do anything; for sure it didn't in our case.

If you want your repository back you have to go through the filing of a counter notice. Before taking this step Github advises to get in touch with an lawyer, and since one of the prerequisites is consenting to the jurisdiction of a US Federal Court we took that advice very seriously: we are (fortunately) not familiar with courts and laws, on either side of the pond.

Our reactions, others' reactions¶

We had - and still have - a clear conscience and while we were looking for legal advice we were also reaching out publicly - on twitter and reddit - to explain why we thought that takedown was exaggerate and also highlighted that who initiates a takedown notice can also send a retraction to Github. Meanwhile already several people reached out to us via mail offering support and financial help for handling this situation. In the next days our case was mentioned as "Another Good Reason not to use Github" and also a big German news site wrote about it.

We were fortunate enough to get the help of a very competent lawyer in a timely manner (first contact was established during the weekend) and we were reassured by him that our feeling of clear conscience was indeed backed by hard facts, and we could proceed with the counter notice. So we decided to proceed.

Filing the counter notice¶

We read carefully the guide provided by Github and prepared the contents of the counter notice together with the lawyer, the result was submitted by our lawyer at first using the web form provided by Github. Apart for a confirmation message, we didn't get any further acknowledgment.

A few days later - not having heard anything back - our lawyer submitted the counter notice again, via mail. This time an email reply came back, stating that personal information of at least one of the repository owners must be included in the counter notice. We didn't do it in the first place given the following passage of the guide:

If you are concerned about your privacy, you may have a lawyer or other legal representative file the counter notice on your behalf.

We agreed upon adding the contact information of one of us in order to speed up the process, despite the text cited above. The amended version was promptly submitted. One week later, not having heard anything back, we reached out to Github to understand if things were somehow progressing or if there were other issues in processing out counter notice. We had to wait a couple of days before getting an acknowledgment.

Fast forward to June 27 when the counternotice was published in the DMCA repository on Github. At the same time we received a reply from Github to our mails, where they basically announced to us that the counter notice was published.

The repository is available again¶

After 10 business days the repository was suddenly made available again without further notices from Github. As we agreed to the removal of the issues mentioned in the takedown notice despite there is no copyright infringement involved we closed the issue tracker as soon as we got access, this way we can check if Github cleaned the offending URLs or if we should do it. The issue tracker will be re-opened again as soon as this check has been completed.

We were also surprised because almost immediately upon its availability some Pull Requests were submitted to the repository. We believe this is quite telling on how strong and motivated the community around the project is.

The future¶

In the few weeks when our repository was unavailable we thought about future scenarios: on the one hand we could have moved our code anytime anywhere (the code was actually safe on each of the developers' machines) on the other hand we realized how much value the metadata of the project is worth. In two and a half years a lot of knowledge was put in our wiki by various contributors, same for the discussions that took place in the issues / pull requests. Github is a valuable resource for free software projects, because it allows to reach a huge community and provides useful tools. We underestimated the "lock-in" effect though.

We are currently establishing an online presence that goes beyond Github, without requiring too much efforts to be maintained. So far we have set up:

a static homepage available under https://gadgetbridge.org (which is an automatically updated copy of the project's README.md file)
the blog you are currently reading: https://blog.freeyourgadget.org (where content is manually written, hence could be updated less often)
automatic procedures to back up the entire content of our Github repository (this includes the wiki, issues and pull requests) thanks to the great github-backup tool

We also contacted some git hosting providers outside of the U.S.: we neglected the distributed nature of git by relying on a single hosting provider and we intend to act differently in the future. More details will follow.

We also realized how vulnerable a small free software project maintained by few individuals in their free time could be: we contacted a variety of free software organizations - from a very local level to Europe-wide - and have found great support in them. There are so-called umbrella organizations which take care also of the legal side of free software development, including enforcing the source code license and representing a project in courts. Also to this end more details will follow.

You can reach the core developers via mail at all [at) freeyourgadget·org if you have questions, suggestions or criticism. (yes, the address is formatted weirdly but a human should be able to parse it)

Lessons learned¶

Despite the wording, when a Github repository is closed due to a DMCA takedown notice, the access is not only disabled for the public, but also for the owners.
The counter notice is processed by Github internally without giving any information about its progress: you submit the counternotice and wait - in our case 12 days - until it's public.
Github does not give visibility to a submitted counter notice on the repository, only the original takedown notice will be linked from the repository until it opens again.
At the end of the 10-business-days window, it's best to monitor the repository constantly, as it will be opened again without any notice. This is true especially if some content must be removed.
A local copy of the whole repository is invaluable, even though every developer has the full history of the code base there is so much more to keep a backup of. There are free software tools that make this easy and there's no reason to not be using those.

Timeline of the events and reactions¶

June 3rd: Takedown notice published, access to repository disabled
June 6th: First version of the counter notice drafted together with the lawyer
June 7th: A blog post by Adam Hide is published
June 8th: Web submission of the counter notice
June 12th: Email submission of the same counter notice due to lack of feedback from Github
June 13th: An article in German about our case is published
June 14th: Email reply from Github: the counter notice must contain the details of one of the owners
June 15th: Email submission of the amended counter notice
June 20th: A podcast in Spanish about our case is published
June 27th: Counter notice published
July 11th: Gadgetbridge repository opens again
July 12th: Post-Mortem published

Gadgetbridge repository reopened by Github

Andreas Shimokawa — Tue, 11 Jul 2017 00:00:00 +0000

Gadgetbridge repository reopened by Github¶

Today, Github finally reopened our repository including wiki, issues and all other content, since the 14 days waiting period, which started after they published our Counter Notice is over now.

We want to thank all the great people who supported us during the last five weeks!

The issue tracker is disabled on purpose for now, but will re-open it during the next few days!

Gadgetbridge Github DMCA Counter Notice

Andreas Shimokawa — Fri, 30 Jun 2017 00:00:00 +0000

Gadgetbridge Github DMCA Counter Notice¶

Just a quick update on our DMCA Case:

In response to the recent DMCA Takedown Notice, we filed a Counter Notice

Gadgetbridge Github DMCA Takedown

Andreas Shimokawa — Sun, 25 Jun 2017 00:00:00 +0000

Gadgetbridge Github DMCA Takedown¶

You may have noticed that our github repository, including the issue tracker and wiki at github is currently not accessible.

This is because the developer of another app filed a DMCA request and github shut down the entire repository.

We're working on a solution, but it is hard to get a response from github, so please be patient.

Project Gadgetbridge

Andreas Shimokawa — Sun, 25 Jun 2017 00:00:00 +0000

Project Gadgetbridge¶

Gadgetbridge is an Open Source Android app for interacting with smart watches, smart wristbands, and other gadgets.

Interacting means

alerting about notifications by message display/vibration/LEDs for chat messages, mail, calendar events, weather, location, ...)
handling responses
tracking fitness data (activity, steps, distance, heart rate, calories, ...)
tracking and visualizing your sleep
configuring alarms
control the music player
installing apps on the gadgets
updating the firmware
live activity display
and more

Obviously the available features depend on feature set of the actual devices. At the moment the following devices are supported

all Pebble smart watches
all Mi Bands
HPlus devices (e.g. ZeBand)

Support for further devices is in the works.

Privacy of Your Data¶

The data tracked with Gadgetbridge is stored in Gadgetbridge only. It is not sent or synchronized anywhere, unless you manually export it.

Download¶

Download Gadgetbridge from F-Droid and install it on your Android phone or tablet.

The source code, issue database and wiki documentation is available at https://github.com/Freeyourgadget/Gadgetbridge

Development and Community¶

Gadgetbridge is a collaborated effort. Please join us and

translate Gadgetbridge to further languages
spread the word and grow the community
help other users
add new features
improve the UI
add support for new devices
fix issues

Why¶

See here for some reasons why we create Gadgetbridge and why you should consider joining us.

Legal¶

Gadgetbridge is licensed under the GNU Affero GPL (AGPL) 3.0.

Why Gadgetbridge

Andreas Shimokawa — Sun, 25 Jun 2017 00:00:00 +0000

Why Gadgetbridge¶

Gadgetbridge is an Open Source Android app for interacting with smart watches, smart wristbands, and other gadgets.

This post explains why we create this app and why you should consider using it.

Privacy¶

Gadgetbridge does not upload your personal data anywhere.

Other apps often require you to create an account at one or more companies and provide personal data like your name, email address, age, size, weight, and more. Smart gadgets then track your daily activity, e.g.

when you wake up
when you take a shower
when/how you go to work/school/...
when/if you do sports
when you go to bed
what you're doing in bed

Sometimes they even track your location, so they even record where exactly you go partying at night before waking up late next day.

All that data is then uploaded to someone you don't know. Every day. And they can do pretty much everything with your data.

Some people may be fine with this. We also like these gadgets, but we think that much of their functionality can be used without requiring you to upload all your data.

Gadgetbridge is FLOSS¶

We love Free/Libre/Open Source Software. Unlike most other apps for interacting with today's gadgets, you can have a look at how Gadgetbridge communicates with the gadgets. By being able to look at the code

you can be certain that your data will stay your data
you can learn how controlling such gadgets works
you can verify that there is no hidden treasure (tojan) in the app

You can also make changes to the source code to

add new features
support new gadgets
change some thing that annoys you

Fun¶

And last, we create Gadgetbridge because it is fun!

So, join us at https://github.com/Freeyourgadget/Gadgetbridge :-)

Gadgetbridge 0.12.2 finally released!

Andreas Shimokawa — Sun, 11 Sep 2016 00:00:00 +0000

Gadgetbridge 0.12.2 finally released!¶

After two months of hard work we are pleased to announce the availability of Gadgetbridge 0.12.2.

For those who don't know, Gadgetbridge is an Open Source Android app for interacting with smart watches (currently Pebble), fitness trackers (currently Mi Band) which does not send your data to any third parties.

Visible Changes¶

The list of visible changes in the new version is a quick read:

Support for Pebble Health on Firmware 4.0
Fixed displaying of deep sleep vs. light sleep for Mi Bands
Moved some data import/export operations to a dedicated screen
Devices are now displayed even if Bluetooth is turned off

So why did it take us that long to release that?¶

Answer: because of many invisible changes under the hood.

The most important change is the much richer database schema and much nicer access to its data, with the help of greenDAO.

But it already worked fine before, what are the benefits?¶

I'm glad you asked, here they are:

Your activity data (steps, sleep tracking, etc.) is now stored per device, per user and includes additional data. It's all nicely separated, so you will be able to tell exactly with which device, even with which firmware version you ran that marathon back then in 2018. Oh and all your configured user data, e.g. your weight will be associated as well.
Per user?? Yes. Gadgetbridge associates your activity data and everything else to a user in your database. At the moment there is just one, but there could be more in a family where not everybody has a smart phone, maybe even some you didn't think of at all.
Now that everything's cleanly separated, we will (in the coming versions) provide ways to better visualize your data.
You will also be able to categorize your activity manually. So far, Gadgetbridge mostly differentiates between light sleep, deep sleep and no sleep. But it is already prepared to accept your own activity classification, by tags and descriptions. You will be able to retrospectively tell why your heart rate jumped to 180 bpm in October 2016 when you tag it with "climbed the Monte Baldo by bike".
The tagging might also enable creative people to implement activity recognition algorithms based on the specific patterns captured by the activity trackers.
Speaking of heart rate -- we will add more measurement options and especially record the measurements in the database, soon.
Oh, and now that we have a rather stable database interface, we hope to have a self hostable synchronization server at some point. Please contact us if you want to work on this!
And finally, we will be able to easily integrate data from new devices (e.g. Pebble 2 and Mi Band 2).

Roundup¶

So to sum up, this release is mostly unspectacular for users, except for the few points at the top of this post.

But it is spectacular for our ability to improve the application and add new features.

Please join us if like Gadgetbridge, help us improve it, add support for new devices, translate it or help with documentation.

We're also looking for a discussion forum, preferably one that supports Github authentication. Discourse would be an option, but so far we have not managed to get a forum on their servers.

Any help is much appreciated.