greenart7c3 7ddcb26dc4 Reduce background battery drain from subscription tick and Tor retries ...

The ConnectivityService safety-net tick woke the CPU every 30 seconds for
the whole life of the process (~2,880 wakeups/day) even though every real
state change already refreshes the subscriptions explicitly and Quartz
replays subscriptions on reconnect. Raise the tick to 5 minutes; it now
only covers genuinely missed paths.

Bound the built-in Tor startup: when Tor cannot bootstrap (airplane mode,
censored network), runMigrations previously stop/start cycled the whole
daemon every ~2 minutes forever, burning battery and data until the
network came back. After 5 attempts (120s bootstrap window each, backoff
3/6/12/24s) the daemon is stopped, a non-ongoing Failed notification with
the Restart action is shown, and relay connections stay down instead of
failing endlessly through a dead SOCKS proxy.

Relay connections now recover automatically when Tor comes back: a new
rising-edge observer on TorManager.isRunning refreshes subscriptions
(covers manual restarts mid-session, which previously left relays
disconnected), and a network change retries Tor when it had given up.

2026-09-14 08:39:31 -03:00

..

java/com/greenart7c3/nostrsigner/service

Reduce background battery drain from subscription tick and Tor retries

2026-09-14 08:39:31 -03:00

AndroidManifest.xml

Fix offline SecurityException from WorkManager network tracking

2026-09-09 08:32:19 -03:00