Mobile Phone Browsers doesn't keep playing when screen asleep/timesout

Question

Mobile Phone Browsers doesn't keep playing when screen asleep/timesout

s3m1s0n1c opened this issue 4 years ago · comments

Hey Guys,

Looks like trunk-player doesn't keep playing on mobiles when the screen times out or goes to sleep...
It plays the call then stops and doesn't keep playing the next call..

Is there an easy way to fix this as my users would like to have it in the BG so they can hear whats going on.

Thanks
Sonic

Sonic · Answer 1 · Mon Dec 28 2020 08:55:04 GMT+0800 (China Standard Time)

After doing some tests..

Safari is the only one at the moment..

Doing more tests on other browsers

Brett · Answer 2 · Mon Dec 28 2020 09:11:59 GMT+0800 (China Standard Time)

Android as a whole will do that sort of behavior. Once the screen timeout happens, Android will begin to shush/put-to-sleep apps that use the most CPU time thus most battery usage.

The only real way around that issue is by using an app (ScannerRadio, VLC, MXPlayer), Tasker or some other sort of keep-alive application, or having users go to the developer settings on android to force the phone screen to always remain on while charging.

Sonic · Answer 3 · Mon Dec 28 2020 18:16:05 GMT+0800 (China Standard Time)

So it seems its not just mobiles..
If I open Chrome on my Mac and not actively on the table it stops playing after a while..
Its doing the same on mobile as well..

Brett · Answer 4 · Mon Dec 28 2020 19:09:16 GMT+0800 (China Standard Time)

Correct. Background tabs are throttled on Chrome (and most Chromium-based browsers) - timer dependent.

There used to be an option under chrome://flags to override the background tab CPU limiter. It would appear it was changed in recent years to: chrome://flags/#intensive-wake-up-throttling

Dylan Reinhold · Answer 5 · Tue Dec 29 2020 02:39:04 GMT+0800 (China Standard Time)

Yeah the browser have locked down a lot of javascript activities when the page is not in focus.
I'm sure there are some workarounds but probably each browser has their own.
The mplayer that was added 4 years ago (which is an eternity in browser development) a newer javascipt player might help, but that code a spaghetti mess.
I don't see a quick fix for this one, but does need some love.

Sonic · Answer 6 · Sun Jan 03 2021 14:08:19 GMT+0800 (China Standard Time)

Mmm that's a bit shitty.. Oh well... it is what it is..

Thanks for your comments 👍

Sonic · Answer 7 · Mon Aug 16 2021 16:32:48 GMT+0800 (China Standard Time)

I'll leave this one open..

Maybe someone might want the challenge to re-visit mplayer

Brian Hall · Answer 8 · Fri Jan 28 2022 02:22:14 GMT+0800 (China Standard Time)

This is still an issue. I noticed that audio from TR/Trunk-Player stops whenever the browser is minimized on iOS/iPad OS 15 (regardless of whether I'm using Safari, Chrome, or Firefox).

However, I did discover that the scanner app NoraSector has figured out a way to keep the audio running in mobile web browsers even when the browser is not in focus. Not sure if it's because it's using WebRTC or something else.

Max Watermolen · Answer 9 · Mon Jan 31 2022 02:31:03 GMT+0800 (China Standard Time)

@bhall7 this seems to be an issue with the Channels implementation of Websockets and websockets in general. I am working on a complete re-write to Trunk-Player and it will be using sockets.io... unfortunately for now there is not a great solution