Release 1.1.13: fix app movement and add launcher actions
Keep the displayed app order intact until the grid reuse comparison, and retain selection during rebuilds so D-pad rearranging visibly moves the chosen tile. Add Android-confirmed uninstall for user apps and a foreground-only Wi-Fi/Ethernet shortcut with separate TV-input spacing. Remove the duplicate Personalize footer. Use an explicitly authorized replacement signing identity after loss of the original key. Document the one-time reinstall and preserve signature verification. Add a portable build using ignored signing configuration and regression checks for movement, lifecycle, native network settings, and cancel/confirm uninstall. Validated on the authorized onn 4K Plus: original failing move reproduction now passes, HomeActions/GridReuse/WakeRegression/Navigation instrumentation passes, and native settings/uninstall checks pass. Input-header availability was simulated; physical Ethernet and input switching were not exercised. Restore prior visible settings and Home override; remove the disposable test APK.
This commit is contained in:
parent
2739b278cd
commit
6a08aa242c
24 changed files with 635 additions and 79 deletions
|
|
@ -260,3 +260,21 @@ Both devices passed the final 200 ms accent/coalescing regression, same-color ca
|
|||
Final UI checks verified the removed package is absent on both devices, Settings and Default launcher contain no obsolete integration text/actions, Back stays in Luma, and physical-input controls remain visible only on the TV. The installed APK hashes match the final signed payload. Wallpaper, app art, original spacing, and focus behavior remain intact. Enabled accessibility lists remain Button Mapper only on the onn and null on the TV; the existing Home override remains Off on both. Memory saver remains Off on the onn and On on the TV. The supplied benchmark documents in the repository root were left untouched and untracked.
|
||||
|
||||
After settling with Android settings foreground, both launcher processes consumed zero CPU ticks over five seconds. This round's temporary diagnostic APKs, scripts, on-device reports, locks, and trace files were removed after archiving the reports locally. Both devices were returned to Luma. Android's stock launcher and unrelated apps/settings remain unchanged.
|
||||
|
||||
## 1.1.13 app actions and network shortcut (2026-10-25)
|
||||
|
||||
Built on Windows with JDK 17 and Android SDK/build tools 36, retaining minSdk 26 and targetSdk 34. VersionName 1.1.13 / versionCode 16. The original signing key was missing; the user explicitly authorized a replacement identity and a reinstall. The new RSA certificate SHA-256 is `5982677675475eab76e8aaa52f939b7a563aef69e869b8c5e342ac9e921b12ad`. The key and randomly generated signing password remain under ignored `.tools/`; neither is published. Build scripts now pass signing passwords through environment variables and refuse automatic key replacement.
|
||||
|
||||
On the authorized onn 4K Plus (Android 14/API 34), `scripts/check-app-move.py --adb <adb> --device <serial>` failed against installed 1.1.12: Right after selecting Move in grid left the first three visible apps in the same order. It passes against 1.1.13. The cause was mutating `visibleApps` before `renderApps` captured the displayed order, so the reuse comparison incorrectly skipped rebuilding. The fix swaps a separate order list, and preserves the requested selection while replacing focused children.
|
||||
|
||||
The final `HomeActionsInstrumentation` passed menu entry with remote OK, all four directions, upper/left boundaries, focus remaining on the moving app, Back restoring order, OK saving it across stop/start, and preference restoration. It also passed offline presentation followed by live-network recovery, callback stop/restart, absence of Personalize, and header bounds/D-pad navigation with simulated physical-input availability. The test exits Android touch mode with a remote arrow before requesting focus, so prior tap-based checks do not consume the first OK merely to leave touch mode.
|
||||
|
||||
`GridReuseInstrumentation` passed label-only reuse, focus callbacks, interrupted focus animation, hiding, reordering, and column changes. `WakeRegressionInstrumentation` passed interrupted loading, pause-only recovery, memory trimming, screensaver dismissal, and five stop/start cycles. Normal/rapid `NavigationInstrumentation` passed with zero dropped callbacks; FrameMetrics p95 was 16.37 ms normal and 16.64 ms rapid. These are functional navigation samples on one device, not a performance improvement claim or a comparison with another GPU.
|
||||
|
||||
The real UI check `scripts/check-home-actions.py` opened the native TV network page. Canceling Android's uninstall confirmation preserved the disposable Luma test app; confirming removed it for the current Android user and the resumed Luma library refreshed. The test checks the current user explicitly because the device has a second Android profile. System apps retain app info and do not receive an uninstall action. No user app was uninstalled by these checks.
|
||||
|
||||
Physical Ethernet, captive-portal/limited-internet hardware states, and real physical-input switching were not exercised in this run. Ethernet has its own vector port icon and accessible label selected by Android's active-network transport. Disconnected presentation was injected through the UI update seam without disconnecting wireless ADB. Input availability was simulated only for header bounds and focus; no input hardware or second TV was modified.
|
||||
|
||||
The signing migration required a reinstall of the authorized test device. The visible five-column layout, Kaleido-first ordering, Scenic screensaver with clock, and previously downloaded nature video were restored through Luma UI. Existing versions on the other two devices require a one-time reinstall; signature and update integrity checks remain enabled. Future releases must retain the new key.
|
||||
|
||||
Final cleanup restored the prior enabled-accessibility list (Button Mapper plus Luma's own Home override) and notification permission. Home returned from native Android settings to Luma after its existing accessibility redirect. Android's native Home selection and other launchers were preserved. The diagnostic APK was removed from all profiles, temporary on-device captures were deleted, and the installed APK SHA-256 matched the release manifest. The final Home screenshot was visually checked: the Wi-Fi icon has separate space beside the gear and the five-column app layout is intact.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue