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 37

post #541 of 5936
guys still getting this when i plug my ibasso d2 boa in/out of the usb otg cable on my nexus 7.. <6>[ 1930.223413] Switched to NOHz mode on CPU #1 <6>[ 1930.223985] cpufreq_interactive_input_connect: connect to elan-touchscreen <6>[ 1930.224211] auto_hotplug: CPU1 up. <6>[ 1930.485021] auto_hotplug: Offlining CPU, avg running: 180 <5>[ 1931.508349] CPU1: shutdown <6>[ 1931.512884] auto_hotplug: CPU1 down. <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 Any suggestions?
post #542 of 5936
You have always the same error message "usb 2-1: device descriptor read/64, error -71".
 
Do you use a new modded kernel in which "static int old_scheme_first = 1"; substitutes "static int old_scheme_first = 0;"?
post #543 of 5936
I've got an Evo 4G LTE that is running CM10 with a kernel that has USB host mode support, and USB Host Controller sees my Fiio E7 as a USB DAC, so I'm pretty sure it should work, but I've found no way to actually get audio to be piped through it.
post #544 of 5936
Thread Starter 
Quote:
Originally Posted by cthalupa View Post

I've got an Evo 4G LTE that is running CM10 with a kernel that has USB host mode support, and USB Host Controller sees my Fiio E7 as a USB DAC, so I'm pretty sure it should work, but I've found no way to actually get audio to be piped through it.

 

It'll be using the stock Jelly Bean implementation of USB Audio, which does NOT work with DACs unless they are made specifically for it. There is a mod to allow the Nexus 7 to utilise DACs not made to operate specifically with the Jelly Bean USB Audio implementation though, so I would check at XDA to see whether anyone has/can port this mod to your 4G LTE.

post #545 of 5936

It's sort of confusing trying to order through their sight. Where do I need to go?

post #546 of 5936
I recently got a Galaxy S3, Canadian version (T999V), and tested an old M-Audio Duo USB audio interface I had since long time. To my surprise it worked and sounds great but when I unplug it the audio in the S3 crashes and stops working. I have to restart the phone in order to recover sound. Re-plugging the Duo doesn't bring it back. This interface runs at 44, 48 or 96 kHz sample rate, set through dip switches located in the bottom. I had it set at 48. I've seen videos of people unplugging and plugging DACs to the S3 by just pulling the cable in and out. Is there a safer way of "ejecting" the device to avoid crashes? Any other clues?

Thanks!

Hector
post #547 of 5936
Would I be able to playback 24/192 files with the galaxy note 2 if the external dac that I hook up to the note 2 supports 24/192 audio?
post #548 of 5936

Yes using the latest Trinity Kernel

post #549 of 5936
Quote:
Originally Posted by micksaddress View Post

Yes using the latest Trinity Kernel


A link please.
post #550 of 5936

hey guys, support this bounty to have USB audio added to CM10 or AOKP http://forum.xda-developers.com/showthread.php?t=1930664 ... you don't need to add $, just show your interest! if we can show that a large group of people are dying for this feature it will more likely be added.

post #551 of 5936
Quote:
Originally Posted by micksaddress View Post

Yes using the latest Trinity Kernel

That's good to hear, renders getting a fiio x3 or hifiman 901 a waste of time :D

post #552 of 5936
Quote:
Originally Posted by atmospheric View Post

hey guys, support this bounty to have USB audio added to CM10 or AOKP http://forum.xda-developers.com/showthread.php?t=1930664 ... you don't need to add $, just show your interest! if we can show that a large group of people are dying for this feature it will more likely be added.

Will this be for all the note 2's also? Or only for the at&t galaxy s3?

post #553 of 5936
Quote:
Originally Posted by zachchen1996 View Post

Will this be for all the note 2's also? Or only for the at&t galaxy s3?

if the commit is added to CM10 or AOKP it will be for the Samsung galaxy s 3, and will likely be compatible with the galaxy note II dude to their similarity.  it could probably be ported to other devices without to much difficulty but this is not guaranteed.  

 

it really boggles my mind why google decided to make a standard for a device, instead of going with the status quo.  

 

edited for accuracy


Edited by atmospheric - 10/19/12 at 8:23am
post #554 of 5936
Quote:
Originally Posted by brandonnash View Post

Any love (USB audio) for the galaxy nexus? I have seen the s3 getting all the praise but a lot of the s3 providers seem reluctant to put out 4.1. AFAIK only Verizon hasn't stepped up for the nexus/4.1 combo. With millions of users I am surprised this hasn't been talked about more.

 

If I understand the following XDA thread correctly, the standard Galaxy Nexus desktop pogo dock will output digital audio:

 

http://forum.xda-developers.com/showthread.php?t=1851321

 

Now this is certainly not "portable", and it is not USB audio, but for home listening it might be quite nice.  As I have the Galaxy Nexus and this dock, I am seriously thinking about picking up something like the Fiio 17....

 

Cheers

post #555 of 5936

Hoping to get a little clarification. Looking to get a samsung Note 2 within a few weeks and now hoping to get a usb DAC to pair it with :)   

 

The E17 does not work due to its firmware. Does fiio know about this, and are they coming out with a firmware update? It looks like the unit can have an update. thx all

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