I added a feature to our app to detect "long presses" - when the user is holding down a directional key, the focus keeps moving until the key is released. Problem is that sometimes the roku does not detect that the key has been released and the focus keeps moving indefinitely until the user presses a new key. This seems to happen more with older-style remotes and with roku stick devices. I'm trying to figure out if there's another way to detect that the user is not holding down the key any longer.Is there a way to detect the current state of the remote (pressed / not pressed) other than listening for key release events?tyvmia

I have run into that issue as well. I use it to cheat when playing a space game I'm writing. 😄 At least for now. The remote sends the keyup code, but it doesn't mean the roku receives it, so if you hit a button, then aim the remote away when you release it, often that never gets received. The only thing I know of would be to cancel any key holds on any new keypress. So if they hold down the right key, and you never receive that key up, but you receive a new key, of course the right button has been released since only one key at a time works in bs.

That's a tough one. Maybe ifDeviceInfo - TimeSinceLastKeypress() could be helpful in some way?I dunno, maybe it will be rare enough to just live with it. I don't know of any way to detect the current remote status.

"BradC" wrote:The remote sends the keyup code, but it doesn't mean the roku receives it, so if you hit a button, then aim the remote away when you release it, often that never gets received.Actually that's not how the IR remotes work. While holding down a button, the remote repeatedly sends a key code. When you release the button, it stops sending the code. The Roku software generates a release event when it detects that it is no longer receiving the key code. So it shouldn't be possible to miss a release event simply by pointing the remote away when you release the button.IR remotes are basically simple flashlights. There's no way to query the current state, or in fact to send any information or commands from the Roku to the remote.--Mark

"RokuMarkn" wrote:Actually that's not how the IR remotes work. While holding down a button, the remote repeatedly sends a key code. When you release the button, it stops sending the code. The Roku software generates a release event when it detects that it is no longer receiving the key code. So it shouldn't be possible to miss a release event simply by pointing the remote away when you release the button.IR remotes are basically simple flashlights. There's no way to query the current state, or in fact to send any information or commands from the Roku to the remote.--MarkGood point. Well, I sure can't say why it works, but it does work. Seems to only work on the roku TV if that matters. I just made a test case channel that does nothing but dump the events to console, and absolutely can't get it to happen there. So far every down has an up. I've clearly gone insane because I know this was happening, but I also understand why it's impossible.

"RokuMarkn" wrote:"BradC" wrote:The remote sends the keyup code, but it doesn't mean the roku receives it, so if you hit a button, then aim the remote away when you release it, often that never gets received.Actually that's not how the IR remotes work. While holding down a button, the remote repeatedly sends a key code. When you release the button, it stops sending the code. The Roku software generates a release event when it detects that it is no longer receiving the key code. So it shouldn't be possible to miss a release event simply by pointing the remote away when you release the button.IR remotes are basically simple flashlights. There's no way to query the current state, or in fact to send any information or commands from the Roku to the remote.--MarkCan you be more specific? Perhaps explain the different types of remotes in use: Using the 2D I do not see repeated codes, just the keypress when pressed and the keypress + 100 when released. I use a flag to keep tract of the last key pressed to perform continuous behavior. But I have experienced a "lost" key up event from time-to-time. You can set a timer to get around this if its that big a deal but I am curious about your statement. I just tested it again using ROKU 4 and its packaged remote, and I only get the down and release codes, no matter how long I hold the button down.

Detecting Keypress Release

35 Replies

joetesta
Roku Guru
10 years ago
In the code I'm working on now, i'm seeing this happening to me somewhat frequently on Roku 3 & Roku 4 to the point where it's becoming a quality issue. It's like the roku is busy doing something else and doesn't notice the user released the key, and then keeps scrolling forever until the user clicks something else. I wish there was a way to poll the current keystate (hey remote, are you *really* still being pressed?)
NewManLiving
Visitor
10 years ago
I rarely have the problem and use keypress logic extensively. What I do notice is more on the stick which I already mentioned and with the ROKU 4 and it's remote, especially when the battery is getting low (which is about every three to four weeks on mine). I stopped using the ROKU 4 remote altogether and took out the batteries. Rule of thumb - never buy the first release of anything. But other than that I have no real issues with keypress release
joetesta
Roku Guru
10 years ago
ah thanks! Must be because I'm using the Roku 4 for R&D I'm seeing this more.
Komag
Roku Guru
10 years ago
My Roku stick with wifi remote has the rubber direction/ok pad
EnTerr
Roku Guru
10 years ago
Here is an alternative theory - maybe it's the component that has the issue, not the remote?

This is what happened to me today in Roku's Google "Play Movies", so bizarre i figured i'll film it:
https://www.youtube.com/watch?v=BetjLZ8MXkw

Basically the "My Movies" grid screen can get stuck infinitely scrolling, which is so weird because it seems to be a regular roGridScreen sub-type. There is no hidden remote. This all happened using the remote held, using left/right arrows made it stuck scrolling and repeat use of the arrows won't un-stuck it. The << / >> stop it but... only temporarily. It is a repeatable bug, not a one-off. WTF...

Forum Discussion

Detecting Keypress Release

35 Replies

Recent Discussions

Missed USD payment

Check your PayPal revenue payments

Does it really take 3 months for ROKU support to help you?

Is pixel-level writing supported?

Feed not being updated