@fastmango Could you please be more specific as to what you would like to know more about, that has not been covered with official statements by @michalstasiuk our Managing Director.
He pretty much covered all of it here:
there was also discussing there Mudita will not be updating to AOSP 13
Additionally, as per the roadmap, security patches are included in the release of 1.5.0
Let me know if there is anything specific that was not addressed. Perhaps I might have missed it.
I have been giving some more thought to the subject of AOSP security updates on the Kompakt. When this subject was first raised many months ago, I was of the opinion, that if sensitive apps and information were not on the device, then the threat from exposed security vulnerabilities was low, and this is something I still maintain.
I donāt have banking apps or online account password databases anywhere on my Kompakt, so I consider my threat model to be low.
Unlike many people who own the Kompakt, I only install the basic apps I need. Over the past few days I have been looking into what other companies who run older AOSP versions on their devices do in terms of patches.
It seems you either get a handset that is fully locked down to prevent users introducing security issues by loading apps that require additional protection, or like most, security patches are sporadic, and focus on the core functionality that their specific device ships with out of the box.
To me this seems logical, Mudita would require a huge team of software developers to accommodate patching every possible vulnerability / software risk scenario introduced to the Kompakt by the installation of added apps and software.
Mudita have actually posted updates faster and more frequently than most of the other manufacturers I have looked at.
so although it may not appear to be the case they seem to be using a similar approach to and reacting faster than most other manufacturers.
@sundancermartin Thanks for this take 
Much appreciated.
Hi all! First time poster here and tinkerer. Has anyone else previously had an issue trying to install the 1.1.1 version of MuditaOS step?
Iām stuck in a loop of adb not having permissions to apply the sideload from ADB (1.1.1_ota.zip). Adding USB debugging permissions in dev mode and using adb reboot recovery (requires USB debug permissions to run from PC) functions just fine, but once it boots up in recovery, the permissions seem revoked (yes, Iām hitting the checkbox to remember device).
With about an hour of tinkering, there was ONE time I did get past this loop, where I applied the _ota.zip file, and got an error/aborted message at about 50% completion, that it is too old of a version and being denied (I believe it said by the bootloader?). Could this be because Iām on the NA version, and/or updated to MuditaOS 1.5? Thanks in advance for any tips, etc.
Thank you for the guide and all the work, by many folks, to get this all working! I was worried I couldnāt get it working after several folks posted issues with the fastboot loop nāat. But I was able to successfully flash and boot into Lineage following the instructions with a few adjustments, noted below.
Rollback partitions to 1.1.1
After rolling back to 1.1.1 (Step 2) I had to restore my original modem partitions from the backup in order to get the phone to connect to my carrier (initially I did not do this and once in lineage I had no SIM registered was unable to add either a physical or eSIM). I did this via mtk_gui and wrote the md1img_a.bin and md1img_b.bin partitions I had from firmware 1.5 without any issues. I booted back into 1.1.1, made sure I was on my carrier network before moving on to flashing the GSI.
Step 3: Flash the GSI
I used @esquared ās solution:
fastboot --disable-verity --disable-verification flash vbmeta --slot=all vbmeta.img
I tried erasing the system partition, but then had issues flashing lineage
I tried both Lineage 20.0 and 21.0 with gapps - both wrote without issue and seemed the same to me in terms of speed - ie a little slower than stock but overall great!
I didnāt know where to post this, but since this can only be done when rooted I thought this would be the best place.
Doing some tests I discovered the images for power off, sleep screen (or what users here call lock screen due to the lock icon) live in Kernel. Four of them: sleep screen with the padlock, logo, powered off, and flat battery. Plain 480Ć800 bitmaps, no files anywhere. (drivers/misc/mudita/eink/).
Problem is you canāt just rebuild the kernel with your own. Muditaās published source is missing the eink/ folder that holds them. So the workaround is a small Magisk-loaded kernel module that swaps them in memory at runtime. Reboot restores the originals, so it re-applies each boot.
You can also tell the kernel to paint the power off image any time, and it doesnāt actually power off, it just draws. So that slot works as a repaint channel, letting notifications show up on the sleep screen without waking the phone. (kinda like an Always on display, which this technically itās not).
Hereās a demo of my custom locked screen on the left, and it updates when I receive any notifications.
In addition to the text notification it turns on the LED (green for whatsapp, blue for signal and red for anything else).
Battery cost for these features is negligible. Nothing runs on a timer, the screen only draws when a notification arrives, which already wakes the phone anyway. Once itās drawn the phone goes straight back to sleep. The LED draws almost nothing and switches off as soon as you check the phone or you view the notification in aother device (phone, pc).
Please donāt ask for a tutorial, this was just to show that the sleep/locked display can do much more than just show you a lock icon.
I had made an app in the past to do this! Same rough requirements.
Uh I had missed this before very cool!
Iām not sharing mine as it is tied all in one to the notifications/led light and I donāt want users to brick their phones doing something wrong.
Let me know if you have a chance to test my method for installing LineageOS on your device.
I want to try LineageOS 20, as I am not happy with the progress on Mudita OS K over the last months. After following the instructions, I end up in orange state or in fastboot mode or in red state, which happens when I lock the bootloader again after installation of LineageOS. Nothing dramatic so far, as I am able to get back to OS K 1.6.0 with the backup all the time. But Iām wasting hours over hours without success. Probably it is just a simple thing and one step missing or wrong from my side. I already followed the additional instructions posted by @pdsluk and installed files on both slots, but no improvement so far. Iām not sure if he erased the system before installing LineageOS or not. This is something that I didnāt test yet, but will do it in next trial.
I want to install system file lineage-20.0-20251021-UNOFFICIAL-arm64_bgN-vndklite-signed.img on a global Kompakt.
I have the feeling that sideloading a custom ROM was easier some years ago, when there didnāt exist this A/B thing.
I hear ya, it was WAY easier years back. I am in the category of tinkerer who knows just enough to trial and error my way through other peopleās work but I only have a loose grasp on how these things work. I spent an embarrassing amount of time first rooting and installing microG to get AndroidAuto working, then pivoting to LineageOS in order to be able to use RCS. I can run through the process again and add notes.
For those who have Lineage working, howās the experience so far? How does the battery usage compare to MuditaOS? Iām not thrilled with the MuditaOS but I love the device so Iām strongly considering making the switch. I do love not having to charge my phone every night, though.
Wait. You can use RCS on Lineage?
I donāt track battery usage much, Iād say I can get a day and a half per charge if I am listening to a couple hours of audiobooks and my usual light texting. Overall itās definitely sluggish, but doesnāt seem way slower than MuditaOS to me. I like it much better than stock, and find it hits the sweet spot for me of still being a smartphone, but one that is so much less appealing to use for browsing/endless scrolling that my daily usage is minimal.
Yep! Though you need to use Play Services. My understanding is that microG wonāt cut it. Fair trade off for me, missing text messages was super frustrating, and the whole MMS run around with existing groups felt unworkable.
Do you have a more detailed guide on how to get rcs enabled? Had to stop using my Kompakt because of mms issues but would love to start using it again.
Hmmm. I wonder why I couldnāt get it working after rooting. I do have Play Services installed. Itās been more of a pain than usual to not have RCS: I had a family emergency recently, and everyone kept texting me documents and things that I couldnāt read. I tried to get people to email me instead, but they either forget or it just doesnāt sink in.
How is it sluggish? Do you have animations disabled?
I flashed lineage-20.0-20251021-UNOFFICIAL-arm64_bgN-signed, installed Messages, and RCS just worked. I donāt know if it matters, but I initially set up Lineage & enabled RCS Messages without root, then later rooted.
Sluggish like many apps are slow to open, there are delays in loading new screens, canāt type as fast as a traditional phone - things like that. Itās tolerable, but noteworthy. I do have animations disabled and used sal-melliculusā settings.
Will be interested to see if anyone else is able to get rcs working, if that happens Iām going to take the plunge and try this out
Another question for those that got it working: What happens when you use the Offline+ button now? My understanding was that some things are killed via hardware and others are killed via software, so Iām curious of the software side still works under Lineage.
