Related
Hi to all Devs and Pros here in the Forum,
I have recently been staying at a friend who owns an iPad and has a setup where he listens to all his music on his iPad and Online Radio via A2DP streaming to his Stereo via a relatively cheap belkin Bluetooth A2DP receiver.
The quality is absolutely perfect and ti sounds as though he has a wired connection.
I had my Iconia with me and also gave it a try. Unfortunately the sound quality was best said acceptable and nothing near the one of the iPad.
So I did some googling about it and found out that A2DP supports various codecs but only enforced one: SBC which seems to be a rather low quality option.
So my guess is Android / our Iconia is only using the SBC codec instead e.g. MP3 which is supported by most HW A2DP receivers todays (also the cheaper ones)
I found that there is a possibility to allow non-SBC codecs in Android to some degree by changing the following settings in '/system/etc/bluetooth/audio.conf'
Code:
[A2DP]
SBCSources=[COLOR="Red"][0|1][/COLOR]
MPEG12Sources=[COLOR="Red"][0|1][/COLOR]
I tried this but when enabling the MPEG12Sources I am not able to connect to any A2DP device at all (I tried 2-3 different ones).
On some place I read that to use e.g. MP3 as a codec license fees for the device manufacturer would apply.
So here are my questions:
Could it be that Acer has simply left this unimplemented? If yes do we have any chance to add this somehow to the system?
Or is it possible to change the settings for SBC to a higher quality?
I am looking forward to any of your thoughts or ideas about this...
/schaze
schaze said:
Hi to all Devs and Pros here in the Forum,
I have recently been staying at a friend who owns an iPad and has a setup where he listens to all his music on his iPad and Online Radio via A2DP streaming to his Stereo via a relatively cheap belkin Bluetooth A2DP receiver.
The quality is absolutely perfect and ti sounds as though he has a wired connection.
I had my Iconia with me and also gave it a try. Unfortunately the sound quality was best said acceptable and nothing near the one of the iPad.
So I did some googling about it and found out that A2DP supports various codecs but only enforced one: SBC which seems to be a rather low quality option.
So my guess is Android / our Iconia is only using the SBC codec instead e.g. MP3 which is supported by most HW A2DP receivers todays (also the cheaper ones)
I found that there is a possibility to allow non-SBC codecs in Android to some degree by changing the following settings in '/system/etc/bluetooth/audio.conf'
Code:
[A2DP]
SBCSources=[COLOR="Red"][0|1][/COLOR]
MPEG12Sources=[COLOR="Red"][0|1][/COLOR]
I tried this but when enabling the MPEG12Sources I am not able to connect to any A2DP device at all (I tried 2-3 different ones).
On some place I read that to use e.g. MP3 as a codec license fees for the device manufacturer would apply.
So here are my questions:
Could it be that Acer has simply left this unimplemented? If yes do we have any chance to add this somehow to the system?
Or is it possible to change the settings for SBC to a higher quality?
I am looking forward to any of your thoughts or ideas about this...
/schaze
Click to expand...
Click to collapse
I changed the MPEG12Sources to 1 and I can connect my Nokia BH-214 and it works fine.
The OnePlus 5 has those 3 options but I do not know the difference between them or which is best to use. Any help would be appreciated. Thank you!
+1
Both the phone and Bluetooth device have to support AptX for it to work, so often your issue resolved by that.
AptX will provide better sound than SBC. SBC is the default codec used by the A2DP Bluetooth profile.
So, in short, if your headphones/speakers have AptX, use that. If they don't, SBC.
What happens if you choose aptX if your device doesn't support it?
yubimusubi said:
What happens if you choose aptX if your device doesn't support it?
Click to expand...
Click to collapse
It will probably just switch to SBC so the connection will work, as that's the baseline standard in Bluetooth. I couldn't say with absolute certainty, as my OP5 hasn't arrived yet.
AptX is a proprietary thing - someone other than the Bluetooth consortium developed it and licenses it. That's why not everything has it - you have to pay to use it in the products you make. They created AptX because the default Bluetooth audio profile pretty much sucks when you start to examine how it butchers bit depth and sample rates just to cram audio data across a low power wireless signal.
On the flip side of that coin - yeah, AptX is better (and I'd use it if both devices supported it) but the audio quality differences are probably not going to readily apparent when listening to $20 to $50 Bluetooth devices. It's been my experience that it takes a somewhat trained ear and better-than-good equipment to be able to easily spot the difference. So, if you're an audiophile, you probably already know to stay away from Bluetooth for the best quality sound. If you're not an audiophile, try to use the best Bluetooth profile you can, but don't sweat it too much.
The A2DP profile is negociated at pairing and the best supported by both devices is picked (SBC < AptX < AptX HD). Problem is that the codec is just one link in the whole daisy chain. Other equally important aspects:
- music source quality (don't expect 128 kbps CBR mp3 to sound good)
- DAC and amplifier (each and every sound system that converts bits to sound has these!)
- speakers (from those in IEM's to those in BT boom boxes - they are all speakers)
So just that you're using AptX doesn't imply you are listening to high quality sound and probably implementing AptX and putting its logo on the product is the cheapest and least development intensive way to raise the price of a product.
Just my two (euro) cents...
Hi,
The question here is how the phone behaves when a higher quality codec has been selected (eg aptX) and a standard bluetooth headset (SBC - only )has been connected?
So far it seems to work (but then the question is why there is a selection available)
Best Regards
Joerg
My wild guess is that tis setting acts like a low-pass filter threshold. The phone will negotiate the highest available option without going above setting.
If the setting is AptX, the phone and speaker support AptX HD, the connection will be made at AptX quality. If the speaker only supports SBC, the connection will be made with SBC.
Honestly I don't see the point in such a setting. 99% of the people would want the best quality available anyway.
Is there a power consumption difference?
Sent from my ONEPLUS A5000 using Tapatalk
daniel_loft said:
My wild guess is that tis setting acts like a low-pass filter threshold. The phone will negotiate the highest available option without going above setting.
If the setting is AptX, the phone and speaker support AptX HD, the connection will be made at AptX quality. If the speaker only supports SBC, the connection will be made with SBC.
Honestly I don't see the point in such a setting. 99% of the people would want the best quality available anyway.
Click to expand...
Click to collapse
It makes sense to have the setting *if* for some reason you want to force SBC or the non-HD aptX. I have it set to aptX HD right now and it seems to work with my car (I'm about 95% sure it doesn't support aptX).
The real question is, if it fails back appropriately, why on Earth would OnePlus set the *default* to SBC?
@aa_chow: There surely is a consumption difference. SBC was designed decades ago with low computational complexity in mind (among others). On the current smartphone hardware (which is probably on par with a medium desktop from 5-6 years ago) the difference would be so small that measurements are impossible (you might see a difference on the battery life of the speakers, but I wouldn't loose my time there) .
@yubimusubi: I cannot even find the reason why that setting is even there! It only limits the best usable codec, which makes no sense to me. Maybe you can find more answers on the oneplus forums.
lag
with the sb, i experience music lag from when i have played in 1 minute and it continues, is it low power consumption or something on sbc? I'm gonna try the apex option when i get home to check if its better.
I'm suffering micro breaks on HD audio (320 bitrate MP3) from aptX HD, aptX or SBC.
Is there a way to correct it?
All my files are stored at 320 and I doesn't have time to convert to a bitrate of 128
Edit: No issues with iPhone 7+ and Huawei P10 using the same BT headset and MP3 files
bartito said:
I'm suffering micro breaks on HD audio (320 bitrate MP3) from aptX HD, aptX or SBC.
Is there a way to correct it?
All my files are stored at 320 and I doesn't have time to convert to a bitrate of 128
Edit: No issues with iPhone 7+ and Huawei P10 using the same BT headset and MP3 files
Click to expand...
Click to collapse
I have an issue on my International LG G6 where it sounds like the 24 bit lossless tracks are essentially dropping frames to borrow a gaming term. Then it will correct itself. It happened on my VW and the problem persists in my wife's new Subaru.
The LG G6 sports Aptx HD. Any ideas?
i prefer aptX but then again ive been using it quite a while now
APTX-HD do not work on One Plus 5. The music hacks constant.
Hi,
I've the OP5 128 GB, in the setting and advanced, we have an option Bluetooth audio codec. In this step we have 3 codec we can try :
* aptX HD
*aptX
*SBC
By default, SBC is select, but do you have try others ? what's the best ?
Sometime, i loose the bluetooth connection in my car and i must to off/on the connection.
Thank you.
Jarrod
http://www.mobilefun.co.uk/blog/2017/02/our-guide-to-aptx-and-aptx-hd-everything-you-need-to-know/
When this was brought up before: https://forum.xda-developers.com/oneplus-5/help/whats-to-aptx-hd-aptx-sbc-bluetooth-t3627794
tl;dr set it to aptX HD and hope it falls back gracefully when not supported. No idea why it wasn't set as default...
I don't think the Bluetooth connection issue with your car has anything to do with the codec. Mine has trouble connecting every time regardless of what is picked. It is really frustrating, so hopefully it'll improve with a future update...
Depends on which codec your headphones supports of headphones supports aptxx
Sent from my ONEPLUS A5000 using Tapatalk
If your device supports Aptx (like some High-Rez Audio headseats), go for it .
If not select SBC
Aptx HD in only for Bluetooth 5.0 devices (actually no headsets or car audio system are available on the market with this feature)
Pouic said:
If your device supports Aptx (like some High-Rez Audio headseats), go for it .
If not select SBC
Click to expand...
Click to collapse
Why not just select aptX[ HD] and let the devices negotiate down if it's unsupported?
Hmm my Sony XB650BT seems to connect using aptx hd. It doesn't appear to step down, but maybe it's playing aptx but still on aptx hd? The headset lists that it is aptx.
yubimusubi said:
Why not just select aptX[ HD] and let the devices negotiate down if it's unsupported?
Click to expand...
Click to collapse
Unfortunately no because most of the time the AD2P protocol will choose SBC as the default codec if the codec you chose (aptx or aptx hd) is not compatible/available
Edit
Pouic said:
Unfortunately no because most of the time the AD2P protocol will choose SBC as the default codec if the codec you chose (aptx or aptx hd) is not compatible/available
Click to expand...
Click to collapse
As far as I know this is true and matches my experiences bouncing between aptX in my car and my non aptx Bose qc 25..
Sent from my OnePlus 5 using XDA Labs
I got the Oreo update and in developer options you're supposed to be able to change the codec, samplerate and a few other things to improve Bluetooth audio. However when I select a codec it doesn't change. It defaults to aac. I wanted to use Ldac. Tried aptx hd and Samsung hd as well and they don't work.
I have the same issue. When you select for example, AptX, the settings don't seem to stick.
Any suggestions? Thanks!
Same here on S9+ cant change codec, always goes back to AAC
jUsT2eXy said:
I have the same issue. When you select for example, AptX, the settings don't seem to stick.
Any suggestions? Thanks!
Click to expand...
Click to collapse
Try deactivating Bluetooth, then change the codec. Should work. Cheers
Which codec is best? AAC was my default.
Sent from my SM-G965F using Tapatalk
Apt-X is the best. That being said, the bluetooth device you connect too has to be compatible. Maybe that's why it switches back to AAC for you. (It sticks to apt X in my case)
Same problem here, it doesn't seem to stick. Even if I disable bluetooth. After closing and re-opening developer options it reverts back to SBC.
Any fix?
For me it only changed when a device was actually connected
Mine does not stay after I change it, it goes back to SBC.
Yo, everyone. I use a sennheiser gt 4.40 with aptx with s8. If you want to enable aptx. first go to BLUETOOTH settings, click the 3 dots. disable the duo bluetooth audio and then go to the developer settings, you will see it's working. but to be honest, I find no difference between these. LOL
Cheers
starfishhaha said:
Yo, everyone. I use a sennheiser gt 4.40 with aptx with s8. If you want to enable aptx. first go to BLUETOOTH settings, click the 3 dots. disable the duo bluetooth audio and then go to the developer settings, you will see it's working. but to be honest, I find no difference between these. LOL
Cheers
Click to expand...
Click to collapse
Finally! Disabling dul audio is what allows the setting to work on my Note 8. Using Forza Metallo headphones there is a VERY noticeable improvement when using aptx!
The audio codec is switching back from LDAC because your bluetooth headphones/speaker doesnt support LDAC. Same would be the case with APTX HD.
starfishhaha said:
Yo, everyone. I use a sennheiser gt 4.40 with aptx with s8. If you want to enable aptx. first go to BLUETOOTH settings, click the 3 dots. disable the duo bluetooth audio and then go to the developer settings, you will see it's working. but to be honest, I find no difference between these. LOL
Cheers
Click to expand...
Click to collapse
My problem is my stereo in my car is older and needs to use the SBC codec to stay connected with any reliability, but the phone automatically switches back to AAC when it connects to it. If I switch it back to SBC after it connects I have no connectivity issues but if I leave it on AAC it disconnects every 5 mins, won't display some track information, etc.
Duo bluetooth audio is not enabled, I have changed settings with both bluetooth and duo audio off. It will accept the change to SBC, but it reverts back to AAC when the stereo connects. The phone will not accept any change to any other bluetooth developer option either, when I exit the developer options and go back in they all are reverted back from my changes. Quite frustrating.
starfishhaha said:
Yo, everyone. I use a sennheiser gt 4.40 with aptx with s8. If you want to enable aptx. first go to BLUETOOTH settings, click the 3 dots. disable the duo bluetooth audio and then go to the developer settings, you will see it's working. but to be honest, I find no difference between these. LOL
Cheers
Click to expand...
Click to collapse
Just logged cause of this solution, thank you comrade, this solved the issue.
on the s9 plus u can only change to profiles whilst playing sound through the bluetooth headphones and only codecs the headphones support. when you re-pair it will auto select the best codec the headphones support anyway so no need to change it at all. i would leave this setting alone unless you want to dowbscale the codec (as it picks the best one for your bluetooth device)
Codec change on S8 does not stick
I have tried the dual audio status trick mentioned above for Note 8, but it doesn't work for my S8. I can select AptX in the developers section, but when you return to that section, the codec selected reverts to SBC. I have a pair of earbuds that supports AptX. Is Samsung pulling a fast one on us?
frankfrank1 said:
I have tried the dual audio status trick mentioned above for Note 8, but it doesn't work for my S8. I can select AptX in the developers section, but when you return to that section, the codec selected reverts to SBC. I have a pair of earbuds that supports AptX. Is Samsung pulling a fast one on us?
Click to expand...
Click to collapse
Worked for my s8. I am using it with a fiio q5. Aptx sticks after duo audio disable.
My S7 kept reverting back to aptx after I used LDAC With mij Sony 1000mx2.
There is an extra setting in the bluetooth settings for that headphone (tap the little)cog) to enable LDAC.
Switching that on worked for me.
where is this setting Dul Audio?
Sennheiser aptX HD
Hi all,
I can choose all the settings in my Umidigi A1 Pro but when connecting BT settings go back to default SBC. Android 8.1 has as far as I can see no more 3 dots or dual playback.
Default:
avrcp 1.4
sbc codec
44.1 khz
16 bit
stereo
ldac default=best
https://forums.oneplus.com/threads/...ault-setting-after-5-1-0-update-in-5t.821840/
According to this topic in the Oneplus forums, it has been down by design. Is there a mod or something that you can do in order to unable it?
saar17 said:
https://forums.oneplus.com/threads/...ault-setting-after-5-1-0-update-in-5t.821840/
According to this topic in the Oneplus forums, it has been down by design. Is there a mod or something that you can do in order to unable it?
Click to expand...
Click to collapse
No, since otherwise, your headphones wouldn't work. You can't use AptX HD on a headphone that only supports AAC or SBC. If your headphones support both AptX and AAC, the system will let you change that. The same goes for the rest of the settings. Every BT headphone supports the SBC standard, headphones that are Apple branded (AirPods, Beats) and others use AAC and higher priced BT headphones with Qualcomm chips support AptX (HD) and AAC. Higher end Sony headphones use LDAC. All of these support the lowest quality standard SBC. There's absolutely no need to any of these, since it would just break things.