While watching a movie and activating the OSD by pressing the select button on the Shield Remote, it is not dismissed after the short timeout. It can be dismissed by pressing the back button some other action, i.e., activating/deactivating PIP.
Press the back button the remote to dismiss OSD.
Hi @GoDanno
this behaviour has been recently changed following new playback style rules given by Google for the Android TV platform.
Thanks
@jesusmc does that mean it wont be disappearing any more? youtube doesnt do the same!
@jesusmc can we get a word on this?
@jesusmc Sorry, I just noticed your reply…
Aren’t style rules mostly strong suggestions? I certainly hope you don’t fully follow the new YouTube app (I meant web view) in that it takes many more clicks to do the simplest of actions.
This is really annoying and just gets in the way of a previously pleasant experience.
Here’s a possible issue, though: After being well into a movie (possibly 1/4 or 1/2 way though) and after pausing/resuming/back button several times, it takes two clicks instead of one of the select/up/down buttons for the controls to appear. It’s as if after a while, the first click is ignored.
@teshiburu said:
@jesusmc does that mean it wont be disappearing any more? youtube doesnt do the same!
No other apps follow these supposed style guide, not even those from Google. Not sure why Plex is hanging on to this excuse. The Android app has an absolutely convoluted UI and especially terrible UX. I use it because I have to. If someone released a third-party client app matching the UI of PMP (full screen mode, not the web UI), I’d never use the official version ever again.
I’d like to see links to referenced Google guidelines any time this type of excuse is given. As per updated guidelines (they’re NOT rules by any means) an App can have 7 actions on the primary action row of the transport control view - we only get 5 with Plex and there are no commands available to skip anything other than 30 seconds forward and 10 seconds back. No 1 minute, no 10 minute.
So Plex is offering what they want within guidelines which are very loose to begin with.
I haven’t found anything about keeping the transport OSD active. But I did see that one of the guidelines is that focus should always default to the MIDDLE action when the OSD is brought up (with pressing any nav direction). Plex doesn’t do this - it comes up with the last action that was selected, such as forward or reverse - in fact, even clicking the center button won’t produce the center action by default - it will produce the last used action (without showing the OSD). Both of these issues are BUGS.
Thank you for you concerns.
We updated to the latest version of the Leanback SDK and the default behaviour was changed (by Google). After tinkering with a workarounds (time consuming, I also thought it was a bug) we decided to go with what was provided by the platform. We understand that most other other apps use the old behaviour. This means they haven’t updated to the latest version of the library, don’t use the standard controls, or worked around the change.
There wasn’t a release note for this change so we were also taken by surprise.
You can see the behaviour is the same in the Leanback sample (https://github.com/googlesamples/androidtv-Leanback) and the documentation for the control explicitly states that if tickle() is called (i.e. any button is pressed) the autohide timer will be disabled.
There is still some internal discussion happening around this change, I’ll make sure the UX guys are aware of this thread.
@roflharrison Thanks for the update.
Just confirming that this has been fixed since 6.13.0.3396-beta. Thanks.
@roflharrison After a brief read, it sounds to me like the tickle call is simply to delay the auto-hide behavior by killing the timer any time you touch a control. If the overlay persists when the autohide property is enabled (tickle isn’t supposed to disable the property) then that’s a bug.
There doesn’t appear to be anything out of the ordinary with the documentation you linked and it doesn’t imply that the overlay should persist forever after being used.
I see that auto-hiding is back, which is good. If Google has a bug, you guys should make sure they know about it. I’m still hopeful of course you’ll stop using their basic controls in a revamped client someday.
On my nvidia shield I find that I’ll bring up the osd to search through a programme and while pressing the forwards or backwards button the osd disappears meaning I can’t see how far through I am until I press select again, then I’ll get about 5 seconds of pressing the buttons to skip while seeing the progress before it goes again.
It makes using the osd and searching too frustrating to use. Is this what others see?
@andrewpmoore said:
On my nvidia shield I find that I’ll bring up the osd to search through a programme and while pressing the forwards or backwards button the osd disappears meaning I can’t see how far through I am until I press select again, then I’ll get about 5 seconds of pressing the buttons to skip while seeing the progress before it goes again.It makes using the osd and searching too frustrating to use. Is this what others see?
That’s expected. If you don’t use any of the on screen buttons, the OSD will go away. If you want to keep it up, use the on screen << >> buttons.
But I am using the on screen buttons and it’ll still go. It didn’t used to until a recent build
Oh, I thought you were using the physical buttons on the remote. Let me double check. Last time I tried, the OSD worked fine. What version of the app are you using?
I’m on 6.14.0.3665
