Version 2.2.0 Released

February 19, 2023

Herald Version 2.2.0 Released

It’s been a busy few months for the Herald team. So busy in fact we didn’t announce the previous version 2.1.0! So in this post we’ll walk you through all the recent improvements in Herald.

We’ve moved to a small release schedule whereby each time a feature, or feature and a few associated bugs, are fixed we test and push out a release immediately. This should make upcoming releases every 1-3 months rather than 12-15 months. This also allows us to get ahead of mobile operating system releases and perform compatibility testing on the latest iOS and Android releases. Expect to see more frequent releases and updates from the team in future!

Since v2.2.0 (Released 19 February 2023):-

  • Tested on the latest iOS and Android OS versions for reliability and compatability
  • Improvements in detection (including one way detection) on both iOS and Android, with connect back on iOS working well
  • iOS now connects much less often to Android devices, reducing workload on Android and improving battery use on both platforms
  • BREAKING CHANGE: A more explicit way for app developers to specify a custom Bluetooth Service UUID either alongside or instead of Herald’s default mode (See BLESensorConfiguration for details)
  • Added production of graphs about all other phones seeing a target phone (the ‘observation’ charts when you run the script) in the Analysis Scripts which ‘zoom in’ to a small time window of interest to help to pinpoint specific phone issues
  • Added an anomaly detection Java app to the Analysis scripts repository which allows the creation of issue scenarios and root cause analysis over many phones across many days, to aid anomaly detection, prioritisation, and resolution

Since v2.1.0 (Released 14 January 2023):-

  • Healthcheck routines on both platforms to correct any local bugs or reliability issues
  • BREACKING CHANGE: Herald now using the official, registered Linux Foundation Bluetooth Service UUID (which we share with the Zephyr Project). We’re keeping detection of the previous ID in place, but not advertising it by default since v2.1.0.
  • Various security primitives and options, and the use of a new hashing function

For a full list of changes please see the release notes:-

The releases are available here:-

You can also build the Herald test app by cloning our repositories and building the app locally.

Get Involved

The Herald Project thrives on community participation. If you want to get involved, or have a great idea for improving healthcare, please get in touch. Visit the Herald Community Page.

Related Content
Version 2.2.0 Released
Introducing the Herald Bluetooth MESH API
Bluetooth RSSI proximity self calibration enhancements
Singapore's GovTech donates OpenTrace to Linux Foundation Public Health's Herald Project
Why Digital Contact Tracing is still needed
Why Digital Contact Tracing is still needed
We’re now over a year since the first national lockdowns due to SARS-CoV-2 (COVID-19). In this post we look to the continued need for Digital Contact Tracing (DCT), and where the technology is going next.
Getting Started

To help you get started, see the documentation.