A notification sound bug in Android 16 assigned some pixel owners, mutilating subsequent alerts if we remain in the notification shade; Google has recognized the problem and said that a fix will be implemented in a next quarterly version (QPR).
The stable version of Android 16, published in June, presented this problem where notifications fail to read sounds if an existing notification is present in the drop -down menu. A user documented the problem on Google Issue Tracker in June.
The user’s report said: “During notification tests, we realized that subsequent notifications do not play any sounds, even when the volume was defined on the maximum volume, as well as the Disturb replacement authorizations are granted (although this problem exists both when the DN mode is activated and deactivated).” He also noted: “By rejecting the notifications, the next notification will play a sound.”
This problem extends over various models of pixel telephone, with complaints from users of the Pixel 6 via the Pixel 9 series. Users have indicated that this bug has particularly an impact on essential alerts, including those of alarms, smart cameras and glucose monitors.
Google officially recognized the problem August 7Confirming a resolution is underway. The company said: “Thank you for reporting this problem. It is set internally and will be included in the next quarterly version. ”
The exact QPR version which will contain this correction remains not confirmed. Android 16 QPR1 is later scheduled for this month, while the QPR2 version is planned for December. Some users have adopted temporary solutions, such as acquiring the Play Store notification manager applications.