Hacker News Reader

Comment by karteum | Hacker News Reader

Is it a Google issue or a Qualcomm issue ? (e.g. does it occur when using Calyxos/GrapheneOS/LineageOS instead of the raw Google Android OS ?)

View on HN

I have a Pixel 6 running GrapheneOS, and the one time I called 112 in the Netherlands it worked. Hard to extrapolate from that one data point though.

It's a bit of a bother that this is not something you can test at any reasonable scale. “Just testing if my call gets through” is not something you want to see inundating emergency call centres.

112 worked for me in France when i had to call, pixel 6 running stock firmware... It sure is hard to reproduce

AFAIK this only occurs when you have Microsoft Teams installed.

Can't help thinking dialling emergency services should trigger a force close of everything non-essential on the phone.

It's a side effect of that Android version letting apps register to take over calling functions (for, e.g., VOIP purposes). If any such app on the phone doesn't handle the emergency call case correctly, then the attempt fails in one way or another.

Why does Android allow apps to take over emergency calls?

Because it allows apps to take over calls.

In short, bad overly-generified design that they completely tore out in later Android updates, limiting emergency calls to OS handling only.

The Pixel 6 has a Samsung SoC and 5G modem. If the Exynos based Samsung phones were also affected you'd have heard about it a lot more and earlier.

I had a Samsung 5G Exynos and when one time I couldn't call 112 (emergency number in Europe). Tried over and over. Even restarted my phone but the phone line was silent when it answered.

Pixel 6 and 7 phones don't use Qualcomm hardware anymore - they use Samsung modems I think.

Reply on news.ycombinator.com