Follow-up to v1.0.11, and it comes this fast on purpose — one of the fixes in v1.0.11 made this symptom more visible, so the two belong together.
The home no longer loads one catalog, swaps it, then settles
Reported by the owner rather than through an issue: the home would load a catalog, replace it with another, and only then settle into the right order.
The cause was one flag doing four jobs. The sync cycle collapsed four different changes into a single "rebuild" signal, and their costs are not comparable:
| change | what it affects | what it used to trigger |
|---|---|---|
| add-ons | what to fetch | full network cycle — correct |
| Trakt link | what to fetch | full network cycle — correct |
| catalog order | only which rows exist, and in what sequence | full network cycle — wrong |
| collections | only which rows exist, and in what sequence | full network cycle — wrong |
The last two do not change a single item, yet they re-ran Trakt, every manifest and every catalog. And because the second cycle publishes a different set of rows from the first, the swap showed up on screen.
v1.0.11 widened that gap. Its collections fix means the first cycle and the second now disagree more, not less: on the first pass the account's collections have not arrived yet, so their catalogs become loose rows; on the second they have. Shipping that without this would have made the flicker worse.
Rows are windows into the item list, so reordering, filtering or changing the limit touches no items — and needs no network. There is now a rows-only republish, and order/collection changes use it. The synthesized rows stay put: "Continue Watching" and the friends feed are not add-on catalogs and do not take part in the ordering, otherwise the merge would push them to the end as unknown keys.
Measured on an OLED65C9 after deploying: the discovery cycle now runs once instead of twice, with remontagem dispensada in place of the second pass. 60.0 fps, zero janks.
One cost, stated rather than left to be discovered
The v1.0.11 collections fix added a lookup that scans the collection folders and each folder's sources, and it runs per candidate catalog in two loops. With 169 folders that is thousands of comparisons per pass. It did not show up in the measurement, but it is a nested scan on a hot path and it is the first place to look if start-up ever gets slower.
Installing
LG webOS 4.x — space.nuvio.native.legacy_1.0.12_arm.ipk. Samsung Tizen 5.5+ — NuvioTV-1.0.12-tizen.wgt, unsigned; sign it with your own TV's DUID (steps in the v1.0.7 notes).
Everything in v1.0.11 is included — #16, #18 and #19.
Verification
This one was run on a TV: deployed to an OLED65C9 and the cycle count read from its own log. The three fixes carried over from v1.0.11 still have not been watched on a device.
Unofficial, and not affiliated with NuvioMedia.