Shared publicly  - 
NOTE: The Verge's article on this ( says I'm an Android developer and I made S&S work on the Nexus Q.  It wasn't me - it was a software engineer at my startup, Apportable, named Philippe Hausler.  I basically everything but programming at Apportable.

Further adventures of the Nexus Q (and the Nexus 7)

We got Swords and Soldiers to run (well, start up) on the Q! Amazing!

We tried to run Osmos on it, but there's a multitouch requirement that the Q somehow does not satisfy :(.

#nexusq   #io12  
Corentin Debains's profile photoSam Hiatt's profile photoFL C's profile photoRyan Warner's profile photo
so jealous... seriously..
Everyone's pretty impressed with how well it runs out of the box.  I just enabled debug mode and the engineers went to town on it.
I am kind of wondering if this Nexus Q is a dare for the Ubuntu group.  I looked at the specs, and it could potentially be a platform for them.  There was a little bit of a wink there when they said hackable.  It actually seems like the ideal place to do a dual system.  This is just my guess though.  
How can you show the tablet screen on TV ? I think you can't :( Why they didn't put a HDMI in the tablet? 
The picture is slightly misleading - the monitor is showing output from the Nexus Q, not the Nexus 7 (the Nexus Q is behind the monitor).
+Al Sutton - I don't think the Q's digitizer works like that. I'm pretty sure it's just aware of whether it's being touched or not. I don't think it even knows locations for single touches.
Currently have a Ubuntu build ready for it... just waiting to get my hands on it to both run Ubuntu in a chroot and natively.

From what I can tell, the micro usb port should support USB Host OTG, so you can connect a mouse and keyboard to it...
javk b
You guys you try get a HID mouse connected via Bluetooth? Maybe it can generate some of the touch events. Bind via shell command (hciattach?)
We haven't tried that yet.  But my coworker Marc is splicing a USB and microUSB cable together to make an adapter to try to plug in a mouse that way (there's a real adapter on the way, but we're impatient).
Christina, Really dumb question... How did you folks manage to get the Q into USB debug mode without a settings UI?
There's a Settings UI in the Nexus Q app for Android devices.  I installed the app on the Nexus 7 and then registered the Q with the app via Bluetooth, then enabled debug mode.
Was there any specific process for getting the application to display on the TV? Also: Do you know if the Nexus Q application is based on the Google TV remote that is open source? Can't wait to get my own to do some work with.
If you guys get DroidMote Server to run on the Nexus Q you will be able to control it via DroidMote Client from another android device.
Do you know if the micro-usb can be used as an input for an audio device like a turntable or MP3 player?
+Thomas Sohmers The process was that we 1) installed the game APK on the Q via adb, 2) hooked the Q up to the monitor via HDMI cable, and 3) launch the app using intent (you can find the specific intent command by getting a logcat when you launch the app from an app launcher on a phone).

+Vikram Ramesh I don't know, but that would be interesting to play around with.  I would guess that there would be software which would allow you to control that interaction at some point.
During the install, have you looked for the application waiting for instructions from connected devices?

I believe that one of the main feature I would like to add is the DLNA compatibility, to play my own content. I would like to have exactly the same features, but with my private network data!

Another interesting thing would be to use the tablet as a remote/touch screen that would be designated as touch screen for the Q.
+Corentin Debains I don't think the Q indicated that it was looking for a source of input when the game was installed.   Swords & Soldiers does require some kind of touch event or mouse click or something to progress beyond the title screen, and we weren't able to provide that, so it just stayed in the initial launch state.  One of my coworkers is trying to figure out if it'll accept mouse input via microUSB.

I don't know much about DLNA (I'm not a developer - I just play one on G+), but being able to use your own network data for the Q and using a tablet as a touch screen remote are likely very doable.
+Christina Kelly Thanks for your answer :) I hope we will all together (basically you right now) find a way to create new Q service apps (like the embedded one!)

I also hope the embedded one is not only a single app but multiple bricks that we will be able to use (for example: the NFC discovery/linking, the apps communication protocol between the linked devices...). That would make our life easier!
This is exciting. Sounds like a mythTV frontend using the Q for display and a touchscreen for control shouldn't be too far off.
 Trying to get root access.

NOTE: be very careful about 2 things.
1)about uninstalling the Nexus Q app once you have successfully connected to the nexus Q
2) about unpairing from the Nexus Q from the Bluetooth settings menu....

I did a combination of #1 and #2 (forget in which order or home many times)....And what ended up happening was I was not able to get the app to reconnect to the Nexus Q as "owner".... Fortunately, there is a way to do a factory reset from the device itself (unplug and replug the nexus Q, and place your palm on top of the Q's single LED light until it flashes purple)....I only learned this because of the rare case I actually read an instruction manual...
Update... Got it rooted... My nexus q's bootloader is unlocked and I pushed su to /system/xbin/.. I'll post details on what I did later.
Hi Folks,
1.5 hrs later

I Got HID Mouse to work on the Nexus Q. So you can use a HID mouse to do your touch events.  I'll post instructions on how to do it.
I wrote a simple android app that uses the Bluetooth API's to pair and connect to the HID mouse. (no hcitool/hciattach/etc needed)
However, the trick was that on the Nexus Q, the HID host profile is disabled. This requires pushing a new updated configuration file for the bluez stack /system/etc/main.conf, with the "input" module NOT disabled. And doing that requires you to have root access to /system.
There was another person that already got clockworkmod to work. So once I unlock my bootloader, and booted the clockworkmod recovery image, I could mount /system with write access and update the needed file... I'll writeup everything later tonight.

But here's how it looks.
P.S. Sorry, I was using a "Microsoft" mouse. It was the only HID Mouse I had at home...
Thanks for posting this information guys, currently trying to get it into debug mode.

 +Fr Ch I can't see the debug option in the menu as a Q owner so I think I'll try those instructions that were ironically in the manual lol I must not somehow be the "owner"

Edit: Nope, even doing a factory reset doesn't show up the debug slider in the Q app

Edit 2!: I found out that the USB Debugging menu in the Nexus Q app shows up when you turn on Developer Options in the Settings > Developer Options menu of Jellybean on the Nexus 7. +Tomi Blinnikka  You might want to test this as well on your devices
Add a comment...