yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] akulp:
As I said , I'm also from unsupported contry, Slovenia. I and @cvick already found some things and I also made report to our biggest (national) operator.

What I found in last 3 days is that I don't have anymore missed calls or problems with "no network".

I set "preffered network type" to 4G and my operator turned off 5G/VoLTE/VoWIFI on my number from their side.

They said this could be a potential problem because the network is pushing VoLTE/VoWIFI but phone don't have support for it. The same for 5G.

But I still get "crackling" in a call after 10+ min long calls.
[Google Pixel 7 Pro] jcrutchvt10:
I've found dialing *#*#4636#*#* and selecting all the network options has helped me. It was limited to only NR/LTE/TDWCDMA by default for some reason on the second beta. Haven't had an issue since doing that and updating sim manager.
[Google Pixel 7 Pro] enyaj:
Could this be coz of Samsung made Tensor chip or no connection to that? Just curious 😁
[Google Pixel 7 Pro] akulp:
You don't have issue with "crakling" or "no network"?

But this dialed number is only supported by your carrier as I see. I thought this is option connected to the phone.

Where did you get last SIM manager version? apkmirror?

I have D.2.1.473171966
[Google Pixel 7 Pro] superchesser:
I'm in Spain, which is an officially supported country, I have no VoLTE with the Pixel 7 Pro (had it for 4 years on my previous phone), network drops seem solved for my in the latest beta. But I'm getting 20-25% battery usage from mobile network, anyone else getting such high numbers?
[Google Pixel 7 Pro] jcrutchvt10:
I used to have those issues until I upgraded SIM Manager from apkmirror and made those changes in the dialer menu. Since then, no problems. If the 4636 doesn't work for you try *#*#46368676#*#*
[Google Pixel 7 Pro] cvick:
It's *#*#4636#*#* not #*#*4636#*#*
[Google Pixel 7 Pro] jcrutchvt10:
good catch thanks!
[Google Pixel 7 Pro] akulp:
So can you confirm you have the same SIMm version as me? D.2.1.473171966

I also had "NR/LTE/TDSCDMA" when I made first look.

But since we have no 5G support I selected 4G as preferred net. type (settings->Network->SIM) and than if I look into "*#*#4636#*#*" menu I got: GSM/WCDMA/LET(PRL)

So you chosen "NR/LTE/TDSCDMA/CDMA/EvDo/GSM/WCDMA" from drop down menu and you're from "5G unsupported country"?
[Google Pixel 7 Pro] tensux:
I am using google fi (t-mobile) on my pixel 6 I always get 5G UC (wide band), on the pixel 7 pro I am only getting 5G NSA which is much slower. I wonder if there is a modem issue on this device.
[Google Pixel 7 Pro] Lughnasadh:
I'm using Mint Mobile (T-Mobile) and am able to use 5G UC on my Pixel 7 Pro, for what it's worth.
[Google Pixel 7 Pro] tensux:
thanks, I will have to figure this out then.
[Google Pixel 7 Pro] swieder711:
When I look at phone info from *#*#4636#*#*,

I see Cell Info Refresh Rate = Disabled.

That seem strange to meet. Choices are Immediate, Min 5s, 10s, and 60s.

How is your phone set for this? I am on Verizon.
[Google Pixel 7 Pro] akulp:
Disabled as well.

I don't think you should mess with those options. :)
[Google Pixel 7 Pro] omf05:
Since I've owned my phone for a week now I've lost complete signal twice. Seem to stay around one bar in my home. After turning off 2g I've definitely seen an improvement. Still don't like the idea of having to do that.
[Google Pixel 7 Pro] EtherealRemnant:
All that does is update the tower polling info on that screen. It won't do anything for reception.
[Google Pixel 7 Pro] zetsumeikuro:
https://www.reddit.com/r/GooglePixel/comments/ymysuk
this has worked for some but only caveat is one sim active at a time.
[Google Pixel 7 Pro] akulp:
I did some troubleshooting to diagnose why I kept losing network. I discovered it was only when the phone went to a pure 5G band in SA mode I found that this was the only band that I could not seem to connect to.

