I did since 2 days now and it didn't fix my signal issue.
Basically I tried everything by now from disabling 2g, changing apn, disabling dual sim, resetting the phone, resetting the network, etc
The weird thing is that it shows exclamation mark as no data connection but some apps still connect like whatsapp, instagram, etc while for example Youtube wouldn't connect unless i had it open before switching from wifi to mobile data and then toggling airplane mode few times.
Only 3G available here, overall the only thing i have issue with is the mobile data connection that keeps disconnecting and going offline all the time, while making calls and receiving calls work fine.Yes, I noticed the same. Sometimes browsing with Firefox works for me, but I can't make a phone call.
Beside that I had problem that I can not disable 2G, because my carrier don't support 2G anymore.
But you wrote that you tried to disable 2G. So you use 3G for phone calls and you still have problems with "no network"?
Strange, because in our country people with 3G network are not reporting these errors.
Modem is not the same. P6P has Samsung Shannon 5123B, P7P has Samsung Shannon 5300G. This modem hasn't even been used in a Samsung device yet, it launched with the Pixel 7 series.If you have these problems, exchange phone. As others have said, P6P had same problem with some phones and not with others. Believe modem is the same, so don't wait. I suffered for a year and finally gave up and upgraded just to get rid of the problem phone I had.
What you mean with re-flash radio?So I got a new 5G SIM for the P7P. My previous 4G SIM was getting 200Mbps d/l. The new 5G SIM gets maybe 30 if I am lucky....
Yesterday, I woke up and my phone was able to make connections to Verizon but there was no sound whatsoever. Nothing from my mic and nothing thru the ears.......Verizon couldnt figure it out, and blamed it on a large outage here in Los Angeles. I need to reflash my radio to get back to normal.
Maybe that will assist someone....try to reflash the radio.
No magic, you flash the radio with Fastboot. fastboot flash radio radio_file_nameWhat you mean with re-flash radio?
There is a magic where you just re-flash radio firmware?
Thanks, if you found that custom radio firmware is better, please share some notes here.No magic, you flash the radio with Fastboot. fastboot flash radio radio_file_name
Its not a custom radio, I just reflashed the radio from the standard Google package. Reflashing fixed my problem, so figured maybe it might help someone else....GL!Thanks, if you found that custom radio firmware is better, please share some notes here.
Root required? And what you mean with standard google package? we are on standard build - factory installed, or updated with November OTA.Its not a custom radio, I just reflashed the radio from the standard Google package. Reflashing fixed my problem, so figured maybe it might help someone else....GL!
Root is not required to flash with Fastboot. However, an unlocked bootloader is required.Root required? And what you mean with standard google package? we are on standard build - factory installed, or updated with November OTA.
Good to know, I was working with older information that obviously was wrong. As I did type, so far so good. Have had one instance of losing signal while using Google Maps in an area I know to be well covered, but to early to say it was anything but a one-off anomaly.Modem is not the same. P6P has Samsung Shannon 5123B, P7P has Samsung Shannon 5300G. This modem hasn't even been used in a Samsung device yet, it launched with the Pixel 7 series.
What version firmware of radio file did you get? Please let me know, thanksIts not a custom radio, I just reflashed the radio from the standard Google package. Reflashing fixed my problem, so figured maybe it might help someone else....GL!
I hope that beta radio file get released in the December update. I'm getting way too many exclamation points on Verizon.Flashed the beta and it seems to have improved the issue for me. Got the exclamation mark yesterday and instead of staying that way my device switched to LTE. Then moments later it reconnected to 5G whereas on stable it would just stay without data until the airplane toggle. Also, on the beta on Verizon I'm getting 5G UWB more reliably as well as inside. On stable I would rarely get 5G UWB inside at my home.
I flashed the beta radio when I was on the November build and it was still the same for me. They did mention a fix they specifically did in the beta in regards to UW. So if everything or majority of the fixes from 3-3.1 will make it into the Dec build it'll help a lot.I hope that beta radio file get released in the December update. I'm getting way too many exclamation points on Verizon.
Which version you mean by A2 ? This one 13.0.0 (TD1A.220804.009.A2, Oct 2022)Witch rom version you have ?
Same problem.
Just switch to a2 rom and lock update.
Problem solved
That would be a great solution to stay out of beta...I am tempted to install the latest Beta modem file to my P7P phone that is running the January update.
Has anyone tried this combination?
Great.I just installed the Beta 2 modem file on top of the stable January update. I will report back if there is any noticeable change.
I flashed the beta radio when I was on the November build and it was still the same for me. They did mention a fix they specifically did in the beta in regards to UW. So if everything or majority of the fixes from 3-3.1 will make it into the Dec build it'll help a lot.I hope that beta radio file get released in the December update. I'm getting way too many exclamation points on Verizon.
I don't know if this will help, but...I live in Boston metro area with abundant LTE/5G coverage, but drive through two nearly dead zones, each of them lasts just a few seconds. My previous phone would not stop YouTube playback going through those areas. My Pixel 7 Pro loses connection for ~5 minutes completely and then reconnects via EDGE even though strong 5G is available. I have to toggle the airplane mode for it to connect to the correct network.
I'm on Mint/T-Mobile and this has been happening every day. Is it a software bug or is my Pixel defective? Thanks for any ideas, I still have a week to decide if I should return it![]()