[WiR3D]

Lol the apples falling off the wagon, because the Steves not doing their jobs

 

[bmichels]

Gentleman,

Sonde i have booth an iPhone AND an Android Samsung
galaxy S3 phone, I am considering purchasing the "AlgoRhythm Solo -dB DAC"
to use it with my MacBook pro and also my Android Samsung
galaxy S3 phone or iPhone

I understand that the AlgoRhythm Solo -dB support 24/194 from the Mac
and 16/48 from an iPhone, but.... (1) will it work With a Samsung
Android galaxy S3 or Note 2 phone ? And (2) what will be the
limitation bits/kHz with the Samsung Android phone ? Will it be
better than the 16/48 when connected to an iPhone ?

Many tanks in advance for your reply

Bertrand

 

[NZtechfreak]

Quote:

Gentleman,
Sonde i have booth an iPhone AND an Android Samsung
galaxy S3 phone, I am considering purchasing the "AlgoRhythm Solo -dB DAC"
to use it with my MacBook pro and also my Android Samsung
galaxy S3 phone or iPhone
I understand that the AlgoRhythm Solo -dB support 24/194 from the Mac
and 16/48 from an iPhone, but.... (1) will it work With a Samsung
Android galaxy S3 or Note 2 phone ? And (2) what will be the
limitation bits/kHz with the Samsung Android phone ? Will it be
better than the 16/48 when connected to an iPhone ?
Many tanks in advance for your reply
Bertrand

 
Not sure about what limit will be listening from an iPhone, but it will be 16/48 with the S3 I think.
 
No idea if it will work with the S3, I don't think anyone has tried it yet? Not on DanBa's list as far as I can recall.

 

[DanBa]

Quote:

Received my OTG cable for my Samsung S3 today and was able to play music with the UD100 DAC on my first try

and it sounded very good with the O2. I also tried my Centrance DACmini (desktop DAC/Amp) but could not get any sound out using Poweramp. I can hear the relay when I connect the S3 but no go. I also tried my DACport with a powered USB hub but again no sound.
I will download the emulator that Danba mentioned and will post the log back later. Cheers!
Edit:
Here the log output for DACmini
http://db.tt/BCvWD5lw

 
 
The Galaxy S3 detects the DACmini:
 
<6>[155961.354628] usb 1-1: new full speed USB device number 11 using msm_hsusb_host
<6>[155961.525115] usb 1-1: New USB device found, idVendor=1c07, idProduct=0004
<6>[155961.525176] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
<6>[155961.525206] usb 1-1: Product: CEntrance DACmini
<6>[155961.525237] usb 1-1: Manufacturer: CEntrance Inc.
 
But then:
 
<4>[155961.551362] 11:1:1: cannot get freq at ep 0x1
 
"
>These messages are from the snd-usb-audio driver.
>
>It seems your device [USB DAC] doesn't conform to the USB Audio specification.
>
>It might be possible to work around this.  Please try the following:
>edit the file sound/usb/usbaudio.c, search for "cannot get freq", and
>replace the following line:
>
>  return err;
>
>with:
>
>  return 0;
>  
>
 
And that did the trick: it works!
So what now: should it stay like it is.
 
Well, there is nothing else that could be done at this point except ignoring the error."
http://sourceforge.net/mailarchive/forum.php?forum_name=alsa-user&max_rows=25&style=nested&viewmonth=200405
 
 
Unluckily, this modification was done in the UAC1 USB audio driver of the Nook kernel
https://github.com/dalingrin/nook_kernel/blob/encore-32/sound/usb/usbaudio.c#L1298
 
as well as in UAC2 USB audio driver of the Galaxy S3.
https://github.com/sgs3/GT-I9300_Kernel/blob/master/sound/usb/clock.c#L237
 
 
There is a same issue with an Arcam rDAC driving by a UAC2 USB Audio driver this time.
http://forums.slimdevices.com/showthread.php?93310-Async-USB-Dac-Experiments-testers-wanted&p=696302&viewfull=1#post696302
 
"I get no playback and dmesg includes the line:
"ALSA sound/usb/clock.c:227: 2:1:1: cannot get freq at ep 0x1""
 