But as I get this post this is only (maybe) a solution when you have 5G signal. So, just for "supported countries".
[Google Pixel 7 Pro] rusinov:
Hello,

Coming from not supported country - Bulgaria, so no VoLTE or 5G. Huge signal issues, even after November update on Pixel 7. Almost most of the calls at home are dropping first time, so I have to call again. The signal at home is not perfect, but was always enough to do usual cellular calls, on my last phone Pixel 5.

I'm not cellular expert, but I found that during standby Pixel 7 is refreshing cell info only for LTE. In compare with Pixel 5, it is refreshing LTE cell info, but also 3G cell info (WCDMA). Not sure whether this is the issue, but Pixel 5 never drops calls at home, Pixel 7 drops each call randomly from first 3-4sec to the 40-50sec, at some cases it is drooping the call at 2mins.

Based on my experience, Google is doesn't care about cases at bug tracker portal, the internal community is full of "diamond" experts who blame the others that they have to check with their service provider, but not Google, chat and phone support representatives are also useless.

The black screenshot is from Pixel 5, the white is from Pixel 7, they are one to one at my desk.
[Google Pixel 7 Pro] rosuvladut:
Did someone with signal issues tested the QPR beta?
[Google Pixel 7 Pro] akulp:
I just signed in to QPR beta. I'll try to upgrade and report in few days.
[Google Pixel 7 Pro] mahdiattieh:
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.
[Google Pixel 7 Pro] akulp:
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.
[Google Pixel 7 Pro] mahdiattieh:
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.
[Google Pixel 7 Pro] Yensid eno:
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.
[Google Pixel 7 Pro] EtherealRemnant:
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.
[Google Pixel 7 Pro] cmh714:
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.
[Google Pixel 7 Pro] rusinov:
What you mean with re-flash radio?

There is a magic where you just re-flash radio firmware?
[Google Pixel 7 Pro] cmh714:
No magic, you flash the radio with Fastboot. fastboot flash radio radio_file_name
[Google Pixel 7 Pro] rusinov:
Thanks, if you found that custom radio firmware is better, please share some notes here.
[Google Pixel 7 Pro] cmh714:
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!
[Google Pixel 7 Pro] rusinov:
Root required? And what you mean with standard google package? we are on standard build - factory installed, or updated with November OTA.
[Google Pixel 7 Pro] swieder711:
Root is not required to flash with Fastboot. However, an unlocked bootloader is required.
[Google Pixel 7 Pro] Yensid eno:
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.
[Google Pixel 7 Pro] tungsteinbk:
What version firmware of radio file did you get? Please let me know, thanks
[Google Pixel 7 Pro] zetsumeikuro:
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.
[Google Pixel 7 Pro] swieder711:
I hope that beta radio file get released in the December update. I'm getting way too many exclamation points on Verizon.
[Google Pixel 7 Pro] zetsumeikuro:
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.
[Google Pixel 7 Pro] xpact:
Which version you mean by A2 ? This one 13.0.0 (TD1A.220804.009.A2, Oct 2022)
[Google Pixel 7 Pro] xpact:
I did same sh*t. No improvement.

The December factory stock update seems to have improved the things at least for me. 13.0.0 (TQ1A.221205.011, Dec 2022)

I had installed OTA update but I intend to wipe it clean and do the factory image. I may try QPR2 when available and compare which is better.
[Google Pixel 7 Pro] tom beckett:
Yes this
[Google Pixel 7 Pro] Ytujok:
The update also does not really solve the problem of connection?
[Google Pixel 7 Pro] xpact:
It did solve mine for now or at least made the things better I did not see the exclamation mark ("!") next to my signal. And now I am able to make phone calls even if I stop the Mobile Data, I was not able before. I have tried the beta QPR 1 but it was not good. I did a wipe and clean install of the December update and it is fine now , how ever I have stayed only in urban areas and I have suspicion the reception is not that good compared to Pixel 2 XL for example.
[Google Pixel 7 Pro] drmoeed:
Well, my problems started after the OTA update of latest QPR1 with December patch ...

Now in an extreme agonizing situation, missing calls, no LTE ...

Have performed all tantrums of 2G, 5G and DSDA blah blah ...

