Optimize portable tile rendering and add optional memory saver
This commit is contained in:
parent
5bb15fa69e
commit
25ea43bea7
18 changed files with 918 additions and 63 deletions
|
|
@ -1 +1 @@
|
|||
Further improves focus animation performance with a small shared soft-shadow texture. Keeps the cinematic background, app-colored glow, focus enlargement, and smooth scrolling. Includes the integrated-TV background rendering optimization.
|
||||
Improves app-tile rendering and reduces the shared focus-shadow texture to one quarter of its previous size. Adds an optional Memory saver setting for background colors. All devices use the same rendering default, with no model-specific pathways. Keeps cinematic artwork, focus effects, and smooth scrolling. Tested on the onn box and integrated TV.
|
||||
|
|
|
|||
|
|
@ -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.7): 2,753,622 bytes. SHA-256: `b15cd4abad3cb55eab29916fdd61b4702e665d163d3225779b04b7dee302ee23`.
|
||||
Final APK (1.1.8): 2,753,622 bytes. SHA-256: `9f4fecf5162c897e9614b9fe4b3af37989bd10d3959d9278f1314e4e0630b80b`.
|
||||
|
||||
## Updater regression — October 18, 2026
|
||||
|
||||
|
|
@ -108,3 +108,32 @@ The same TV-local focus benchmark with the new shadow enabled produced **640 fra
|
|||
The enhanced wake regression passed with the cached-shadow build, including checking that its animation stops on leaving Home, nonblank bounded backgrounds, interrupted-load recovery, screensaver dismissal, and five stop/start cycles. An initial attempt began while the TV was asleep; later ADB disconnects interrupted streamed test reports. Running the diagnostic locally with saved output while the TV was awake completed successfully. The temporary diagnostic APK is removed after verification.
|
||||
|
||||
The broader 42-key D-pad sequence on 1.1.7 recorded 861 frames, 16 missed deadlines (1.86%), median 14 ms, 90th percentile 25 ms, and 95th percentile 25 ms. This is roughly level with the 1.1.6 sample (1.41%, 13/24/26 ms); the cached shadow's isolated-focus consistency gain did not produce a measurable improvement to the whole navigation workload in these samples. It is not presented as a new overall performance leap. Screenshots confirm the soft app-colored shadow, scale/outline, wallpaper, and spacing remain visible. The remaining navigation time is primarily GPU/compositing work; main-thread draw/traversal was already sub-millisecond in the sampled 1.1.6 trace. The onn comparison remains 1.1.5, rather than claiming a same-version hardware comparison.
|
||||
|
||||
|
||||
## Portable tile optimization — October 19, 2026
|
||||
|
||||
Version 1.1.8 uses the same default rendering path and settings on every device. No model, manufacturer, product, IP address, or device-name selection is used. App banners are marked opaque after composition over an opaque background. Rounded app artwork uses a cached bitmap shader and matrix, avoiding repeated path clipping and redundant background draws. Transparent artwork retains its underfill and media progress bars retain their rounded clipping. The shared focus shadow is now ALPHA_8: 23,424 bytes instead of 93,696 bytes. Focus enlargement, color glow, 160 ms focus transitions, background transitions, and smooth scrolling remain enabled.
|
||||
|
||||
The onn and integrated TV were first brought to the same released 1.1.7 baseline. The following comparisons use a same-signature diagnostic with real D-pad key injection, Android FrameMetrics, and identical 42-key sequences across the app rows. Normal navigation waits 350 ms between keys; rapid navigation waits 80 ms. This avoids the extra process/VM startup caused by invoking Android's shell `input` command for every key. Metrics were collected locally on each device, rather than timing the ADB connection.
|
||||
|
||||
| Device / pace | 1.1.7 median / p90 | 1.1.8 median / p90 | Missed deadlines, baseline → optimized |
|
||||
| --- | ---: | ---: | ---: |
|
||||
| onn, normal | 12.09 / 15.08 ms | 10.49 / 13.30 ms | 8/798 → 7/801 |
|
||||
| onn, rapid | 11.60 / 14.89 ms | 10.76 / 13.63 ms | 3/254 → 1/255 |
|
||||
| TV, normal | 25.03 / 26.75 ms | 13.28 / 24.24 ms | 32/828 → 17/864 |
|
||||
| TV, rapid | 25.36 / 26.91 ms | 24.39 / 25.17 ms | 28/212 → 25/210 |
|
||||
|
||||
The TV improves substantially in normal-navigation median duration, but its rapid-navigation GPU cost remains greater than the onn's. These are short samples of each device's existing app grid, not proof of identical hardware performance or perfect 60 fps. FrameMetrics total duration and deadlines are reported directly; they should not be mixed with earlier gfxinfo histogram values or an isolated first-six-tile benchmark. All samples above had zero dropped FrameMetrics callbacks. Raw reports are saved locally under `output/performance/round2/` and are ignored by Git.
|
||||
|
||||
**Settings → Appearance → Memory saver** is available on every device and is **off by default**. It separates accent tint into a bounded alpha mask, retaining the same composed background when only the selected app's color changes. This reduces repeated full-image allocation/uploads, with a different GPU tradeoff. Earlier shell-workload onn PSS samples were 132,417 KiB for 1.1.7, 109,413 KiB for optimized tiles with the default background, and 67,578 KiB with Memory saver and optimized tiles. PSS is variable, includes framework/graphics overhead, and is not a guaranteed reduction on every device.
|
||||
|
||||
With Memory saver enabled, the same native-input test measured normal/rapid p90 durations of 13.03/14.88 ms on the onn and 24.44/24.81 ms on the TV. Missed-deadline counts were 12/681 and 1/259 on the onn, and 20/732 and 27/208 on the TV. It is not consistently faster than the default, so it is an explicit preference rather than an automatic device classification. Both modes work on both devices. GPU-specific single-pass shader experiments were discarded after they regressed performance.
|
||||
|
||||
GPU PixelCopy checks passed on both devices for wide opaque banners, portrait center cropping, transparent artwork, media progress bars, and rounded corners. Sampled tile interior differences against the previous drawing implementation were at most 1/255 per color channel. Clearing a tile image also clears its cached shader reference. Memory-saver backgrounds matched the original composited colors within 2/255, and artwork crossfades at 25%, 50%, and 75% matched within 3/255. Accent changes reused the existing background and mask.
|
||||
|
||||
Wake regression passed on both devices in both rendering modes: cold launch, interrupted loading/pause/resume, memory trim, existing-tile reuse, partial-grid recovery, bounded nonblank backgrounds, texture/queue release on stop, screensaver dismissal, and five stop/start cycles. Memory-saver checks also verified loading the saved preference and switching back and forth at runtime. Temporary preference changes were restored by the test runners. The first tile-comparison test had an uninitialized reference bitmap in the diagnostic overlay; fixing that test setup allowed the comparisons to pass without changing production rendering.
|
||||
|
||||
|
||||
The final signed 1.1.8 APK was installed on both devices and retains the previous certificate. Final screenshots show the original five-column spacious layout, mountain background, rounded banners, and app-colored focused shadow. Temporary diagnostic packages were uninstalled. The onn Home helper was re-bound after instrumentation using its original enabled-service list, retaining Button Mapper; Home from Android settings and repeated Back returned/stayed in Luma. The TV's Home override remains off with its original empty service list. Projectivy remains installed and enabled.
|
||||
|
||||
With Android settings foreground, the onn UI and Home helper each consumed zero CPU ticks over five seconds. The TV initially consumed five CPU ticks over five seconds after installation; a later five-second sample after settling consumed zero. These short samples show idle behavior after pending work completes, rather than establishing overnight endurance. Both devices were returned to Luma after verification.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue