Google confirms a permanent fix is coming for a bug that prevents some Android users from calling 911 if Microsoft Teams is installed but they are not logged in
Last week, a user reported that their Pixel 3 was not able to dial 911 (emergency services in the US).
Context & Ripple Effects
Reports had isolated the failure to a condition in which Microsoft Teams was installed but not signed in, as documented in the Android and Teams call-failure analysis. Google’s confirmation of a permanent fix turns that diagnosis into an Android-platform remediation issue rather than a Pixel 3-only incident.
The episode sits alongside Google’s earlier work on automated emergency-call location relays: emergency calling depends on the phone’s core calling path continuing to work even when third-party apps are in an unusual state.
First-order effects
- Affected Android users with an installed, signed-out Microsoft Teams app get a committed path to restore reliable 911 dialing once Google ships the fix.
- Google must change the Android behavior behind the failure, while Microsoft Teams remains the app condition associated with the reported trigger.
Second-order effects
- Google and Microsoft face stronger pressure to test interactions between installed communications apps and Android’s emergency-call flow, not merely normal calling and sign-in states.
- For Android device users, emergency-call reliability becomes a platform-quality concern that cannot be separated from the behavior of preinstalled or commonly deployed workplace apps.
Third-order effects
- If Android treats emergency calling as a protected system path across third-party app states, safety-critical calling will become a more explicit compatibility constraint for app developers and platform updates.
The trend: Android is tightening the boundary between third-party communications software and safety-critical emergency functions.