General September 26 2023 - Google survey about Android 14 QPR1 Beta 1 U1B1.230908.003 - "Upside Down Cake" - Pixel 6 Pro [Raven]

[amritpal2489]

Is pixel 6 pro boot.img working fine for rooting or do we still need to use 7 pro's??
PS: Using Magisk Delta

 

[MartinN6]

Is pixel 6 pro boot.img working fine for rooting or do we still need to use 7 pro's??
PS: Using Magisk Delta

pixel 6 pro boot.img works pretty good for root with magisk canary

 

[roirraW "edor" ehT]

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

 

[acwcanada]

Update to A14 Beta 3 by flashing the factory image with platform-tools v33.0.3, patched boot.img with Magisk canary-26102, retained root and everything seems to be OK.

Edit: If you are users of "Classic Power Menu", it is crashed when starting. AOSPMods users would also find many features are now not working such as some status bar icons, lock screen features etc.

 

[acwcanada]

Just realized that the fingerprint sensor is disappeared on my Pixel 6 Pro after update to this A14 beta 3! Google the web and find out I am not the only person, please read this web page and think hard before you decide to update:

Android 14 Beta 3 breaks the fingerprint sensor entirely on some Pixel phones

Android 14's third beta release seems to cause some Pixel phones to lose their fingerprint sensor entirely, frustratingly.

9to5google.com

PS: Further searching and I am seeing a lot of people reporting this issue to Google's "Android Issue Tracker" although most of them are Pixel 6/6P/6a. So if you are using one of these, I would suggest you stay with Beta 2.1 and not update to this Beta 3 until Google fix the issue, hopefully they would release a Beta 3.1 soon to rectify the problem.

 

[D_JWhite]

Just realized that the fingerprint sensor is disappeared on my Pixel 6 Pro after update to this A14 beta 3! Google the web and find out I am not the only person, please read this web page and think hard before you decide to update:

Android 14 Beta 3 breaks the fingerprint sensor entirely on some Pixel phones

Android 14's third beta release seems to cause some Pixel phones to lose their fingerprint sensor entirely, frustratingly.

9to5google.com

PS: Further searching and I am seeing a lot of people reporting this issue to Google's "Android Issue Tracker" although most of them are Pixel 6/6P/6a. So if you are using one of these, I would suggest you stay with Beta 2.1 and not update to this Beta 3 until Google fix the issue, hopefully they would release a Beta 3.1 soon to rectify the problem.

My fingerprint reader has also gone since updating. I will say that updating was still preferable as I was experiencing excessive battery drain on beta 2.1, and this seems to have resolved.

 

[KwstPap]

on me fp working fine. come from a13 stable. aosp mods have bugs. universal face unlock module is broken now. lsposed we need to flash debug-canary version to work. battery seems good, smooth

 

[liber]

My fingerprint reader has also gone since updating. I will say that updating was still preferable as I was experiencing excessive battery drain on beta 2.1, and this seems to have resolved.

You can fix fingerprint using the pixel repair tool here
It works until reboot.

 

[roirraW "edor" ehT]

Android 14 Beta Software Survey

Hi Beta users, We'd like your feedback on the latest Beta version of Android 14 on your Pixel device. This *anonymous* survey should take you about 5-10 minutes to complete. Please only fill out this survey if your Pixel device is running Android 14 Beta build. You can verify this by going to...

docs.google.com

 

[roirraW "edor" ehT]

Android 14 Beta 3.1:

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

 

[Hell-Razor]

Anybody elses magisk crashing on them when trying to select the boot file to patch? Tried reinstalling, nada.

 

[roirraW "edor" ehT]

Anybody elses magisk crashing on them when trying to select the boot file to patch? Tried reinstalling, nada.

What version of Magisk are you using? And Stable, Beta, Canary, or ? As far as I remember observing, those who are on 14 Beta 3/Beta 3.1 have had no issue with Magisk v26.1 Stable (26100).

Also, is there any possibility that you previously hid Magisk, and that you've accidentally installed a new copy instead of unhide the original?

Hopefully, someone who is actually running the recent Betas will chime in, too, since I'm on 13 Stable for June.

 

[Hell-Razor]

What version of Magisk are you using? And Stable, Beta, Canary, or ? As far as I remember observing, those who are on 14 Beta 3/Beta 3.1 have had no issue with Magisk v26.1 Stable (26100).

Also, is there any possibility that you previously hid Magisk, and that you've accidentally installed a new copy instead of unhide the original?

Hopefully, someone who is actually running the recent Betas will chime in, too, since I'm on 13 Stable for June.

I'm on 26100 too.

No never did that hiding stuff.

 

[Lughnasadh]

PSA:

I was not able to patch the boot image with the newly released Canary 26103 on A14B3.1. Cpio changes were made to this release and I got a cpio error. A Github issue has been opened.

 

[acwcanada]

PSA:

I was not able to patch the boot image with the newly released Canary 26103 on A14B3.1. Cpio changes were made to this release and I got a cpio error. A Github issue has been opened.

I am also on A14B3.1 with Canary 26102 and just got updated to 26103, confirmed that patching the P6P boot image returned with the same error as yours.

 

[acwcanada]

PSA:

I was not able to patch the boot image with the newly released Canary 26103 on A14B3.1. Cpio changes were made to this release and I got a cpio error. A Github issue has been opened.

One more question: If I remember correctly, you did mention you have a P7P, did this also occur to it? I was thinking that if it is only with the P6 series then I wouldn't expect a update to rectify it too soon and I may have to consider going back to 26102. Thanks

 

[Lughnasadh]

One more question: If I remember correctly, you did mention you have a P7P, did this also occur to it? I was thinking that if it is only with the P6 series then I wouldn't expect a update to rectify it too soon and I may have to consider going back to 26102. Thanks

I'm running stable Magisk on my P7P so I don't know if it affects that device, or whether it affects stable A13 builds as well. Haven't really seen any other reports except for mine and yours.

 

[acwcanada]

I'm running stable Magisk on my P7P so I don't know if it affects that device, or whether it affects stable A13 builds as well. Haven't really seen any other reports except for mine and yours.

Noted, thanks to clarify. People just may not realize it as I wouldn't know either if I don't see your message and run a test patching to get the error.

 

[Lughnasadh]

PSA:

I was not able to patch the boot image with the newly released Canary 26103 on A14B3.1. Cpio changes were made to this release and I got a cpio error. A Github issue has been opened.

Looks like there is a Pull Request in progress to fix this issue.

 

[acwcanada]

Looks like there is a Pull Request in progress to fix this issue.

The opened issue in Github is disappeared, do you have any idea? Thanks