Koel v2.0 Problems about player HOT 9 CLOSED

Submitted v2.0.1 on Google Play, waiting for approval.

from player.

I do have a similar problem which might be linked, although not a dealbreaker in my case, with a motorola g22, android 12.

My setup involves:

• connecting to my home's wireguard vpn (which also pushes my internal DNS server).
• connecting with Koel app to my home Koel server (hosted on my home's kubernetes cluster, https handled by ingress-nginx, let's encrypt certificates, postgresql database).
• No problem if I use Firefox for Android to connect through this setup, browsing music library and playing songs works as intended.
• No problem with Koel Android app to browse my music library but when I play the first song, it'll start playing and around 20-30 seconds later app will show the "app is not responding" window. Clicking on "Wait" solves the problem and other songs play without a hitch.

Edit: In my case, this seems related to Android's per application battery settings/optimizations. Switching battery optimization off for Koel seems to have solved my problems.

from player.

I've had this exact same problem as well, I start playing a song and the app just crashes about a minute in. This only started happening after the 2.0 update. One thing I've also noticed is Koel media controls no longer show up on the lockscreen or in the pulldown menu like they did before, not sure if these 2 issues are related though. This issue also happens with playing both locally cached and online songs

+1 to the comment of the new design looks fantastic, but this issue makes the app completely unusable

from player.

You guys are lucky, mine crashes in around 5 seconds after putting it in the background.
Xiaomi Redmi 8
Havoc Os 4.14, Android 11

from player.

Same problem here, app crashes after a few seconds of playing a song. I also noticed that the app isn't showing up in the pull down status bar.

Android 12

from player.

Sorry folks, I should have tested it more thoroughly. Will work on a fix.

from player.

Fixed in the latest commit. This apparently is due to a new security requirement that comes with higher API versions, which I couldn't catch as my testing device is too old :(

from player.

Just updated and I can confirm that playback works normally now 👍 Thanks!

from player.

@zv0n Oh, that's super fast. Thanks for the feedback, and enjoy!

from player.