Skip to content

Fix remote Jellyfin play commands - #2136

Closed
7831940 wants to merge 1 commit into
damontecres:mainfrom
7831940:fix-remote-casting
Closed

7831940 wants to merge 1 commit into
damontecres:mainfrom
7831940:fix-remote-casting

Conversation

@7831940

@7831940 7831940 commented Oct 26, 2026 •

Copy link
Copy Markdown

Description

Previously, Wholphin could be discovered as a cast target, but it ignored the incoming play command. The fix routes the command into the same playback path used by normal app launches.

Fixed casting by handling Jellyfin’s remote PlayMessage WebSocket event
Subscribed ServerEventListener to PlayMessage
Extracted the requested item ID, playlist index, and playback position
Converted that data into Wholphin’s existing ACTION_PLAYBACK intent
Added INTENT_POSITION so casting can start at the requested timestamp
Added a MainActivity handler that passes the intent into the normal playback startup flow

Related issues

Fixes #1467

Testing

Wolphin installed on Fire Cube 3, successfully casted media from browser and phone

AI or LLM usage

This change was developed with assistance from OpenAI Codex. I reviewed and tested the implementation. Assistance was used in MainActivity.kt, IntentService.kt, and ServerEventListener.kt

@damontecres

Copy link
Copy Markdown
Owner

Thanks for the contribution, but I have a local branch I'm working on to more fully implement the play message options.

@damontecres damontecres closed this Nov 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Using Cast To device from browser / client (from another device) broken.

2 participants