Nothing working ...

Should I downgrade to A1 update ? What I perceived reading all this thread.
[Google Pixel 7 Pro] noodles222:
HI all,

FOr sure there is a problem with December Update. I am from Slovakia, I have tried two brand new Pixel 7s.. Once it is on TD1A.220804.009.A2, connection and calls are OK.. once you install December update, its over. So far I stay with TD1A.220804.009.A2 and via developer options I have blocked installing automatic updates.
[Google Pixel 7 Pro] drmoeed:
Exactly ditto.

My situation.

I also clean flashed this A2 built and turned off the auto-updates.

And now I have absolutely NO issues regarding signals drop or missing any calls.

QPR1 with December security patch crashed my phone.
[Google Pixel 7 Pro] Ytujok:
I managed to use the latest firmware TQ1A.221205.011 I changed the region of the radio station from Europe to Japan. *#*#4636#*#* - information about the phone - three dots at the top - select a radio station - press Japan. Then I turned off 2g, set the priority type of connection to LTE, now everything is in order with calls, it helped me.
[Google Pixel 7 Pro] kahaips:
I have T-Mobile service and recently added a 2nd line on Tello, and have been keeping track of the various frequency bands the phone connects on. Tello's connectivity mimics TMO connectivity. I use the Network Cell Info app but one can use its Lite version, too. On the Pixel 7 Pro, when I toggle the Use SIM button under the SIMs menu, it connects on 5G band 2, eventually switches to 41, then to band N1. What's important here is that both bands 2 & 41 are shown as NSA (Non-Stand Alone) bands on the Network Cell Info app and N1 is a SA (Stand Alone) band. I see 5G UC next to the signal bar on both the NSA bands. However, as soon as the phone switches to band N1, it loses network connectivity and I see the ! sign on the signal bar. I still see 5G UC next to the signal bar but there is no network connectivity.

My gut feeling is that T-Mobile is restricting access to SA bands for MVNOs like Tello and Mint. Given that their service is very inexpensive, TMO may be reserving its SA bands for MVNOs that charge more for their service than Tello does. The natural tendency for Pixel 7 Pro is to move to SA band where available and therein may lie its compatibility problem with Tello. The good thing is that if one forces phone to stay on LTE, one gets LTE+ connectivity on the Pixel 7 Pro. I haven't tested the speeds on LTE+, though.

I also have a TMO Samsung Galaxy Flip 4 for my TMO service. Since the phone is locked to TMO, it won't allow the use of Tello SIM in it. I know I can try a temporary unlock on it, then put the Tello SIM to see if its behavior is similar to what I see on the Pixel.

I am not sure if anyone has observed and done what I have but hope this leads to some understanding of the problem. I am going to report this to Tello to see if they will work with TMO to allow use of SA bands on the Pixel.
[Google Pixel 7 Pro] EtherealRemnant:
Yeah it's been known since May that it's an SA problem.

Interesting the n1 though because that's not a band we use in the states.

You can try this to fix your Tello problem. Don't change the MVNO value that populates when you select GID for the type as it's not the same for Tello as it is for Mint but people have been reporting this to fix their connectivity.

https://www.reddit.com/r/mintmobile/comments/zeev10
[Google Pixel 7 Pro] kahaips:
Yes, tried this. It was recommended by Tello support but the result is the same as I have described in my post. At this time, I took Tello's service more for multifactor authentication as some websites do not allow using Google Voice number as an option for it; I do not want to use my TMO cell number for that. So, as long as I am able to send and receive SMS, I am fine restricting the phone to LTE connectivity.

Yes, I am aware that we do not use band N1 here in the US. Why it shows-up in the Network Cell Info app is beyond me!

And, seriously, thank you. I did not realize that it was a known SA problem. AT least we are on the same page with that.
[Google Pixel 7 Pro] gato72:
I read that the new QPR2 beta has a new modem update as well.

Has anyone noticed any improvements in reception?
[Google Pixel 7 Pro] drmoeed:
Really ?
[Google Pixel 7 Pro] EtherealRemnant:
Tello seems unwilling to admit that it's an SA issue but on my OnePlus 9 I was able to completely resolve it by using the developer option they give in OOS12/13 to switch the 5G network mode from NSA/SA to just NSA. It was just a hunch as I noticed that my signal would be much stronger than normal indoors when the data would drop and that's suggestive of being on n71.

