Develop Bugs

Issues with February delivered Pixel XLs

For those who received their XLs in February after the delay (who ordered in November/December), have you been experiencing issues? I had trouble activating the phone and ever since, my cellular connection has been spotty. Even when it says its connected, texts and calls sometimes fail to go through or drop. Despite the reviews, I have experienced some lag and freezes. And my battery life definitely does not last a day (I have to charge it twice a day for moderate to light use with 2 hours screen on time). I wonder if this is common with the new batch of XLs that were shipped out or if, I hope, I just received a faulty device.

Try flashing the new Feb factory image, it will wipe all data and be a complete factory reset. Try that it will most likely fix any issue or issues.

I'm completely stock (locked and unrooted) and have done a couple factory resets. I'm on the latest build. Would it still help? If so, how do I do it?

RLPSZ said:
I'm completely stock (locked and unrooted) and have done a couple factory resets. I'm on the latest build. Would it still help? If so, how do I do it?
Click to expand...
Click to collapse
Go to the link below and follow googles instructions. Pick the feb image that is in the Marlin section and listed for Verizon and most others, unless your on rogers which the other is supposed to be for rogers which is in Canada.
https://developers.google.com/android/images?hl=en

Is you're phone from vzw or directly from Google.

RLPSZ said:
I'm completely stock (locked and unrooted) and have done a couple factory resets. I'm on the latest build. Would it still help? If so, how do I do it?
Click to expand...
Click to collapse
Oh sorry about that I looked past the part where you listed your stock and locked. Since your all factory I would call verizon and let them troubleshoot it, or if you bought through the google play store contact google cs about it, because you cant flash factory images with a locked bootloader.

Thanks for the replies! I bought it directly through Verizon and they will be sending out a replacement (in a couple weeks tho :/). I'm just wondering if anyone else with a February-delivered XL has been dealing with these issues.

RLPSZ said:
Thanks for the replies! I bought it directly through Verizon and they will be sending out a replacement (in a couple weeks tho :/). I'm just wondering if anyone else with a February-delivered XL has been dealing with these issues.
Click to expand...
Click to collapse
No problem here. Got mine last week.

Picked up mine from a corporate Verizon store a week ago and my cell connection is garbage. No service 30% of the time for no reason. Not to mention, the wifi calling keeps disabling itself. I going to try a factory wipe and reflash a Google image to see if that helps.

mycomputerisjunk said:
Picked up mine from a corporate Verizon store a week ago and my cell connection is garbage. No service 30% of the time for no reason. Not to mention, the wifi calling keeps disabling itself. I going to try a factory wipe and reflash a Google image to see if that helps.
Click to expand...
Click to collapse
Are you running a custom rom or stock ? Honestly I get better signal and performance running the rom Pure Nexus and the Elemental x kernel. If your on stock I would recommend giving Pure Nexus a try and Elemental x also.

I got my pixel xl at the beginning of feb, thru verizon, so far no problems. The pixel xl definitely doesnt get the same reception as my g3 did/does. All i can say is thank god im not having any issues with wifi calling, cuz i now get zero bars at my home. Purenexus is pretty nice, but i saw no gain in reception using it but ymmv. The only other thing is with substratum on PN, regardless which theme i choose they all set the color of links in irc for android to the same color as the background.
Sent from my VK810 4G using Tapatalk

RLPSZ said:
Thanks for the replies! I bought it directly through Verizon and they will be sending out a replacement (in a couple weeks tho :/). I'm just wondering if anyone else with a February-delivered XL has been dealing with these issues.
Click to expand...
Click to collapse
couple of weeks? how come I'm getting a replacement tomorrow and I talked to them sunday Feb 19.

alobear said:
couple of weeks? how come I'm getting a replacement tomorrow and I talked to them sunday Feb 19.
Click to expand...
Click to collapse
That's what they had told me. Though I did notice that they shipped it yesterday!

RLPSZ said:
That's what they had told me. Though I did notice that they shipped it yesterday!
Click to expand...
Click to collapse
Guess what? Verizon shipped a regular Pixel instead of an XL! Verizon has been messing up and misleading at every freaking point. This is unacceptable on so many levels. And they charged me for it!

