"NewManLiving" wrote:
Nice remote app ! Works perfect, better than the remote itself - And there is no extra set of commands sent to the device. So the problem is apparently with the new Roku App. Just tested the new ROKU app again and the problem still exists.
So since only the new ROKU app is exhibiting the problem and no other app or remote, then probably is more likely the app itself
Ok, i scrutinized the behavior with both apps and can confirm that Roku's own iOS app (v3.3.1) causes the player to receive 1 extra Up and 1 Down event on release of long-pressed <</>> button. On the other hand this is not the case with a previous version (v3.2.2) of the iOS app that i tried, nor the Android (3.3.1) or Windows phone (2.1) versions of "Roku". So the (d)effect was introduced either in November by 3.3.1 or in October by 3.3.0.
Here is how it looks in Roku "home" screen: using the "Roku" iOS app, stay in the left (text) menu, press&hold [>>] - the menu starts rolling continuously. Now release [>>] and see how it suddenly yanks 1 screen ahead and then stops. Try that with a physical remote or another app to compare.
And here is what events i receive (72 is Marmalade key code for >> but i bet timing situation looks the same in BrSc):
pressed 72 <-- here we press >>
.
. <-- nothing happens here, long wait holding >> down
.
released 72 <-- here >> was released, 3 rapid events received
pressed 72
released 72
Now i don't know what/why ECP commands the 3.3.1 "Roku" app sends to get this weirdness - but i know what my app does and that seems to work well, it's described here
viewtopic.php?f=34&t=85535#p506285
