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.