2 ms·
I'm not at all surprised by this. For a 5 year span I used probably 4-5 different Android phones, from HTC & Samsung. All of them had this kind of glitch, where
by phendrenad2 5y ago
I'm not at all surprised by this. For a 5 year span I used probably 4-5 different Android phones, from HTC & Samsung. All of them had this kind of glitch, where some kind of race condition gets the system stuck in an unanticipated state. UI elements that were supposed to scroll smoothly off the screen would get stuck halfway. Some system app would lock out touch events temporarily while loading something, and it would stay locked until a hard reboot.
I think it's a symptom of a system that's designed as a stack of abstraction layers, with developers who don't communicate. The developers of project A think a bug is a minor issue, not knowing that project B relies on it for something critical.
It's hard to write an app for a platform like this, too. Instead of one cohesive target, you have discontinuous abstraction layers.
Looks like Microsoft Teams was part of the problem here. I assume they had to hook into some semi-documented functionality that Google wasn't aware of or thought no one would use. On iOS, where Apple keeps tight control over their API surface, this is less likely to happen.
- macromagnon 5y agoAndroid has the concept of an Intent[0] which are basically a category of apps that can fulfill a functionality like sending an email, browsing the internet, or dialing a number, etc. So a developper can create contacts/caller app so that for example, when you click on a call button from say a google search, the OS asks the user to pick one app that was declared to be able to ACTION_CALL. If I had to guess, I'd say it's something having to do with Teams being given priority on calls followed by failure to having priority for emergency calls and no way to gracefully recover. Quickly browsing the documentation I see comments like Note: there will be restrictions on which applications can initiate a call; most applications should use the ACTION_DIAL. Note: this Intent cannot be used to call emergency numbers. Applications can dial emergency numbers using ACTION_DIAL, however.[1] [0] https://developer.android.com/guide/components/intents-common https://developer.android.com/guide/components/intents-commo... [1] https://developer.android.com/reference/android/content/Intent#ACTION_CALL https://developer.android.com/reference/android/content/Inte...
- fshbbdssbbgdd 5y ago> On iOS, where Apple keeps tight control over their API surface, this is less likely to happen. I snorted when I read this. Trust me, iOS has plenty of broken and poorly-documented APIs.
- kaba0 5y agoI have yet to use any system where the UI can’t get stuck. Usually any menu/whatever that appears on mouse over will remain open when some other action overlays another GUI element over it. But there are myriad other small bugs like this on windows to ios to even tiny tiling wms.
- varjag 5y agoSounds like the problem is too few people can code at Google.
- jdiez17 5y agoI think the problem is exactly the opposite.