Android Police

Articles Tagged:

AOSP

89 articles
...

Google Finally Completely Redesigns The AOSP Site To Look About A Googol Times Better

While the Google Developers site received its massive redesign quite a while ago, its sibling AOSP one at source.android.com has remained an ugly duckling. Until about an hour ago.

The difference is huge - it's like it went from Cupcake days to Jelly Bean in the blink of an eye. It would be nice if you could update Android the same way, wouldn't it?

Here are some images of the old (visible at archive.org) and new sites side-by-side (can you guess which one is which?):

image image

image image

Source: AOSP

Read More
...

Paranoid Android Says Hello To Halo – 'This Is How You Do Multi Windowing On Android'

After some teasing, Paranoid Android has unveiled (in a lovely promo image) their plan for multi-window functionality on Android, which they promise to "get right," – Halo.

The premise is simple, yet extremely ambitious in scope – allow apps to give you notifications right on top of your screen, which allow you to pop into that app without leaving the one you're in (no matter what it is), take care of business, and resume your experience uninterrupted.

Read More
...

Sony Releases Pure AOSP For The Xperia Z To Its GitHub, Encourages Developers To Hack Away

Back in August of '12, Sony teamed up with Google to make the Xperia S an officially supported AOSP device. The project initially got off to a decent start, but after an issue with some proprietary software binaries that couldn't be released by either Sony or Google, the project was canned on the official side and moved to Sony's GitHub, where it can still be found today.

Now, the company is doing something similar with the Xperia Z, minus Google's interaction from the get-go.

Read More
...

Google Pushes New Android 4.2.2 Code To AOSP (JDQ39E, 4.2.2_r1.2) - Here Is The Developer Changelog

Earlier today, Google started pushing some new open source code to AOSP (Android Open Source Project) marked with 2 new tags: android-4.2.2_r1.1 and android-4.2.2_r1.2. The build number corresponding to the 4.2.2_r1.2 release is JDQ39E.

image

The dates you see here are commit dates, not dates the commits were made public (which is today, April 17th 2013)

What's New?

After weeding out the changes from the commit logs, it looks like all of them are, as expected, very minor.

Read More
...

[Achievement Unlocked] Google: Nexus 4 And Nexus 7 Are The First Ever AOSP Devices That Have 100% Of The Proprietary Binaries Available

As an addendum to the announcement of Google completing AOSP rollout for Android 4.2.2, I wanted to highlight a big milestone for the Nexus program - something that has never been the case before today.

After asking JBQ (not to be confused with JDQ39) a follow-up question, I was able to get some clarity on his earlier post and confirm that as of today, with the release of Android 4.2.2 binaries, we have for the first time ever Nexus devices that have 100% of proprietary binaries available.

Read More
...

Android 4.2.2 (JDQ39) Source Has Started Pushing To AOSP [Updated]

It's begun - the newest version of Android, 4.2.2, is being pushed to AOSP right now. We saw the accompanying Nexus OTA rollout start last night, with update files slowly springing up thereafter. Right now, 4.2.2 builds can be downloaded for the Takju Galaxy Nexus, Nexus 7 (Wi-Fi), and Nexus 10.

The build number is JDQ39 and the tag in AOSP is android-4.2.2_r1. Here are a few of the many directories that have been updated:

While the push has just started this morning, source will likely continue to show up throughout the day, and we'll update this page as that happens.

Read More
...

Google Pushes New Android 4.2.1 Code To AOSP (JOP40G, 4.2.1_r1.2) - Here Is The Developer Changelog

Earlier this week, we got wind of a new OTA build JOP40G possibly hitting the Nexus 4 soon. I thought this update would finally be the elusive Android 4.2.2 that we've been hearing about, but it looks like that's not the case.

Yesterday, Google pushed some new open source code to AOSP (Android Open Source Project) marked with 2 new tags: android-4.2.1_r1.1 and android-4.2.1_r1.2. The build number corresponding to the 4.2.1_r1.2 release is - you guessed it - JOP40G (with mentions of JOP40F and JOP40E along the way too) - the same one we thought would be 4.2.2.

Read More
...

Android 4.2.1 (JOP40D) Live In AOSP [Updated]

Earlier today, both the Nexus 4 and the Nexus 10 started receiving small ~1MB OTAs to Android 4.2.1 with fixes to the missing month of December in the People app, among other things. The corresponding open source files are being pushed by Google to the Android Open Source Project (AOSP) as we speak, Android release engineer Jean-Baptiste Queru just announced in the Android Building group.

The build number is JOP40D and the tag is android-4.2.1_r1.

Read More
...

Breaking: Android 4.2 Released To AOSP

The new Nexus devices just went live, and, as promised, Google has simultaneously started pushing the code for the latest iteration of our favorite mobile OS - Android 4.2 Jelly Bean - to the Android Open Source Project. Jean-Baptiste Queru, chief Android release engineer, announced the news via a post to the Android Building group.

Update 11:22am: Android 4.2 source just finished replicating to AOSP. "The platform source files for 4.2 have finished replicating, you can now sync." -JBQ

The build number is JOP40C, while the AOSP tags is android-4.2_r1.

Read More
...

There Is Hope For AOSP Support Of Sprint's Galaxy Nexus After All As Google Releases "Experimental" Binaries

The Galaxy Nexus variant on Sprint might actually have a chance of being officially supported by Google in AOSP after all, which would be a big step in the right direction for carrier-branded Nexus devices.

If you remember, neither Verizon's nor Sprint's Galaxy Nexus was supported by the Android Open Source Project at launch, with the Verizon's version joining the program over half a year after its release. Even though the Nexus S 4G is fully supported, Sprint's GNex variant remained absent from the Nexus Binaries page and was therefore completely unsupported by the Android team.

Read More
Quantcast