CTO bad architecture decisions brings enormous tension within company

So first let’s clarify the topic.

The Consequences of the CTO’s Choice (by AI):

  • A Hardware Dead-End: They locked themselves into a specific system-on-chip (SoC) family that was hardwired for Android 7. Because of this, they cannot simply push an over-the-air update to a newer Android or Linux base without bricking the physical hardware.
  • The RW800 Bandaid: Instead of admitting the mistake and building a clean, modern Linux-based OS from scratch for their customers, their solution was to sell you another box (the RW800) to act as a hardware bandaid for their outdated software.

Now the question is why and how using stupid android bundle against pure linux os which can easily scale, being updated without braking changes?
Did Rose realy push big screen topic as TTM objective against more mature approach to build lasting and robust platform?
Few tears back I demanded them to make at least smb2 and they did. The question is, how do you publish a product with 20 year legacy protocol abandoned and shut off from anyone in last 15 years. It brings kind of mindset behind…

I’m still waiting for years on smb3, logarithmic volume (rs520), native connect ifaces(tidal and others, etc.).

Looks like moving to Lumin x2 is my only choice left. Don’t mind the price as it sounds levels above any Rose product, not as visually appealing though.

Ok, so you’re saying a lot of things that need a bit more information…

What SoC did they use that is hardwired to a specific version of Android?

I agree that to many existing customers… the RW800 is a bandaid, yet… and here’s the thing…
There’s actually a market for it. Take a look at the WiiM that looks like a hockey puck.