And they no doubt will make it right. Ffs anybody or company if you prefer, can make mistakes, nobodies perfect. But, because verizon is everyones favorite whipping boy any and all oopses are just dogpiled onto. Give just a tiny bit of room for human error, believe me, they undoubtedly will do something else before long to incur everyones anger.
Sent from my VK810 4G using Tapatalk

wyrdtrtle said:
And they no doubt will make it right. Ffs anybody or company if you prefer, can make mistakes, nobodies perfect. But, because verizon is everyones favorite whipping boy any and all oopses are just dogpiled onto. Give just a tiny bit of room for human error, believe me, they undoubtedly will do something else before long to incur everyones anger.
Sent from my VK810 4G using Tapatalk
Click to expand...
Click to collapse
Of course, I understand this is a mistake and human error is normal. But, it can be frustrating for someone after ordering a phone, it taking two months to be delivered with constantly being told different dates and information each time they contact Verizon, being promised a fee being waived by one rep but then being told otherwise by another, and then again being promised it but it not being applied after multiple calls. Then, the same thing occurs with a Daydream View. Then, when the phone finally arrives, it has cellular and battery issues. Then, when a replacement phone is promised, it turns out the be the wrong one. And this is just a summary. I had to speak with Verizon multiple times for different things and the customer service to address these issues was not so great.
To update on this situation, they now tell me I need to wait for this phone to arrive and activate it, in order to return it for a refund and receive the correct replacement without charge. So I still have to wait another couple weeks to enjoy a usable Pixel XL :/

I feel your pain, ordered mine dec 15th, i also kept getting diff shipping dates, was literally on the phone cancelling my order when the shipped e-mail arrived. I didnt have a clue about the vr headset until fedex dropped it off on monday cuz i had not returned their call that previous fri.
I can understand your frustration, and tbh, had forgotten the litany of mishaps you had already gone thru, i just see and read so many gripe fests against them, and most of them are from people that are mad about the locked bootloader and they then blame them for world climate change, dropping birthrates, famine, pestilence and hillary losing. Allbeit, that last one i for one would praise them for, if it were their doing.
Anyhoo, dealing with most any corporation can and often is a PITA, but ill say this, after six years, verizon has not once failed to make it right by me. The wait has rarely been very long, but it has happened.
Hope they fix it for you sooner rather then later.
Sent from my VK810 4G using Tapatalk

I got a QB and a VS Pixel XL in February. No problems at all. I live in a rural area and both my wife and I had Samsung GS4 phones before these. I actually get a little better reception I believe.
The only problem I've run into is Trusted Voice doing its auto-disable thing, but I applied the workaround and haven't had any problems since.
My battery life is really good. I play Pokemon Go with my kids and use my phone as a hot-spot, and I can still get through a full day. Though, if I'm around a charger when the phone hits 50% I just charge it anyway.

JU57US said:
I got a QB and a VS Pixel XL in February. No problems at all. I live in a rural area and both my wife and I had Samsung GS4 phones before these. I actually get a little better reception I believe.
The only problem I've run into is Trusted Voice doing its auto-disable thing, but I applied the workaround and haven't had any problems since.
My battery life is really good. I play Pokemon Go with my kids and use my phone as a hot-spot, and I can still get through a full day. Though, if I'm around a charger when the phone hits 50% I just charge it anyway.
Click to expand...
Click to collapse
That's good to hear! It means I just received a faulty device and the replacement should work fine. I was worried that the new batch may have all come out like this since perhaps Google rushed their production by reducing time for quality checks or something like that.

I still haven't received a replacement :/ Verizon keeps sending a regular Pixel by accident.
Anyways, from the many conversations I've had with them, they eventually admitted that the February XL's have had multiple reports of issues with activation, like mine did.
Did anyone else have activation and cellular issues? If so, how are your phones doing now?

I just got update to Nougat on AT&T

Did anyone else get updated, my phone is not rooted or unlocked. so far update looks sleek, need to explore a lot.
enjoy all.

jhogal12 said:
Did anyone else get updated, my phone is not rooted or unlocked. so far update looks sleek, need to explore a lot.
enjoy all.
Click to expand...
Click to collapse
Mine is updating now but stated "security update will install?"

Looks like the N920AUCS4EQG1 update Nobarb found for all of us and referenced as unreleased a little bit back. (Thank you once again, Nobarb for all your hard work!!)
Probably just another security update. With the S8, S8+ and now the Note 8 forthcoming I can't imagine Samsung throwing us any more bones for our good old Note 5.

