Here’s how to get rid of ‘Sensitive’ notifications issue on Android 15

Android 15 has introduced a new security feature that’s causing headaches for many users. The feature, designed to protect one-time passwords (OTPs) from malware, is blocking notification content on certain apps, smartwatches and other connected devices. But don’t worry, there’s a fix. Before getting to that, let’s first talk about what’s happening.

What’s going on with some notifications on Android 15?

Users are reporting that notifications on their smartwatches and other devices are showing up as “Sensitive notification content hidden” instead of displaying the actual message. This is affecting a wide range of devices, including Garmin watches as well as some apps such as third-party messaging apps. We’re seeing discussions about the problem on Reddit, Google’s Issue Tracker, and other community forums. It’s not just users talking about it either, even app developers are trying to figure out ways to address the problem.

To be clear, this isn’t something that’s popped up out of the blue. Users were complaining about the problem during the Android 15 beta testing phase. But it seems Google didn’t think it was serious enough to fix it before dropping the stable build.

Why is this happening?

Google implemented a feature to enhance security by protecting OTPs and other sensitive information from potential malware. However, the system seems to be overzealous, flagging many non-sensitive notifications as well. Android expert, Mishaal Rahman, provided a good explanation of the situation on Reddit, here’s what they said:

It’s because your app is considered an “untrusted” Notification Listener service hence it isn’t allowed to read sensitive notifications, like ones that hold OTP codes. Your app needs the new RECEIVE_SENSITIVE_NOTIFICATIONS permission which was added in Android 15. However, the permission has a protection level of signature|role, and the only roles the permission is granted to are COMPANION_DEVICE_WATCH (ie. watch companion apps), SYSTEM_AUTOMOTIVE_PROJECTION (like Android Auto), SYSTEM_NOTIFICATION_INTELLIGENCE (Android System Intelligence), SYSTEM_UI, COMPANION_DEVICE_COMPUTER (like Cross-Device Services), COMPANION_DEVICE_GLASSES, and HOME (the default launcher).

Many users are frustrated with this change, calling it “annoying” and “breaking functionality.” Some report that it’s affecting work emails, financial apps, and even marketing notifications.

How to fix it

There are a couple of ways to address this issue:

1. Disable Enhanced Notifications:
   • Go to your phone’s Settings
   • Navigate to Notifications
   • Turn off the “Enhanced notifications” option
2. Use ADB commands (for tech-savvy users):
   • Connect your phone to a computer
   • Open a command prompt or terminal
   • Run the following command: adb shell appops set [app_package_name] RECEIVE_SENSITIVE_NOTIFICATIONS allow
   • Replace [app_package_name] with the package name of your watch companion app or affected application
   • Restart the app after running the command

What’s next?

As this issue gains more attention, it’s likely that Google will address these concerns in future updates. For now, the workarounds mentioned above should help you get your notifications flowing again on all your devices. Remember, while these fixes can restore functionality, they may also reduce the security benefits of the new feature. As usual, we’ll keep an eye out for any further developments and will update the article.