CamAPS FX (mmol/L): compare 189 vs 192

Investigation date: 17/06/2026 (updated with CamAPS Liberty findings)

Compare 189 vs 192:

Method: APKEditor decompile, manifest diff, strings/arrays diff, smali package scan, public sources.

Executive summary

New in 192 at a glance

Version and platform table

Fully NEW features in 192 (not present in 189)

1. Dexcom G7 CGM integration (major)

Evidence: 160 smali files under com.camdiab.dexcomg7 and com.dexcom.coresdk.g7* in 192; zero in 189.

User-visible G7 capabilities in 192:

• Select Dexcom G7 as CGM type (alongside G6 and Libre 3).
• Sign in with a Dexcom account inside CamAPS.
• Pair G7 using a 4-digit pairing code (not G6-style sensor code).
• G7-specific help, troubleshooting, and calibration messaging.
• Factory-calibrated G7 workflow (different from G6 sensor code flow).

Note: 189 contains a cloud DTO enum value DEXCOM_G7 in BaseDTO$CGMType (backend typing only). There is no runnable G7 stack in the 189 APK.

2. CamAPS Liberty fully closed-loop mode (major)

CamAPS Liberty is CamDiab's fully closed-loop (FCL) feature: when enabled, users can skip meal/snack boluses and carb counting while Auto mode is on. It is optional and intended for periodic use.

Evidence in 192: present. In 189: zero Liberty strings, no fxfcl package.

In-app strings found in 192 (English):

Norwegian strings are also bundled (e.g. CamAPS Liberty-opplæring, CamAPS Liberty er aktiv).

User-visible behavior (when enabled and available):

• Toggle Liberty from Settings (per CamDiab Liberty page).
• More proactive algorithm; no pre-meal bolus or carb counting during active Liberty periods.
• Standard hybrid closed-loop (manual boluses) remains available when Liberty is off.

Built-in vs visible in your app:

CamDiab's public site notes rollout is pending local market approvals for some user groups (YpsoPump / Dana). The 192 APK contains the feature; visibility may depend on server-side flags.

3. Wearable / Dexcom watch plumbing (new infrastructure)

This is Dexcom SDK watch communication, not a full standalone CamAPS Wear OS app. It supports the G7/Dexcom ecosystem; CamDiab still lists Wear OS CamAPS as a future roadmap item on community changelogs.

4. Notification policy access (new permission)

Likely allows the app to interact with Do Not Disturb / notification policy for alerts. No user-facing label found; treated as supporting improved alert delivery on newer Android versions.

MODIFIED / updated in 192 (existing areas changed)

5. Android OS compatibility and minimum version

CamDiab does not publish a line-by-line "Android 16 fixes" list for build 192. The update is best described as keeping the app working on current OS versions.

6. Security / licensing stack

192 updates anti-tamper / Play licensing integration. Not a user-facing feature, but relevant for install source validation.

7. App size and code structure

Growth is primarily G7 SDK integration, CamAPS Liberty (FCL) code, updated dependencies, and arm64/xxhdpi assets (the 189 XAPK bundle is also smaller/wrong-arch).

8. Dependency / library updates (modified, not new product features)

Obfuscation package rename (b.* → a.* for many support stubs) is a rebuild artifact, not a user feature.

Google Play Services components updated (e.g. GoogleApiActivity registered in 192).

UNCHANGED core product features (both versions)

These exist in both 189 and 192:

Features NOT found as new in 192

Searched but not evidenced as new user features in 192 vs 189:

Public changelog vs APK analysis

Recommendation table

CGM error codes (Libre, G6, G7)

Yes: all user-facing support reference codes and internal notification enums can be extracted from a decompiled APK. CamAPS does not ship a public error-code manual; the APK strings.xml and HandleErrorMessage$NotificationCodes smali enums are the authoritative in-app sources.

Two layers of "error codes"

User-facing messages for internal errors are mostly generic ("Internal error XXXXX. Restart your smart device."). The code is still useful when contacting CamDiab / mylife support.

Counts in 1.4(192).101

G7 user-facing codes (192): DG7X001, DG7X002, DG7X003, DG7X023, DG7X024, DG7X025, DG7X026, DG7X027, DG7X028, DG7X029, DG7X030, DG7X031, DG7X032, DG7X033, DG7X034, DG7X037, DG7X038, DG7X041.

Libre user-facing codes (both builds): LBR001 through LBR025.

G6 user-facing codes (both builds): DDC001 through DDC081 and DCI001 through DCI082 (sequential blocks). All use the same message pattern except where noted below.

Full user-facing error code list (1.4.192.101)

