Has QPR1 been already pushed to AOSP or not?

person92

More than 1 week has passed. It was supposed to be done on 3rd. Today is 12th.
If it has not been done till now then what could be the reason behind this?

ElliesSurviving

it unfortunately hasnt yet, its been confirmed its coming "in the next few weeks" however

xxx

ElliesSurviving in the next few weeks" however

Google doin goole things...

wuseman

ElliesSurviving
Do we know why there's such an annoying delay?

ElliesSurviving

not at this moment in time

Miles

What is the big deal with this build?

wuseman

Miles
I'm dying to know the same.

Best case scenario, they found a critical bug that they need to fix.

Worst case scenario, this is part of their "slowly dismantling AOSP" plan. Maybe they are testing the waters to see how people would react to AOSP being 3 weeks behind Android. Then 5 weeks. Then 2 months. Then 6 months. Then it slowly just disappears.

Kaziq

Miles For me it's going to introduce resizable quick settings tiles. I can't stand this modern tendency of making everything so huge that only a few of them fit on the screen. Also hoping for being able to unlock without waking the screen first, but not sure if it's going to be in this release.

IcyScroll

wuseman how people would react to AOSP being 3 weeks behind

I'm afraid that currently the only operating system affected by this is... GrapheneOS.

Pixels were pretty much the only devices that received QPR updates in practice. Vast majority of OEMs didn't really care about those updates. They did the bare minimum, which is shipping backported patches instead of keeping their Android distributions up to date. Even Samsung is no exception to this.
Looking at recent Project's posts on X and Mastodon, this might be about to change.

Google recently made incredibly misguided changes to Android security updates. Android security patches are almost entirely quarterly instead of monthly to make it easier for OEMs. They're giving OEMs 3-4 months of early access which we know for a fact is being widely leaked including to attackers.

Source: https://grapheneos.social/@GrapheneOS/115164183840111564

This might be related to the delay.

GrapheneOS

IcyScroll The security update changes aren't directly related. The quarterly security bulletin is already out, but not the quarterly OS update. It's not blocked in any way by security updates. The backports were already released after the embargo ended.

IcyScroll

GrapheneOS Thank You for the clarification.
And the most reasonable OS. Seriously, I would hate my smartphone if it wasn't for your work ❤️

I was thinking it could be related in some different way, which only Google understands at the moment, given how they've left us in the dark.

de0u

IcyScroll I was thinking it could be related in some different way, which only Google understands at the moment, given how they've left us in the dark.

Maybe the AOSP release coordinator quit to go work for OpenAI...

Maybe the AOSP variant of A16 QPR1 triggered a bug in Cuttlefish, and since AOSP no longer builds on Pixels they are having trouble testing...

Maybe they went to get some gnarly thrash boots!

de0u

IcyScroll I was thinking it could be related in some different way, which only Google understands at the moment, given how they've left us in the dark.

Maybe they're too busy trying to get Daily Hub to work: One of Google’s new Pixel 10 AI features has already been removed.

Or maybe they went to get a Vespa scooter.

As long as they choose to not say what's happening, only speculation is possible.

mirimex

Quite annoying situation as the trade in promotion forced many to buy the new Pixel 10 before GrapheneOS support is possible, having now a brick in a drawer waiting. Such a breach of trust fom Google. As it is hard to just descibe the problems that might have been discovered, it is understanable if bugs appear and things take time but radio silence is the worst abuse of market postition.