txDisabled
+ Whether the device is configured not to transmit. Null-safe against the pre-config LocalConfig so the notice cannot flash before the device's config arrives.
diff --git a/api/core/testing/org.meshtastic.core.testing/-robolectric-ble-bonding/index.html b/api/core/testing/org.meshtastic.core.testing/-robolectric-ble-bonding/index.html index 05a39fafc3..465f6f34cd 100644 --- a/api/core/testing/org.meshtastic.core.testing/-robolectric-ble-bonding/index.html +++ b/api/core/testing/org.meshtastic.core.testing/-robolectric-ble-bonding/index.html @@ -95,7 +95,7 @@
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.
Single source of truth for the UI's "connection status" pill/banner. Derived from connectionState, ServiceRepository.connectionProgress, and regionUnset; kept here rather than in the composable so the mapping is observable and testable.
The ConnectionStatus.RECONNECTING case is signalled by the WiFi/TCP handshake watchdog writing ServiceRepository.RECONNECTING_PROGRESS_TEXT to ServiceRepository.connectionProgress immediately before its recovery sibling transitions to ConnectionState.Disconnected. See ServiceRepository.RECONNECTING_PROGRESS_TEXT for the cross-track contract.
Single source of truth for the UI's "connection status" pill/banner. Derived from connectionState, ServiceRepository.connectionProgress, and regionUnset; kept here rather than in the composable so the mapping is observable and testable.
The ConnectionStatus.RECONNECTING case is signalled by the WiFi/TCP handshake watchdog writing ServiceRepository.RECONNECTING_PROGRESS_TEXT to ServiceRepository.connectionProgress immediately before its recovery sibling transitions to ConnectionState.Disconnected. See ServiceRepository.RECONNECTING_PROGRESS_TEXT for the cross-track contract.
Whether the device is configured not to transmit. Null-safe against the pre-config LocalConfig so the notice cannot flash before the device's config arrives.
Composable screen for managing device connections (BLE, TCP, USB). It displays connection status.
Composable screen for managing device connections (BLE, TCP, USB). It displays connection status.