The ‘Try hardware decoding’ option doesn’t work.

[comeback556]

Steps to reproduce

In previous versions, enabling the ‘Try hardware decoding’ option would activate HW+, but now it only uses HW. I even tried forcing it with the ‘hwdec=mediacodec’ command in mpv.conf, but it didn’t work.

Expected behavior

.

Actual behavior

.

Crash logs

animiru_crash_logs.txt

Animiru version

0.19.7.3

Android version

Android 13

Device

Poco x3

Other details

No response

Acknowledgements

• I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
• I have written a short but informative title.
• If this is an issue with an extension, I should be opening an issue in the extension's repository.
• I have gone through the FAQ and troubleshooting guide.
• I have updated the app to version 0.19.7.3.
• I have filled out all of the requested information in this form, including specific version numbers.
• I understand that Animiru does not have or fix any extensions, and I will not receive help for any issues related to sources or extensions.

[Secozzi]

You need to add a crash log. To share crash logs go to More → Settings → Advanced and enable Verbose logging, then restart Animiru.

Reproduce the issue and go to More → Settings → Advanced then tap Share crash logs.
You can disable Verbose logging afterwards.

[comeback556]

You need to add a crash log. To share crash logs go to More → Settings → Advanced and enable Verbose logging, then restart Animiru.

Reproduce the issue and go to More → Settings → Advanced then tap Share crash logs. You can disable Verbose logging afterwards.

The thing is, I’m not getting any error logs. It’s just that the player no longer defaults to the HW+ decoder like it did in the previous version. But I’m not sure if you’d still like me to send the logs anyway.

[fakebhai]

yeah just do the steps with config added and relevant settings on.

[comeback556]

animiru_crash_logs.txt

[Secozzi]

animiru_crash_logs.txt

The logs tells me you didn't recreate the issue after applying the setting and restarting the app like I told you to.