GlucoWatch 0.1.18

GlucoWatch 0.1.18 adds KronLSTM R.80 and Timestral R.81 local glucose forecasts.

• KronLSTM R.80 forecasts up to ten hours. It becomes the default when a GlucoseDao access key is supplied and there is no installed model or explicit prior forecast choice. Explicit model addresses and model choices take precedence. No key or model is required for demo data or the built-in linear forecast.
• Timestral R.81 uses up to 72 hours of history and forecasts two hours. Both models are available in the phone's Model tab. config.example.yaml selects KronLSTM.
• Supported models receive available historical basal, bolus and carbohydrates from the selected glucose source and additional pump sources. Basal stays in U/h, bolus in U, and carbs in grams. Sensor gaps remain missing; long gaps reset recurrent memory. Corrected glucose or pump history replays the affected memory.
• KronLSTM imports its history and decoder graphs together from one pinned repository commit. Validation finishes before replacing a working model. First setup can take several minutes; automatic setup runs in the background while glucose refreshes, warnings and watch syncs continue. Prepared graphs are cached privately for later launches. Startup preparation also runs in the background with a labelled glucose-trend fallback. Large downloads stream into private temporary files rather than being duplicated in the Java heap.
• The watch can receive all 120 five-minute points of the ten-hour forecast from GlucoPhone. The pairing protocol and face's complication order are unchanged.

The core adapter accepts explicit future meal announcements for both models and planned extra bolus for KronLSTM, restricted to events known at the forecast origin. There is no what-if editor in this release. Delivered insulin is never reinterpreted as a planned extra dose, and future glucose is withheld.

All three APKs use versionCode 19 and the existing release certificate. No model weights, credentials, personal readings or health screenshots are bundled or committed. Models run locally; Hugging Face keys remain on the phone. The owner confirmed physical phone/watch pairing, syncing and login copying on 2026-11-04.

Validation passed all 291 checks (290 core regressions plus the real-model integration check), the actual revision-pinned bundles through the shared ONNX Runtime 1.28.0 adapter, physical-unit treatment inputs, glucose-only inputs, capability-gated explicit plans, cached graph reloads, minified standalone release builds, vital release lint, signing/alignment and signature-copy comparison against independent clean source builds. These checks establish integration behavior, not clinical accuracy. GlucoWatch and GlucoPhone are not medical devices.

Install

Obtainium installs GlucoPhone only, the phone app (glucowatch-phone-0.1.18.apk). It cannot put the watch app or the face on the watch. Wear OS does not let an app on the watch install other apps, so Obtainium on the watch cannot do it either.

The watch files are glucowatch-0.1.18.apk and glucowatch-watchface-0.1.18.apk. Send both from the phone with Wear Installer 2 (Malcolm Bryant, Play Store). Phone and watch must be on the same Wi-Fi.

1. Download both watch APKs from this release into the phone's Downloads.
2. On a Galaxy Watch, open Settings → About watch → Software information and tap Software version until Developer options appear. On other watches, tap Build number under Settings → System → About → Versions.
3. Turn on ADB debugging, then Wireless debugging.
4. In Wear Installer 2, enter the watch's IP address and tap Done. Menu → Pair with watch → Enable. On the watch, tap Pair new device. Enter the six-digit code, a space, and the pairing port.
5. Go back to the watch's main Wireless debugging screen. Enter its connection port in Wear Installer. That port is a different number from the pairing port, and it can change every time debugging is turned on.
6. Custom APK → glucowatch-0.1.18.apk → Install. Repeat for glucowatch-watchface-0.1.18.apk. Install both.
7. Open GlucoWatch once so the face can refresh.
8. Turn off Wireless debugging, then ADB debugging. The apps stay. Leaving debugging on uses the battery.

If the watch still has a debug-signed test copy installed, uninstall GlucoWatch and GlucoWatch face first. Android will not replace that test copy, and uninstalling it clears the login, the pairing, and stored forecasts. A later update of this release does not need an uninstall.

The same debugging on, install both files, open the app, debugging off cycle is how each later watch update is installed. The longer write-up is in the repository README under "Install the watch app and face from your phone".

GlucoWatch 0.1.17

