Is APT-X software? - T-Mobile, Samsung Galaxy SIII

Just wondering if the APT-X tech would be functioning if I switch to AOSP ROMs. Or is it just something that the phone has and will do?

SiNJiN76 said:
Just wondering if the APT-X tech would be functioning if I switch to AOSP ROMs. Or is it just something that the phone has and will do?
Click to expand...
Click to collapse
I think aptX is not software because there is a special Bluetooth adapters for PC and headsets with aptX support.
P.S.: my Glalxy Tab 7.0 Plus and HS3000 sounds really good instead PC's ASUS Xonar DX with A2DP Bluetooth 2.0 adapter.

I'd like to know for sure too - I'm thinking of flashing an AOSP-based ROM onto my Samsung Galaxy S3 but I'm worried that by moving away from a Samsung-based ROM I'll lose apt-x support...

gers1978 said:
I'd like to know for sure too - I'm thinking of flashing an AOSP-based ROM onto my Samsung Galaxy S3 but I'm worried that by moving away from a Samsung-based ROM I'll lose apt-x support...
Click to expand...
Click to collapse
I did a test on exactly that on the international GT-I9300.
You can find it here

As the A2DP specificationa allows the usage of custom codecs, I think it is pure software, but a license to use it is needed I guess...

Related

[Q] Galaxy S III VS Note II Bluetooth driver difference?

