- /e/OS version: 3.3-t - Device model(s): FP3 - Impacted Application: ~ - Affected application/URL: - Browser/client and version: ## The problem When I get a message (for instance mail or SMS) and a notification is placed in the notification area the configured notification sound is not immediately audible but delayed until the display is activated. This comes up every few days: you open the display and suddenly several waiting beeps come up, an entire queue. I watched this for a while and saw it's indeed only the beep, the LED is blinking ordinary. And when this situation is reached once it never changes anymore. That's annoying. The dependence of the beep on display activity is a strange thing. This must be findable in the code. Why is this so? What's the reason? As I always understood this a notification sound is something strictly independent, it must be audible under any circumstances, there can't be a condition. This is an old problem, is has been there several times in the last years but it could also be that I didn't have it for a year or so. Now with 3.3-t I have it regularly. My installation is from Dec 10 last year, a month ago, since then I had it about five (?) times. And I know also a second device (FP3) where this happens. What you then can do is a reboot. After a reboot notifying works again. Note: this is different from the ntfy problem handled in case 9135. **Update**: today a beep came about three hours to late without that I activated the display. It came on it's own. - How? **Steps to reproduce** You can't reproduce it. It just happens after some days of typical work. <!--Add the labels corresponding to your issue by adding a tilde and typing the name of the label you think apply to your issue in the line above. You need to type a tilde before the name of each label you want to apply to the issue. -->