Source: to-do/CGM-ERROR-CODES-192.csv. Libre and G6 codes are identical in 189 and 192. G7 codes are 192 only.

FreeStyle Libre 3 (LBR###) — 25 codes, both 189 and 192

Norwegian locale (nb): Intern feil LBRnnn. Start smartenheten på nytt.

Dexcom G7 (DG7X###) — 18 codes, 192 only

Dexcom G6 (DDC### + DCI###) — 163 codes, both 189 and 192

All codes use: Internal error {code}. Restart your smart device.

DDC block (81 codes): DDC001, DDC002, DDC003, DDC004, DDC005, DDC006, DDC007, DDC008, DDC009, DDC010, DDC011, DDC012, DDC013, DDC014, DDC015, DDC016, DDC017, DDC018, DDC019, DDC020, DDC021, DDC022, DDC023, DDC024, DDC025, DDC026, DDC027, DDC028, DDC029, DDC030, DDC031, DDC032, DDC033, DDC034, DDC035, DDC036, DDC037, DDC038, DDC039, DDC040, DDC041, DDC042, DDC043, DDC044, DDC045, DDC046, DDC047, DDC048, DDC049, DDC050, DDC051, DDC052, DDC053, DDC054, DDC055, DDC056, DDC057, DDC058, DDC059, DDC060, DDC061, DDC062, DDC063, DDC064, DDC065, DDC066, DDC067, DDC068, DDC069, DDC070, DDC071, DDC072, DDC073, DDC074, DDC075, DDC076, DDC077, DDC078, DDC079, DDC080, DDC081

DCI block (82 codes): DCI001, DCI002, DCI003, DCI004, DCI005, DCI006, DCI007, DCI008, DCI009, DCI010, DCI011, DCI012, DCI013, DCI014, DCI015, DCI016, DCI017, DCI018, DCI019, DCI020, DCI021, DCI022, DCI023, DCI024, DCI025, DCI026, DCI027, DCI028, DCI029, DCI030, DCI031, DCI032, DCI033, DCI034, DCI035, DCI036, DCI037, DCI038, DCI039, DCI040, DCI041, DCI042, DCI043, DCI044, DCI045, DCI046, DCI047, DCI048, DCI049, DCI050, DCI051, DCI052, DCI053, DCI054, DCI055, DCI056, DCI057, DCI058, DCI059, DCI060, DCI061, DCI062, DCI063, DCI064, DCI065, DCI066, DCI067, DCI068, DCI069, DCI070, DCI071, DCI072, DCI073, DCI074, DCI075, DCI076, DCI077, DCI078, DCI079, DCI080, DCI081, DCI082

Full internal notification enum list (1.4.192.101)

Source: to-do/CGM-NOTIFICATION-ENUMS-192.csv. Used in logs and developer mapping; not always shown to users. Libre and G6 enums are identical in 189 and 192. G7 enums are 192 only.

Libre (LS3_*) — 44 constants

LS3_DB_CONTEXT_NULL, LS3_DB_CREATION_FAIL, LS3_DB_DELETE_FAIL, LS3_DB_DEL_EXCEPTION, LS3_DB_DEL_EXCEPTION2, LS3_DB_DEL_EXCEPTION3, LS3_DB_GET_EXCEPTION1, LS3_DB_GET_EXCEPTION2, LS3_DB_INS_EXCEPTION, LS3_DB_INS_FAILED, LS3_DB_INTEGRITY_FAIL, LS3_DB_OPEN_EXCEPTION, LS3_HANDLER_STUCK, LS3_MSG_BAD_IDX_1, LS3_MSG_BAD_IDX_2, LS3_MSG_BAD_IDX_3, LS3_MSG_BAD_IDX_4, LS3_MSG_CRC_CALC, LS3_MSG_CRC_CHECK, LS3_MSG_CURR_SENSOR, LS3_MSG_EXC_MSG_ACK, LS3_MSG_EXC_SAVE_INFO, LS3_MSG_FALL_RATE, LS3_MSG_HIGH, LS3_MSG_LOW, LS3_MSG_NO_READINGS, LS3_MSG_RISE_RATE, LS3_MSG_SENSOR_2HOURS, LS3_MSG_SENSOR_30MINUTES, LS3_MSG_SENSOR_6HOURS, LS3_MSG_SENSOR_EXPIRED, LS3_MSG_SENSOR_FAILED, LS3_MSG_SENSOR_WARM_UP, LS3_MSG_SIGNAL_LOSS, LS3_MSG_START_SESS_ERR, LS3_MSG_TEMP_HIGH, LS3_MSG_TEMP_LOW, LS3_MSG_UNKNOWN_ERROR, LS3_MSG_URGENT_LOW, LS3_MSG_URGENT_LOW_SOON, LS3_MSG_VITAMIN_C, LS3_MSG_WAKELOCK_ERROR, LS3_MSG_WRONG_PIN, LS3_TOO_BIG_GAP

Dexcom G6 (DX_*) — 59 constants

DX_DB_CIPHER, DX_DB_CONTEXT_NULL, DX_DB_CREATION_FAIL, DX_DB_DELETE_FAIL, DX_DB_DEL_EXCEPTION, DX_DB_DEL_EXCEPTION2, DX_DB_DEL_EXCEPTION3, DX_DB_GET_EXCEPTION1, DX_DB_GET_EXCEPTION2, DX_DB_INS_EXCEPTION, DX_DB_INS_FAILED, DX_DB_INTEGRITY_FAIL, DX_DB_OPEN_EXCEPTION, DX_END_OF_LIFE, DX_MSG_1ST_CALIB, DX_MSG_2ND_CALIB, DX_MSG_CALIB_ERR, DX_MSG_CRC_CALC, DX_MSG_CRC_CHECK, DX_MSG_CYCLE_BLUETOOTH, DX_MSG_END_SESS_ERR, DX_MSG_EXCEPTION, DX_MSG_EXC_MSG_ACK, DX_MSG_FALL_RATE, DX_MSG_GATT_ERROR_NOTI, DX_MSG_HIGH, DX_MSG_INVALID_BG, DX_MSG_LOW, DX_MSG_NEXT_CALIB, DX_MSG_NEXT_NEW_CALIB, DX_MSG_NO_READINGS, DX_MSG_PAIRED, DX_MSG_PAIRING, DX_MSG_PAIRING_FAILED, DX_MSG_PLANNED_CALIB, DX_MSG_RESTART_APP, DX_MSG_RISE_RATE, DX_MSG_SCAN_STUCK, DX_MSG_SENSOR_2HOURS, DX_MSG_SENSOR_30MINUTES, DX_MSG_SENSOR_6HOURS, DX_MSG_SENSOR_EXPIRED, DX_MSG_SENSOR_FAILED, DX_MSG_SENSOR_RESTART, DX_MSG_SENSOR_WARM_UP, DX_MSG_SIGNAL_LOSS, DX_MSG_SN_NAME_WRONG, DX_MSG_START_SESS_ERR, DX_MSG_TRANS_14DAYS, DX_MSG_TRANS_22DAYS, DX_MSG_TRANS_FAILED, DX_MSG_TRANS_LAST_END, DX_MSG_TRANS_LAST_START, DX_MSG_TRANS_LOW_BATTERY, DX_MSG_TRANS_TAKEN, DX_MSG_UNKNOWN_ERROR, DX_MSG_URGENT_LOW, DX_MSG_URGENT_LOW_SOON, DX_MSG_WAKELOCK_ERROR

Dexcom G7 (DX_*, separate package) — 44 constants, 192 only

DX_DB_CONTEXT_NULL, DX_DB_CREATION_FAIL, DX_DB_DELETE_FAIL, DX_DB_DEL_EXCEPTION, DX_DB_DEL_EXCEPTION2, DX_DB_DEL_EXCEPTION3, DX_DB_GET_EXCEPTION1, DX_DB_GET_EXCEPTION2, DX_DB_INS_EXCEPTION, DX_DB_INS_FAILED, DX_DB_INTEGRITY_FAIL, DX_DB_OPEN_EXCEPTION, DX_INVALID_TEST_CODE, DX_MSG_BAD_CALIBRATION, DX_MSG_CRC_CALC, DX_MSG_CRC_CHECK, DX_MSG_EXC_MSG_ACK, DX_MSG_FALL_RATE, DX_MSG_HIGH, DX_MSG_LOW, DX_MSG_OUT_OF_RANGE, DX_MSG_PAIRED, DX_MSG_PAIRING, DX_MSG_PAIRING_FAILED, DX_MSG_RESTART_APP, DX_MSG_RISE_RATE, DX_MSG_SENSOR_24_HOURS, DX_MSG_SENSOR_2HOURS, DX_MSG_SENSOR_FAILED, DX_MSG_SENSOR_GRACE, DX_MSG_SENSOR_NO_GRACE, DX_MSG_SIGNAL_LOSS, DX_MSG_SIV_FAIL, DX_MSG_STOPPED, DX_MSG_TEMP_PROBLEM, DX_MSG_TRANS_FAILED, DX_MSG_UNKNOWN_ERROR, DX_MSG_URGENT_LOW, DX_MSG_URGENT_LOW_SOON, DX_MSG_WARMUP, DX_NO_DEXCOM_CERT, DX_NO_DISK_SPACE, DX_NO_FACTORY_TIME, DX_NO_ROOT_CERT

Smali paths (192 decompile)

Example internal Libre codes: LS3_MSG_SENSOR_EXPIRED, LS3_MSG_WRONG_PIN, LS3_MSG_VITAMIN_C, LS3_MSG_SIGNAL_LOSS.

Example internal G6 codes: DX_MSG_1ST_CALIB, DX_MSG_TRANS_LOW_BATTERY, DX_MSG_PAIRING_FAILED, DX_END_OF_LIFE.

Example internal G7 codes: DX_MSG_BAD_CALIBRATION, DX_MSG_SENSOR_GRACE, DX_MSG_WARMUP, DX_INVALID_TEST_CODE.

G6 and G7 share the DX_ prefix in enums but live in different packages; G7 enums are not a superset of G6.

How to extract (repeatable)

1. Decompile build 192:

   java -jar backups\camaps-fx\tools\APKEditor.jar d -i <path-to-192.apk> -o $env:TEMP\camaps-deep\192
   

2. Run the extractor script:

   .\backups\camaps-fx\tools\extract-cgm-error-codes.ps1 -DecompileRoot $env:TEMP\camaps-deep\192
   

3. Or grep strings.xml manually:

   Select-String -Path "$env:TEMP\camaps-deep\192\resources\package_1\res\values\strings.xml" -Pattern '\b(DG7X|DDC|DCI|LBR)\d{3}\b'
   

Exported inventories (this investigation)

Limits

• Codes are CamAPS-internal reference IDs, not Dexcom or Abbott public fault codes.
• Most user strings do not explain root cause; support uses the code to look up logs.
• Norwegian (nb) and other locale splits may override message text; codes stay the same.
• Runtime-only errors (no string resource) would not appear in strings.xml; enum smali is the fallback list.

Abbott Libre numeric codes (2024 community list) vs CamAPS codes

Your August 2024 list uses Abbott LibreLink / sensor fault numbers (e.g. 57, 335, 373, 380, 4000-series, 410–725). CamAPS uses a different scheme and does not embed those Abbott numbers in strings.xml.

Practical mapping (conceptual, not 1:1 in APK):

Still current for CamAPS (192): use LBR### + LS3_* from this report and CGM-ERROR-CODES-192.csv, not the 2024 Abbott number list, when talking to CamDiab / mylife support about CamAPS. Keep the Abbott list for LibreLink-only or raw NFC troubleshooting.

Unchanged 189→192: Libre user-facing (LBR###) and internal (LS3_*) sets are identical. New in 192: only G7 codes (DG7X###, 18 user-facing).

Companion, Glooko, and third-party sharing (xDrip+ / Nightscout)

Short answer

Official sharing channels (both 189 and 192)

Companion and SMS Followers are mutually exclusive (same as before).

What Companion shares (unchanged GDPR text 189 vs 192)

GDPR Usage and Linkage Data paragraph is byte-identical in 189 and 192:

• Pump and transmitter serial number
• Pump, sensor, and closed-loop / open-loop actions trail
• App command-flow trail
• Event trail
• Follower / portal account info as entered in the app
• Support queries, trainer details

Companion invite text (192): share sensor glucose and insulin data with optional trend graph view. Companion mode: no data re-sharing, no pump/CGM control.

Cloud DTO fields (Glooko / mylife upload): 189 vs 192 diff

Compared com.camdiab.fx_alert.cloud.mylife.data.dto.* between builds:

So there are no new JSON/DTO properties in 192 that xDrip+ or Nightscout could consume without a separate bridge.

What is new in practice for followers (192 only)

These are not new Companion settings, but new content a Companion or cloud upload may carry when the patient uses 192 features:

Recommended paths to Nightscout / xDrip+ (outside CamAPS)

Bottom line: 192 adds G7 and Liberty as therapy features, but no new open export for xDrip+ or Nightscout. For open-loop integrations, use Glooko, Dexcom Follow, or a parallel CGM path (Juggluco/xDrip+), not CamAPS Companion.

Investigation artifacts

• Decompiled trees: %TEMP%\camaps-deep\189-base, %TEMP%\camaps-deep\192
• CGM error exports: to-do/CGM-ERROR-CODES-192.csv, to-do/CGM-NOTIFICATION-ENUMS-192.csv
• Norwegian report: to-do/APK-COMPARISON-189-vs-192-REPORT.nb.md
• Extractor script: tools/extract-cgm-error-codes.ps1
• Tools: APKEditor 1.4.5, platform-tools adb 37.0.0
• Original plan: camaps_apk_comparison_7491c498.plan.md