I have a JVC head unit in my car paired up to my Galaxy S III, and no matter what I do (tried a different SIII, resets, different music apps, etc.) the Bluetooth drops when I go to skip tracks from the radio (AVRCP). I have been forced to go to the CM10 ROM to get a reliable connection (although I'm stuck on a build from about a month ago, as some Bluetooth bugs have introduced there as well). Anyway, I'm eyeing up the Note II, but I'm wondering if anyone can confirm/deny if the Note II (stock ROM) has a different Bluetooth driver than the SIII. I hate to say it, but I actually really like Samsung's new interface, but the Bluetooth issue I'm having is a deal breaker. The other question is if anyone knows if the 4.1 update coming out for the SIII will have the same BT driver as 4.0.
Thanks!
had you ever flashed the KT747 kernel on the stock ROM of your s3? it changes the WiFi and Bluetooth drivers.
OR, if you haven't, maybe give it a try since it changes the WiFi and Bluetooth drivers.
Russ77 said:
had you ever flashed the KT747 kernel on the stock ROM of your s3? it changes the WiFi and Bluetooth drivers.
OR, if you haven't, maybe give it a try since it changes the WiFi and Bluetooth drivers.
Click to expand...
Click to collapse
I have not tried that. I would prefer to keep it stock, but that's something to try.
I thought I was the only one with this issue. I can relate as well . I too have a JVC unit and also experience the same bug on JB TW Rom. It tends to disconnect after I skip a few tracks and reconnects again . It does F*** up the mood when jamming to your music. At the moment im trying a different kernel to see if it does the same. But like you said CM10 doesn't disconnect.
Sent from my SGH-T999 using xda premium
J-ROCK said:
I thought I was the only one with this issue. I can relate as well . I too have a JVC unit and also experience the same bug on JB TW Rom. It tends to disconnect after I skip a few tracks and reconnects again . It does F*** up the mood when jamming to your music. At the moment im trying a different kernel to see if it does the same. But like you said CM10 doesn't disconnect.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I emailed JVC on it, and they gave me the whole "did you try a reset" business... Infuriating. At this point I just want a stock ROM that works. My S & S II worked perfect on the same head unit...
How can you tell if the stock S III and Note II use the same BT driver? Oh, and let me know what your experience is with the new kernel.
It's a few more days until Jelly Bean is released. There are changes to the Bluetooth stack in Jelly Bean. I'd wait and give that a try before getting a new phone.
I had the same problem on my JVC receiver. Had the issue with Task's ROM too. Would happen when you skip through the songs fast. I switched to an Alpine deck and it still has slight issues but not as much. I also have an issue of it disconnecting and reconnecting right after I make a call. Hopefully Monday will bring a fix for us Canadians.
Sent from my SGH-I747M using xda app-developers app
Bluetooth has been messed up on the S3 from day one. I think it's an ICS issue because my gf's OneX has the same issues. I have a Mercedes B200 and I can't get sound through the car's speakers at all. Tried a bunch of different ROMs and kernels, including some JB (4.1) builds, all to no avail. I'm at this point waiting for 4.2.
I dont see any problems with my SG3 connecting my hyundai sonata car(2013 model) and honda CRV via bluetooth. No problems playing songs, phone calls and Google navigation.
Same phone didn't work with kia soronto SUV.
I feel the car bluetooth software has issues, not the phone software.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
nani4215 said:
I dont see any problems with my SG3 connecting my hyundai sonata car(2013 model) and honda CRV via bluetooth. No problems playing songs, phone calls and Google navigation.
Same phone didn't work with kia soronto SUV.
I feel the car bluetooth software has issues, not the phone software.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
It could be, but I've used a Captivate, Infuse, & S2 on the same radios (two different JVC decks), and they've all worked perfect. Those all had stock ROMs (to start). I flashed CM9 and then CM10 on the Captivate & SII, and they still worked perfect. The only phone (stock/not stock ROM) that has ever had problems for me is the S3. My gut tells me it's a problem with the Bluetooth stack on the stock ROM, seeing as BT on CM9/CM10 works perfect on the S3 (other than the bass-less sound bug on the "stable" release and after - nice "stable" release).
Somebody on XDA should start hacking the software on these touchscreen head-units (they are update-able :good, then I'll be impressed.
Note 2 BT
Anyway, has anyone tried a Note 2 on one of the radios you had problems with? If not, I might try a re-post over in the Note 2 forum...
rytymu said:
Anyway, has anyone tried a Note 2 on one of the radios you had problems with? If not, I might try a re-post over in the Note 2 forum...
Click to expand...
Click to collapse
Well I bought a Note 2, SAME DAMN PROBLEM! I'm 95% sure I'm returning it, the only other option is to buy a different head unit. Anyone else have a GS3 and an aftermarket radio that DOESN'T drop the bluetooth connection when skipping tracks?
rytymu said:
Well I bought a Note 2, SAME DAMN PROBLEM! I'm 95% sure I'm returning it, the only other option is to buy a different head unit. Anyone else have a GS3 and an aftermarket radio that DOESN'T drop the bluetooth connection when skipping tracks?
Click to expand...
Click to collapse
i have a kenwood ddx 418 and ive got no issues with bluetooth, best bet would be to go to a bestbuy and try out the display units there imho
Bluetooth audio for music and calls works fine with my Ford Edge...however there is no track information (avrcp) sent to the headunit which is annoying. No change with the Jellybean update either.
mixxy said:
i have a kenwood ddx 418 and ive got no issues with bluetooth, best bet would be to go to a bestbuy and try out the display units there imho
Click to expand...
Click to collapse
funkydude101 said:
Bluetooth audio for music and calls works fine with my Ford Edge...however there is no track information (avrcp) sent to the headunit which is annoying. No change with the Jellybean update either.
Click to expand...
Click to collapse
But are both of you running bone-stock ROMs? If so, I may have to start looking at radios again.
Returned it. I guess that's a $35 experiment (thank you AT&T for the restocking fee). Either the Sammy BT stack is too advanced for my basic A2DP radio (as in ALL BT radios), or the Sammy BT stack is just horribly developed (which I've come to believe is true). Now I just have to wait for an apt-x head unit to come out, then I can try this experiment again...

Bluetooth and apt-x support?

Does the note 8 support bluetooth apt-x?
Has anybody succefully connected with an apt-x enabled headphone?
Sent from my GT-N7000 using xda premium
I'd like to get confirmation of this as well. My guess is that it most likely will have APT-X since the hardware and software is nearly identical to the Note II.
The Note II sounds phenomenal connected to the Samsung HS3000 BT adapter, even driving my Grado PS500 headphones directly w/o a separate amp! I honestly can't tell the difference between the APT-X BT connection and a direct hardwired connection, even on FLAC files from audiophile labels like Chesky, EMI, Telarc, and AudioQuest, etc. But I can't hear much above 15kHz...was a drummer for too long and trashed my ears.
Unfortunately, audio stablity isn't great as Note 2 because I encounter some audio dropout even it's rare. Next week I will switch memory card to does it help.
mingkee said:
Unfortunately, audio stablity isn't great as Note 2 because I encounter some audio dropout even it's rare. Next week I will switch memory card to does it help.
Click to expand...
Click to collapse
Hmmm...I hope it is just your microSD card causing the dropout problem. Please let us know when you try a new microSD card. Thanks!
Would Like to know this as well. Did you ever find the answer? I think i saw it on the back on the 5100 unboxing video but have not found any info on the 5110 version. If the 5100 has it, i would think the 5110 does.
No i haven't found out yet. Still looking for an answer.
Sent from my GT-N7000 using xda premium
The N5110 and 5100 both have AptX. My set of AptX headphones have an EQ mode that only functions when AptX isn't enabled. It works on my Thinkpad (no AptX) and not on my Note 8, leading me to the conclusion AptX is working and integrated.
Thank you. Would be nice if there was a App that could tell you. I looked and did not find one. I thought it might. I saw a unboxing of the n5100 and it was printed on the back apt-x, so i knew it had it. I figured the 5110 should also then. But thx again with the info.
robyr said:
The N5110 and 5100 both have AptX. My set of AptX headphones have an EQ mode that only functions when AptX isn't enabled. It works on my Thinkpad (no AptX) and not on my Note 8, leading me to the conclusion AptX is working and integrated.
Click to expand...
Click to collapse
Although I would tend to agree with you there could be some sources of error, which makes your conclusion tenative. I have contacted both Samsung and CSR, who has developed APTX. None of them could give a definitive answer! Part of that is the devices vary depending on region. CSR's crew in South Korea, who has worked with Samsung on their devices, will hopefully come back with a clear response. CSR will, come new Year's, set up an APTX microsite to be able to provide more detailed responses than the present general CSR site can supply.
CSR has now via Samsung confirmed the Note 8 sold in the EU has aptx despite that there's no info on the packaging or on the device over here.

[Q] APT-X?

OK I have an LG phone and a LG 730+ headset, but it seems that my LG headset has APT-X support and my new LG-G3 doesn't. Which seems weird that a flagship phone does not have the codex that their headset would. Has anyone found support for APT-X on this new G3 phone? Since I don't know enough about the APT-X codex, is it hardware or software based? I asked because if it's software based maybe it can be added with an upgrade from LG, if hardware then it looks like I'm SOL and I really thought buying this phone would get me APT-X support.
I'm not sure exactly what aptx is but I do see them on my headphones as well buy my headset works fine with my g3
A few minutes on Google and I found this info...
From the aptX site:
http://www.aptx.com/product/lg-g3-smartphone
On LG's site, the spec listing shows Bluetooth 4.0 LE (APT-x) Connectivity:
http://www.lg.com/us/mobile-phones/g3
webfrm said:
OK I have an LG phone and a LG 730+ headset, but it seems that my LG headset has APT-X support and my new LG-G3 doesn't. Which seems weird that a flagship phone does not have the codex that their headset would. Has anyone found support for APT-X on this new G3 phone? Since I don't know enough about the APT-X codex, is it hardware or software based? I asked because if it's software based maybe it can be added with an upgrade from LG, if hardware then it looks like I'm SOL and I really thought buying this phone would get me APT-X support.
Click to expand...
Click to collapse
http://www.jessebandersen.com/2012/05/list-of-apt-x-compatible-devices.html?m=1
So few devices use this codec. I definitely can't head difference. Used my Samsung that does support it and my g3. So change in sound quality at all. Head phones work just fine.
AWESOME G3
Heard it may not be enabled on t-mobile
OK thanks everyone for looking at LG's website and checking the specification (why I didn't do tha) but I heard that the t-mobile version in the US may not be enabled for APT-X codec, again another thing removed for no reason. Since I have root any terminal command to check this would be appreciated. I tried the one "getprop persist.service.btui.use_aptx" which was the way to check on the LG2 but it isn't the same I guess with kitkat. So I have no clue if the rumors are right that big Pink T won't support aptx.
I think T-Mobile rumors of them not supporting it is fallacy. Simply because other devices have it installed. From Sony, Samsung, and HTC. I think it's more possibly if it's no additional charge and a default thing it's there. If the manufacturer has it as an option and charges for it T-Mobile may have forgone paying the extra(like headsets for example).

