We typically like Pixel phones a lot, but we have some reservations about Google’s quality control
r/android comment section giving the expected behavior as usual. These news sites know how to be a puppet master, I’m telling ya.
Webite wants to push pro Pixel discussion:
Proceeds to drop a article with a sensationalist title that triggers said Pixel owners.
Comment section is immediately filled with folks declaring how great their Pixel is.
This tactic flip flops between OEMS. It’s generally in Samsungs favor but not always.
Disclaimer: Idgf what phone you own. I’m only speaking on what is painfully obvious to me.
Great point.
It’s so weird to me when people reply with “doesn’t happen to me”.
And?
That these things happen to people is a positive claim on their part. The idiots commentors saying it doesn’t happen to them don’t even realize their dispositive claim is meaningless.
I have a pixel 8 that doesn’t have any issues, but I can read the title that says Google’s quality control is shit. So I can understand my phone is okay and other people have problems. Even if I bought 100 pixels, my sample size would still be too small to dismiss other people’s claims.
Funnily enough, this is my first comment I’ve made about how my pixel is fine. So now I’m part of the problem :3
My pixel 7 Pro’s vector motion sensor is broken. How the hell does that even happen? I’ve never even heard of it and there’s like nothing online about it.
I can’t do anything that requires tracking how the phone is moved- no compass calibration, no Map’s guidance arrow, etc.
There have been some strange issues with my 8 pro that resemble hardware connection issues or even the start of bad memory chunks. (The display glitches are mentioned in the article, actually.)
The new screen capture feature is buggy as all hell and is prone to buffer issues after long periods of spot translation.
I’d argue that a luck of the draw issue is worse than a consistent, across the board QA issue.
Still can’t bring myself to bite the bullet and buy a Pixel because of these “horror stories”.
Yeah, I am biased to QA as well.
Some of the glitches are subtle enough to make me think it’s something crunchy in the physical hardware. Many people simply wouldn’t notice the issues, TBH.
Like all hardware bugs, it’ll likely take a bit of time to manifest fully. Being cynical, I would probably say the failures will fully manifest around the Pixel 10 release timeframe.
All I know that really surprised me is I’d been disgusted with nothing phone 1 constantly rebooting for no reason since an update (still does it).
When I complained on a reddit sub about it I got a ton of replies saying it’s normal and not as bad as the pixel phones.
I’ve nowhere to go with that people are defending a completely unstable buggy phone and I’ve owned half a dozen androids before that and never seen any of them just randomly restarting.
I’ve had pixel phones for at least 5 years now. I’ve probably had less than 10 random restarts, most of those would have been from apps crashing.
Sometimes the device gets slow and I restart it. But that happens maybe 3 times per year. Otherwise the phone only gets restarted when an update is installed.
Yeah I’m skeptical of those claims as well, I’ve never owned a phone that did it a lot until this one and I’m pretty sure it’s Nothing who introduced the vast majority of problems.
Their just too concerned with things like clothing lines and pr stunts to actually fix anything they break
I wouldn’t buy the phone 1 again anyway put it that way.
It was actually great until phone 2 released then they updated it to be very unstable and the cameras also got noticeably worse from updates.
On the plus side I’ve read the custom roms for it are pretty good, I haven’t went that far yet but I know I will eventually.
I used to have that issue on my midrange samsung when i set the ramplus(virtual ram in samsung) to max and did medium to heavy multi-tasking. It was mitigated in a future update but did happen once a while. The slow storage speeds combined with heavy usage of virtual ram were the main reason for that.
Largely exaggerating bugs. If it happens to you that sucks, but I’ve never actually met anyone in the real world running into these bugs. This is “your holding it wrong” writing designed to rile up nerds.
You shouldn’t discount these reports just because you haven’t seen them yourself. I mean, how many people do you talk to in the real world about their Pixel phones? If it’s less than hundreds, it doesn’t really say much — that’s well within chance since, as the article states, the problem is inconsistency. If 1% of users experience a given problem, that’s actually a pretty big deal. If 10% experience it, it’s pitchfork time.
Pixel phones are notorious for poor quality control, and Google is notorious for poor customer support. That’s a bad combination. Lots of people have perfectly good experiences, but there are still a lot of problems that aren’t just flukes.
I read the article and I think it’s pretty fair. I’ve used a couple different Pixel models and followed their respective subreddits for years. It’s always something. Green tint, or poor signal, or overheating, or a barely-functional fingerprint reader, for example. None of these things affect everyone, but they’re real problems. Probably the fingerprint reader is the most widespread. At least that’s improved (for me) over time.
I have an 8 Pro that has had bugs since it was released.
They’re mostly frustrating inconveniences that make using it annoying. Graphical glitches, phone calls hanging up unexpectedly, being able to type even after going into open apps view, not being able to switch apps because it just disappears from the open apps view, the fingerprint sensor just not working at all sometimes, and more.
Nothing that breaks the phone, but it’s real annoying more often that it should be.
