ARTICLE AD BOX
My VoIP Android app shows a full-screen incoming call UI using Android’s full-screen intent (FSI). On Samsung Android 16, the FSI works perfectly when installing the debug build — but fails completely in the release build (Play Store). I need help understanding the difference and why Samsung blocks it.
Xiaomi: FSI works only after enabling “Show on Lock Screen” under “Other Permissions”. So OEM-specific suppressions exist.
Samsung Android 16: No similar toggle available
Permissions / settings (all granted by user)
I am using an old build toolchain, and I cannot upgrade. Android Gradle Plugin, AGP version: 8.2.2, target: 34
Push arrives via Batch.com (not Firebase-only). Release and debug receive the push. Only release fails to launch the full-screen Activity.
Please analyze why the exact same code executes FSI on Samsung Android 16 in debug mode, but not in release mode, and provide:
Samsung-specific rules that suppress full-screen intents (FSI).
How Samsung differentiates “debug” and “release” apps at the OS level.
Whether Samsung blocks FSI for non-dialer apps or non-privileged packages unless:
App is default Dialer
App has specific roles
App meets call-style UI expectations
Whether signature, Play Store install source, or app reputation affects FSI.
Whether Samsung requires the CALL notification channel to be created ONLY once, or with specific flags.
How to get equivalent to Xiaomi “Other permissions → Show on Lock screen” on Samsung.
Any Samsung OneUI 6 / Android 16 behavior that silently downgrades CALL notifications to heads-up notifications for release apps.
Any known OEM bugs where debug apps bypass FSI restrictions but release apps don’t.
How to reliably force FSI to appear on Samsung for normal VoIP apps.
