"squirreltown" wrote:
Been two months now, Any news on fixing this bug?
"squirreltown" wrote:
Hello Roku?
"RokuJoel" wrote:
Can folks who are experiencing this dropbox us some example channels we can side-load that demonstrate this bug, so we can work out the cause? You can send it to me in a private message or email jbraverman at roku dot com.
Thanks
- Joel
"squirreltown" wrote:
I'd like to say thanks for replying - but with all due respect, it might be more effective to just say whatever it is you are trying to say. Other than the appearance of irritation at being asked a question, I'm really not sure what that reply is supposed to mean.
"squirreltown" wrote:Has Joel responded to the PM or email you sent him when you provided the sample code? If not, perhaps another PM/email to remind him wouldn't hurt. Can you share a minimal amount of sample code that can reliably trigger the issue with the other developers here on the forum so we can compare, comment, confirm and/or make suggestions? Even if it's straight out of the sdk examples, it would still be helpful.
Thank you theEndless
Since I started this thread its probably not surprising that I sent my channel in the day it was requested too. Google Analytics tells me it was run at Roku. I then waited 8 weeks & two firmware upgrades before asking about it here on the developer board. And finally the problem is happening in areas where I did not create any code, as in when selecting an item from a grid screen, or simply exiting a grid screen to return to the poster screen, whatever code is in those areas is straight out of the SDK, and worked fine before 5.1.
I have a very simple channel and would like it to not look like someone is jiggling the HDMI cable when just going from one screen to another, the way it worked before 5.1. I'm glad you aren't experiencing that, but I am and there is nowhere else to ask.
"squirreltown" wrote:
Thanks gonzotek. No I never got a response, but since I could tell it was "in the system" at Roku I am happy to stay out of the way and let folks do their jobs. I think i waited a perfectly respectful amount of time before asking about it.
As far as posting code here, its really not the kind of problem that lends itself to that or I might have done it already. If someone is curious I would be happy to send them the install code and directions for seeing the problem, although since its clearly not a wide-spread occurrence I suspect my hardware (2XS's) might be part of it, but I don't have the experience to actually know that.
"RokuJoel" wrote:
FYI, I believe we have a fix checked in for this issue for an upcoming firmware release.
- Joel