Roku Developer Program

Join our online forum to talk to Roku developers and fellow channel creators. Ask questions, share tips with the community, and find helpful resources.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
renojim
Community Streaming Expert

Re: rOS 7: [*] button => "deadend" sound, why?

Ok, so my RTV running v7.1.0 4055-08 doesn't make the sound but my R3 running v7.1.0 4061-04 does on roScreen. They all make the sound w/*, Rew, & FF on roImageCanvas.

-JT
Roku Community Streaming Expert

Help others find this answer and click "Accept as Solution."
If you appreciate my answer, maybe give me a Kudo.

I am not a Roku employee.
0 Kudos
EnTerr
Roku Guru

Re: rOS 7: [*] button => "deadend" sound, why?

"renojim" wrote:
Ok, so my RTV running v7.1.0 4055-08 doesn't make the sound but my R3 running v7.1.0 4061-04 does on roScreen. They all make the sound w/*, Rew, & FF on roImageCanvas.

I thought it might be the kind of remote (IR vs radio) but did a quick check and "*" deadends on R3 both with radio and IR remote, so not that.
My guess is that RokuTV handles "*" differently (since it is also used for TV settings).

The << and >> in roImageCanvas are something separate since "*" deadend is pervasive throughout the player - no matter where - be it SDK or NDK app (Netflix, Vudu, YouTube, Pandora, games etc etc).
0 Kudos
EnTerr
Roku Guru

Re: rOS 7: [*] button => "deadend" sound, why?

"RokuKC" wrote:
I just filed an issue ticket for it.

Thank you!
0 Kudos
EnTerr
Roku Guru

Re: rOS 7: [*] button => "deadend" sound, why?

"RokuKC" wrote:
I just filed an issue ticket for it.

Hey KC - what's the word on this?
It's been a few months, i imagine someone had opined yet.
0 Kudos
RokuKC
Roku Employee
Roku Employee

Re: rOS 7: [*] button => "deadend" sound, why?

"EnTerr" wrote:
Hey KC - what's the word on this?
It's been a few months, i imagine someone had opined yet.


Unfortunately, still on the backlog.
0 Kudos
Komag
Roku Guru

Re: rOS 7: [*] button => "deadend" sound, why?

I just noticed that this issue seems to finally have been fixed! Yeehaw! It may have been months ago, not sure.
0 Kudos