Head-Fi.org › Forums › Equipment Forums › Portable Source Gear › Android phones and USB DACs
New Posts  All Forums:Forum Nav:

Android phones and USB DACs - Page 32

post #466 of 5379
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.gif
post #467 of 5379

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

 

post #468 of 5379

How is battery life with that tiny Stoner Acoustics usb dac plugged in ? I mean just listening music with screen off.
 

post #469 of 5379
Quote:
Originally Posted by DanBa View Post

 

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
 
post #470 of 5379

Hi Dan,

 

Thanks for your quick and detailed answer !

 

So, from the first list (or even from ebay...) , which usb-spdif converter do you think will sounds better with custum nexus 7?

post #471 of 5379

Sorry, I don't know.

If I am not mistaken, there are only two USB to S/PDIF converters on this list: ESI Dr. DAC nano and Turtle Beach Micro II.

post #472 of 5379
Quote:
Originally Posted by micksaddress View Post

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
 

 

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

 

"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;
 
post #473 of 5379

Matrix Mini > OTG Cable -> Galaxy S3. Sweet:)

 

 

 

post #474 of 5379

hmm

 

could you use USB > SPDIF > E17? Anyone doing similar?

post #475 of 5379

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.

post #476 of 5379

BBEG:

 

http://www.matrix-digi.com/english/cpshow.asp?pid=31

 

Wonder if anyone has tested this with an android phone?


Edited by rG-tom - 10/11/12 at 1:10am
post #477 of 5379

other option would be the turtle beach micro 2, that isnt huge....just need a tiny 3.5mm spdif to 3.5mm spdif cable then!

post #478 of 5379
post #479 of 5379

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.

post #480 of 5379
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.gif
Galaxy Note 2 >> USB OTG cable >> normal USB cable >> Go-DAP X >> Grado GR10 cool.gif
Edited by JCJiffy - 10/11/12 at 6:33am
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Portable Source Gear
Head-Fi.org › Forums › Equipment Forums › Portable Source Gear › Android phones and USB DACs