The physical Menu button is an interesting holdout from an earlier age of Android. While Google's devices and those manufacturers that roughly follow Google's guidelines (like Motorola and LG) don't use it, Samsung and a few others do, leaving app developers in a tight spot when it comes to implementing an overflow button. Today a Reddit user found this change to the Action Bar Policy file for KitKat in Google's Git repository.
Android fans in India were happy to be included in KitKat's international Android 4.4 promotion and have the chance to get their hands on the 2013 Nexus 7. However, the prizes being sent out are not exactly as advertised. Instead of receiving the 2013 Nexus 7, winners in India are getting the old 2012 model. A multinational corporation not living up to its end of the deal? Surely you jest.
Winners of the Nexus 7 tablets in every other country were given the new Nexus 7, and those prizes mostly shipped out weeks ago.
With a new Android release comes another one of Funky Android's crazy-detailed AOSP developer changelogs, this time detailing every commit made between Android 4.4 (build KRT16M) and Android 4.4.1 (build KOT49E).
As usual, it's really long, and for the most part full of fairly cryptic comments you may not understand unless you have a pretty deep familiarity with the Android OS on a technical level. That said, there are always some interesting, readable tidbits people manage to pull from these logs, so if you can make the time, it may be worth perusing through for some unadvertised goodies packed in Android 4.4.1.
Just yesterday the Nexus 4, 5, 7, and 10 all received their first nightlies for CyanogenMod 11. Now KitKat-flavored builds are rolling out for a slew of additional devices. The team has shared a list of devices with incoming nightlies, and while it isn't yet an exhaustive list, it does include multiple variants of the HTC One (m7att, m7spr, m7tmo, m7ul) and LG G2 (d800, d801, d802), as well as the international Galaxy SIII (i9300).
Android 4.4.1 continues to wind its way through the air, hitting devices a few at a time. Being a smart young individual, you know you don't need to wait for the OTA to reach your device in the old fashioned way – you can skip the line. The OTA update file for the WiFi version of the new Nexus 7 (that's Flo) has been spotted and we've got it right here for you.
With Android 4.4.1's release earlier today, many of you have been asking about and expecting the corresponding factory images, especially for devices without OTAs at this point: the 2012 Nexus 7s, the Wi-Fi 2013 Nexus 7, and the Nexus 10. Factory images can help recover soft-bricked Nexus devices, update the OS or its parts without losing data in case an OTA doesn't want to apply, or go back to stock after trying a custom ROM.
Usually the boys in Cyan take a pretty good while to get nightly custom ROM builds of a new version of Android out, but for KitKat 4.4, they've outdone themselves. Tonight the first builds for CyanogenMod 11 (Android 4.4) were posted to Get.CM for the Nexus 4, Nexus 5, both 2012 and 2013 models of the Nexus 7, and the Nexus 10. You can download them right now.
But wait a minute - these are decidedly not nightly builds, as would usually be the case.
While we're not entirely sure what changes Android 4.4.1 will be bringing across the host of Nexus devices it's currently rolling out to (aside from an improved camera on the Nexus 5), we do know that the latest release of Google's mobile OS is hitting the repositories of the Android Open Source Project as we speak.
Just head to the kitkat-mr1-release branch and you'll see the build number KOT49E. Update: The relevant tag for the update is android-4.4.1_r1.
Android 4.4.1 is rolling out for a number of devices today, including the Nexus 5, but as with most Nexus device updates, it's happening in stages. As such, it could be a few days before you get the OTA if you choose to wait, and we all know what that's like: annoying. So, here's the Android 4.4.1 OTA for the Nexus 4.
What's new in Android 4.4.1? We know the Nexus 5's camera has been improved, but not much else, so we're working on figuring that out at the moment - expect a post in the coming days.