Infeasible
Status Update
Comments
cl...@google.com <cl...@google.com>
dn...@google.com <dn...@google.com>
dn...@google.com <dn...@google.com> #2
Thanks for reporting this issue.
Can you please provide the below requested information to better understand the issue:
SDK version
Which version of the SDK are you using?
Android build
Which Android build are you using?
Device used
Which device did you use to reproduce this 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.
Can you please provide the below requested information to better understand the issue:
SDK version
Which version of the SDK are you using?
Android build
Which Android build are you using?
Device used
Which device did you use to reproduce this 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.
mg...@gtempaccount.com <mg...@gtempaccount.com> #3
Which version of the SDK are you using?
27
Android build?
Android 8.1
Build Number: OPM1.171019.01
Kernel version: 4.4.88-g2e1fc62d168a(Android clang version 5.0.300080 (based on LLVM 5.0.300080))android-build@wprm6.hot.corp.google.com#1 Sat Dec 23 03:21:18 UTC 2017
Device used?
Pixel 2 XL
Steps to reproduce?
Sadly I can't provide an apk at the moment, but for now I can give you the steps we used to reproduce this issue:
1-Trigger the notification which will behave accordingly to priority set in the channel
2-Go to the device Settings/Apps & notifications/App Info and disable the channel and then re-enable it
3-Trigger the notification again and you will notice that the notification behave as if the channel had been set to default priority
Frequency?
100% of the time
Expected output
It should retain the behavior of the original priority set in the channel
Current output
The notification changes to a NotificationManager.IMPORTANCE_DEFAULT behavior
27
Android build?
Android 8.1
Build Number: OPM1.171019.01
Kernel version: 4.4.88-g2e1fc62d168a(Android clang version 5.0.300080 (based on LLVM 5.0.300080))
Device used?
Pixel 2 XL
Steps to reproduce?
Sadly I can't provide an apk at the moment, but for now I can give you the steps we used to reproduce this issue:
1-Trigger the notification which will behave accordingly to priority set in the channel
2-Go to the device Settings/Apps & notifications/App Info and disable the channel and then re-enable it
3-Trigger the notification again and you will notice that the notification behave as if the channel had been set to default priority
Frequency?
100% of the time
Expected output
It should retain the behavior of the original priority set in the channel
Current output
The notification changes to a NotificationManager.IMPORTANCE_DEFAULT behavior
mg...@gtempaccount.com <mg...@gtempaccount.com> #4
I won't be able to provide an apk but I can provide the sniped of the source code related to the setup of the notification channel and how we build the notifications, please see file attached
mg...@gtempaccount.com <mg...@gtempaccount.com> #5
If you need I can attached a video on how to reproduce this issue
dn...@google.com <dn...@google.com> #6
We are not able to replicate the issue with the sample code shared.
Can you please share complete project/apk to test this issue?
It would be helpful if you share video on how to reproduce this issue.
Can you please share complete project/apk to test this issue?
It would be helpful if you share video on how to reproduce this issue.
dn...@google.com <dn...@google.com> #7
Please provide the information requested in comment #6 to investigate this issue further.
dn...@google.com <dn...@google.com> #8
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.
ka...@gmail.com <ka...@gmail.com> #9
Really? This issue is present in every app i'm using. "MyFitnessPal" "Results" etc. Just downoad one app with notifications, change toggle notification off and on again and you will see -> no notificaiton sound.
[Deleted User] <[Deleted User]> #10
compileSdkVersion 26
buildToolsVersion '27.0.3'
targetSdkVersion 26
int importance = NotificationManager.IMPORTANCE_DEFAULT;
NotificationChannel channel = new NotificationChannel(CHANNEL_ID, name, importance);
Will incorrectly create notification channel with importance high instead of normal.
buildToolsVersion '27.0.3'
targetSdkVersion 26
int importance = NotificationManager.IMPORTANCE_DEFAULT;
NotificationChannel channel = new NotificationChannel(CHANNEL_ID, name, importance);
Will incorrectly create notification channel with importance high instead of normal.
so...@gmail.com <so...@gmail.com> #11
Every app that registers a channel of NotificationManager.IMPORTANCE_DEFAULT gets this wrongly upgraded to NotificationManager.IMPORTANCE_HIGH.
If the Notification is manually toggled off and then on again, it get's downgraded to NotificationManager.IMPORTANCE_DEFAULT and starts behaving correctly.
The only workaround is to create a channel with NotificationManager.IMPORTANCE_LOW.
Saying that "there is not enough actionable information" sounds like a lame excuse. Of course you need to go through the OS's source code to debug this bug. Isn't that the job you get paid for? To implement features and debug them when necessary?
If the Notification is manually toggled off and then on again, it get's downgraded to NotificationManager.IMPORTANCE_DEFAULT and starts behaving correctly.
The only workaround is to create a channel with NotificationManager.IMPORTANCE_LOW.
Saying that "there is not enough actionable information" sounds like a lame excuse. Of course you need to go through the OS's source code to debug this bug. Isn't that the job you get paid for? To implement features and debug them when necessary?
le...@gmail.com <le...@gmail.com> #12
Hi! My App is https://play.google.com/store/apps/details?id=net.wargaming.wot.blitz&hl=ru I always use NotificationManager.IMPORTANCE_DEFAULT but on Android 8.0 devices it starts vibrate or make sound... And You say it is Won't Fix?
People already point out how to hack it -https://stackoverflow.com/questions/45919392/disable-sound-from-notificationchannel
People already point out how to hack it -
da...@gmail.com <da...@gmail.com> #13
This same issue also exists on my app. Also found on other apps I downloaded from the store. Google/Android, Please fix this. Thanks
da...@impalastudios.com <da...@impalastudios.com> #14
Unless you provide an APK google will most likely ignore these kinds of bugs/issues. Setting up a project with notifications literally takes less than 5 minutes. If it really bothers you so much, suck it up and give them a sample app that creates a test notification.
[Deleted User] <[Deleted User]> #15
>>Unless you provide an APK google will most likely ignore these kinds of bugs/issues. Setting up a project with notifications literally takes less than 5 minutes. If it really bothers you so much, suck it up and give them a sample app that creates a test notification.
Are you not able to check the sources?
Are you not able to make a sample code?
Isn't the description of the bug sufficient?
That's really unbelievable to see the approach like that!
Are you not able to check the sources?
Are you not able to make a sample code?
Isn't the description of the bug sufficient?
That's really unbelievable to see the approach like that!
so...@gmail.com <so...@gmail.com> #16
Why should you even need to provide a sample app if every app, even apps provided by Google, like Gmail, are affected by that bug. Just install Gmail and try it out. Well, by now I guess the Gmail app will have it's source code adapted to this new, changed behavior.
Look at thishttps://github.com/googlesamples/android-NotificationChannels/issues/18
That would mean recompile googlesamples/android-NotificationChannels to have the apk for submission and reexplain the problem.
It's odd that this answerhttps://stackoverflow.com/questions/45919392/disable-sound-from-notificationchannel/45920861 has so many upvotes.
We all have settled to use the workaround of using IMPORTANCE_LOW for "Medium user-visible importance level" and IMPORTANCE_MIN for "Low user-visible importance level". That is a disconnect with reality. It's quoted from the table inhttps://developer.android.com/training/notify-user/channels .
PRIORITY_DEFAULT did not make a sound in Android 7.1 and lower.
My rant is regarding this related issuehttps://issuetracker.google.com/issues/65108694
But it's the same underlying problem.
The central thing to that issue is this sentence
> 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"
It clearly states it "Importance: HIGH"... HIGH. As in NOT_LOW, NOT_MIN, when registered as IMPORTANCE_DEFAULT. What source code do you need for that? It's not some kind of corner-case. Doing a pull forhttps://github.com/googlesamples/android-NotificationChannels really ought to be enough.
Look at this
That would mean recompile googlesamples/android-NotificationChannels to have the apk for submission and reexplain the problem.
It's odd that this answer
We all have settled to use the workaround of using IMPORTANCE_LOW for "Medium user-visible importance level" and IMPORTANCE_MIN for "Low user-visible importance level". That is a disconnect with reality. It's quoted from the table in
PRIORITY_DEFAULT did not make a sound in Android 7.1 and lower.
My rant is regarding this related issue
But it's the same underlying problem.
The central thing to that issue is this sentence
> 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"
It clearly states it "Importance: HIGH"... HIGH. As in NOT_LOW, NOT_MIN, when registered as IMPORTANCE_DEFAULT. What source code do you need for that? It's not some kind of corner-case. Doing a pull for
Description
Some of the symptoms seems to be similar to this previous issue