Description: Truecaller or another calling app crashes when a call arrives seconds after rebooting Android 15 or 16. Check Google issue #409069722, the beta fix and safe workarounds.
If a call arriving immediately after reboot makes Truecaller or another calling app crash on Android 15 or 16, check Google issue #409069722. Google lists a fix in Android 17 QPR3 Beta 1, released October 2, 2026. That confirms a beta fix, not a universal stable rollout.[1][2]
The specific trigger
Truecaller developers reported the problem on Android 15, including Pixel devices, in April 2025. A call arriving just after startup could trigger ForegroundServiceStartNotAllowedException as the app attempted to start its call-handling service. Another VoIP developer reported a similar sequence on Android 15 and 16 in March 2026.[2]
Android correctly restricts some services started by the boot-completed broadcast. In this case, the system could mistake a call-triggered service start for one triggered by boot completion. Google engineers investigated that misclassification. Not every dropped call or app crash shares this cause.[2][3]
| Symptom | What it suggests |
|---|---|
| App crashes only on calls immediately after reboot | Matches the reported timing |
| App crashes hours after startup | Check other app or system problems |
| Cellular signal disappears entirely | Investigate SIM and network service separately |
| App crashes simply by opening it | Investigate a general launch failure |
Safe checks before resetting anything
- Open Settings → About phone → Android version and record the build number.[4]
- Under Settings → Apps → Default apps → Phone app, check which app handles calls; menu names vary.
- Update the affected app from its official store. Record the crash time and the interval since reboot. Do not repeatedly miss real calls just to reproduce the bug.
- If missing calls would be serious, arrange another reachable contact method. Check features before changing the default dialer.
- If your Pixel is already enrolled in a compatible beta track, check Settings → System → Software updates for an offered official build.[4]
Fixed version and data-loss warning
The public issue was marked fixed on September 21, 2026. Google then included #409069722 in the October 2 Android 17 QPR3 Beta 1 notes. Published build identifiers are DP11.260918.005 and DP11.260918.006.[1][2]
The original reports concern Android 15/16, while the named fix is an Android 17 beta. As of October 18, stable rollout needs to be checked for each manufacturer. Do not join a beta solely to fix your main calling phone without considering the risks. Returning from beta to stable normally wipes local data, except during limited no-wipe windows explained by Google.[5]
Bottom line
Match the app name, Android build and timing of the call before changing anything. Prefer official app and system updates to factory resetting a phone that otherwise works.
References (1)
[1] Google, Android 17 QPR3 Beta 1 release notes (2026-10-02; last updated 2026-10-16): https://developer.android.com/about/versions/17/qpr3/release-notes [2] Google Issue Tracker #409069722, developer reports and fix status (2025-04 to 2026-09-21): https://issuetracker.google.com/issues/409069722 [3] Android Developers, foreground service types and restrictions: https://developer.android.com/develop/background-work/services/fgs/service-types [4] Google Pixel Help, check and update Android version: https://support.google.com/pixelphone/answer/7680439 [5] Google Android Beta Program, opt-out and data wipe: https://www.google.com/android/beta
