The Pixel 6 Pro has the worst connectivity and reception of any phone I've used
androidauthority.com
androidauthority.com
Products are not going to do a good job on aspects that arent well revuewed. This article makes it sound like this is crisis level bad on this device, at whichnpoint everyone might take notice. But I'd just like all phones to be competing not just to be ok, but to be good at cellular communication. Currently we dont evaluate that?
Could also be specific to the type of modem being used or specific frequency band for the article author (who is in France, I think?) vs reviewers who might be in the US or UK or etc.
Personally I've had very bad experiences with quality control on Google phone handsets. Every single one I've owned had various problems that wouldn't make it past QC at other manufacturers - like a broken proximity sensor on the Pixel 4 I got for work, improper cooling on the nexus 5X I bought while working at google (constantly thermal throttled), and a nexus 4 I bought that had a bad internal flash drive that failed a week after I set it up (RIP my 2fa codes).
It does sound like multiple people caught this, though:
> In case you’re wondering, this isn’t a problem with my particular unit because I’m not the only one to have expressed concerns about it. Marques Brownlee has already mentioned it in his Pixel 6 second-try video, my friend Cameron Summerson talked about it, and people are complaining about it on Twitter, Reddit (1, 2), and the Google Support forums (1, 2, 3).
For example, you can see rtings reviews on audio equipment where they have a test dummy and bring that test dummy onto a train/subway track to test microphone performance or noise cancellation performance.
Testing wireless signals could be done on a private network (say it costs some tens of thousands of dollars) but replicated for a comprehensive list of phones (say, gsmarena style) could be done.
I'm glad awareness is being brought to this issue.
I have a feeling that some of these may have assembly or hardware defects, and only kinda sort of work. The difference between my two phones is very pronounced.
It's recently decided to not re-connect to Wi-Fis till reboot. Leaving home is now scary, thankfully I have 80GB data I use about 2 of on an average month.
Another absolute PITA has been WebView being broken. An insane amount of apps refuse to work without it, and I've been forced to de-Google... on a Google phone.
12 has been a buggy, freezy, needs-reboot-daily mess. Noticeably worse than any Android OS release I've used (since the late Gingerbread days). Preview builds have occasionally, temporarily been worse, but this long for an official release is horrendous.
From what I remember it was Android 12 out of the box, but the problems started popping up after a while. First the bundled earphones carked it, then various issues with the phone. The UI feels less responsive relative to even the mid-range Samsung I had previously...
Seriously considering an iPhone next time around, and hey at least I can escape the Eye of Sauron, somewhat. I realised I don't care about tinkering, custom ROMs, launchers, and funky widgets. I just want a phone that does what it's supposed to, when I want it to. The less time I spent stuffing around on the phone, the more time I will have for more meaningful things.
... But I really do like fdroid. And Firefox. And a number of open source apps and replacement things that will never be on Apple's store (e.g. I'm using gadgetbridge because I hate some of the first party apps).
I'd have too much I'd miss.
Most people only take a plane once per year or less. Do they really need fast access to airplane mode?
No... Airplane mode is in fact "reset the cell modem because it's being flaky" mode... And it's on the quick access menu because people need to use it a lot.
To me, this just points out a massive engineering failure, and it disappoints me every time I see it... And then press it... Cos mobile data is being flaky again...