I’ve had two issues with the SD card - 1) formatted exFAT and became a non issue, 2) I pulled it out while it was downloading maps and corrupted a few files. Ran lsblk in the terminal, fixed files and it was good to go.
Only to say, SD card has been awesome - using a little over 60 of a 512 - mostly music (and maps).
Does your SD regularly show O?
I actually still go to AAA for paper triptiks. I also have a North America road atlas in the car - when possible, I avoid digital maps. Apparently flock cameras also pick up cell signals and info. Offline + switch, drive, paper maps - moments to enjoy.
Funny.- I have not been looking for updates and this one just popped up. I was expecting end of September 
Updating as I type - we will see if I get the number shield. The off vibrations with alarm is NICE. Going from win to win…thank you Team Mudita!
Edit: As a PS, I got the badge on the phone icon that say 9+ even though I do not have any unread/unheard messages. Not sure if it goes to 10 - we shall see
The VM tally includes un-listened to deleted voicemails, they still count toward your storage quota until you permanently clear them from your deleted or trash folder.
My voicemail is empty and I have +1 stuck. I am sure if I cleared cache or storage on the phone app that it would probably be fixed going forward. They must have missed some kind of migration.
Yes. Missed something with the VM tally or included something extra. A large population of people here reporting an incorrect voicemail tally. I think it could also be carrier related, delete is a flag for the record, permanent deletion is another step. Similar tally issue with missed calls.
I just did a factory reset on this manner and it solved the problem with the permanent notification badge. It seems to be back to normal now. Other option (maybe less drastic) could be to clear the call history via ADB (but I do not know if it helps).
Checking and emptying my mailbox and also the workaround with blocking/unblocking a number (as recommended in the context of issues with the SMS app) did not help.
Yep, I have zero voicemails and no unread messages. Clicked on all miss calls. Maybe I’ll try a factory reset as suggested by @mamue
I just cleared call history via ADB and it cleared the 9+ icon on the launcher. Will see what happens when I get a new voicemail
Just did the same but I think it is going to come back. Digging through the call log over ADB, I found that the badge is counting every call the phone considers ‘unseen’ rather than just missed calls. My missed calls were all correctly marked as seen, but hundreds of ordinary incoming and outgoing calls were not, and clearing those flags made the badge disappear instantly. If the phone keeps marking normal calls that way, the count will simply climb back to 9+ over time. We shall soon know…give it a few days
What is the adb terminal command for this procedure (I use Debian 13)?
I did the following on Fedora 44. Make sure you have developer options and debug via USB authorized.
adb shell content query --uri content://call_log/calls --projection _id:date:type:new:is_read > calllog-before.txt
grep -o 'type=[0-9]*, new=[0-9]*' calllog-before.txt | sort | uniq -c
Type codes: 1 incoming, 2 outgoing, 3 missed, 4 voicemail, 5 rejected, 6 blocked. On my phone every missed call was already new=0, while hundreds of incoming and outgoing calls sat at new=1.
adb shell 'content update --uri content://call_log/calls --bind new:i:0 --bind is_read:i:1 --where "new=1"'
adb shell content query --uri content://call_log/calls --projection _id:type:new:is_read | grep -o 'new=[0-9]*' | sort | uniq -c
Badge cleared immediately, no reboot required, and no call history was deleted.
PS: This only clears the flags. It does not fix the underlying issue (if there is one). Bottom line: I expect the count to come back..
Very late edit: the count never came back. It stayed clear. Once again, I was wrong but happily so.
Is this a one time clean up of flags or regular maintenance a Kompakt user needs to do?
Not sure. It could be it just flagged all calls that were there at the time of the upgrade. I, or we, will know in a few days if this has to be a regular cleaning until the next update. Need to see if incoming calls get flagged. My guess is that it will be a regular cleaning until the next update.
@urszula maybe the team can tell us? Either way, LOVE no vibrations on alarm. That alone is worth the update.
I went through the painful task of clicking on every single call and the call history between those calls, still does not get rid of the notifications. I think it’s a bug but maybe there is something I missed
Same here, no update at all for mine.
I’ve reached out to the team about these notification & they are investigating the issue. Thank you for flagging this.
Our team is currently looking into the notifications issue on the PHONE app. They are troubleshooting it as I write this.
While they are troubleshooting, please also remind them to remove the new vibration that happens exactly while typing in the pin numbers right after turning on the phone. That vibration wasn’t there before the update and is totally unnecessary.
@jppelt Our team is currently troubleshooting this issue. Once they know more, I will share it here.