4 ms·
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 ?)
by karteum 4y ago
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 ?)
- Freak_NL 4y agoI 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.
- lesquivemeau 4y ago112 worked for me in France when i had to call, pixel 6 running stock firmware... It sure is hard to reproduce
- preisschild 4y agoAFAIK this only occurs when you have Microsoft Teams installed.
- Underphil 4y agoCan't help thinking dialling emergency services should trigger a force close of everything non-essential on the phone.
- hocuspocus 4y agoThe 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.
- qqqturing2 4y agoI 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.
- crooked-v 4y agoIt'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.
- izacus 4y agoPixel 6 and 7 phones don't use Qualcomm hardware anymore - they use Samsung modems I think.