Interestingly, converting my Tello pSIM to eSIM completely shut off SA on my Pixel 7 Pro so I haven't had to deal with the problem again. Unfortunately this didn't work for everyone who tried it or it only worked for a short period of time before it stopped working again.

I wish Google would just give us control over the 5G network mode.
[Google Pixel 7 Pro] kahaips:
Just saw this article:

Android 13 QPR2 Beta 1: Google Pixel 7 and Pixel 7 Pro will support T-Mobile 3CA

In their next major Android update, Google will be updating the Pixel 7 and Pixel 7 Pro with better support...

9to5google.com

Applying update as we speak. Maybe this will help but if Tello doesn't support it, at least I know my TMO connection will be solid.
[Google Pixel 7 Pro] kahaips:
Ok, good news to report. Android 13 QPR2 Beta 1 now has no apparent 5G issues. It works; no more exclamation sign on the signal bar.

Another feature? Vo5G option now available in SIM Settings.

Hopefully, this is the start of something good!
[Google Pixel 7 Pro] ciobi:
Indeed, NetMonitor seems good enough to detect disconnects, but one issue I have with it is that I can't figure out how to make it sound an alarm continuously once the phone is disconnected (in case I'm in a noisy area and don't hear it the first time). So I also published my own app, which is much simpler - https://play.google.com/store/apps/details?id=tech.ciobi.cellchecker

All it does is beep if the cell provider got disconnected, so you can start enabling and disabling airplane mode.
[Google Pixel 7 Pro] itiskonrad:
Just confirming that December update ruined my signal as well. I went from having to reset my connection daily on my 6 pro to never having to do it once on my 7 pro, and back to having to reset it DAILY after the December update. It's like I'm back on my 6 pro 😭😭😭
[Google Pixel 7 Pro] swieder711:
So odd. I think my cellular reception improved with the Dec update. Seems like that I am seeing fewer exclamation points.

With my Pixel 6P, doing a fresh install versus keeping the user data intact, improved my cellular performance. I might try that with my P7P.
[Google Pixel 7 Pro] bocabakra:
its really lame ass stuff from google, now i'm restarting my 7P whenever I'm moving out of wifi zones. its really so bad that within a 100 meter zone i'm disconnected from cellular. Restarting is the only thing which works. feels like i'm back with some Windows 98 shizz
[Google Pixel 7 Pro] kenbrownstone:
Mine has gotten worse..Use on TMobile
[Google Pixel 7 Pro] Lughnasadh:
My mobile connection seems the same on QPR2 Beta 1 compared to QPR1 stable. Have not really had any problems with reception since I got the phone. Using T-Mobile via Mint Mobile.
[Google Pixel 7 Pro] ciobi:
In the last several days things seem to have been relatively OK for me, for no clear reason. (I installed the latest Android update yesterday, but the improvements could be seen earlier.)

Anyway, I don't know how long this will last (I had no issue the first 3 days after I bought the phone either), so here's what I settled on:

Enabled and configured voicemail so if somebody tries to call me while I have no signal, I get a text message with the missed calls when the signal is restored, even if a caller didn't leave a message.

Have an app to constantly monitor my connection. I wrote my own, Cell Connection Monitor, to actually make sure that a connection is available. There are alternatives, but I couldn't find them at first, and mine has some advantages. One alternative is NetMonitor, which does a lot more than my app does, but seems to rely on the phone broadcasting changes in it "connected" state, and the phone doesn't always know when that happens. So there are times when NetMonitor thinks things are OK while they aren't.
[Google Pixel 7 Pro] akulp:
Interesting...

I used NetMonitor at the beginning as well but than I uninstalled it when I was sure it's not phone/carrier problem...

Is it possible, that your app somehow force mobile to have signal always alive?
[Google Pixel 7 Pro] ciobi:
The main thing my app does is periodically make HTTP requests to google.com on the cellular network, ignoring WiFi. I've set the ping interval to 40 seconds, which might help keep the signal alive, I'm not sure. Anyway, in the last few hours I got plenty of disconnects, with the phone placed on the same desk, in the same location as ever.