mattern1974 said:
Looks like the N920AUCS4EQG1 update Nobarb found for all of us and referenced as unreleased a little bit back. (Thank you once again, Nobarb for all your hard work!!)
Probably just another security update. With the S8, S8+ and now the Note 8 forthcoming I can't imagine Samsung throwing us any more bones for our good old Note 5.
Click to expand...
Click to collapse
well as I said I got Official Nougat, i will post some pics but security enhancements shows as April 13. Im sure ATT rolls these out in phases.

jhogal12 said:
well as I said I got Official Nougat, i will post some pics but security enhancements shows as April 13. Im sure ATT rolls these out in phases.
Click to expand...
Click to collapse
My apologies...I may have misunderstood what you were talking about. I just got an update yesterday and it was the QG1 update which brings in the July 1, 2017 update.
If you are not fully up to that build, keep trying for an update. You might try manually pushing your clock ahead a day if it is restricting you by the time limit.

I also received this new update and installed it. No difference in battery life or performance whatsoever... Just security updates.
Ever since my phone was updated to Nougat, it has been randomly rebooting (sometimes once a week and sometimes twice in 10 minutes). I can still use it fine but I'm honestly getting tired of finding it stuck at the "Enter PIN" (encrypted phone) screen after restarting. So I'm missing important calls without even realizing it when the phone is in my pocket. Anybody else seeing this? Suggestions welcome.
I did a cache wipe at least 10 times now and that didn't help. Don't wish to do a factory reset... It's a pain to setup android the way I like.
Thanks for any help guys.

someone can give me firmware N920AUCS4EQG1, im out side US,pls!

Sprint V30+ November 2018 security patch

Figured I'd post this since it seems to have changed a few things.
Today I got an update notification and the size seemed a bit large (~900 MB). I kinda was hoping it would be a surprise Pie update, but alas it is not. Still 8.0.0 oreo, but there are a few new things I noticed.
Calling Plus is no more. Appears to be replaced with VoLTE capabilities. Phone tried registering on the network, but I got an error. Regular calling seems to be fine.
Always on Display is different now. Similar functionality, but fewer options.

pjsnyc said:
Today I got an update notification and the size seemed a bit large (~900 MB). I kinda was hoping it would be a surprise Pie update, but alas it is not.
Click to expand...
Click to collapse
I know you're probably joking, but PIE is not going to show up as some random update. It's going to Korea carrier variants first. Maybe Q1 2019. Then everyone else. PROBABLY Q2 2019.
We will have plenty of notice about Pie, when it starts happening.
Sent via open market LG US998 V30/V30+

In any case, functionality has changed a bit. Just a heads up.

After update phone no longer has lte. Stays on 3g. Not sure why or how to fix it. Reset networks, Rebooted, updated prl and profile but nothing has fixed it so far.

jjairal said:
After update phone no longer has lte. Stays on 3g. Not sure why or how to fix it. Reset networks, Rebooted, updated prl and profile but nothing has fixed it so far.
Click to expand...
Click to collapse
Sometimes updates create issues on a phone running stable and fine with current rom and we wonder why we updated?
I bought this phone a month ago (living in India) and I find that phone is running absolutely fine, with great battery life and no issues whatsoever with August security update.
Now -- may be I will update to new update (whenever released for India phones) only after couple of weeks after going through feedback from users who updated.

I have read that lg v30 is part of google enterprise recommended which need to be regularly updated every 90 days for atleast security patch. I am from india and i got last update at end of august but till i am posting this message i didn't got any update which shows avery pathetic promise breach. Which not good for brand like lg i didn't expect from lg???

Sabarixda said:
I have read that lg v30 is part of google enterprise recommended which need to be regularly updated every 90 days for atleast security patch. I am from india and i got last update at end of august but till i am posting this message i didn't got any update which shows avery pathetic promise breach. Which not good for brand like lg i didn't expect from lg???
Click to expand...
Click to collapse
Don't be concerned on not receiving update. From what I am reading on some other threads for V30+ -- believe me, you are saved from issues in new updates released in other parts of the world for our phone. Phone is running absolutely fine with last update. We should wait for an update which will not give us any performance issues.

