No, the problem continues. Or better again. I had a workaround from Jolla Support. The file /usr/share/lipstick/androidnotificationpriorities to supplement an entry for my messanger blabber.im. That worked. The upgrade has reversed the change to the file again.
Perfect!!! This workaround works perfect! This is exactly what I’ve been looking for!
In /usr/share/lipstick/androidnotificationpriorities I added the lines
Delta Chat;chat,chat_exists
package:chat.delta;chat,chat_exists
And voilà: The notification on the lock-screen and the LEDs work perfect!
Thank you very much for sharing!
2 Likes
Do you know how can I identify in which package my Android App is? I want nextcloud talk to add it to lipstick. Thank you!
Hey Calinutzzz,
after installing you can find the app package name here:
/android_storage/Android/media
in case of Nextcloud talk it should be: com.nextcloud.client
So the whole entry should look like this:
Nextcloud Talk;chat,chat_exists
package:com.nextcloud.client;chat,chat_exists
Please do not forget to restart your device to let this change take effect.
Please give feedback if it worked!
Good luck!
2 Likes
Thank you very much! That was it!!!
Thank you. I created the same topic 8 days before you and get an answer only here)))
But I have all notifications but haven’t sounded.
how is the step by step of this process? I will love to connect Molly with lipstick. thanks
I cant really rewrite the file. I dont know how to do it, eventhough I am in root through my PC
How would I do this kind of entry for the Tesla app? It would be nice to have notifications about running the alarm or if charging would have stopped.
Thanks for figuring this out! 
I guess that you have ssh working and are logged in in terminal, right?.
To get root access, you would have used
devel-su
To edit the file, use vi. It is the predecessor to vim, but works well enough. Copy & paste the last entry and edit it with the commands available in vim. For me this is the fastest way.
The command would be: vi /usr/share/lipstick/androidnotificationpriorities.
Go to the end of file with [G], then add [a] two lines (with enter). Press [Esc] to finish edit mode, use the mouse to copy and paste the last lines, use [x] to delete single digits and input [i] to edit the last two lines so you have your entry fixed.
I hope that this helps.
1 Like
Something strange is happening.
I have another Phone and now the Sailfish Version is 4.3.0.15, and I did the same thing and it is not working 
Could it be something wrong in the Android Nextcloud Talk App? I do not remember which version I used before.
Do you have any hint what can I check more?
Thank you!
I’m having the same issue with Home Assistant but there is no package name in /android_storage/Android/media
Can I reference the whatsapp package instead and use that?
To find the package name, I used top from a shell on SFOS and stress the UI of the targeted Android app while looking top output to catch the CPU consumer.
The package name is the command name (ie. the COM. column in top).
Moving to Threema Libre on a phone with Android App Support 10 (4.4.0.72 (Vanha Rauma)), I had to use the workaround documented here, to get the LED light blue for a new message.
- (Prerequisite): Developer mode, enabled, using ssh access and devel-su priviledges.
- Find the application identifier, using “top” and “ps -Af”:
ch.threema.app.libre - add the folloging lines in the file
/usr/share/lipstick/androidnotificationpriorities:
Threema Libre;chat,chat_exists
package:ch.threema.app.libre;chat,chat_exists
- restart device
It does not look to be a defect, but it seems that in general this is the file that controls if an android application can use SFOS LEDs for notifications.
Thanks for all hints in this thread!
2 Likes
To all: In the pull request, it was explained that an improvement is on the way for the system, so that with future versions it is not necessary anymore to list each android application in a file as described above. I’m looking forward to it. 
@thigg thanks for the pr.
Thanks for all of the discussion on this. As you point out @ber, and as explained by @pvuorela on the PR, the approach is changing and it should fix this issue in the next major release. I’ve therefore tagged this as “fixed”.
It would be great if you could please test it again after the release to check it then works as expected, and report back here.
To kick this off again.
I cannot get and audio alerts with notifications on the Home Assistant app.
Should the “fix” mentioned above have sorted out this problem or is there another issue I need to look at?
I tested the notifications from WhatsApp and Signal on an Xperia 10 III running the upcoming 4.6.0 release (the next after 4.6.0.13).
I sent pictures via the two apps to the phone. In all cases, the phone indicated the incoming messages in these ways:
- sound and vibration
- banner at the top of the display
- blue LED blinking first, then steady blue light
- item in the Events view.
There should not be any fixes for this issue after 4.6.0.13, though. The already published 4.6.0.13 should work in the same way.
Does anyone (in addition to Alan) have problems with the notifications on 4.6.0.13?
1 Like
Just clarify, it’s only the audio part of the notification that I’m not getting. The notification works otherwise.