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 176

post #2626 of 5146
Quote:
Originally Posted by Twinster View Post


The Fiio E18 look promessing if you can wait a few weeks.

 

Wow, it does look nice.  I usually don't pay that much attention to Fiio because they are generally below my price point (all though I respect them as a company for what they have done for the audio industry).  However, in the real world I design outerwear, and I really like the look of the Fiio E18.  It looks like it might be priced a bit higher than previous Fiio DAC/amps which is why I am excited for it.

 

Quote:
Originally Posted by Theogenes View Post

No prob man. If you're considering using the Leck as a desktop, you might want to look into getting something that either converts USB audio into digital coax, or just use a source that outputs digital coax-- I believe it does 24/96 from S/PDIF, and supposedly sounds better to boot (haven't tied it myself). There are some portable USB-to-S/PDIF adapters that are around as well in case you want to do 24/96 on the go, but I haven't tried any of them. And my comparison is here-- be warned, however, that I have never used two words when twenty would suffice ;). 

 

I'm also very interested in the D-Zero SE-- I think the D-Zero frankly kicks everything's butt from a value-for-money perspective. Killer little device. 

 

As for the DragonFly, I believe some people have had success with a few of the USB-powered DACs by using special splitter cables and a portable power source, although I don't recall if it worked with the AQ DF specifically. The only time I tried to use a portable battery (a Monoprice dealio), I got a lot of noticeable noise on the line, so I dropped it pretty quickly-- but others have had better results, I think. 

 

As for sound quality, a couple of brief qualifiers: the only actual A/B comparison I did was with the PCSTEP and the Glacier, and my tastes drew me to the PCSTEP; I apparently listen at unusually low volumes, and prefer a brighter sound signature; I am in absolutely no way whatsoever an audio professional of any kind; and while my musical tastes are varied to say the least, I tend to listen to more dissonant music (metal, some classical and string groups, some jazz) and atypical time signatures than your average bear. So keep those in mind. But in general, I believe I lean a bit more towards the Leck and Meier than the Glacier, and while I love the D-Zero, I think those two are a bit more clear and neutral. 

 

Hope this helps! Search the forums for used devices, as the Leck, Meier, and Apex tend to hold their value pretty well IMO, so you might be able to try a couple of them out without losing your shirt in the process. That's how I got my Glacier ;)

 

 

Your opinion seems to be inline with what I've read.  The glacier has a beautiful form factor, but its DAC (while not bad) aren't any thing spectacular for the price point.  It seems like the sweet spot is ~$300 for portable DAC/amps and I'm more than happy to spend that much.  I tend to enjoy a neutral sound signature as long as the components in question are very good (I EQ my car a bit because it doesn't have the best components in it).  I've also been waiting for the iBasso DX50 to come out as a potential upgrade for my portable rig, but I've been leaning towards consolidating my phone/portable DAP.  I think I'm going to wait a few weeks/month(s) to see how the iBasso D Zero-SE, and the Fiio E18 fair against the above DAC's.  

Thanks for everyone's help!  Being an audiophile would be so much more expensive/time consuming if Head-Fi wasn't such a great place!

post #2627 of 5146
Quote:
Originally Posted by Raenmor View Post

Hi all,

 

I was able to use FiiO E07K with HTC One X running CyanogenMod without using AuidoRecorderPro, or any other third-party applications. And it is running 96/24 as well.

It involved a little bit of programming, but nothing too hard. If you're interested - check the thread at xda (http://forum.xda-developers.com/showthread.php?t=2305631), 'cause copying the instruction here will be messy.

 

Hope it will help at least some one dt880smile.png

 

Interesting 96/24 mod!

Bravo!

post #2628 of 5146
Quote:
Originally Posted by DanBa View Post

Interesting 96/24 mod!
Bravo!

Yeah, this is very interesting. I plan to give it a go (I also have a FiiO E07K), but I'm currently running an AOKP build with the 3.4 kernel, which currently has no USB OTG support at all. I guess OTG support will come as the kernel matures so I may wait, or I might flash back to the latest 3.0 build and have a go getting it working on that.
post #2629 of 5146

Rather good news!

The Google issue 24614 "Add support for USB Audio" has been switched from "Reviewed" to "Assigned".

