You may have noticed that while AutoResponder works well on Android 15 and higher, some messages are no longer answered automatically or you see a [name_error]. The problem is that with Android 15, Google wanted to add a new feature to protect user privacy. The content of notifications is hidden from third-party apps if they contain certain "sensitive" information such as numerical codes (e.g. for two-factor authentication). In this case, only “Sensitive notification content hidden” will be shown to the apps instead of the actual message and chat name. Your device uses an algorithm to detect those sensitive messages. Unfortunately, this algorithm is not free of errors. Some normal messages are also recognized as sensitive, which prevents AutoResponder from working as expected. Even messages from unknown numbers are often identified as sensitive, even though the message itself only contains text. This is because the chat name contains the numbers. But there is no reason to worry, you can fix it.
If AutoResponder already works as you want it to, or you value privacy over functionality, you don't need to do anything else (Note that you can always be sure that AutoResponder will only process messages as specified in your rules). However, if you want to restore AutoResponder's reliability as in Android 14, respond to messages that contain number sequences or to messages that you receive from unknown contacts + all messages that follow a sensitive message until they are marked as read again, you can get the behavior back using this guide. There are two different approaches:
Easy and quick solution for many devices
Android detects sensitive notifications using the same algorithm that also delivers smart responses and functionality within notifications. This algorithm can be disabled. The downside is that these smart features are then also disabled. Here's how to do it (the exact location and name of the setting may depend on the device):
Open your device's general settings.
Go to Notifications.
Depending on the device you may need to click on Advanced settings.
Turn off the Enhanced notifications option. It can also be called something like Suggest actions and replies for notifications.
If you can't find the option, the problem isn't solved, or you don't want to give up smart notifications, you can use the following method.
Better advanced solution that should always work
This guide uses the ADB (Android Debugging Bridge) tool, which is originally intended for developers, to grant AutoResponder the RECEIVE_SENSITIVE_NOTIFICATIONS permission. With these instructions it shouldn't be too difficult though. But only follow them if you feel comfortable doing so.
You need to temporarily enable developer options on your device which you can disable again later (the exact location and name of the setting may depend on the device, but you can search the web for how to enable developer options for your exact device model):
Open your device's general settings.
Go to About device or About phone.
Depending on the device you may need to click on Software information.
Tap Build number seven times (7x). If there is no such option, it may also be called something like Operating system version. But the button for the Android version is never the right one.
You have enabled developer options now. Let's continue with the actual instructions:
Download the Termux app on the same device as AutoResponder if your device supports split screen. If your device does not support split screen, you can install the Termux app on a separate device (with a separate device it's probably easier). Without split screen it won't work on the same device because you have to have two apps open at the same time. Don't worry, you can uninstall Termux at the end.
In Termux, run following command which installs ADB (don't worry, will be removed again when uninstalling Termux at the end):
pkg install android-toolsCheck the console output and enter Y (means yes) after being asked to confirm. Run it. Always check the output when running commands.
Connect your devices to the same Wi-Fi network (Wi-Fi is even required if you are only using one device). For security reasons, you should not do this on a public Wi-Fi.
Find the developer options in the general settings of your device (the device with AutoResponder installed). Search the internet to see where you can find these on your exact device.
Within the developer options tap on the Wireless debugging (or Debugging over Wi-Fi) text (not the switch). Then enable it.
Open Termux and the Wireless debugging screen in split-screen mode (or Termux on a separate device). Search the web for how to use split-screen on your device model. Without split screen, the dialog of the next screen will be dismissed when switching apps before we can use it.
In the Wireless debugging settings click Pair device with pairing code. Keep the dialog open (make sure the screen does not turn off and don't switch apps) and use the information shown there in the next step. Note that the port for pairing is different to the port for connecting.
In Termux run the following command with YOUR IP-address and port from the previous step:
adb pair 192.168.1.1:12345You will be asked for the pairing code. Enter the pairing code from the dialog and confirm. After successful pairing, the dialog is closed automatically.
Now connect using the IP-address and other port shown in the Wireless debugging setting:
adb connect 192.168.1.1:56789With this command you can check if you are successfully connected. It will show the list of devices:
adb devices -lAfter connecting, you can run the command to enable AutoResponder to receive sensitive notifications. Don't worry, you can easily undo this by reinstalling AutoResponder or by setting the command to ignore instead of allow. Make sure to use the package name of the right AutoResponder app that you are using. You can also use this command multiple times with different package names if you have multiple AutoResponder apps installed. Following example is for AutoResponder for WhatsApp:
adb shell appops set tkstudio.autoresponderforwa RECEIVE_SENSITIVE_NOTIFICATIONS allowPackage names:
AutoResponder for WhatsApp: tkstudio.autoresponderforwa
AutoResponder for FB Messenger: tkstudio.autoresponderforfb
AutoResponder for Telegram: tkstudio.autoresponderfortg
AutoResponder for Instagram: tkstudio.autoresponderforig
AutoResponder for Signal: tkstudio.autoresponderforsignal
AutoResponder for Viber: tkstudio.autoresponderforviber
Optionally, you can check if the permission has been added successfully. It needs to say allow:
adb shell appops get tkstudio.autoresponderforwaIMPORTANT: Restart your device (the device with AutoResponder installed) for the change to take effect.
You can now uninstall Termux and disable the developer options again.
That's it! AutoResponder now works as reliably as in Android 14.