Complete implementation of the Android Auto / AAOS car module: Phase 1 - Setup: - Version catalog entries (car-app 1.9.0-alpha01) - Module build.gradle.kts with android-library, flavors, koin - AndroidManifest with MESSAGING category, minCarApiLevel 8 - AAOS automotive_app_desc.xml - Car-specific string resources - ProGuard keep rules Phase 2 - Foundation: - MeshtasticCarAppService (CarAppService entry point) - MeshtasticCarSession (session lifecycle, Crashlytics tagging) - FeatureCarModule (Koin DI with ComponentScan) - HomeScreen (TabTemplate: Messages + Nodes) - CrashlyticsCarTagger, TemplateBuilders helpers - CarUiModels (presentation state models) Phase 3 - Messaging (MVP): - MessagingScreen (300ms debounced invalidation, max 10 conversations) - ConversationScreen (voice reply, read-aloud, max 5 messages) - FuzzyNodeNameResolver (LCS-based voice name matching) - MessageFilter (emoji/admin exclusion, 237-byte limit) - BatchMessageLoader (50 unread on session start) - CarNotificationManager (MessagingStyle + reply/mark-read) Phase 4 - Emergency: - EmergencyHandler (flow collection, alert state, audio tone) - EmergencySpotlightBuilder (alert rows for messaging screen) - EmergencySessionWiring (lifecycle attach/detach) Phase 5 - Nodes: - NodeDashboardScreen (sorted list, signal/battery, topology header) - NodeDetailScreen (PaneTemplate with Message action) Phase 6 - Channels: - ChannelChipBuilder (ActionStrip with unread badges) Phase 8 - Status Panel: - MeshStatusPanel (connection, node count, last msg time) - MeshStatusSessionWiring (Flow-based lifecycle) Phase 9 - Voice: - CarTtsEngine (TTS read-aloud) - VoiceDmCoordinator (fuzzy resolve + voice DM flow) Phase 10 - Polish: - OnboardingScreen (no channels configured state) - DisconnectedScreen (BLE disconnect graceful degradation) - ProGuard consumer rules Verified: spotlessApply ✓ detekt ✓ compileGoogleDebugKotlin ✓ assembleGoogleDebug ✓ Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
:androidApp
Overview
The :androidApp module is the entry point for the Meshtastic Android application. It orchestrates the various feature modules, manages global state, and provides the main UI shell.
Key Components
1. MainActivity & Main.kt
The single Activity of the application. It hosts the shared MeshtasticNavDisplay navigation shell and manages the root UI structure (Navigation Bar, Rail, etc.).
2. MeshService
The core background service that manages long-running communication with the mesh radio. While it is declared in the :androidApp manifest for system visibility, its implementation resides in the :core:service module. It runs as a Foreground Service to ensure reliable communication even when the app is in the background.
3. Koin Application
MeshUtilApplication is the Koin entry point, providing the global dependency injection container.
Architecture
The module primarily serves as a "glue" layer, connecting:
core:*modules for shared logic.feature:*modules for specific user-facing screens.
Module dependency graph
graph TB
:androidApp[androidApp]:::android-application
:androidApp -.-> :core:ble
:androidApp -.-> :core:common
:androidApp -.-> :core:data
:androidApp -.-> :core:database
:androidApp -.-> :core:datastore
:androidApp -.-> :core:di
:androidApp -.-> :core:domain
:androidApp -.-> :core:model
:androidApp -.-> :core:navigation
:androidApp -.-> :core:network
:androidApp -.-> :core:nfc
:androidApp -.-> :core:prefs
:androidApp -.-> :core:proto
:androidApp -.-> :core:service
:androidApp -.-> :core:resources
:androidApp -.-> :core:ui
:androidApp -.-> :core:barcode
:androidApp -.-> :core:takserver
:androidApp -.-> :feature:intro
:androidApp -.-> :feature:messaging
:androidApp -.-> :feature:connections
:androidApp -.-> :feature:map
:androidApp -.-> :feature:node
:androidApp -.-> :feature:settings
:androidApp -.-> :feature:docs
:androidApp -.-> :feature:firmware
:androidApp -.-> :feature:wifi-provision
:androidApp -.-> :feature:widget
classDef android-application fill:#CAFFBF,stroke:#000,stroke-width:2px,color:#000;
classDef android-application-compose fill:#CAFFBF,stroke:#000,stroke-width:2px,color:#000;
classDef compose-desktop-application fill:#CAFFBF,stroke:#000,stroke-width:2px,color:#000;
classDef android-feature fill:#FFD6A5,stroke:#000,stroke-width:2px,color:#000;
classDef android-library fill:#9BF6FF,stroke:#000,stroke-width:2px,color:#000;
classDef android-library-compose fill:#9BF6FF,stroke:#000,stroke-width:2px,color:#000;
classDef android-test fill:#A0C4FF,stroke:#000,stroke-width:2px,color:#000;
classDef jvm-library fill:#BDB2FF,stroke:#000,stroke-width:2px,color:#000;
classDef kmp-feature fill:#FFD6A5,stroke:#000,stroke-width:2px,color:#000;
classDef kmp-library-compose fill:#FFC1CC,stroke:#000,stroke-width:2px,color:#000;
classDef kmp-library fill:#FFC1CC,stroke:#000,stroke-width:2px,color:#000;
classDef unknown fill:#FFADAD,stroke:#000,stroke-width:2px,color:#000;