Boost

Boost in AAPS 4.0

Boost is an independently maintained variant of AAPS 4.0.0 that adds the Boost APS plugin. It is not a release of, or supported by, the AAPS project. You build it yourself and you are responsible for how you use it. AGPL-3.0, as AAPS.

This line is Boost 6.3.3: the V6 meal logic and the Boost high temp, with each SMB sized by the Boost tiers as in Boost 6.2.0 for AAPS 3.4.2.6.

6.3.3 changes the default of Boost max IOB to 12 U, which makes Boost use your max IOB (up to 12 U), and stops auto-config copying max IOB into it. A value you set lower is kept. It also lets the committed cap go up to 5.0 U, keeps the sleep detector from starting sleep before your night start when no heart rate reaches the phone, adds a light version of the Boost overview, and logs a night insulin-need check that never notifies. It otherwise doses as 6.3.2.

6.3.2 sets the two SMB minutes settings to 15 (standard) and 20 (UAM) once, the first time Boost runs, and then leaves them to you. 6.3.1 lowered a higher value on every loop cycle, so neither could be raised. A value 6.3.1 lowered stays as it is until you change it. Settings imported from AAPS without Boost have both reset, so they start at 15 and 20 in the same way; settings from a Boost build keep theirs. 6.3.2 also keeps the night mode BG offset correction from 6.3.1, and otherwise doses as 6.3.1.

Dosing changes from Boost 6.2.0

Other changes

Installing over your current build

Android installs over an existing AAPS only when the new APK is signed with the same key. The workflow below uses the signing key already held in your repository’s secrets. Android 12 or later is required.

Before you start, export your settings in AAPS and keep your current APK. The move to 4.0 changes the database and the settings store, and neither can be read by an older build. To go back, you reinstall the older APK after uninstalling and import the export.

The same applies to a standard AAPS 4.0 build. It installs over Boost, because the package and version code are the same, but it cannot open Boost’s database and the app stops at start, so the loop does not run. To move from Boost to standard AAPS, export your settings, uninstall Boost, install AAPS and import the export.

You already build AAPS in the browser

  1. In your existing AndroidAPS fork on GitHub, choose Add file, Create new file, and name it .github/workflows/boost-ci.yml.
  2. Paste in the contents of boost-ci.yml and commit.
  3. Under Actions, run Boost CI and select the release.
  4. Install boost-<release>.apk from the AAPS/<release> folder in your Google Drive, over your current app.

Your fork’s KEYSTORE_SET and GDRIVE_OAUTH2 secrets are used as they are.

You have a fork of Boost-in-AAPS_3.4

This repository was Boost-in-AAPS_3.4. Its Boost 6.2.0 for AAPS 3.4.2.6 is now on the branch dev-3.4.2.6, and the earlier 6.1.2 line that was master is on master-3.4.2.6. master and dev are both this 4.0 line. A fork of it already holds the secrets Boost CI needs, including the separate keystore secrets.

You are new to browser builds

Fork this repository, enable Actions, and create the two secrets with the AAPS browser build instructions. Then run Boost CI. To reuse the key from another repository, run CI Keystore Export there first.

You build in Android Studio

Check out the release tag and build fullRelease with your existing keystore.

After installing

Open Config Builder and check that OpenAPS Boost is the selected APS. Check your maximum IOB and SMB settings, then watch the first cycles in the APS tab before relying on it.

Tools

The Simulator shows how Boost sizes a dose from a glucose level, trend and IOB; choose Boost 6.3.2 at the top. The Analyser compares V1 and V6 dosing on your own Nightscout data. The Tuning Guide explains each setting for 6.3.2 and 6.2.0.