yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] roirraW "edor" ehT:
Beta 1.1:

Android 14 | Android Developers

<!-- hide description -->

developer.android.com

Normal system images: Use https://flash.android.com/preview/udc-beta1.1

Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developer.android.com

Pixel 7 Pro	cheetah_beta-upb1.230309.017-factory-e8416573.zip	e841657355f0e64630921c85d3b66711c8203bf5174ec2deb41e1a7fef26b994

Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developer.android.com

Pixel 7 Pro	cheetah_beta-ota-upb1.230309.017-97a73547.zip	97a735476ff24cc4da0696b7e8bf4f66ac9833d1f2e5d0df957550c96ec6e792
[Google Pixel 7 Pro] LLStarks:
Hope they fixed the modem but it doesn't look like it.
[Google Pixel 7 Pro] morpheus620:
Flashing with fastboot is still not possible.

Flash Failed​

An error occurred while communicating with your device. You may have to select restart in the bootloader menu in order for it to be recognised again.

If you disconnected the device this is expected.

Try using a different USB cable and/or port.

Don't use a USB extension cable or hub (including through monitor hubs).

More debugging tips
[Google Pixel 7 Pro] LLStarks:
Guess we're not getting a polished build until I/O.
[Google Pixel 7 Pro] EtherealRemnant:
Got back my 5G indicator (previously I would have signal bars but no indicator). com.android.qns still crashes every boot.
[Google Pixel 7 Pro] GrndSers-Rcng:
My P7P just hard-bricked when I manually flashed 14 beta 1.1. It gave me a fastboot error while manually flashing, just like the first 14 beta did (ended up unrooting and doing the OTA for that first 14 beta update). But this time instead of booting back to the bootloader, I selected to boot to system from Fasbootd and all I got was nothing, just a dead phone... Taking it to UBREAKIFIX tomorrow through its warranty....
[Google Pixel 7 Pro] aer0zer0:
Where does yours die fastboot flashing? Mine has been stopping at product 7 of 12.
[Google Pixel 7 Pro] ajaxchen:
Seems Beta 1.1 did not fix fingerprint issue yet , com.android.qns pop-up few times as well .

BTW , I tried to use platform-tools v33.03 to sideload full OTA file and got read error right away , file SHA-256 checksum is correct , no idea what went wrong ......after OTA update in system , boot to bootloader error appeared again .
[Google Pixel 7 Pro] gpvecchi:
I updated with OTA, both slots, using 33.0.3, no problems here.
[Google Pixel 7 Pro] federicocip85:
Updated, seems smoother than before, still no audio from usb-c earphones though.
[Google Pixel 7 Pro] wangdaning:
Did it error while flashing bootloader? If not you probably just have to hold the power button down for a long time, 30 seconds or something, and it should go back to bootloader. If you broke bootloader then only warranty repair can help. They will probably replace it or the motherboard.
[Google Pixel 7 Pro] jaythenut:
Mines working now
[Google Pixel 7 Pro] mmeidl78:
Funny thing with the fingerprint-sensor. I deactivated developer options in the previous beta and got the problem that every time I wanted to use the fingerprint sensor I had to use my pin instead. Reactivated developer options (nothing special in the options itself) and rebootet the phone and the fingerprint sensor worked again.
[Google Pixel 7 Pro] FedericoUY:
Thanks for the input. Not trying out the beta because of the FP sensor. Already checked this error on my old p6p and was annoying.

Such a basic functionality should not be failing even in early beta stages...
[Google Pixel 7 Pro] Aks:
It fixed my fingerprint issue, android.qns crash issue and wallpaper settings crash. It works seamlessly now. Also, I used pixel flasher with Magisk 26.1 patched image and platform tool 33.03. Everything went smoothly. No issues with Google pay, Wallet and other banking app, thanks to safetynet-fix-v2.4.0-MOD_1.2.
[Google Pixel 7 Pro] ajaxchen:
No idea why but I am not alone . My P7P's FP stop working since Android 14 DP1 , wait for beta 2 to fix if possible .
[Google Pixel 7 Pro] Aks:
Hope they release it soon, keeping fingers crossed 🤞
[Google Pixel 7 Pro] exocetdj:
my motherboard is fried too