I posted the relevant code at https://gist.github.com/mciobanu/0bdaf19ce0ee36c63ac003039dd789c2
[Google Pixel 7 Pro] jblparisi:
https://www.reddit.com/r/GooglePixel/comments/1076hz6
[Google Pixel 7 Pro] akulp:
But then you were unreachable then or did the phone made connection back by itself?
[Google Pixel 7 Pro] ciobi:
I'm quite sure I was unreachable, but these were short disconnect episodes, of around 10 seconds, so I couldn't really check. Come to think of it, most disconnects in the last week or so were like this, while a month ago quite a few were longer than 3 minutes, and I could call from a different phone to make sure it was unreachable.

Anyway, it's been a week or so since I didn't turn airplay mode on and off. The connection comes back pretty quickly by itself. (Of course, other phones with the same provider in the same location don't lose the connection to begin with.)
[Google Pixel 7 Pro] akulp:
Thank you for your explanation.

I'l try your app and I'll come back with a report in a week. :)
[Google Pixel 7 Pro] jblparisi:
May I ask who is your carrier and what plan do you sub?
[Google Pixel 7 Pro] ciobi:
Sure.

I'm in Romania, which is not supported by Google, so there's no 5G, VoLTE, VoWifi for now, though carriers might add these at some point. My main carrier is Vodafone, but I put the SIM back in the old phone (so I could have a reliable phone where I could be reached) and got a cheap pay-as-you-go SIM from Digi.Mobil to have something to play with on the Pixel. Both plans are 4G and I don't care much about them beyond that. The Vodafone plan includes VoWifi for sure.

The Pixel behaves about the same with both carriers: disconnects from time to time, in particular when somebody tries to call me, then it usually connects back on its own after a few minutes at most, or after turning on and off airplane mode, perhaps several times.
[Google Pixel 7 Pro] akulp:
So you use 4G. But when you're in a call do you use 3G or 2G?

Because my carrier (Slovenia, also unsupported c.) don't have 3G anymore so my signal drop from 4G to 2G when call is connected.

And I noticed that your app recognize that as a network disconnect and I get alarm during call. :)
[Google Pixel 7 Pro] ciobi:
In Preferred network type I asked it to use 3G, hoping it would work better. But I guess this is just a suggestion, and it uses whatever it wants. I don't know how to force something. Now I switched to LTE and seems the same. My app detected a brief disconnect when I called once, but not the other times or after I answered. I wanted to make a change to allow you to ignore these brief disconnects anyway.
[Google Pixel 7 Pro] akulp:
Yesterday I had about 4 disconnects, I was unreachable until phone restart. App was active, signal loss was detected but it didn't get back on without a restart.

I thought that maybe the application would miraculously help when setting up the signal, but unfortunately it obviously doesn't work that way. :) I just noticed that the Android Beta QPR2 should have a fix for the modem and maybe that will help...

Pixel 7 & 7 Pro 'No network' or 'No service' (connectivity) issue

Some Pixel 7 and 7 Pro users are reporting 'No network' or 'No service' connectivity issues, but Google is allegedly aware.

piunikaweb.com
[Google Pixel 7 Pro] groverXIII:
I've been having ongoing issues with connection loss since getting the phone, and since getting the latest beta update a few days ago things seem more stable. The handful of times the connection has dropped, it's reconnected a lot faster. I'm going to need to test it further, but it definitely seems like things are looking up.
[Google Pixel 7 Pro] sigma119:
Hey mates, i had same problems with cellular connection. I am from Poland so i cant really say hows 5G BUT i am using single sim and connection was just awfull.

I have managed to find a fix for that and now its all super good.

to try it for yourself just do:

Go to dialer app and input *#*#4636#*#*

go to phone information

search for DSDS

Disable this the f*** out

all good from now on

Hope that'll help !
[Google Pixel 7 Pro] akulp:
I tried this long time ago... nothing better.
[Google Pixel 7 Pro] swieder711:
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?