When the legacy telecom settings component is missing on Android 17, Cheogram falls back to the telecomui activity. Android can still deliver an early DIALLER_INTEGRATION callback for the failed legacy launch before the real fallback result arrives. Use a separate fallback request code and ignore that bogus legacy callback while the telecomui result is still pending. Keep the final phone account settings launch deferred until the fallback flow returns so the deeper telecomui screen stays first in the task. Persist the request code and in-flight flag across savedInstanceState so the guard survives if Android kills and recreates the activity mid-flow, matching the existing pending-intent persistence.