Hello,
So based on my request for help in the following thread, I was initially trying to setup ultimate audio experience with ARISE (not only V4A) to run on stock 8.1 (Mar 18 updates). However after numerous tricks and ways to make it work , i reliazed its not possible for now. I also came to know that V4A and Atmos dont live together well and Atmos overrides the sound processing by V4A, which has to be manually reactivated time and again.
https://forum.xda-developers.com/pixel-xl/how-to/guide-ultimate-audio-battery-guide-t3727124
I reverted to Android 8..0.0 (Oct 17) and then following the guide in this thread
https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-install-arise-sound-8-0-t3692415
I was able to install V4A , Dolby Surround to work together (Arkamys , A3MD crash repeatedly and ICESound breaks the sound at all from speaker or headsets, didnt find a solution for it so far).
One of reasons for me to try Google Pixel with 8.+.+ was to try the new (supposedly) hi resolution bluetooth codecs namely AptxHD and LDAC (a Sony version of Hi-res audio protocol).
Being an amateur audiophile, I bought Sony Wh1000MX2 which supports both LDAC and AptXHD.
A finding which I made was when I paired the XL with Sony Headphones using LDAC, the audio quality was good, however I wanted to make it better by activating V4A and Dolby Surround audio mods. After fiddiling for a couple of hours, I realize V4A and Dolby does not work or recognized the sound output when the headphones were connected using LDAC. It was seen as the V4A driver status showed "Abnormal" and no "Processing" was done. However with the same setup as soon as I changed my bluetooth audio connection to use AptxHD , the V4A and Dolby started working and sound was equally superb with the added value of tuning it more to my taste using the audio mod.
I am not sure why the audio mods are not bluetooth connection protocol agnostic, or why not working with LDAC.
Shared it for information, maybe the gurus would be able to reproduce the setup and post a working solution.
Thanks.
Hi, same problem here. I have a pair of Sony MDR 1000x Bluetooth cans with ldac support. Flashed my Xiaomi Redmi Note 4x to LOS unofficial Oreo to get the ldac codec going (it works indeed), but v4a does not work with this codec. If I choose the SBC codec, it apears to at least realize that it can do something (although changeing effects dosent work). With ldac enabled v4a driver status says abnormal and obviously nothing works. All in all I guess that we cant do anything other than wait, so that some devs will adopt to the new features of Android Oreo.
Hope for the best
PS: sorry for possible spelling mistakes
edit: if someone needs logs, im happy to provide them.
HyperEscape said:
Hello,
So based on my request for help in the following thread, I was initially trying to setup ultimate audio experience with ARISE (not only V4A) to run on stock 8.1 (Mar 18 updates). However after numerous tricks and ways to make it work , i reliazed its not possible for now. I also came to know that V4A and Atmos dont live together well and Atmos overrides the sound processing by V4A, which has to be manually reactivated time and again.
https://forum.xda-developers.com/pixel-xl/how-to/guide-ultimate-audio-battery-guide-t3727124
I reverted to Android 8..0.0 (Oct 17) and then following the guide in this thread
https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-install-arise-sound-8-0-t3692415
I was able to install V4A , Dolby Surround to work together (Arkamys , A3MD crash repeatedly and ICESound breaks the sound at all from speaker or headsets, didnt find a solution for it so far).
One of reasons for me to try Google Pixel with 8.+.+ was to try the new (supposedly) hi resolution bluetooth codecs namely AptxHD and LDAC (a Sony version of Hi-res audio protocol).
Being an amateur audiophile, I bought Sony Wh1000MX2 which supports both LDAC and AptXHD.
A finding which I made was when I paired the XL with Sony Headphones using LDAC, the audio quality was good, however I wanted to make it better by activating V4A and Dolby Surround audio mods. After fiddiling for a couple of hours, I realize V4A and Dolby does not work or recognized the sound output when the headphones were connected using LDAC. It was seen as the V4A driver status showed "Abnormal" and no "Processing" was done. However with the same setup as soon as I changed my bluetooth audio connection to use AptxHD , the V4A and Dolby started working and sound was equally superb with the added value of tuning it more to my taste using the audio mod.
I am not sure why the audio mods are not bluetooth connection protocol agnostic, or why not working with LDAC.
Shared it for information, maybe the gurus would be able to reproduce the setup and post a working solution.
Thanks.
Click to expand...
Click to collapse
Rakkke said:
Hi, same problem here. I have a pair of Sony MDR 1000x Bluetooth cans with ldac support. Flashed my Xiaomi Redmi Note 4x to LOS unofficial Oreo to get the ldac codec going (it works indeed), but v4a does not work with this codec. If I choose the SBC codec, it apears to at least realize that it can do something (although changeing effects dosent work). With ldac enabled v4a driver status says abnormal and obviously nothing works. All in all I guess that we cant do anything other than wait, so that some devs will adopt to the new features of Android Oreo.
edit: if someone needs logs, im happy to provide them.
Click to expand...
Click to collapse
Not the type to necro old threads, but I believe I've found the solution to your problem. I had this problem myself on my V30 and realized what was making Viper effects not processing. LDAC by default starts off with an audio sample quality of 96 kHz and 32 audio bits per sample. If you can change these settings in developer options, lower the sample rate(sample quality) to 44.1 kHz - the rate used for 90% of all music & audio and the bits per sample to 24. Viper audio effects should work now with LDAC. You will have to do this every time you turn on/pair your headphones to your phone.
Ypu can use James DSP for ldac codec with any sample rate and bits per sample. James DSP has a magisk module and can be installed from magisk.
Does s7 edge with Nougat have aptx Bluetooth codec? If so then how do I activate it?
Does s7 edge exynos with nougat have aac Bluetooth codec?
If so then how do I activate it?
If my headphones support the older aptx codec then will they support aptx hd as well?
I'm hoping that s7 edge exynos isn't limited to sbc only.
S7 Edge supports aptX, not aptX HD. Probably not AAC. I don't think you manually activate anything, the best codec should be chosen automatically.
You might want to look into UHQA, which is supported by a few Bluetooth headphones like the Samsung Level On Pro and Level U Pro. This you can manually enable or disable, for wired headphones too!
in Oreo you can select your codec in Developer Options.
I am running Oreo 8.1 on Nitrogen OS OPM3-171019.013
I have a pair of Bluetooth headphones Sennheiser Momentum Free and the definitely support Apt-X but the only allow me to use AAC (HD audio) or SBC. I want to use Apt-X but the damn setting in Developer Options won't change.
Please help me :'(
Link to headphones info
https://en-uk.sennheiser.com/headphones-bluetooth-momentum-free
Hi guys, is there any solution or magisk module to activate ldac codec on mia1 using pie? I was able to find only module for activating of aptx, not ldac.
Any advice please?
I'm on Pie custom ROM (HavocOS 2.6) and LDAC works out of the box (I tested Sony WH-1000XM3 headphones and the app shows LDAC logo while playing music, probably is the same with stock Pie.
Could anyone with the phone double-check their bluetooth codec options?
Being Android 8.1.0, it should have LDAC ... and that is extremely important to me. But it's missing from my phone. I have tried installing JamesDSP through Magisk, and it works, however I do not see how to enable its LDAC so its running everything through SBC or whatever that low-quality sounding codec is called.
Thanks.
Brian
I also wondered if such audio drivers like LDAC enabling is similar to having 4K 265H codec built in to the chipset & not a question of software updates can enable.....