The VideoLAN Forums

I'm using VLC as my media player on my iPhone presently, and I've run into a problem. The app works flawlessly when I've got my device unlocked, whether I'm on the app or on a different one it plays my music perfectly, however, after locking my device it plays through the song it's on, then goes to the next one - but it doesn't play the audio. It will continue to play through videos, and go to the next one afterwards, without any sound until you press the home button to turn the screen on, at which point it will play the sound like normal from wherever it's at now. Say you were listening to a song, you hit the lock button on the top of your device, it'll play music fine until the end of the song, then it;ll move to the next song and you won't get any audio. If you wait three minutes then press the home button to wake your screen up it'll start playing audio from three minutes into the track. It will not play audio until the screen is on, but once it's on it plays fine right till the end and then switches to the next song and won't play audio until you turn the screen on again.

This happens with and without a passcode on my device. I'm using version 3.1.2 of the VLC for Mobile app from the ios app store.

I'm wondering if I've got some setting causing this, or if it's normal? Many thanks for any help!
- Night

Hi,

Thanks for the report.

The issue is quite weird, I tried reproducing this issue on a iPhone 7 - iOS 11.4.1 but no luck.
Do you have this issue with specific type of file? Could you double check in the settings if you have "audio playback in background" activated?

Hi,

Sometimes got the same issue on a iphone SE iOS 12.1 with vlc 3.1.3. As soon as the screen is loc’ed, vlc will play the song to its end, but will not continue to the next until I lift the iPhone and the screen lights up. In the background the song has been playing, but without sound

Kind regards,

Hi, same issue here on iPhone 13 mini. The "audio playback in background" and "automatically play next item" both activated.

We fixed that for the next update.

Any word on when that update is coming out?