luckily im getting it fixed & back tomorrow under warranty. Not sure exactly what happened but phone is competley non responsive
[Google Pixel 7 Pro] Aks:
Does this clock look bigger to anyone? I find it odd but it wasn't this big before update.
[Google Pixel 7 Pro] roirraW "edor" ehT:
It looks exactly the same size as mine on Stable April firmware.
[Google Pixel 7 Pro] exocetdj:
i have heard that with A14 factory images won't work with USB A-C Cables. rubbish for anyone without a lighting port on their PC

Is this some new "Feature" google are implemeting? or will it likely get sorted when platform tools is fixed?
[Google Pixel 7 Pro] roirraW "edor" ehT:
I'd be extremely surprised if Google is actually preventing them from working, or even trying to distinguish what kind of cable is being used. The desktop computer I built just over two years ago has several USB-C ports, plus I'm staying on Stable, so I can't say definitively whether this is true or not.

Are you talking about Apple's Lightning port? Whether lighting or Lightning port, what's the relationship to this scenario?
[Google Pixel 7 Pro] LLStarks:
I've never seen any issue with USB port type for factory images. Deeper parts of bootloaders such as emergency nand flash modes can be more picky or require USB 2.0. The Pixel doesn't have anything like that though.

Just use a high quality cable and the fastest port available. Usually there's no problem at that point.
[Google Pixel 7 Pro] davebuddy69:
Noob question. Currently on stable A13 P7Pro not rooted. I want to install this Beta OTA with all of its perils. My question i download & Install this Beta then do a factory reset like usual with full version upgrades??? Or does it make a difference since it's a Beta. Hope that makes sense.

Thanks in advance,

Dave
[Google Pixel 7 Pro] roirraW "edor" ehT:
It depends on how you install the 14 Beta whether your phone will be wiped. Note that some users found that Android 14 Beta works better for them if you do wipe. Also note that once you try 14 Beta, you can't downgrade to 13 Stable (or 13 QPR Beta) without wiping.

If your bootloader is locked and don't plan on unlocking it, or you can't unlock it, then your choices are more limited.

I know you could officially Opt into the Beta program (instructions at one of the links/quoted article in the OP). Then your phone won't be wiped.

You might be able to sideload the 14 Beta 1 with the bootloader locked. That won't wipe your phone.

Also, and this is very important - if you can't unlock your bootloader, then you'll be stuck in the Android 14 Beta program until it goes final or you - or you officially opt out, then I *think* you'll get the latest Android 13 Stable OTA, but it'll wipe your phone.

If your bootloader is unlocked:

You can use platform-tools v33.0.3 to manually flash the factory image. As with any Pixel factory image, if you remove the -w from the flash-all.bat or flash-all.sh (if that's what you use), then it won't wipe your phone.

You can use the web-based official Android Flash Tool and untick the box to wipe your device. Again, see the links or the quoted article in the OP for the link.

I'm going to repeat just because it's important. Some users found that the Beta worked better for them if you start fresh. Even with a factory reset, users are having many issues. We're still on Beta 1.1, so it's still fairly early.

And I'm also going to repeat that once you get on the Beta program, you can't downgrade without wiping. Things wouldn't work correctly if you didn't wipe when downgrading.

I hope that all answers your question.
[Google Pixel 7 Pro] ajaxchen:
I did flashed A14 Beta 1.1 and Beta 1 factory image with USB A-C cable without any problem , wondering where you heard from ?
[Google Pixel 7 Pro] exocetdj:
Sorry guys forgot to add my sources (im adhd as hell and forget things especially if tired)

It was this post from p11, my friends experiences which mirror this and also the fact i had no joy with a a-c cable gave me this impression so just sought some clarification here. (albeit my experiences were on b1 not b1.1 as my phone was a brick before i got to fully flash it lol)

@roirraW "edor" ehT again me being damn senile - thunderbolt port is what was meant (sorry to pollute this thread with apple terminology haha)

anyway - looking like my assumptions could be wrong which would be great :)
[Google Pixel 7 Pro] davebuddy69:
Thank you Edor. Very thorough explanation of my options. Have a great day! Regards, Dave
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thank you for the confirmation that A->C works.

No sweat. Occasionally, even one or the other of my USB-C cables/ports occasionally fails to flash the monthly Stable update, even when I try again, but switching to one of my other USB-C ports and cables then works fine, and they're all high or extra high quality, not OEM Google which are USB 2.0 as well. I have four different cables already plugged into each all the time.

Then months later, sometimes I have to switch back to the "old" USB-C cable and port, and then it works fine until it doesn't.

Don't try this at home, and seriously, it's not recommended, but I've even flashed all my phones including Pixel 7 Pro and 6 Pro through a powered USB 3.2 Gen 2 4-port hub which is connected via (12 foot? 15 foot?) USB-C cable to one of my desktop computer's USB-C ports.

So things happen no matter what. I don't usually sweat it, since just switching to a different port and cable usually solves it, and I feel it's not worth trying to solve as it's likely just going to happen whenever.

You're welcome! You too.
[Google Pixel 7 Pro] LLStarks:
Beta 1.1 appears to be a bit more stable. Whatever they did since Beta 1 and supplemented with carrier services updates seems to be helping. I honestly didn't expect that but it would make sense given how the issue seems to be rooted in IMS failures.
[Google Pixel 7 Pro] reg66:
com.android.qns issue now fixed for me too, just in case it gives others a better idea of numbers of people that have it fixed now as a percentage of reports.

@ajaxchen, before installing 1.1, I managed to remedy it by removing all fingerprints, then reboot, then re-do all fingerprints, still wasn't working until I toggled fingerprint security off and on again... you could try this if you haven't already.

Maybe I just got lucky, though. Worth a go tho

EDIT: can confirm also, USB headphones not working tho
[Google Pixel 7 Pro] ajaxchen:
@reg66 , thanks for your advice , but my P7P was fresh installed Beta 1.1 factory image with flash-all -w (both slots) command , so , not my lucky day then .

@LLStarks , I just found my P7P has no carrier server installed after flashed Beta 1.1 factory image , no Pixel Camera services either . But network ( mobile 5G and Wifi ) , camera works flawlessly , weird enough .
[Google Pixel 7 Pro] sanjsrik:
Anyone else opt-out of the beta? I had to go back to 13 because the constant dropping of calls and calls just cutting out for recipients. I can hear them, they literally cannot hear me at random intervals.

Yes, I know, it's beta software. Feels like alpha software really.
[Google Pixel 7 Pro] Beddadizi619:
I'm trying to fastboot flash the radio image from QPR3beta3 but it wouldn't let me. My device is OEM locked. Is that the reason?
[Google Pixel 7 Pro] Dave_247:
Strangely I never got the update notification for the new 1.1 build, and nor do I seem to be able to manually sideload the OTA in the stock recovery either for some reason as it is unable to mount the SD and isn't being recognised by my PC when selecting the option to sideload over ADB.

With the option to use Fastboot still being borked I guess I just have to wait as I really don't feel like having to wipe my phone yet again for such a minor fix
[Google Pixel 7 Pro] aleksgiab:
How do I unlock the bootloader in this version I can't do it?
[Google Pixel 7 Pro] roirraW "edor" ehT:
Is your Pixel 7 Pro is a factory unlocked model? Can you explain more about what you can't do? Are you able to toggle the OEM unlocking in Developer Options? Or is it the command to unlock the bootloader which is failing? Are you using Platform-Tools v33.0.3?

