Yes thisWhich version you mean by A2 ? This one 13.0.0 (TD1A.220804.009.A2, Oct 2022)
Yes thisWhich version you mean by A2 ? This one 13.0.0 (TD1A.220804.009.A2, Oct 2022)
The update also does not really solve the problem of connection?
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.The update also does not really solve the problem of connection?
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.
Exactly ditto.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.
Yeah it's been known since May that it's an SA problem.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.
View attachment 5783687
View attachment 5783689
View attachment 5783691
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.
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.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
Really ?I read that the new QPR2 beta has a new modem update as well.
Has anyone noticed any improvements in reception?
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.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.
Just saw this article: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.
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.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.
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.cellcheckerCool, I just about finished writing mine. (I'm supposedly on the latest things but still got many disconnects today.)
Well, I'll give NetMonitor a try. It seems to do many things, which hopefully include everything that I did, which is an MVP.
Mine has gotten worse..Use on TMobileI read that the new QPR2 beta has a new modem update as well.
Has anyone noticed any improvements in reception?
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