Google Launches Android 11 Developer Preview 1

An anonymous reader writes: Google today launched the first Android 11 developer preview, available for download now at developer.android.com. The preview includes a preview SDK for developers with system images for the Pixel 2, Pixel 2 XL, Pixel 3, Pixel 3 XL, Pixel 3a, Pixel 3a XL, Pixel 4, Pixel 4 XL, and the official Android Emulator. While it's the fifth year running that Google has released the first developer preview of the next Android version in Q1, this is the earliest developer preview yet. Android N (later named Android Nougat), Android O (Android Oreo), Android P (Android Pie), and Android Q (Android 10) were all first shown off in the month of March. Last year, Google used the Android Beta Program, which lets you get early Android builds via over-the-air updates on select devices. This year, however, Google is not making the first preview available as a beta (you'll need to manually flash your device). In other words, Android 11 is not ready for early adopters to try, just developers.

Not 20?

[SAU!]

Wait, what? They didn't jump straight to 20?

Re:

[swillden]

Wait, what? They didn't jump straight to 20?

I think they should. I think they should change the Pixel numbers to match release year, too.

Re:

[maybe111]

they will skip 13 cause unlucky

Re:

[arglebargle_xiv]

And if you want it on a non-Google phone, just throw away your existing $1,000 phone, buy a new $1,000 phone, and hope it has 11 on it. If not, throw it away and buy a new $1,000 phone. Repeat as required.

We don't need new versions of Android with the bling moved left 3mm and a different shade of pastel, we need some Google-enforced mechanism to ensure that the majority of the phones out there aren't running long-obsolete vuln-riddled versions of Android because the vendors never update.

Re:

[swillden]

we need some Google-enforced mechanism to ensure that the majority of the phones out there aren't running long-obsolete vuln-riddled versions of Android because the vendors never update.

If Google had a mechanism to do that, we would have done it.

That said, Android 11 has some nice stuff in it. One of the nice things from a security point of view is increasing use of "mainline modules" -- core system components that are updated directly by Google, bypassing the vendors. This appears to be a mechanism that will work to get updates out, but it's going to take a few system releases to transition all of the important bits. It's worth noting that the update situation is already improving aft

Re:

[B2382F29]

One of the nice things from a security point of view is increasing use of "mainline modules" -- core system components that are updated directly by Google, bypassing the vendors.

This has the obvious downside of Google slowly replacing the open source parts of Android with its proprietary closed-source binaries in the name of "security"

That has been an increasing problem during the last few years, see this article from 2018:

https://arstechnica.com/gadgets/2018/07/googles-iron-grip-on-android-controlling-open-source-by-any-means-necessary/ [arstechnica.com]

Re:

[swillden]

One of the nice things from a security point of view is increasing use of "mainline modules" -- core system components that are updated directly by Google, bypassing the vendors.

This has the obvious downside of Google slowly replacing the open source parts of Android with its proprietary closed-source binaries in the name of "security"

No. Mainline modules are all in AOSP. Yes, for a few years Google did move some stuff out of AOSP and into Play services for security reasons but that was never a very good solution; it was just the solution that was available. Mainline modules are an attempt to fix the problems of that approach, not continue them.

Re:

[Voyager529]

we need some Google-enforced mechanism to ensure that the majority of the phones out there aren't running long-obsolete vuln-riddled versions of Android because the vendors never update.

No, we don't need that, either. I mean, maybe as a last step, but there are several others that I submit are bigger issues...

1.) The whole OS needs to be better modularized. Say what you will about how terrible Windows is, but it's possible to install Windows 10 build 1909 on decade-old workstations. Windows patches don't usually wreak havoc with vendor-specific extensions or drivers. Let Samsung have their touchwiz overlay, or LG have their own launcher, or give the Pixel some exclusive eye candy, but deco

Re:

[lexman098]

Didn't read TFA I see. Google agrees. Search for "project mainline".

Re:

[Canberra1]

I would mod up, but also say to everyone, look up the official definition of an operating system. Not some manufacturers moving target perversion of true OS definitions - not press releases crap peddled to pretend IT tech writers. Understand the layers - the OS coordinates the drivers to where the hardware works up to the command prompt. Look at the TRS-80 and the Apple2 or even DOS. The OS is teeny. Everything else bolted on is eye candy, bling, vendor applications, and forced vendor bloatware, and in the

So what are losing this time?

[Hydrian]

With every new version, Google takes away app developer permissions possibilities thus limiting power users. The more android progresses, the lest useful and less customizable it has become.