31–40 of 265 posts
Quoted post unavailable.
It's not a network problem. It's a side effect of that Android version letting apps register to take over calling functions (for, e.g., VOIP purposes), when then makes emergency calls fail if any of the apps that have registered that functionality don't handle it properly.
Earlier quoted context omitted.
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?
Earlier quoted context omitted.
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?
Is there any theory or explanation why this happens? "Third party apps" is totally vague, what third party app could stop you from dialing an emergency number? And even if such apps exist (or even are common) is it not a huge design flaw by itself, which the manufacturer has to remedy?
Not sure why they don't say it by name but the bug was originally found with MS Teams. "The issue is the result of an “unintended interaction” between Teams and Android, specifically when the users have the app installed but are not logged in to any account." [0] [0] https://www.androidauthority.com/google-pixel-microsoft-team...
Earlier quoted context omitted.
It's not a network problem. It's a side effect of that Android version letting apps register to take over calling functions (for, e.g., VOIP purposes), when then makes emergency calls fail if any of the apps that have registered that functionality don't handle it properly.
Do you mean users install apps that are buggy, and this is somehow Androids fault? At the same time, if Android wouldn't allow VoIP apps, it would be somehow at fault again ?
Let's just spell it out instead of this clickbait title: Dialing the local emergency number (112, 000, and 911 were reported, but presumably also others) sometimes doesn't work, just gives a click instead of dialing. Google blames third party apps. Users report similar issues since Pixel 4 that were reported to Google but haven't been resolved since release. Not like "911 doesn't ring" is much longer of a title than…
Nothing about your explanation refutes that this is a very scary issue. Third-party apps or not, a phone that can't call emergency services in every situation other than empty battery should be treated by the government like food that can potentially poison people.
title implies "911 doesn't ring sometimes" ∈ "very scary issue dialing 911", that is incorrect
frankly "doesn't ring" is probably the most routine issue that can happen when dialing a number
the comment you respond to responds to article title and posits "911 doesn't ring sometimes" ∉ "very scary issue dialing 911"
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 ?)
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.