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 8

post #106 of 2344
6/30/12 at 12:25am
Quote:
Originally Posted by Gofre View Post

Quote:
Originally Posted by WiR3D View Post


Actually this means it leaves it up to the manufacturer, so no not bad news, great news. Because that way we can have extended batteries built into dacs like the vamp
Sent from my HTC HD2 using Tapatalk 2

 

So theoretically I'll have no problem using my E17 with the Nexus 7 with the appropriate adaptors?


Jip. If the accessory mode / host mode is user controlled, otherwise we may have issues

Sent from my HTC HD2 using Tapatalk 2
Reply

Gear mentioned in this thread:

post #107 of 2344
6/30/12 at 5:40am
Quote:
Originally Posted by DanBa View Post

There is likely another possibility to fix some SGS3 non-interworking issue: use the USB core driver of the Archos G9 tablet.
 
The Archos G9 tablet can interwork with the FiiO E17.
 
The SGS3 can’t interwork with the FiiO E17, even via a powered USB hub.
 
And drivers/usb/core/message.c of Archos G9 and of SGS3 are different, slightly different.
 
Some XDA developer could build and try a modded Android Linux kernel including the USB core driver of the Archos G9 tablet.
 
 

Dmesg log output and lsusb log output could detail what is going on at the kernel level.

http://comments.gmane.org/gmane.linux.alsa.devel/96433

 

dmesg:

https://play.google.com/store/search?q=dmesg

 

lsusb:

https://play.google.com/store/search?q=lsusb

 

Here's my log output from the lsusb if you still wanted to see one.

 

http://pastebin.com/9HiyyQZ7

 

 

Reply
post #108 of 2344
6/30/12 at 8:06am

I wonder anyone who has updated to Jelly Bean on the Nexus can try if USB Audio is working for Fiio E17 now.

Reply
post #109 of 2344
6/30/12 at 8:08am
Quote:
Originally Posted by gordec View Post

I wonder anyone who has updated to Jelly Bean on the Nexus can try if USB Audio is working for Fiio E17 now.

 

+1

Reply
post #110 of 2344
6/30/12 at 10:08am

As far as I understand, a Jelly Bean-powered Android device won't work with a legacy or standard USB DAC/amp FiiO E17 using a native Jelly Bean USB audio out feature.

It will work with a new type of USB DAC compatible with the Android-specific USB audio.

This Android-specific USB DAC acts as a USB host while the legacy or standard USB DAC, like the FiiO E17, acts as a USB device.

This Android-specific USB DAC should be compliant with the new Android Open Accessory Protocol 2.0.

http://developer.android.com/tools/adk/aoa2.html#audio-support

 

USB audio.jpg

Reply
post #111 of 2344
6/30/12 at 10:11am
Quote:
Originally Posted by MikeB123 View Post

 

Here's my log output from the lsusb if you still wanted to see one.

 

http://pastebin.com/9HiyyQZ7

 

 

 

Thanks!

 

Could you provide a dmesg output?

Reply
post #112 of 2344
6/30/12 at 11:09am

Is there any possibility, hack, mod, or whatever, to make a galaxy s2 work with a fiio e7 or e17???

Reply
post #113 of 2344
6/30/12 at 11:54am

Yes, some XDA developers are working to enable standard USB audio on SGS2.

 

 

"We just need 3 base things:
1st: USB Host support in Android kernel.
2nd. USB audio driver, in kernel, or compiled as a module.
3rd. Some logic to switch to USB audio card, or back to internal one." 
 
"In ICS, I've done it this way, with audio library and tinyalsa library." [tsynik]
 
Reply
post #114 of 2344
6/30/12 at 1:13pm

So, if I download the files, my sgs2 can use any usb dac?? Sorry - I'm a complete noob, but where can I find out how to install those files on my phone??

 

Thank you a lot!

Reply
post #115 of 2344
6/30/12 at 1:41pm

You should ask some Android kernel developer to follow the instructions of Tsynik, who has successfully enabled the standard USB audio feature on Android-powered Ainol Novo tablet.

http://forum.xda-developers.com/forumdisplay.php?f=1058

Reply
post #116 of 2344
6/30/12 at 6:35pm
Quote:
Originally Posted by DanBa View Post

 

Thanks!

 

Could you provide a dmesg output?

http://pastebin.com/8jqgKnaB

http://pastebin.com/Hh2jCJqq

 

Here you go.

 

What happens is I get the USB Connected or Disconnected information in the notification bar, the E17 gets a lock and even when playing sound out through speaker I connect it in and it still plays like I had just inserted headphones or a dock.

 

So its just the issue of the kernel not switching over I suppose. 

 

It's like getting to 3rd base then finding out shes saving herself for marriage. Haha


Edited by MikeB123 - 6/30/12 at 6:52pm
Reply
post #117 of 2344
6/30/12 at 9:05pm

@ Danba re use of S3 with ODAC.

 

Great that you've confirmed these two work together. I'm seriously considering getting the ODAC to use with the S3 and a portable amp, so would be interested in your experiences re practicality of using this unpowered DAC with the S3. 

 

How do you find battery life / drain on the S3 with the ODAC connected? Also how is the dynamics of the sound of this combo, particularly in the bass frequencies? I ask as in the ODAC impressions thread there is some commentary re power draw by the ODAC and limitations in the power available via USB bus of a computer (let alone a low power phone), and anecdotal improvements in sound dynamics where additional power is provided to the ODAC via a USB hub/external power supply. My concern is although the two "work" together, the ODAC's output might be compromised by the S3's limited power supply...

 

Cheers

Reply
post #118 of 2344
7/1/12 at 1:34am

You should ask Martin for that:

https://plus.google.com/107354758331405644147/posts/PCaM42irMeU

http://forum.xda-developers.com/showpost.php?p=27595086&postcount=426

 

I'd rather connect the ODAC to the Samsung Galaxy S III via a self-powered USB hub, a battery-powered USB hub in your case.

http://www.head-fi.org/t/604479/good-news-about-android-phone-supports-digital-audio-output/120#post_8488184

http://www.aqvox.de/usb-power_en.html

Reply
post #119 of 2344
7/1/12 at 1:46am
Quote:
Originally Posted by MikeB123 View Post

http://pastebin.com/8jqgKnaB

http://pastebin.com/Hh2jCJqq

 

 

Thanks!

 

It seems that the E17 has the same buggy descriptor than the E10:

http://www.head-fi.org/t/595071/android-phones-and-usb-dacs-how-to-increase-the-issues-priority-with-google/75#post_8469751

 

 

<4>[ 1040.806786] c0 usb 2-1: config 1 has an invalid interface number: 3 but max is 2
<4>[ 1040.806910] c0 usb 2-1: config 1 has no interface number 2
 
I"ll do a deeper analysis.
Reply
post #120 of 2344
7/1/12 at 2:11am
Quote:
Originally Posted by DanBa View Post

 

Thanks!

 

It seems that the E17 has the same buggy descriptor than the E10:

http://www.head-fi.org/t/595071/android-phones-and-usb-dacs-how-to-increase-the-issues-priority-with-google/75#post_8469751

 

 

<4>[ 1040.806786] c0 usb 2-1: config 1 has an invalid interface number: 3 but max is 2
<4>[ 1040.806910] c0 usb 2-1: config 1 has no interface number 2
 
I"ll do a deeper analysis.

 

 So am I right in thinking the only way to fix this is to create a kernel with the edits by tsynik which could sort it?

Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Portable Source Gear

Gear mentioned in this thread:

Head-Fi.org › Forums › Equipment Forums › Portable Source Gear › Android phones and USB DACs