Hi all!
I wanted to open up a discussion about the new Oreo features for Bluetooth codecs in the developer section. I haven't been able to find a comprehensive guide or info anywhere that covers how it actually should work, and I don't believe it's working correctly - I would like to explore more with you.
I'm on a Google (carrier free) Pixel, using a fresh install of OPR6.170623.012 - which is working brilliantly by the way.
It seems to me that I can't make the settings stick, if I for example change the Bluetooth Audio Codec to aptX, or modify any of the other settings when I go back in it always reverts to the 'Use System Selection (Default)' option. I'm typically trying this with Bluetooth off, changing the setting and turning Bluetooth on. I've also tried rebooting in-between, as well as different variations. The developer toggle is set to on of course.
It may be my misunderstanding of how this works, but it even if I stay on the developers screen and change the codec, if I turn Bluetooth on and it connects to a device, for instance my in-car Bluetooth audio, which I believe supports aptX, it doesn't care what the codec setting is and displays 'Streaming: SBC', which is of course what I'd expect would be overridden.
The only thing that seems to stick is the AVRCP version. I'm wondering if the Bluetooth HCI snoop log will provide any information?
Have any of you had any experience with this, or have anything to add to the conversation?
Many thanks in advance,
OK so it seems this codec list doesn't allow you to set a 'default', it just allows for modifying the codec during playback?
What I've experienced so far is that it does work with 'Use System Selection' to use the best codec available on the device you are connected to. It also allows you to change the codec to another while streaming/playing. The sub-text under Bluetooth Audio Codec does dynamically change from SBC to AAC.
Example: My headphones support SBC and AAC, the Pixel defaults to AAC on establishing a Bluetooth connection but does allow downgrading to SBC by picking from the list (as a test).
It however doesn't retain whatever you pick in the list if bluetooth is turned off then back on, it basically always defaults to system selection, then auto-picks on every connection. Perhaps this is by design, it is developer tools after all.
I haven't been able to get this to work with aptX in my car yet with my Pixel, even though it is apparently supported?
Also of note: To achieve AAC on my Bluetooth headphones I had to put them into a 'Priority on sound quality' mode and also turn off the Bluetooth phone (i.e. call connectivity, music ONLY) on the Pixel connection to achieve AAC.
are you sure that your car supports aptx? before this developer option it was very hard to actually see the codec being used.
I believe so, the Bluetooth product states that it supports EDR and aptX, but yes, I cannot be 100% certain.
Are you suggesting it should be possible with Pixel and the Oreo build as-is?
Related
Hi,
I'm looking for something (app, magisk/xposed module, ROM that supports this...) that'll provide a quick and simple way to switch between audio outputs without disconnecting anything. In Android P we can connect to multiple Bluetooth devices and switch the output between them, by setting the 'active' device in the Bluetooth menu. We still can't route audio to the speaker while being connected to a Bluetooth device, though, and going to the Bluetooth menu is kinda slow anyway.
What I have in mind is something similar to the solution in Samsung Galaxy devices, where when you have multiple audio devices available you get a persistent notification that allows quickly switching between them. I believe it's even possible to pick audio output for specific apps somewhere in the settings.
Suggestions?
I've been experimenting with the Bluetooth options in developer options, but every time I change them, they change back to the default settings.
Has anyone any help on how to make them stick?
Sent from my [device_name] using XDA-Developers Legacy app
I've experienced this as well. I believe by design, you must first have an audio device paired and connected before changing these settings, and even then, when doing so, the BT device must be capable of such settings. As an example, when my BT headphones are connected, I can set the DEV option to a lower than 24 bits "per sample" but not higher. All the settings here depend on the hardware in use and whether it is capable of the setting. ->Then when disconnected, the dev options return to their default settings. -But they should return when re-connected.
-hope this helps to at least get the discussion ball rolling.
oryanh said:
I've experienced this as well. I believe by design, you must first have an audio device paired and connected before changing these settings, and even then, when doing so, the BT device must be capable of such settings. As an example, when my BT headphones are connected, I can set the DEV option to a lower than 24 bits "per sample" but not higher. All the settings here depend on the hardware in use and whether it is capable of the setting. ->Then when disconnected, the dev options return to their default settings. -But they should return when re-connected.
-hope this helps to at least get the discussion ball rolling.
Click to expand...
Click to collapse
^ The above is definitely not true. At least not for everyone. I have a galaxy note 9 and I've tried connecting headphones as well as a pair of edifier speakers. Nothing except AVRCP version sticks, and that sticks whether I have a bluetooth device connected or not. Everything else does not stick, even though both devices are of course capable of aptX and 48khz and 24b/s. In fact the speakers are intended for 48khz 24b/s, it causes audio stuttering if I have anything else. No matter what I do, everything just defaults to SBC, 44.1khz, 16b/s. It's clearly broken and has been for like 3 versions of android OS lol. Every android phone I've ever had has had this problem too. So clearly it has nothing to do with the hardware you're connected to, since all the devices I've connected are intended for aptX, 48khz, 24b/s. And I don't think it has anything to do with the phone's hardware either, since I used to use an essential phone which is advertised as being intended for aptX HD use with the "TIDAL" app. They gave me a 3 month free trial to this service and said it output high fidelity audio via aptX HD. But no, the essential phone's bluetooth developer options behaved in exactly the same way. I've tried a lot of other things as well, so I'm pretty sure this UI element is either just fundamentally broken, or is intentionally locked from the user, presumably for some patronizing reason
Hi.
I've seen barely any mention of this issue.
I've tried several ROMs like Bliss, Havoc and Evolution, all of them Q.
I have an EarStudio E100 DAC which supports AptX and AptX HD, which were working perfectly well on Android 9.
I was able to select the right codec from Developer Options and the sound would be much better and SBC or AAC, but now on Android 10, there is no difference whatsoever. I can select AptX HD it does not stick and reverts back to the lowest quality codec.
Any idea on how to solve this?
EDIT:
On Reddit, from user CoolGeek71, I found out that selecting the capabilities FIRST and only after that selecting AptX HD inside Developer Options, Android will use the requested codec. So, instead of selecting AptX HD only as it was on Pie, I have to select before the "Bluetooth Audio Sample Rate" to 44.1kHz or 48kHz and "Bluetooth Audio Bits per Sample" to 24 bits. Only then, stupid Android 10 will use it.
Once again, Google making simple things harder to use.
I noticed that if I change the developer settings for Bluetooth codec it automatically changes it back to defaults after I close out of the settings.
Sent from my GM1917 using Tapatalk
This stupid problem is also present with LDAC quality settings as well. I use the Fiio BTR5.
Interestingly, Beta 8 fixed this issue. However this bug has reared its ugly head on the newest 1.0.3.1 again.
Any way to enable all of the bt codecs that are supported by the processor but disabled by samsung?
Can only select SBC.
Bt device needs to support the codec.
Some apps use only sbc.
If the app and device use the blanked out codec try clearing system cache, a network reset, turning Developer options off then back on.
Make sure you didn't disable a needed service, turn off global power management.
The problem is Samsung disabled the high res codecs. Even with a supported device, it can not be selected.
LDAC and SCC should be available.
No APTX HD.
I got ldac working. Thanks
当你连接蓝牙设备后，这个会自动切换的
Translated by GT: When you connect a bluetooth device, this will automatically switch
bestbocai said:
当你连接蓝牙设备后，这个会自动切换的
Click to expand...
Click to collapse
"When you connect a bluetooth device, this will automatically switch"
Welcome to XDA
English only please per forum rules.
Best to check it in Developer options when connected and using to verify the codec in use if set to automatic detection.
Samsung also hides a toggle in Settings - Connections - Bluetooth - your Bluetooth device. This is how I got LDAC working on my Soundcore Liberty 3 headphones.
Hi, Can i use LDAC codec with s22 ultra and Sony WF-1000XM4 ? In the developer options i can't, even if I select LDAC, it remains on AAC ? Any ideeas please ? Thanks a lot
You don't need to go to developer options. Open Bluetooth settings, find the XM4, tap the settings wheel and select LDAC codec (you need to have the headphones connected to activate this option)
That stumped me as well when I first tried activating LDAC as well on my Soundcore Liberty 3 earbuds. xsam123 is correct
Perfect, it works ! Thanks !
Hi!
If you have any other problems with LDAC, even with using developper option, don't waste you time any further.
(I've spent so much time to correct the issue in this way)
Developer solution's won't work.
And you'll not have the choice to enable LDAC in Bluetooth normal user setting
Reboot your Xiaomi with hard reset.
Everything will become clear and operational.
LDAC Choice will appear correctly again.
Best regards
Be sure HD audio is enabled as LDAC codec in the bluetooth device info, in the bluetooth connection app.