Add scheduled TV updates from Forgejo
Check a commit-pinned manifest on a configurable schedule, notify about newer versions, verify downloaded APKs, and hand off installation to Android. Generate the feed with each signed build. Include the wake artwork recovery fix and on-device lifecycle and updater regression tests.
This commit is contained in:
parent
f5f1c0928f
commit
0d1a11d943
23 changed files with 1493 additions and 51 deletions
1
docs/UPDATE_NOTES.md
Normal file
1
docs/UPDATE_NOTES.md
Normal file
|
|
@ -0,0 +1 @@
|
|||
Adds scheduled update checks, TV notifications, and downloading/installing Luma updates directly from Settings. Includes the fix for missing app images and wallpaper after TV wake. Your appearance, screensaver, app order, and Home routing settings are preserved.
|
||||
|
|
@ -15,7 +15,17 @@ Validated on the user’s onn. 4K Plus Streaming device over ADB, October 17, 20
|
|||
- Projectivy fallback stays open when explicitly selected through its app tile or Settings. Back stays on Luma; from lower rows it returns to the first row. Home returns to Luma. Projectivy remains installed and enabled; only its competing “Override current launcher” preference is off. Its accessibility service and Button Mapper’s service are retained.
|
||||
- Luma’s override Off control removes only its own accessibility service. Re-enabling through Android’s actual Accessibility settings was verified. The service is system-bound in a separate `tv.luma.launcher:home` process. No view-content retrieval capability is requested.
|
||||
|
||||
## Performance
|
||||
## Wake regression — October 18, 2026
|
||||
|
||||
The original blank state was captured before sending input or restarting Luma. Android reported the existing activity as resumed; tiles were displaying their text placeholders and the alpine bitmap was absent. The recorded wake sequence included start/resume, a brief pause, and then resume without another start. Image work scheduled only from `onStart()` could be skipped or discarded while paused, with no retry when the activity resumed.
|
||||
|
||||
Version 1.0.1 moves restoration to `onResume()`, retries interrupted app discovery, and reloads missing wallpaper, app icons, and optional media artwork. Pausing invalidates stale asynchronous results; stopping still releases image references and caches. A pause-only resume retains existing tile views and decoded app images. This follows Android's documented [pause/resume lifecycle](https://developer.android.com/guide/components/activities/activity-lifecycle).
|
||||
|
||||
A separate same-signature instrumentation APK reproduces the interrupted-load sequence deterministically. The installed 1.0.0 build failed with missing artwork; the fixed build passed the same case, recovery of a partially rendered grid whose icon jobs were interrupted, pause-only memory trimming, reuse of existing loaded tiles/bitmaps, and five complete stop/start cycles. No preferences are rewritten by these tests. The temporary diagnostic APK was removed afterward.
|
||||
|
||||
One real sleep/wake cycle also passed screenshot checks for the alpine wallpaper and Plex banner without pressing Home or restarting the launcher. A subsequent automated wake was interrupted by HDMI standby (`mLastSleepReason=hdmi`), and One Touch Play timed out; no CEC settings were changed. The user turned the TV on again for the final screen check. The final screenshot shows the alpine wallpaper and app banners restored, with the user’s five-column layout preserved. Both the launcher and Home helper recorded zero CPU ticks over a ten-second background sample. Home returned correctly from Android settings and restored the UI after its cached process was explicitly reclaimed. The Home helper was re-bound after instrumentation cleanup, preserving the original enabled services. This is not an overnight endurance test.
|
||||
|
||||
## October 17 performance baseline
|
||||
|
||||
Final device sample with the Home override enabled:
|
||||
|
||||
|
|
@ -38,4 +48,10 @@ No launcher application was disabled or uninstalled. Screensaver selection at th
|
|||
|
||||
Build validation uses aapt2, javac, D8, zipalign, and apksigner signature verification. There are no third-party runtime libraries.
|
||||
|
||||
Final APK: 2,737,238 bytes. SHA-256: `46ca53681ff7fc34651402a8e4e806aa0fde7f7e49516aa94d8342ee762472a3`.
|
||||
Final APK (1.1.1): 2,749,526 bytes. SHA-256: `b145da41c95c927562f41d6052443723e377c7c40e775c078be0aa41ffefd19b`.
|
||||
|
||||
## Updater regression — October 18, 2026
|
||||
|
||||
The same-signature updater test ran against the installed 1.1.0 bootstrap and a newer signed 1.1.1 APK. It passed persisted daily network scheduling, Off cancellation, branch-to-commit pinning, a real APK download and certificate/package/version/checksum verification, and private provider read access. It rejected an incorrect checksum, another signing key, a different package, a mismatched version code, oversized metadata declarations, and public HTTP sources. The provider rejected write requests and unknown paths. The current version was not offered as an update. Test preferences were restored afterward.
|
||||
|
||||
The production default is the public HTTPS Forgejo feed in `output/update.json`, generated with the APK by `scripts/build.sh`. It requires no credentials on the TV. Native installer and unknown-source permission activities resolve on the onn. Android 14 device.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue