WiR3D
We intend to hurt him...quite a bit. 
- Joined
- Feb 2, 2012
- Posts
- 2,319
- Likes
- 98
So I have been on a mission to find out as much as a I can about USB audio on Android as possible, mainly because my Aune T1 doesn't work with my stupid #$%^&* Samsung S3, and the Fiio E17 has a glitch that prevents it working with most things.
This has been about a year, and I have discovered that USB Audio is a mess. And linux had to a build a quirks table just to cater for all the blunders that hardware and chip manufacturers make.
Which is all good if you are running the latest Linux distro, but heres where the wheels fall of the bus, Android is linux fork, and google doesn't strictly force much kernel wise onto the device manufacturers like Samsung. So the net result is a very fragmented kernel space. And then manufacturers like Samsung use 3 year old implementations of ALSA that barely has a quirks table and then we are stuck with the broken functionality.
So you can blame, TI, Qualcomm, Samsung, HTC and even Fiio (and I'm a big fan of them, and this is to a lesser degree than the others), for the ****ty testing and QA process and shortcuts they took.
For reference I own an SGS3, and have access to a Note I, Note II, Sony Xperia V and Sony Z tablet. I also own a Fiio E7, Aune T1, and Fiio E17.
I figured a lot of this out by cloning the Samsung S3 i9300's stock kernel sources, the i9300 Boeffla kernel source, the Sony Xperia V stock kernel sources, and the ALSA sources from alsa-project.org
The Sony can actually work with the Aune T1, and thats mainly due to the much newer ALSA implementation that they use, not the (and I'm not even joking and yes I am reiterating) 3 year old ALSA that Samsung dug out of the grave.
This has been about a year, and I have discovered that USB Audio is a mess. And linux had to a build a quirks table just to cater for all the blunders that hardware and chip manufacturers make.
Which is all good if you are running the latest Linux distro, but heres where the wheels fall of the bus, Android is linux fork, and google doesn't strictly force much kernel wise onto the device manufacturers like Samsung. So the net result is a very fragmented kernel space. And then manufacturers like Samsung use 3 year old implementations of ALSA that barely has a quirks table and then we are stuck with the broken functionality.
So you can blame, TI, Qualcomm, Samsung, HTC and even Fiio (and I'm a big fan of them, and this is to a lesser degree than the others), for the ****ty testing and QA process and shortcuts they took.
For reference I own an SGS3, and have access to a Note I, Note II, Sony Xperia V and Sony Z tablet. I also own a Fiio E7, Aune T1, and Fiio E17.
I figured a lot of this out by cloning the Samsung S3 i9300's stock kernel sources, the i9300 Boeffla kernel source, the Sony Xperia V stock kernel sources, and the ALSA sources from alsa-project.org
The Sony can actually work with the Aune T1, and thats mainly due to the much newer ALSA implementation that they use, not the (and I'm not even joking and yes I am reiterating) 3 year old ALSA that Samsung dug out of the grave.
gerrit link
So in light of this uphill challenge, I would like to gather support and show appreciation for the effort he is doing. Please post your thanks here, or on your social network of choice and direct the support at Cyanogenmod and Steve Kondik and post a link here.
This is no mean feat, and has been an issue for years, and google is eating glue with their fingers in their ears going "la la la la la la".
Spread the word!
