mirror of
https://github.com/meshtastic/Meshtastic-Android.git
synced 2026-05-30 09:37:13 -04:00
End-to-end plumbing for LockdownAuth.max_session_seconds (per-boot uptime cap on the unlocked session; 0 = unlimited). Wire: - CommandSenderImpl populates LockdownAuth.max_session_seconds in the outbound admin packet (clamped non-negative). Coordinator + persistence: - LockdownCoordinator.submitPassphrase gains optional maxSessionSeconds (default 0); persisted alongside boots/hours and replayed by auto-unlock so cached sessions keep the operator's cap on reconnect. - StoredPassphrase gains a new field with a default of 0 so existing call sites stay source-compatible. - LockdownPassphraseStore (Android EncryptedSharedPreferences impl): reads/writes the new field with a `_maxSessionSeconds` key suffix; legacy entries decode to 0. - LockdownPassphraseStore (JVM file-backed impl): bumps the per-entry on-disk serialization from 3-line to 4-line; legacy 3-line entries still decode (treated as maxSessionSeconds=0). IPC + radio plumbing: - IMeshService.sendLockdownUnlock AIDL gains a 4th int parameter. - MeshService stub, MeshActionHandler, RadioController interface, and both impls (AndroidRadioControllerImpl, DirectRadioControllerImpl) thread the field through. - FakeIMeshService, FakeRadioController, FakeLockdownCoordinator updated to match. UI: - LockdownDialog adds a single optional "Session cap (minutes)" field below the boots/hours row. Operators enter minutes for ergonomics; the dialog multiplies by 60 before passing to the coordinator. Blank or 0 = unlimited (firmware default). - UIViewModel.sendLockdownUnlock gains the new param with default 0. - New string resources: lockdown_session_minutes, lockdown_session_minutes_help. Strings re-sorted via scripts/sort-strings.py. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
:core:data
Overview
The :core:data module implements the Repository pattern, serving as the primary data source for ViewModels in feature modules. It orchestrates data flow between the local database (core:database), remote services, and network repositories.
Key Components
1. Repositories
NodeRepository: High-level access to node information and mesh state.MeshLogRepository: Access to historical logs and diagnostics.FirmwareReleaseRepository: Manages the discovery and retrieval of firmware updates.
2. Data Sources
Internal components that handle raw data fetching from APIs or disk.
Module dependency graph
graph TB
:core:data[data]:::kmp-library
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;