[akwok]

Quote:

 
akwok bought a new Pico DAC/Amp in April, and he says its just plug and play with his North American Galaxy S3.

 
Right.  I just plugged in my Pico for "fun" without really expecting it to work at all.  I was extremely surprised when it did!  This is the cable I used, coupled with a generic mini-USB to male USB:  http://www.amazon.com/Micro-Female-Cable-Galaxy-I9100/dp/B0073EPXO4
 
I only tested it with the Poweramp music player though, but I don't think that matters at all.  What probably does matter is the chipset itself -- North American S3s use a Snapdragon chipset, whose USB implementation is more likely than not to be way different than the Exynos chipset on international S3s.  I skimmed through some of the posts in this thread and it seems that those who have issues getting the Pico to play nice with the S3 are on the Exynos chipset.
 
Edit:  I was running the stock kernel and stock rom provided by Rogers here in Canada.  That might also make a difference, especially with kernels such as Siyah which might strip out useful yet niche functionality in order to preserve battery life / increase performance.

 

[ah_kap]

akwok, thanks for the chime in. that helps to clarify a bit. it seems like the the exynos based s3 is the one that is having problems with the pico 
 

 

[sanity8me]

It's definitely a possibility, akwok, but I would imagine it's more to do with Samsung's TouchWiz UI since this is what seems to allow the S3 to work with some of the certain external DAC's while other Android phones still can't.
 

 

[Kojaku]

Quote:

It's definitely a possibility, akwok, but I would imagine it's more to do with Samsung's TouchWiz UI since this is what seems to allow the S3 to work with some of the certain external DAC's while other Android phones still can't.
 

The only issue with this suggestion is that ah_kap tried it with the stock kernel, which is Samsung's TouchWiz/ICS implementation...I think this, meaning the chip set, probably the issue, honestly. I have my pico DAC/Amp ready to go for when I buy my AT&T US SGS3 this Saturday. I'll post if it works IMMEDIATELY on Saturday night.
 
Kojaku

 

[ah_kap]

Quote:

The only issue with this suggestion is that ah_kap tried it with the stock kernel, which is Samsung's TouchWiz/ICS implementation...I think this is probably the issue, honestly. I have my pico DAC/Amp ready to go for when I buy my AT&T US SGS3 this Saturday. I'll post if it works IMMEDIATELY on Saturday night.
 
Kojaku

FWIW, I have tried it with 3 different region stock roms with the stock kernel and the results are the same. still no go. It may very well be the exynos chipset...

 

[DanBa]

Quote:

DanBa, thanks for the explanation.
I will upload a dmesg log file from my international S3 later when i get a chance to load a stock kernel on my S3.
tapatalk'd
update:
here is the dmesg log for a stock kernel LF1
http://dl.dropbox.com/u/24975342/dmesg2.log

 
 
There is the same error (i.e. 62 ETIME) than with Siyah kernel.
http://www.head-fi.org/t/608535/wolfson-dac-confirmed-for-galaxy-s3/615#post_8577555
 
<7>[   18.896475] c0 s5p-ohci s5p-ohci: urb f1c14200 path 1 ep0in 5ec20000 cc 5 --> status -62
 
 
A (same?) problem:
http://search.gmane.org/?query=EBOX-3300&author=Toan+Pham&group=gmane.linux.usb.general&sort=relevance&DEFAULTOP=and&query=
 
<7>[49289.147493] ohci_hcd 0000:00:0a.0: urb cf384e60 path 1 ep1in 5c160000 cc 5 --> status -62
 
The solution:
"Regarding your query, indeed, there are some our clients reported that their USB devices sometimes could not work on EBOX-3300, but when they connected their devices to EBOX-3300 via an USB hub, the fault disappeared.
 
We have found that the fault is caused by the USB 2.0 PHY. It will
lead to USB 2.0 PHY and some devices sometimes miss commands when they are handshaking."
 
 
Could you use a powered USB 2.0 (i.e. high speed / full speed) hub (S3>>high speed>powered hub>full speed>>Pico) just for testing purposes?
 
Another example of a USB 2.0 hub fixing some hardware bug:
http://forums.slimdevices.com/showthread.php?94512-Announce-Enhanced-Digital-Output-app-USB-Dac-and-192k-Digital-Ouput&p=701516&viewfull=1#post701516
 
"There seems to be a bug in the Touch hardware that prevents async from working properly when running at full speed. In this case you need the USB 2.0 hub which talks to the Touch at high speed, but talks to the DAC at full speed. This gets around the bug in the Touch. This is only needed for an async full speed DAC. An adaptive full speed DAC or a high speed DAC of any type can be used without the hub. Thus if your DAC is a full speed only DAC (ie has a maximum sample rate of 96KHz) and you get ticks and pops, it is probably running using async mode and will need the hub to work properly."

 

[Kojaku]

So...is it an issue with the chip? In other words, the snapdragon shouldn't have any issues but the exynos does?
 
Kojaku
 
Quote:

 
 
There is the same error (i.e. 62 ETIME) than with Siyah kernel.
http://www.head-fi.org/t/608535/wolfson-dac-confirmed-for-galaxy-s3/615#post_8577555
 
