52809f6ed4
So centralcloud-ops can SEE that this phone is alive and the SMS relay
is working. Server side (POST /api/devices/heartbeat + /devices LiveView)
landed in centralcloud_ops commit 6a7f22e.
DeviceHeartbeatWorker
Periodic CoroutineWorker (15min, the WorkManager floor) that POSTs
sms_relay state + device_state to /api/devices/heartbeat.
sms_relay summary: enabled, whitelist_size, last_forward_at,
failure_count_24h.
device_state: battery_level, is_charging, network_type,
low_power_mode, dnd_active, ringer_mode.
DND read via NotificationManager.currentInterruptionFilter — works
on API 23+ without notification policy access permission.
Skips (Result.success) when relay isn't configured yet — no point
spamming the server, but the schedule stays alive so it picks up
automatically as soon as config lands.
SmsRelayInit
One-liner bootstrap. Call from Application.onCreate when your
managed-config / branding WIP merges:
SmsRelayInit.start(this)
Idempotent (WorkManager KEEP policy) so safe across cold starts.
SmsRelayPreferences (extended)
Tracks lastForwardAtMs (epoch-ms, set by SmsForwardWorker on 200)
and failureCount24h (rolling, reset by heartbeat on success).
SmsForwardWorker (extended)
On 200 → record lastForwardAtMs. On 4xx/5xx/exception → bump
failureCount24h. Heartbeat then reports both up to the server,
which renders them on the /devices LiveView.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
||
|---|---|---|
| .. | ||
| schemas | ||
| src | ||
| build.gradle | ||