UPDATE 2/22/2014: Google kills the workaround without fixing the original issue. Total cluster-fail. #chromefail
Well, not completely (unless you’re an unlucky sod like me), but makes it unusable. You now have to reopen each previously closed tab one-by-one. No more clicking on “21 closed tabs” to open up what you were working on previously. Unfortunately, the new menu item is greyed out completely for me and doesn’t show _any_ recently closed tabs.
Luckily, there’s a way to disable this new feature (along with the new big search box and not seeing Chrome Apps in the start window):
- Open a new tab, and enter chrome://flags .
- Search for Enable Instant Extended API for Mac, Windows, Chrome OS.
- Select Disabled from the dropdown.
- Restart Chrome.
I spent a moment this morning slapping together another application for the Nexus Q. This one is really simple, and all it does is to use the LEDs to show the time. There are three “hands” that show the hour in white, minutes in blue, and seconds in red.
The video doesn’t do full justice to the ability to read the time. The camera picked up too much light around each hand due to the diffusion the LEDs have. For example, the second hand looks fully red in real life, and doesn’t have the rainbow band around it as seen on the video.
The QRemote REST API documentation is now bundled into the application itself, but here’s a copy/paste for reference.
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…
Here it is in all it's glory.
- Download QRemote.apk here.
- Upload the file using adb with the following command: adb install QRemote.apk
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/
- 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.
- Run the following command: adb uninstall com.blinnikka.android.qremote
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.
Here are a few random tidbits I’ve come across while messing around with the Q.
- Operating System: Android 4.0.4 Ice Cream Sandwich (SDK/API 15)
- Processor: OMAP4460 (dual ARM Cortex-A9 CPU and SGX540 GPU)
- RAM Memory: 1GB LPDDR
- Flash Memory: 16GB NAND
- Connectors: TosLink (S/PDIF) audio, 10/100BASE-T Ethernet RJ45, Micro HDMI (Type D), Micro AB USB, Banana jack speaker outputs (2 right, 2 left, 4 total), AC power (Figure 8)
- Wireless: Wi-Fi 802.11a/b/g/n
- Lighting: 32 RGB perimeter LEDs, 1 RGB status/mute indicator
- Hardware controls: Rotating top dome (volume control), capacitive touch sensor (mute)
- Weight: 923 grams (2 pounds)
- Diameter: 116 mm (4.6 inches)
- Product name: Tungsten
- Device name: Phantasm
- Board name: Steelhead
- Bootloader: steelheadB4H0J
- The Nexus Q Android application is called “setupwarlock”
- It looks like the hardware and software might support up to 2048x2048 resolution
- Closed captioning works for movies (or at least the Transformers movie that was given away)
- iFixit teardown: http://www.ifixit.com/Teardown/Nexus-Q-Teardown/9636/1
I’ve only quickly looked at the power consumption, but my Kill-A-Watt shows between 2-3W when the Q is on and playing music and the same based on a quick test of movie playback. This is with Ethernet and HDMI connected. The numbers will obviously be higher if you use passive speakers and the internal amplifier.
This is just a quick post to list out the applications that I’m aware of that use the LEDs on the Nexus Q and their priorities within the system. The priority determines which application gets to control the LEDs at any given moment. Higher numbers represent higher priority. I haven’t looked at the code close enough to see how duplicate priorities are handled, but I’m guessing that that situation is not deterministic.
I haven’t put a lot of effort into verifying whether the descriptions match reality of what the applications do. I’m sure I’ve missed applications, too. Feel free to let me know if something is off.
|Priority ||Application ||Description |
|0 / 100 ||TungstenLEDService ||Master volume. Uses 100 to override everything when volume is changing and switches to 0 otherwise. |
|5 ||Visualizer ||Displays theme-based animations. |
|10 ||NetworkLedController ||Network status indication. |
|20 ||HubBroker ||Bluetooth Pairing portion of the @home broker. |
|25 ||HubBroker ||NFC handler. |
Here’s a quick list of ways I’ve been able to control playback using the adb developer tool.
- Send media key codes.
- 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
Do the following at your own risk!
Now that we’ve got that out of the way, here are some caveats:
- The internal “SD card” will be erased (mine only contained empty folders).
- You will unpair the device from your other Android devices and will need to set it up again.
- I wouldn’t flash the boot ROM I’m providing below. I know I haven’t.
- Nexus Q
- Android Development Kit, including the adb tool and fastboot.
- Plug your USB cable between your computer that contains the Android developer kit and the Nexus Q.
- Run adb reboot-bootloader . The LED ring will stay solid red. You should also be able to do this by holding your hand over the mute LED when it boots. Just let go when the ring turns red.
- Run fastboot devices to make sure you’re connected.
- Run fastboot oem unlock to unlock the bootloader.
- Within five seconds, run fastboot oem unlock_accept . The Q will erase user data and reboot.
- Pair your Android device again with the Q.
- Turn on debug mode again.
- I also put together a new boot.img file that modifies default.propwith the following values:
- Download nexusq-boot.img.
- Run adb reboot-bootloader .
- Run fastboot boot nexusq-boot.img to start the Q with root permissions.
Now you can upload su and back your regularly scheduled Android hacking.
adb reboot recovery results in pulsing red LEDs. Touching the mute LED flashes white. I didn’t see anything show up via the HDMI connector. The only way to get out of this mode was to tap the mute LED repeatedly (about five times).