@RomanMtz wrote:
Mrbungle's decision is his own and it worked out for him.. but should it really be labeled as an official solution?
Mrbungle is the one who accepted it as the solution, for others to more easily see the conclusion to his problem (45 days later).
Maybe if Roku offered an alternative solution? In a timely manner? All we ever see here is "give me the details, I'll pass it on." It's a one-way street. At the rate official solutions are arriving, and new updates are breaking more things -- never knowing if something is considered a bug or an enhancement, and if it's a bug, if it's considered a priority, or you (the customer) is left to die on the vine -- I think Mr B's solution is the best anyone can realistically hope for. Consider how a disruptive update was pushed out just 5 days before Christmas (when Roku knew employees would be taking time off for the next couple weeks). What kind of solutions should we expect from a company like that? (I'm not trying to sound snarky. I just think it's logical. If Roku didn't like Mr. B's solution, maybe they'd step their support up a notch. But, *everything* we see says they really don't care.). Mr. B's the smart one. He cut his losses, moved on with his life, instead of being entangled with a company that doesn't care about their customers.
"People are often amazed at how much we’ve done with the number of engineers we’ve got." (Roku CEO Anthony Wood, Austin Statesman, Oct 4, 2019). "Amazed" is one way of putting it.
