So I arrived home from Google I/O a few hours ago. Decided to plug in the Nexus Q.
Posted on 2012-07-01, 7 comments, 34 +1's, imported from Google+/Chainfire

NOTICE: This content was originally posted to Google+, then imported here. Some formatting may be lost, links may be dead, and images may be missing.

Reshared from

So I arrived home from Google I/O a few hours ago. Decided to plug in the Nexus Q.

First I needed to find a power socket thingy to convert from US plug to Dutch plug. Luckily I had a few lying around.

I also needed to install the Q app, which of course is not available from my country (typical Google-style thinking), luckily somebody posted it somewhere on XDA.

HDMI cable worked, but for some reason my receiver will not do 5.1 from YouTube videos on the Q that I know have 5.1 audio. I would try the optical out, but due to the Q's great design, my optical cable doesn't fit, I need a different one.

So I enabled USB debugging. Of course even the just-updated SDK drivers did not work with it - no biggy, the .inf is easy enough to modify. It was a bit of a hassle as my laptop was low on juice, and I didn't want to unpack all my bags to find the charger.

Anyhoo, finally I could go the "adb tpcip 5555" and "adb connect x.x.x.x:5555" route to use adb wirelessly, because this freed up the USB port to connect a mouse (wireless of course) using an OTG cable.

So, I went ahead and grabbed the APKs for Rockplayer and UPnPlay, and "adb install"ed both of them to the Q.

If you're wondering, this is how you start up UPnPlay: "am start -n cx.hoohol.silanoid/.Silanoid"

That did allow me to play some music and video from my DLNA server. This is far from an ideal - or an even at all workable - setup though. It does show the possibilities.

I could go on, but I've been awake way too long, I need to unpack, my girlfriend wants control over the TV back, etc.

For those interested: yes, I did also connect a USB hub (powered), and USB sticks and hard drives. The system does recognize them, but no auto-mounting, so we're going to need root for that (haven't tried / bothered yet).

Possibly the above has all already been done, I have not kept up with ANY news while I was at I/O or travelling. Maybe somebody has already made a custom firmware with XBMC or whatnot (if so, link me up!), but this was my first 2.5 hours with the Q.

Chainfire commented on 2012-07-01 at 17:28:

(Please comment to the original post here: instead of to this share, thx)

Herm Vasquez commented on 2012-07-01 at 20:00:

Thanks for the info. Well definitely take this into consideration as I am thinking of purchasing one when they become available

Shiv Manas commented on 2012-07-02 at 00:02:

+Herm Vasquez Why would you want to buy one? What does this do that a $25 raspberry pi cant?

Mario Miniaci commented on 2012-07-02 at 13:13:

+Shiv Manas Dass Err, it runs Android and a Pi doesn't (yet). But seriously - the hardware looks nice and solid but you're into Sonos money there, without the multiroom. Still, Zigbee could be the game changer.

Dave Vaughan commented on 2012-07-02 at 21:55:

Interesting... As a product where do you see the Q going. The Goog obviously have high hopes for this lil guy BUT where do they see it going? Where do you see this in the average Rooters home???

Dave Vaughan commented on 2012-07-02 at 21:58:

Actually... Feeding on the Sonos multi room comment I'm think an upcoming product used as an extention to the Q... The Q mini if you will... Extending to every room...

Mario Miniaci commented on 2012-07-04 at 08:08:

That would be a great extension to the Q. Technically, there's no reason why a current Android phone couldn't become and extension - it has a speaker jack, wifi, bluetooth, a touchscreen...

This post is over a month old, commenting has been disabled.