December 2, 2012 By: Former Writer
Earlier, we brought you news that the universal naked driver received a well deserved update. For those who are unaware of the universal naked driver, it is a project that fits as many drivers as possible into a single driver install to save new users hassle. It’s been updated once again, and this time for the newer Nexus devices.
The new update supports the Nexus 4, Nexus 10, Nexus Q, and—even though it’s a little late—the Nexus S. XDA Senior Member 1wayjonny posted the update in the Nexus 4 forums. The drivers are supported on Windows XP, Vista, 7, and 8.
For most Windows machines, it’s a matter of installing the drivers like any other driver, which is install and go. Windows 8 users may have a more complicated time installing it, but it’s still pretty easy. 1wayjonny posted a tutorial for Windows 8 users to disable driver signature enforcement, so that the drivers can be installed correctly. Once installed, all your devices should be supported under a single driver. For anyone who has a number of devices or plans on adding a member of the Nexus family to their device list, this is definitely something to check out.
To learn more, check out the original thread.
The Nexus Q, Google’s new cloud-based media center, is one of the most intriguing devices to hit the market this year. Recently, we wrote about unlocking the device and installing Android apps. The latest mod for the device comes to us from XDA Forum Member fredc888, and allows users to connect an HID-compliant mouse to the media player, further enhancing the device’s capacity to run apps and games.
Since the Q doesn’t have a traditional Bluetooth menu to connect to devices other than Android phones or tablets, the Bluetooth stack configuration file must be directly edited to allow input devices and connect to them automatically. This requires unlocking the bootloader, which wipes the device’s data partition. Unbricking options for the Nexus Q are very limited, so users should be extra careful when writing to the device.
If you have a Nexus Q and would like to add Bluetooth mouse functionality, check out the mod thread. Be sure to provide feedback and thank fredc888 for his contributions. As always, keep your eyes on the Portal and the Q forums for the latest updates on all things concerning the device!
July 9, 2012 By: Jimmy McGee
In this episode, Jordan talks about the important articles on the XDA Portal. Jordan talks about the CyanogenMod team starting work on Jelly Bean-based CyanogenMod 10. Also covered is the step-by-step guide on how to compile kernels from source. Jordan talks about the petition for root for the Verizon Galaxy S III, and the root and recovery for the Verizon Galaxy S III.
Jordan then talks about the latest news for the new Nexus line of devices. There is an easy-to-follow root guide for the Nexus 7, along with unbricking instructions. Finally, the article about rooting, unlocking and installing apps for the Nexus Q is covered. What are you waiting for? Check out this video now!
The Google Nexus Q is unlike any other Android device out there. It’s round, there’s no touch screen, and many reviewers still have no idea what niche this device is actually supposed to fill. This is XDA-Developers, however, and we try not to discriminate. That said, despite no touch screen and no obvious purpose, the Nexus Q is still seeing some development.
To start, it is actually possible to unlock this device just like any other Nexus device. XDA Recognized Contributor fiveipads has written up a quick little tutorial to help users get the Nexus Q unlocked. The method is traditional for Nexus devices as it’s just the old fastboot oem unlock. A little further in the thread, XDA Forum Member fredc888 gives a quick tutorial on getting the device rooted as well. Not too shabby for the uncanny device.
Additionally, there is also being work done on running Android applications on the Nexus Q. While the guide isn’t quite complete yet, XDA Forum Member shodutta92 has written up a tutorial on how to install and run applications. It’s a highly irregular process, which involves using ADB to install the applications and Terminal commands to run them. The interface of the applications is still a little tricky, but there has been some success with the monkeyrunner tool found in android-sdk/tools/. There is also some talk about using a Bluetooth Input Device Emulator. Eccentricity aside, the device has a pretty decent start to its development.