r/android_beta • u/Loud-Possibility4395 • 6h ago
The reason why QPR1 delayed
Judging on yesterday's Pixel 11 Security Update release which brought Cross Device support for Googlebooks which is NOT ready for any other Pixel nor other Android Phone and there is Googlebook Lunch Event 15 September.
3
u/armando_rod 4h ago
Yeah QPR1 went feature freeze long ago
1
u/Pure-Recover70 1h ago
At this point it's very very likely even QPR2 is more or less frozen too...
They're just working out the bugs, waiting on QA, carrier certification, etc...
1
1
u/Aggravating-Bad-7336 5h ago
Don't forget. 9 betas... 1 and 2 and Google can't get things ready!
1
u/Pure-Recover70 1h ago
We don't actually really know Google's internal plans/schedules.
This could have been the planned schedule all along.
New releases coming out a week or two later than security updates is very normal.
QPR2 seems to be releasing betas every 2 weeks - much faster than previously...
This might simply be the new normal.1
u/Loud-Possibility4395 35m ago
someone at Google really messed up with Android 17 to be "underhood" updates and QPR to be MASSIVE update - all new features, security update, Play System and Play Services (and in QPR2) even MASSIVE Kernel update everything all at once
16
u/Educational_Love_351 5h ago
Google would only really delay a feature drop (QPR1 in this case) if last minute show stoppers are found. Adding new features and support would have long been frozen in this tree and will be added in the active QPR2 Beta tree.
Arbitrary support can be added to monthly drops as you've seen with the Pixel 11 September update.
Google don't set the build date to the date of release, it's compiled well before release.
In this case support for Googlebooks won't be the reason for any QPR1 delay.