GlucoWatch 0.1.17 adds a phone exercise library and optional glucose warnings on the phone and watch.

• More → Exercise imports complete Strava ZIP exports or individual FIT, GPX and TCX recordings, including gzip files. Activities stay on the phone, can be searched by name/date and filtered by sport, and exact recording duplicates are reused. Summary-only activities remain visible when no usable recording exists.
• Open an activity for interactive pace/speed, heart rate, elevation, glucose, bolus and basal panels. Pan, zoom and tap to inspect the shared time axis, or switch to whole-day context. Historical glucose/pump CSV imports persist separately from the live cache, tied to the configured source account. Before/during/after comparisons show available observations; absent data remains absent. Basal calculated from rates is labelled estimated.
• Alarms & notifications is available on each device. Warnings start off and must be enabled separately, with Android notification permission. Defaults are urgent low at or below 54 mg/dL, a fall of at least 2 mg/dL/min near or below 90, and high above 220 or a rising forecast crossing 220. Thresholds, forecast horizon and repeat interval are editable. Recent warning history, repeat suppression and urgent-low escalation are included.
• Warnings reject demo data and readings more than ten minutes old. Phone background checks use an inexact five-minute alarm and an Android network job; the watch uses its existing refresh schedule. Android scheduling, channel settings and Do Not Disturb affect delivery. These supplementary warnings never control the pump; keep official CGM alerts enabled and follow your care plan.

All three APKs use versionCode 18 and the existing release certificate. Validation includes 283 core tests, the complete 750-activity sample archive, Android import/persistence and duplicate-import checks, background network job scheduling, notification posting/throttling/escalation, stale/demo suppression, minified standalone builds, release lint checks, signature/alignment checks and comparison against clean source builds. Physical phone/watch warning delivery and live provider sign-in still require hardware verification. Existing unrelated watch-app full-lint findings remain. Personal exports, screenshots, credentials and model files are excluded from the release.

The Exercise page is phone-only. The watch face retains its existing layout and complication order. GlucoWatch and GlucoPhone are not medical devices.

Install

Obtainium installs GlucoPhone only, the phone app (glucowatch-phone-0.1.17.apk). It cannot put the watch app or the face on the watch. Wear OS does not let an app on the watch install other apps, so Obtainium on the watch cannot do it either.

The watch files are glucowatch-0.1.17.apk and glucowatch-watchface-0.1.17.apk. Send both from the phone with Wear Installer 2 (Malcolm Bryant, Play Store). Phone and watch must be on the same Wi-Fi.

1. Download both watch APKs from this release into the phone's Downloads.
2. On a Galaxy Watch, open Settings → About watch → Software information and tap Software version until Developer options appear. On other watches, tap Build number under Settings → System → About → Versions.
3. Turn on ADB debugging, then Wireless debugging.
4. In Wear Installer 2, enter the watch's IP address and tap Done. Menu → Pair with watch → Enable. On the watch, tap Pair new device. Enter the six-digit code, a space, and the pairing port.
5. Go back to the watch's main Wireless debugging screen. Enter its connection port in Wear Installer. That port is a different number from the pairing port, and it can change every time debugging is turned on.
6. Custom APK → glucowatch-0.1.17.apk → Install. Repeat for glucowatch-watchface-0.1.17.apk. Install both.
7. Open GlucoWatch once so the face can refresh.
8. Turn off Wireless debugging, then ADB debugging. The apps stay. Leaving debugging on uses the battery.

If the watch still has a debug-signed test copy installed, uninstall GlucoWatch and GlucoWatch face first. Android will not replace that test copy, and uninstalling it clears the login, the pairing, and stored forecasts. A later update of this release does not need an uninstall.

The same debugging on, install both files, open the app, debugging off cycle is how each later watch update is installed. The longer write-up is in the repository README under "Install the watch app and face from your phone".

GlucoWatch 0.1.16

GlucoWatch 0.1.16 improves GlucoPhone's long-interval exports and insulin comparison reports.

