Quote:
Originally Posted by
ClieOS 
DX100 is implemented on Android, which is notorious for its sub-par stock audio driver (if you don't believe me, just google the XDA forum on Android SQ) and why iBasso spent a lot of time writing its own audio driver (and thus the subsequent improvement in sound via software update). What iBasso did is merely bring the software up-to-par with its hardware. Different from iBasso's approach (which is hardware first then software follow), the firmware on HM901 has been developed over the last three years to make sure the SoC they are using will work with the two ES9018 without a problem (it is not a standard design so they need to write the firmware to control two ES9018). I am not saying this to defend HifiMan, but to point out that there are story that you have no idea of and so shouldn't make hasty judgement.
As for Fang's comment, actually I have been reading them over at erji.net where he spent most of his time these days and not here. I read the iBasso discussion there as well, in case you think I am just blindly trying to defend Fang on this, well, but I guess you might just think I am making things up or in defensive mode....

Do not confuse what Android has done to what it really is capable of. Android care o-meter for sound is what has been implemented.... Think Beat Audio DSP or a big fat donut for "audiophiles".
The DX100, although on a depracated OS in Androind 2.3.1, is just a shell. The real portion of the DX100 sound (along with every phone that has something like a Wolfson in them) is the coding to use the DAC(in the DX100 case, ES9018). Direct I2S digital stream from the CPU. Firmware changes to the DAC CLK cycle will affect the sound of course.
I said it before. The probability of a dual DAC capable of feeding a 32 channel mixer directly working correctly right off the bat is very very low probability. Why do I say that? The programming needed is in the realm of parallel thread programming, dual firmware loading to sync the DACs, buffers to sync the outputs. Needlessly complicated. Not easy AND not cheap if it is being outsourced. Something that more than likely Feng is finding out first hand. There is a principle in the programming world (and electronic Engineering also) that applies here.
K.I.S.S
Keep It Simple Stupid.
I have seen the DX100 code.. ALL of it to include the android compile. It is actually very simple in what it does. Personally it is a shame that iBasso contracted RockChip to code as they are one of the few Chinese firms to stay at 2.3.1 with no future plans to go to ICS or JB. iBasso missed a couple of things but they have been very responsive to my input (and sorensiim) on what they need to do to implent or fix some items. I am not getting paid by them, I do not even own there product. But I find it a simple debug of the code and answers are retrieved just by looking at the code. iBasso has been reading the thread here just by some of the fixes that have been implemented. WIth the latest firmware... the reports are that the DX100 sounds damn great rivalling some of the desktop DAC's.
If iBasso (RockChip) can get the UI polished as they have been slowly doing and leave the sound as it is in 1.2.7 (with fixing the inital music cut during manual track selection), they will be hard to beat.