Add capability-based TV input button and switching
This commit is contained in:
parent
22a2130563
commit
5f035d909a
13 changed files with 374 additions and 11 deletions
|
|
@ -1 +1 @@
|
|||
Reduces unnecessary cinematic background work while moving quickly through apps. App focus feedback stays immediate; the background follows the final selected color after a short pause. Preserves smooth scrolling, artwork, and wake recovery. Tested on both the integrated TV and onn, with the same behavior across devices.
|
||||
Adds a TV-input button beside Settings on devices that expose physical inputs. Choose an HDMI or other supported input with the remote. The button stays hidden on streamers without inputs. Detects Android capabilities automatically, with no device-specific configuration.
|
||||
|
|
|
|||
|
|
@ -48,7 +48,7 @@ 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 (1.1.9): 2,753,622 bytes. SHA-256: `bf03db00b66fd1aa2eaf6ed6c6b65da222a32725e9549133e37890a758fd27df`.
|
||||
Final APK (1.1.10): 2,761,885 bytes. SHA-256: `d0bdcb6cecc43ecd6652d9c3da6b704f6f4586f07c2273e8694f31b6a96e0f9a`.
|
||||
|
||||
## Updater regression — October 18, 2026
|
||||
|
||||
|
|
@ -162,3 +162,21 @@ The new scheduling regression passed on both devices in both rendering modes. Th
|
|||
|
||||
|
||||
The final signed 1.1.9 build was installed on both devices. Screenshots confirm the wallpaper, app banners, focus appearance, and original layout. After settling with Android settings foreground, both launcher UIs and the onn Home helper consumed zero CPU ticks over five seconds. Home/Back returned/stayed in Luma on the onn; the TV retained its original disabled Home override. The onn's original accessibility list was restored after instrumentation, including Button Mapper. Both diagnostic APKs and the round's temporary on-device reports/scripts were removed; Projectivy remains installed and enabled on both devices. Both devices were returned to Luma.
|
||||
|
||||
|
||||
## Capability-based TV input button — October 19, 2026
|
||||
|
||||
Version 1.1.10 adds a focusable input icon immediately left of Settings. It is shown only when Android's TvInputManager exposes visible physical passthrough inputs. The code uses public input types/metadata, custom labels, hidden-input settings, and connection states; it contains no model/manufacturer/IP checks. CEC children whose physical parent is already listed are omitted. Tuners and virtual/app-only inputs do not create the button. Discovery runs on the existing worker, and input-change events are coalesced. The listener and pending refresh callback are removed on pause; stale results are discarded. No new Android permissions are requested.
|
||||
|
||||
On the onn, the system exposed no physical input entries and UIAutomator confirmed the header contains Settings with no input button. The existing header spacing remains intact. On the integrated TV, UIAutomator and screenshots confirmed the input icon, focus colors, D-pad Up to Settings then Left to inputs, and a picker with HDMI 1–4 plus Cancel. The connected CEC device is not duplicated as a fifth port.
|
||||
|
||||
The implementation discovers an exported/accessible standard channel-view handler through its MIME filter, excluding generic content browsers. Where no such handler is available, a private input activity uses Android's TvView and the selected passthrough URI. The TV did not expose a native channel-view activity to the active user during testing, so the TvView fallback was exercised without enabling/reinstalling any system app. The viewer requests media audio focus while visible, resets its input session and abandons audio focus on pause, and returns to Luma on Back.
|
||||
|
||||
Selecting HDMI 1 created a real TV-input session for Luma's UID with the expected physical input ID. The video-available callback hid the loading text. Selecting HDMI 2 created the corresponding port session and displayed “No signal · Press Back to return.” HDMI 1 was then selected again; its video-available callback fired, and Back returned to the launcher with artwork restored. TV-input dumps after returning confirmed Luma's session was released. The pre-existing provider session was retained. Live HDMI pixels were not available in the ADB screen capture; verification used input session IDs, video callback state, and the UI hierarchy. Audio was not listened to remotely.
|
||||
|
||||
The enhanced wake regression passed on both devices, including interrupted-load recovery, pause-only image reuse, partial-grid recovery, memory trimming, screensaver dismissal, nonblank bounded backgrounds, five stop/start cycles, and an assertion that the TV-input listener is removed when paused. This change makes no rendering-performance claim and does not change image resolution or the app grid layout.
|
||||
|
||||
The platform interfaces are documented in [TvInputManager](https://developer.android.com/reference/android/media/tv/TvInputManager), [TvInputInfo](https://developer.android.com/reference/android/media/tv/TvInputInfo), and [TvView](https://developer.android.com/reference/android/media/tv/TvView).
|
||||
|
||||
|
||||
Final 1.1.10 package/version checks passed on both devices, with the input button visible only on the TV. After settling with Android settings foreground, both UIs and the onn Home helper consumed zero CPU ticks over five seconds. The diagnostic APKs and temporary on-device files were removed. The onn's original Home/accessibility service list was restored after instrumentation; Home returned from Android settings, and Back stayed in Luma. The TV's existing Home override remains off. Projectivy remains installed/enabled on both devices, and both devices were returned to Luma. Raw local checks are in ignored `output/performance/input-switching/`.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue