yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] roirraW "edor" ehT:
v34.0.0 and 34.0.1 of Platform-Tools is known to be buggy. Stick with 33.0.3:
[Google Pixel 7 Pro] roirraW "edor" ehT:
Yep, likely. USB connection directly to a motherboard/laptop is always recommended.
[Google Pixel 7 Pro] jordi.id96:
v33.0..3 worked perfectly
[Google Pixel 7 Pro] gpvecchi:
I think that factory images have some issue. I'm trying to flash back DP2.

Edit: No issues flashing DP2.
[Google Pixel 7 Pro] Jiggs82:
u manually flashed beta 1 over stable 13?
[Google Pixel 7 Pro] jordi.id96:
I installed over the dev preview
[Google Pixel 7 Pro] EtherealRemnant:
What about n77 DoD?
[Google Pixel 7 Pro] LLStarks:
I'm still looking for that. I don't have an AT&T sim. I'm also trying to remember whether the phone was certified to operate on that frequency.
[Google Pixel 7 Pro] Dave_247:
Urgh, this is the second time now from Google somehow managing to screw up even bigger than last time with version 34 of platform tools. I had to hunt to find a link to the DP2 build because of course Google doesn't make that easy either. Here it is for anyone else who gets stuck and wants it,

https://dl.google.com/developers/android/udc/images/factory/cheetah_beta-upp2.230217.004-factory-d601ddfb.zip

Also I created a ticket in the issue also about the build flash error, maybe if we are lucky it might get fixed before they fix thep platform tools issue. or we just wait until Beta 2 I guess.

Google Issue Tracker

issuetracker.google.com
[Google Pixel 7 Pro] LLStarks:
XDA articles are usually a good archive of previous release links.
[Google Pixel 7 Pro] EtherealRemnant:
Sure looks like it.

3705-3975MHz testing: https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=6037055

3455-3544MHz testing: https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=6037056
[Google Pixel 7 Pro] Pietrakovsky:
lost 5g and volte, p7p Orange poland
[Google Pixel 7 Pro] LLStarks:
So the last piece of the puzzle is whether it works.

Everything's in place. Release 16 and especially extendedBand-n77-r16 were the final hurdle.
[Google Pixel 7 Pro] Murderburger:
It's been pushed to my phone officially on the Android Beta Program
[Google Pixel 7 Pro] aunni:
I installed Beta 1 over stable 13 on my P7P. The Primary SIM (physical SIM in the SIM Card tray) disappeared. Only have a secondary eSIM working. Reboots, and even factory reset didnt work. Going back to stable now. Hope that sorts it out. There are bugs and then there is this! Anyone else faced this?
[Google Pixel 7 Pro] skymera:
You legitimately seem mad that beta software has issues.
[Google Pixel 7 Pro] aunni:
Would you consider the primary SIM not working a typical beta software issue?
[Google Pixel 7 Pro] skymera:
Beta software could affect any compnent in any way. I've not seen others report this yet so it could be a rarer bug, so report it.
[Google Pixel 7 Pro] aunni:
Reported already by someone else.

https://www.reddit.com/r/android_beta/comments/12khkjn
[Google Pixel 7 Pro] roirraW "edor" ehT:
Everyone, +1 this (near the top right corner) on the Google Issue Tracker (also linked to in the Reddit post):

Google Issue Tracker

issuetracker.google.com

Thanks @aunni for reporting.
[Google Pixel 7 Pro] Pixel86:
Curious what battery life is like in comparison to Android 13. I'm assuming with it being beta, it is considerably worst than Android 13 stable.
[Google Pixel 7 Pro] bagarwa:
Adding my data point.

State at start:​

Pixel 7 Pro, running Android 14 DP2, Magisk 26.1

Platform Tools 33.0.3

Phone connected to PC using USB A to C cable.

Flash Combos tried:​

Flashing the Android 14 Beta 1 failed with this error -

Sending sparse 'vendor_a' 3/3 (189388 KB) FAILED (Write to device failed (Unknown error))

I "upgraded" the platform tools to the latest 34 RC2.

Flashing the Android 14 Beta 1 now failed with this error -

Sending sparse 'super' 1/1 (4194303 KB) FAILED (Sparse file is too large or invalid)

Phone was essentially corrupted at this point, so I tried to flash 14 DP2 using platform-tools 34 RC2. That too failed with same error -

Sending sparse 'super' 1/1 (4194303 KB) FAILED (Sparse file is too large or invalid)

:eek:

Similar errors occurred when I tried to use the web based official Android Flashing Tool.

Back to local, I tried flashing 14 DP2 with Platform Tools 33.0.3, and that succeeded. So, I'm convinced that v34 is bugged / useless.

What Worked for 14 B1?​

Later at night, I switched to an USB C to C cable. FINALLY that worked. I was then able to flash Android 14 Beta 1 using Platform Tools 33.0.3.
[Google Pixel 7 Pro] p51d007:
So far, the only issues I've see are my app bluemail and on the times I use my DJI Mini2 (I usually use the air2S with the other controller) crash when launched. No biggie...it's a beta.

Both reported to google and the app developers.
[Google Pixel 7 Pro] roirraW "edor" ehT:
You may want to add your +1 (near the upper right corner) of the issue that was reported to Google about this, and they know about, but haven't fixed yet. Note, also, there is no 34 RC2. At least, they released 34.0.0, then they released 34.0.1, and then for unfathomable reasons, they have 34.0.0 RC2 listed above the release notes for 34.0.1, but the most recent download is actually for the same 34.0.1 that was out all along, but both versions of 34.x indeed have a known serious bug and shouldn't be used:
[Google Pixel 7 Pro] Murderburger:
Phone runs great on the new Android 14, only issue is signal. Phone loses signal in spots it didn't before, takes longer to get back signal after it's lost.

I live in an area with very low bars on my drive to and from work I know the exact sign I lose signal and the exact bolder on the side of the road it comes back at.. lol

I reset the Network, and just because the Bluetooth and Wifi.. issue still persists. I even manually added T-Mobiles APN.
[Google Pixel 7 Pro] ajaxchen:
I would like to know if many people got physical SIM issue ? Since My P7P updated from QPR3 Beta 2.1 to Android 14 Beta 1 with ADB(33.03) sideload method , except reboot or power-on to fastboot boot failure screen from time to time , fingerprint sensor not working , I did not have physical SIM issue even with different SIM .
[Google Pixel 7 Pro] xunholyx:
^^^ this leads me to wonder what method of updating did the others with this issue use? Were they all adb sideloaded OTAs?
[Google Pixel 7 Pro] LLStarks:
My spare sims are in various states of working and not working. Maybe that's why my TracFone one was failing but I probably just need to activate it.
[Google Pixel 7 Pro] exocetdj:
No issue side loading ota but platform tools and the factory image was being a bugger
[Google Pixel 7 Pro] WillyRy:
I did the same, QPR3 Beta 2.1 to Android 14 Beta 1 via flash-all.bat (removed -w) with 33.03

Physical VZW SIM came out of ! state first, VZW eSIM took a couple reboots before becoming active.

Signal and data speeds are pretty abysmal, however.
[Google Pixel 7 Pro] EtherealRemnant:
Google is such a joke. I can't believe they posted images that neither PixelFlasher nor their own freaking flash tool can successfully flash using the same damn USB-C cable every other flash has ever used on the same computer, and not running the busted v34 platform tools (another thing that makes them a joke).

Good thing I didn't have anything I needed to save as I'm having to reinstall QPR3 (which means a factory reset due to the bootloader downgrade since the bootloader for 14 flashed) and then I'll have to OTA to 14. I get that it's a beta but seriously, that's just lazy and it's pretty damn inexcusable in my book. That's some alpha level crap, not what should be expected from a beta.
[Google Pixel 7 Pro] xunholyx:
I agree. I haven't flashed it because of issues I've seen online. Betas have bugs, but this level hasn't been seen in many years.
[Google Pixel 7 Pro] LLStarks:
Going back to the QPR modem. I need something that works while I'm on vacation.

The beta modem made my signal garbage and I couldn't even receive calls without constantly toggling my esim.
[Google Pixel 7 Pro] ericDraven77:
@p51d007 Try using the beta program / App of bluemail.

This should work :)

I only have an issue with my DreameHome App. Everything else is running as before.

Sadly, my battery drain in idle mode is running like before too..... when I switch off WLAN it is a lot better, but that can't be the solution when using a Phone at home.
[Google Pixel 7 Pro] Dave_247:
I ended up doing a clean flash of DP2 (following the corrupt flash of Beta 1 factory image) and from there did the automatic OTA update as I have my phone enrolled in the beta program still. So far the worst thing I have experienced is the system up will lock up and freeze for a few seconds at certain moments, but I've experienced worse then this with custom ROM's in the past. So far the one certain way I've found to reproduce it is when uninstalling a app.

I haven't experienced any issues with my physical sim, though I am in Australia so perhaps the county/locale has something to do with it.
[Google Pixel 7 Pro] RYZONN:
Any way to roll back 14B1 to stable version without wiping? I'm full of bugs

In case I have to rollback through the normal wipe process, do I have to remove the esim card?
[Google Pixel 7 Pro] roirraW "edor" ehT:
No, you can never downgrade without wiping. If you did, expect things to not work correctly, if the phone even boots at all.

I guess I don't specifically know, but I wouldn't think so. As far as I know, treat it just like a physical SIM card. I don't remove my physical SIM card when I wipe or flash anything.
[Google Pixel 7 Pro] p51d007:
The developer team sent me the beta APK which worked. I noticed the play store had an update posted today (Friday) but I haven't installed that.
[Google Pixel 7 Pro] gururoop:
Has anyone noticed that proper # keys are not being input during a call. I tried booking a service appointment for my car yesterday and I kept on pressing 1, to which the service centre kept on giving me invalid input error. I thought it was an error on their part, but today I was trying to access my voicemail and it kept on giving me invalid pin. I tried resetting the pin online, but even that doesn't work. I tried using Truecaller as my default phone app and still it gave me the same problem. Am I the only one with this issue, as I didn't see anyone else complain about it?
[Google Pixel 7 Pro] federicocip85:
Same for me, tried now because I read your message! No big deal for me at the moment, but I think it's worth to give feedback to Big G.
[Google Pixel 7 Pro] Aks:
No, you don't need to. Your esim will automatically get activated once you start setup process. If you do then you'll have to download sim again with help of your operator which might be but painful.
[Google Pixel 7 Pro] Aks:
Update on Beta 1 after 2 days, rooted with Magisk 26.1.

No random reboots (finally). Issues noticed so far -

1. Sometimes UI becomes unresponsive for a few seconds

2. Gpay (India version) didn't work initially after update, had to uninstall and then setup again

3. Blackberry Work and UEM Client didn't recognize A14 and locked me out, but resolved after uninstall and install

4. Themer sometimes loses the settings applied and have to reapply my settings (could be app issue too, don't know for sure).

Will report another observations as and when I come across any. Till then enjoy folks! (y)
[Google Pixel 7 Pro] LLStarks:
Here's a pretty major discovery.

The Beta 1 modem supports 4CA. It can combine 4 sub6 5G signals. Your carrier is likely not broadcasting 4CA yet.

This brings the 5300 modem a lot closer to the Snapdragon X70.

Source: Amelie
[Google Pixel 7 Pro] EtherealRemnant:
Fascinating. If Samsung had such a capable modem on deck, what was their strategy in hiding what it was capable of? I mean they didn't announce specs or anything when they did their little product announcement a few days before the Pixel 7 series dropped. Samsung finally put up a site for the 5300 now too.

Exynos Modem 5300 | Modem | Samsung Semiconductor Global

Exynos Modem 5300 provides 5G speeds with a reliable connective anywhere and a long-lasting battery. Experience a next-generation mobile experience today.

semiconductor.samsung.com

Specs seem pretty damn comparable to the X70. It's weird that the maximum aggregated 5G downlink is 200MHz while the uplink is 400MHz though.
[Google Pixel 7 Pro] Dave_247:
You know I just had a thought, maybe no one at Google has been bothering to test if builds are compatable on Windows? As they are probably all cooking then on Linux as I forgot that's where Android's roots are. I highly doubt Google are that would be pushing out builds if they in this state internally. Same with the platformtools issue. Though it they are also borked on Linux then I'll laugh/cry.
[Google Pixel 7 Pro] LLStarks:
The aggregated bandwidth specs are probably wrong.

Apparently the modem can also do 9CA NR-DC. A sub6 standalone anchor and 8CA mmwave standalone.
[Google Pixel 7 Pro] Psyscope:
Actually it's the biggest pain, phone before unusable while driving. Lose signal and at times don't get service back for a while.
[Google Pixel 7 Pro] LLStarks:
The Beta 1 modem is not usable as a daily driver. Only good for research.
[Google Pixel 7 Pro] xunholyx:
Personally, I haven't even flashed it to my secondary device. I meant to on day 1, but I was busy and was going to flash it to both of my phones the next day. I saw multiple reports about various bugs and now I'm glad I was busy that day
[Google Pixel 7 Pro] EtherealRemnant:
It is interesting to me that the pSIM disappearing from the phone bug I reported months ago seems to be hitting a lot of people. If you pull the pSIM and put it back in, it will usually show back up in the phone, but sometimes, you have to use a different pSIM to get it to come back.

Hopefully this will make Google fix the issue altogether.
[Google Pixel 7 Pro] WillyRy:
Has anyone had trouble with hotspot? Mine won't stay activated. Will try for a second, then fail. Tried on both pSIM and eSIM. VZW

Searched but didn't see any posts
[Google Pixel 7 Pro] tauio111:
Here is a partially decoded NR NSA & NR SA combo dump from the new combo format introduced with the new modem for anyone that wants to see:

pixel-shannon-combos/uecapconfig_csv at main · NXij/pixel-shannon-combos

Initial decoding attempt at decoding the new uecapconfig files on Android 14 Shannon Pixels - NXij/pixel-shannon-combos

github.com

9CA NR-DC (as advertised by Samsung on their site) is there for US carriers. 1x FR1 and 8x FR2.

That should be able to deliver a maximum of 900MHz of downlink and 500MHz of uplink as per the combinations (not too sure) in the US carriers config files. Think Samsung has a few typos on the modem page where they mixed up the sub-6 DL and UL bandwidths.

4CA FR1 NR-SA is also available for the US, German carriers (DT for example) and the Wildcard(yes) profile. There probably arent many if any networks capable of 4CA SA yet so this has not been tried.

Google also does not seem to care much about UL-CA - seems to basically only happen in the case of FR1+FR2. Atleast there seems to be UL MIMO on n41, n77, n78.

There is also a bug currently that appears to be loading the APAC_COMMON combo set for carriers that are lacking a combo file instead of the WILDCARD one, so expect 5G not to work properly if your network does not use the n78 band in NSA.
[Google Pixel 7 Pro] V0latyle:
How's UPB1 been for everyone? Any weird display drawing issues? Seems to be the main issue on my Pixel 5, every once in a while stuff gets "stuck" on the screen, such as Youtube small picture, or the lock screen overlays atop home screen. Other than that, everything else seems to be working OK...
[Google Pixel 7 Pro] the_alchemis7:
Same, apart from that the data icons come and gobfor long periods, and data (or wireless) stutters, if I open a message eg WhatsApp on the lockscreen it won't use fingerprint rather it asks for pin
[Google Pixel 7 Pro] LLStarks:
Excellent write-up.

Unfortunately, the modem is not usable. I was only able to solve my dropped calls with the QPR3 Beta 2.1 modem.

Wi-Fi calling wasn't working either.
[Google Pixel 7 Pro] ajaxchen:
Then , I think I am lucky enough . Flashed OTA file from 13 QRP3 Beta2.1 to 14 Beta 1 , only fingerprint error and some boot error are the major bugs to me . Other than these , everything works better than 13 QPR3 Beta 2.1 . I got 4CA and fast mobile speed than before , VOWifi and VOLTE working as well . It leads me to think if some bugs are related to different carrier .
[Google Pixel 7 Pro] WillyRy:
Did you just fastboot flash radio QPR3B2.1modem.img on top of 14.Beta 1?

EDIT: corrected CMD to radio to avoid mistakes
[Google Pixel 7 Pro] LLStarks:
Yep. It's fastboot flash radio xyz.img though.
[Google Pixel 7 Pro] jcrutchvt10:
T-Mobile here only issue I have is the data symbol disappearing from the status bar. It still works, just don't have the symbols. Downloading the AOSP Magisk mod and adding the VOLTE Icon seems to be helping all data icons stick? I don't know.
[Google Pixel 7 Pro] jamestaylorxda:
I have the same issue. My in call keyboard doesn't work at all.

I installed the QPR3 2.1 modem, and it helped with the phone and data, but didn't have any affect on the keyboard issue.

Does anyone have a fix or workaround they've uncovered?
[Google Pixel 7 Pro] roirraW "edor" ehT:
Several people have said this Beta 1 works much better if you start fresh (factory reset), although you should still replace the radio.img with the one from either Stable or QPR3 Beta 2.1.
[Google Pixel 7 Pro] gururoop:
But does starting fresh with QPR 2.1 img solve the in call keypad problem? This issue is a deal breaker for me and frankly this is the first time in years I was forced to leave the latest Android version and go back to stable.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I don't know, but there is no way to downgrade the whole Android image from 14 Beta 1 to either QPR3 Beta 2.1 or Stable without wiping everything anyway, so you might as well try a factory reset. Using the QPR3 Beta 2.1 modem.img will only fix the issue users are having with their signal.

All I know is that several users said things were much better after wiping data.
[Google Pixel 7 Pro] WillyRy:
Flashed QPR3B2.1 radio on top of 14b1 and helped signal, but didn't fix hotspot.

FWIW

(System UI keeps crashing and "Wallpaper & Style" force closes, so I can't change that God awful puke green color. Don't judge me 😜)
[Google Pixel 7 Pro] roirraW "edor" ehT:
You could try QPR3 Beta 3's radio.img. Doubtful if it will fix hotspot for you, but there's always a chance.
[Google Pixel 7 Pro] morpheus620:
Hello,

I installed the beta to test it. I can't see my fingerprint on the lock screen. It only shows me the lock even though I have deposited a finger.

And me Network is working. I have O2 Germany. The only thing is, the 5G/4G icon is missing from the top bar.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Try that below:
[Google Pixel 7 Pro] morpheus620:
Still, my fingerprint doesn't work. I'm switching back to stable.
[Google Pixel 7 Pro] ajaxchen:
I got fingerprint bug since Fresh installed Android 14 DP1 ( 14 beta 1 as well ) . Back to 13 QPR3 beta is zero bug but after flashed 14 beta 1 OTA file via platform tools 33.03 , fingerprint didn't work again . I had tried android flash tool to fresh install 14 beta 1 yesterday but failed by unknown error . Then , flashed 14 beta 1 factory image by platform tools 33.03 (flash-all -w) , fingerpring not working still but fixed boot to bootloader error , less bugs and much smoother than flashed OTA file to 14 beta 1 , worthy to give it a try .
[Google Pixel 7 Pro] morpheus620:
the fingerprint is broken in beta 1.
[Google Pixel 7 Pro] ericDraven77:
I niether have a problem with my fingerprint, nor with the SIM card and the network.

So it is not a general bug in beta 1 ;)

The only thing I still have is an absolutely lousy battery. Especially when the phone is in idle mode it drains my battery as if I have my screen on.

In this moment I have 50% left with less then 1,25 hours of screen on time. Yesterday I had 17% left with under 2 hours SOT. And i loaded the phone the night before.

It seems to be my mobile service that drains battery, but I have this now since March update on the regular Android 13. Updated to beta 13 and did full wipe but nothing changed, then updated to beta 1 from Android 14 and still it is ridiculous how fast battery drains with mobile network on. If I turn this of battery is absolutely OK. I have Wifi, bluetooth and GPS on and my watch connected and it works fine. I turn mobile network on and I can see the battery percentage go down.
[Google Pixel 7 Pro] kastuvas:
I have no problems with fingerprint or hotspot. Battery is OK, not best. My problems so far: eSIM completely broke, I can't turn it (my main number) back on, no network symbols, physical sim loses signal in places where it had before and sometimes not regaining signal for a long time, camera sometimes freezes or force closes, nova launcher freezes or doesn't go to home screen, recents menu most of the time does not show clear all neither shows app previews, among the usual styles bugs and maybe more stuff what I forgot. I was so annoyed with this 'beta' (how could they release that sh ite to the public????) that I bought myself a S23 Ultra and getting rid of this :LOL: If I need to reset my apps might as well get another device.
[Google Pixel 7 Pro] gururoop:
Hi, since you mentioned that you don't have a lot of common problems, can you please confirm if your keypad is working fine during calls? i.e. the other side are getting the numbers you input during the calls properly? If so, I can try your update path.
[Google Pixel 7 Pro] kastuvas:
I've just tried and no, beeping doesn't work either
[Google Pixel 7 Pro] WillyRy:
screw it, back to 13QPR3B3. See y'all over there for a little longer

Tired of my kids yelling and complaining about their tablets not connecting to my hotspot :ROFLMAO::cautious:
[Google Pixel 7 Pro] ericDraven77:
@gururoop If I get you right you mean if I can use the Dial Pad during Phone calls?

Yes I can use this. The last days I had to call a hotline several times and had to get my birthday with the dial pad to prove it's me ;)

But I just updated from Android 13 normal to Android 13 Beta QPR 2 and then after a full reset I updated to Android 14 Beta 1. The reset was only because of my poor battery with network draining 5% an hour when I don't use the phone. I had no problems with the phone anyone ever mentioned but the battery drain. Never, with no Version of Android.
[Google Pixel 7 Pro] ajaxchen:
Mine dial pad during calls works fine as well , no problem at all .

As for battery , I got better battery life than QPR3 Beta ; WIFI , 5G and bluetooth are always on , only 2% droped after 7 hours sleeping hours .

Just wish Google will fix fingerprint in next beta which is the major bug in my P7P .
[Google Pixel 7 Pro] gururoop:
Well, initially I tried to flash full image of Beta 1 on top of DP1 after removing -w flag, which failed and corrupted all my data. Then I clean flashed DP1 and took OTA to beta 1 which had the keypad issue. Then I went to 13 stable and set up all my apps and settings. After reading your comment, I again took OTA to beta 1 and the keypad issue was gone. After a couple of days today, I again tried the keypad during call and again it is giving me same issue. I don't know what is causing the problem exactly. I seriously miss the good old days when we could take full image backup and restore it in case of issues. Now I am too tired to format and go back to an earlier version. I hope Google fixes this issue soon.