MuditaOS K 1.6 Rollout Has Begun

Clearing Recent Calls should be a button.
Yes, a Kompakt user needs to have Android development skills.

1 Like

I’m sorry, but I don’t think we’re on the same page :slight_smile: I have absolutely no idea what you’re trying to do in the Notes App. Do you see a text-selection “Select all” command somewhere, despite Notes not having a dedicated Select All feature? I’m confused.

I think the technically easiest fix is to do a factory reset but you’ll lose your contacts and pictures. You could save all those prior to the reset. Once reset, other posts suggest the problem goes away. I know that since I cleared via abd, the problem has gone away. Not sure why it was a one time thing. Fingers crossed.

2 Likes

I decided to go for it. I’ve never used adb before now. I had chatGPT help me a bit on where to get the download, how to enable Debug over USB on my phone, all that jazz. Followed some of @jppelt comments (thank you) about how to issue the adb commands, although I’m on windows and not fedora, so I don’t think I can do the ‘grep’ stuff.

Before upgrading, I wanted to get a baseline:

I connected my kompakt to laptop via USB cable, and ran this adb command from where I unzipped the adb sdk:

adb devices

That prompted my Mudita Kompakt to ask me for permission. I approved permission.

Before I applied the upgrade I ran this adb command to generate a report of my mudita call history:

adb shell content query --uri content://call_log/calls --projection _id:date:type:new:is_read

Then I ran it again to save that output to a file for later compare or review:

adb shell content query --uri content://call_log/calls --projection _id:date:type:new:is_read > calllog-1.5-before-upgrade.txt  

Used chatgpt to give me a breakdown of the output and ‘type’ meanings:

Call type Count Typical state
Incoming (type=1) 75 new=1, mostly is_read=NULL count 75
Outgoing (type=2) 153 new=1, mostly is_read=NULL count 153
Missed (type=3) 27 new=0, is_read=1 count 27
Rejected (type=5) 18 new=1, is_read=1 count 18
Blocked (type=6) 2 new=1, is_read=NULL count 2

That above is my baseline.

Then I applied the 1.6.0 Update

It shows (9+) on my phone icon and wouldn’t dissapear after going into phone app and viewing call history.

Then I ran this command to see generate a fresh post upgrade report:

adb shell content query --uri content://call_log/calls --projection _id:date:type:new:is_read

Ran that again to save the output to a file for later compare or review

adb shell content query --uri content://call_log/calls --projection _id:date:type:new:is_read > calllog-1.6-after-upgrade.txt

The output showed that the calllog didn’t change at all during the 1.5.0 → 1.6.0 upgrade. The before and after calllog report were identical. That’s good. That means the 1.6.0 did not mark a bunch of old calls as unread. Instead it appears that 1.6.0 changed the notification logic so that it now counts old calls that were already with new=1.

As you saw in my baseline report, I had lots of type=1, new=1 or type=2, new=1.

The fix:

So I then ran the same non-destructive fix @jppelt used to simply change the old call-log records from new=1 to be new=0

adb shell "content update --uri content://call_log/calls --bind new:i:0 --bind is_read:i:1 --where "new=1""

The phone icon no longer shows 9+ after that above command, post upgrade.

That should:

  • keep all your call history;

  • keep all contacts;

  • not touch SIM data;

simply changes the old call-log records from new=1 to new=0.
Now time to enjoy my phone

thank you

2 Likes

The culprit is this.

Mudita added voicemail notifications and on top of that added rejected calls notification which on the phone app still says Missed Call but android treats it differently.

So Mudita added rejected call notification but previous Mudita OS K didn’t have rejected call notification, however people had rejected calls before. Update 1.6.0 comes, those rejected calls that weren’t a notification become a stale notification that the phone app / mudita launcher doesn’t clear even when you open recents calls.

I’ve tested this by downgrading the phone and mudita launcher apps to the previous version.

This can be fixed by an APK update of the phone/launcher. However Mudita still hasn’t stopped the rollout, so this might be another bug like the Camera/Offline switch fiasco.

