im using 2 raspberry pi devices with premium account
both units are controlled with IOS
both running ver 3 and now ver 4 on both
I complained at least 20/30 times with support regarding the error with no luck
using safari, on IOS , screen flicked with no control
the units mixed the playlist , impossible to use
today ive upgraded both to ver 4, expecting a solution
ive realized, that maybe, the browser was the issue . Ive connected via Chrome and it seems that the issue was solved
Anyone at support had this stupid clue to help?
Hey @mr.wire,
Let’s address your support experience concern, but first we need to establish some technical facts about Safari on iOS and web-based audio streaming.
Safari iOS Audio Streaming - The technical reality:
Safari on iOS has well-documented, long-standing audio streaming issues that affect ALL web-based audio applications, not just Volumio. These are Apple WebKit bugs that have been filed, tracked, and remain unresolved across multiple iOS versions:
- iOS 17.2.1: Audio streaming stops when Safari loses focus between tracks (Apple Community thread #255413652)
- Web Audio API: Requires AudioContext.resume() on user interaction due to suspended state (WebKit bugs #221334, #230902)
- WebRTC audio: Low volume issues, stream interruption problems (WebKit bug #230902)
- Background playback: Inconsistent behavior when switching apps or locking screen
- Autoplay restrictions: Stricter than Chrome, requires explicit user gestures
These issues impact WebRTC streaming, HTML5 audio players, Web Audio API implementations, and web-based audio applications universally. They are NOT Volumio-specific problems.
Chrome on iOS - Why it works better:
Chrome on iOS uses its own rendering engine for web applications, which bypasses many of Safari’s WebKit audio stack limitations. This is why your experience improved after switching browsers - Chrome doesn’t inherit Safari’s audio streaming bugs.
The support question:
Before we discuss support’s responsibility, I need you to clarify:
-
Did you explicitly inform support that you were using Safari on iOS when reporting the “screen flickered with no control” and “units mixed the playlist” issues as result of your consultations with Apple support first?
-
Did you explicitly inform support that you were using Safari on iOS when reporting the “screen flickered with no control” and “units mixed the playlist” issues without consulting Apple support first?
-
What exact symptoms did you report in those 20-30 complaints? (Screen flickering, playlist mixing, control loss - these need to be described precisely)
Why this matters:
If you reported generic symptoms like “can’t control Volumio” without mentioning Safari iOS specifically, support would investigate the Volumio backend, hardware, network, or general configuration issues - NOT browser-specific rendering problems. Safari’s audio bugs manifest as UI control issues, playback interruptions, and state management failures that look identical to backend problems when browser details are omitted.
Support cannot diagnose browser-specific issues without browser information. This is basic troubleshooting protocol.
The bottom line:
Safari iOS audio streaming problems are Apple’s responsibility to fix, not Volumio support’s. These are documented WebKit bugs affecting the entire web audio ecosystem. If browser details were not provided in your support communications, then support investigated the wrong area because they lacked critical diagnostic information.
Provide the support ticket evidence showing you gave them the Safari iOS details, and we can evaluate whether support should have suggested trying Chrome. Without that evidence, this is a case of incomplete problem reporting leading to misdirected troubleshooting.
Kind Regards,
thanks for your explanation
Support never asked me what OS I was using
Ive sent couple if videos showing the errors
Only suggestion given to fix it was re flashing the device and to use play.volumio.com as new link
this replies most of all your questions ,
20 -30 complaints sent but most of them no reply
You can track a bit here GDSC-4368
Now, it looks that via Chrome is responsive, but I do not have it as default browser.
In the meantime , im still paying for a premium service
We mods don’t have access to the ticket system.