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

Feature request: client (or at least mobile) "keep alive" option #3872

Open
c-prompt opened this issue Dec 29, 2024 · 0 comments
Open

Feature request: client (or at least mobile) "keep alive" option #3872

c-prompt opened this issue Dec 29, 2024 · 0 comments

Comments

@c-prompt
Copy link

My use case: I have a spare Android 13 mobile phone hooked up directly to a stereo system (plugged in via USB) that otherwise couldn't have music streamed to it. The stereo plays to speakers throughout my home. The stereo and phone stay on all the time. The only purpose of the phone is for an Emby client and the screen stays off all the time. Thus, no matter what room I'm in, I can use my primary mobile phone or laptop to play music on the Android 13 Emby client with Play To.

However, it appears the Android 13 Emby client times out (after 10 minutes?) when not in use. Thus, music won't play when I go to play music from another client with Play To. So I have to open the Emby app on the Android 13 phone to wake it up and then I'm able to use Play To.

It would be nice if the Emby client had a keep alive switch and/or you could set the number of minutes before the client times out. As a workaround for anyone who also has this use case, I use https://www.macrodroid.com/ to turn on the screen and then open the Emby app every 5 minutes.

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

No branches or pull requests

1 participant