• About GlucoPhone shows the installed version name and code.
• Three months (90 days) collects three Medtronic CSV files in displayed 30-day intervals, newest first. Each file and its progress survives process restart. After confirming the pump files, Dexcom opens for one full-interval CSV. Overlapping native events merge once; renamed duplicate files cannot advance collection.
• PDF and CSV remain independent selections. CSV is enabled by default, including activity reports, and old format drafts migrate once to include it. Both selected files are saved in their respective Exports folders.
• The overview adds recorded bolus and basal amounts. When native data provides rates rather than measured basal doses, rate-times-duration basal and the resulting total are clearly labelled estimated. Missing coverage remains visible.
• Daily/activity ISF and ICR panels compare response points against native Bolus Wizard parameters. A pale step reference holds a known setting forward for up to 24 hours; the CSV does not contain the entire programmed schedule. The overview adds compact hourly rounded min-max rectangles and median marks over the pale pump reference. Provisional estimates remain labelled.
• Model information lists the accepted channels. GlucoseDAO bundles already receive available historical basal and bolus; most also accept carbs. The built-in trend and generic small ONNX imports use only glucose. Trained model metadata determines supported channels; missing pump data is not fabricated.

All three APKs use versionCode 17 and the existing signing certificate. Before publication: core regressions, Android three-file collection/restoration and 90-day PDF/CSV output, synthetic response/total checks, rendered PDF review, minified standalone builds, phone/watch-face release lint, signature/alignment and unsigned-build equivalence checks. Physical-device provider sign-in and portal date selection remain manual; emulator fixtures do not validate those live services. Existing watch-app lint findings are unchanged. Credentials, health exports and model files are excluded from the release.

These are conditional retrospective response estimates, not measured absorption or dose recommendations. GlucoWatch and GlucoPhone are not medical devices.

Install

Obtainium installs GlucoPhone only, the phone app (glucowatch-phone-0.1.16.apk). It cannot put the watch app or the face on the watch. Wear OS does not let an app on the watch install other apps, so Obtainium on the watch cannot do it either.

The watch files are glucowatch-0.1.16.apk and glucowatch-watchface-0.1.16.apk. Send both from the phone with Wear Installer 2 (Malcolm Bryant, Play Store). Phone and watch must be on the same Wi-Fi.

1. Download both watch APKs from this release into the phone's Downloads.
2. On a Galaxy Watch, open Settings → About watch → Software information and tap Software version until Developer options appear. On other watches, tap Build number under Settings → System → About → Versions.
3. Turn on ADB debugging, then Wireless debugging.
4. In Wear Installer 2, enter the watch's IP address and tap Done. Menu → Pair with watch → Enable. On the watch, tap Pair new device. Enter the six-digit code, a space, and the pairing port.
5. Go back to the watch's main Wireless debugging screen. Enter its connection port in Wear Installer. That port is a different number from the pairing port, and it can change every time debugging is turned on.
6. Custom APK → glucowatch-0.1.16.apk → Install. Repeat for glucowatch-watchface-0.1.16.apk. Install both.
7. Open GlucoWatch once so the face can refresh.
8. Turn off Wireless debugging, then ADB debugging. The apps stay. Leaving debugging on uses the battery.

If the watch still has a debug-signed test copy installed, uninstall GlucoWatch and GlucoWatch face first. Android will not replace that test copy, and uninstalling it clears the login, the pairing, and stored forecasts. A later update of this release does not need an uninstall.

The same debugging on, install both files, open the app, debugging off cycle is how each later watch update is installed. The longer write-up is in the repository README under "Install the watch app and face from your phone".

GlucoWatch 0.1.15

GlucoWatch 0.1.15 fixes phone export storage and successive downloads, and adds observed ISF/ICR response points that update with incoming data.

