Don’t be surprised if an update to Android 5.0.1 shows up on your Nexus device in the near future. Google seems to have just pushed it to AOSP as Android 5.0.1_r1, which is also known as build LRX22C. (more…)
When Google released the Android L Developer Preview last week to the Nexus 5 and Nexus 7 (2013), I can imagine that a number of you were disappointed – namely those with a Nexus 4, Nexus 7 (2012) or Nexus 10. While Google still hasn’t released flashable images for any of those devices today, they have pushed Android L code for each to the Android Open Source Project (AOSP),
which means that your favorite developer will likely having something for you shortly in the form of a ROM. (more…)
It’s (almost) official: Google will eschew the Dalvik virtual machine for ART in the next release of Android. Commits in the AOSP master branch point to the removal of Dalvik entirely.
What does that mean, exactly? Dalvik was a useful stop-gap for Google in the early days of Android, when the team had to formulate a solution for running apps on a myriad of hardware. The virtual machine essentially acted as a translator of sorts, interpreting code to run on different architectures. (more…)
With Android 4.4 hitting AOSP yesterday, it was only a matter of time before the first set of stock ROMs started showing up for our favorite devices. An AOSP Nexus 4 ROM was the first to pop into our inboxes late last night, though we are sure there could be more at this point. For now though, we wanted to share this to get you into the comments and sharing others for other devices. (more…)
You read that title right – Android 4.4 is being pushed to AOSP right now. We typically see Google push source to AOSP shortly after an announcement, so this isn’t necessarily surprising. With that said, this is amazing news for our friends in the ROM game. How long before someone can get us a working build? (more…)
Google’s JBQ, the man behind the Android Open Source Project, recently took to Google+ to discuss why folks shouldn’t ever ask for ETAs on OTA updates. He explained it quite simply in that Google wants to make sure people don’t experience some catastrophe after the update, as something can always slip through the cracks during the internal test period. (more…)