Tab S 10.5 + Lollipop 5.02 + USB DACs

after working perfectly with 4.4 - my Fiio E17 DAC no longer works with my Tab S
from reading forums this seems quite a common complaint across Samsung users - including some Note 4 users (although bizarely some seem to have no issue)
I am not sure if it is a combination of the Tab S Exynos chipset + 5.02 + my specific DAC that has an issue - so has anyone with a Tab S and Lollipop got any USB DAC to work please ? I find the Headphone out rather poor (nowhere near as god sounding with my headphones as my Note 3) - but the screen class leading - so the combination of the Tab S + USB DAC was absolutely superb
I have read of one user using a E17 with a Sony device and Lollipop 5.02 - although can't verify it
I think Samsung had their own USB audio implementation before on 4.4 - which worked flawlessly for me - have they moved across to generic Android 5.02 implementation - and therefore could that be the issue (but doesn't explain why some non Samsung devices working ok) - OR has Samsung disabled their own USB audio but hasn't somehow implemented the 5.02 audio correctly?
hence I was wondering if anyone has managed to get USB Audio out of their Tab S please
USB audio works fine in USB Audio Pro tool - but you can only play local music content, 99.9% of my Tab S usage is with Spotify, Netflix, Amazon Instant Video etc etc
thanks for any help
LOVING Lollipop on Tab S otherwise so would be a shame to have to go back to 4.4 just for USB Audio
Bought an Oppo HA-2 and am having the same issues.
Sounds totally distorted using Player Pro, Poweramp, Samsung native music player, Spotify.
On Poweramp. the sound is distorted and the speed is super slow ie it gives the low demonic voice, like when slowing down a LP.
I don't want to have to load the Tab S with audio files and that only to use UAPP.
Fiio E18 here, works flawlessly with my Sony Z3 Compact.
On Tab S 10.5 LTE just gives slowmo playback and massive distortion..
I'm in the same boat. I used to use DACs with my Tab S 10.5 fine on the stock OS (4.4 I think), but when I upgraded to Lollipop it just hisses at me when I plug one in now. This is esspecialy annoying as I've just bought the Oppo HA-2 as well. I find this very odd since Lollipop is supposed to bring generic support for this to devices and yet it has stopped it working here. My wife has a Elephone P7000 (running Lollipop) and that works fine. I have a Samsung Galaxy Note 2 and a Galaxy Alpha (both running 4.4) and they work fine, butt if the Alpha (my main phone) gets an upgrade to Lillipop I will have to leave it now, as I need these two devices to work (they look so damn pretty together!).
Have you complained to Samsung about this? If so have you got a response? I think I will mention it to them now...
Im having problems as well...ive recently got a tab s 8.4...i upgraded to lollipop right out of the box...damn!
Anyway....my device is SMSL X-USB (XMOS based usb receiver). Works great with UAPP but not natively....no sound. On my Note 4 with lollipop 5.1.1 UAPP and native works great with it.
I want native to use RDIO, TUNEIN RADIO ETC....and then use UAPP for my hidef 96/24 flacs.
Im thinking of trying some custom roms but there are so many! Has anyone had any success with any of the custom roms?
Ok, I decided to change my entire Car Tablet install. Eliminate my Bluetooth head unit for a DAC and a DSP only to find issues. Both my Tab S 8.4 and S6 Edge will NOT WORK without using UAPP. But that's a music player. So no Android app sounds go through it. No YouTube, videos etc. Total fail with Samsung. I can test a HTC M8 just to try. Nexus 7 fresh from the 5.1.1 update doesn't work but I don't trust using my current DAC, since it's a 5.1 Surround Asus Xonar U5.
I've been trying to find DACs that work but haven't found much. I joined HeadFi and found some people that ditched the awesome Tab S for the downgraded Tab S2 because their USB SPDIF only DAC worked on the Tab S2.
I wouldn't mind downgrading to 4.4 to make DACs work, but will not get rid of my lovely screen, size, and install to go to a different tablet I dislike.
Like I stated I can't trust the Xonar, it's not a typical DAC. Unless someone can confirm it works with the Tab S on 4.4.
I know I'm not a 10.2 user but virtually the same devices, including the Tab Pro. So no need to make a new thread.
Sent from my SM-T700 using Tapatalk
So, Cheap USB DAC's are working fine on Samsungs with Android 5+. But the ones I've tried out that are capable of digital audio output don't work unless using UAAP. This is not Ok. Time to look for a CM10 Rom to install on my Tab S. This is a huge failure on Android 5. I don't think its just samsung because my Nexus 7 on 5.1.1 OEM (Maybe CyanogenMod 12 as I have not tried it yet) also does not work, as well as my HTC M9. Everything works if using UAAP, but thats just a Music Player, does not work with any other audio. I personally might end up trying a decent priced DAC with only Analog output. Since I can't hear the difference in quality in my car.
USB audio out and DACs
I had same problems with usab audio out on lollipop on tab s, nexus 7 and LG G3.
I eventually got Tab S T805 USB audio out to work after I flashed the AICP 5.1.1 rom. Worked perfectly.
Last week I flashed the AOSP Marshmallow ROM and USB audio out and this works perfectly too.
I am sending to an Audio GD DAC via an OTG adaptor.
Eventually got the G3 to work on lollipop by using a powered hub but this did not work for Tab S.
Buckster76 said:
after working perfectly with 4.4 - my Fiio E17 DAC no longer works with my Tab S
from reading forums this seems quite a common complaint across Samsung users - including some Note 4 users (although bizarely some seem to have no issue)
I am not sure if it is a combination of the Tab S Exynos chipset + 5.02 + my specific DAC that has an issue - so has anyone with a Tab S and Lollipop got any USB DAC to work please ? I find the Headphone out rather poor (nowhere near as god sounding with my headphones as my Note 3) - but the screen class leading - so the combination of the Tab S + USB DAC was absolutely superb
I have read of one user using a E17 with a Sony device and Lollipop 5.02 - although can't verify it
I think Samsung had their own USB audio implementation before on 4.4 - which worked flawlessly for me - have they moved across to generic Android 5.02 implementation - and therefore could that be the issue (but doesn't explain why some non Samsung devices working ok) - OR has Samsung disabled their own USB audio but hasn't somehow implemented the 5.02 audio correctly?
hence I was wondering if anyone has managed to get USB Audio out of their Tab S please
USB audio works fine in USB Audio Pro tool - but you can only play local music content, 99.9% of my Tab S usage is with Spotify, Netflix, Amazon Instant Video etc etc
thanks for any help
LOVING Lollipop on Tab S otherwise so would be a shame to have to go back to 4.4 just for USB Audio
Click to expand...
Click to collapse
interestingly I get proper sound out of Neutron with their new "direct to USB" option
except then my Note 3 crashes
Neutron?
Sent from my SM-G925T using Tapatalk
It's a music player
Whilst talking about USB DACs - someone on another thread posted a work around for Note 3 and USB DACs and woks perfectly on my Note 3 but no go on Tab S
If you just want to play Music, try UApp. I'm completely against settling for JUST a music player. I want to play a movie and YouTube and everything.
Sent from my SM-G925T using Tapatalk
I totally agree as most of my usage is the likes of Spotify etc
The workaround for my Note 3 although adds a few steps allows you to use DAC for all apps but doesn't work for Tab S
Annoying as the headphone out from my Note 3 is very very good anyway but the output from my Tab S I find rather poor and the main reason I bought the DAC in the first place !
Yes. I'm hoping there is a fix on 6.0 because I am not ok with just music. My tablet is built into my car, with a optical DAC, and a Helix DSP.
Sent from my SM-G925T using Tapatalk
I can't comment on the fiio as I've only got the amp only E11k but I can say my turtle beach earforce 450 DAC seems to work fine on my tab s. No surround, obviously, but I do get sound.
Sent from my LG-D855 using Tapatalk
All analog DACs seem to work. It's the DACs that have an optical out that are having issues.
Might join in on the Android 6 pages to see if they can fix the Native drivers. Doubt Samsung really cares enough. Typical DACs are working, that's good enough for them.
Sent from my SM-G925T using Tapatalk
Well, guess the "Native" USB DAC 'crap' Google has implemented doesn't work worth a damn on 6.0 either. Soo odd how it works almost flawless across soo many platforms before Android 5, then they release "Native" drivers that cripple all worthwile DACs. It's like they are purposely preventing us from using better DACs than that was installed internally so we'd be forced to use the Wolfson.
And Apple devices have Optical built in. Lol
Anyway I'm on 6.0 now testing out my Asus Xonar. Same issues as before. Using UApp it works but since UApp is 'only' a music player it leaves all other audio routed through the tablet. Noticing one issue that's new, there is a click sound every couple seconds of music playback that wasn't there on 5.1.1.
Need to find me a pre 5.0 CyanogenMod Rom to run.
Sent from my SM-G925T using Tapatalk
kernel
what about trying your stock 5.0.2rom with another kernel? like ironkernel or skyhigh kernel.
i do(or want to) belive dac suport is a kernel issue
if already are on lollipop 5.0.2 i would try this before anything else
i am currently on 4.4.2 and was just about to update to 5.0.2, had read it has native dac suport lol.
just tought i would check if there was any issues first
becouse i do have some issues of my own with my cheepo 5$ ebay pcm2704 dac with optical out (everytime i coldstart my xenons or i bump my cable it gets disconnected/connected in an instant and then sound gets wierd kinda like an echo of sorts, and i have to close music player remove cable wait a bit plug in and all is fine. quite annoing and dangerus now in the wintertime when there are frequent xenon cold starts) was hoping 5.0.2 would solve this.
im in the same boat as many others, dac suport inside player does nothing for me, as im using the tab as gps/mediasenter
so from what im reading im gonna live with it or atleast until someone have tryed 5.0.2 with another kernel
Cmon be a guinnipig, your device doesnt work anyway nothing yo lose ;p
Name the kernel and Rom, I've been on them all. I'm a vivid tester. It's not a kernel issue. This "native" support, technically just removed drivers for some dedicated DACs. Leaving the others that have been tested and proved working for years... Yes years before "native", I know I've been using DACs in all my tablet car installs from cheapo eBay 1 dollar pos dacs to high end, removed. The app UApp has this specific driver built into the app itself.
However what your describing sounds like a wiring issue.
I even jumped on the Android 6 bandwagon. It's not working on OEM Samsung Android 6 that was just released in beta form.
The hifi forum has 790 pages of info. And page one a collab of info on what dacs work and how they work.
Sent from my SM-G925T using Tapatalk
indeed i had wirering issues, nothing was sheilded, resoldered otg with sheilded cables and grounded dac chassie to cable (at the same time made a y on the otg cable for simulcharge with 88kohm resistor) and behold all is as should. ( all but a clicking sound left so i guess my dsp needs the same treatment) thanks
no build with a fix thats just wierd, there are so many clever rom/kernel builders in here
guess we cant do nothing but hope for a fix then
thanks for testing and letting us know

Make the OnePlus 3 apt-x compatible

Hello !
I have a good apt-x pair of headphones and an apt-x compatible phone for the time being. I thought about buying the OP3(T) but I'd like not to loose this funtionality.
That's why I thougt I could buy an apt-x transmitter and plug it to the jack, in order to have apt-x !
What if i also buy an external DAC and plug the transmitter to it ? Would it work, does it make sense?
So overall, do you think it is a good option to do like that ? Do you have something better ? Or do you think that what I am saying is completely dumb ?
Thanks !
Does apt-x make such a difference that it is worth the effort?
lekronop said:
Does apt-x make such a difference that it is worth the effort?
Click to expand...
Click to collapse
Imo it doesn't if all you do is audio listening. But then again, I reverted back to wired cause even aptx still sucks.
On the other hand, latency response is noticeably better, so in those quite rare instances where I want to watch a movie (from tv mostly) via bt, aptx helps. I mean, without aptx, same content would be unwatchable due to audio lag.
millicent said:
Imo it doesn't if all you do is audio listening. But then again, I reverted back to wired cause even aptx still sucks.
On the other hand, latency response is noticeably better, so in those quite rare instances where I want to watch a movie (from tv mostly) via bt, aptx helps. I mean, without aptx, same content would be unwatchable due to audio lag.
Click to expand...
Click to collapse
Ah okay, never thought about the latency of bt cause whenever i watch a movie over external speakers i just use aux since the speakers are right next to the tv.
Eventually, I'm working on an apt-x support for a while without success... A lot of phones provide apt-x functionality without hw support.. It's a sw solution, but I didn't find the method to load the closed source codec like BlueZ. If I found working libraries from other phone, I'll let you know...
I swapped from my Xperia Z2 (with apt-x) to my Oneplus 3 and the only device I have that was capable of receiving apt-x Bluetooth audio is my car receiver. I noticed no difference.
Maybe car audio is a poor test because, despite my custom in-car setup with high quality receiver, amp and speakers, the car is very noisy, so some differences are lost to exhuast/wind/tyre/road noise.
lekronop said:
Does apt-x make such a difference that it is worth the effort?
Click to expand...
Click to collapse
Well, to be honest, if you have a great pair of headphones (not necessarily ultra high end, just mid-high headphones) that are compatible, you can hear the difference, it's a question of details imo. And low latency is definitely the first thing you notice. But no matter for music obviously. Is it a deal breaker? Well, I'm asking myself, I might reconsider the Apt-x necessity.
dh.harald said:
Eventually, I'm working on an apt-x support for a while without success... A lot of phones provide apt-x functionality without hw support.. It's a sw solution, but I didn't find the method to load the closed source codec like BlueZ. If I found working libraries from other phone, I'll let you know...
Click to expand...
Click to collapse
Really interested in that if you find something, but as long as it is a protected technology, it's a hard task that you try to achieve :/
kcajjones said:
I swapped from my Xperia Z2 (with apt-x) to my Oneplus 3 and the only device I have that was capable of receiving apt-x Bluetooth audio is my car receiver. I noticed no difference.
Click to expand...
Click to collapse
Thanks for this feedback, but I'm not surprised that in a car the sound is the same, for the reason you told
Hi,
I've really good news... I think, I've found a perfect device to make OP3 apt-x supported...
Unfortunately, my apt-x enabled headset will be my x-mas present, so I'm not 100% sure... I need to test it... Stay tuned...
EDIT: it's working, I've aptx
12-16 23:55:42.482 1462 1606 I bt_btif_media: btif_a2dp_encoder_init Selected Codec aptX
care to share how you did that?
iCstyle said:
care to share how you did that?
Click to expand...
Click to collapse
It's working on cm14.1, maybe it could work on N as well... It won't work on 6.0.1 based roms... You need 2 libraries from Moto-Z...
http://forum.xda-developers.com/oneplus-3/themes/mod-aptx-codec-t3521228
Wow. I mean, really?
Thank you so much for sharing, I hope it can work with the Snap dragon 821 as the OP3 is no longer available, but anyway, I could try to buy an original OP3 just for that.
Awesome, thank you
ElDonTheo said:
Wow. I mean, really?
Thank you so much for sharing, I hope it can work with the Snap dragon 821 as the OP3 is no longer available, but anyway, I could try to buy an original OP3 just for that.
Awesome, thank you
Click to expand...
Click to collapse
There's a really good chance to make it working with op3t as well...

Categories

Resources