Jump to content

Lil' issues with PA and Xiaomi Redmi 2201117TG (SPES_global)


Go to solution Solved by andrewilley,

Recommended Posts

Shows that it failed to read /vendor/etc/audio_output_policy.conf

and is now reading from /vendor/etc/audio_io_policy.conf.

Apparently, it supports LDAC, and in developer options, it displays several codecs, but supposedly Android is functional with AptX Adaptive at 24/96, among other audio codecs. In the Bluetooth codec changer app, it shows that my device is compatible with AptX TWS+, AptX, AAC, and SBC, while according to the same app, my Sennheiser Momentum 4 is only compatible with standard AptX at most (16/44.1). In the Sennheiser app, I already modified the codec to 24/96. My device is supposed to support such codecs, but it doesn't allow me to disable AD2P download or modify the maximum number of connected devices. This reading error does not occur with other devices I’ve tested. Is there any way to configure PA or my Android properly with my Momentum 4?

It’s running HyperOS 1.0.8.0.TGCMIXM with Android 13. I’m attaching the audio output log file for reference.

btw thanks.

SPES Global.txt

  • Solution

Different manufacturers store the audio configuration log in different locations, and sometimes under different filenames. PA will check several options until it finds one, showing a read error (or more accurately I guess, "file not found") for others it looks for in the meantime.

Manufacturers also may or may not provide live support for different codecs in their ROMs, even if the chipset does support it. Have you had a look in Android Settings=>Developer Options, as sometimes there is a switch to set your preferences in there.

Andre

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...