Google is Starting Work on Android P (Android 9.0) in the AOSP Master Branch

It’s been barely 5 months since Google presented the main Android 8.0 Developer Preview and barely seven days since the most recent discharge, now known as Android Oreo, was authoritatively propelled. In any case, while just an infinitesimal division of general Android clients have their hands on the delicious Oreo refresh, we would expect that Google is as of now beginning work on the following real form of Android. Also, we would be appropriate, as today around evening time another tag has opened up in the Android Open Source Project called “ace p” that demonstrates that submits made to the AOSP ace branch will appear in Android P (probably Android 9.0).

The three confers demonstrate that Google is currently trying Android P on the Google Pixel (sailfish) and Google Pixel XL (marlin). The first, titled “ace is presently P”, was quite recently converged to the ace branch this evening. In the progressions made to the version_defaults.mk record, we can see the new stage code name and form.

As should be obvious, the code name is Android P when contrasted with Android O for the past discharge. Besides, the stage variant is PPR1 contrasted with OPR1, which takes after Google’s new form number tradition.

The following confer, titled “ace is P just, evacuating old esteems”, changes the stage form in the Compatibility Test Suite from “8.0.0” to simply “P” (not marked Android 9.0 starting at yet, which mirrors how Google alluded to Android 8.0 only as Android O for a long while). This demonstrates additionally testing on submits made to the ace branch, all of which go under Android P, will be done to guarantee that they pass the refreshed CTS.

As should be obvious, the code name is Android P when contrasted with Android O for the past discharge. Besides, the stage variant is PPR1 contrasted with OPR1, which takes after Google’s new form number tradition.

The following confer, titled “ace is P just, evacuating old esteems”, changes the stage form in the Compatibility Test Suite from “8.0.0” to simply “P” (not marked Android 9.0 starting at yet, which mirrors how Google alluded to Android 8.0 only as Android O for a long while). This demonstrates additionally testing on submits made to the ace branch, all of which go under Android P, will be done to guarantee that they pass the refreshed CTS.

Obviously, that hypothesis could be off since we don’t approach Google’s inside gerrit. It’s conceivable that Google as of now has work finished on an Android 8.1 discharge which will be propelled with the Google Pixel 2 and Google Pixel 2 XL, similarly as Android Nougat MR1 (7.1) propelled with the original Google Pixel and Pixel XL. There is point of reference for avoiding a noteworthy refresh to an Android letter refresh, however, as Android Marshmallow never observed a 6.1 discharge. Then again, there were 3 support discharge branches in AOSP for Marshmallow, so that may not really be strong reason for this hypothesis.

It’s somewhat right on time now to state for beyond any doubt what will occur with Android P and whether it will dispatch as Android 9.0 without us consistently observing Android 8.1, yet unmistakably the confers we found today around evening time in AOSP demonstrate that Google likely has a rundown of components they are focusing for the following real arrival of Android. We trust that whatever those elements might be are ones that will thump us off our feet.