[larntz]

I have a pixel 6 pro and this has been my experience since they day I got it. I even had it replaced and still have to reset the cellular modem several times per week because I get the no service `!`.

Starting to believe it is a T-Mobile service issue in my area. Previously had a pixel 2 on Verizon and never had a problem. Planning to leave T-Mobile in the near future.

[zdragnar]

Pixel 6 on AT&T, I don't think I've ever had this experience.

Phone calls sound much better than my previous carrier (some cheap mvno) and things generally Just Work.

Only complaint is that it's missing some things I hadn't realized were not stock Android, such as per-app volume control. I just might switch back to LG after this one dies, though the battery seems to be holding up much better so who knows.

[mook]

Switching back to LG might be difficult; they are no longer making (Android) phones.

https://en.wikipedia.org/wiki/LG_Electronics#Mobile_devices

[zdragnar]

Well, there goes that plan :(

[beart]

I have a 6A on T-Mobile. Exact same issue for me.

Do you use wifi calling when you are at home? It has been my experience that T-Mobile WiFi calling is absolutely terrible, and I've oftentimes wondered if something in the software "locks" into WiFi instead of switching to cellular data, until the phone is rebooted.

[larntz]

Yep! I work from home and use WiFi calling. When I leave my house is usually when I have the issue.

Sometimes it'll work fine for a while after leaving and a few hours later I notice I don't have service.

[0_____0]

Same issue for me! After my previous Pixel bricked due to a flash chip wearing out (wtf?) I'm swearing off the Pixel line.

I'm in the Northeast USA on T-Mobile. You?

[larntz]

I'm in South Florida.