LoudnessCodecController possibly missing on some devices causing crash

[Tolriq]

Version

Media3 main branch

More version details

No response

Devices that reproduce the issue

Random OEM devices

Devices that do not reproduce the issue

Most

Reproducible in the demo app?

Not tested

Reproduction steps

It seems some OEM strange TV devices can be missing the proper Loudness code and will crash when Media3 try to use it.

Failed resolution of: Landroid/media/LoudnessCodecController;

Would be nice to add a try catch for those thanks.

Expected result

No crash

Actual result

Crash

Media

N/A

Bug Report

• You will email the zip file produced by adb bugreport to android-media-github@google.com after filing this issue.

[icbaker]

These are presumably devices that report SDK_INT >= 35? In that case, I'm not sure how they would have passed CTS, as it should check the presence of every public class on the boot class path - as well as explicitly testing LoudnessCodecController.

[Tolriq]

Not all devices goes via CTS :) They are Android 15 devices, usually Chinese low cost.

A try catch does not hurt. I can of course try catch on my side at the MediaCodecAudioRenderer creation and call the explicit constructor to force null, but I do not think that's something that should be done client side.

[icbaker]

If a device didn't pass CTS we cannot assume anything about it. You are firmly in "undefined behaviour" territory. I'm afraid it's not feasible for us to wrap every access to every framework class with a try-catch in case a device somewhere decides to not to provide that class on the boot class path, and it's equally infeasible to play whack-a-mole wrapping try-catch around classes people occasionally report aren't implemented on certain devices.