Successful workaround:
"2) ignoring the request from the dac and always using a more frequent interval to poll for frequency."
http://forums.slimdevices.com/showthread.php?93310-Async-USB-Dac-Experiments-testers-wanted&p=696565&viewfull=1#post696565
 
"The new kernel includes:
- possible work around for the rDAC issue (based on my option 2, it ignores the parameter from the dac and uses a smaller parameter - the question is whether the dac likes this..?)"
http://forums.slimdevices.com/showthread.php?93310-Async-USB-Dac-Experiments-testers-wanted&p=696686&viewfull=1#post696686
 
"rDac Success!"
http://forums.slimdevices.com/showthread.php?93310-Async-USB-Dac-Experiments-testers-wanted&p=696803&viewfull=1#post696803
 
 
Hence, a question to be asked to Triode: what is the smaller parameter?

 

[BleaK]

Subbed!

 

[DanBa]

From ibasso 
...
You may ask why other products that use the ES9018 dont have the fade-in problem.  On the DX100, we use our own driver to replace andoird's Audioflinger.  The android's audioflinger only allows 16/44.1 output. That is also why all other android products only can output 16/44.1, but the DX100 can output 24/192.
If all tracks are downsampled to 16/44.1, then there is not noise btw tracks, and the mute function is not needed.
On the CD players that use the ES9018, the whole CD has the same sample rate, mute function isnt needed as well.
...
 

 
 
Quote:

I understand that the AlgoRhythm Solo -dB support 24/194 from the Mac
and 16/48 from an iPhone, but.... (1) will it work With a Samsung
Android galaxy S3 or Note 2 phone ? And (2) what will be the
limitation bits/kHz with the Samsung Android phone ? Will it be
better than the 16/48 when connected to an iPhone ?
 

 
There is no limitation in open source Android: Google specifies Android-specific USB audio, Samsung implements standard USB audio.
 
 
As far as I understand, Audio Flinger is just a mixer.
 
 

 

 

 

 

 
 
As far as I understand, Audio Flinger can be:
. removed: iBasso DX100?
 
. improved: use a variable sampling rate (parameter)
"That is the very point that mixer output buffer is transferred to hardware related codes I think, and the audio clip is in mMixbuffer, with size mixBufferSize. In this buffer, there are PCM raw audio data with 44100Hz sampling rate, 2 channels and 16 bits little endian as its param."
http://xzpeter.org/?p=254
 
. replaced by other module like PulseAudio:
http://arunraghavan.net/2012/01/pulseaudio-vs-audioflinger-fight/
 
 
The USB audio driver for ALSA of the Galaxy S3 is able to drive USB Audio Class 2 (UAC2) devices (i.e. USB DAC playing up to 32/384):
https://github.com/sgs3/GT-I9300_Kernel/blob/master/sound/usb/card.c#L246
 
 
The Android-powered Meizu MX 4-core is able to MHL-output a 24/192 stream:
http://www.innerfidelity.com/content/sound-smartphone-meizu-mx-4-core
 
 

 
 

 

[BBEG]

From what I understand, the digital out from the MX is not normal MHL, just through the MHL port. You must turn on SPDIF audio in the settings and have an adapter for a coaxial cable to the DAC. I'm hoping it's also possible using the same setup as used by the Galaxy S3/Note 2, but I won't know until I get the phone (next week, woot!).
 
Shopping list right now:

1. USB OTG cable ($5) (one coming with phone, but want another just to be sure)
2. USB-SPDIF coaxial adapter

1. USB-to-HDMI cable ($7)
2. short coaxial/SPDIF cable ($8)
3. the smallest 4-port powered USB hub I can find

 
I'm not sure what kind of cable I need for SPDIF audio. I have a coaxial and an optical adapter as both came with my E17. I'd appreciate someone educating me on how this will work. I realize not all DACs will come with SPDIF input but since I have one that does, and I've seen desktop DACs that do, I think it's worth asking about.
 