https://xdaforums.com/t/may-1-2023-...der (required in order to root),-The one-time
[Google Pixel 7 Pro] p51d007:
Only issue I've seen, is the signal drops from time to time, put it in airplane mode for a second or two, then out of airplane mode and the signal returns. Any "quick fixes" for that?
[Google Pixel 7 Pro] ariesgodofwar:
I am missing calls constantly because of this. Only know I missed them by the email notification I receive. Hitting the network reset button under Network & Internet will fix the issue (at least temporarily). I've also noticed that there is hardly a word in the English language to describe how terrible Network Switching is. It is either beyond slow or non-existent when going from Wifi to Mobile connectivity. They rolled out a new version of Google Connectivity Service (v61) this morning, hoping that perhaps there was something related causing the issue and that it might make positive some impact, but that is probably overly optimistic of late. Not sure why they focused Beta 1.1 on really dumb UI stuff and not the serious connectivity issues.
[Google Pixel 7 Pro] davebuddy69:
For those of you having buggy call problems and other beta issues this is what I did with my TMO 7Pro. Set preferred carrier to LTE and turned off WiFi calling and have zero problems. I know this is not ideal but better than setting your phone up again. The next beta will be out soon enough.
[Google Pixel 7 Pro] LLStarks:
Or don't do that and simply downgrade to the QPR3 Beta 3.1 modem and keep 5G and wifi calling.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Not Android 14, but...

Android 15 might decouple NFC from system updates

At this pace, it almost feels like we won’t need proper Android updates at all in a few years

www.androidpolice.com

https://twitter.com/i/web/status/1655636463760056320
[Google Pixel 7 Pro] LLStarks:
I see the Beta 2 DSUs but no images or OTA files yet. Soon, I guess.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Beta 2:

Android 14 | Android Developers

<!-- hide description -->

developer.android.com

Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developer.android.com

Get Android 14 | Android Developers

Get Android 14 on your eligible device.

developer.android.com

Android 14 | Android Developers

<!-- hide description -->

developer.android.com
[Google Pixel 7 Pro] Lughnasadh:
Their blog post...

Second Beta of Android 14

The Android 14 beta is now available from partners including Lenovo, Nothing, OPPO, OnePlus, Realme, Tecno, Vivo, and Xiaomi across select devices!

android-developers.googleblog.com
[Google Pixel 7 Pro] LLStarks:
Finally seeing sub6 4CA advertised for T-Mobile.

n25-n41-n41-n71 is the most exciting combo.
[Google Pixel 7 Pro] ~Dipper~:
They finally fixed the factory image 😬
[Google Pixel 7 Pro] Murderburger:
But are calls staying connected?
[Google Pixel 7 Pro] LLStarks:
For the moment, but we'll see.
[Google Pixel 7 Pro] Pixel86:
Battery life good enough to daily drive over QRPs?
[Google Pixel 7 Pro] One2ManyPhones:
It was just released..... No one will be able to give you an accurate recommendation.
[Google Pixel 7 Pro] Pixel86:
Should have been more specific. I meant Android 14 beta in general 🙂.
[Google Pixel 7 Pro] iRhyiku:
Got 2x battery backup in safari and recording in 4k allowed 3 days of usage
[Google Pixel 7 Pro] Dave_247:
Ah thankfully I got the OTA notification for beta 2 which saves me a lot of trouble. Hopefully that's that worst and most annoying issues now dealt with.
[Google Pixel 7 Pro] One2ManyPhones:
Past Beta's were bad, will update when I run this one some more.
[Google Pixel 7 Pro] iRhyiku:
Only issue I'm dealing with on A14 is the Wallet Payments not working
[Google Pixel 7 Pro] Aks:
At a glance text definitely got smaller! Rest all is good including gpay, wallet and banking apps.
[Google Pixel 7 Pro] BlueReaperX:
Beta 2 seems to have fixed the issue with the radio. I used to lose cell signal (LTE and phone calls, but not 5G for some reason) every 5 minutes or so at the office. With the latest Beta, I no longer have this issue and overall, it seems like a solid build.
[Google Pixel 7 Pro] ariesgodofwar:
That is crazy as my experience seemed to have been the exact opposite. I am on TMO, and my phone was unusable with 5G/Vo5G enabled, 80% of my calls went straight to voicemail, and calls would drop left and right. The network switching was totally borked, but then I set to LTE, and saw significant improvement. In any case, so far so good with Beta 2, was able to reenable 5G and seems to work properly now
[Google Pixel 7 Pro] the_alchemis7:
Beta 2 been feeling a lot smoother for me however, twice it's frozen and screen went black needed rebooting, and the fingerprint no longer works in apps (works fine on lockscreen)

