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
Related
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?
I have no clue where the perfect forum section for this would be so I do it here and hope people find it.
Especially Nvidia devices seem to suffer from a problem that can drive you nuts if you are a power user.
But I had the issue with a few other chipsets and amps as well.
The problem seems to always look like this:
After some use you put your device in sleep mode, turn the TV/monitor off and when you want to continue there is no sound.
All drivers and hardware seem to perform normal and nothing you do bring the sound back until you restart.
Usual recommendations from the web, Nvidia forums, MS and dedicated tech sites include:
Installing a different driver
Using full featured and quality cables
Searching for drivers and services that might interfere
Getting new graphics card or upgrading the TV/monitor
None of the above really works or makes and difference if you ask me.
The fix on many modern TV's is simple and some monitors should have similar settings available.
For me the trick works like this:
Check the HDMI setting on the TV/monitor.
For the affected input you are likely to find something to change/activate/de-activate HDMI 2.0.
Usually this setting is set to auto mode and the system should use the right setting once a HDMI device connects.
And there is the culprit of the implementation for (mostly) Nvidia devices!
Sound will be activated after a video signal is established but the card will do the HDMI settings after establishing the video.
In the meantime the sound part fails to initialise.
Changing the TV HDMI setting from AUTO to anything else will fix the issue.
Of course it makes sense to first check if your device fully supports and uses HDMI2.0, if so enable it otherwise disable it on the TV.
Now, when coming from sleep the sound shouls always be active.
What exactly happened and why does it work?
HDMI2.0 mainly provides a higher bandwidth, so all quality HDMI1.4 cables and equippment will work just fine.
But to make it work both ends must use the same standards.
Some chipsets like Nvidia like to negotiate the standards for best possible performance.
This goes something like that:
Graphic system is activated
Check for HDMI connection, multiple standards supported
Set resolution as reported from the TV
Enable sound
Check HDMI standard and if HDMI is supported switch from 1.4 to 2.0.
The last step here is what messes things up.
It seems that even if the standard remains unchanged the sound will be initialised again but fails to know where to go.
If the HDMI settings on the TV are fixed instead of being set to AUTO it goes like that:
Graphic system is activated
Check for HDMI connection, fixed setting
Switch to the set HDMI standard
Set resolution as reported from the TV
Enable sound
A tiny difference in the approach and the sound finally knows where to go
Special case, amplifiers...
For Nvidia the same problem happens if you have an amp connected for better sound.
There are different ways to connect an amp these days.
Sometimes the amp passes the HDMI signla through and hijacks the audio signal only.
Sometimes you use a dedicated output from your device for the amp.
And in rare cases you feed the amp back from the TV with a dedicated amp output.
The possible options for failure are a bit higher as you can imagine by the number of combinations.
Either way the approach is the same.
If you can change the HDMI settings on the amp then check there first.
After all it could be that the amp tries to negotiate the right standard.
If not then again check on the monitor/TV and change the HDMI setting from auto to something else.
If you use a dedicated sound output on your device, even if it is optical, then please make sure it is set as the default audio output.
Even better, if you only use the amp for sound and make no use of the sound coming over HDMI then disable the sound for HDMI completely.
This way the HDMI output won't get priority or be mixed in, which can often cause crackling sound.
Been using the Pixel 3 as my daily driver for a while now, but just recently came an interesting piece. Apparently, the Pixel 3 doesn't support LDAC at Optimum Audio Quality (more details here - https://themrphone.com/article/google-pixel-3-xl-doesnt-support-ldac-at-optimum-audio-quality/)
I was planning on buying a high-end set of Bluetooth headphones, in fact, was considering the same ones used in the link above. Can anyone else confirm this?
varounmirchi said:
Been using the Pixel 3 as my daily driver for a while now, but just recently came an interesting piece. Apparently, the Pixel 3 doesn't support LDAC at Optimum Audio Quality (more details here - https://themrphone.com/article/google-pixel-3-xl-doesnt-support-ldac-at-optimum-audio-quality/)
I was planning on buying a high-end set of Bluetooth headphones, in fact, was considering the same ones used in the link above. Can anyone else confirm this?
Click to expand...
Click to collapse
Working fine for me with both LDAC (detected and used automatically) and "Optimised For Audio Quality" (switched from default "Best Effort" in Developer Settings)
Pixel 3 (non XL) with Sony MDR-1000X (gen 1 of the headphones in your linked article) and Google Play Music.
Granted GPM isn't a Hi-Res source, but it's playing fine! There was a momentary drop in audio for a split second on changing bit rate but it resumes with no issue!
I had this same issue with my Audeze Mobius--the Pixel 2 allowed me to set the rate to 990, but the Pixel 3 would do as described in the link. Seems like a software bug, I doubt it actually isn't capable of using the full rate
I can't say, I'm much of an audiophile or anything but I do like to play with settings for what sounds best with what I have. On my Galaxy s8 running oreo and my previous s5 running aospx/oreo I could change the developer Bluetooth settings on the fly and notice the difference instantly (avrcp/bt_codec/sample_rate/bit_rate/ldac_codec).
If I do it on the pixel 3, the Bluetooth just falls out, connection wise it stops but still shows it's connected, app wise I can't close and reload the app. I have to turn the Bluetooth off or reset it completely sometimes.
It's kind of a bummer, being a brand new phone and all, I noticed the absolute volume disable didn't seem like a difference either.
I hope they resolve it.
Update: disabling bluetooth a2dp hardware offload let me freely change all those settings while in use with out locking anything up. What that necessarily does or the effect of changing the settings and how well they actually change??? I can't answer with any rational or testworthy explanation as my audio products are oem Bluetooth radios in vehicles.
So I've been beating myself up trying to accomplish this, using every everything from JaDx to APK editor Pro and getting nowhere. Okay here's what I'm trying to accomplish I had an LG Phoenix 5 and it... well it no longer functions. it was just a cheap $40 phone BUT it had a fully loaded Bluetooth Developer menu section that had every option available and never had grayed out dot, even the HD audio option. It didn't matter what I paired it to (high or low end devices) it always worked. I could always make Bluetooth speakers sound better than anybody. So now I have a Motorola G Pure it's still a cheap device but still cost more than the Phoenix. It has almost no Bluetooth option that are sound quality related available just grayed out dots even on devices I know the option work on. so I set out to mesh together the Bluetooth controller apps from both devices and well its not going to well.
it could be a hardware limitation... but I've been seeing a lot of companies claiming hardware limits when they really just don't want you using something a certain way (I.e.Windows 11) or the fact that the control app (uncompressed) is 3x smaller than the Phoenix 5's was.
any insight or advice help would be awesome.
try this app :
Wavelet: headphone specific EQ - Apps on Google Play
Headphone specific equalization with lots of customizability
play.google.com
made by the dev of viper4android, runs with adb, might be a solution
Hi everyone,
I have paired my OP 9 with my Cambridge Audio Melomania Touch Bluetooth earphones as soon as I got the phone, about eight months ago.
The phone has received several updates and upgrades in the meantime, but an issue has surfaced recently, as the title indicates: when I'm in a public place and there are other BT devices around, the music playing from the phone into my earphones suffers interruptions and distorsions, as if the phone was trying to pair with those devices, or maybe the Melomania Touch, I don't know.
I'd tend to think it's the phone, because I've had those earphones for about two years now, and with my previous phones (Xiaomi/Poco, Samsung), I never had such an issue. Once paired, the devices would deliver a solid, steady sound, with the occasional hiccup if the phone was in my pant pocket and I turned my head in the opposite direction, but that was it.
With the OP 9, however, every time I'm on the bus or the tram, or even waiting at the bus stop and a car passes by, I hear an interruption in sound delivery and I know the car in question had BT enabled.
In the Bluetooth settings, I've unchecked the option to make my phone visible by other devices, and in the Developer options, I've limited the number of devices the phone should try to connect to to 2, the Melomania Touch (it used to be 3, the third device being a Sony WH-700 BT headset I have at home, but I cleared it from the list).
I don't see any other settings to play with to make this inconvenience go away, and the Melomania Touch app doesn't offer any option either. The earphones are set to deliver max performance (not Low Energy BT).
I'm counting on you guys on this one!
Have to tried to enable HD audio (AAC) from that device's Bluetooth settings?
shadabkiani said:
Have to tried to enable HD audio (AAC) from that device's Bluetooth settings?
Click to expand...
Click to collapse
Hi and thanks for taking the time!
Yes, HD Audio is enabled, though I found it in the Developer options. BT options are pretty basic on this phone, if you ask me, but sound quality is really good, especially with those earphones.
UglyStuff said:
Hi and thanks for taking the time!
Yes, HD Audio is enabled, though I found it in the Developer options. BT options are pretty basic on this phone, if you ask me, but sound quality is really good, especially with those earphones.
Click to expand...
Click to collapse
Hmm... I don't know what could be the issue then. Maybe someone else with more knowlege can give more suggestions...