Support

Setup and troubleshooting

If devices do not connect or notifications are not delivered, check the items below in order.

Built for AndroidCheck permissionsCheck connection status

Quick checks

Three things to check first.

Notification access

Notification access for Notification Relay must be enabled on the sending device.

Exclude from battery optimization

Exclude the app from power saving on both devices and allow background data.

Matching connection details

Confirm that the connection code and encryption key are exactly the same on every device.

The app cannot connect to the server.

Check that Wi‑Fi or mobile data is working and allow background data for the app. If a VPN, ad-blocking DNS, or firewall blocks WebSocket connections, temporarily disable it for comparison.

Notifications from one specific app are not forwarded.

Confirm that the app is selected in Notification Relay and that its notifications are allowed in Android settings. Trigger one notification and refresh the detection status.

Forwarding stops when the screen turns off.

The manufacturer’s power-saving feature may be stopping the background service. Set battery usage to “Unrestricted” and allow auto-start, background activity, or power-saving exceptions if available.

The reply button does not appear.

Reply is a Pro feature, and the original messaging app must provide an Android notification reply action. Some apps, notification types, and security notifications do not support replies.

I want to change devices or reset the connection.

Review the device list and target selections. If needed, create a new connection code and encryption key and enter them on every authorized device. Old connections cannot decrypt new notifications without the new key.

Contact

Still having trouble?

When contacting support, include the device model, Android version, the step where the issue occurs, and any status message shown in the app. Never send your connection code or encryption key.

[email protected]