ScreenTinker 6add29bf6a fix(player): auto-relaunch after OTA self-update (#96) ... After the OTA installs, PACKAGE_REPLACED kills the old process and nothing brought MainActivity back, so updating screens dropped to the launcher (the 1.9.0 fleet bug). Add a MY_PACKAGE_REPLACED receiver that relaunches via a shared Relauncher cascade (extracted from BootReceiver so boot + post-update share one path): 1. overlay-direct startActivity (SYSTEM_ALERT_WINDOW) - legal on all versions when granted 2. full-screen-intent notification - auto-launches <14; on 14+ (USE_FULL_SCREEN_INTENT revoked) degrades to a VISIBLE, tappable "tap to resume" prompt - fail loud, never a silent dark screen Emulator-proven on Android 16: MY_PACKAGE_REPLACED -> Relauncher[update] -> overlay-direct (BAL_ALLOW_SAW_PERMISSION) -> MainActivity on the new version. Accessibility re-binds across the package-replace (Service connected fires post-relaunch), so sequential OTAs keep their auto-confirm. Unattended OTA requires accessibility (auto-confirm the install) + overlay (relaunch); the setup wizard grants both. A device where they're skipped degrades to the visible prompt. Closes #96. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>		2026-06-12 22:34:32 -05:00
..
src	fix(player): auto-relaunch after OTA self-update (#96)	2026-06-12 22:34:32 -05:00
build.gradle.kts	chore(release): v1.9.0	2026-06-11 21:11:31 -05:00
proguard-rules.pro	Initial open source release	2026-04-08 12:14:53 -05:00