<7>[   18.896475] c0 s5p-ohci s5p-ohci: urb f1c14200 path 1 ep0in 5ec20000 cc 5 --> status -62
 
 
A (same?) problem:
http://search.gmane.org/?query=EBOX-3300&author=Toan+Pham&group=gmane.linux.usb.general&sort=relevance&DEFAULTOP=and&query=
<7>[49289.147493] ohci_hcd 0000:00:0a.0: urb cf384e60 path 1 ep1in 5c160000 cc 5 --> status -62
 
The solution:
"Regarding your query, indeed, there are some our clients reported that their USB devices sometimes could not work on EBOX-3300, but when they connected their devices to EBOX-3300 via an USB hub, the fault disappeared.
 
We have found that the fault is caused by the USB 2.0 PHY. It will
lead to USB 2.0 PHY and some devices sometimes miss commands when they are handshaking."
 
 
Could you use a powered USB 2.0 (i.e. high speed / full speed) hub (S3>>high speed>powered hub>full speed>>Pico) just for testing purposes?
 
Another example of a USB 2.0 hub fixing some hardware bug:
http://forums.slimdevices.com/showthread.php?94512-Announce-Enhanced-Digital-Output-app-USB-Dac-and-192k-Digital-Ouput&p=701516&viewfull=1#post701516
 
"There seems to be a bug in the Touch hardware that prevents async from working properly when running at full speed. In this case you need the USB 2.0 hub which talks to the Touch at high speed, but talks to the DAC at full speed. This gets around the bug in the Touch. This is only needed for an async full speed DAC. An adaptive full speed DAC or a high speed DAC of any type can be used without the hub. Thus if your DAC is a full speed only DAC (ie has a maximum sample rate of 96KHz) and you get ticks and pops, it is probably running using async mode and will need the hub to work properly."

 

[DanBa]

May be.
 
Apparently the System-on-Chips Snapdragon S4 of the US S III and Exynos 4412 of the international S III include their own USB transceiver feature.
 
"To reduce the total system cost and enhance the overall functionality, Exynos 4412 includes many hardware peripherals, such as TFT 24-bit true color LCD controller, Camera Interface, MIPI DSI, CSI-2, System Manager for power management, embedded GPS and GLONASS, MIPI slimbus interface, MIPI HSI, four UARTs, 24-channel DMA, Timers, General I/O Ports, three I2S, S/PDIF, eight IIC-BUS interface, three HS-SPI, USB Host 2.0, USB 2.0 Device operating at high speed (480Mbps), two USB HSIC, four SD Host and high-speed Multimedia Card Interface, Chip to Chip interface, and four PLLs for clock generation."
http://www.galaxys3blog.net/2012/05/exynos-4412-cortex-a9-15ghz.html
http://www.qualcomm.com.au/products/snapdragon

 

[ah_kap]

looks like i will need to get another usb powered hub and try it again. I will post the results over the weekend after i get another hub.

 

[fueltank]

Anyone tried ibasso D12 with the international GS3?

 

[NZtechfreak]

Any updates from international owners in relation to the PICO working/not working? Just curious, my PICO has yet to ship and I'm just wondering about buying at AT&T S3 and SIM unlocking it for use with the PICO if it truly isn't working with the international one... My partner needs a phone upgrade and she would gladly take my international S3 off my hands, so could be win-win!

 

[fueltank]

Just installed Siyah and ExTweaks. Anyone else running Siyah kernel?
Voodoo Sound looks like it's dead?

 

[NZtechfreak]

Quote:

Just installed Siyah and ExTweaks. Anyone else running Siyah kernel?
Voodoo Sound looks like it's dead?

 
I'm not presently, but was earlier on. The amping and stereo separation seemed to help, however DAC direct and 128x oversampling didn't appear to do anything on that earlier build (I see the available tweaks have changed a bit since then, so not sure what the current state of play is). I think Siyah and ExTweaks is about the only way to really exert much more control over the sound output at the moment, at least without resorting to a USB DAC.
 
How are you finding Siyah + ExTweaks?
 
...in relation to Voodoo Sound, I still expect it to come, but who knows how long it might take.

 

[Kojaku]

I CAN CONFIRM IT, EVERYONE! The Pico DAC/Amp is simply plug and play with US Galaxy S3s! yay! Listening to my LCD-2 Rev.2 out of the Pico at my university commons right now . This is the most glorious portable setup I've ever owned !

Kojaku

 

[NZtechfreak]

Quote:

I CAN CONFIRM IT, EVERYONE! The Pico DAC/Amp is simply plug and play with US Galaxy S3s! yay! Listening to my LCD-2 Rev.2 out of the Pico at my university commons right now

. This is the most glorious portable setup I've ever owned

!
Kojaku

 
Cool. I confirmed with nnotis too - his PICO is working with the international version. My PICO will hopefully arrive next week (at the same time as my Beyerdynamic T5p!), so I will check with my international one then. I have a garnet red AT&T S3 coming to me also (will SIM unlock it for use here) and will check that too.