starred/ntfy

Fork 0

mirror of https://github.com/binwiederhier/ntfy.git synced 2026-05-09 08:26:00 +02:00

[GH-ISSUE #520] Listening notification isn't minimised #398

New issue

Closed

opened 2026-05-07 00:23:49 +02:00 by BreizhHardware · 7 comments

BreizhHardware commented

2026-05-07 00:23:49 +02:00

Owner

Originally created by @alexhorner on GitHub (Nov 27, 2022).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/520

Quasseldroid, Conversations and Automate as you can see in my screenshot have their notifications minimised by default. I believe Quasseldroid and Conversations are open source so maybe that could be of help for reference? As you can see, I have manually minimised the listening notification.

Originally created by @alexhorner on GitHub (Nov 27, 2022). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/520 ![Screenshot_20221126_201534_Nova7.jpg](https://user-images.githubusercontent.com/33007665/204114497-feb56205-d671-46c9-a861-280567448a5e.jpg) Quasseldroid, Conversations and Automate as you can see in my screenshot have their notifications minimised by default. I believe Quasseldroid and Conversations are open source so maybe that could be of help for reference? As you can see, I have manually minimised the listening notification.

BreizhHardware

2026-05-07 00:23:49 +02:00

closed this issue
added the
enhancement

android-app
labels

BreizhHardware commented

2026-05-07 00:23:50 +02:00

Author

Owner

@s-h-a-r-d commented on GitHub (Nov 27, 2022):

Could it be that you are mixing the listening notification with the regular one? In your screenshot 4th notification from the top is the one that is the listening and it seems to be minimized. The topmost is not the listening notification, but the actual notification.

@s-h-a-r-d commented on GitHub (Nov 27, 2022): Could it be that you are mixing the listening notification with the regular one? In your screenshot 4th notification from the top is the one that is the listening and it seems to be minimized. The topmost is not the listening notification, but the actual notification.

BreizhHardware commented

2026-05-07 00:23:50 +02:00

Author

Owner

@alexhorner commented on GitHub (Nov 27, 2022):

Could it be that you are mixing the listening notification with the regular one? In your screenshot 4th notification from the top is the one that is the listening and it seems to be minimized. The topmost is not the listening notification, but the actual notification.

No, I just worded it poorly last night. Please see my updated description.

@alexhorner commented on GitHub (Nov 27, 2022): > Could it be that you are mixing the listening notification with the regular one? In your screenshot 4th notification from the top is the one that is the listening and it seems to be minimized. The topmost is not the listening notification, but the actual notification. No, I just worded it poorly last night. Please see my updated description.

BreizhHardware commented

2026-05-07 00:23:50 +02:00

Author

Owner

@binwiederhier commented on GitHub (Nov 28, 2022):

I looked again and I cannot find a way to programatically do this. I even looked at the Quasseldroid source code and I can't find anything special that they are doing. Some Stackoverflow answers even suggest that it's not possible at all.

@binwiederhier commented on GitHub (Nov 28, 2022): I looked again and I cannot find a way to programatically do this. I even looked at the Quasseldroid source code and I can't find anything special that they are doing. Some Stackoverflow answers even suggest that it's not possible at all.

BreizhHardware commented

2026-05-07 00:23:50 +02:00

Author

Owner

@alexhorner commented on GitHub (Nov 28, 2022):

I looked again and I cannot find a way to programatically do this. I even looked at the Quasseldroid source code and I can't find anything special that they are doing. Some Stackoverflow answers even suggest that it's not possible at all.

Might it be this? https://git.kuschku.de/justJanne/QuasselDroid-ng/-/blob/main/app/src/main/java/de/kuschku/quasseldroid/service/QuasseldroidNotificationManager.kt#L276

@alexhorner commented on GitHub (Nov 28, 2022): > I looked again and I cannot find a way to programatically do this. I even looked at the Quasseldroid source code and I can't find anything special that they are doing. Some Stackoverflow answers even suggest that it's not possible at all. Might it be this? https://git.kuschku.de/justJanne/QuasselDroid-ng/-/blob/main/app/src/main/java/de/kuschku/quasseldroid/service/QuasseldroidNotificationManager.kt#L276

BreizhHardware commented

2026-05-07 00:23:51 +02:00

Author

Owner

@binwiederhier commented on GitHub (Nov 28, 2022):

I tried it in the emulator, and .setPriority is deprecated and (according to the docs) is ignored. Though in actuality, .setPriority(Notification.PRIORITY_MIN) will just make the foreground notification not show up at all (on SDK 33), similar to when it is swiped away.

The Android docs also discourage the use of minimum priority:

If the action is of low enough importance that you want to use a minimum-priority notification, create a background task instead.

The status bar notification must use a priority of PRIORITY_LOW or higher. If your app attempts to use a notification that has a lower priority, the system adds a message to the notification drawer, alerting the user to the app's use of a foreground service.

I think it's not entirely inconceivable that the System UI decides to minimize the Quasseldroid notification because it is low priority and you have many other ongoing notifications.

I think I'm going to call it a day trying to minimize this by default. I'm happy to try out ideas, but I don't want to spend more time on it.

@binwiederhier commented on GitHub (Nov 28, 2022): I tried it in the emulator, and `.setPriority` is deprecated and (according to the docs) is ignored. Though in actuality, `.setPriority(Notification.PRIORITY_MIN)` will just make the foreground notification not show up at all (on SDK 33), similar to when it is swiped away. The Android docs also discourage the use of minimum priority: > If the action is of low enough importance that you want to use a minimum-priority notification, create a [background task](https://developer.android.com/topic/performance/scheduling#categories_of_background_tasks) instead. > The status bar notification must use a priority of [PRIORITY_LOW](https://developer.android.com/reference/androidx/core/app/NotificationCompat#PRIORITY_LOW) or higher. If your app attempts to use a notification that has a lower priority, the system adds a message to the notification drawer, alerting the user to the app's use of a foreground service. I think it's not entirely inconceivable that the System UI decides to minimize the Quasseldroid notification because it is low priority and you have many other ongoing notifications. I think I'm going to call it a day trying to minimize this by default. I'm happy to try out ideas, but I don't want to spend more time on it.

BreizhHardware commented

2026-05-07 00:23:51 +02:00

Author

Owner

@alexhorner commented on GitHub (Nov 28, 2022):

I tried it in the emulator, and .setPriority is deprecated and (according to the docs) is ignored. Though in actuality, .setPriority(Notification.PRIORITY_MIN) will just make the foreground notification not show up at all (on SDK 33), similar to when it is swiped away.

The Android docs also discourage the use of minimum priority:

If the action is of low enough importance that you want to use a minimum-priority notification, create a background task instead.

The status bar notification must use a priority of PRIORITY_LOW or higher. If your app attempts to use a notification that has a lower priority, the system adds a message to the notification drawer, alerting the user to the app's use of a foreground service.

I think it's not entirely inconceivable that the System UI decides to minimize the Quasseldroid notification because it is low priority and you have many other ongoing notifications.

I think I'm going to call it a day trying to minimize this by default. I'm happy to try out ideas, but I don't want to spend more time on it.

No worries, totally understand. I'll have a play around I think and see if I can be of any further assistance but thank you very much for taking a look

@alexhorner commented on GitHub (Nov 28, 2022): > I tried it in the emulator, and `.setPriority` is deprecated and (according to the docs) is ignored. Though in actuality, `.setPriority(Notification.PRIORITY_MIN)` will just make the foreground notification not show up at all (on SDK 33), similar to when it is swiped away. > > The Android docs also discourage the use of minimum priority: > > > If the action is of low enough importance that you want to use a minimum-priority notification, create a [background task](https://developer.android.com/topic/performance/scheduling#categories_of_background_tasks) instead. > > > The status bar notification must use a priority of [PRIORITY_LOW](https://developer.android.com/reference/androidx/core/app/NotificationCompat#PRIORITY_LOW) or higher. If your app attempts to use a notification that has a lower priority, the system adds a message to the notification drawer, alerting the user to the app's use of a foreground service. > > I think it's not entirely inconceivable that the System UI decides to minimize the Quasseldroid notification because it is low priority and you have many other ongoing notifications. > > I think I'm going to call it a day trying to minimize this by default. I'm happy to try out ideas, but I don't want to spend more time on it. No worries, totally understand. I'll have a play around I think and see if I can be of any further assistance but thank you very much for taking a look

BreizhHardware commented

2026-05-07 00:23:51 +02:00

Author

Owner

@binwiederhier commented on GitHub (Nov 28, 2022):

I'm gonna close this for now, but if there is any new info, please do not hesitate to comment. We can always re-open the ticket.

@binwiederhier commented on GitHub (Nov 28, 2022): I'm gonna close this for now, but if there is any new info, please do not hesitate to comment. We can always re-open the ticket.

BreizhHardware referenced this issue

2026-05-07 00:26:46 +02:00

[GH-ISSUE #1009] Feature request: Allow hosting / running the web app in sub path #707