• GlucoPhone creates and restores its complete Downloads/GlucoPhone folder tree before exports. Provider originals and generated PDF/CSV files go into their category folders. Each saved path is verified; an unexpected flat-Downloads destination is an error. Folder creation is serialized across app processes. CSV archive reuse verifies the full content hash under a cross-process lock, preventing duplicate copies during the handoff.
• Sensor/pump exports now use the app-owned managed portal regardless of the default browser or older Chrome preferences. After a CSV is safely archived, that portal closes and the next source opens. External browsers are an explicit fallback. Browser-owned originals retain that browser's location; GlucoPhone archives a copy when imported/shared. Strava Google sign-in remains in Chrome.
• More → Insulin analysis refreshes live selected-account CGM/pump history every minute while open. It shows dated response estimates with their actual observation/window times and waiting reasons, instead of substituting the last imported report's pump settings.
• ISF points use isolated correction response from 90 minutes; ICR points use meal response from 3 hours with an independent observed/recorded ISF, or conditional near-baseline balance. No future readings, settings or later delivery confirmations populate earlier points. Gaps, overlapping meals, exercise, disconnection and basal changes exclude windows.
• Phone and PDF charts draw separate observation points without connecting curves or invented hourly values. Hollow points are provisional. Display thinning keeps charts readable; CSV retains every point, input window, method and assumptions. Native pump settings remain separate.

These are conditional retrospective estimates updated as readings arrive, not measured absorption or dose recommendations. The explicit triangular 6-hour action model, neutral-basal assumption and assumed meal appearance remain experimental. GlucoWatch and GlucoPhone are not medical devices.

All three APKs use versionCode 16 and the existing release certificate. 261 core regressions, synthetic folder/portal/response checks, standalone minified release builds and phone/watch-face release lint are checked before publication. Existing watch-app lint findings remain documented with 0.1.14; Play Store readiness and live provider authentication on physical phones are not established by emulator fixtures. Credentials, private reports and models are excluded from release APKs.

Install

Obtainium installs GlucoPhone only, the phone app (glucowatch-phone-0.1.15.apk). It cannot put the watch app or the face on the watch. Wear OS does not let an app on the watch install other apps, so Obtainium on the watch cannot do it either.

The watch files are glucowatch-0.1.15.apk and glucowatch-watchface-0.1.15.apk. Send both from the phone with Wear Installer 2 (Malcolm Bryant, Play Store). Phone and watch must be on the same Wi-Fi.

1. Download both watch APKs from this release into the phone's Downloads.
2. On a Galaxy Watch, open Settings → About watch → Software information and tap Software version until Developer options appear. On other watches, tap Build number under Settings → System → About → Versions.
3. Turn on ADB debugging, then Wireless debugging.
4. In Wear Installer 2, enter the watch's IP address and tap Done. Menu → Pair with watch → Enable. On the watch, tap Pair new device. Enter the six-digit code, a space, and the pairing port.
5. Go back to the watch's main Wireless debugging screen. Enter its connection port in Wear Installer. That port is a different number from the pairing port, and it can change every time debugging is turned on.
6. Custom APK → glucowatch-0.1.15.apk → Install. Repeat for glucowatch-watchface-0.1.15.apk. Install both.
7. Open GlucoWatch once so the face can refresh.
8. Turn off Wireless debugging, then ADB debugging. The apps stay. Leaving debugging on uses the battery.

If the watch still has a debug-signed test copy installed, uninstall GlucoWatch and GlucoWatch face first. Android will not replace that test copy, and uninstalling it clears the login, the pairing, and stored forecasts. A later update of this release does not need an uninstall.

The same debugging on, install both files, open the app, debugging off cycle is how each later watch update is installed. The longer write-up is in the repository README under "Install the watch app and face from your phone".

GlucoWatch 0.1.14

GlucoWatch 0.1.14 adds integrated glucose, insulin and workout reports, with matching watch, watch-face and phone releases.

• Export CSV and PDF together for 1–90 completed days. Portal prompts show the exact inclusive dates to select; originals and exports have separate provider/format folders and dated filenames.
• Read redesigned PDF summaries and daily glucose/insulin overlays, with food markers, cumulative extended-bolus ramps, basal layers and median/range summaries. Activities appear immediately after their day, newest first, with recorded elevation shaded behind the graphs. Open PDFs in the built-in offline viewer.
• Import multiple FIT workouts, including pool swims and activities with sparse observations. Edit pace/heart-rate zones, choose per-activity or combined reports, and record user-reported pump disconnection during swims. Incoming Strava originals are retained unchanged; filename suffixes do not determine duplicates.
• Inspect recorded pump ISF/ICR settings and clearly labelled experimental retrospective CGM-response estimates. Estimated insulin action and apparent carb appearance are model assumptions, not measured absorption or dose recommendations. CSV retains source events and identifies calculated/user-reported rows separately.
• Improved Hugging Face model discovery/download handling, stored forecast comparisons, phone/watch Bluetooth reliability, and Windows simulator tooling. Portal back gestures now follow browser history and popup navigation on Android 13+. The watch face now declares that it works without a phone app. The phone simulator checks for Chrome before external Google/Strava sign-in.