Network wise seems better than beta 1
[Google Pixel 7 Pro] Gordietm:
It's been freezing for me a lot. I went back to A13. Also Nova launcher doesn't work properly.
[Google Pixel 7 Pro] EtherealRemnant:
Anyone else having their battery read 0%? lol. Weirdest bug I have ever seen. Third party apps report 0% too while reporting 3.9v, which isn't 0%. Plugging it in with the power off, the battery is actually at 68%.

EDIT: Turning it on after plugging it in, the battery level is being read again.
[Google Pixel 7 Pro] 94b20gsr:
Interesting, under the release notes for the new Beta section "Other resolved issues" they describe the same issue you're experiencing being resolved
[Google Pixel 7 Pro] EtherealRemnant:
It's my first time seeing it so I guess not lol
[Google Pixel 7 Pro] p51d007:
Hey, it's NOT a big deal, but go to the help/about tap on it to bring up the easter egg.

Mine still shows the Android 13 stuff, not the 14.

Anyone else still seeing that?

Guess it's not a big deal for google yet to splash the 14 easter eggs.
[Google Pixel 7 Pro] Gordietm:
They also said back gestures on custom launchers was resolved, but nova launcher was basically unusable. I went back to A13.
[Google Pixel 7 Pro] gpvecchi:
Almost unusable to me: phone keeps freezing, even worse than first beta.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I wonder if it works any better for those who wipe data, like it did on one of the previous betas.
[Google Pixel 7 Pro] One2ManyPhones:
I installed using fresh wipe and factory image. It is freezing on me too randomly especially while in the App Switcher.
[Google Pixel 7 Pro] p51d007:
I'm using Nova prime...everything seems to be working on my end. Interesting...
[Google Pixel 7 Pro] Gordietm:
What version of nova? I was on v8 04.
[Google Pixel 7 Pro] reg66:
Left the beta for A13, but just letting you know there's a newer update just out...

https://novalauncher.com/beta
[Google Pixel 7 Pro] Gordietm:
Yes, I know. I'm on 8.05 now on A13.
[Google Pixel 7 Pro] reg66:
Ahhh my bad, thought you were saying you had issues and were still on 8.0.4
[Google Pixel 7 Pro] xunholyx:
I've seen several reports of this on other forums/groups. A friend of mine from the OG Team Venom had the same happen to him as well
[Google Pixel 7 Pro] Aks:
Any observations of Bluetooth connectivity? I'm having hard time using pixel buds on this build, not for calls but while listening to music. May it be any app or even offline music, first 5 minutes it's good. After that, it keeps losing connection for about up to 5-7seconds (time varies) and then reconnecting. I also reset my pixel buds but it didn't help.
[Google Pixel 7 Pro] p51d007:
Mine shows 7.0.57
[Google Pixel 7 Pro] One2ManyPhones:
No issues with bluetooth here. Connected to my Pixel Watch and Pixel Buds Pro just fine with no drop outs.

Besides the random lagging and freezing happening with the App Switcher this build has been pretty solid.