jjairal said:
After update phone no longer has lte. Stays on 3g. Not sure why or how to fix it. Reset networks, Rebooted, updated prl and profile but nothing has fixed it so far.
Click to expand...
Click to collapse
Strange, I havent had problems with LTE after update.

Question Google delists faulty December 2021 update for Pixel 6 & 6 Pro, preventing manual updates

Well, there you have it. For all those people who said it was my fault for flashing the December build and corrupting my 6 Pro - almost to the point of no return (to be clear, I'm not saying this was the major factor in pulling the release - but it doesn't look good imo)
Google delists faulty December 2021 update for Pixel 6 & 6 Pro, preventing manual updates
Google has now removed the Pixel 6's faulty December 2021 update from its website, to prevent it from being manually installed.
9to5google.com

Luckily I did not manually install it.
By the way, nicely done gGoolge! You've got enough information already and don't need people as guinea pigs for now.
I hope the coming up January update is workable and doable, I can not expcet an outstanding update, Google.

Alekos said:
Well, there you have it. For all those people who said it was my fault for flashing the December build and corrupting my 6 Pro - almost to the point of no return:
Google delists faulty December 2021 update for Pixel 6 & 6 Pro, preventing manual updates
Google has now removed the Pixel 6's faulty December 2021 update from its website, to prevent it from being manually installed.
9to5google.com
Click to expand...
Click to collapse
I don't think they removed it because it was corrupting people's phones.
Most likely it was due to the many complaints of connection issues people were/are having, though I didn't experience any issues... I'm currently on ProtonAOSP just to test it out.

bouchigo said:
I don't think they removed it because it was corrupting people's phones.
Most likely it was due to the many complaints of connection issues people were/are having, though I didn't experience any issues... I'm currently on ProtonAOSP just to test it out.
Click to expand...
Click to collapse
yeah that's fine. I agree. I should edit my post. I think there's multiple issues with this build. lots of reports of people corrupting their phones on this build. none for October or November, many for December. Can't say exactly why that is - but I feel there's a lot wrong with the December Build (not just connectivity issues). This is pretty huge. For Google to pull a build? I've only heard that once in the past 8 years for Google to do that.

December build works perfectly for me lol

P6P said:
December build works perfectly for me lol
Click to expand...
Click to collapse
The ancient problem. Some people are affected, others are not.
Now imagine that Googles QA consists of 10 people and all those 10 people were people with "build works perfectly for me" - so they pushed it out to the public, and kaboom.
I guess Google can only improve this process, by widening the QA across the globe (they need to test firmwares in all countries of sale + more device variations, meaning some with Google Backups, some with Backup transfers from an Iphone, from a Samsung, from an old Google etc.) - I have the feeling that they only test their firmwares on brand new devices, and we can see in this forum how many issues come from backups). Since - apparently - testing it in the USA does not help much for European network problems.

Morgrain said:
The ancient problem. Some people are affected, others are not.
Now imagine that Googles QA consists of 10 people and all those 10 people were people with "build works perfectly for me" - so they pushed it out to the public, and kaboom.
I guess Google can only improve this process, by widening the QA across the globe (they need to test firmwares in all countries of sale + more device variations, meaning some with Google Backups, some with Backup transfers from an Iphone, from a Samsung, from an old Google etc.) - I have the feeling that they only test their firmwares on brand new devices, and we can see in this forum how many issues come from backups). Since - apparently - testing it in the USA does not help much for European network problems.
Click to expand...
Click to collapse
Yes sure you are right but it's kinda weird what they did there.

P6P said:
December build works perfectly for me lol
Click to expand...
Click to collapse
the thing is, to pull an update is kinda crazy. and the issue seems to mostly be in EMEA (and some parts of North America). this has to be directly related to not using Qualcomm. It sucks, but its true.
This isn't a small company we're talking about here. They need to do better. MUCH Better. Look, I've used pixels from the beginning, and will always, but they still need to do better.

Hmm ... then I'm thinking ... If I were Google: "Maybe we should remove the manual upgrade possibility completely" in the future ...

Alekos said:
the thing is, to pull an update is kinda crazy. and the issue seems to mostly be in EMEA (and some parts of North America). this has to be directly related to not use Qualcomm. It sucks, but its true.
This isn't a small company we're talking about here. They need to do better. MUCH Better. Look, I've used pixels from the beginning, and will always, but they still need to do better.
Click to expand...
Click to collapse
Yeah and that's even more weird now because im using EMEA and also live in that region. Just crazy what they did there.

