3 ms·

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 the

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.

ddalex 4y ago
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 ?
- crooked-v 4y ago
  It's absolutely Android's fault that it allows a buggy app to interfere with emergency calls, and Google agrees, given that in later Android versions they tore out the code that allowed anything but OS handling for emergency calls placed through the default phone app.
- theshrike79 4y ago
  There is no reasonable way a normal user could suspect that buying a phone from one of the biggest companies in the world (Google) and installing a very common application from another huge company (Microsoft) will result in their phone no longer being able to dial the emergency number. This is most definitely Google's fault for allowing emergency calls to be overridden and not having a fallback if the override fails.
- zinekeller 4y ago
  Most custom versions of Android (in this context, non-Pixel phones) have actually hardcoded that all emergency calls (especially in lock screens) be routed into a different, lightweight, for-emergency-only dialer. Google has known about this but didn't do anything to also provide a hardcoded override. Edit: and apparently recent Android versions, but I can't confirm that.
rerenjkl 4y ago
Thanks for the clarification. I had no idea Android apps could intercept calling functions like that. I can see the benefits, but I’m amazed devices are allowed to be that open

3 ms·

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 the

by crooked-v 4y ago

ddalex 4y ago
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 ?
- crooked-v 4y ago
  It's absolutely Android's fault that it allows a buggy app to interfere with emergency calls, and Google agrees, given that in later Android versions they tore out the code that allowed anything but OS handling for emergency calls placed through the default phone app.
- theshrike79 4y ago
  There is no reasonable way a normal user could suspect that buying a phone from one of the biggest companies in the world (Google) and installing a very common application from another huge company (Microsoft) will result in their phone no longer being able to dial the emergency number. This is most definitely Google's fault for allowing emergency calls to be overridden and not having a fallback if the override fails.
- zinekeller 4y ago
  Most custom versions of Android (in this context, non-Pixel phones) have actually hardcoded that all emergency calls (especially in lock screens) be routed into a different, lightweight, for-emergency-only dialer. Google has known about this but didn't do anything to also provide a hardcoded override. Edit: and apparently recent Android versions, but I can't confirm that.
rerenjkl 4y ago
Thanks for the clarification. I had no idea Android apps could intercept calling functions like that. I can see the benefits, but I’m amazed devices are allowed to be that open