"rjune11111" wrote:
As a workaround to this issue, we have our companion mobile app send a Home key press via ECP prior to sending the launch command. But we've seen some weird effects, like:
1) Sometimes one home key press doesn't work, but sending two consecutive presses prior to sending the launch command does.
2) When sending two presses followed by a launch, sometimes we see our channel start to launch, then we get returned immediately to the Home screen.
Our mobile app is pipelining the two Home key presses and the launch command on the same connection and waiting for the HTTP responses from each post before performing the next. But it seems as though the Roku might be executing some part of the ECP command processing asynchronously in such a way that the commands can actually be executed in a different order from the send order. Can anyone with knowledge of how ECP commands are processed confirm if that is really the case? Thanks!
I can't confirm the possibility of the asynchronous processing, but I can share that one reason two presses of Home may be required is that if a screensaver is running, the first home press only stops the screensaver, requiring the second press to get back to the home screen. Looking forward to a response from Roku about the rest of your question!
