I have an issue as described in the title on all Lollipop ROMs on my OnePlus One (Bacon). It is affecting me hugely as I am used to listening to Spotify/Google Music through a Bluetooth interface and it is totally broken. The audio skips/glitches all the time. The problem is always present to some degree (a skip every 10-20 seconds or so), sometimes being so bad that audio is actually totally broken and only glitches are present. The car audio I use is Toyota Touch (1st gen as far as I can tell). Curiously, phone calls and system notifications seem to not be affected. Only music is broken. The problem was absent on CM11S.
Anyway - I have already tried all the suggested workarounds that I could find, both on XDA (like this one: http://forum.xda-developers.com/oneplus-one/help/music-skips-beeps-audio-glitches-t3028166 and http://forum.xda-developers.com/showpost.php?p=58780279&postcount=1691) and elsewhere. I have set CPU setting to "performance" (no change), did all kinds of voodoo with WiFi settings (no change), switched players (NuPlayer vs AwesomePlayer - no change).
I have tried a bunch of ROMs - CM12 nightlies (close to all of them), Oxygen, Exodus. (which I am using right now) - no change. I have switched kernels. I am now on Franco Kernel, but I have used AK and some other variants which I can't even remember. None of this makes a difference in my case. Skips continue
Today I started digging a bit deeper. I ran logcat while listening to music and it turns out that there are entries like this in the log at the moment of every glitch:
Code:
04-09 17:44:02.487 3016 3105 E bt-btif : ## Audio Congestion (iterations:23 > max (10))
04-09 17:44:04.883 3016 3105 E bt-btif : ## Audio Congestion (iterations:30 > max (10))
04-09 17:44:24.736 3016 3105 E bt-btif : ## Audio Congestion (iterations:22 > max (10))
04-09 17:44:29.043 3016 3105 E bt-btif : ## Audio Congestion (iterations:53 > max (10))
04-09 17:44:30.547 3016 3105 E bt-btif : ## Audio Congestion (iterations:54 > max (10))
04-09 17:44:32.161 3016 3105 E bt-btif : ## Audio Congestion (iterations:52 > max (10))
04-09 17:45:14.066 3016 3105 E bt-btif : ## Audio Congestion (iterations:47 > max (10))
04-09 17:45:15.166 3016 3105 E bt-btif : ## Audio Congestion (iterations:21 > max (10))
Being a software engineer myself (but not an Android programmer), I have analyzed a bunch of CM12 patches found on XDA related to the above logs. The discussion seems to center around changing the "max" to some larger value. As you can see, the value I have is 10, but it is beeing exceeded by a lot - in some cases it goes above 50! I guess I could try changing the max so high and see what happens (after learning how to build CM12 ), but maybe some experts already know what needs to be done to fix this in my case.
I can offer myself as a test animal - if you want to test your experiments with BT fixes on me, I am more than willing to give them a try. I am really really desperate about this
Have you tried blisspop + linaro unofficial boeffla kernel? this works for me without bt stuttering. I had the bt stuttering problem with the uber version of the unofficial boeffla kernel.
bill1clinton said:
Have you tried blisspop + linaro unofficial boeffla kernel? this works for me without bt stuttering. I had the bt stuttering problem with the uber version of the unofficial boeffla kernel.
Click to expand...
Click to collapse
I'm going to give this kernel a try to see if it resolves the Bluetooth issues while streaming music. Will report back my findings tomorrow.
bill1clinton said:
Have you tried blisspop + linaro unofficial boeffla kernel? this works for me without bt stuttering. I had the bt stuttering problem with the uber version of the unofficial boeffla kernel.
Click to expand...
Click to collapse
What does this combination of ROM+kernel fix? Do they somehow explicitly addressed the issue?
Anyway, where do I get this kernel?
kalamon said:
What does this combination of ROM+kernel fix? Do they somehow explicitly addressed the issue?
Anyway, where do I get this kernel?
Click to expand...
Click to collapse
It does not specifically states that it fixes the bt stuttering problem. I only stated that when I use the blisspop+uber combination, I had the stuttering problem but once I switched to the blisspop+linaro combination, the problem was no longer present.
http://forum.xda-developers.com/one...ernel-boeffla-kernel-linaro-sabermod-t2910357
In having this same issue, but with headsets, not Bluetooth specifically.
I changed from Awesome Player to NuPlayer in developer options and now my music plays smoothly, no matter what I'm doing simultaneously.
That Wolf Dude
Related
I thought it would be nice if we cfoudl get some Q&A going about this topic.
I'd like to hear which Tornado ROMs seem to have good working A2DP, which BT stack they use (if you know), what headset/remote you're using.
I'd also like to know if anyone can give use directions for checking what stack our phone is using.
I'd also like to know your opinions on volume, hiss, etc.
If you are satisfied or unsatisfied with your volume, please include your audiogain settings for comparision:
HKLM\SOFTWARE\HTC\AUDIOGAIN
(note: audiogain settings are in hexidecimal)
Here is some info on A2DP reg tweaking, that is supposed to be relevant to the WM6 bt stack.
i.e. from the "final" or "official" released, not a beta.
[ Default Settings are as follows: ]
HKLM\Software\Microsoft\Bluetooth\A2DP\Settings\
BitPool DWORD 30
MaxSupportedBitPool DWORD 30
SampleRate
UseJointStereo DWORD 1
HKLM\Software\Microsoft\Bluetooth\AudioGateway\
Capability DWORD 37
[ Aternate Settings: ]
HKLM\Software\Microsoft\Bluetooth\A2DP\Settings\
BitPool DWORD 51
MaxSupportedBitPool DWORD 60
SampleRate DWORD 48000
UseJointStereo DWORD 0
Cant remember if i changed the one below or it was already at that value.
HKLM\Software\Microsoft\Bluetooth\AudioGateway\
Capability DWORD 60
-----------------
[ Sleuth255's WM6 optimum settings for bluetooth A2DP: ]
These are applicable to the newer releases of WM6.
Finding #1:
ADD/CHANGE the following values from the registry at HKLM\Software\Microsoft\Bluetooth\A2DP\Settings :
Name: UseJointStereo
Value (DWORD): 1
What this does is enable Joint-Stereo for the SBC codec, which is important and makes the biggest significant change to improve sound quality. (Note: In earlier versions of WM5 and WM6, Joint-Stereo was broken and resulted in a mono-output. This is not the case anymore with the newer WM6 ROMS.)
Further note: Sleuth255 found that some of his A2DP headsets could not work with JS turned on. In that case, you have to set the value to 0 to disable JS (resulting in poorer quality sound with more "hissing").
Finding #2:
REMOVE the following values from the registry at HKLM\Software\Microsoft\Bluetooth\A2DP\Settings if they are present:
- BitPool
- MaxSupportedBitPool
These values are used to manually set limits for the BT stack for the A2DP SBC codec. Previously, it was thought that these values should be set between 38 to 86. But if the values are removed, I think that the BT stack automatically chooses the best BitPool values for maximum quality. I've tried removing these values and the sound quality either improved or at least stayed the same.
[ SUMMARY ]
At this point, you should have only one value in the registry at HKLM\Software\Microsoft\Bluetooth\A2DP\Settings:
UseJointStereo = 1
Your A2DP audio should be very good at this point - almost indistinguishable from a wired headset. However, if you are still unsatisfied with the sound (you may notice some very slight "hissing" or "swishing" sounds on high frequencies of certain songs), you may want to try the optional setting below.
[ OPTIONAL ]
Finding #3:
This is optional, and a matter of preference.
ADD the following value to the registry at HKLM\Software\Microsoft\Bluetooth\A2DP\Settings:
Name: SampleRate
Value (DWORD): 48000 (decimal)
This forces the A2DP stack to send the audio to the headset at 48000Hz instead of the default 44100Hz. For some reason, I find that the 48Khz value makes the "hissing" sounds less obvious. Your findings may vary, as some people may prefer the slightly more forward sound of the original setting. But if you are game, give this a try - one thing for sure is that it definitely changes the sound quality.
To reverse the change, just remove the SampleRate value.
If you make this 3rd optional change, you should have the following values in the registry at HKLM\Software\Microsoft\Bluetooth\A2DP\Settings:
UseJointStereo = 1
SampleRate = 48000
[ Note - Quick tip on registry editing ]
Of course, every registry change needs a soft-reset to take effect. And please take the usual proper care when editing the registry or risk damaging your device.
Find that your settings dont "stick" after a reset?
Make sure you reset the phone like this: After making changes to the registry, exit your registry editor. Then push the power button of your phone (putting it into standby, with the screen off). Wait for about 10 seconds (the phone will be saving the data to disk during this time), and only after that push the reset button.
Click to expand...
Click to collapse
I like to quote my sources, but I don't have the links at this moment. I will update them later.
Varied...
My experience across four or five builds has always been mixed. My older Motorolas work fine but my newer S9s dropout periodically. Interestingly, not all builds have the same result when I use them for handsfree. Some builds give me the voice I am speaking to in mono and some in stereo. Currently I am using Nitro's build from a month ago.
I have already exchanged the S9s once, so it wasn't specific to that one headset.
Exitao - Do you have dropouts periodically? What headset do you have?
kkrull said:
My experience across four or five builds has always been mixed. My older Motorolas work fine but my newer S9s dropout periodically. Interestingly, not all builds have the same result when I use them for handsfree. Some builds give me the voice I am speaking to in mono and some in stereo. Currently I am using Nitro's build from a month ago.
I have already exchanged the S9s once, so it wasn't specific to that one headset.
Exitao - Do you have dropouts periodically? What headset do you have?
Click to expand...
Click to collapse
Sorry, I was intending to post my personal details soon.
I am using a Sonorix C3
Standards Bluetooth Specification V2.0
RF Frequency Range 2402 ~ 2480 MHz
Profiles Supported A2DP, AVRCP, Headset, Handsfree V1.5
Transmission Power 0.25 ~ 2.5mW (Bluetooth Power Class 2)
Receiver Sensitivity < -80dBm (PER 1 %)
Distance 10m (in open space)
Click to expand...
Click to collapse
I am using EA's Chinese "WM6 5.2.318.18120" ROM:
http://bbs.koxo.cn/thread-14687-1-1.html
Currently my headset (well, the remote dongle, really) supports stereo playback, call display and bt handsfree usage.
Reception seems very clear. Mic pickup is sensitive and noise cancellation seems to be just as sensitive (I was holding the mic in my hand and gesturing madly one day, and realised what I was doing).
My only complain is the volume. I need to muck about in the audiogain settings to increase it.
As for what bt stack I'm using, I have no clue.
If I dump the zip file from this link, http://forum.xda-developers.com/showthread.php?t=263735&highlight=a2dp the bta2dp.dll was last modified on april, 2006. When I look in the windows directory of my phone, it only tells me I flashed it. I guess I have to dump the ROM to find out.
There is also the problem that the WiMP in my ROM can't handle VBR files. I'll be updating to vjgrace's 3.5 ROM shortly.
edit:
No dropouts. Mostly it is a fight to manage system resources on the phone.
any ppl know how yo make when the phone ringtone can ring in bluetooth.
mean we can listen the ring tone from bluetooth.
Here is the info I posted over at Rootz, thought I'd better post it here too for reference. Not sure if it was just mine, or if this happens to everyone.
Using Build 32, any music player (Music, Winamp), MusicFX & Bluetooth headset (I think it did it while wired too), I get constant drop outs of audio. At first I thought it was the Bluetooth radio, so I flashed multiple radio's but the problem always persisted.
I finally found that by switching to Google Play Music (CM9 Music is such a CPU hog!) and DSP Manager from this thread fixes things just nicely. No more drop outs and a music player that works properly with all 3 of my BT devices (2 vehicles and a headset).
I'm not sure if the problem was device specific or not, but now it is at least fixed!
I wouldn't use DSPManager. We have Wolfson chipset and Voodoo control app for that.
build 33 change log
1st item
bug fixes
- Bluetooth: Fixed memory leak and file handles leak
Will have to try an unmodified Build 33 early in the week and see if the issue is resolved.
Edit 10/28/2012: I tried replacing all files in /system/etc/bluetooth from the ones from CM9 and CM10. It still does not work. So fail for me. I also tried solution recommended in post # 2. No go for me.
Background: I have a 2012 Honda CRV and SGS2 Skyrocket (obviously!!) I prefer to use stock rooted deodexed roms with all AT&T bloatware removed. Bluetooth worked perfectly with Gingerbread ROMS.
Issue: As soon as I upgraded to ICS (leaks , Rogers and real deal from AT&T) I started having bluetooth Auto Connect issues. The problem was simple. My phone would never auto-connect to Car Audio. As you know there are two profiles (Settings -> Bluetooth -> HandFreeLink -> Settings) Phone and "Media Audio". Media Audio always autoconnected meaning I could play music etc from my phone to car car stereo. "Phone" never autoconnected. I always had to manually connect.
Debugging: I tried various ROMS hoping something would work. Finally when I tried CM9 everything worked!! Later when CM10 became stable, I tried that as well and it worked. When I say worked it means BOTH phone and Media audo profile autoconnected
Summary:
Bluetooth works perfectly in 1) All GB ROMS, All CM9 base ROMS and all CM10 base ROMS. Does not work in any stock AT&T/Rogers ICS ROMS
Possible Solution??: I tried to figure out what can be the issue and here is what I see
/system/etc/bluetooth/auto_pairing.conf is different in CM9 and Stock ROMS. Here is the difference
Stock ROM
// Blacklisting by Exact Name:
ExactNameBlacklist=Motorola IHF1000,i.TechBlueBAND,X5 Stereo v1.3,KML_CAN,SYNC,UConnect
// Blacklisting by Partial Name (if name starts with)
PartialNameBlacklist=BMW,Audi,Parrot,HandsFreeLink,Car,MB PhoneSystem,CAR MULTIMEDIA,MB Bluetooth
Click to expand...
Click to collapse
CM9
// Blacklisting by Exact Name:
ExactNameBlacklist=Motorola IHF1000,i.TechBlueBAND,X5 Stereo v1.3,KML_CAN
// Blacklisting by Partial Name (if name starts with)
PartialNameBlacklist=BMW,Audi,Parrot,Car
Click to expand...
Click to collapse
To me this would explain why I was facing problems. The bluetooth connection Honda CRV establishes is called HandsFreeLink. For some reasons connections with that name are blacklisted.
Questions:
1) Is this really the root cause of the problem?
2) Will changing the BT connection or fixing /system/etc/bluetooth/auto_pairing.conf fix the issue.
Next steps
1) I will try to run a test. I will rename phone bluetooth connection from "HandsFreeLink" to somethng else and see if that fixes the problem.
I am not confident it will work because some bluetooth address are also blacklisted and AT&T stock list is larger than CM9 so there is a chance that my HondaCRV BT address might be in there. I will report results of test tomorrow.
2) Can a Dev using ICS stock as base replace the conf file and provide a new build? I don't have linux and I noticed several overwriites while I unzipped the CWM zip file indicating that there are symlinks in there and I need Linux to build the new CWM file with file changed
I read this somewhere here on the forums but it has helped me
goto
/system/etc/bluetooth/
edit
audio.conf
uncomment(delete #) these lines
#AutoConnect=true
#[Headset] - not sure if this is necessary but I do it anyway
#HFP=true
below is from cm10
Code:
# Configuration file for the audio service
# This section contains options which are not specific to any
# particular interface
# NOTE: Enable=Sink means that bluetoothd exposes Sink interface for remote
# devices, and the local device is a Source
[General]
Enable=Sink,Control
Disable=Headset,Gateway,Source
# Switch to master role for incoming connections (defaults to true)
Master=false
# If we want to disable support for specific services
# Defaults to supporting all implemented services
#Disable=Control,Source
# SCO routing. Either PCM or HCI (in which case audio is routed to/from ALSA)
# Defaults to HCI
#SCORouting=PCM
# Automatically connect both A2DP and HFP/HSP profiles for incoming
# connections. Some headsets that support both profiles will only connect the
# other one automatically so the default setting of true is usually a good
# idea.
[COLOR="red"]AutoConnect=true[/COLOR]
# Headset interface specific options (i.e. options which affect how the audio
# service interacts with remote headset devices)
[COLOR="red"][Headset][/COLOR]
# Set to true to support HFP (in addition to HSP only which is the default)
# Defaults to false
[COLOR="Red"]HFP=true[/COLOR]
# Maximum number of connected HSP/HFP devices per adapter. Defaults to 1
#MaxConnections=1
# Set to true to enable use of fast connectable mode (faster page scanning)
# for HFP when incomming call starts. Default settings are restored after
# call is answered or rejected. Page scan interval is much shorter and page
# scan type changed to interlaced. Such allows faster connection initiated
# by a headset.
FastConnectable=false
# Just an example of potential config options for the other interfaces
[A2DP]
SBCSources=1
MPEG12Sources=0
[AVRCP]
InputDeviceName=AVRCP
# The Sony car stereo Ford is using under their brand as '6000 CD' has a
# completely broken AVRCP 1.3 implementation. After recognizing AVRCP 1.3 TG
# capabilities and exchanging a few PDUs, the car stereo disconnects and
# reconnects BT, also resetting USB devices if connected to it.
# To avoid that and allow at least HFP and A2DP to work, prevent any AVRCP 1.3
# PDUs from being sent on those models - add the device to the black list.
# Since 2012 Ford models have it fixed, removing the device from the list
# will result in full functionality.
MetaDataBlackList=Ford Audio
reboot and test, it solved my autoconnect issue.
Hope this helps
This did not work for me. I tried replacing all config files as well and phone does not auto connect. Strange since CM9 and CM10 work perfectly.
Hi all,
I just got the OPO few days ago and I'm having issues with bluetooth. I use bluetooth in my car to stream music. Everything was working fine on my Nexus 5.
On the OPO i can connect without problems but when playing some music there is some strange stuttering and skipping of music...
Anyone also having this issue ?
I'm thinking this is a software bug as I found out that CM had a lot of issues with bluetooth stuttering...
Bump ?
I haven't had any issues. I've probably steamed at least 12 of audio over Bluetooth so far this week. Being CyanogenMod, I'm not sure if it supports aptx or just a2dp. Either way, no issues here.
Sent from my One using XDA Premium 4 mobile app
What rom? Did you change performance settings? Installed Viper4Android? Anything not stock?
fwiw I found that V4A caused issues with certain settings (convolver enabled, clarity) if low max screen-off frequency was forced. Otherwise my BT doesn't skip at all or lag on two sets of speakers, Sony MDR-1RBT headset and a car stereo.
Does your previous phone have the same prob?
CrashTestDroid said:
What rom? Did you change performance settings? Installed Viper4Android? Anything not stock?
fwiw I found that V4A caused issues with certain settings (convolver enabled, clarity) if low max screen-off frequency was forced. Otherwise my BT doesn't skip at all or lag on two sets of speakers, Sony MDR-1RBT headset and a car stereo.
Does your previous phone have the same prob?
Click to expand...
Click to collapse
I'm now on Mahdi ROM and I have the same issue. I'm streaming via bluetooth into a FM transmitter (http://www.newpotatotech.com/TUNELINK_ANDROID/tunelink_android.html). It was working fine with my Nexus 5.
I don't think I changed anything... I will try to troubleshoot it again, but I think it must be some software bug..
d3sm0nd said:
I'm now on Mahdi ROM and I have the same issue. I'm streaming via bluetooth into a FM transmitter (http://www.newpotatotech.com/TUNELINK_ANDROID/tunelink_android.html). It was working fine with my Nexus 5.
I don't think I changed anything... I will try to troubleshoot it again, but I think it must be some software bug..
Click to expand...
Click to collapse
Same issue here. With a tunelink FM transmitter.
I don't have any problems with a prius Bluetooth and generic chinese navigation system.
Sent from my GT-N5110 using Tapatalk
With the M8 stable rom, the Audio quality is better, the micro stutters are still there though
It's a known bug with CM11 no fix in sight as far as I could find:
https://jira.cyanogenmod.org/browse/CYAN-4147
thelestat said:
With the M8 stable rom, the Audio quality is better, the micro stutters are still there though
It's a known bug with CM11 no fix in sight as far as I could find:
https://jira.cyanogenmod.org/browse/CYAN-4147
Click to expand...
Click to collapse
Atleast we are not alone. Hope it gets fixed soon.
I also have issues with Bluetooth, I use Poweramp as my media player and have it set to autoplay when it connects to BT but when it connects, it plays a brief second and stops. I have to manually play the music.
I also noticed it only sends the first song metadata rather than change every time I play something different... Annoying.
had similar problems with both my S4 and Z1 on CM (using both since one is my private and one my business mobile) Both are now on PAC (7/10/2014) and even before that i did not have the bluetooth issues with them on PAC. try it out - there is a PAC for the One (which i will use as well when mine arrives this week (hopefully))
or try with omnirom - they use a different BT implementation
gl
Cheers
Buster
Buster99 said:
had similar problems with both my S4 and Z1 on CM (using both since one is my private and one my business mobile) Both are now on PAC (7/10/2014) and even before that i did not have the bluetooth issues with them on PAC. try it out - there is a PAC for the One (which i will use as well when mine arrives this week (hopefully))
or try with omnirom - they use a different BT implementation
gl
Cheers
Buster
Click to expand...
Click to collapse
Yep PAC sorted my problems with poor in call bluetooth.:good:
Buster99 said:
had similar problems with both my S4 and Z1 on CM (using both since one is my private and one my business mobile) Both are now on PAC (7/10/2014) and even before that i did not have the bluetooth issues with them on PAC. try it out - there is a PAC for the One (which i will use as well when mine arrives this week (hopefully))
or try with omnirom - they use a different BT implementation
gl
Cheers
Buster
Click to expand...
Click to collapse
Could you give us a link to the PAC ?
Check bacon-1005 on jira and vote it up. Cyan-4147 was reported specifically for the m7 and it's gki_Linux errors. There are some patches I'm testing to isolate the cause of the stuttering. Don't worry you all are not the only ones with the issue.
Cholerabob said:
Could you give us a link to the PAC ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/oneplus-one/development/rom-pac-4-4-4-beta-1-0-t2811990
Ah ok u meant the ROm... lol I thought it was a PAC audio interface
Cholerabob said:
Ah ok u meant the ROm... lol I thought it was a PAC audio interface
Click to expand...
Click to collapse
Yes got to have good bluetooth in call reception, every other rom i tried terrible.
PAC rom bluetooth quality?
Can anyone confirm that PAC rom has fixed the problem of bad quality BT audio?
I am runnig the stock CM rom - now rooted, but the problem has been there all the time since I got the phone. The sound quality is not acceptabe with my Lexus RX 450h handsfree for the outbound call audio, that is I can hear quite well, but the other person can not.
My old phone Galaxy Nexus worked just fine, so there has to be something wrong with OPO's bluetooth.
Guys user: BIOYAM
Found a fix that worked for him and for me. You can try this:
Install SetCPU (I used a free app No-frills Cpu controll) with Governor: Interactive, CPU: Max 2265MHZ & Min 652
This totally stopped my bluetooth audio issues. Of course you need to be rooted to use these tools.
Hope this helps. :good:
Problem solved!
Hey problem solved
I had bluetooth pairing and buffering problems and now everything works perfectly. what I did was flash OPO_OxygenOS_1_0-modem-flashable.zip (you can find it somewhere in google docs..don't remember the link)
anyway after doing that everything works perfectly.
I am running cyanogen 12.1 nightly build from 20150601
then I flashed the modem.
Hi. I use Bluetooth airbuds. recently i found in the developer option that i can change the following settings:
1. Disable Audio A2DP ( OPTIONS ARE: enable/ disable)
2. Bluetooth audio Codec (OPTIONS ARE: SBC/AAC/Qualcomm aptX HD/ Qualcomm aptX HD Adaptive Audio/ Qualcomm aptX TWS+ audio/ LHDC_V3/LHDC_V2/LHDC_V1)
3. Bluetooth audio SAMPLE rate (POTIONS ARE: 44.1kHz/48kHz/88.2kHz/96.0kHz)
4. Bluetooth audio Bits per sample (POTIONS ARE: 16/24/32 bits/sample)
5. Bluetooth Audio Channel mode (MONO/ STEREO)
6. Bluetooth Audio LDAC Codec ( 990kbps/660kbps/330kbps)
7. Bluetooth Audio LHDC ( 256Kbps/ 400kbps/ 500kbps/ 900kbps)
i want to change the settings but it doesnt. when i change the settings it changes but when i close the settings it returns to the default settings. now how to change it and make it working ? thank you for your help.
no one knows about this ? really ? :/
Same issue here
I think only supported setting for both bt tws and phone that can be applied, i've use dual codex tws (kz z1) that use ACC and sbc codec, with both codec only supported 44.1 khz sample rate and 16bits per sample.
When i select AAC/sbc then i close the setting and check it again, the codec is same at last time i selected, but when i select aptx the codec setting is revert back to AAC/SBC again.
1 year late. that cannot be changed. It depends on the compatibility of your phone and the headset.
Use (checker a2dp) apk from Google Play store. Use this link, https://play.google.com/store/apps/details?id=com.widget7.check.a2dp&hl=en ...
it worked for me, using it for years i have redmi k20 pro and used the same software in OnePlus too....
For bit per sample and audio sample rate, we can directly Change it under bluetooth codecs in
developer option as per the music file we are going to play