foobar66 said:
Hmm ... then I'm thinking ... If I were Google: "Maybe we should remove the manual upgrade possibility completely" in the future ...
Click to expand...
Click to collapse
Oh no lol. We won't have anything to play with then haha

foobar66 said:
Hmm ... then I'm thinking ... If I were Google: "Maybe we should remove the manual upgrade possibility completely" in the future ...
Click to expand...
Click to collapse
they pulled the update due to the connectivity issues. Google will never (and shouldn't ever) remove the manual upgrade process. It had nothing to do with that process anyhow. it was the build specifically that was the issue. It could have happened to any manufacturer. Google removing the ability to manually update has no bearing on this.
What would happen if users needed to roll back an update? Or they don't have internet? Or the ota update doesn't work? No way Jose

This is an extreme move. Anyone who's flashing the December build manually should be tech savvy enough to flash the November radio if they're having network issues. Everyone should have the ability to choose what build they're running - I, for one, couldn't deal with all the November bugs again.
If they wanted to limit novice users from flashing manually, they could have removed the ability to flash Dec build from the Android Flash Tool - all that pulling the build does is leave the people already on Dec build with no backup plan in case of bootloop, etc.
I still can't wrap my head around why they haven't released a minor OTA update & carrier services fix to resolve the widespread radio issues - they could have negated all of this with a quick fix in mid December to tide everyone over until January, but instead are making people wait over a month for the next build to fix a simple problem.

DanielF50 said:
This is an extreme move. Anyone who's flashing the December build manually should be tech savvy enough to flash the November radio if they're having network issues. Everyone should have the ability to choose what build they're running - I, for one, couldn't deal with all the November bugs again.
If they wanted to limit novice users from flashing manually, they could have removed the ability to flash Dec build from the Android Flash Tool - all that pulling the build does is leave the people already on Dec build with no backup plan in case of bootloop, etc.
I still can't wrap my head around why they haven't released a minor OTA update & carrier services fix to resolve the widespread radio issues - they could have negated all of this with a quick fix in mid December to tide everyone over until January, but instead are making people wait over a month for the next build to fix a simple problem.
Click to expand...
Click to collapse
They just needed to replace the Dec radio.img with Nov radio.img and that's all. Like you said... That could be the mid dec build then

P6P said:
They just needed to replace the Dec radio.img with Nov radio.img and that's all. Like you said... That could be the mid dec build then
Click to expand...
Click to collapse
but pulling the build - means there's much more to this. it must. On the december build, I could force a Corrupt message simply by turning off location access to the "ImsSetting" service in the Privacy menu. November build it's fine.
I suspect there is something more going on here

Alekos said:
but pulling the build - means there's much more to this. it must. On the december build, I could force a Corrupt message simply by turning off location access to the "ImsSetting" service in the Privacy menu. November build it's fine.
I suspect there is something more going on here
Click to expand...
Click to collapse
Oh ok didn't know that. I have just heard about the data connection problems.

P6P said:
Oh ok didn't know that. I have just heard about the data connection problems.
Click to expand...
Click to collapse
yeah I think there's more to it. obviously I can't prove it. but October/november there weren't any "corrupt" messages appearing. December? tons on reddit and here...

Alekos said:
yeah I think there's more to it. obviously I can't prove it. but October/november there weren't any "corrupt" messages appearing. December? tons on reddit and here...
Click to expand...
Click to collapse
Dunno. I had a few issues with October and November build but December is fine. No issues at all.

P6P said:
Dunno. I had a few issues with October and November build but December is fine. No issues at all.
Click to expand...
Click to collapse
yeah I didn't have issues either... October, November... then just flashed December's build and got the corrupt message. when I saved it, it was fine, but it was a close one. Almost couldn't get it back. nothing would work... bootloader, ota, factory reset etc etc.... finally flashing original build from October, did the trick.
but it's been great... no issues with signal, fingerprint, battery life....all good

Alekos said:
yeah I didn't have issues either... October, November... then just flashed December's build and got the corrupt message. when I saved it, it was fine, but it was a close one. Almost couldn't get it back. nothing would work... bootloader, ota, factory reset etc etc.... finally flashing original build from October, did the trick.
but it's been great... no issues with signal, fingerprint, battery life....all good
Click to expand...
Click to collapse
Wait you mean corrupt message while updating? Never had that.

Question Verizon calling problems

Lately, I have been having trouble calling and receiving phone calls. I often get an exclamation point next to the cell phone signal icon. Sometime the exclamation goes away. Other times, I get a message that the cellular network is not available.
I tried the following:
Reseating the SIM
Resetting the network settings
Toggle airplane mode
Switch Preferred network between LTE and 5G
Results are inconsistent, so I am coming the XDA to see if others have seen this or have suggestion for a fix.
EDIT: Seems to be a common problem, with no clear fix.
https://www.reddit.com/r/GooglePixel/comments/qkag56
thanks

I had the same problem on Orange network in France but the last android 13 beta (3.2) solved the problem.

swieder711 said:
Lately, I have been having trouble calling and receiving phone calls. I often get an exclamation point next to the cell phone signal icon. Sometime the exclamation goes away. Other times, I get a message that the cellular network is not available.
I tried the following:
Reseating the SIM
Resetting the network settings
Toggle airplane mode
Switch Preferred network between LTE and 5G
Results are inconsistent, so I am coming the XDA to see if others have seen this or have suggestion for a fix.
EDIT: Seems to be a common problem, with no clear fix.
https://www.reddit.com/r/GooglePixel/comments/qkag56
thanks
Click to expand...
Click to collapse
The last option you have before warranty is to re-flash the device. It's worth a shot... When flashing, be sure to enable wipe and force flash partitions (by hitting the pencil for advanced options located on the flasher page).
Google's web flash tool is here.

mine has been doing the same, seems to be really bad last few weeks too. I was planning to do a full reset and see what that does. Good to now about the A13 beta, as that was my next step if full factory reset/flash doesn't help. Thanks for this thread.

hpower1 said:
mine has been doing the same, seems to be really bad last few weeks too. I was planning to do a full reset and see what that does. Good to now about the A13 beta, as that was my next step if full factory reset/flash doesn't help. Thanks for this thread.
Click to expand...
Click to collapse
The cellular service has definitely gotten worse in the last few weeks. Maybe the June update broke something.
Hard for me to image that I factory reset would help. Can you let us know how that goes for you?
Let's hope the cell service gets better with the July update.

will do. I'm gonna have to do something. Lost connection 3 times today alone. Annoying.

I'm going to flash the modem files from Android 13 beta to the June update. Someone with a P6 said that this worked for them.
I just ran the following and see an immediate improvement!
fastboot flash radio radio-raven-g5123b-102852-220609-b-8701566.img
EDIT: I spoke too quickly. Still getting "!" and "mobile network not available"
EDIT2: Since this problem appears to have started for me with the June update, I am going to flash the May update modem file and see how that works. Just ran "fastboot flash radio radio-raven-g5123b-97927-220225-b-8226700.img" Stay tuned.

swieder711 said:
I'm going to flash the modem files from Android 13 beta to the June update. Someone with a P6 said that this worked for them.
I just ran the following and see an immediate improvement!
fastboot flash radio radio-raven-g5123b-102852-220609-b-8701566.img
EDIT: I spoke too quickly. Still getting "!" and "mobile network not available"
EDIT2: Since this problem appears to have started for me with the June update, I am going to flash the May update modem file and see how that works. Just ran "fastboot flash radio radio-raven-g5123b-97927-220225-b-8226700.img" Stay tuned.
Click to expand...
Click to collapse
Unfortunately, I don't think that's the issue. The radio sucks and no amount of software updates or down-dates will fix it. If you need it for work then what I would do is sell it and buy a different phone until they come out with a new device that is as good as the P5. I can be without signal and data for close to 15 minutes while my wife and her P5 never once lost it. Once the ! hits the signal bar it will take me a minimum of 5 - 10 minutes to come back unless I reboot the phone. Then it's only about 5. If I needed it for business or critical functioning I wouldn't be on this forum any longer. Oh yeah, other than that the phone is great. Well... other than mediocre battery life and a FPR that will never success after a shower or swim. And I do mean never.

I decided against a full wipe/install of June update, and just went for the A13 beta 3. Flashed it via the android flash tool, then rooted with magisk. Setting up apps and things now, so I'll report back when I know more. I wanna love this phone, but it has been hard. Hoping this is better. I'll try to probably manage with this until the 7 comes out.

also for what its worth, swift backup is nice. Restoring my apps and data now, the few I have tested all work as if I didn't update/wipe my phone. Really makes it nice

hpower1 said:
also for what its worth, swift backup is nice. Restoring my apps and data now, the few I have tested all work as if I didn't update/wipe my phone. Really makes it nice
Click to expand...
Click to collapse
Also a fan of swift backup

hpower1 said:
I decided against a full wipe/install of June update, and just went for the A13 beta 3. Flashed it via the android flash tool, then rooted with magisk. Setting up apps and things now, so I'll report back when I know more. I wanna love this phone, but it has been hard. Hoping this is better. I'll try to probably manage with this until the 7 comes out.
Click to expand...
Click to collapse
Looking forward to hearing about your experience with A13 and if it improves your cellular service.

I would say on my experience, Beta 3 has gotten better but should've been fixed months ago before it was released. I am going to wait a while before I got buy another phone in general

biggiesmalls657 said:
I would say on my experience, Beta 3 has gotten better but should've been fixed months ago before it was released. I am going to wait a while before I got buy another phone in general
Click to expand...
Click to collapse
Are you getting reliable cellular connections with Verizon using Beta 3? Do you ever get the exclamation point of no service?

swieder711 said:
Are you getting reliable cellular connections with Verizon using Beta 3? Do you ever get the exclamation point of no service?
Click to expand...
Click to collapse
Maybe once in the last week

Getting the same here. Last few weeks have been unbearable. Was just down in the Smoky Mountains on my motorcycle for a week. Spotty coverage is to be expected. But I would get back to town and have to reboot to get coverage again. Still it often went back to the explanation mark after reboot.
This modem is crap, I may break out the Note 20 my kid gave me. I will hate it, but at least I can make calls and text.

TonikJDK said:
Getting the same here. Last few weeks have been unbearable. Was just down in the Smoky Mountains on my motorcycle for a week. Spotty coverage is to be expected. But I would get back to town and have to reboot to get coverage again. Still it often went back to the explanation mark after reboot.
This modem is crap, I may break out the Note 20 my kid gave me. I will hate it, but at least I can make calls and text.
Click to expand...
Click to collapse
And how we tried. It's just a shame they released this device with hardware that is not useful for network connectivity. And how do we migrate to a P7 after this without making sure they didn't screw up again? I'm at a loss at this point. I'll give it until A13 final and then sell it if nothing changes. I just don't know where to turn but to me the iPhone 13 6" might be it sorry to say. I just can't deal with this crap much longer. Sucks huh?

well after today, I would say its better. But time will tell. Went out several times to different places and I never lost connection. I'll keep you all updated. I will say that on the beta the phone feels much faster and the FP reader seems better too.
I keep saying that I love this phone, and hate it at the same time.

bobby janow said:
And how we tried. It's just a shame they released this device with hardware that is not useful for network connectivity. And how do we migrate to a P7 after this without making sure they didn't screw up again? I'm at a loss at this point. I'll give it until A13 final and then sell it if nothing changes. I just don't know where to turn but to me the iPhone 13 6" might be it sorry to say. I just can't deal with this crap much longer. Sucks huh?
Click to expand...
Click to collapse
Just wondering if you've tried the latest beta using the flash tool and choosing the options wipe and force flash all partitions (which reinstalls all the firmware on the phone).
It would be super frustrating to have signal issues. I've also heard some users who still had issues after re-flashing, were able to get replacements from Google Support.

Alekos said:
Just wondering if you've tried the latest beta using the flash tool and choosing the options wipe and force flash all partitions (which reinstalls all the firmware on the phone).
It would be super frustrating to have signal issues. I've also heard some users who still had issues after re-flashing, were able to get replacements from Google Support.
Click to expand...
Click to collapse
Not yet. I was going to wait for the fall release of A13 before I wiped and finally gave up. It's not often enough, although frustrating, that I have to rely on a reboot to restore connectivity since mostly I've learned to just look the other way, shake my head and wait the 15 minutes. The point being they should never have released this last October with all the fpr issues and radio malfunctioning. This has been ongoing for 9 months already in various iterations. I don't think any other device has these issues other than the P6 series.