One holder's claim on a RadioOperation. Releasing a lease affects only that holder.
Identity matters: two concurrent claims on the same operation produce two distinct leases, so a late release from an abandoned holder cannot retire a live one.
Tracks which RadioOperations are in flight, so the rest of the app can keep out of their way.
Three consumers, which is why one lock replaced the single-purpose FirmwareMaintenanceLock it grew out of: SharedRadioInterfaceService reads suppressesTransport to stay off the device, MeshService reads holders to refuse to stop itself and to hold a wake lock, and the service notification reads it to say what is running.
Holders are tracked as individual leases rather than a set of operation types. The set was wrong: a caller that cancels a job and immediately starts a replacement — which FirmwareUpdateViewModel does, without joining — lets the cancelled job's finally run after the replacement has acquired, and a shared entry would be retired out from under the live holder. Two holders of the same operation are now independent.
Lives in :core:common because the parties sit in modules that cannot see each other: the flows that take an operation are in :feature:firmware and :feature:discovery, and the code that must respect it is in :core:service.
Process-local by design. A process death drops every lease, which is correct — nothing is in flight any more — but it means this narrows the window in which an interrupted flash can strand a device rather than closing it.
The distinct operations currently in flight.
Every live lease, keyed by lease id. Emits on every acquire and release.
True while an operation that needs the transport off the device is in flight.
Takes operation and returns the lease that holds it. Each call is a distinct holder.
Releases lease. Idempotent, and null-safe so a caller can release a hold it may never have taken.
Releases lease. Idempotent, and null-safe so a caller can release a hold it may never have taken.
Releasing a stale lease is harmless: its id is already gone, and other holders of the same operation keep theirs.
A USB firmware-maintenance sequence (factory erase).
A factory erase leaves the device enumerating as a bare CDC port with no Meshtastic protocol on it. The serial transport will happily bind to that — its device lookup falls back to whatever probed device it can find, not just the saved address — and the environmental-recovery listeners re-enter transport startup whenever Bluetooth or the network flips. Both would claim the port the maintenance flow needs.
Marks a USB firmware-maintenance sequence as in flight, so the radio transport does not fight it for the device.
A factory erase leaves the device enumerating as a bare CDC port with no Meshtastic protocol on it. The serial transport will happily bind to that — its device lookup falls back to whatever probed device it can find, not just the saved address — and the environmental-recovery listeners re-enter transport startup whenever Bluetooth or the network flips. Both would claim the port the maintenance flow needs.
Lives in :core:common because the two parties sit in modules that cannot see each other: the flow that takes the lock is in :feature:firmware, and the code that must respect it is in :core:service.
The consequence of ignoring the lock is bounded rather than destructive — a transport that claims the port asserts DTR itself, which happens to unblock the erase — but it makes the flow's own signal unreliable, and a mesh handshake against erase firmware is noise nobody needs to debug.
An OTA/DFU flash.
Does not suppress the transport: the flow already frees it by deselecting the device (radioController.setDeviceAddress("n")), and the post-flash verification deliberately reconnects the radio, so suppression would block the very step it is meant to protect.
Releases the lock. Must run even on failure, so callers use try/finally.
A long-running operation that owns the radio and must not be interrupted halfway.
suppressesTransport is per-operation rather than blanket because the operations genuinely differ: a USB factory erase needs the transport to stay off the port, while a discovery scan needs the transport to keep running.
A USB firmware-maintenance sequence (factory erase).
An OTA/DFU flash.
A Local Mesh Discovery preset sweep. Needs the transport, so it must never suppress it.
Returns the enum constant of this type with the specified name. The string must match exactly an identifier used to declare an enum constant in this type. (Extraneous whitespace characters are not permitted.)
Returns an array containing the constants of this enum type, in the order they're declared.
Returns the enum constant of this type with the specified name. The string must match exactly an identifier used to declare an enum constant in this type. (Extraneous whitespace characters are not permitted.)
if this enum type has no constant with the specified name
Marks a USB firmware-maintenance sequence as in flight, so the radio transport does not fight it for the device.
One holder's claim on a RadioOperation. Releasing a lease affects only that holder.
A long-running operation that owns the radio and must not be interrupted halfway.
Tracks which RadioOperations are in flight, so the rest of the app can keep out of their way.
Minutes to dwell on each preset by default.
Deliberately short. The dwell is per preset, so this multiplies: at the previous default of 15 a three-preset sweep ran for 45 minutes, which outlived the wake lock that keeps the CPU up for it. Longer dwells hear more, so every previous option is still offered in the picker — this only changes what an untouched first scan costs.
Minutes to dwell on each preset by default.
Reactive persistence for received Mesh Beacon invitations. Records are opaque, self-describing strings (see MeshBeaconOffer.encode) so this prefs layer stays free of proto/model types.
Reactive persistence for received Mesh Beacon invitations. Records are opaque, self-describing strings (see MeshBeaconOffer.encode) so this prefs layer stays free of proto/model types.
Returns the last-built service state notification, or an immediately available application-label fallback. This method is used by MeshService for android.app.Service.startForeground, so it must not wait for Compose Multiplatform resource loading.
Returns the last-built service state notification, or an immediately available application-label fallback. This method is used by MeshService for android.app.Service.startForeground, so it must not wait for Compose Multiplatform resource loading.
Manages the creation and display of all app notifications.
This class centralizes notification logic, including channel creation, builder configuration, and displaying notifications for various events like new messages, alerts, and service status changes.
Manages the creation and display of all app notifications.
This class centralizes notification logic, including channel creation, builder configuration, and displaying notifications for various events like new messages, alerts, and service status changes.
Creates all necessary notification channels on devices running Android O or newer. This should be called once when the service is created.
Deliberately blocking (Main-thread, one-time cost): the orchestrator posts the foreground-service notification synchronously right after this returns, so channels must exist before then — do not lazy-gate this into the suspend notify paths. Blocking getString is safe here only because Main is not a Dispatchers.Default worker.
Creates all necessary notification channels on devices running Android O or newer. This should be called once when the service is created.
Deliberately blocking (Main-thread, one-time cost): the orchestrator posts the foreground-service notification synchronously right after this returns, so channels must exist before then — do not lazy-gate this into the suspend notify paths. Blocking getString is safe here only because Main is not a Dispatchers.Default worker.
Re-posts the conversation silently after an inline reply, so the notification updates in place with the sent reply appended (the read context becomes historic, the reply is the visible latest message) instead of disappearing. Re-posting under the same (tag, id) is also what resolves the RemoteInput spinner.
Re-posts the conversation silently after an inline reply, so the notification updates in place with the sent reply appended (the read context becomes historic, the reply is the visible latest message) instead of disappearing. Re-posting under the same (tag, id) is also what resolves the RemoteInput spinner.
Android foreground service that hosts the Meshtastic mesh radio connection.
Acts as the lifecycle anchor for the MeshServiceOrchestrator, which manages all manager initialization and connection state.
Android foreground service that hosts the Meshtastic mesh radio connection.
Acts as the lifecycle anchor for the MeshServiceOrchestrator, which manages all manager initialization and connection state.
No device is selected, but a long-running radio operation is in flight and needs this process alive.
The firmware update flow deselects the device (setDeviceAddress("n")) to free the transport before it flashes. That deselect is what makes this case real: without it the service would stop roughly five seconds into a flash that runs for minutes, taking the foreground notification and the wake lock with it.
What the mesh service should do once the selected-device address has settled.
Returns the enum constant of this type with the specified name. The string must match exactly an identifier used to declare an enum constant in this type. (Extraneous whitespace characters are not permitted.)
Returns an array containing the constants of this enum type, in the order they're declared.
Returns the enum constant of this type with the specified name. The string must match exactly an identifier used to declare an enum constant in this type. (Extraneous whitespace characters are not permitted.)
if this enum type has no constant with the specified name
Shared multiplatform connection orchestrator for Meshtastic radios.
Manages the connection lifecycle (connect, active, disconnect, reconnect loop), device address state flows, and hardware state observability (BLE/Network toggles). Delegates the actual raw byte transport mapping to a platform-specific RadioTransportFactory.
Shared multiplatform connection orchestrator for Meshtastic radios.
Manages the connection lifecycle (connect, active, disconnect, reconnect loop), device address state flows, and hardware state observability (BLE/Network toggles). Delegates the actual raw byte transport mapping to a platform-specific RadioTransportFactory.
Manages the creation and display of all app notifications.
Manages the creation and display of all app notifications.
What the mesh service should do once the selected-device address has settled.
Shared multiplatform connection orchestrator for Meshtastic radios.
Shared multiplatform connection orchestrator for Meshtastic radios.
Decides whether the mesh service keeps running once the address flow has settled.
Decides whether the mesh service keeps running once the address flow has settled.
Pure and platform-agnostic so the gate is unit-testable without standing up a Service, in the same shape as bootReconnectDecision.
Deliberately not consulted by the service's other two teardown paths. A held operation must not keep alive a service that failed dependency injection or could not enter the foreground — in the latter case ActivityManager has already armed the pending-start watchdog, and refusing to stop would turn a recoverable refusal into a process kill.
Reusable Robolectric helpers for driving Android Bluetooth bonding logic in androidHostTest source sets.
These let a unit test exercise the real AndroidBluetoothRepository.bond() (and any future BLE bonding code) without an emulator and without a production seam. They rely on two Robolectric behaviors (verified against Robolectric 4.16.x):
android.bluetooth.BluetoothAdapter.getRemoteDevice caches the returned BluetoothDevice by address in a static map, so the shadow configured here is the same instance production code reads when it calls getRemoteDevice(mac) internally.
ShadowBluetoothDevice.createBond calls checkForBluetoothConnectPermission() first, so tests must call grantBluetoothConnectPermission or createBond() throws SecurityException instead of returning a value.
Isolation note: because the device cache is static and survives across tests in the same JVM, give each test a distinct MAC so bond-state cannot bleed between tests.
Reusable Robolectric helpers for driving Android Bluetooth bonding logic in androidHostTest source sets.
These let a unit test exercise the real AndroidBluetoothRepository.bond() (and any future BLE bonding code) without an emulator and without a production seam. They rely on two Robolectric behaviors (verified against Robolectric 4.16.x):
android.bluetooth.BluetoothAdapter.getRemoteDevice caches the returned BluetoothDevice by address in a static map, so the shadow configured here is the same instance production code reads when it calls getRemoteDevice(mac) internally.
ShadowBluetoothDevice.createBond calls checkForBluetoothConnectPermission() first, so tests must call grantBluetoothConnectPermission or createBond() throws SecurityException instead of returning a value.
Isolation note: because the device cache is static and survives across tests in the same JVM, give each test a distinct MAC so bond-state cannot bleed between tests.
A comprehensive and flexible dialog component for the Meshtastic application.
Modifier for the dialog.
The title text of the dialog.
The title string resource of the dialog.
Optional plain text message.
Optional string resource message.
Optional color for the plain text message; Color.Unspecified uses the default text color.
Optional HTML formatted message.
Optional leading icon.
Optional custom composable content for the body.
Text for the confirmation button.
String resource for the confirmation button.
Callback for the confirmation button.
Text for the dismiss button.
String resource for the dismiss button.
Callback for when the dialog is dismissed or the dismiss button is clicked.
If provided, displays a list of buttons instead of the standard confirm/dismiss actions.
Whether the dialog can be dismissed by clicking outside or pressing back.
A comprehensive and flexible dialog component for the Meshtastic application.
Modifier for the dialog.
The title text of the dialog.
The title string resource of the dialog.
Optional plain text message.
Optional string resource message.
Optional color for the plain text message; Color.Unspecified uses the default text color.
Optional HTML formatted message.
Optional leading icon.
Optional custom composable content for the body.
Text for the confirmation button.
String resource for the confirmation button.
Callback for the confirmation button.
Text for the dismiss button.
String resource for the dismiss button.
Callback for when the dialog is dismissed or the dismiss button is clicked.
If provided, displays a list of buttons instead of the standard confirm/dismiss actions.
Whether the dialog can be dismissed by clicking outside or pressing back.
Shared "icon + label" button used throughout the Connections screen. Centralises M3 sizing conventions (ButtonDefaults.IconSize, ButtonDefaults.IconSpacing, and the variant-appropriate *WithIconContentPadding) so every scan / add / empty-state affordance renders identically.
accessibility label for the leading icon. Defaults to null because the visible text usually describes the action; override when the icon carries information the text does not.
Shared "icon + label" button used throughout the Connections screen. Centralises M3 sizing conventions (ButtonDefaults.IconSize, ButtonDefaults.IconSpacing, and the variant-appropriate *WithIconContentPadding) so every scan / add / empty-state affordance renders identically.
accessibility label for the leading icon. Defaults to null because the visible text usually describes the action; override when the icon carries information the text does not.
Shared "icon + label" button used throughout the Connections screen. Centralises M3 sizing conventions (ButtonDefaults.IconSize, ButtonDefaults.IconSpacing, and the variant-appropriate *WithIconContentPadding) so every scan / add / empty-state affordance renders identically.
Shared "icon + label" button used throughout the Connections screen. Centralises M3 sizing conventions (ButtonDefaults.IconSize, ButtonDefaults.IconSpacing, and the variant-appropriate *WithIconContentPadding) so every scan / add / empty-state affordance renders identically.
Core scan engine for Local Mesh Discovery.
Cycles through a queue of LoRa presets, dwells on each for a configured duration while collecting packets, then persists aggregated results via DiscoveryDao.
Core scan engine for Local Mesh Discovery.
Cycles through a queue of LoRa presets, dwells on each for a configured duration while collecting packets, then persists aggregated results via DiscoveryDao.
Watches reconnects for persisted discovery sessions left without a confirmed home-radio restore. Recovery is device-bound and skipped while this engine owns an active scan.
Watches reconnects for persisted discovery sessions left without a confirmed home-radio restore. Recovery is device-bound and skipped while this engine owns an active scan.
Starts a discovery scan across the given targets — public presets and/or beacon-advertised custom channels. (Distinct name from the ChannelOption overload: both would erase to the same JVM signature otherwise.)
The scan queue (ScanTarget).
How long to listen on each target.
Starts a discovery scan across the given targets — public presets and/or beacon-advertised custom channels. (Distinct name from the ChannelOption overload: both would erase to the same JVM signature otherwise.)
The scan queue (ScanTarget).
How long to listen on each target.
Convenience overload: scan a list of public presets (each becomes a preset ScanTarget labelled by name).
Convenience overload: scan a list of public presets (each becomes a preset ScanTarget labelled by name).
Core scan engine for Local Mesh Discovery.
Core scan engine for Local Mesh Discovery.
Default FirmwareUpdateManager that routes to the correct handler based on the current connection type and device architecture. All handlers are KMP-ready and work on Android, Desktop, and (future) iOS.
Default FirmwareUpdateManager that routes to the correct handler based on the current connection type and device architecture. All handlers are KMP-ready and work on Android, Desktop, and (future) iOS.
Recover a device stranded in nRF DFU/bootloader mode after an interrupted update, while the app is disconnected.
Unlike startUpdate, routing does not depend on the (absent) live connection — this always drives the BLE DFU handler, which derives the MAC+1 bootloader address from address and tolerates a device that is already in DFU mode.
The device's normal mesh BLE address (transport prefix stripped).
Recover a device stranded in nRF DFU/bootloader mode after an interrupted update, while the app is disconnected.
Unlike startUpdate, routing does not depend on the (absent) live connection — this always drives the BLE DFU handler, which derives the MAC+1 bootloader address from address and tolerates a device that is already in DFU mode.
The device's normal mesh BLE address (transport prefix stripped).
Begin a firmware update for the connected device.
A FirmwareArtifact that should be cleaned up by the caller, or null if the update was not started.
The firmware release to install.
The target device's hardware descriptor.
The bare device address (MAC, IP, or serial path) with the transport prefix stripped.
Callback invoked as the update progresses through FirmwareUpdateState stages.
Optional pre-selected firmware file URI (for "update from file" flows).
Begin a firmware update for the connected device.
A FirmwareArtifact that should be cleaned up by the caller, or null if the update was not started.
The firmware release to install.
The target device's hardware descriptor.
The bare device address (MAC, IP, or serial path) with the transport prefix stripped.
Callback invoked as the update progresses through FirmwareUpdateState stages.
Optional pre-selected firmware file URI (for "update from file" flows).
ViewModel driving the firmware update screen. Coordinates release checking, file retrieval, transport-specific update execution, and post-update device verification.
ViewModel driving the firmware update screen. Coordinates release checking, file retrieval, transport-specific update execution, and post-update device verification.
The version-row easter egg also unlocks the nightly preview channel, like the web flasher's konami code.
The version-row easter egg also unlocks the nightly preview channel, like the web flasher's konami code.
Resumes a maintenance sequence once the user has pointed at the device's UF2 volume.
Distinct from saveDfuFile because the URI kinds differ: this takes a tree URI, which grants the sibling access needed to read INFO_UF2.TXT and vet the volume before writing. Each pass re-picks, because the device re-enumerates between passes and the previous grant no longer refers to the mounted volume.
Resumes a maintenance sequence once the user has pointed at the device's UF2 volume.
Distinct from saveDfuFile because the URI kinds differ: this takes a tree URI, which grants the sibling access needed to read INFO_UF2.TXT and vet the volume before writing. Each pass re-picks, because the device re-enumerates between passes and the previous grant no longer refers to the mounted volume.
Default FirmwareUpdateManager that routes to the correct handler based on the current connection type and device architecture. All handlers are KMP-ready and work on Android, Desktop, and (future) iOS.
Default FirmwareUpdateManager that routes to the correct handler based on the current connection type and device architecture. All handlers are KMP-ready and work on Android, Desktop, and (future) iOS.
ViewModel driving the firmware update screen. Coordinates release checking, file retrieval, transport-specific update execution, and post-update device verification.
ViewModel driving the firmware update screen. Coordinates release checking, file retrieval, transport-specific update execution, and post-update device verification.