@Bachelard
If using the list and one of the items solves the issue of apps not opening/closing to Home is "ridiculous", then yes, its "ridiculous".
However, the countless number of users who have used it successfully might disagree.
Just to be very clear, that entire list was created, culled and tweaked based on known effective multiply-reported/confirmed workarounds/solutions.
Not every item works for every model or configuration (hence the ordered list), but all items have worked for many people, many times.
Nor does the list always work - there are some devices/configurations for which the entire list is ineffective.
Also to be clear, the list wouldnt be necessary if Roku coded RokuOS more capably/competently, and tested it more extensively before release. Unfortunately, there is little to no pre-release testing because Roku (like many companies now) has decided to use its installed consumer device base as its QA process (this is why they use limited/staggered rollouts for firmware releases...)
The last 3 major version upgrades (9.3/9.4/10) have been particularly bad, to put it charitably - everything from killing wireless connectivity (especially for 2.4Ghz models) effectively bricking them, to causing massive widespread app load crashing for just about every major app/service (hence the list), to rendering remotes inoperable/re-programming the TV control (hence a different list post), to broken video/audio playback modes for local streamed media (unresolved), to broken default display modes (including the forever regressive HDCP errors), and on and on.
Whoever manages RokuOS development (and from my understanding there isnt much - they have a flat mostly non-hierarchical employee organization) doesnt seem to have much care or concern for the overall UI/UX (let alone the technical requirements for specific hardware interfaces), and it has gotten worse/more inconsistent over time (the repeat regression bugs are truly staggering for each OS release).
They need to get a very technically competent OS programmer/architect/developer/MANAGER to come in and effectively ride roughshod with the riot act in hand over the entire RokuOS department - they are currently way too tolerant of godawful programming and way too reliant on consumer-based QA to fix it post-release.
Considering they now have around 2000 employees (up from 700 in 2017), they need to expend more employee capital on RokuOS development/management.
So yes, its a "systemic problem" - a RokuOS development, programming, and management one.
