POSTS TAGGED: Google Nexus 7 (2013)
Posted November 24, 2013 at 10:00 am by Tomek Kondrat
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.. . . READ ON »
Posted November 19, 2013 at 11:30 pm 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.
Posted November 14, 2013 at 04:30 pm 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) . . . READ ON »
Posted November 13, 2013 at 03:30 pm by TK
The Google Nexus 5 was just released a few weeks ago, packing Android 4.4 Kit Kat. The Nexus 7 (2013) was released not that long ago, and officially received KitKat earlier today. KitKat brings a nice new feature that allows you to record the screen on your device. Previously, this required (paid) third party apps. And even then, many faced compatibility issues with certain SoCs and ROMs.
The new feature has one major down side, though. You must be connected to your PC to start the process. However, XDA Senior Member prsterero brings us a user-friendly PC interface that simplifies the process and allows you to control the screen recording functionality from your Windows-based computer. It also allows you t. . . READ ON »
Posted November 13, 2013 at 09:00 am by Tomek Kondrat
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 un. . . READ ON »
Posted November 10, 2013 at 06:00 pm 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.
Android 4.4 Coming Soon to the Nexus 4, 7, 10, Moto X, New Droids, HTC One and SGS4 GPe; No 4.4 for the Galaxy Nexus
Posted November 1, 2013 at 02:00 am 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 »
Posted October 14, 2013 at 07:00 pm by TK
The Nexus 7 (2013) has been out since the late July, and many have enjoyed the device, which features numerous improvements over last year’s model. That said, many users have reported multi-touch issues right out of the box, and Google tried to address the issue back in August with the JSS15Q update. Sadly, this update didn’t fix the issue for all users, and it even brought on new touch issues for some who previously had none.
XDA Recognized Contributor sfhub came up with steps to fix the multi-touch issues for a purported 75% of the Nexus 7 (2013) users.
. . . READ ON »
Don’t you hate it when you have a workable system, then an update comes along which fixes something, let’s say GPS, but then you
Posted October 9, 2013 at 05:00 am by Will Verduzco
A few days ago, we mentioned that the JLS36I update to Android 4.3.1 had begun rolling out to LTE-enabled Nexus 7 (2013) tablets. However, at the time, we found it a bit curious that there was no associated restore image available on Google’s Nexus Factory Images website. Even though the incremental OTA links had been captured and the files themselves mirrored, it’s always nice to have a full restore image of the latest firmware just in case.
Now, Google has finally made the factory restore images available for download. We’re still unsure what (if any) user-visible changes have occurred since then. Some seem to think there may be something related to a kiosk mode, but we’re unable to . . . READ ON »