Android phones and USB DACs
Jun 2, 2014 at 5:10 AM Post #4,832 of 9,526
I'm using my nexus 5 with the HRT microstreamer (with CM11 nighlty builds - updating regularly). I got the issue with constant clicking after 5-6 minutes of listening (I assume it is buffering issue effecting asynchrous USB devices).
Is the C5D free of this issue? (I've tried my nexus 5 with a Fiio e07k, that was not showing this problem)
  I got the Nexus 5 & C5D working with cm-11-20140518-EXPERIMENTAL-hammerhead.zip 
It's an experimental, not a snapshot; let's see how stable it is.
 
Edit: can connect & disconnect without any issue. C5D bass boost & TPEOS H-300 is too much fun 
ksc75smile.gif

 
Jun 2, 2014 at 6:35 AM Post #4,833 of 9,526
  I'm using my nexus 5 with the HRT microstreamer (with CM11 nighlty builds - updating regularly). I got the issue with constant clicking after 5-6 minutes of listening (I assume it is buffering issue effecting asynchrous USB devices).
Is the C5D free of this issue? (I've tried my nexus 5 with a Fiio e07k, that was not showing this problem)

C5D doesn't have this issue with the nexus 5 & the experimental CM11 build I linked above. I haven't tried any other builds except the M6 snapshot, which didn't work at all.
 
Jun 2, 2014 at 8:42 AM Post #4,834 of 9,526
I had bad clicking on my moto g (using an HTC m8 now). It was a problem with the buffer setting. When you change the buffer you have to exit USB audio player fully for the setting to change. The clicking went away with the 4000 setting. If you change the settings in app and don't close it completely they won't stick.
 
Jun 2, 2014 at 9:07 AM Post #4,835 of 9,526
  C5D doesn't have this issue with the nexus 5 & the experimental CM11 build I linked above. I haven't tried any other builds except the M6 snapshot, which didn't work at all.

Thanks a lot for the confirmation, so there is hope for good quality audio on the nexus 5.
 
I had bad clicking on my moto g (using an HTC m8 now). It was a problem with the buffer setting. When you change the buffer you have to exit USB audio player fully for the setting to change. The clicking went away with the 4000 setting. If you change the settings in app and don't close it completely they won't stick.

USB audio player is working fine on my Nexus5, but I mainly use google play music (all access) or spotify - is there a way to change the standard android buffer size as well?
 
Jun 2, 2014 at 4:58 PM Post #4,836 of 9,526

... have you considered powering your DAC from the external battery pack and only using the phone to supply the USB data stream?



USB OTG-Y cable from Elijah Audio: apparently a clean 5V from an external battery could improve the USB DAC sound
https://www.facebook.com/ElijahAudio?ref=stream

. micro OTG (ID pin grounded) plug to micro / mini / standard plug USB OTG-Y cable:



Galaxy S4 >> micro OTG plug to standard type-B plug USB OTG-Y cable powered by a 5V battery >> Digitech USB DAC/amp with a standard type-B receptacle








. micro OTG plug to standard type-A receptacle USB OTG-Y cable:



Android phone >> micro OTG plug to standard type-A plug USB OTG-Y cable powered by a 5V battery >> USB DAC with a standard type-A plug like LH Labs Geek Out, AudioQuest DragonFly, HiFimeDIY Sabre, ....



Android phone >> micro OTG plug to standard type-A plug USB OTG-Y cable powered by a 5V battery + regular USB cable provided by the USB DAC maker >> USB DAC








 


So-called USB OTG cable with separated power and data signal lines from Elijah Audio:
https://www.facebook.com/ElijahAudio/posts/547143015400331



Android phone >> micro OTG plug to micro / mini / standard plug USB cable >> USB DAC
Galaxy S4 >> micro OTG plug to mini-B plug USB cable >> HRT Microstreamer USB DAC/amp with a mini-B receptacle






 
Jun 3, 2014 at 10:52 PM Post #4,837 of 9,526
   
The Galaxy S4 - Geek Out 450 non-interworking seems due to the non-quite-compliancy of the Geek Out descriptors to the USB specification (Universal Serial Bus Device Class Definition for Audio Devices):
http://goo.gl/pYJbTu
 
For example: Audio Streaming Format Type Descriptor:
bLength:              0x06
bDescriptorType:      0x24
bDescriptorSubtype:   0x02
bFormatType:          0x01
bNrChannels:          0x04
bSubframeSize:        0x20
bBitResolution:       0x07
bSamFreqType:         0x05
tSamFreq[1]:      0x880501 (8914177 Hz)
tSamFreq[2]:      0x080101 (524545 Hz)
tSamFreq[3]:      0x000125 (293 Hz)
tSamFreq[4]:      0x080200 (524800 Hz)
tSamFreq[5]:      0x050700 (329472 Hz)
 
The size bLength of this descriptor should be more than 6 (bytes)!
The USB audio code of the Galaxy S4 is not tolerant and the S4 seems to refuse to connect to the Geek Out due to invalid argument:
 
Logcat 05-16 11:53:07.762 I/usb_audio_hw(283): Open output Card=1 Device=0 rate=44100 period=1024 format=0
Logcat 05-16 11:53:07.762 E/usb_audio_hw(283): pcm_open() failed: cannot set hw params: Invalid argument

Good catch... And this issue already listed in my firmware bug fix too. In Galaxy S3, this bug won't be detected.
 
Thanks a lot,
Larry
 
Jun 3, 2014 at 10:56 PM Post #4,838 of 9,526
  Good catch... And this issue already listed in my firmware bug fix too. In Galaxy S3, this bug won't be detected.
 
Thanks a lot,
Larry

 
Awesome that you guys are on this. Thanks, Larry!!
 
Jun 4, 2014 at 3:44 AM Post #4,839 of 9,526
Dear DanBa and Larry
 
Hope the above mentioned attribute issue will enable the GeekOut to sound music when fed by an S4.
 
Do you think that using the following cable configuration:
 

will resolve the Earphones getting very HOT while connected to my S4 and GeekOut 450 DAC?
 
I did try the following connections:
1. S4 connected to GeekOut with regular Y-OTG cable fed by a battery - earphones get extremely  HOT
2. S4 connected to GeekOut with regular OTG cable - earphones get extremely HOT, connection is stopped after a short while due to large current draw
3. S4 is connected to a self powered (battery) USB HUB,  GeekOut is connected to a USB port - earphones get very HOT (not as hot as before)  
 
Jun 4, 2014 at 5:13 PM Post #4,840 of 9,526
I am wondering if you should wait for the fix issued by LH Labs.
 
Apparently your S4, your OTG cable and your earphones seem to be OK because your following setup is functional:
S4 >> OTG cable >> FiiO E18 >> earphones
 
and your following setup has some issues (S4 - Geek Out non-interworking, hot earphones):
(same) S4 >> (same) OTG cable >> LH Labs Geek Out >> (same) earphones
 
 
Another solution is that Samsung modifies the USB Audio code of the S4.
The USB Audio code of the S4 could become as tolerant as the USB Audio code of the Galaxy Note3, because the Note3 can work with the Geek Out.
http://www.head-fi.org/t/595071/android-phones-and-usb-dacs/4680#post_10542408
But finding a Samsung contact is not easy.
 
By the way, Samsung should have the same USB Audio code running on all Samsung's Android devices.
 
Jun 6, 2014 at 3:13 PM Post #4,841 of 9,526
Lenovo A10 & USB Audio Player PRO:
http://www.cnet.com/products/lenovo-a10/
http://www.tellementnomade.org/forum/viewtopic.php?f=82&t=2116&sid=a5b186eb85a96de8eef80230b76d880a&start=825
 
Lenovo A10 tablet >> HiFimeDIY Sabre USB DAC >> RSA SR-71B amp >> Unique Melody 3DD IEM
 

 
 
music files stored on USB hard drive > UAPP running on Lenovo A10 tablet >> HiFimeDIY Sabre USB DAC >> RSA SR-71B amp >> Audio Technica ATH-W1000X headphones
 

 
Jun 7, 2014 at 10:27 AM Post #4,844 of 9,526
The main issue for me with UAPP and UARP is the fact that currently audio streaming is not supported.
According to UAPP developers they may support streaming in the future.
I mostly listen to RDIO.
 
Jun 8, 2014 at 2:22 AM Post #4,845 of 9,526
BTW, did anyone have the opportunity to check the capabilities of the Galaxy S5 with external USB DACs that  are not compatible with the S4 (e.g. HRT, Verza, GeekOut, dragonFly, etc.)?  No need for UAPP/UARP.
 
Thanks
 

Users who are viewing this thread

Back
Top