To preface, on OxygenOS 5.0.x/Android 8.0 we were provided with additional bluetooth codecs and additional setup for bluetooth codec manipulation in Setup>Advanced and Setup>Dev Options. In OxygenOS 5.1.x/Android 8.1, the Setup>Advanced options were removed. I'm currently on 5.1.4 on my OP5.
That out of the way, I'm trying to validate if anyone else is experiencing an issue that I'm having. I have a set of Bose QC35 bluetooth headphones that support the AAC bluetooth codec, support of which was added to the OP5 with Oreo. In OxygenOS 5.0.x, I had no problems with it. In OxygenOS 5.1.x, it will only connect with AAC when first paired. If I turn off the headphones and turn them back on, when it reconnects, it defaults to SBC and will not switch back to AAC unless I unpair and repair the headphones.
Does anyone else have Bose QC35 headphones that can confirm this behavior? Or perhaps another set of headphones that support AAC? I've tested with a pair of headphones that support aptX and it keeps the codec, so it appears to be either an issue with AAC on OxygenOS 5.1.x, my headphones, my phone, or Android 8.1 in general. Any validation would be helpful. Thank you
Album here showing proof: imgur.com/a/kTbxZs4
bhcompy said:
To preface, on OxygenOS 5.0.x/Android 8.0 we were provided with additional bluetooth codecs and additional setup for bluetooth codec manipulation in Setup>Advanced and Setup>Dev Options. In OxygenOS 5.1.x/Android 8.1, the Setup>Advanced options were removed. I'm currently on 5.1.4 on my OP5.
That out of the way, I'm trying to validate if anyone else is experiencing an issue that I'm having. I have a set of Bose QC35 bluetooth headphones that support the AAC bluetooth codec, support of which was added to the OP5 with Oreo. In OxygenOS 5.0.x, I had no problems with it. In OxygenOS 5.1.x, it will only connect with AAC when first paired. If I turn off the headphones and turn them back on, when it reconnects, it defaults to SBC and will not switch back to AAC unless I unpair and repair the headphones.
Does anyone else have Bose QC35 headphones that can confirm this behavior? Or perhaps another set of headphones that support AAC? I've tested with a pair of headphones that support aptX and it keeps the codec, so it appears to be either an issue with AAC on OxygenOS 5.1.x, my headphones, my phone, or Android 8.1 in general. Any validation would be helpful. Thank you
Album here showing proof: imgur.com/a/kTbxZs4
Click to expand...
Click to collapse
in the open betas the advanced bluetooth options are still there under developer options
can't help you with any of the other queries as I use apt-x HD
Related
Hey all,
Ever since opting into the Android O beta, my Nexus 6p has been working fine, except for connected to my car via BT. It connects, but just shows 'Unknown Artist' for any kind of track info, and if I switch playback apps (for instance, from Pocketcasts to Google Play Music), my phone disconnects from the car for a second or two, connects again, and still doesn't work. The car in question is a 2016 Mini Cooper S. Anyone else seeing issues like this? Works fine on 7.1.2.
ive got the same issue vw polo. audio plays via bluetooth but no artist info it just shows im connected to 6P and skip track controls dont work just mute and volume
Yeah, I don't even get audio. Nothing actually plays, car displays "unknown artist".
I have this as well on a 2017 toyota, calls etc work fine, just music dips out
sickfallout said:
Hey all,
Ever since opting into the Android O beta, my Nexus 6p has been working fine, except for connected to my car via BT. It connects, but just shows 'Unknown Artist' for any kind of track info, and if I switch playback apps (for instance, from Pocketcasts to Google Play Music), my phone disconnects from the car for a second or two, connects again, and still doesn't work. The car in question is a 2016 Mini Cooper S. Anyone else seeing issues like this? Works fine on 7.1.2.
Click to expand...
Click to collapse
what are the bluetooth settings in the developer setting section?
mine are as follows if you want to try them to see if it gives you some audio
Bluetooth AVCRP Version
AVCRP 1.6
Bluetooth Audio Codec
Streaming: SBC
Bluetooth Audio Sample Rate
Streaming: 44.1kHz
Bluetooth Audio Bits Per Sample
Streaming: 16 Bits/Sample
Bluetooth Audio Channel Mode
Streaming: Stereo
Bluetooth Audio LDAC Codec: Playback Quality
Streaming: Optimised for Audio Quality
MkBy said:
what are the bluetooth settings in the developer setting section?
mine are as follows if you want to try them to see if it gives you some audio
Bluetooth AVCRP Version
AVCRP 1.6
Bluetooth Audio Codec
Streaming: SBC
Bluetooth Audio Sample Rate
Streaming: 44.1kHz
Bluetooth Audio Bits Per Sample
Streaming: 16 Bits/Sample
Bluetooth Audio Channel Mode
Streaming: Stereo
Bluetooth Audio LDAC Codec: Playback Quality
Streaming: Optimised for Audio Quality
Click to expand...
Click to collapse
Thanks for the setting tips, I'll try them out tomorrow and report back.
No luck, same issue persists. I even tried usb-c to usb-a, but my Mini doesn't recognize it as an audio device that way Time to get a new head unit possibly.
No luck, still 'unknown artist' and no audio, even though my phone thinks it's connected and playing.
sickfallout said:
No luck, still 'unknown artist' and no audio, even though my phone thinks it's connected and playing.
Click to expand...
Click to collapse
Do you have this issue on 7.1.2 as well? Don't forget Android O is still in "beta" and I wouldn't be surprised if the BT is a little screwy still.
Triscuit said:
Do you have this issue on 7.1.2 as well? Don't forget Android O is still in "beta" and I wouldn't be surprised if the BT is a little screwy still.
Click to expand...
Click to collapse
Everything works fine on 7.1.2, I had to decide what was more important: working car audio or a much faster OS experience. Hopefully this is something that's either fixed in the release of O, or something my car manufacturer can patch into their system.
Not sure if this will help but my car seems to have pretty good luck with this technique and BMW/Mini ICE systems are similar. I use the aac codec keeping everything else default. I've had the issue a well where it's playing on my phone but not the car; the info also doesn't show. Restarting the phone right before starting the car or soon after seems to be relatively effective as it would then connect after the restarts and actually play the music correctly and show the info.
Not the best solution but hopefully this ends after the final is released.
Hi! I hope this helps. It seem like changing the setting (unchecking) for AAC audio helps with the issue. This seems to be a new feature in Oreo, so go to Bluetooth settings and in the little gear next to device it will popup with a couple of options, uncheck AAC.
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.
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
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.....
Hi everyone! I just bought the Sony 1000XM4 headphones. The headphones support SBC, AAC and LDAC. However, when I connect to my device (Max Pro M2), I can only use SBC. even though in the bluetooth settings for the headphones, the option HD Audio: AAC (No LDAC) is enabled.
I went to the developer options to set the Bluetooth codec to LDAC (Qualcomm aptX Adaptive Audio), but the setting does not stick.
I don't have the 'Connect to two devices simultaneously' option enabled and the priority is on Sound Quality instead of Connection Quality.
I have tried resetting the WiFi and bluetooth settings but still can't get it to work.
I tried connecting the headphones to the Sony XZs and it instantly gave the option to use LDAC and used it. This makes me wonder if this phone even supports LDAC, even though on the internet it says that it does. I can't even use AAC, I am stuck on SBC.
Does anyone have any idea? Please?
abcxyz1171 said:
Hi everyone! I just bought the Sony 1000XM4 headphones. The headphones support SBC, AAC and LDAC. However, when I connect to my device (Max Pro M2), I can only use SBC. even though in the bluetooth settings for the headphones, the option HD Audio: AAC (No LDAC) is enabled.
I went to the developer options to set the Bluetooth codec to LDAC (Qualcomm aptX Adaptive Audio), but the setting does not stick.
I don't have the 'Connect to two devices simultaneously' option enabled and the priority is on Sound Quality instead of Connection Quality.
I have tried resetting the WiFi and bluetooth settings but still can't get it to work.
I tried connecting the headphones to the Sony XZs and it instantly gave the option to use LDAC and used it. This makes me wonder if this phone even supports LDAC, even though on the internet it says that it does. I can't even use AAC, I am stuck on SBC.
Does anyone have any idea? Please?
Click to expand...
Click to collapse
I'm on Havoc 3.11, I don't know about stock ROM.
Yeah, couldn't get it to work on the stock ROM. Now, I'm on Resurrection Remix and it works!