Conversation

This Tweet was deleted by the Tweet author. Learn more

Replying to

and

The security patch level still appears to be 2021-10-05. The month listed on the factory images page doesn't correspond to the patch level. It would be very strange if they somehow got half a year of firmware and driver security updates previously not developed / available.

Replying to

and

It seemed odd to me that the kernel hasn't been updated but the SPL has - makes sense that the patches aren't new. I was waiting for a dump of the firmware to finish before confirming.

Replying to

and

They build from exactly the same code they publish to AOSP so checking there is quite reliable unless they made a mistake and pushed the wrong code. We've seen them make mistakes with the kernel tags before which we've had to report to get fixed but never for the main AOSP tags.

Replying to

and

Stock OS is built from the same AOSP source tree with additional device repositories providing the full build targets without the aosp_ prefix where they replace various AOSP modules with Google modules, include Google Play + other Google apps/services and build more vendor code.

Replying to

and

Dropping in additional code works because AOSP doesn't define raven, oriole, barbet, redfin, bramble, etc. but rather only aosp_raven, aosp_oriole, aosp_barbet, aosp_redfin, aosp_bramble, etc. so they can drop in private device repositories which source the AOSP code as a base.

10:53 PM · Jun 27, 2022Twitter Web App

Replying to

and

AOSP code just has to support the extensibility and configuration for everything they need. I think they do essentially the same thing for desktop Chrome but Android Chromium is different and the internal Android Chromium code isn't always aligned with the publicly release code.

Replying to

and

The top 3 tweets have been removed who and what did they reference? (Specifically as Ive managed to piece the topic together from yours and Mishaals conversation.)

Show replies