Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tizen TV: Unable to jump repeatedly using the TV remote as the client focuses on the pause button #6480

Open
tuhlaajapoika opened this issue Jan 26, 2025 · 3 comments
Labels
bug Something isn't working

Comments

@tuhlaajapoika
Copy link

Describe The Bug

This issue occured after updating to v10.10.4. On Samsung Tizen TV, when I press the jump/rewind on the TV remote, the client immediatelly focuses on the OSD's pause/play button after just a single press. I then have to navigate back to the seek bar above or to the OSD's left/right rewind buttons to continue jumping.

Steps To Reproduce

  1. Play any content.
  2. Attempt to jump/rewind using the TV remote.
  3. The UI focuses on the pause button after a single press.
  4. One has to navigate upwards to the seekbar or the UI's left/right rewind buttons to continue jumping

I have not tried any emulators as I haven't set one up.

Expected Behavior

On a desktop browser client, for example, I can repeatedly jump by pressing the keyboard's arrow keys. In earlier versions for Tizen, the client would keep its focus on the seekbar (the blue ball indicator), allowing continuous jumping without interruption.

Logs

I'll rebuild the Tizen client and try to catch logs if necessary.

System:

  • Platform: Tizen 6.5
  • Jellyfin Version: 10.10.4 and 10.10.5
@tuhlaajapoika tuhlaajapoika added the bug Something isn't working label Jan 26, 2025
@tuhlaajapoika
Copy link
Author

I moved the issue to the tizen repo: jellyfin/jellyfin-tizen#331

@SjoerdV
Copy link

SjoerdV commented Feb 24, 2025

@tuhlaajapoika I can confirm this is also an issue on LGTV, so this is not tyzen specific issue (Jellyfin on LGTV app AND the builtin browser have same issue). 10.10.3 does not have the issue. Please reopen in this repo

@tuhlaajapoika tuhlaajapoika reopened this Feb 24, 2025
@megosugit

This comment has been minimized.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants