When working with apps on HyperOS 2.0, encountering notification display issues can be frustrating. You've mentioned your app is granted auto-start permissions, and while initial notifications might work, subsequent broadcasts show as 'No response from [app]' in the logs. Here's a breakdown of potential causes and troubleshooting steps:

**1. App State:**

- **Background Restrictions:** Ensure your app isn't subject to aggressive background restrictions on HyperOS 2.0. Some background activities might require specific permissions or configurations.
- **Wake Locks:** Double-check if your app is correctly acquiring and releasing wake locks when necessary. Without proper management, your app might not be active enough to receive notifications.

**2. Broadcast Receiver Issues:**

- **Receiver Registration:** Verify that your app's broadcast receiver is properly registered and listening for the specific notification intent.
- **Manifest Permissions:** Review your app's manifest file to ensure you have the required permissions for receiving and displaying notifications.

**3. Network Connectivity:**

- **Intermittent Connection:** Test your app's network connectivity to rule out intermittent issues that might be interrupting notification delivery.

**4. HyperOS 2.0 Updates:**

- **Recent Changes:** Consult HyperOS 2.0's release notes or documentation for any recent updates that might affect notification behavior.

This article is created by nurl and is licensed under the Creative Commons Attribution 4.0 International License.
All articles on this site, unless otherwise specified as reprints or sources, are either original works or translations by this site. Please ensure proper attribution before reprinting.