All three APKs use versionCode 15 and the existing release certificate. Core tests: 257 passing. Release APKs are minified and built from inside each module; signatures and unsigned-build equivalence are checked before publication. Phone and watch-face release lint pass. Developer-tool tests pass (27 passing, one platform-specific skip), as do the portal CSV capture regressions. The broad watch lint audit still reports existing permission, restricted tile API, preview-resolution and Wear password-entry issues; this release does not establish Play Store readiness.

config.example.yaml is an unfilled configuration template. Credentials, private reports, original health files and prediction models are not bundled in the release. GlucoWatch and GlucoPhone are not medical devices; do not use their reports or predictions for treatment decisions. Live portal sign-in, automatic file acquisition and the phone/watch link still need verification on physical devices.

Install

Obtainium installs GlucoPhone only, the phone app (glucowatch-phone-0.1.14.apk). It cannot put the watch app or the face on the watch. Wear OS does not let an app on the watch install other apps, so Obtainium on the watch cannot do it either.

The watch files are glucowatch-0.1.14.apk and glucowatch-watchface-0.1.14.apk. Send both from the phone with Wear Installer 2 (Malcolm Bryant, Play Store). Phone and watch must be on the same Wi-Fi.

1. Download both watch APKs from this release into the phone's Downloads.
2. On a Galaxy Watch, open Settings → About watch → Software information and tap Software version until Developer options appear. On other watches, tap Build number under Settings → System → About → Versions.
3. Turn on ADB debugging, then Wireless debugging.
4. In Wear Installer 2, enter the watch's IP address and tap Done. Menu → Pair with watch → Enable. On the watch, tap Pair new device. Enter the six-digit code, a space, and the pairing port.
5. Go back to the watch's main Wireless debugging screen. Enter its connection port in Wear Installer. That port is a different number from the pairing port, and it can change every time debugging is turned on.
6. Custom APK → glucowatch-0.1.14.apk → Install. Repeat for glucowatch-watchface-0.1.14.apk. Install both.
7. Open GlucoWatch once so the face can refresh.
8. Turn off Wireless debugging, then ADB debugging. The apps stay. Leaving debugging on uses the battery.

If the watch still has a debug-signed test copy installed, uninstall GlucoWatch and GlucoWatch face first. Android will not replace that test copy, and uninstalling it clears the login, the pairing, and stored forecasts. A later update of this release does not need an uninstall.

The same debugging on, install both files, open the app, debugging off cycle is how each later watch update is installed. The longer write-up is in the repository README under "Install the watch app and face from your phone".

GlucoWatch 0.1.13

GlucoWatch 0.1.13 keeps more of the recent glucose on the watch face and stores a forecast so it can be compared with what happened later.

• The watch face keeps two hours of history and draws a bolus as a small dot with the dose beside it.
• Check prediction, under Refresh on the watch and under Refresh now in the phone menu, stores the model's full forecast. Prediction history lays that forecast over the readings that followed.

All three APKs use versionCode 14 and the existing release signing certificate. Core tests pass. Release APKs are built inside each module.

config.example.yaml is an unfilled template. Account credentials and models are not bundled in any APK.

Install

Obtainium installs GlucoPhone only, the phone app (glucowatch-phone-0.1.13.apk). It cannot put the watch app or the face on the watch. Wear OS does not let an app on the watch install other apps, so Obtainium on the watch cannot do it either.

The watch files are glucowatch-0.1.13.apk and glucowatch-watchface-0.1.13.apk. Send both from the phone with Wear Installer 2 (Malcolm Bryant, Play Store). Phone and watch must be on the same Wi-Fi.

