March 12, 2014 By: Will Verduzco
It’s no secret that despite being a great device overall, the Google Nexus 7 (2012) offers less than ideal flash memory performance. While the issue has been mitigated to a certain extent through the use of TRIM, file system performance is still often the device’s Achilles heel. Because of this, it stands to reason that any steps taken to improve storage performance on the device will greatly improve the overall user experience.
XDA Senior Member legolas93 decided to take on the task of improving the Nexus 7′s storage performance through the use of F2FS, which is a different file system created to be more optimized to the characteristics of NAND memory in flash devices. But before we go any further, it’s important to note that when changing your file system, you will lose all of your data. So please make sure that you make a full backup, and then transfer that backup to your computer while you perform the required steps.
To get started, you must first download the F2FS-enabled kernel and a modified TWRP capable of reformatting the tablet with F2FS. Then you flash the kernel through your current custom recovery and the modified version of TWRP through fastboot. Next you access the modified TWRP and format to the new file system. And finally, you can restore your backup after copying it back onto your tablet form your PC.
December 15, 2013 By: eagleeyetom
As you all know, AOSP is the purest form of Android. All Nexus devices are shipped with relatively clean Android, baked by Google engineers. Constant and frequent updates make it a quite interesting position for all Android enthusiasts. But AOSP is pretty barebone, as it lacks many of the key features of skinned ROMs that many of us have come to enjoy. This is when the brilliant Xposed Framework enters the picture.
A few months ago, we talked about an Xposed Module aimed at bringing some goodies to Samsung stock ROMs made by XDA Recognized Developer wanam. This time, wanam created a module dedicated to Nexus devices owners running KitKat. This module allows you to customize many little things to make your stock ROM more suitable for your needs. With this kit, it’s possible to change the clock position, the type and color of your battery text, and so much more. Everything can be found in the original posts, where a video demonstrating the module is also available.
Nexus devices should not be limited to AOSP features only, and Wanam Kit gives you a great chance to enhance the user experience. More information and the module itself can be found in the development thread. Keep in mind that your device must be rooted and running the latest version of Xposed Framework.
December 11, 2013 By: Will Verduzco
Just two days ago, we wrote about how Android 4.4.2 was rolling out to the most recent Nexus devices. This was only four days after the Android 4.4.1 roll out. And earlier today, we took a quick look at what changed from 4.4 to 4.4.2. Now, we’re glad to report that the Android 4.4.2 source code has made its way over to the AOSP, and factory restore images are now available for the Google Nexus 4, Nexus 5, Nexus 7, Nexus 7 (2013), and Nexus 10.
Ever since Android 4.4.1 was released, we were wondering when the factory images would see the light of day. Thankfully, that day is today. And while users have been able sideload the incremental OTAs manually using adb sideload, it’s great to also have the freedom to perform a clean install, directly to the most recent version—either through flash-all.bat or by manually flashing the images directly through fastboot.
Google didn’t only provide us with new factory images for all the currently supported Nexus devices. They also released the full source code to Android 4.4.2. With this, your favorite aftermarket developers can start merging the new commits over from Google’s repos into their own builds.
End users looking to download the factory restore images can do so by heading over to the Nexus Device Factory Images page. Developers looking to start building with the new Adnroid 4.4.2 code can do so by browsing the 4.4.2_r1 source code directly on Google’s Git.
NEXUS 5 hammerhead:
NEXUS 7 2013 razor:
NEXUS 7 2013 razorg
NEXUS 4 occam:
NEXUS 10 mantaray:
NEXUS 7 2012 nakasi:
NEXUS 7 2012 nakasig:
December 9, 2013 By: eagleeyetom
Google likes surprises—we all know that. Four days after releasing the Android 4.4.1, they decided to push out Android 4.4.2, which is a bugfix release of a bugfix release. It’s probably one of the fastest releases in the history of the company.
A full list of improvements is still unknown, and hopefully we will notice what has been changed when the source comes out. Thanks to Sprint’s community moderator 4Social, we know that build KOT49H brings the following improvements:
- Fix for clearing the VM Indicator
- Fix for delivery of the VM Indicator
- Various additional software fixes
- Security enhancements
The OTA should be rolled out within next few days to all supported Nexus devices. Some of the packages are already available to download from Google servers. All you need to do is to execute the command adb sideload [file name] to flash it to your device.
The links for other devices should pop out soon, as well as factory images and proprietary blobs to download.
If you get the update, let us know in the comments below what you think about this release and if the changes mentioned above live up your expectations.
December 6, 2013 By: Will Verduzco
Ever since the release of Android 4.4 KitKat, we knew that it was only a matter of time before custom ROM developer teams started incorporating the goodies into their own builds. Accordingly, the CyanogenMod team stated their plans to release their Android 4.4-based CyanogenMod 11 once work on CM 10.2 had finished. Approximately one month later, the CyanogenMod Team has now reached the M1 Milestone in their Android 4.4-based CyanogenMod 11 ROM for certain Nexus Devices.
Not every device is receiving official CM11 M1 love. In fact, it is only available for “actively AOSP-supported Nexus devices.” In other words, this means the Google Nexus 4, Nexus 5, Nexus 7, and Nexus 7 (2013). Because of this restriction, though, you can expect a relatively bug-free experience. Devices other than the supported current Nexus fleet will be receiving official CM 11 nightlies instead.
What are your thoughts on this new approach to pushing out Nexus device releases a bit earlier? Let us know in the comments below!
[Source: CyanogenMod Blog]
Android is six years old now. One week ago, we presented the first part of the Android story. Now, it’s time to continue the journey.
A long time ago in a galaxy far, far away—located in Mountain View, the first version of the operating system dedicated for tablets was born. Google called it 3. 0 Honeycomb and presented it alongside the Motorola Xoom.
November 19, 2013 By: Will Verduzco
Capping off a busy day chock-full of KitKat news, Google has just released a new build of Android 4.4 to the AOSP servers and various recent Nexus devices. The new build comes in at version KRT16S, and it replaces the older KRT16O build.
The KRT16S update is currently available for the Nexus 4, Nexus 7 (2012 – all variants), Nexus 7 (2013 – all variants), and Nexus 10. Curiously left out, however, is the Google Nexus 5, which features a different build altogether (KRT16M). Also of note, this new KRT16O build is unrelated to the mystery KOT31B build seen a week and a half ago on the Chromium Issue Tracker.
According to AOSP Moderator Conley Owens, the new build is largely a bug fix build. As such, you shouldn’t expect too many user-facing features. That said, users looking to get in on the action can easily do so by going to the Nexus Factory Images page and downloading the latest firmware images. If building from source is more up your alley, head over to the Android Git and Nexus Driver Binaries page.
[Source: Android Building Google Group]
November 14, 2013 By: Will Verduzco
Ever since Android 4.4 KitKat was released, the question quickly turned to when devices other than the Google Nexus 5 would get to see the goods. We’ve seen various unofficial builds pop up for unsupported devices. In fact, we’ve highlighted quite a few highly functioning releases for a few of the more popular devices currently available. But up until yesterday, if you wanted to enjoy Android 4.4 KitKat in official capacity, you needed to own a Nexus 5.
Then, Google pushed out the official KitKat OTA updates for the Nexus 7 (WiFi only), Nexus 7 (2013, WiFi only) and Nexus 10, and the OTA links were soon captured. However, the timeframe for the Nexus 4 (as well as the Nexus 7 variants with mobile data) was still up in the air, with the only official statement being that it would come soon. Apparently, “soon” actually meant the following day. To that end, the official Android 4.4 KitKat restore images are now available for the Nexus 4, Nexus 7 (all variants and both years), and Nexus 10. Along for the ride are the proprietary driver binaries, which enable ROM developers to make fully functioning builds for these devices. Curiously, the OTA update for the Nexus 4 has not started making its way out to handsets. That said, we can’t imagine it’d be too long now that the KitKat images for the device have been released.
If you’re an end user, installation is as simple as downloading the images and executing the flash-all.bat file. Alternatively, you can extract the available archive and flash them piecemeal through fastboot by executing the command fastboot <partition name> <image name and path>. This will enable you to flash without losing data.
Update: It looks like some of the update links on Google’s site are currently down. We assume this is because they are likely being uploaded to the website. Keep trying every now and then, as we’re confident that they will be live soon.
[Many thanks to reader Sampo S. for sending in the tip!]
November 14, 2013 By: Will Verduzco
Yesterday, we were happy to share the news that the official Android 4.4 KitKat updates were being rolled out to the Nexus 7 (2012), Nexus 7 (2013), and Nexus 10 via over-the-air updates. Naturally, however, not everyone has yet received the official OTA update. And making matters a bit more complicated for those wishing to update before the OTA hits their device, Google has not yet posted these updates for download directly from the Nexus Factory Images page.
Thankfully, the community has pulled through and captured the incremental OTA update links housed on Google’s own servers. You will of course want to be on stock recovery and stock firmware to apply these update. Further, since these are incremental OTAs, you need to be on the correct stock firmware in order for the flash to work. For the Nexus 7 (2012) and Nexus 10, this means that you have to be on build JWR66Y. And for the Nexus 7 (2013), you must be on JSS15R. Thankfully, these builds are all available as complete packages in the Nexus Factory Images page.
If you can’t wait to update your device to official KitKat and are looking for the captured OTAs, head to the appropriate link below!
November 13, 2013 By: eagleeyetom
Google has announced on the official Android Google+ that starting today, the Nexus 7 (both 2012 and 2013) and Nexus 10 will receive an over-the-air update to Android 4.4 KitKat. According to Google, the Nexus 4 and versions of the Nexus 7 with mobile data will be getting the update soon as well.
KitKat was released nearly two weeks ago, and it brought many improvements in security and user-facing features. Google promised that older Nexus devices, unfortunately not including the Galaxy Nexus, would receive an update to Android 4.4 within few weeks. Today’s announcement now reaffirms this. It didn’t take long for developers here on XDA to bake some unofficial ports for these devices. But unfortunately, not everything was perfect in these early builds. Now, however, the unofficial builds will also benefit, as Google will also release the proprietary binaries required to build a fully working system.
We all hoped that it wouldn’t take long for Google to push out the OTA updates for all supported devices. And soon, current Nexus owners will be able to enjoy official KitKat. In the meantime, head over to your device-specific forum and keep an eye out for system dumps and OTAs available to flash.
November 10, 2013 By: Will Verduzco
A little under a year ago, we talked about a rather unique multiboot solution available for the Google Nexus 7 (2012). The tool, which was developed by XDA Recognized Developer Tasssadar, differed from most other multiboot solutions available on other devices because it streamlined the process and requires no modification of your device’s bootloader or existing /system partition. It did, however, require modification to the /data partition, but things were still more civilized than most other multiboot solutions due to the integrated installer app.
Now, Tasssadar’s MultiROM solution has been extended to also support the Nexus 4 and Nexus 7 (2013). Just as before, the main staple of MultiROM is its ability to allow you to boot into any number of Android ROMs. In addition to adding support for the two new devices, however, MultiROM has undergone a whole host of improvements over the last year.
For starters, MultiROM now allows you to restore from an existing Nandroid backup for use as a secondary ROM. This is an extremely practical feature because it allows you to make a backup of your existing ROM and transfer it to the secondary installation so that you can objectively compare results when flashing modifications.
Tasssadar has also removed one of the key limitations from last year’s release. Before, all ROMs had to be installed on internal memory. This presented somewhat of a challenge to many since modern Nexus devices lack external SD card expansion slots. Now, MultiROM allows you to use a USB-OTG cable and connected USB storage to house the ROMs off of device storage.
To get started, visit the appropriate thread below:
[Thanks to Tasssadar and Nikwen for the heads up!]
November 1, 2013 By: Will Verduzco
Ever since Google released the source code for Android 4.4 KitKat, we knew it wouldn’t be long before proper, source-built ROMs were made available for certain devices. And naturally, we all expected these initial builds to appear first on some of the current Nexus fleet. That is indeed the case, as there are now builds for the Google Nexus 4, Google Nexus 7 (2012), and the Google Nexus 7 (2013).
These builds all come courtesy of the Paranoid Android team, and are labeled “4.4r1 by AOSPA.” The Nexus 4 build comes courtesy of XDA Recognized Developer franciscofranco, the Nexus 7 (2012) build comes courtesy of XDA Senior Member EvanA, and the Nexus 7 (2013) comes courtesy of XDA Recognized Developer aaronpoweruser.
At this point, it is unclear what exactly works and what doesn’t work. However, we do know that Paranoid Android’s signature features have not yet been merged. Rather, this is just based on the source code that was released yesterday. And since this is such an early build and source was only released a day ago, we wouldn’t use these as daily drivers just yet. That said, it’s great to see such early source-built progress being made. Kudos to the Paranoid Android team. We can’t wait to see the ROM’s key features merged!
To get started, head over to the appropriate link below!
[Many thanks to EvanA and aaronpoweruser for the Flo link!]
November 1, 2013 By: Will Verduzco
What an exciting day we had yesterday. As was widely speculated, the Google Nexus 5 was finally released, which means that you can finally put that F5 key to rest. However, the new device wasn’t the only important announcement yesterday. We were also given a nice dose of the next version of Android, version 4.4 KitKat. Now the question in everybody‘s mind undoubtedly turns to when their device will get the update. Luckily, we now know the roadmap for certain key devices. READ ON »