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.
Pretty sure they don't have gyroscopes and accelerometers anymore, but they did early on. It was basically a Wii Mote and I played a ton of Angry Birds on my TV.
On my rokus, I am able to use my phone as a remote via the roku app. This includes typing on mobile via my phone's keyboard. Makes logging into things much easier.
That looks neat, the code appears be mostly in C, seems reasonable documented and is hosted on GitHub: https://github.com/rokudev/lt-sdk
The good thing is, it is not written in Brightscript.
Brightscript could have been worse!
And much, much better, as well
>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.
Pretty sure they don't have gyroscopes and accelerometers anymore, but they did early on. It was basically a Wii Mote and I played a ton of Angry Birds on my TV.
Voice command handling, I would suspect.
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.
Please someone make a Roku remote with a physical keyboard.
On my rokus, I am able to use my phone as a remote via the roku app. This includes typing on mobile via my phone's keyboard. Makes logging into things much easier.
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.