WAI
Status Update
No update yet.
Comments
vi...@google.com
vi...@google.com
We have passed this to the development team and will update this issue with more information as it becomes available.
co...@gmail.com
I would also consider this a major regression, for many of the reasons stated above. Being able to choose between multiple DND modes was a hugely beneficial feature which I used nearly every day. When I'm at work, I want "Priority Only" mode, but when I'm in a meeting I want "Total Silence."
I would encourage the return of the original three DND modes, with sensible defaults for users who may encounter the notification panel button but not follow-through to customize the modes in the settings screen.
The current solution in P makes DND extremely annoying to interact with, as I now have to go all the way through to settings to achieve what I could previously achieve in one or two taps. Couple that with the obtuse nature of the settings, and DND becomes practically unusable as a day-to-day feature. At this point, I feel that my only option is to set DND to the equivalent of a "Total Silence" toggle, which is impractical, and not at all what I need.
I would encourage the return of the original three DND modes, with sensible defaults for users who may encounter the notification panel button but not follow-through to customize the modes in the settings screen.
The current solution in P makes DND extremely annoying to interact with, as I now have to go all the way through to settings to achieve what I could previously achieve in one or two taps. Couple that with the obtuse nature of the settings, and DND becomes practically unusable as a day-to-day feature. At this point, I feel that my only option is to set DND to the equivalent of a "Total Silence" toggle, which is impractical, and not at all what I need.
vi...@google.com
Once again, thank you for submitting the feature request. After following up with our product and engineering teams, the feature request will not be able to be considered at this time.
19...@gmail.com
Well, that's not surprising in the least. Now I'm 100% sure this was an intentional feature removal, and it was probably intended to make DND more like the iOS equivalent.
Looks like I'm not updating to P when it releases now. Fuck you Google. 🖕🏻
Looks like I'm not updating to P when it releases now. Fuck you Google. 🖕🏻
vi...@google.com
We've deferred this issue for consideration in a future release. Thank you for your time to make Android better.
vi...@google.com
In case you want to provide more information with respect to this bug, please file a bug in AOSP via "https://goo.gl/TbMiIO ".
jo...@gmail.com
I was involuntarily updated to Pie. It looks nice, but I NEED total silence mode, and I miss priority only enough that I might revert to Oreo. It's such a hassle to downgrade, though...
jo...@gmail.com
Mine wasn't working when I first installed 9/Pie, but now after an update when I click the do not disturb icon it's now blocking all sounds. This is Lineage OS 16.0/Android Pie. Could be different for manufacturer versions.
st...@gmail.com
This is so annoying. Please don't try to emulate iOS. Android being so different from it has been the reason I've been sticking with it. You're not gonna win more users, sheep will still buy Apple products. Please strive to make a good product for power users. Anyway, even my mother has been using Android for years without any glaring issues and she's as far as from power user one can be.
TLDR: Please give us the original DND functionality back. It was so useful!
TLDR: Please give us the original DND functionality back. It was so useful!
jo...@gmail.com
There is only one mode available. "Priority only" functionality should be possible under a separate ruleset.
da...@gmail.com
What happened to total silence mode? Just bought a Google Pixel (aka lPhone wannabe) and it sucks! Total Silence was a very practical feature on my old Nexus. At least l bought the old model that has a headphone jack. I can't believe Google got rid of that. Please fire whoever is in charge of Google Pixel.
pe...@gmail.com
Google removing features makes totally no sense. This was a vital feature for my daily usage and its removal will eventually lead me to install custom ROMs in my device. So, if Google wants us to stay away from custom software that is potentially dangerous, why do they keep on removing useful features? It truly makes no difference for them, so there is no point in doing so. Is there a specific reason, then?
zv...@yahoo.com
why is there no silent mode, i want to se if someone called but dot want it to wake me up,.
if i could go back i would never upgrade to pie.
if i could go back i would never upgrade to pie.
rt...@hobi.com
I am still on Android Oreo, and this change alone leaves me hesitant to upgrade. I absolutely depend on the different modes - I use priority only or Alarms only in various scenarios, and occasionally use Total Silence.
For example, I use Dexcom Follow app to keep tabs on my Type 1 Diabetic family member - most of the time, I want notifications from that app to blast through my DND settings and alert me (in priority or alarm only)...but occasionally (like at church or movies when I'm with the family member) I don't need that alert, so I use total silence.
In Android Oreo it is two taps & done (first tap get DND presets up, second tap to select desired preset)...in Android Pie I have to go muck around in DND settings each time I am in a different scenario.
I think a nice compromise would be to add the ability to add DND profiles...many people might be fine with a single profile, but others could add a second or third DND profile for quick activation.
For example, I use Dexcom Follow app to keep tabs on my Type 1 Diabetic family member - most of the time, I want notifications from that app to blast through my DND settings and alert me (in priority or alarm only)...but occasionally (like at church or movies when I'm with the family member) I don't need that alert, so I use total silence.
In Android Oreo it is two taps & done (first tap get DND presets up, second tap to select desired preset)...in Android Pie I have to go muck around in DND settings each time I am in a different scenario.
I think a nice compromise would be to add the ability to add DND profiles...many people might be fine with a single profile, but others could add a second or third DND profile for quick activation.
sa...@gmail.com
I second the suggestion in
To the developers: Please include an option to enable priority mode. Doesn't need to be enabled by default, but an option for advanced users who know what they are doing to enable it.
To the developers: Please include an option to enable priority mode. Doesn't need to be enabled by default, but an option for advanced users who know what they are doing to enable it.
rg...@gmail.com
I've got the Beta for Android Q and some of the custom settings were added back in. You can setup overrides for predefined schedules that, for the most part, mimic the Oreo DND settings
si...@gmail.com
We also need custom settings for the notification channels!
rg...@gmail.com
Like this? The settings are per app.
jo...@gmail.com
LineageOS brought this feature back in their latest builds (roughly June 1st and later). If anyone absolutely needs this, switching to it could be an option. https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/246850
tp...@gmail.com
This problem makes my phone essentially unusable at work. I use messaging apps and they have beeps and boops that are impossible to turn off. My old phone allowed me to enforce "total silence" which meant that I could use the phone without disturbing my coworkers in an open office. Now I just can't.
qa...@gmail.com
The good news for some -- hopefully many -- is that on Android Q, while they did not return the multiple modes, the one mode has a much more granular bunch of settings for exactly which sounds are on or off when DND is active. While they have also not re-separated the phone ringer and notifications volume controls elsewhere as it used to be a few versions ago, they have separated those and other things within DND so that you can turn on one while the others are off or vice-versa. Further, scheduled events can each have its own complete set of options for which sounds are on or off. I can have the main DND (the one that is activated using the pull-down) that turns off literally every sound, while setting up a scheduled event for sleep that activates at a specific time, but this one can leave the ringer active in case I get any emergency calls while silencing everything else. I have yet another for meetings that turns on every time I have a calendar event on my work calendar if I selected "busy" for it. Finally, with this bunch of changes, it makes the DND able to handle all of the scenarios I previously needed before Pie made it too limited for me.
ka...@gmail.com
This needs to be addressed. It is a serious regression. Technology should enhance life, not make it aggravating.
ct...@gmail.com
I used to use priority only at night and total silence for movies and meetings. Now, I can't just use one or two taps. This regression is very inconvenient. I now have to keep DND settings equivalent to priority only and permanently on and manually change the ringer to silent. I'm not able to use message notifications at all, because there's no way way to toggle those on and off like there was with different DND modes.
br...@gmail.com
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>This is what happens when Google focuses on making their Android
OS *too much* like iOS. We don't want the simple, restrictive
stupidity of an iPhone. We want the advanced options of Android.
If you want more entry level users to be comfortable on your
Android OS, then instead of removing advanced features for
advanced users, how about you just put those advanced features
under a single menu item called "Advanced"?<br>
</p>
<div class="moz-cite-prefix">On 7/17/19 7:14 AM,
<a class="moz-txt-link-abbreviated" href="mailto:buganizer-system@google.com">buganizer-system@google.com</a> wrote:<br>
</div>
<blockquote type="cite"
cite="mid:80089859+31+32+brazildan87ATgmail.com@buganizerPROD.corp.google.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div itemscope="" itemtype="http://schema.org/EmailMessage ">
<div style="background-color: #fbe983; border: 1px solid
#debe07; color: #594c04; font-weight: bold; padding: 5px
10px;">Replying to this email means your email address will be
shared with the team that works on this product.</div>
<br>
<a href="https://issuetracker.google.com/issues/80089859 "
moz-do-not-send="true">https://issuetracker.google.com/issues/80089859 </a><br>
<br>
<strong>Changed</strong><br>
<br>
<span itemprop="text"><strong><a class="moz-txt-link-abbreviated" href="mailto:ka...@gmail.com">ka...@gmail.com</a> added <a
href="https://issuetracker.google.com/issues/80089859#comment23 "
moz-do-not-send="true">
This needs to be addressed. It is a serious regression.
Technology should enhance life, not make it aggravating.<br>
<br>
</span><br>
_______________________________
<div itemprop="about" itemscope=""
itemtype="http://schema.org/CreativeWork "><span
itemprop="action" itemscope=""
itemtype="http://schema.org/ViewAction ">
<meta itemprop="url"
content="https://issuetracker.google.com/issues/80089859 ">
<meta itemprop="name" content="Open bug">
</span><br>
<strong>Reference Info: 80089859 [Developer Preview Android P]
Do Not Disturb lost its three modes, which allowed
versatility</strong><br>
</div>
<span style="color:#808080;">component: </span><a
href="https://issuetracker.google.com/components/190602 "
target="_blank" moz-do-not-send="true">Android Public Tracker
> Android Beta (Developer Preview)</a><br>
<span style="color:#808080;">status: </span>Assigned<br>
<span style="color:#808080;">reporter: </span><a class="moz-txt-link-abbreviated" href="mailto:19...@gmail.com">19...@gmail.com</a><br>
<span style="color:#808080;">assignee: </span><a class="moz-txt-link-abbreviated" href="mailto:vi...@google.com">vi...@google.com</a><br>
<span style="color:#808080;">cc: </span><a class="moz-txt-link-abbreviated" href="mailto:19...@gmail.com">19...@gmail.com</a><br>
<span style="color:#808080;">type: </span>Bug P3 S3<br>
<span style="color:#808080;">blocked by: </span><a
href="https://issuetracker.google.com/issues/80178096 "
target="_blank" moz-do-not-send="true">80178096</a><br>
<span style="color:#808080;">duplicate issue: </span><a
href="https://issuetracker.google.com/issues/80555708 "
target="_blank" moz-do-not-send="true">80555708</a><br>
<span style="color:#808080;">hotlist: </span><a
href="https://issuetracker.google.com/hotlists/710308 "
target="_blank" moz-do-not-send="true">Google Domain</a>, <a
href="https://issuetracker.google.com/hotlists/461195 "
target="_blank" moz-do-not-send="true">Platform</a><br>
<span style="color:#808080;">retention: </span>Component
default<br>
<br>
<br>
<br>
Generated by Google IssueTracker notification system<br>
<br>
<span style="color:#808080;">You're receiving this email because
you are subscribed to updates on Google IssueTracker issue <a
href="https://issuetracker.google.com/issues/80089859 "
moz-do-not-send="true">80089859</a> where you have the role:
starred. </span></div>
</blockquote>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>This is what happens when Google focuses on making their Android
OS *too much* like iOS. We don't want the simple, restrictive
stupidity of an iPhone. We want the advanced options of Android.
If you want more entry level users to be comfortable on your
Android OS, then instead of removing advanced features for
advanced users, how about you just put those advanced features
under a single menu item called "Advanced"?<br>
</p>
<div class="moz-cite-prefix">On 7/17/19 7:14 AM,
<a class="moz-txt-link-abbreviated" href="mailto:buganizer-system@google.com">buganizer-system@google.com</a> wrote:<br>
</div>
<blockquote type="cite"
cite="mid:80089859+31+32+brazildan87ATgmail.com@buganizerPROD.corp.google.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div itemscope="" itemtype="
<div style="background-color: #fbe983; border: 1px solid
#debe07; color: #594c04; font-weight: bold; padding: 5px
10px;">Replying to this email means your email address will be
shared with the team that works on this product.</div>
<br>
<a href="
moz-do-not-send="true">
<br>
<strong>Changed</strong><br>
<br>
<span itemprop="text"><strong><a class="moz-txt-link-abbreviated" href="mailto:ka...@gmail.com">ka...@gmail.com</a> added <a
href="
moz-do-not-send="true">
This needs to be addressed. It is a serious regression.
Technology should enhance life, not make it aggravating.<br>
<br>
</span><br>
_______________________________
<div itemprop="about" itemscope=""
itemtype="
itemprop="action" itemscope=""
itemtype="
<meta itemprop="url"
content="
<meta itemprop="name" content="Open bug">
</span><br>
<strong>Reference Info: 80089859 [Developer Preview Android P]
Do Not Disturb lost its three modes, which allowed
versatility</strong><br>
</div>
<span style="color:#808080;">component: </span><a
href="
target="_blank" moz-do-not-send="true">Android Public Tracker
> Android Beta (Developer Preview)</a><br>
<span style="color:#808080;">status: </span>Assigned<br>
<span style="color:#808080;">reporter: </span><a class="moz-txt-link-abbreviated" href="mailto:19...@gmail.com">19...@gmail.com</a><br>
<span style="color:#808080;">assignee: </span><a class="moz-txt-link-abbreviated" href="mailto:vi...@google.com">vi...@google.com</a><br>
<span style="color:#808080;">cc: </span><a class="moz-txt-link-abbreviated" href="mailto:19...@gmail.com">19...@gmail.com</a><br>
<span style="color:#808080;">type: </span>Bug P3 S3<br>
<span style="color:#808080;">blocked by: </span><a
href="
target="_blank" moz-do-not-send="true">80178096</a><br>
<span style="color:#808080;">duplicate issue: </span><a
href="
target="_blank" moz-do-not-send="true">80555708</a><br>
<span style="color:#808080;">hotlist: </span><a
href="
target="_blank" moz-do-not-send="true">Google Domain</a>, <a
href="
target="_blank" moz-do-not-send="true">Platform</a><br>
<span style="color:#808080;">retention: </span>Component
default<br>
<br>
<br>
<br>
Generated by Google IssueTracker notification system<br>
<br>
<span style="color:#808080;">You're receiving this email because
you are subscribed to updates on Google IssueTracker issue <a
href="
moz-do-not-send="true">80089859</a> where you have the role:
starred. </span></div>
</blockquote>
</body>
</html>
so...@gmail.com
please bring the complete silence mode back to android pie
be...@gmail.com
Please bring back total silence. Its so inconvenient to not have this when using the phone in a situation where you want to avoid accidentally disturbing anybody. Media always plays, often at volume, despite being on silent/dnd. Please address this. Thanks.
li...@yahoo.com
Please...
ba...@gmail.com
So annoying that after all this time this issue has still not been resolved.
an...@gmail.com
Who was (ir)responsible for this ? What a clusterfuck... If you like iOS so much, buy an iPhone...
Please, Make DND useful again...
Please, Make DND useful again...
pe...@gmail.com
I just want a plain, simple TOTAL SILENCE mode. Do not make a sound. When I'm at the movies - don't make a sound. When I'm at a classical music concert - you better not make a peep. When I want to give someone my full attention - do not interrupt me. Not. One. Sound.
It used to be so easy, and then they removed it. So frustrating.
It used to be so easy, and then they removed it. So frustrating.
su...@gmail.com
Please bring it back, this feature was so usefull.
d....@gmail.com
If anyone is interested you can use the app one shade to allow the drop down menu again for the 3 modes. It's not quite as smooth as stock but customizable and allows for the flexibility that usually makes android better than ios...
Good work around in the mean time until they fix this.... Which may never happen so yea just get used to one shade or some equivalent I guess? Could someone make an apk or something of the old do not disturb and override the stock quick setting or did they do away with that in pie too?
Good work around in the mean time until they fix this.... Which may never happen so yea just get used to one shade or some equivalent I guess? Could someone make an apk or something of the old do not disturb and override the stock quick setting or did they do away with that in pie too?
ol...@gmail.com
Please bring back the 3 DND modes. If I wanted simple but useless features, I would have bought an iPhone. You're better than this.
ol...@gmail.com
Comment has been deleted.
ce...@gmail.com
PLEASE bring back Total Silence mode. I need it for church and other situations where I need the phone to be absolutely silent. It's not always possible or safe to just turn the phone off or leave it at home. It's a huge nuisance having to change all the DND settings every time I need teei silence.
vi...@google.com
Re-
ad...@google.com
Thanks for the feedback. We've investigated your request and found that the current behavior is by design.
rd...@gmail.com
You say that it's working as designed.
I am a user and I don't like the design. You removed functionality that I
valued and used.
Changing something, getting complaints, and responding that there's no
error; that it's working as designed is ignoring the complaints!
On Wed, Feb 26, 2025, 8:36 AM <buganizer-system@google.com> wrote:
I am a user and I don't like the design. You removed functionality that I
valued and used.
Changing something, getting complaints, and responding that there's no
error; that it's working as designed is ignoring the complaints!
On Wed, Feb 26, 2025, 8:36 AM <buganizer-system@google.com> wrote:
er...@gmail.com
@rd (post 39) Thank you for saying exactly what I was thinking.
Description
This issue details a major regression in functionality from Oreo to P. (To my knowledge, this is by design.)
In Android 8.1 Oreo, Do Not Disturb had a selection of three modes could be enabled at any one time: "Priority only," "Alarms only," and "Total silence." These three modes allowed the Do Not Disturb feature to be utilized with different levels of granularity, making the feature more useful and versatile. For example:
- When enabled manually, I could specify what level of silencing I desired, allowing me to select a harsher or weaker setting depending on what I am doing at the moment.
- When enabled by a scheduled routine, I could specify it to use a harsher or weaker setting than I would normally trigger manually. This allowed me to automatically silence my phone during work hours, where I would be personally liable if it were to make noise.
- When enabled by the Pixel 2's smart "driving" mode, I could specify it to exempt priority callers who I would probably want to hear from behind the wheel, but block all other callers. Again, this is different desired functionality from the other two use cases listed here.
(An additional note: The different levels had different tolerances of media playback, which allowed me to use DND to guarantee media silence in most cases while leaving my headset media volume intact. This was not true, however, in Total silence, which was expected behavior.)
The old system wasn't perfect. The modes were somewhat confusing to new users, and I only could control which mode scheduled routines could put the device in and what fell under "priority." But Android P is a major step backward, for one very obvious reason.
In Android P DP2, the three modes have been REMOVED. Instead, I am forced to use the same settings for Do Not Disturb in every use case, which is not only illogical but has also disrupted my normal habits. A few examples:
- Since I must use the same settings of DND for my scheduled routines, manual activations, and driving mode, I had to make a few undesired changes to my settings. For example, I added alarms and media to my exception list, which is NOT wanted in the case where I turn it on and off automatically.
- I also can no longer specify different levels of granularity when manually enabling the setting. This means that whenever I use DND in any case I no longer can rely on it to exempt priority callers and messages. As I have already explained, I cannot change my exceptions permanently to accommodate this. I also think it would be silly to have to open Settings and change this every time I manually enable or disable DND, as that is precisely what the old modes were for.
- When Driving mode is enabled, my headset volume is now blocked. This makes very little sense before considering this issue, and really shouldn't be lumped together with speaker media volume.
The obvious solution to this would be to add the old modes back. (But for reasons beyond the scope of this issue, I don't think you're going to consider that.) So I offer a secondary proposal:
Each scheduled routine (under "Turn on automatically," including the Pixel 2's Driving mode) should have its own unique submenus that override the default "Block visual disturbances" and "Exceptions settings for that one routine. This would allow me to configure each automatic routine to fit its desired use case without the confusion of the three modes, while providing a net improvement in functionality from Android 8.1 Oreo.
Attached is an example of what this feature could look like.
SUMMARY:
I would like to be able to apply P's granular Do Not Disturb controls individually to my automatic rules, including Driving mode. This would correct the feature regression from Oreo to P caused by the removal of Oreo's three Do Not Disturb modes.
OTHER NOTES:
- I personally would like to see the differing icons from the three modes return in some form. I would like to be able to tell the difference between a manual activation, automatic routine, and Driving mode simply by looking at the status bar. I don't exactly know the best way for something like this to be implemented, but it would be nice.
- Some of the new features coming in future previews centered around Digital Wellbeing would also benefit from this change, the primary example being Shush mode. To be honest, I see no purpose for Shush mode if Do Not Disturb remains the way it is in DP2. But if this issue's feedback was incorporated into a future preview, I would be able to set Shush to mute all but priority callers, which I would find more logical. (Note that this assumes Shush is implemented via Automatic rules like Driving mode, which may very well not be the case.)