https://code.google.com/p/android/issues/detail?id=24614&sort=-stars&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars

 

 

 

 

 

"Assigned (someone is on it, possibly behind closed doors, possibly anonymously, possibly on a closed-source component relevant for AOSP)."

https://groups.google.com/forum/#!msg/android-contrib/1RMecRPymU4/L91az8Rr9jIJ

 

"The expected issue life-cycle for most projects is something like this:

 

1. A user reports an issue and it has status New.

2. The issue is triaged by a project member, if it was not originally entered and triaged at the same time. It may be rejected by setting its status to Invalid, WontFix, or Duplicate. Or, it may be Accepted. It it is accepted, it is may be labeled with a milestone and a priority within that milestone, and it may also be labeled to identify the part of the product affected or the nature of the cause of the problem.

3. The project owner may ask for more information and the initial reporter may add comments to provide that information. The issue owner may set the status to Started.

4. Other users may provide additional comments that can help resolve the issue, or express their interest in having the issue resolved in a timely milestone.

5…

…"

https://code.google.com/p/support/wiki/IssueTracker

post #2630 of 5146

If the Google issue 24614 owner ask for more information, the USB Audio requirements should be:

 

Basic requirements:

1. Support for 24-bit/192kHz digital output

Rationale:

More and more USB DACs can support 24/192, and it is already supported in some Android USB audio implementations:

. USB Audio Recorder PRO

http://www.head-fi.org/t/595071/android-phones-and-usb-dacs/1080#post_8968861

. Modded CyanogenMod CM 10.1

http://www.head-fi.org/t/595071/android-phones-and-usb-dacs/2625#post_9614865

 

2. Support for USB ACA (Accessory Charger Adapter)

http://www.head-fi.org/t/595071/android-phones-and-usb-dacs/2580#post_9598490

Rationale:

An ACA-compliant Android device operating as a USB host is also able to charge at the same time. It draws power from an external power supply, or from an ACA-compliant USB DAC.

It is not a USB Audio feature per se, but such a USB ACA feature recommended by Google should encourage the mass production of USB OTG – ACA components, and prevent Android device manufacturers from implementing non-standard ACA.

http://www.head-fi.org/t/595071/android-phones-and-usb-dacs/2595#post_9601384

 

Optional requirement: USB Audio parameter settings like buffer size setting for sound quality tweaking purposes

Rationale:

. "The secret of USB Audio Recorder PRO [my preferred SQ music player]: "source direct" like the audiophile Audirvana player for Mac OS X?"

http://www.head-fi.org/t/595071/android-phones-and-usb-dacs/2475#post_9512914

. "An interesting example is the HRT music streamer II, it IS asynchronous USB, but it is still very sensitive to what happens in the computer. On the SAME COMPUTER I can make simple changes to OS scheduling parameters and get a huge difference in the sound. At one end of the scale it’s dull, lifeless, no depth at all, at the other end of the scale it is wonderfully alive, dynamic, huge depth etc. And all this by just changing a few numbers, NO change in hardware at all."

http://www.audioasylum.com/cgi/m.pl?forum=pcaudio&n=101397

 

 

Any missing USB Audio requirement?


Edited by DanBa - 7/15/13 at 11:05pm
post #2631 of 5146

AWESOME!!!! Now let's just hope it takes them less time to implement than it did to identify that this needed to be fixed ;). 

 

