Android phones and USB DACs
Oct 10, 2012 at 2:31 AM Post #466 of 9,526
Anyone tried the Audioquest Dragonfly with the Samsung galaxy s3 or note 2? I intend to buy a Dragonfly to pair with my Note 2 :rolleyes:
 
Oct 10, 2012 at 3:17 AM Post #467 of 9,526
The AudioQuest DragonFly has been unsuccessfully tested with a Samsung Galaxy S3 without a powered USB hub.
 
There is a upcoming AudioQuest Bumblebee designed specifically for Android devices:
http://www.head-fi.org/t/595071/android-phones-and-usb-dacs/390#post_8738656
 
Another USB DAC based on the same 24-bit ESS Sabre conversion chip: Stoner Acoustics UD100
http://www.head-fi.org/t/595071/android-phones-and-usb-dacs/345#post_8720188
 

 
Another USB DAC based on the same 24-bit ESS Sabre conversion chip: ODAC
http://www.head-fi.org/t/595071/android-phones-and-usb-dacs/315#post_8707637
 

 
Oct 10, 2012 at 5:51 AM Post #469 of 9,526
Quote:
 
Yes, the micro A plug of the USB OTG cable should switch the Nexus 7 to the USB host mode.
I suppose you has successfully tested the iBasso D2 & the USB micro B cable with a PC.
Could you provide a dmesg output?

Yes tested with pc running windows 7 and laptop running ubunto both work fine, here is the dmesg output
 
 
<6>[ 1931.646441] usb 2-1: new full speed USB device number 15 using tegra-ehci
<6>[ 1931.649204] auto_hotplug: Onlining single CPU, avg running: 180
<4>[ 1931.671054] CPU1: Booted secondary processor
<6>[ 1931.671441] Switched to NOHz mode on CPU #1
<6>[ 1931.672207] cpufreq_interactive_input_connect: connect to elan-touchscreen
<6>[ 1931.673538] auto_hotplug: CPU1 up.
<6>[ 1931.776511] auto_hotplug: Offlining CPU, avg running: 180
<3>[ 1932.113477] usb 2-1: device not accepting address 15, error -71
<6>[ 1932.228923] usb 2-1: new full speed USB device number 16 using tegra-ehci
<3>[ 1932.696428] usb 2-1: device not accepting address 16, error -71
<6>[ 1932.810482] usb 2-1: new full speed USB device number 17 using tegra-ehci
<5>[ 1932.814452] CPU1: shutdown
<6>[ 1932.816541] auto_hotplug: Onlining single CPU, avg running: 180
<6>[ 1932.818571] auto_hotplug: CPU1 down.
<6>[ 1932.838477] auto_hotplug: Onlining single CPU, avg running: 230
<4>[ 1932.839107] CPU1: Booted secondary processor
<6>[ 1932.839402] Switched to NOHz mode on CPU #1
<6>[ 1932.840607] cpufreq_interactive_input_connect: connect to elan-touchscreen
<6>[ 1932.840738] auto_hotplug: CPU1 up.
<4>[ 1932.843203] CPU2: Booted secondary processor
<6>[ 1932.843405] Switched to NOHz mode on CPU #2
<6>[ 1932.843969] auto_hotplug: CPU2 up.
<6>[ 1932.860436] auto_hotplug: Offlining CPU, avg running: 230
<3>[ 1933.021945] usb 2-1: device descriptor read/64, error -71
<3>[ 1933.334956] usb 2-1: device descriptor read/64, error -71
<6>[ 1933.558729] usb 2-1: new full speed USB device number 18 using tegra-ehci
<3>[ 1933.772683] usb 2-1: device descriptor read/64, error -71
<5>[ 1933.868010] CPU1: shutdown
<6>[ 1933.876927] auto_hotplug: CPU1 down.
<3>[ 1934.090424] usb 2-1: device descriptor read/64, error -71
<6>[ 1934.187495] auto_hotplug: Offlining CPU, avg running: 150
<3>[ 1934.191996] hub 2-0:1.0: unable to enumerate USB device on port 1
<5>[ 1935.203468] CPU2: shutdown
Thanks
 
 
Oct 10, 2012 at 3:07 PM Post #472 of 9,526
Quote:
Yes tested with pc running windows 7 and laptop running ubunto both work fine, here is the dmesg output
 
 

<3>[ 1932.113477] usb 2-1: device not accepting address 15, error -71
<6>[ 1932.228923] usb 2-1: new full speed USB device number 16 using tegra-ehci
<3>[ 1932.696428] usb 2-1: device not accepting address 16, error -71
<6>[ 1932.810482] usb 2-1: new full speed USB device number 17 using tegra-ehci
 

 
[size=11.0pt]http://morfic.euroskank.com/git/?p=trinity-ns-ics.git;a=blob;f=drivers/usb/core/hub.c;h=34bb059607f5838f97a28d7fe5fe0a769acb502a;hb=refs/heads/tjb#l121[/size]
 
"As of 2.6.10 we introduce a new USB device initialization scheme which closely resembles the way Windows works. 
Hopefully it will be compatible with a wider range of devices than the old scheme.
However some previously working devices may start giving rise to "device not accepting address" errors; if that happens the user can try the old scheme by adjusting the following module parameters.
 
For maximum flexibility there are two boolean parameters to control the hub driver's behavior.  On the first initialization attempt, if the old_scheme_first" parameter is set then the old scheme will be used, otherwise the new scheme is used.  If that fails and "use_both_schemes" is set, then the driver will make another attempt, using the other scheme.

 
 
static int old_scheme_first = 0;"
 
=>
 
static int old_scheme_first = 1;
 
http://www.guyrutenberg.com/2008/06/26/usb-1-4-device-descriptor-read64-error-71/
 
Oct 11, 2012 at 12:00 AM Post #475 of 9,526
I believe that's exactly what's being described here regarding the 4-core's MHL capability. He appears to be using it successfully in this, so I would venture to say that it's perfectly possible. We'd just need a practical adapter that turns USB to SPDIF, be it an all-inclusive single cable or a micro-dock like FiiO's L7 and L11.
 
Oct 11, 2012 at 5:43 AM Post #479 of 9,526
out of interest, is there a technical limitation as to why the FiiO e17 has been successfully made to work with the Nexus 7 with a hacked firmware, but not the Galaxy S3? Is it just a case that a developer has not yet made that modification to an S3 firmware?
 
Thanks,
 
Tom.
 
Oct 11, 2012 at 8:17 AM Post #480 of 9,526
I am reconfirming that AQ Dragonfly does NOT work through USB OTG. I have a new Samsung Galaxy Note 2.

However, I can confirm that the recently released Sony PHA-1 does work with Note 2. Also confirmed that the Go-DAP X does work with Note 2.

Galaxy Note 2 >> USB OTG cable >> normal USB cable >> Sony PHA-1 >> Grado GR10 :cool:
Galaxy Note 2 >> USB OTG cable >> normal USB cable >> Go-DAP X >> Grado GR10 :cool:
 

Users who are viewing this thread

Back
Top