12.6. Preinstalled apps (Boox, GMS, AOSP)¶

The factory app set, catalogued by partition, with an eye to two questions that matter below the app layer: which components reach the network (the telemetry / attack-surface picture), and which apps exist only for hardware this device does not have. This is an inventory, not a reverse of the apps themselves — the code is compiled Java (odex/vdex) and is not decompiled here.

Counts: 65 APKs in system, 27 in system_ext, 32 in product (124 total). Everything here is from the partition listings read with 7z. No code was executed.

12.6.1. The Boox application suite (system)¶

The user-facing Boox software is preinstalled, in /system/app and /system/priv-app (named *-release / k*-release, not onyx* — which is why an onyx-only search misses it). This is the user-facing Boox software, backed by the native Onyx SDK in The Onyx/Boox platform layer:

App dir	Evident function
`knote2-release`	the note / handwriting app (the product’s headline feature)
`kreader2-release`	the e-book reader (NeoReader)
`app-market-release`	the Boox app store
`ksync-release`	cloud sync (BooxDrop / Onyx cloud)
`NeoBrowser`	the built-in web browser
`ai-assistant-release`	the AI assistant
`dict-release`	the dictionary front-end (uses `libonyx_stardict` / `libonyx_mdict`)
`kmail-release` / `kcb-release` / `Kime-release`	mail client / a Boox component / an input-method component
`Gallery-release`, `Music-release`, `VoiceRecorder-release`, `calculator-release`, `Clock-release`	the Onyx-skinned basic apps
`floatingbutton-release`	the on-screen floating navigation ball
`igetshop-release`	a content/shop component
`OnyxLatinIME-release` / `OnyxOtaService`	the soft keyboard and the OTA service (Userspace boot — init, SELinux, A/B updates)
`ProductionTest-release` / `tscalibration-release`	factory production-test and touch-calibration apps

(The purpose of a few — kcb, igetshop — is inferred from the name only.)

12.6.2. Google / GMS (product + system_ext)¶

This is a GMS-certified build: the Google apps live in product with GoogleServicesFramework in system_ext:

Core GMS — GmsCore (Google Play services), Phonesky (Play Store), GoogleServicesFramework; plus webview / chromium_TrichromeLibrary and GoogleExtShared.
Google services — QuickSearchBox, SpeechServicesByGoogle, GoogleCalendarSyncAdapter, GoogleLocationHistory, GoogleRestore, ConfigUpdater, SettingsIntelligence.
AOSP framework overlays (RRO) in product — the DisplayCutoutEmulation*, NavigationBarMode* and TransparentNavigationBar runtime resource overlays.

12.6.3. Network / telemetry surface¶

The components that reach the network by design — relevant to a privacy or attack-surface view — are the two cloud stacks: Google (GmsCore and its satellites: location history, config updater, search, speech, Play) and Onyx (ksync/cloud, app-market, ai-assistant, OTA). Everything else in the app set is local. This is a factual census of what is installed; runtime network traffic was not captured or profiled.

12.6.4. Apps for absent or disabled hardware¶

Consistent with the HAL and SoC-fabric leftovers (Vendor drivers and HALs, Absent and vestigial hardware (reference-base leftovers)), several preinstalled apps target features this device does not expose (android.hardware.{telephony,nfc,location.gps,camera} are declared unavailable, The e-ink software stack (Onyx EPDC)):

Telephony / cellular — TelephonyProvider, ImsRcsService, ImsDataChannelService, WAPPushManager, NtnSatApp (non-terrestrial / satellite), PowerOffAlarm; the modem exists but has no cellular front-end (ADSP and CDSP firmware).
NFC / eSE — Nfc_st (ST NFC) and SecureElement; NFC is declared unavailable (Security and DRM userspace).
Camera — CameraExtensionsProxy, DeviceAsWebcam (no camera, Absent and vestigial hardware (reference-base leftovers)).
Wireless display / WiGig / XR — WfdService (Miracast), WigigTetheringRRO, Xpan, and the xr{cb,vd,wifi}service XR helpers — reference-stack services with no matching hardware use here.

Their presence on this device answers only “what the reference image ships,” not “what this device does” — that question is settled by the unavailable-features declaration plus DTB population.

12.6.5. Provenance¶

Source:: artifacts/notes/ls/{system,system_ext,product}.txt (APK inventory by partition, from 7z listings of the super images), corroborated by the earlier artifacts/notes/onyx_apps.txt recon.
Method:: APK directory names enumerated from the ext4 image listings; function inferred from name and, for the Onyx apps, from the backing native libraries. No APK was decompiled and no code executed.
Cross-refs:: The Onyx/Boox platform layer (the native SDK behind the Boox apps, the version split), Userspace boot — init, SELinux, A/B updates (OTA), Security and DRM userspace (GMS/keystore, eSE), Vendor drivers and HALs + Absent and vestigial hardware (reference-base leftovers) (present-but-disabled hardware), The e-ink software stack (Onyx EPDC) (unavailable-features).