Currently Being ModeratedMar 26, 2012 3:53 AM (in response to Ferre)
Try playing and pausing the audio. The codec ID may have gotten stuck.
Currently Being ModeratedApr 23, 2012 6:36 PM (in response to Ferre)
I have this exact same problem, with a Creative ZiiSound D5 speaker system. I'm using my MacBook Air's built-in Bluetooth instead of the Creative USB dongle.
It says that the Active Codec is SBC, not aptX. Stopping and starting the audio doesn't help at all. I have a 13-inch Mid-2011 Core i7 Macbook Air, running OS X 10.7.3.
Currently Being ModeratedAug 12, 2012 8:46 AM (in response to Ferre)
Same to me , apt-x is enabled in my macbook pro 13 middle 2009 but not in my iMac 21 early 2011. I dont know how to enbable it here??
Currently Being ModeratedDec 24, 2012 9:43 AM (in response to jamarita)
i had the same initial problem.
sennheiser px 360's freshly connected and working on the macbook pro 15" but after checking the bluetooth icon with "alt click" it seemed they were using sco codec.
However after a mac restart the codec changed to apt x. and has remained since.
then again i cant really hear any significant difference in audio quality.. maybe just a touch more open..
so its not the end of the world if you cant release apt x.. although with mountain lion its there.
BTW.. sennheisr px 360's 9 £70 on ebay) awesome... just dont hit the srs button...eeek.. nasty nasty remove it.
Currently Being ModeratedAug 11, 2013 10:26 AM (in response to Ferre)
It may be necessary to turn on the aptX codec via Bluetooth Explorer -> Utilities -> Special Options
That did the trick for me.
The bluetooth explorer used to be available by pressing option then the bluetooth button, but now its bundled seperatly either with xcode or here : https://developer.apple.com/downloads/index.action?name=bluetooth%20explorer
Currently Being ModeratedOct 28, 2013 4:54 AM (in response to rideMTB)
I used bluetooth explorer as you described and for a while apt-x was working for me when I connected to Nuforce S3-BT speakers.
At some point, and I think it may have been with the most recent OS update 10.9, apt-x no longer seems to be an option for me. My iMac always connects to the speakers using SBC.
But not only that, now the connection to the speakers breaks after a few minutes and once the connection gets broken, the speakers emit a loud tone.
Other devices such as my iPhone4 and iPad3 (not apt-x enabled) connect to the speaker with no issues.
So I'm not sure what happened but apt-x is no longer there for me and even SBC is flakey.
My iMac is literally 2 feet away from the speakers and the connection strength is 100% according to bluetooth explorer.
Currently Being ModeratedDec 1, 2013 10:40 AM (in response to Ferre)
i also have the same problem with my macbook air 13" mid 2012 (with OSX 10.9) :-(
bought a new BT 4.0 speaker with apt-x but my mac does not change to this codec.
i'v deleted every connection which use bluetooth (mouse, keyboard) and also tried the "force to apt-x" option in bluetooth explorer, but nothing did help.
Currently Being ModeratedJan 16, 2014 10:10 AM (in response to Ferre)
apt-X is invalidated by default.
- - - - -
$ defaults write com.apple.BluetoothAudioAgent "Enable AptX codec" -bool true
- - - - -
- - - - -
$ defaults delete com.apple.BluetoothAudioAgent "Enable AptX codec"
- - - - -
From 2010, some Mac's Bluetooth module
Open Bluetooth icon on MenuBar with option key.
If your Mac's Bluetooth module can use apt-X,
you may confirm that it becomes effective.
Currently Being ModeratedJan 27, 2014 5:30 PM (in response to Raffael M.)
I tried the command line enable and rebooted, and re-paired the whole nine yards...nada, then I tried the Bluetooth Explorer module. In the Bluetooth Explorer, I went to Tools then Audio Options and checked off Force use of aptX. Viola!!! The Bluetooth Explorer is available from here: https://developer.apple.com/downloads/index.action?name=bluetooth%20explorer . I am running Mavericks OS X 10.9.1...let me know if it works for you...cheers
Currently Being ModeratedFeb 22, 2014 10:58 PM (in response to Ferre)
Also, if none of these work for you ... Try turning off multipoint functionality on your headphones if the feature is available. Having this enabled forced the SBC codec to be used regardless of the 'force aptx' setting.