One thing I did notice is my battery life over the past 24 hours from installing this build has been fantastic. It is even better than when I was on a custom ROM with a custome kernel, or my previous use of Stable 13.
[Google Pixel 7 Pro] Aks:
I just had a random freeze (first time) and then it went into bootloop. Rebooted in safe mode and then normal boot. Now after normal boot, all Magisk modules are disabled. If I turn any of those on then bootloop again. Phew!!! Will figure out on weekend what exactly is causing this.

PS - it worked well for couple of days but now...
[Google Pixel 7 Pro] roirraW "edor" ehT:
Safe mode disables all Magisk Modules, so that part is normal - just in case you weren't aware. No idea what to suggest about re-enabling any modules causing a bootloop, especially since they worked for a day or two.
[Google Pixel 7 Pro] Aks:
Exactly why I'm wondering what could be the issue since it worked well. Yeah, I'm aware safe mode disables all modules. However, when I enable those again, it messes up something. I guess I'll check each module individually but I'm assuming that it might have something to do with aosp mode. Will confirm after I play around with it.
[Google Pixel 7 Pro] Aks:
It's confirmed, AOSP mods! Enabled on all modules individually, rebooted and no issues. When I enabled AOSP mods and rebooted, it went into bootloop. Did it 3 times just to be sure. For now, I've kept it disabled.
[Google Pixel 7 Pro] Aks:
This seems to be resolved now today! My guess would be post # 359 but can't be sure.
[Google Pixel 7 Pro] amandeepparmar:
Bluetooth issue with random freezes confirmed on Beta 2... probably something to do with deep leep state be ause as soon as you double tap on AOD...music resumes!
[Google Pixel 7 Pro] Aks:
And issue persists! With any Bluetooth headphones. Submitted feedback to Google.
[Google Pixel 7 Pro] DAE1964:
I clean installed Friday and restored from Google back-up. I am also running without Root. I have Amazon music HD paired with my Sony WH-1000XM3.

I have had zero issues with playback.

No pausing, freezing. Wired headphones with usb dac have consistent pausing during playback. Earmen Sparrow with Sivga Phoenix.

I have had several random system freezing where Android rebooted after 10-15 seconds.

Settings/System/Rules is missing also.

Everything else including battery life seems to be a step up over Android 13.
[Google Pixel 7 Pro] dd805bb:
Is anyone having issues with Ful Screen Gestures not working? Came back to 14 and still can't get it working. Thank you in advance.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Are you using a custom launcher like Nova, or the built-in Pixel Launcher? If something other than Pixel Launcher, it might require waiting for the launcher to be updated, and/or for Android 14 to go Stable.
[Google Pixel 7 Pro] dd805bb:
No custom launcher. And light on modules. While on 13 I did have aosp mods and lsposed installed. I might have to do a clean install.

AdAway, Repainted and root explorer on root apps. And Fullscreen gestures, systemless hosts, displax universal safetynet fix. I might just clean install to cover my bases.
[Google Pixel 7 Pro] Aks:
Set App Battery Restriction to unrestricted and I believe it helps with uninterrupted playback.
[Google Pixel 7 Pro] DAE1964:
I was setting up tasker to sub for rules and I noticed settings/system/rules just appeared. Weird!
[Google Pixel 7 Pro] BlueReaperX:
It's weird how some are finding Beta 2 to be worse than Beta 1.

In my case, it's been very stable with no issues at all. If I didn't know any better, I would say it's a stable release. I didn't even clean wipe before flashing the DP2 after A13 QPR3 Beta 2 and I just kept updating with OTAs from there. DP2 was horrible and Beta 1 was arguably worse with the unusable radio image.

A14 Beta 2 fixed the modem, Bluetooth, Android Auto usability, and it's as smooth as A13 QPR3.
[Google Pixel 7 Pro] p51d007:
Beta 2 for me, is better than beta 1. Non rooted, updated from the beta 13 to 14.

Signal strength is better.

Previously, I would have to turn on airplane mode for a couple seconds, to get the signal

to show up again.