2 ms·
Google blames third party apps. I'm not going to suggest third parties can't screw with a phone and make it effectively unusable, but why isn't emergency calli
by onion2k 4y ago
Google blames third party apps.
I'm not going to suggest third parties can't screw with a phone and make it effectively unusable, but why isn't emergency calling a separate code path in the dialler app and OS that just ignores everything that third parties have done? It should be impossible to change the behaviour of that small bit of the phone. Don't fire any OS level events, don't call any callbacks, ignore any registered intents.
This is on a Pixel. Google can have complete control of the OS and dialler if they want to. They should be able to effectively isolate this from the rest of the phone. Blaming third parties doesn't really explain it.
- fourthark 4y agoThis link posted by crooked-v seems to explain why it was like that, and how it has been fixed. https://arstechnica.com/gadgets/2022/01/google-fixes-nightmare-android-bug-that-stopped-user-from-calling-911/ https://arstechnica.com/gadgets/2022/01/google-fixes-nightma...
- Sakos 4y ago> Next bug: when picking a PhoneAccount to run the emergency call through, Android goes through a complicated sorting process to figure out which account to use. The last step in this sort process, the tiebreaker, is sorting by hashcode. The hashcode comparison just subtracts one hashcode from the other. But just like that stupid Y2K22 Microsoft Exchange bug from the other day, it's possible for this to result in an integer overflow or underflow, and now the phone subsystem is going to crash. This is horrifying and stupid and horrifyingly stupid.
- Aachen 4y agoI didn't mean for it to sound as though I thought this was a legitimate reason absolving Google of blame. I cited it as a lame excuse, exactly for the reason you mentioned: this should be a core system thing, not influenceable by third parties.