-
Notifications
You must be signed in to change notification settings - Fork 2
Description
Issue type
Source code related
Device
POCO F2 Pro (lmi)
crDroid version
crDroid 12
Exact version / Build date
12.8/2026-03-16
Bug description
When trying to play any media in the app tidal after a few seconds the app crashes and playback stops. When looking at the logcat it seems the cause is because with a call to media.MediaMetadata$Builder.scaleBitmap the bitmap has Config.HARDWARE and thus the call to android.graphics.Bitmap.createBitmap fails with java.lang.IllegalArgumentException. The problem seems to exist with other media players as well, for example jellyfin (see their issue) And at least in that issue it seems to only affect devices running crdroid. From reading the comments on the jellyfin issue it seems that in the 12.0 release it still seemed to work properly. But it could be just a coincidence, becasue at least with my issue on tidal, I just realized it a few days ago because with a big update they seemed to change their used player or their playback logic in turn now triggering this issue with crdroid.
Steps to reproduce
- Open the media player app tidal
- Play any song
- After a few seconds the app crashes
Relevant log (logcat/build log)
03-17 15:29:44.817 E/AndroidRuntime(18128): FATAL EXCEPTION: DefaultDispatcher-worker-35
03-17 15:29:44.817 E/AndroidRuntime(18128): Process: com.aspiro.tidal, PID: 18128
03-17 15:29:44.817 E/AndroidRuntime(18128): java.lang.IllegalArgumentException: can't create mutable bitmap with Config.HARDWARE
03-17 15:29:44.817 E/AndroidRuntime(18128): at android.graphics.Bitmap.createBitmap(Bitmap.java:1283)
03-17 15:29:44.817 E/AndroidRuntime(18128): at android.graphics.Bitmap.createBitmap(Bitmap.java:1246)
03-17 15:29:44.817 E/AndroidRuntime(18128): at android.graphics.Bitmap.createBitmap(Bitmap.java:1194)
03-17 15:29:44.817 E/AndroidRuntime(18128): at android.graphics.Bitmap.createBitmap(Bitmap.java:1153)
03-17 15:29:44.817 E/AndroidRuntime(18128): at android.media.MediaMetadata$Builder.scaleBitmap(MediaMetadata.java:1029)
03-17 15:29:44.817 E/AndroidRuntime(18128): at android.media.MediaMetadata$Builder.build(MediaMetadata.java:1005)
03-17 15:29:44.817 E/AndroidRuntime(18128): at android.media.session.MediaSession.setMetadata(MediaSession.java:539)
03-17 15:29:44.817 E/AndroidRuntime(18128): at android.support.v4.media.session.MediaSessionCompat$MediaSessionImplApi21.setMetadata(SourceFile:15)
03-17 15:29:44.817 E/AndroidRuntime(18128): at android.support.v4.media.session.MediaSessionCompat.setMetadata(SourceFile:3)
03-17 15:29:44.817 E/AndroidRuntime(18128): at com.aspiro.wamp.player.b0.invoke(SourceFile:43)
03-17 15:29:44.817 E/AndroidRuntime(18128): at com.aspiro.wamp.player.MediaArtworkHelper$getArtwork$1.invokeSuspend(SourceFile:60)
03-17 15:29:44.817 E/AndroidRuntime(18128): at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(SourceFile:9)
03-17 15:29:44.817 E/AndroidRuntime(18128): at kotlinx.coroutines.DispatchedTask.run(SourceFile:122)
03-17 15:29:44.817 E/AndroidRuntime(18128): at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(SourceFile:4)
03-17 15:29:44.817 E/AndroidRuntime(18128): at kotlinx.coroutines.scheduling.TaskImpl.run(SourceFile:3)
03-17 15:29:44.817 E/AndroidRuntime(18128): at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(SourceFile:1)
03-17 15:29:44.817 E/AndroidRuntime(18128): at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(SourceFile:34)
03-17 15:29:44.817 E/AndroidRuntime(18128): at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(SourceFile:29)
03-17 15:29:44.817 E/AndroidRuntime(18128): at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(SourceFile:1)
03-17 15:29:44.817 E/AndroidRuntime(18128): Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [StandaloneCoroutine{Cancelling}@73c8ac6, Dispatchers.IO]Screenshots or videos
No response
Solution
No response
Additional context
No response
Acknowledgements
- I've checked device is officially supported and that no support is provided for unofficial devices (for device specific reports and not source related).
- I'm running latest version available on crdroid.net for this device and that the device is still maintainer supported (not flagged unsupported on download page)
- I have searched the existing issues and this is a new and no duplicate or related to another open issue.
- I have written a short but informative title.
- I filled out all of the requested information in this issue properly and understand that not doing so will automatically result in closing of ticket.