General September 20 2023 - Android 14 QPR1 Beta 1 U1B1.230908.003 - "Upside Down Cake" - Pixel 7 Pro [Cheetah]

[Lughnasadh]

Links are up now.

 

[roirraW "edor" ehT]

Edit: Was ninja'd.

Hey! Finally on the English page:

Beta 3:

Release notes | Android Developers

Release notes and known issues for the latest Android 14 builds.

developer.android.com

Factory images for Google Pixel | Android Developers

Instructions for downloading and installing preview system images for Pixel devices.

developer.android.com

OTA images for Google Pixel | Android Developers

Instructions for downloading and appying preview OTA images for Pixel devices.

developer.android.com

Get Android 14 | Android Developers

Get Android 14 on your eligible device.

developer.android.com

Android 14 Preview | Android Developers

How the Android 14 Preview works, the timeline, and what is included.

developer.android.com

 

[gpvecchi]

Live translate not working anymore

 

[Dr.Pepper]

Lock sreen editing (at least you can choose only)

Modem version g5300q-230519-230524-B-10194843,g5300q-230519-230524-B-10194843

Now version shows 14 not upsidedowncake

Can add shortcuts on lockscreen

 

[gpvecchi]

I flashed both slots and I almost bricked my device. Now I managed to resurrect it, but I get the device corrupted message.
Is there any way to remove it?
Thanks!

 

[roirraW "edor" ehT]

I flashed both slots and I almost bricked my device. Now I managed to resurrect it, but I get the device corrupted message.
Is there any way to remove it?
Thanks!

Factory Reset is a possibility.

Sometimes flashing the boot.img from an old firmware fixes the issue, then you can flash the new boot.img back.

 

[LLStarks]

Lock sreen editing (at least you can choose only)

Modem version g5300q-230519-230524-B-10194843,g5300q-230519-230524-B-10194843

Now version shows 14 not upsidedowncake

Can add shortcuts on lockscreen

It's still broken. n71 and n25 don't carry data. 3CC aggregation does not work.

Samsung is still changing a lot under the hood though.

 

[federicocip85]

I had a issue with wallpaper and style, solved with reinstalling system app. Everything is fine! I appreciate finally more customisation of lock screen! Will see in this days how battery and all will behave.

 

[gpvecchi]

Factory Reset is a possibility.

Sometimes flashing the boot.img from an old firmware fixes the issue, then you can flash the new boot.img back.

Thank you. The phone works normally, but I have that message at the beginning.

 

[Puksom]

All works fine! But from time to time i get the error about Android System Intelligence

 

[gururoop]

I flashed both slots and I almost bricked my device. Now I managed to resurrect it, but I get the device corrupted message.
Is there any way to remove it?
Thanks!

Can you please outline the steps how you almost bricked your device? And also, how you resurrected it. Please share for everyone's knowledge. I always used to flash full factory images after removing -w flag but have been scared to do so since loosing all my data because of platform-tools problem.

 

[gpvecchi]

I flashed factory image removing -w on slot A. The phone booted fine. Then I flashed the OTA on slot B. The phone didn't boot anymore.
Luckily I managed to boot to bootloader, so I flashed the factory image without the -W on slot A.
I got the corruption message, but confirming with power button made the procedure go on in fastbootd.
The phone now works, but I have the corruption message at boot.

 

[roirraW "edor" ehT]

I flashed factory image removing -w on slot A. The phone booted fine. Then I flashed the OTA on slot B. The phone didn't boot anymore.
Luckily I managed to boot to bootloader, so I flashed the factory image without the -W on slot A.
I got the corruption message, but confirming with power button made the procedure go on in fastbootd.
The phone now works, but I have the corruption message at boot.

If you don't try either of the two things I suggested, sometimes or even frequently, flashing the next firmware that comes out (Beta 3.1? Beta 4?) will fix it, too. Still fine to leave out the -w when doing so.

The flashing the old boot.img temporarily (and trying to boot with it), then re-flashing the new boot.img, is the easiest and most immediate way of trying to fix it, or you can wait until the next firmware.

 

[rosms]

Hello, are the banking apps working in this version? Any major bugs or is it usable as daily driver? Thanks in advance

 

[Gordietm]

Hello, are the banking apps working in this version? Any major bugs or is it usable as daily driver? Thanks in advance

No major bugs for me. My banking apps work. It's a lot more stable than the previous betas. I'll probably stay on A14 from now on.

 

[gpvecchi]

If you don't try either of the two things I suggested, sometimes or even frequently, flashing the next firmware that comes out (Beta 3.1? Beta 4?) will fix it, too. Still fine to leave out the -w when doing so.

The flashing the old boot.img temporarily (and trying to boot with it), then re-flashing the new boot.img, is the easiest and most immediate way of trying to fix it, or you can wait until the next firmware.

Thank you, I now have time to make tests. Flashing old boot.img, try to boot, then flash the new boot. img fixed the issue.
Do you think I have to do it for inactive slot, too?

 

[p51d007]

Read on another site the "auto pin confirmation" is suppose to work in this build, but has to be turned on via ADB. Anyone know if there is a way around that with a simple toggle?
Checked in developer options, didn't see anything.

 

[roirraW "edor" ehT]

Thank you, I now have time to make tests. Flashing old boot.img, try to boot, then flash the new boot. img fixed the issue.
Do you think I have to do it for inactive slot, too?

Short version: I wouldn't mess with it if it's working as it is right now.

If you used the factory image to flash both slots, only the most recently flashed slot will work, anyway - as @Lughnasadh, @badabing2003, and possibly others have educated me about.

As both @Lughnasadh and @badabing2003 have tested, this is not the case if using OTAs instead of factory image. If you use OTAs, either slot is bootable - keeping in mind that both slots would be using the exact same system data, and user apps and data, so it would be a bad idea to have different ROMs/firmware in each slot, as something isn't going to mesh correctly.

 

[gpvecchi]

According to this behaviour, I suppose that flashing both slots with OTA would be advisable...
In effects, that's what I always did, except this time, as OTA was still unavailable.

 

[TotallyAnxious]

It's still broken. n71 and n25 don't carry data. 3CC aggregation does not work.

Samsung is still changing a lot under the hood though.

Can you tell if there are changes for low signal situations? Having major issues with that on stable, Google sending replacement.

Only asking because you seem most knowledgeable on this subject.