Hi,
I have an issue on mobile browser, when streaming a webradio as background sound, when I close the browser on mobile the sound pause and play again...
I have to kill the browser to stop the sound...
tried on android / chrome and android browser
for exemple you can try this url : https://www.360images.fr/360/nyc/bridges.html
sound doesn't stop when closing mobile browser
-
-
Going to that page in Chrome on Android I get no sound.
In my develpement using v1.20.2 I have no problem with sound continuing playing after switching to a different tab. Example: Carlsbad Caverns.
BTW, consider changing your htaccess file to automatically redirect any http URL requests to https.
-
Thx for looking Scott.
Well I have sound ?
You use playsound in your exemple which works fine, the problem appears with streamsound !
PS : my non www or https redirection is managed by my cmsBest regards
-
You use playsound in your exemple which works fine, the problem appears with streamsound !
Good point. I haven't tested with streaming sound.
And to clarify. I get sound in a desktop browser in your example, but not in Chrome on Android
-
Ok, strange ?
it works for me on android 8.0 + chrome 78.0.3904.108 -
Fo me: Android 8.0.0, Chrome Chrome v79.0.3945.79 on a Galaxy S7. Strange that it works on my desktop but not the phone. Should just require a screen touch to start playing.
-
Looks like Chrome 79 was buggy ?
-
Looks like Chrome 79 was buggy ?
Could be. I just checked on another phone but that is also Chrome 79. Also checked using the Samsung browser and no sound there, either.Tried in Safari on iPhone: Sound played and would not stop after switching to another tab.
Chrome on iPhone: Sound played and stopped when switching to another tab. But it wouldn't start again after switching back. Reloaded page and then it would restart after switching back. switched away and waited longer. Now can't get sound to play after switching back.
Hope that helps a little.
-
just noticed that you are using v1.20.1. Don't know if it would make any difference but maybe try upgrading to the current 1.20.2?
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!