Roku remotes are sophisticated devices. There are many models, so features vary, but among the possible features are 3.5mm audio output, Bluetooth audio, voice command input, Wi-Fi, infrared, battery charger and other things. Clearly a substantial MCU is present and thus, an RTOS.
The good thing is, it is not written in Brightscript.
That looks neat, the code appears be mostly in C, seems reasonable documented and is hosted on GitHub: https://github.com/rokudev/lt-sdk
>that is already used in our industry-changing Roku remote controls.
Why does a remote control require a RTOS?
Roku remotes are sophisticated devices. There are many models, so features vary, but among the possible features are 3.5mm audio output, Bluetooth audio, voice command input, Wi-Fi, infrared, battery charger and other things. Clearly a substantial MCU is present and thus, an RTOS.
Voice command handling, I would suspect.
Please someone make a Roku remote with a physical keyboard.
This might be possible now. I think the better option is having a hardware device that acts a bridge between a bluetooth keyboard and the Roku.
I wish they would offer the instruction in text as well rather than only in videos. Videos become stale and can't easily be used as a reference.