Hacker News Reader

Comment by vpt | Hacker News Reader

Here is the associated Google Pixel subreddit thread: https://www.reddit.com/r/GooglePixel/comments/z3knqv/action_...

I don't think this is newsworthy at this point. My Pixel 6 and Pixel 7 both are unreliable when trying to call 911, calling with an over the top app or dialing the PSAP's number directly are the only workarounds.

Google doesn't give a fuck about this issue. I have filed repeated support cases over the past year with Google about this when using T-Mobile or Verizon.

Google already didn't give a fuck about 911 problems (or 112 in my case) on the Pixel 4a, those have been unfixed since release.

Google doesn't seem to care that dead people don't make for good customers.

And FTC doesn't give a fuck about choice for consumers.

Pixel 6 is the last Google phone I bought, after owning every single Pixel up until that point.

A company who fucks up this badly is not worth my money.

I would say a life or death years old bug still present in the newest model (on which I'm writing this) is newsworthy.

Although I'm not sure how there's no legal repercussion here?

I have a Pixel 7, and I am curious how do you test the reliability of calling 911? I assume you don't actually call 911 and say "just testing!"

Most interesting is a user story[1] shared giving an idea of how often this happens: 3 times over 8 months, with ~5 calls a week. We could round it at around 1% error rate. It's both relatively low (as a chance it happens to you), and extremely high (I can't imagine how many people might have the issue and not be aware of it!).

I'm sure there are other conditions that aren't identified here, but this definitely warrants more regulatory scrutiny.

[1] https://www.reddit.com/r/GooglePixel/comments/z3knqv/comment...

Reply on news.ycombinator.com