The QRemote REST API documentation is now bundled into the application itself, but here’s a copy/paste for reference.

More...

I just finished setting up a repo on GitHub for QRemote: https://github.com/docBliny/qremote

It includes the source for both the Android application and the web interface.

I also updated the installable APK with the rough API documentation.

UPDATE July 14, 2012: I updated the APK to contain rough API documentation. Just navigate to http://192.168.1.1:8080/api.html adjusting the IP address to match your Q.

OK, it’s late (I mean early), but here’s a very rough alpha version of QRemote which let let you control the Nexus Q via a RESTful-ish API and your web browser. It’s developer-only friendly at the moment, but that shouldn’t a problem since only Google I/O attendees have them. If you’re brave enough to test it and have feedback, hit me up via Twitter, Google+, or email. I’m lazy at approving comments here on the site. Anyway, to the point…

GALLERY

Here it is in all it's glory.

Installation

• Download QRemote.apk here.
• Upload the file using adb with the following command: adb install QRemote.apk

Running

Unfortunately, you’ll have to manually start the application every time you power on the Nexus Q. I’m working on to get the boot message receiver to work with a signed package (seems to work fine with a debug build).

• Start the application with the following command: adb shell am start -a android.intent.action.MAIN -n com.blinnikka.android.qremote/.StartServiceActivity
• Open up a browser and navigate to port 8080. For example, http://192.168.1.1:8080/

Known Issues

• You need to start it manually every time you power up the Nexus Q.
• You have to know your Q’s IP address.
• You need to load up a playlist with the Play application on an Android device.
• Videos are not supported.

Uninstalling

• Run the following command: adb uninstall com.blinnikka.android.qremote

Upgrading

You will need to uninstall and re-install the application if you had the initial Alpha version as I changed the keys used to sign the application. Just follow the instructions above to uninstall and install again.

The video says it all.

Here’s a quick list of ways I’ve been able to control playback using the adb developer tool.

1. Send media key codes.
2. Send broadcast Intents.

The values for both options are listed in the following tables.

adb shell input keyevent 85

adb shell input keyevent 88

adb shell input keyevent 87

adb shell am broadcast -a com.android.music.musicservicecommand.togglepause

adb shell am broadcast -a com.android.music.musicservicecommand.next

adb shell am broadcast -a com.android.music.musicservicecommand.previous

adb shell am broadcast -a com.android.music.musicservicecommand -e command play

adb shell am broadcast -a com.android.music.musicservicecommand -e command play

asb shell am broadcast -a com.android.music.musicservicecommand -e command stop

OK, so I started “home automation month” last year in May then went ahead and immediately missed it this year. To make up for this grievous error, I put together a plug-in for the Vera home automation device that allows you to remote control a Yamaha RX-V3800 receiver.

You’ll need a Yamaha RX-V3800 A/V receiver (or compatible unit, such as the RX-V1800 or HTR-6190), an Ethernet-to-serial adapter to hook it up to your network, and of course a Vera unit.

The download and additional information can be found on the project page at http://code.mios.com/trac/mios_yamaha-plugin .

The Keyspan ER-RF1 USB remote is designed to work with Macs, but I just plugged it into my Vista machine and it showed up as a standard HID compliant device just fine. The keys, as far as I’ve had time to figure them out, are:

Now all I have to do is get some steering wheel bezels and suitable buttons to hook that up to the CarPC.