July 24, 2013 By: Will Verduzco
We were all expecting it. In fact, we’ve all been waiting for it ever since this year’s Google I/O. However, that conference came and went, without a trace of Android 4.3. But after last week’s Android 4.3 leak, we knew it was finally coming soon. And in today’s Google event, which also marked the release of the Nexus 7 refresh, it has finally been made official.
So what’s new in this latest flavor of Jelly Bean? Here are some of the key changes, courtesy of the Android Developers blog post:
- OpenGL ES 3.0 — Game developers can now take advantage of OpenGL ES 3.0 and EGL extensions as standard features of Android, with access from either framework or native APIs.
- Bluetooth Smart — Now your apps can communicate with the many types of low-power Bluetooth Smart devices and sensors available today, to provide new features for fitness, medical, location, proximity, and more.
- Restricted profiles — Tablet owners can create restricted profiles to limit access to apps, for family, friends, kiosks, and more. Your app can offer various types of restrictions to let tablet owners control its capabilities in each profile.
- New media capabilities — A modular DRM framework enables media application developers to more easily integrate DRM into their own streaming protocols such as MPEG DASH. Apps can also access a built-in VP8 encoder from framework or native APIs for high-quality video capture.
- Notification access — Your apps can now access and interact with the stream of status bar notifications as they are posted. You can display them in any way you want, including routing them to nearby Bluetooth devices, and you can update and dismiss notifications as needed.
- Improved profiling tools — New tags in the Systrace tool and on-screen GPU profiling give you new ways to build great performance into your app.
Much has also been done to improve UI performance. Most notably, the Android 4.3 Platform Highlights page mentions a change to the hardware-accelerated 2D subsystem that modifies the stream of drawing commands to send the commands to the GPU in an optimized manner. And in instances when the CPU is required, these operations are now multi-threaded, allowing the use of multiple CPU cores. Improved window buffer allocation also speeds up buffer allocation, resulting in speedier rendering starts. And to best harness the GPU’s power in 2D hardware-accelerated tasks, the system now uses OpenGL ES 3.0 for optimized texture management and to maintain higher gradient rendering fidelity. Of course, however, the main use of OpenGL ES 3.0 will be to provide game developers with the framework and native API access they need to produce high quality and efficient games.
Another major highlight in this Jelly Bean refresh is a substantial refresh to the notification system, whereby third-party apps can observe the stream of notifications and display them or transfer them to nearby connected Bluetooth devices. And just as before, notifications can be enabled or disabled per app. Building upon this, however, now users are allowed to see and toggle which apps have access to the notification stream.
The tablet multi-user feature has also been revamped. Now in 4.3, users are given the option to set up restricted profiles. This allows owners to easily create separate environments for each user, with the ability to manage restrictions in apps available in those environments. This feature is aimed to sharing your device with friends and use at kiosks.
Other notable changes include Bluetooth Smart Ready to aid in discovery and communication with nearby devices, Bluetooth AVRCP 1.3 support for richer interactions with media streaming devices, an improved DRM framework, and a VP8 video encoder.
You can learn more by heading over to the Android Developers blog post and Android 4.3 Platform Highlights page. If you’re lucky enough to own a Google Nexus 4, Nexus 7, Nexus 10, or Galaxy Nexus, you can expect this update to come over-the-air shortly. And if you find yourself impatiently waiting, you can get a head start and download the images by visiting the Nexus device factory images.
February 13, 2013 By: Conan Troutman
Those of you with Nexus devices will most likely have received an update to Android version 4.2.2 by now. The news of the OTA was broken on the forums yesterday by XDA Senior Member kataria.vikesh. Those of you who have not are no doubt on the verge of applying the update manually after a lengthy session of gawping at your status bar awaiting that notification. Nexus 4 owners may find themselves waiting a little longer than the rest, as there doesn’t seem to be any sign of an update for the device yet. However, the changes have already been merged into some custom ROMs. This latest version, build number JDQ39, was also pushed to AOSP yesterday meaning that we should soon see this latest update becoming unofficially available on a whole host of devices.
So what exactly are the changes in 4.2.2? Well, we already know from the version number that this isn’t a huge update, there are however some notable additions to functionality and tweaks to the UI. Most of these are directed more towards the end user, but one of which will no doubt be a welcome addition for some developers out there so let’s start with that one.
ADB Whitelist: Connecting your device to a PC with USB debugging enabled will now bring up a prompt which displays your PC’s RSA key and offers the option to add this information to a whitelist. Unless a specific computer is allowed access via this prompt, the device will be inaccessible via ADB. This of course adds an extra level of security to the device. Providing you use a secure lock screen any potential thief with a little ADB knowledge will be unable to access the prompt and add themselves to the whitelist. Unfortunately, it seems that this feature may not provide much more security for users with an unlocked bootloader, according to the guys at Android Police.
Other changes include:
There’s speculation as to whether the issue of streaming music over A2DP has been addressed. Some users are reporting an improvement, whereas others are not. If anyone is able to spot this in the commits then please let us know in the comments.
February 9, 2013 By: Will Verduzco
By now, you’ve no doubt heard of Paranoid Android. In fact, there’s a good chance that if you own the Galaxy Nexus, Nexus 4, Nexus 7, or Nexus 10; you’re either running the ROM yourself or you’ve given it a try in the past.
For the few unfamiliar, Paranoid Android’s defining characteristic is what they call Hybrid Engine. Contrary to what many believe, this is not “tablet mode,” though that is one of many things that can be accomplished using Hybrid Engine. Rather, Hybrid Engine allows you to select both dpi and layout on a per-app basis. Rather than being forced to modify the look of your entire device, you can optimize your applications to what works best for each and every one.
A new and important feature that has come to light in the recent beta builds, and now sees light in the official release of PA3 is the PIE control system. What this allows one to do is to disable onscreen buttons and use a swipe gesture to access various common functions, thereby freeing up valuable screen real estate. The menu can be seen in the header image above, as well as the video below.
Per-app color, another significant feature in PA3 and recent pre-release builds, allows you set system UI colors on a per-app basis. Want a black system bar for your launcher, but a blue one for Facebook? No problem. Have more eccentric choices in mind? That’s fine too.
The most recent (and most specific) addition is screen calibration for the Google Nexus 4. While the vast majority of third-party reviews have praised the device for its screen, build quality, responsiveness, and overall value; some have been quick to point out that the screen seems under-saturated, especially to those coming from overly saturated S-AMOLED devices. Rather than trying to offer a simple band-aid solution with RGB calibration, PA3 also corrects for the device’s gamma issues to give it the punch the IPS panel deserves. While you’ll be hard-pressed to find anyone who says that the Nexus 4 screen looks “bad,” the calibration has been met with much praise thus far, and the team only hopes that these changes are incorporated upstream.
Are you salivating yet? Those eager to get started should visit the threads below. Naturally, there will also be a plethora of unofficial ports for various unsupported devices. So if you’re looking for a build for your device, be sure to check in your device forum to see if someone’s already attempted porting the ROM. Even better, you could always try porting and building the ROM from source yourself.
January 14, 2013 By: Haroon Q. Raja
Whenever there is mention of custom ROMs for Android, AOKP is one of the first to come to mind. Over the past year, the popularity of this source-built ROM has skyrocketed to make it one of the most recognizable third party development projects. Though over the past few months, several AOKP users (including myself) decided to jump ship to other ROMs because of the delay in a release based on Android 4.2. There is good news: The wait is over, as Team Kang has officially released Android 4.2.1-based AOKP JB-MR1 Build 1, starting with the Nexus line of devices.
As with the changes in Android 4.2 from 4.1, the changes in this AOKP release from the previous one aren’t as many as we’ve seen in previous major releases. However, they are still substantial enough to improve the overall user experience. Apart from all the AOKP features of the previous Jelly Bean builds, you’ll get:
The Nexus line of devices was the primary focus of AOKP since its very inception, and they are the first ones to get this release as well. However, that doesn’t mean other devices will be left out. The team is working on Galaxy S II, S III, Note, and Note II support for the next build, with builds for many other devices to follow. Until then, you can grab the ROM for Nexus devices from the following links:
The team is also planning a return to its (bi)weekly release schedule once builds for more of the officially supported devices are ready. More information can be found at the AOKP website.
January 8, 2013 By: jerdog
Bootloaders are like locks on a cookie jar: They’re just begging to be unlocked. When users on XDA see a locked bootloader, they immediately start looking for the accomplished developer who is working on hacking the device. It is for this reason that we like to hold Google Nexus devices as the gold standard for how manufacturers (and carriers) should approach their bootloaders, as well as firmware openness.
Nexus devices are easy to unlock: You go into fastboot mode, type ‘fastboot oem unlock’, and you’re done. Easy peasy. Of course, Google’s method involves an automatic wipe of your data, which functions as a pseudo-security measure. There of course is a way to get that data back after the wipe on the Galaxy Nexus, but what most users fail to think about is locking their bootloader again once they’ve gotten their ROM to where they want it to be. This opens up their device to all sorts of potential problems, especially those of the malicious kind.
Recently there has been talk about the Samsung Exynos 4 memory exploit, which leaves Exynos 4-based devices open to malicious attackers. With the fact that Samsung has never fixed the eMMC Brick Bug issue, which affects stock and non-stock Exynos 4 devices, you have the perfect storm of malicious attacker meets manufacturer negligence. Users can have their devices bricked and/or wiped in a matter of moments, and they would be none the wiser.
XDA Senior Member segv11 came across something in the Nexus bootloader, which is cause for concern for the Galaxy Nexus, Google Nexus 4 and Google Nexus 10. segv11 created a bootloader unlock, which does not follow the normal convention. Instead, it falls back on a process where you can keep your bootloader locked, and still keep a sense of security. He does this by simply changing a couple of bits in the /param partition, while keeping the bootloader locked for security reasons. XDA Elite Recognized Developer AdamOutler also released a similar process for the Galaxy Nexus back in April of 2012 which utilizes a brute-force method to unlock the bootloader by replacing the entire /param partition instead of just adjusting the bits.
This app highlights an issue with the way Google has chosen to lock the bootloader, especially when it’s easy to just change the aforementioned bit. What else is contained in there that can be hacked? What else is there that a malicious app, with root privileges, could potentially render your device a pricey brick? It’s for this very reason that we encourage users to be very careful before they mess around with their devices, and to make sure they read all of the instructions the developers put together beforehand.
December 5, 2012 By: Former Writer
Over the last couple of weeks, we’ve been bringing you news of mskip’s toolkits making it to the Nexus 4 and the Nexus 10. It’s a popular and well known toolkit with extensive features. There is a second toolkit making its way around to Nexus devices, known as Wug’s Nexus Root Toolkit. We brought you news that it was released for the Nexus 7. Now, it’s available for the Samsung Nexus S and Nexus S 4G, the Nexus 4, and the Nexus 10.
XDA Recognized Developer WugFresh has been busy this month. The toolkit has made to five different Nexus devices in just a few weeks. The core features of the toolkit are the same for all releases, and include:
This program will automatically bring together all the files you need to unlock and root your device in a few clicks, or flash it back to stock and re-lock it. You can also use this program to backup/restore all your important data, flash zips, set file permissions, push and pull files, install apps, and much more! With the included file association options, you can perform tasks like flashing zips, installing apps, restoring android backup files, and flashing/booting img files with just a double click! The program includes a full featured interface for automating tasks in TWRP, enhanced restore features, an in-built auto-updater/notification system, ‘any build’ mode, and quick tools utilities. All the latest Android builds and Nexus devices are now officially supported, including the new Nexus 10, Nexus 4, and 3G Nexus 7 (with full 4.2.0 support).
The premise of this toolkit is to make rooting easy and provide a few extra features like installing applications and pushing files. For those looking for a root-bringing toolkit, you should give them a shot.
Unless you’ve been hiding under a rock somewhere, you know that Google has released a few new devices (Nexus 4 and Nexus 10), as well as a refresh to the Nexus 7. What makes this different from previous Nexus releases is that there are two new manufacturers added to the mix with Asus (Nexus 7) and LG (Nexus 4) joining Samsung (Nexus 10 as well as Nexus S and Galaxy Nexus) and HTC (Nexus One).
We recently told you about XDA Elite Recognized Developer Chainfire’s new project to automatically root devices and keep them as stock as possible, and we now have an important update to share with you, as Chainfire has added CF-Auto-Root support for the new Nexus devices. What makes this update different from previous versions is that fastboot support has been enabled, as well as an updated version of SuperSU (v0.99).
Follow the links below to learn more and to obtain the downloads.
December 3, 2012 By: Haroon Q. Raja
With the release of Android 4.2, Google added several new features to the the OS. While the CyanogenMod team has officially started the transition to 4.2 based CM 10.1, it may take a while for them to start rolling out the latest 10.1 nightlies for all devices. That’s where XDA Recognized Developer and Team Euroskank member makelegs has stepped in, providing us with a working self-compiled kang built from the latest CM 10.1 sources for the Google Nexus 10.
Announced through Google+ by makelegs, this build joins the CM 10.1 builds for Nexus 7 already bring provided by Team Euroskank. As with all nightlies, some glitches here and there would be expected. However, based on the response in the forum thread, the build seems solid enough to be usable, and it lets the early adopters among us give CM 10.1 a shot before it’s officially released.
You can find more information and download links in the forum thread.
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.
It didn’t take long for developers to sink their teeth into the latest Nexus releases. In an almost instantaneous fashion, the Nexus 4 received a toolkit to help with all rooting and recovery needs and the Nexus 10 was rooted. And now, there is an awesome toolkit for the Google Nexus 10.
XDA Senior Moderator, Recognized Developer, and toolkit guru mskip has released yet another all encompassing toolkit—this time, for the Nexus 10. As we’ve come to expect from his toolkits, there are many, many features. It’s perfect whether you just got your device or have had it awhile. The feature list includes:
* Install correct adb/fastboot drivers automatically on Windows xp/vista/7/8 32bit+64bit
* Backup/Restore a single package or all apps, user data and Internal Storage
* Backup your /data/media (virtual SD Card) to your PC for a Full Safe backup of data
* Unlock/Re-Lock your Bootloader
* Root Stock Jelly Bean builds (upto 4.2.0 JOP40C)
* 1-Click For All to Unlock the Bootloader, Root, Rename the Restore File and Flash Custom Recovery
* Perform a FULL NANDROID Backup of your system (Boot, Cache, Data, Recovery and System) via adb and save in Custom Recovery format on your PC which can be Restored via CWM Recovery
* Pull /data and /system folders, compress to a .tar file and save to your PC
* Dump selected Phone Partitions, compress to a .zip file with md5 and save to your PC
* Install BusyBox on your phone
* Extras, Tips and Tricks section available to all ToolKit Donators
* Auto Update ToolKit to latest pushed version at startup (donator feature)
* Program up to 10 Quickpic slots and run them very quickly (donator feature)
* Mods section to automatically perform certain tasks on your phone
* Download Google Stock Image directly to correct ToolKit folder for extracting and flashing (no need to move it manually anymore)
* Flash Custom Recovery or Google Stock Image to phone
* Rename the Recovery Restore File present on some Stock Roms
* Use adb sideload in Custom Recovery to root/unroot zip files very easily
* Boot into CWM Touch Recovery without Flashing it
* Boot or Flash .img Files directly from your PC
* Install a single apk or multiple apk’s to your phone
* Push Files from your PC to your phone
* Pull Files from your phone to your PC
* Dump selected LogCat buffers to your PC
* Dump BugReport to your PC
* Set Files Permissions on your phone
* Open new Command Prompt for manual input
* Reboot Phone to Fastboot Mode or Android from fastboot mode
* Reboot Phone to Fastboot Mode, Recovery, Android or Download Mode from adb mode
Too long, didn’t read? It does pretty much anything you could possibly need it to, including obtaining root, unlocking, re-locking, recovery, pulling logs, reboot options, installing APKs, and lots of other stuff. If you have the Nexus 10 and you plan on doing some modding, this is definitely a toolkit worth trying out.
To learn more, head to the original thread.
It didn’t take long for developers to get their hands into the Google Nexus 10. There were bootloader unlocking tutorials and root guides basically upon release. ClockworkMod Recovery and TWRP have also been released for the device. Now, source-built ROMs have started showing up for it, including a favorite among XDAers, ParanoidAndroid.
XDA Recognized Developer jaybob413 has released the popular AOSP ROM for the Nexus 10. For those who don’t remember, ParanoidAndroid is a forked ROM (formerly from CyanogenMod, but now directly from AOSP) with a unique hybrid mode that lets users select per-app DPI and layout settings. Of course, it has Android 4.2 as the base, making it among the first ParanoidAndroid ROMs to do so.
There are some issues, though. As jaybob413 explains:
Before you go any further, 4.2 still has a quite a few bugs that need to be resolved by Google. You can read about some of them HERE
This is a blind build depending on the community for testing, so YMMV. Please make sure you have backups for anything you don’t want to lose.
Caution is advised. No promises this will not eat your device and take over your home.
So while users haven’t really reported any issues, this is definitely a work in progress and there could be issues. This on top of the issues that are already known in Android 4.2.
For the full details, check out the original thread.
November 21, 2012 By: Former Writer
While some may have a problem understanding why we would want to do so, the Nexus 4 was rooted in short order. With the whirlwind of Nexus 4 news, it’s easy for some to forget there was a second Nexus device released. The Samsung-made Nexus 10 was released as well. And just as you would expect, it already has root.
XDA Senior Member zedomax has released a series of videos to help get users rooted. There is one video for each supported operating system. As it so happens, all of the big three are supported. So users can root whether they’re running Windows, Mac, or Linux. Included also are step by step tutorials with pictures.
To make things a little easier, all the needed files come in a single zip file. So it doesn’t matter which tutorial you need to follow, all the tools are in a single spot. Just download the zip, unpack the files, and follow of the tutorials to get rooted with a custom recovery. In addition, zedomax has posted a short FAQ video for those who experience bootloops after unlocking the bootloader. Users have reported that the tutorials work well, and so far there have been no major problems.
For all the tutorial videos and download links, check out the original thread.
November 15, 2012 By: Former Writer
Well that didn’t take very long, did it? The new series of Nexus devices has been released, and developers have already started getting their hands dirty coding for the new toys. As they are Google devices, their bootloaders are unlockable. And after only a couple of Fastboot commands, they are ready to be developed on. The Nexus 10 got its first big piece of development with the release of an unofficial build of ClockworkMod Recovery.
XDA Senior Member shimp208 ran the stock recovery.img through the old ClockworkMod Builder and released the results. They are the 220.127.116.11 versions and there is a touch and non-touch version available.
While there are a lot of members who would love to help test it, most Nexus 10 tablets haven’t been delivered yet. So this is a truly untested recovery. Thus, proceed at your own risk. To help reduce the risk of potential soft bricks, shimp208 has put up a warning for users who don’t intend on testing. We’ll echo that here: Don’t flash if you don’t intend to test it. Once it has been thoroughly tested, the okay will be given and users can start flashing things all they want. For those that do want to test it, you’ll have to flash it via Fastboot, as there are no alternate methods right now.
For more details, check out the original thread.