Package-level declarations
Types
Android DI binding of the shared ServiceRepositoryImpl.
This receiver starts the MeshService on boot if a device was previously connected.
What a boot / package-replaced broadcast should do about the previously selected device.
Single owner of the dynamic conversation shortcuts that link Meshtastic conversations to their notifications.
Desktop has no local-network permission model, so a socket to a LAN address is always permitted.
Decides whether starting MeshService as a foreground service is legal, and which foreground service types it may claim.
Whether the platform currently permits opening a socket to a local-network address.
Encrypted per-device storage for lockdown passphrases.
File-backed encrypted passphrase store for JVM/Desktop.
A BroadcastReceiver that handles "Mark as read" actions from notifications.
Manages the creation and display of all app notifications.
Android foreground service that hosts the Meshtastic mesh radio connection.
Platform-agnostic orchestrator for the mesh service lifecycle.
Platform-agnostic RadioController composition root for any target where the service runs in-process (Desktop, iOS, or Android in single-process mode).
Immutable per-start transport identity. generation is bumped on every transport start (including same-address reconnect) so the SharedRadioInterfaceService and its consumers can discard state retained from a previous transport instance even when the selected address is unchanged.
Handles inline emoji reaction actions from message notifications.
A BroadcastReceiver that handles inline replies from notifications.
Encrypted per-node storage for security key backups.
File-backed encrypted key-backup store for JVM/Desktop, mirroring LockdownPassphraseStoreImpl's desktop counterpart. Uses a PKCS12 KeyStore to hold an AES-256 master key and AES-256-GCM to encrypt each node's key backup, stored as individual .enc files under $MESHTASTIC_DATA_DIR/security_keys/.
Platform-agnostic implementation of ServiceRepository.
Why MeshService is being asked to start.
What the mesh service should do once the selected-device address has settled.
Shared multiplatform connection orchestrator for Meshtastic radios.
Functions
Decides what an unattended reconnect should do, given the persisted device and the current permission.
Decides whether the mesh service keeps running once the address flow has settled.
Starts MeshService as a foreground service so the radio link stays alive for the duration of the connection.