CamAPS FX Liberty: access check on build 194

Investigation date: 07/10/2026

Question: after CamAPS FX Liberty became newly accessible on the phone, is there a separate Liberty APK/package, or is Liberty still inside the existing mmol/L CamAPS FX app?

Method: wireless ADB pair/connect, pm list packages, pm path, dumpsys package, aapt dump badging, UTF-8 string scan of base.apk, compare to archive camaps-fx-mmoll-20261005-230724.

Executive summary

At a glance (Liberty vs prior mmol/L work)

Packages discovered on device

Third-party diabetes-related packages of interest:

Commands used:

adb pair 192.168.1.25:42667 <pairing-code>
adb connect 192.168.1.25:40791
adb shell pm list packages | findstr /i cam
adb shell pm path com.camdiab.fx_alert.mmoll
adb shell dumpsys package com.camdiab.fx_alert.mmoll

No package id containing liberty or a second camdiab / fx_alert flavor was present (including disabled / uninstalled remnants).

Note: adb pair returned a transient protocol fault once; adb connect to the debug port still authorized the device (CPH2449 / OP594DL1).

Extract metadata

These four hashes are identical to backups/camaps-fx/camaps-fx-mmoll-20261005-230724/. Re-merge / full decompile was not required for delta detection: there is no binary change to compare against that archive.

dumpsys also showed firstInstallTime / lastUpdateTime of 07/10/2026 10:52:35 (local device time). That indicates a reinstall or Play refresh today, but the payload is still 194 with the same hashes.

Archive copy of this pull: backups/camaps-fx/camaps-fx-mmoll-20261007-171213/ and D:\Temp\camaps-liberty-20261007-171213\.

What CamAPS Liberty is (unchanged since 192)

Official product page: CamAPS Liberty.

Liberty is CamDiab's optional full closed loop (FCL) mode inside CamAPS FX:

• When active (and Auto mode on), users may skip meal/snack bolus and carb counting for periods of use.
• Toggle from Settings when the clinic / account allows it.
• Hybrid closed loop (manual boluses) remains available when Liberty is off.

APK evidence from the earlier 189 vs 192 work (still valid for 194; string set unchanged 192→194):

This extract confirms CamAPS Liberty still appears in base.apk (UTF-8 scan count: 6). No new Liberty-only package id.

Security and packaging (vs older mmol/L)

Relative to build 192, build 194 (this binary) already:

• Raised targetSdk / compileSdk 35 → 36 (Android 16)
• Removed Google PairIP Play license client (com.pairip.*, LicenseActivity, CHECK_LICENSE)
• Kept therapy features (G7, Libre 3 / Plus, Liberty) without a new therapy feature bump

This Liberty access check adds: no further packaging change after 05/10/2026.

Permissions (194 / this extract)

Selected declared permissions from aapt dump badging on base.apk:

No CHECK_LICENSE permission in this build (PairIP era).

DIY / Companion / language (unchanged conclusion)

Practical takeaway

1. Keep treating the installed app as CamAPS FX mmol/L 194 (com.camdiab.fx_alert.mmoll, 1.4(194).101).
2. Liberty access is not a second store app on this phone; look for the Liberty toggle under CamAPS Settings once the account is entitled.
3. For binary diffs, the 05/10/2026 192 vs 194 report remains the correct packaging/security comparison. This report only answers the Liberty-package question.
4. If CamDiab later ships a true separate Liberty package id, re-run pm list packages and extract again; do not assume it from UI wording alone.

Related News Targeted reports

Limits

• No root: cannot read account entitlement flags from app private storage.
• String scan is UTF-8 plaintext in base.apk; obfuscated class names may hide fxfcl as a literal.
• This is technical documentation from APK / package analysis, not medical advice or official Ypsomed / CamDiab support.

Tools

• platform-tools adb (Android SDK)
• Android build-tools aapt 36.0.0
• Prior APKEditor merge/decompile archives for 192 and 194