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

Investigation date: 20/10/2026

Compare 189, 192, 193, and 194 (Android mmol/L line), plus a short link to the connection deep-dive report.

Method: XAPK unzip, APKEditor merge + decompile, aapt badging/permissions, manifest diff, smali package counts, connection-related string value scan.

Device context for Play extracts: OnePlus 11 (CPH2449), Android 16. Lab decompile: D:\Users\USER\Temp\camaps-compare\.

Important package note (evidence): build 193 from APKPure is the Canadian package id com.camdiab.fx_alert.mmoll.ca, not the EU/NO Play package com.camdiab.fx_alert.mmoll used for 189/192/194. Treat 193 as a same product family sibling, not a drop-in Play update of the EU binary.

Executive summary

At a glance

Version and platform table

SHA256 (merged, this lab):

193 XAPK splits:

Smali package footprint (evidence)

Counts of .smali files under multi-dex smali/classes*:

Interpretation: therapy stacks stabilize at 192. 193/194 are packaging / OS / licensing deltas on that base, not a second G7-sized feature add.

Permissions and security

Permissions that matter for connection

Present on all four (same pattern from 192 onward; 189 already had the Android 12 BLE set):

• BLUETOOTH_SCAN with neverForLocation
• BLUETOOTH_CONNECT
• Legacy BLUETOOTH / BLUETOOTH_ADMIN with maxSdkVersion="30"
• NFC
• FOREGROUND_SERVICE + FOREGROUND_SERVICE_CONNECTED_DEVICE
• REQUEST_IGNORE_BATTERY_OPTIMIZATIONS
• Location permissions with maxSdkVersion="30" (pre-Android 12 BLE scan path)

uses-feature: android.hardware.bluetooth_le required=true on 189 to 194.

PairIP / Play license

Evidence: PairIP client stack is removed only in 194 (EU). 193 (CA) still ships it.

Other permission deltas

User-visible / product deltas by step

189 → 192 (major)

Already documented in the older report; still true after re-decompile:

1. Dexcom G7 stack (com.camdiab.dexcomg7, G7CoreService, login activity).
2. CamAPS Liberty (fxfcl + liberty strings / feature flags).
3. minSdk 31 → 33 (Android 13+).
4. ABI of analyzed artifacts shifts to arm64-v8a for later Play extracts.

192 → 193 (CA XAPK)

1. Package id becomes com.camdiab.fx_alert.mmoll.ca.
2. targetSdk / compileSdk 35 → 36.
3. versionCode 524 → 543, versionName 1.4(193).201.
4. English string already includes the G7 switch logout reminder to note weight and total daily insulin dose (same idea later seen on EU 194).
5. This XAPK language split is en-CA only (no nb split in the downloaded bundle).
6. PairIP still present.
7. Smali feature counts essentially match 192 (G7/Liberty/Dexcom SDK).

193 (CA) → 194 (EU) / 192 → 194

1. EU package id remains com.camdiab.fx_alert.mmoll (194 is not .ca).
2. PairIP fully removed on 194.
3. versionCode 551, versionName 1.4(194).101.
4. targetSdk 36 (same as 193).
5. G7 logout weight/TDD reminder present on 194 (and on this 193 CA build).
6. Norwegian (nb) language split present on the Play extracts used here.

Manifest components (connection-related)

Stable from 192 through 194 (evidence):

• com.dexcom.coresdk.g7txkit.g7core.G7CoreService
• com.dexcom.coresdk.cgmkit.watchcommunication.WatchDataListener (192+)
• foregroundServiceType="connectedDevice" on the connected-device FGS path
• Package query for com.freestylelibre3.app.gb (Libre coexistence / conflict awareness)
• Package query for Health Connect (com.google.android.apps.healthdata)

Obfuscated a.* / d.* / e.* service class names churn between builds. That is rebuild/obfuscation, not evidence of new pump brands.

Native libraries

Stable across 192 to 194: libjnidispatch.so, libnative-lib.so, libsodium.so, libsqlcipher.so.

Hashed / obfuscated .so names change each rebuild (anti-tamper churn), for example different lib????.so triples on 192 vs 193 vs 194. Not treated as a user feature.

189 lacks libsqlcipher.so / libnative-lib.so in the same form (older packaging).

What did not change (192 / 193 / 194)

Recommendation table

Investigation artifacts

Bottom line

189 → 192 is the only large therapy jump in this set (G7 + Liberty + minSdk 33).

193 (APKPure) is a Canadian .ca package already on targetSdk 36, still with PairIP, and already carrying the G7 logout weight/TDD note. It is not the same binary identity as EU 194.

194 is the EU Play maintenance line: PairIP removed, targetSdk 36, feature parity with 192 for G7/Liberty/Libre/pumps.

For flaky sensor/pump links, the APK does not show a 192→194 protocol rewrite; see the connection report for architecture evidence and user-facing reconnect guidance already baked into the app strings.