Coalesce passing focus accents to reduce background rendering
This commit is contained in:
parent
25ea43bea7
commit
22a2130563
11 changed files with 199 additions and 14 deletions
|
|
@ -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.8): 2,753,622 bytes. SHA-256: `9f4fecf5162c897e9614b9fe4b3af37989bd10d3959d9278f1314e4e0630b80b`.
|
||||
Final APK (1.1.9): 2,753,622 bytes. SHA-256: `bf03db00b66fd1aa2eaf6ed6c6b65da222a32725e9549133e37890a758fd27df`.
|
||||
|
||||
## Updater regression — October 18, 2026
|
||||
|
||||
|
|
@ -137,3 +137,28 @@ Wake regression passed on both devices in both rendering modes: cold launch, int
|
|||
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.
|
||||
|
||||
|
||||
## Projectivy review and focus-color coalescing — October 19, 2026
|
||||
|
||||
Reviewed the official [Projectivy repository](https://github.com/spocky/miproja1), its [4.70 release notes](https://github.com/spocky/miproja1/releases/tag/4.70), [4.72 release notes](https://github.com/spocky/miproja1/releases/tag/4.72), and public wallpaper-provider documentation. The main repository exposes configuration files, releases, and an issue tracker, rather than the launcher's core rendering implementation. There is no public renderer source there to inspect or port. Findings here come from the documented release behavior and Luma's own source/measurements, not assumptions about Projectivy's internals.
|
||||
|
||||
Applicable lessons from those notes include bounded image caches and content counts, image downsampling, limiting expensive wallpaper/color work, and stopping listeners when backgrounded. The published 50 MB image-cache cap does not establish an in-memory budget; it was not copied into Luma's RAM limits. Luma already bounds images/caches, samples wallpaper, debounces Plex artwork, and cancels background work. This review motivated testing fewer unnecessary accent transitions during rapid focus changes. It does not establish that Projectivy uses this particular implementation.
|
||||
|
||||
Version 1.1.9 retains immediate app-tile focus scale/glow/labels, but coalesces app accent changes until 160 ms without another different color. It then uses the existing 280 ms background transition. Reduced motion and initial rendering apply immediately. A single reusable callback retains only the latest color, is removed on pause/screensaver/stop, and restores the selected color when resumed. Both devices use the same code and behavior. Bitmap resolution, image quality, and the spacious layout are unchanged.
|
||||
|
||||
Fresh same-device 1.1.8 versus candidate comparisons used the native-input 42-key NavigationInstrumentation workload described above, with no shell input process per key. The test ran normal navigation (350 ms between keys), then rapid navigation (80 ms between keys), on each device's existing grid:
|
||||
|
||||
| Device / pace | 1.1.8 median / p90 | 1.1.9 median / p90 | Missed deadlines, baseline → optimized |
|
||||
| --- | ---: | ---: | ---: |
|
||||
| onn, normal | 10.02 / 13.29 ms | 9.90 / 12.92 ms | 5/800 → 10/737 |
|
||||
| onn, rapid | 11.02 / 13.61 ms | 10.76 / 14.02 ms | 1/255 → 1/252 |
|
||||
| TV, normal | 16.52 / 24.34 ms | 12.53 / 24.30 ms | 18/853 → 18/799 |
|
||||
| TV, rapid | 24.37 / 25.07 ms | 20.64 / 21.56 ms | 25/214 → 21/229 |
|
||||
|
||||
On the TV, rapid-navigation median/p90 duration improved about 15%/14%; GPU p90 fell from 20.62 to 17.29 ms. On the onn, frame durations remained roughly level and the normal-navigation missed-deadline count increased in this short sample. This is a reduction in unnecessary background work and an improvement on the TV, not a consistent frame-time improvement on every device. TV rapid frames still exceed a 16.7 ms budget. All captures had zero dropped FrameMetrics callbacks. These samples are not an endurance test or a hardware ranking; raw results are under ignored `output/performance/round3/`.
|
||||
|
||||
The new scheduling regression passed on both devices in both rendering modes. Three colors 60 ms apart produced exactly one final full-color composition (or reused the existing Memory-saver textures), retained the final selected color, canceled pending work on pause, restored on resume, and applied reduced-motion changes immediately. The complete wake regression also passed on both devices in both modes: interrupted loads, partial-grid recovery, memory trimming, image reuse, nonblank bounded scenes, release on stop, screensaver dismissal, five stop/start cycles, and runtime renderer switching. Diagnostic preference changes were restored.
|
||||
|
||||
|
||||
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.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue