Android 15 qpr1 beta 3.1 builds have a timestamp newer than the December OTA for pixels preventing install [383178045]

Assigned

Bug

Platform

Status Update

No update yet.

Description

ne...@gmail.com

created issue #1

Dec 9, 2024 10:52PM

What

User experience

What type of Android issue is this?
Other issue

What steps would let us observe this issue?

The timestamp of the final December update is older than the 3.1 beta builds for all pixel devices. If a user attempts ADB sideload command they will be unable to install the final December OTA over the 3.1 update.

What did you expect to happen?
Updates pushed out in sequence are allways newer than newer the previously installed build.

What actually happened?
Google engineer finalized the December OTA (android 15 feature drop 1) with a timestamp older than 3.1 beta preventing install

What was the effect of this issue on your device usage, such as lost time or work?
High

Additional comments
Please fix before Christmas 🙏. Much thanks.

When

Time and frequency

Time when bug report was triggered: Dec 9, 2024 9:39 AM GMT-06:00

How often has this happened?
Every time

Where

Component

Suggested component: <not visible> (1630575)

Build and device data

- Build Number: google/komodo_beta/komodo:15/AP41.240925.012/12657560:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)

Debugging information
Google Play services
com.google.android.gms
Version 244735036 (24.47.35 (260408-702774332))
System App (Updated)

Android System WebView
com.google.android.webview
Version 677804133 (131.0.6778.41)
System App (Updated)

Network operator: Visible
SIM operator: Visible

Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)
To learn more about our feedback process, please visit https://developer.android.com/preview/feedback#feedback-app.

Comments

ne...@gmail.com <ne...@gmail.com> #2Dec 9, 2024 10:53PM

Information redacted by Android Beta Feedback.

bugreport-komodo_beta-AP41.240925.012-2024-12-09-09-39-32_GMT-06:00.zip

Restricted+

22 MB

Download

bugreport-komodo_beta-AP41.240925.012-2024-12-09-09-39-32_GMT-06:00_REDACTED.zip

Restricted

18 MB

Download

an...@google.com <an...@google.com> Dec 10, 2024 01:33AM

Assigned to an...@google.com.

wf...@gmail.com <wf...@gmail.com> #3Dec 10, 2024 07:13AM

Comment has been deleted.

Message last modified on Dec 10, 2024 02:10PM

dx...@gmail.com <dx...@gmail.com> #4Dec 10, 2024 07:18AM

Upgrade was never offered. I was offered directly Android 16. I can't
install Android 16 as I want to leave beta.

<buganizer-system@google.com> schrieb am Do., 27. Feb. 2025, 08:55:

- Show quoted text -

an...@google.com <an...@google.com> #5Dec 10, 2024 10:12AM

Thank you for reporting this issue. We have shared this with our product and engineering team and will update this issue with more information as it becomes available.

va...@gmail.com <va...@gmail.com> #6Dec 10, 2024 04:14PM

Thanks for reporting this issue.

We are handling "No more paying via Wallet because the system is not up to date" wallet issue here.
Please file a separate ticket for "Upgrade was never offered to install android 16" with details.

kl...@gmail.com <kl...@gmail.com> #7Dec 11, 2024 08:55PM

Comment has been deleted.

Message last modified on Dec 11, 2024 09:00PM

kl...@gmail.com <kl...@gmail.com> #8Dec 11, 2024 09:18PM

And hurry the hell up! People who installed qpr1 beta 3.1 are waiting. And they are well pissed off. You promissed NO DATA WIPE beta exit for Android 15 qpr1 testers in December! Beta 3.1 is still qpr1! So do what you promissed you'd do!

dx...@gmail.com <dx...@gmail.com> #9Dec 18, 2024 09:43AM

Guess y'all just postpone this issue til January security patch and call it a day...

rw...@gmail.com <rw...@gmail.com> #10Dec 27, 2024 05:55PM

This situation is pathetic. Google you should be ashamed of yourselves, you call yourself professionals...

fa...@hotmail.com <fa...@hotmail.com> #11Jan 7, 2025 09:35PM

And this is still a thing, sadly...

dx...@gmail.com <dx...@gmail.com> #12Jan 8, 2025 04:29AM

And this is still a thing, sadly...

Well, at least new OTA image for sideload was released. Who would've thought...

dx...@gmail.com <dx...@gmail.com> #13Jan 8, 2025 05:44PM

And it's not even sideloading for Pixel 7. Just error 7 kInstallDeviceOpenError and that's it. What a mess.

li...@gmail.com <li...@gmail.com> #14Jan 8, 2025 09:45PM

And it's not even sideloading for Pixel 7. Just error 7 kInstallDeviceOpenError and that's it. What a mess.

This sounds like a device problem, not an OTA image problem.

al...@gmail.com <al...@gmail.com> #15Jan 8, 2025 11:56PM

Confirming I am still getting the same error. "kInstallDeviceOpenError" trying to sideload the Jan 5 OTAs over my QPR1 Beta 3.1 Pixel 8 Pro. Details :

Pixel 8 Pro / Android 15 QPR1 Beta 3.1 / AP41.240925.012

Downloaded 15.0.0 (AP4A.250105.002, Jan 2025) (a9df99e894b6cc17256a35a5c6dfb8a4c31978dda26c4d4b74fedfa46b5a6e92) got the following error :

Error applying update: 7 (ErrorCode::kInstallDeviceOpenError)
ERROR: recovery: Error in /sideload/package.zip

Also tried 15.0.0 (AP4A.250105.002.B1, Jan 2025, Telstra) (971dad3fe17b2289b74df0e383920aaf1cfdb0607f85edda927755dfc523c5ad) and got the exact same error.

Tried with and without Dev mode active, With and without unlock bootloader option turned on.

Not sure what else to do at this point.

li...@gmail.com <li...@gmail.com> #16Jan 9, 2025 01:10AM

☝️ Someone from Google should look at this and it's possibly a different problem that needs logs.

al...@gmail.com <al...@gmail.com> #17Jan 9, 2025 01:29AM

Agree. at this point it's likely something else is slightly off

ht...@gmail.com <ht...@gmail.com> #18Jan 13, 2025 08:44AM

??
Will this be fixed by the Assignee?
It's already been over a month since first reported.
And January security patch was already released.
All QPR1 beta3.1 users including me really are waiting for an update release with no data wipe to QPR1 stable, which is promised, I believe.
Anyway, need info, as the Assignee said in #5, please.

Message last modified on Jan 16, 2025 01:07PM

su...@gmail.com <su...@gmail.com> #19Jan 14, 2025 08:13AM

What

More information

Still didn't get January Update, still on November Security Patch. I can't leave QPR1 without wipe.

Where

Build and device data

- Build Number: google/caiman_beta/caiman:15/AP41.240925.012/12657560:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)

Debugging information
Google Play-Dienste
com.google.android.gms
Version 244933036 (24.49.33 (260408-705592033))
System App (Updated)

Android System WebView
com.google.android.webview
Version 677820033 (131.0.6778.200)
System App (Updated)

Network operator:
SIM operator: congstar

bugreport-caiman_beta-AP41.240925.012-2025-01-12-20-33-40_GMT+01:00.zip

Restricted+

22 MB

Download

su...@gmail.com <su...@gmail.com> #20Jan 14, 2025 08:13AM

Information redacted by Android Beta Feedback.

bugreport-caiman_beta-AP41.240925.012-2025-01-12-20-33-40_GMT+01:00_REDACTED.zip

Restricted

18 MB

Download

an...@gmail.com <an...@gmail.com> #21Jan 14, 2025 05:05PM

This is getting endlessly dragged out with no updates. Someone needs to explicitly say they will not fix this so we know what to expect

ma...@gmail.com <ma...@gmail.com> #22Jan 14, 2025 08:00PM

Can someone from Android team post if they need any additional info or they are aware of what is causing the issue? In my case it is Pixel 9 Pro Fold and nothing works including sideloading. Device is completely stock, nothing has been modified.

al...@gmail.com <al...@gmail.com> #23Jan 14, 2025 09:07PM

As posted above, I have the same issue too. I will bite the bullet and exit with data wipe if there's no other option, but I'd prefer not to. If someone could just advise, at least I'd be making an informed decision.

an...@gmail.com <an...@gmail.com> #24Jan 18, 2025 02:52AM

Thanks for nothing Google, had to opt back into Beta 2 since side loading doesn't work. The delays have caused my device integrity to drop to basic because security patch is outdated by 2 months and my work profile stopped working because of this. Should be ashamed of yourselves

ap...@gmail.com <ap...@gmail.com> #25Feb 6, 2025 06:09AM

The timestamp of the final December update is older than the 3.1 beta builds for all pixel devices. If a user attempts ADB sideload command they will be unable to install the final December OTA over the 3.1 update.

ar...@gmail.com <ar...@gmail.com> #26Feb 6, 2025 04:52PM

So with this February security patch, I guess now it's final that I have to exit with data wipe. Thank all the useless google developers.🫰

Issue 383178045

Description

What

User experience

When

Time and frequency

Where

Component

Build and device data

Issue summary

Comments

ne...@gmail.com <ne...@gmail.com> #2Dec 9, 2024 10:53PM

an...@google.com <an...@google.com> Dec 10, 2024 01:33AM

wf...@gmail.com <wf...@gmail.com> #3Dec 10, 2024 07:13AM

dx...@gmail.com <dx...@gmail.com> #4Dec 10, 2024 07:18AM

an...@google.com <an...@google.com> #5Dec 10, 2024 10:12AM

va...@gmail.com <va...@gmail.com> #6Dec 10, 2024 04:14PM

kl...@gmail.com <kl...@gmail.com> #7Dec 11, 2024 08:55PM

kl...@gmail.com <kl...@gmail.com> #8Dec 11, 2024 09:18PM

dx...@gmail.com <dx...@gmail.com> #9Dec 18, 2024 09:43AM

rw...@gmail.com <rw...@gmail.com> #10Dec 27, 2024 05:55PM

fa...@hotmail.com <fa...@hotmail.com> #11Jan 7, 2025 09:35PM

dx...@gmail.com <dx...@gmail.com> #12Jan 8, 2025 04:29AM

dx...@gmail.com <dx...@gmail.com> #13Jan 8, 2025 05:44PM

li...@gmail.com <li...@gmail.com> #14Jan 8, 2025 09:45PM

al...@gmail.com <al...@gmail.com> #15Jan 8, 2025 11:56PM

li...@gmail.com <li...@gmail.com> #16Jan 9, 2025 01:10AM

al...@gmail.com <al...@gmail.com> #17Jan 9, 2025 01:29AM

ht...@gmail.com <ht...@gmail.com> #18Jan 13, 2025 08:44AM

su...@gmail.com <su...@gmail.com> #19Jan 14, 2025 08:13AM

What

More information

Where

Build and device data

su...@gmail.com <su...@gmail.com> #20Jan 14, 2025 08:13AM

an...@gmail.com <an...@gmail.com> #21Jan 14, 2025 05:05PM

ma...@gmail.com <ma...@gmail.com> #22Jan 14, 2025 08:00PM

al...@gmail.com <al...@gmail.com> #23Jan 14, 2025 09:07PM

an...@gmail.com <an...@gmail.com> #24Jan 18, 2025 02:52AM

ap...@gmail.com <ap...@gmail.com> #25Feb 6, 2025 06:09AM

ar...@gmail.com <ar...@gmail.com> #26Feb 6, 2025 04:52PM

Add comment

Issue metadata