This one was measured on a TV, not reasoned about — and the measurement is what found it.
The catalog was rebuilding itself every five minutes
Left a title page open on an OLED65C9 and watched for sixteen minutes. The log:
- four discovery cycles — one at start-up and three periodic;
- three lines of
[addons] 7 vindos da contawith the identical list each time; - three catalog summaries, byte for byte the same.
Those three periodic cycles re-fetched Trakt, every add-on manifest and every catalog, to arrive exactly where they already were.
The cause was one line: the sync applied the add-on list and flagged a rebuild because the response had arrived, not because anything had changed. The list is pulled every five minutes and comes back the same. The list is now compared before it is replaced, and only a real change triggers a rebuild.
It was also silently undoing an earlier fix, on a loop. Replacing the list clears each add-on's sondado flag and the id read from its manifest — and that id is the key the account's collections use to find their own add-on's URL, which was the root cause of #10. So every five minutes the collections lost their addresses until the next manifest read. The #10 fix was being undone and redone indefinitely.
After the change, on the same TV: one cycle in seven minutes instead of four in sixteen, with the periodic sync still running normally (progress and settings still pulled) — the catalog simply stops being rebuilt. 60.0 fps, zero janks.
#16 confirmed fixed, on the device
The same run is the proof for the title-page bug from v1.0.11. Over those sixteen minutes the log shows the repair firing six times:
[detail] catalogo remontou: tt31195136 saiu de 15 para 10
[detail] catalogo remontou: tt31195136 saiu de 10 para 15
Each of those is a moment where the page would previously have become a different film. Screenshots taken sixteen minutes apart are the same frame: the page never moved. And with the rebuild above gone, the trigger is largely gone too — the periodic republish was what pulled the ground out from under that screen.
Installing
LG webOS 4.x — space.nuvio.native.legacy_1.0.13_arm.ipk. Samsung Tizen 5.5+ — NuvioTV-1.0.13-tizen.wgt, unsigned; sign it with your own TV's DUID (steps in the v1.0.7 notes).
Includes everything from v1.0.11 (#16, #18, #19) and v1.0.12.
Verification
Run on an OLED65C9: cycle counts, the repair firing, and the before/after screenshots all come from that device. The Tizen build compiles clean but was not run — there is no Samsung on the bench.
Unofficial, and not affiliated with NuvioMedia.