Infeasible
Status Update
Comments
so...@gmail.com <so...@gmail.com> #2
This really needs to get fixed ASAP. It turns out that using `NotificationManager.IMPORTANCE_MIN` is not a feasible workaround because that will cause the Notification to get inserted into a COLLAPSED Notification Channel Group, making it very inaccessible.
so...@gmail.com <so...@gmail.com> #3
The behavior is exactly the same as if I had changed it manually from default (middle) to high. When you do that, and then disable and re-enable the channel, it will go back to the default (middle) setting.
so...@gmail.com <so...@gmail.com> #4
Also, keep in mind that just changing the `NotificationManager.IMPORTANCE_xxx` value doesn't change it on an already existing channel.
so...@gmail.com <so...@gmail.com> #5
Turns out that using `NotificationManager.IMPORTANCE_LOW` will disable the sound and not collapse the item. Yet the problem with the `NotificationManager.IMPORTANCE_DEFAULT` getting upgraded to a `NotificationManager.IMPORTANCE_HIGH` is still there.
Keep in mind that previous Android versions did not play a sound by default.
Keep in mind that previous Android versions did not play a sound by default.
so...@gmail.com <so...@gmail.com> #6
Actually, when I use `NotificationManager.IMPORTANCE_LOW` then I see that it is labeled as "Importance: Middle: No sound", and when I toggle it off and on, it stays at "Importance: Middle: No sound".
This means that there is a confusion there. Then it should mean that when creating a channel `NotificationManager.IMPORTANCE_DEFAULT`, it doesn not get upgraded to a `NotificationManager.IMPORTANCE_HIGH`, but AFTER TOGGLING it gets downgraded to `NotificationManager.IMPORTANCE_MIN`, yet the text indicates that `NotificationManager.IMPORTANCE_DEFAULT` is presented to the user as "High", and what is presented to the user as "Middle" is actually a `NotificationManager.IMPORTANCE_LOW`
This means that there is a confusion there. Then it should mean that when creating a channel `NotificationManager.IMPORTANCE_DEFAULT`, it doesn not get upgraded to a `NotificationManager.IMPORTANCE_HIGH`, but AFTER TOGGLING it gets downgraded to `NotificationManager.IMPORTANCE_MIN`, yet the text indicates that `NotificationManager.IMPORTANCE_DEFAULT` is presented to the user as "High", and what is presented to the user as "Middle" is actually a `NotificationManager.IMPORTANCE_LOW`
ar...@google.com <ar...@google.com> #7
Can you please provide the below requested information to better understand the issue:
Steps to reproduce
Please provide source code or apk of a sample application to reproduce the issue.
Also kindly mention the steps to be followed for reproducing the issue with the given sample application.
Frequency
How frequently does this issue occur? (e.g 100% of the time, 10% of the time)
Expected output
Could you please explain the expected behavior.
Current output
Could you please explain the current behavior.
Steps to reproduce
Please provide source code or apk of a sample application to reproduce the issue.
Also kindly mention the steps to be followed for reproducing the issue with the given sample application.
Frequency
How frequently does this issue occur? (e.g 100% of the time, 10% of the time)
Expected output
Could you please explain the expected behavior.
Current output
Could you please explain the current behavior.
ar...@google.com <ar...@google.com> #8
Please provide the information requested in comment #7 to investigate further.
so...@gmail.com <so...@gmail.com> #9
I would if I found some time.
The steps to reproduce can be inferred from the problem description. It happens 100% of the time. The expected behaviur is clearly defined as well as the current output.
I'm sorry that I don't have time to provide you a sample application. I am not affected by this problem because in my app I don't have the need for any other setting than NotificationManager.IMPORTANCE_LOW, which isn't affected by this issue.
It could be a problem for those who use NotificationManager.IMPORTANCE_DEFAULT
Once again, my apologies for only pointing out this problem.
The steps to reproduce can be inferred from the problem description. It happens 100% of the time. The expected behaviur is clearly defined as well as the current output.
I'm sorry that I don't have time to provide you a sample application. I am not affected by this problem because in my app I don't have the need for any other setting than NotificationManager.IMPORTANCE_LOW, which isn't affected by this issue.
It could be a problem for those who use NotificationManager.IMPORTANCE_DEFAULT
Once again, my apologies for only pointing out this problem.
ar...@google.com <ar...@google.com> #10
We are closing this issue as we don't have enough actionable information. If you are still facing this problem, please open new issue and add the relevant information along with reference to earlier issue.
gr...@gmail.com <gr...@gmail.com> #11
When creating a Notification Channel
NotificationChannel mChannel = new NotificationChannel(channel_id, "Channel 1", NotificationManager.IMPORTANCE_DEFAULT);
Android actually registers it as
NotificationChannel mChannel = new NotificationChannel(channel_id, "Channel 1", NotificationManager.IMPORTANCE_HIGH);
This means that sounds are played by default, while they should not get played by default at importance level NotificationManager.IMPORTANCE_DEFAULT.
I have the same issue on Nexus 6P and user report about this problem on Pixel XL.
NotificationChannel mChannel = new NotificationChannel(channel_id, "Channel 1", NotificationManager.IMPORTANCE_DEFAULT);
Android actually registers it as
NotificationChannel mChannel = new NotificationChannel(channel_id, "Channel 1", NotificationManager.IMPORTANCE_HIGH);
This means that sounds are played by default, while they should not get played by default at importance level NotificationManager.IMPORTANCE_DEFAULT.
I have the same issue on Nexus 6P and user report about this problem on Pixel XL.
cl...@google.com <cl...@google.com> #12
Here is another report: b/73719217
ya...@gmail.com <ya...@gmail.com> #13
This is till an issue in android p. And the word around is not great (collapsed notifications).
Can we get this fixed for q?
Can we get this fixed for q?
ya...@gmail.com <ya...@gmail.com> #14
hi teams,
Any update this?
(Update 2019-05: It gets worse with Android Q, there I'm even getting a sound when using NotificationManager.IMPORTANCE_LOW, at least in the Emulator...)
https://stackoverflow.com/questions/45919392/disable-sound-from-notificationchannel/45920861
Any update this?
(Update 2019-05: It gets worse with Android Q, there I'm even getting a sound when using NotificationManager.IMPORTANCE_LOW, at least in the Emulator...)
Description
When creating a Notification Channel
NotificationChannel mChannel = new NotificationChannel(channel_id, "Channel 1", NotificationManager.IMPORTANCE_DEFAULT);
Android actually registers it as
NotificationChannel mChannel = new NotificationChannel(channel_id, "Channel 1", NotificationManager.IMPORTANCE_HIGH);
This means that sounds are played by default, while they should not get played by default at importance level NotificationManager.IMPORTANCE_DEFAULT.
When I then go into the Notification Settings via a long-press on the notification, and click on "all channels", I see that channel having "acoustic signal" enabled (translating from German). When I press on that channel to get more settings I can read "Importance: High: Acoustig Signal"
When I now turn that Notification off by switching the toggle above the beforementioned message "Importance: High: Acoustig Signal", and then on again, then the message changes to "Importance: Middle: No sound" This is what NotificationManager.IMPORTANCE_DEFAULT actually is, the middle setting.
If I create the channel with NotificationManager.IMPORTANCE_MIN, then all is OK, it is a "low importance channel".