You know what’s not mindful?

  • Having to use adb/developer options/ or factory reseting the device to remove a stale notification.
6 Likes

Nice! Great you checked prior to the update. Not a programmer so I do not know why it appears to change all to “1” as a one time thing. Ever since I “cleared” it, it works perfectly. And yep, grep would not work on windows.

1 Like

does doing a factory reset delete your contacts?

2 Likes

Yes. And any pictures or files you might have - unless they are on the external SD.

2 Likes

I’m glad you are getting involved as this is above my level. I rejected two calls recently after clearing but the badge did not come back on. Would that change your theory?

1 Like

Because the new phone/launcher update knows those are fresh rejected calls and counts them properly.
The issue is during the upgrade the old reject calls (which weren’t counted as a separate notification) were imported into 1.6.0. But the phone/launcher doesn’t recognize them as “viewed”.

So it’s specifically old stale rejected calls, not new ones. New ones (after the update) will be cleared properly.

6 Likes

How is it possible that the update is still being rolled out even though the first issues have already been reported here? Why aren’t they stopping this, but instead letting even more users run into these problems? I think that’s really irresponsible!

4 Likes

New releases will always have some unforeseen issues. If it’s an update that bricks your phone, I can see stopping a rollout, but not for something that’s inconvenient or annoying but harmless.

9 Likes

Totally agree. The joy of the experience far outweighs the silliness of the 9+ shield. Apple iOS has had more than one failed updates - crashing and basically bricking the phones.

2 Likes

I honestly don’t understand all the hate directed at the Mudita developers.

When I bought this phone, I was perfectly aware that I wasn’t going to get the same level of smoothness, speed, and stability as a product like my (now unused) Google Pixel 9. Nobody forced me to buy this phone, and I have to say that it was one of the best things I could have done for my mental health.

In the past, I had tried using app blockers on my Pixel 9, but in the end my addiction would always shift to something else: WhatsApp, using ChatGPT, or even something as simple as endlessly scrolling through the photos in my gallery.

I had also tried buying a dumbphone, but with very little success.

With this device, however, I have finally been able to reclaim a little bit of my mental health. Sure, I don’t have any particular needs beyond making calls, sending SMS messages, and using WhatsApp occasionally (it’s the only app I have installed), but that is exactly what I was looking for in a phone.

And the fact that a relatively “unknown” team like Mudita is able to provide me with this experience is honestly fantastic. Sure, there are a few minor and annoying bugs, but I can live with them without any problems.

So, for whatever it’s worth, I think the team is doing a great job. Expecting a few bugs after an update is, in my opinion, perfectly normal. It happens all the time across pretty much every industry.

But that doesn’t mean the product is a failure. Quite the opposite.

12 Likes

Nobody is hating the developers. What we’re hating is the stretch of 1 line of code fixes into a year of updates.

  1. The option to clear call history (which would have fixed this bug) is literally one line addition in the manifest.
  2. The option to uninstall apps (which should have been there from the moment they allowed third-party app installations), is literally one line addition in the manifest.

These have been added to the roadmap for 2026. Literally 2 lines of text, just so someone can say we provided X years of updates.

Bugs happen, the call number bug is no big issue at all to me personally I wouldn’t even bothered to make a comment about it. What that bug speaks about is the lack of testing. A single rejected call from previous versions of the Mudita OS K and that bug would have been caught. A single one.

6 Likes

I’m hitting a 1.6 bug which is even more severe than the phone notification problem:

2 Likes

Has the Update been pulled? Havent recieved it yet and want to be sure all the bugs mentioned above is fixed before i update.

2 Likes

I am curios to know about that too. My mac is waiting for macOS 27, so i have two excitements. I do not think i resist it. :face_savoring_food:

1 Like

I just tested this and strangely this doesn’t happen to me, I can still turn Offline+ on and off normally. So once again there are bugs that affect some users, but not all. Mindfulness as usual ? :confused:

2 Likes

Legitimate frustration is not the same as hatred. Nobody is expressing that to anybody. I am sure Mudita will fix this quickly.

3 Likes