1. Download both watch APKs from this release into the phone's Downloads.
2. On a Galaxy Watch, open Settings → About watch → Software information and tap Software version until Developer options appear. On other watches, tap Build number under Settings → System → About → Versions.
3. Turn on ADB debugging, then Wireless debugging.
4. In Wear Installer 2, enter the watch's IP address and tap Done. Menu → Pair with watch → Enable. On the watch, tap Pair new device. Enter the six-digit code, a space, and the pairing port.
5. Go back to the watch's main Wireless debugging screen. Enter its connection port in Wear Installer. That port is a different number from the pairing port, and it can change every time debugging is turned on.
6. Custom APK → glucowatch-0.1.13.apk → Install. Repeat for glucowatch-watchface-0.1.13.apk. Install both.
7. Open GlucoWatch once so the face can refresh.
8. Turn off Wireless debugging, then ADB debugging. The apps stay. Leaving debugging on uses the battery.

If the watch still has a copy installed from a computer, uninstall GlucoWatch and GlucoWatch face first. Android will not replace that test copy, and uninstalling it clears the login, the pairing, and stored forecasts. A later update of this release does not need an uninstall.

The same debugging on, install both files, open the app, debugging off cycle is how each later watch update is installed. The longer write-up is in the repository README under "Install the watch app and face from your phone".

GlucoWatch 0.1.12

GlucoWatch 0.1.12 addresses the F-Droid review of the watch app and watch face.

• The watch listing explains optional Medtronic CareLink setup through GlucoPhone and links to the phone APK. Watch app and watch face installation instructions now describe their separate downloads and review status.
• The watch face has its own title, description, icon, interactive and ambient demo screenshots, and changelog. Its listing explains that glucose complications need the GlucoWatch app on the same watch.
• Watch Settings is private in release builds. Development builds retain the external entry point used by emulator capture tools.
• The standard GlucoPhone APK retains local ONNX prediction, private YAML/.env configuration import, Hugging Face repository resolution, and the full model forecast horizon. No additional ONNX development APK is needed.

All three APKs use versionCode 13 and the existing release signing certificate. Core tests pass. Release APKs are built inside each module and checked against independent clean builds using apksigcopier. Demo surfaces were captured on 432, 438 and 480 px Wear emulators; production Settings navigation was checked on an emulator. Physical-watch heart-rate prompts and Bluetooth pairing still require hardware testing.

config.example.yaml is an unfilled template. Account credentials and models are not bundled in any APK. The ONNX runtime is included only in the normal phone APK; the watch release and code-less face do not contain native runtime libraries.

GlucoWatch 0.1.11

GlucoPhone now includes local ONNX inference in the normal phone release APK. The separate ONNX development APK from 0.1.10 is superseded; install glucowatch-phone-0.1.11.apk on the phone.

• Import a private .env or config.yaml on Connect to configure accounts and automatically download/select a Hugging Face model. A repository name is sufficient.
• Run CITRAS, INPAINT-CITRAS and NF-TFT locally, using available covariates from the same person's overlapping glucose and pump history. Missing pump history permits glucose-only inference; incompatible inputs produce a labelled glucose-trend fallback.
• Display each model's maximum horizon: 120 minutes for CITRAS/NF-TFT and 240 minutes for this INPAINT export, with a continuous forecast line.
• ONNX Runtime Android is pinned to MIT-licensed 1.28.0, whose Android package has no telemetry initializer or transport classes. Telemetry is disabled before sessions are created. Runtime licence and third-party notices are included.
• The watch receives phone forecasts through the existing paired link. Watch release APKs do not bundle the native runtime.

Install glucowatch-0.1.11.apk and glucowatch-watchface-0.1.11.apk on the watch; install glucowatch-phone-0.1.11.apk on the phone. All use the established release certificate. No credentials or model weights are bundled. config.example.yaml has empty credentials; filled personal configurations stay private.

Validation: 161 core tests; all three minified release builds; fresh-checkout APK reproducibility comparisons; signing, alignment and credential checks; F-Droid source/APK scans. The non-debuggable minified phone build loaded all three bundles on an x86_64 emulator and passed private YAML import with model setup. CITRAS and INPAINT produced live Dexcom + CareLink forecasts; NF-TFT used its labelled fallback with the available short history. Real-device Bluetooth pairing is still unverified.

F-Droid scanner checks are not acceptance: the existing watch/face submissions review 0.1.8, and the phone has not been submitted.

