You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Android v0.11.3 APK blocked by Google Play Protect on Galaxy S24 Ultra #637
The official openstrap-edge-v0.11.3.apk from GitHub Releases cannot be installed on a Samsung Galaxy S24 Ultra. Google Play Protect blocks it before installation with this message (Spanish locale):
Se bloqueó la app para proteger tu dispositivo
Esta app puede solicitar acceso a datos sensibles. Esto puede aumentar el riesgo de robo de identidad o fraude financiero.
The dialog only offers “Entendido” (“Got it”). Expected: the official Android APK installs, or the release documentation provides a supported path.
Possible cause to investigate: Google documents this exact warning for browser-downloaded APKs that declare sensitive capabilities, including notification listener access. The v0.11.3 manifest declares notification.listener.service.NotificationListener with android.permission.BIND_NOTIFICATION_LISTENER_SERVICE. This is a hypothesis from the warning and source, not a confirmed diagnosis of the built APK. Could you confirm the cause and consider a release without the optional notification relay, or an appeal to Google Play Protect?
Likely cause. Your hypothesis looks plausible. The NotificationListener service in the manifest isn't declared by the app itself. It's merged in by the notification_listener_service plugin, which is only used by lib/notify/notification_relay.dart. That's the optional feature that relays phone notifications to the band as a buzz. Google lists notification-listener access among the capabilities that can trigger this "may request access to sensitive data" block for APKs downloaded outside the Play Store. I haven't checked this against the built APK, so it's still unconfirmed.
What doesn't fit yet. The same APK installs on my Galaxy S25. I only have to dismiss or turn off the usual Play Protect and "unknown source" prompts, as with any sideloaded app. Your dialog only offers "Entendido". That points to something specific to your device or region. Google has rolled this stricter block out by country and Android version, and Samsung's Auto Blocker can also stop sideloaded installs entirely.
Could you check these?
Your Android and One UI versions.
Whether Samsung Auto Blocker is on (Settings → Security and privacy → Auto Blocker). If it is, turn it off for the install.
Whether the install goes through once Device Protection is off (Play Store → profile icon → Play Protect → settings → "Scan apps with Play Protect" → Advanced Protection). You can turn it back on afterwards.
Whether you downloaded the APK in a browser or through a file manager.
If the listener service does turn out to be the trigger, a release without the notification relay, or a documented install path, would be a question for the maintainers.
Additional device details: Galaxy S24 Ultra running Android 16 and One UI 8.5. The v0.11.3 APK was downloaded from the official GitHub release in Chrome, then opened from Downloads. Samsung Auto Blocker is off; the Google Play Protect block still occurs.
Activity
Riedel-David commentedon Oct 27, 2026
Hey here is what I found.
Likely cause. Your hypothesis looks plausible. The
NotificationListenerservice in the manifest isn't declared by the app itself. It's merged in by thenotification_listener_serviceplugin, which is only used bylib/notify/notification_relay.dart. That's the optional feature that relays phone notifications to the band as a buzz. Google lists notification-listener access among the capabilities that can trigger this "may request access to sensitive data" block for APKs downloaded outside the Play Store. I haven't checked this against the built APK, so it's still unconfirmed.What doesn't fit yet. The same APK installs on my Galaxy S25. I only have to dismiss or turn off the usual Play Protect and "unknown source" prompts, as with any sideloaded app. Your dialog only offers "Entendido". That points to something specific to your device or region. Google has rolled this stricter block out by country and Android version, and Samsung's Auto Blocker can also stop sideloaded installs entirely.
Could you check these?
If the listener service does turn out to be the trigger, a release without the notification relay, or a documented install path, would be a question for the maintainers.
BarqueroJose commentedon Oct 28, 2026
Additional device details: Galaxy S24 Ultra running Android 16 and One UI 8.5. The v0.11.3 APK was downloaded from the official GitHub release in Chrome, then opened from Downloads. Samsung Auto Blocker is off; the Google Play Protect block still occurs.