The row limit stops eating collections (#30).
The setting means one thing, written in the code itself: "it cuts what will be REQUESTED over the network — seven rows must cost seven GETs, otherwise the setting saves pixels and not work." But it was being applied a second time to the assembled list, where it also counted rows that request nothing: your collections, and the fixed rows like Continue Watching. Collections are added at the end, so they were the first to fall — and connecting Trakt brought the cut forward.
Now only rows with an add-on catalog behind them count against it. Measured on a C9 with 169 folders in 9 groups: the home went from 8 rows to 19, still 60.0 fps with zero janks.
If that is more rows than you want, the setting now does what it says — lower it and you lower the number of catalogs fetched.
Side effect worth noting: tests/home.sh passes for the first time in weeks. It asserted 17 rows against a limit of 16 — sixteen catalogs plus one collection — and had been waiting on exactly this decision.
Also in: collection tiles can animate from the account's focus GIF on Tizen. Untested on a real Samsung — it does nothing on webOS, which has no GIF animation support at all. Reports welcome.
LG webOS 4.x and 5+ — space.nuvio.native.legacy_1.0.34_arm.ipk
Samsung Tizen — NuvioTV-1.0.34-tizen.wgt, unsigned; sign it for your own TV before installing.