(Edit: evidently coax and optical are just two ways of moving a digital stream, with coax being more durable.)
 
 
The powered USB hub is to take advantage of the OTG capability of the phone to use a keyboard, mouse, and USB-to-HDMI out to a monitor or TV. It will also let me test to see if I can run this same setup and use the last open USB to attach to the linked coaxial adapter and still get digital audio while using the other peripherals.

 

[bmichels]

Ahhhh... I'm also VERY interested to Know if the Galaxy S3/note 2 can output 24/192 kHz to a USB dac.

Please let me Know.

 

[figgie]

DanBa
 
correct
 
the AudioFlinger can be bypassed in its entirety. That is what the DX100 does to have direct access into the ESS as to stream upto the 24/192 that they.
 
WIth that said, that require custom firmware to initialize the ES9018. Custom drivers for the ES routines. Particularly the handling of bit rate changes prior to the stream of I2s being read by the ES9018. The music player alone from the DX100 crashes without the ESS drivers being present (i was able to pull the apk file but it did not work in emulator in anything that was not 2.3.1).

 

[WiR3D]

this is all getting very interesting.

 

[thread]

I have an AT&T GS3 (i747) and I am in need of a rom that will work with a USB DAC but will not annoy the crap out of me with Touchwiz.

Does anybody know any particular AOSP-based roms that include the necessary Samsung code to make the USB DAC functionality work?

This doesn't seem to be a need that many folks have, so it's not something I hear about often. However, NZtechfreak has suggested that such a rom exists.

Thanks in advance!

 

[DanBa]

Quote:

Hence, a question to be asked to Triode: what is the smaller parameter?

 
Reply from Triode: (Thanks again Triode!)
http://forums.slimdevices.com/showthread.php?93310-Async-USB-Dac-Experiments-testers-wanted&p=723310&viewfull=1#post723310
 
"I'm not convinced this is the same thing. The change I made for rDAC is in post 219:
http://forums.slimdevices.com/showthread.php?93310-Async-USB-Dac-Experiments-testers-wanted&p=702222&viewfull=1#post702222
 
This is basically ensuring the interval requested for the syncpipe (the feedback connection) is not too long for the size of the ehci schedule maintained by the linux kernel - essentially it can't schedule periodic intervals which are too long as the size of the schedule held in memory means that scheduling packets into the future goes beyond the size of the schedule held."
 
Next step: we have to find some developer to test this patch. We also have to contact some Samsung engineer.

 

[fzman]

will the following work correctly?
 
Galaxy S3 plus OTG cable,connecting via a  USB Hub,to HRT Headstreamer (known to work), and a USB drive, either stick or spinner, plus a usb charger, say 5000maH, to power the devices so they don't deplete the phone's internal battery.That is, use the hub plus the external battery/charger as if it is a powered hub, to power the connected USB devices...
 
thanks for any suggestions/recommendations based on things you have found to actually work correctly.  
 
Best,
 
Mark

 

[DanBa]

I think so.

 

[DanBa]

Quote:

I have an AT&T GS3 (i747) and I am in need of a rom that will work with a USB DAC but will not annoy the crap out of me with Touchwiz.
Does anybody know any particular AOSP-based roms that include the necessary Samsung code to make the USB DAC functionality work?
This doesn't seem to be a need that many folks have, so it's not something I hear about often. However, NZtechfreak has suggested that such a rom exists.
Thanks in advance!

 
[size=13.63636302947998px]10-20120801-EXPERIMENTAL-i9300-CODEWORKX build ?[/size]
 
[size=13.63636302947998px]I just switch from iPhones to the Galaxy S3; I'm not familiar with different Android mods.[/size]
 
"Since flashing KERNEL-CM-10-20120801 | Audiopatch for 10-20120801 & Camerapatch for CM10-20120801 yesterday, the USB Audio driver appears to have vanished (was working after flashing just the 10-20120801-EXPERIMENTAL-i9300-CODEWORKX build)
 
I've flashed today's build with a full wipe, and its the same story, the X360 controller and USB HDD still work fine, but no USB Audio, My guess is that it was removed from the kernel?"
http://forum.xda-developers.com/showthread.php?p=29691769&highlight=usb+audio#post29691769