GlucoWatch 0.1.10

GlucoWatch 0.1.10

• Configure the phone from a .env or YAML file, or an HTTPS configuration URL. Supplied Hugging Face models download, validate and select automatically.
• Find ONNX files by Hugging Face repository name, URL or model-name search, with shortcuts for the three GlucoseDao models.
• Display the model's full forecast horizon: 240 minutes for the INPAINT-CITRAS export and 120 minutes for CITRAS and NF-TFT. Prediction lines are continuous and the phone chart clearly separates history from prediction.
• Use overlapping glucose and pump covariates, including basal, bolus and supported carbohydrate channels. Missing pump history allows glucose-only prediction; switching accounts clears inherited pump selections unless explicitly supplied.
• Improve imported-model preprocessing, missing-data masks, Nightscout basal profiles and timestamp coverage. Add private, reproducible inference comparison tools.

Choose the phone APK

For the three GlucoseDao transformer models, install glucowatch-phone-onnx-development-0.1.10.apk. This is a development/debug build with the native ONNX CPU runtime, empty credential defaults and the existing GlucoWatch release signing certificate. Import your private config in Connect → Upload .env / YAML, or use Import from URL. The graph and preprocessing sidecars are downloaded from Hugging Face; model files and personal settings are not bundled. config.example.yaml is a blank-credential example, not a working account configuration.

The standard glucowatch-phone-0.1.10.apk retains the source-only small dense ONNX interpreter. It supports configuration import but cannot run the three transformer bundles. It does not include the native runtime. Choose one of these phone APKs; both use the same package and release certificate. If you previously installed a locally debug-signed APK, uninstall it before installing a release-signed phone APK, then import your configuration again.

Install glucowatch-0.1.10.apk and glucowatch-watchface-0.1.10.apk on the watch. To display the phone's transformer prediction, choose Phone app as its source and Phone app model as its predictor. No model or HF token crosses the phone link. Keep the watch app and phone current. CareLink on a new phone requires browser sign-in unless you move a complete session; rotating refresh tokens must belong to only one device.

Validation

• 161 core tests and 7 inference-preprocessing tests pass.
• All three standard release APKs were built from their module directories, signed with the existing release certificate, and compared against fresh builds from this commit.
• File-picker and URL imports, automatic authenticated model setup, 48-point/240-minute phone inference and watch rendering were checked on Android emulators. Configuration import also passed in the minified release phone APK.
• No personal credentials, filled configs, model binaries or real-data screenshots are published. Standard release APKs have no native inference runtime.

Bluetooth pairing and combined prediction on physical phone/watch hardware still need verification. This is not a medical device.

GlucoWatch 0.1.9

GlucoWatch 0.1.9

• The watch face displays a larger glucose value with the trend arrow beside it, and the date and a 24-hour clock on the right.
• Check graphs in the watch app opens the last 24 hours of stored glucose. Drag the chart or turn the bezel to browse earlier readings.
• Bezel and crown scrolling now work in the main watch app, settings and diagnostics.
• The watch app shows a running temporary basal with its rate or percentage and time remaining.
• CareLink reads temporary basal markers, the currently running temp and cancellations. Pump percentages remain distinct from Nightscout percentage adjustments.

Install glucowatch-0.1.9.apk and glucowatch-watchface-0.1.9.apk on the watch. The optional glucowatch-phone-0.1.9.apk goes on the phone.

Update the watch and phone apps together. The phone-link protocol is now version 3 to carry the pump percentage flag. Existing pairing keys remain valid, but mixed app versions show an update message. Pairing and bezel behavior on real hardware still need verification.

For Obtainium, use an exact APK filename filter for each package: ^glucowatch-[0-9]+\.[0-9]+\.[0-9]+\.apk$, ^glucowatch-watchface-[0-9]+\.[0-9]+\.[0-9]+\.apk$, or ^glucowatch-phone-[0-9]+\.[0-9]+\.[0-9]+\.apk$.

All three APKs use versionCode 10 and the existing GlucoWatch release signing certificate. The 138 core tests pass, and all three module-directory release builds pass. APK signatures and reproducibility against fresh module-directory builds from the release commit were checked.