Can't see anything that you'd be missing there DanBa, other than possibly dictating asynchronous or something (which I'm not at all sure would be beneficial as it seems like it would limit connectivity options). Great work man!!!

post #2632 of 5146
Quote:
Originally Posted by DanBa View Post

Interesting 96/24 mod!
Bravo!

Now I want to try to run MPD server on android somehow, to bypass any interference from the os itself and communicate directly with alsa. Controlling it would be easy, there are tons of MPD Clients on android.

But until then you can try to use XBMC, it supposed to communicate with alsa directly as well.

EDIT: XBMC is no-go, at least for now. Alsa support isn't working properly. At least I can't get it to work. If someone else can - please share.
Edited by Raenmor - 7/14/13 at 7:54am
post #2633 of 5146
Raenmor, I found this the other day. My face lit up as it's something that I've wanted for years, myself.

An Android port of MPD itself.

https://play.google.com/store/apps/details?id=be.deadba.ampd
post #2634 of 5146
Quote:
Originally Posted by thread View Post

Raenmor, I found this the other day. My face lit up as it's something that I've wanted for years, myself.

An Android port of MPD itself.

https://play.google.com/store/apps/details?id=be.deadba.ampd

That's great! But now we have to convince the developer to include alsa output module, and we are good to go for bit-perfect audio output from android. biggrin.gif
post #2635 of 5146
Quote:
Originally Posted by Theogenes View Post

AWESOME!!!! Now let's just hope it takes them less time to implement than it did to identify that this needed to be fixed ;). 

 

Can't see anything that you'd be missing there DanBa, other than possibly dictating asynchronous or something (which I'm not at all sure would be beneficial as it seems like it would limit connectivity options). 

 

As far as I understand, the USB asynchronous mode seems to be no problem for the USB host (i.e. Android device): Samsung USB Audio or USB Audio Recorder PRO can drive the asynchronous HRT microStreamer.

post #2636 of 5146
Quote:
Originally Posted by DanBa View Post

As far as I understand, the USB asynchronous mode seems to be no problem for the USB host (i.e. Android device): Samsung USB Audio or USB Audio Recorder PRO can drive the asynchronous HRT microStreamer.

Makes sense. Thanks for the reply wink.gif
post #2637 of 5146

Did you ever end up making more of these?
 

I would love to buy one with a micro-b, usb-a female and a usb-a male .

 

Does anyone else know if those exist?  I bought this one http://www.ebay.com/itm/130892962220?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1497.l2649 but it didn't charge the phone.

 

Quote:
Originally Posted by Coop View Post

It works!!

Received my new soldering station yesterday, and tonight built me a crude but real world usable OTG + charging cable. In addition to the micro usb-b for the S3 and the mini usb-b for a DAC, it has an additional usb-a connector to hook up to an external usb powersource.

This will allow me to play music via external DAC & use satnav while driving my car without draining my phone battery (the music isnt much of a drain, but satnav with the screen at a useful brightness level...)

Once I find some connectors that I like enough I'll make a nicer finished one, or a few, or maybe a few more and sell some...

post #2638 of 5146

Great news about issue 24614.  Great news about that little bit of code Raenmor gave us.  Quick question about the latter: can a terminal emulator be used to add that code?

post #2639 of 5146
Quote:
Originally Posted by nnotis View Post

Quick question about the latter: can a terminal emulator be used to add that code?

Honestly i have no idea. Probably you can configure alsa through terminal, but it's much easier to use notepad++ or something like this to edit asound.conf. As for the audio_policy - I highly doubt that there is any way to do it through terminal.

2All: Does anyone here is (or knows) any decent developer that can activate alsa output in aMPD found earlier? There are sources available including ported alsa_output module, but unfortunately straightforward approach didn't work, so it requires some (unknown to me) modifications.
post #2640 of 5146

"Android Devices Play High Resolution Audio Using the AlgoRhythm Solo -dB":

http://cypherlabs.com/blog/post/android-devices-play-high-resolution-audio-using-the-algorhythm-solo-db

 

 

 

 

"Tracks of resolutions up to 24/192 now play from Android devices through the AlgoRhythm Solo –dB, at full resolution in asynchronous mode. Simply load tracks, or entire folders of tracks, onto a micro SD card, connect the devices and play tracks using the application "USB Audio Recorder Pro". It is actually very easy, but I've written a detailed procedure here for those who love to read manuals.

 

Equipment needed:

• AlgoRhythm Solo –dB
• Android device, such as Samsung S3 or S4
• OTG male micro USB to female USB A
• USB A to USB mini B cable (supplied with Solo –dB)
• USB Audio Recorder Pro application for Android, created by eXtream Software Development, $6.00 on the Google app store
• Headphone amplifier and headphones
• Recording format selection: wav/flac/ogg/aiff (No mp3)
..."
 
 
By the way, the AlgoRhythm Solo –dB is the 100th USB DAC on my list of USB DACs compliant with the Galaxy S3 from some $ to $2280.
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