Сравнение xiaomi poco x 3 с oppo reno 11 f

BTW, it might now even support other devices, but maybe will require device-specific changes, though this needs to be tested.

I’ll take a look at the github and see what I can do to port it to Poco X3. Fair warning though, I’m not experienced in Android development. Any pointers or tips are highly appreciated. Also feel free to DM me anytime regarding this topic.

Thank you again for your work on this, not a lot going on in this segment

The “Bluetooth Codec Changer” App doesn’t recognize the codec.
The Developer Options UI now shows the options, which it didn’t before.
Third screenshot is from launching the ext2adp app.

Let me know if I can help make this compatible with my device. If logs would help, I’m glad to provide.

You can install good ROM instead of LineageOS, Paranoid Android will most likely do.

Only CLO-based ROMs will ever be supported.

TIL the difference between CAF/CLO and AOSP. Thank you for that.
Got lucky and ParanoidAndroid actually released a A13 rom for my device 4 days ago.
Switched to that.

In even better News:
This module is (nearly) working on POCO X3 NFC!!!

I’ve been trying to solve this actively daily for a month, trying to get anything more than <260kbps from my TWS.
Thank you, thank you, thank you!

TWS’s are connected with LHDC-V, Dev settings, TWS app, BT codec check app are all showing that its connected correctly. BT codec check app can’t read the names, but that should be fine.

Problem:
All sound is being played through the phone speaker instead of the TWS’s

BTW, you could just wait for this to get merged (or build it by yourself) for LHDC.

Patience isn’t my strong suit
+ I was very intrigued to make this happen. Unfortunately I’m only at the beginning of my coding journey, so understanding everything that’s involved is a nice challenge. Original plan was to take a OEM rom that supports LHDC, looking at the diff of the relevant components, and going from there. That probably sounds stupid, when earlier I didn’t even know the about the difference between the AOSP and CLO codebase.
IMO the best way to learn is taking on stuff I don’t even think is surmountable for my level, and just go at it. Growth happens outside of the comfort zone.

That’s a great problem, because I know how to fix it. You’ll need custom Magisk module (instead of what on GitHub). Try attached one.

Installed, rebooted, works flawlessly!
Changing parameters in Dev Settings, etc, all works.

I cannot thank you enough. This makes me so happy. That was some insane response time. Thank you for doing this for me. You made my week!
In my country we say ” I kiss your eyes :* “

Yes, it has to be. Magisk companion module is device-specific.

This is what the problem is, your ROM is incompatible. Once again, only CLO-based ROMs will ever be supported. Try Paranoid Android, your device wouldn’t need installing Magisk module, only LSPosed one is needed.

The thing is I have no idea what CLO means. I’ll try roms on my one plus 6 but I don’t use GAPPS on my main phone (is superiorOS CLO ?)

I would be very happy to enable the codec for good sound on one of these devices, can you help me, I would be grateful

Only CLO-based ROMs have chances of being actually compatible.
As a rule of thumb: if aptX Adaptive is supported then it might work on your device.

No Samsung devices (yet? It will require another approach tho should be doable) or Google Pixels. Even though they might still have the same Snapdragon SoC, the Bluetooth stack is not compatible (and it’s usually statically linked into libbluetooth_jni.so, which is a no-go).
If sound is played through phone speaker instead of earbuds, you’ll need custom Magisk module. It might be beneficial to create “universal one”, but it’s not necessary for the devices I’ll target the development for.

Tested on Red Magic 8 Pro (v3.28).
Install latest LSPosed from GitHub CI and modules, reboot.
LHDC will be selected automatically if supported by audio sink device. It might be necessary to pair the device before enabling the module.
All versions (2, 3/4 and 5) should be supported, the most recent one will be selected automatically.

Switching codecs and playback quality doesn’t work yet. Try restarting “Bluetooth” app if playback fails for some reason.

Other devices might work, if not then pull requests are welcome, sources are here.

Hello, I was using oppo enco x2 headphones before, but they were returned because they were broken. Since oppo is no longer sold in my country, I bought onepluds buds pro 2. But it only supports LHDC codec. Oppo had both LHDC and LDAC. My phone only supports LDAC. I use Samsung Z fold 3. Can I turn on the LDHC feature using the method you mentioned? I can sell the phone I use and buy Google Pixel 6 Pro. Can I use this method on Google Pixel or should I buy a Zte phone? I’ve never rooted before, I don’t know much about how to do it.