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

Just got fw 7.0.9021 and noticing that pressing “Options” (“*”) button on the remote when in-channel has started making a gratuitous “deadend” sound now. What’s up with that?!

Re-stating verbosely: start an app (be it BrSc or native, does not matter). Press “*” on the remote (any remote, incl. ECP app) in a place where you know it did not complain in fw6.2. You’ll hear a slightly-annoyed-“ding” (like when reaching end-of-a-list). Try some other button that is passive in that screen, say A/B or maybe InstantReplay - no ding. This (mis)behavior seems to be in the input API.

Not cool. Is it a regression (i seem to remember there was deadend beep before) or intentional - and if the latter, how is it cured?

Yeah noticed that myself - Perhaps you need to return “True” that you handled it yourself: as in Scene Graph :neutral_face:

“NewManLiving” wrote:
Perhaps you need to return “True” that you handled it yourself: as in Scene Graph :neutral_face:Can’t - there is no facility for that in what i use (see here and here).

Also, AFAIR there is no way for an event to return code back in “classic” B/S events like roUniversalControlEvent. (If there were, we’d be doing 2-way comm. on ECP via roInputEvent.)

Just trying to be funny. There is no way to return. But it may Be a side-effect from the Scene Graph event handler, which does require a return value.

Oy! Roku* - what happened with this?
Four months passed - did somebody look at it, will it be fixed?

I am using the “options” button in an app and my supposedly current rOS 7.0.9044 still makes the stupid sound - but which is worse, when i hold- down, the sound starts repeating itself and turns into a machine-gun-fire audio, akin to http://soundbible.com/1371-Uzi-Shooting.html

Issue still there in rOS 7.1.4062.

@Roku - is there a ticket on this? Any clarification notes from it?

Yeah, it’s really annoying in my game to hear that sound every time the player wants to throw an Item or drink a potion.

Komag, what screen type are you using? I know it makes the sound for an image canvas and, for the record, the FF and Rew buttons also produce the sound, but I don’t hear it when using an roScreen. I reported the FF/Rew image canvas regression years ago when I first noticed it and actually had it acknowledged in one of the beta forums as a bug, but it’s still there years later, so I wouldn’t hold out any hope of the asterisk button deadend sound being fixed.

-JT

I’m roScreen all the way, and it’s only * that makes the sound, and it’s only a partial sound, not the full thing

“EnTerr” wrote:
Oy! Roku* - what happened with this?
Four months passed - did somebody look at it, will it be fixed?

I am using the “options” button in an app and my supposedly current rOS 7.0.9044 still makes the stupid sound - but which is worse, when i hold- down, the sound starts repeating itself and turns into a machine-gun-fire audio, akin to http://soundbible.com/1371-Uzi-Shooting.html

I just filed an issue ticket for it.

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

“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).

“RokuKC” wrote:
I just filed an issue ticket for it.
Thank you!

“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.

“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.

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