I wanted to build on the thread from a couple weeks ago about /e/ OS support, and also the “What Mudita Should Build Next” post, to suggest a direction I think could be a significant differentiator for a future Kompakt revision.
The idea: For a future hardware revision (2027+), Mudita could consider building on a GrapheneOS-compatible base rather than a custom AOSP fork. This would mean selecting a chipset with the security primitives GrapheneOS requires (proper secure element, verified boot chain, open kernel sources) and using GrapheneOS as the security foundation, with Mudita’s UX layer (Kalm launcher, InkApps, Offline+, kill switches) on top. The base would be a security-hardened AOSP derivative with no Google Play Services, no GMS dependencies, and a verified boot chain — not simply AOSP with Google components stripped out. Essentially – a GrapheneOS Fork
Why this fits Mudita’s existing model:
Mudita already operates an “open core” model — kernel and individual apps are open, product layer is proprietary. A GrapheneOS base is permissively licensed (Apache 2.0), so the proprietary UX layer can remain closed.
The current kernel is only partially open (GPL-required Linux proper; MTK and E Ink drivers remain proprietary). A GrapheneOS-compatible chipset (e.g., Snapdragon with full open-source vendor drivers) eliminates that gap by design — no proprietary display or modem drivers to hide behind.
The brand differentiator (E Ink, minimalism, Offline+) stays fully intact. It just runs on a more hardened base.
I recognize the community has raised concerns about the current OS’s source availability. This proposal isn’t about retroactively open-sourcing MuditaOS K — it’s about making a different architectural choice for the next hardware revision, where the security-critical base is open by design from day one and code ownership is clean.
What Mudita would gain:
Verified boot, attestation, and a security patch cadence without building that engineering in-house
A “GrapheneOS-hardened” trust signal that’s hard for competitors to replicate
Alignment with the privacy-focused buyers who are already choosing the Kompakt
An answer to the “trust us, it’s de-Googled” skepticism that some in the community have raised — verified boot and a public security base provide proof
What GrapheneOS would gain:
A second product philosophy (mindfulness/minimalism) they don’t need to build
Proof the security model works beyond Pixel/Motorola
A new market segment (E Ink phone buyers)
The practical barrier: The current Kompakt’s MediaTek chipset doesn’t meet GrapheneOS’s hardware requirements. This would need to be addressed at the next hardware revision by selecting a compatible SoC (e.g., Snapdragon 7-series with proper SE and open kernel). The current architecture is locked down to the point that even Mudita’s own signed OTA cannot be ADB-sideloaded on a locked bootloader, and community members have stated that even basic GSI compatibility broke after 1.2.0 due to unregistered SELinux labels in the vendor partition. A GrapheneOS-compatible base would make third-party OS support a design goal rather than a regression to be patched.
Proof the hardware is capable: Community members have already demonstrated that a patched LineageOS GSI runs well on the Kompakt’s E Ink display (with UI tuned for low-refresh), confirming the hardware is capable. The blocker is purely the OS/vendor architecture, not the panel.
I’m not asking for this tomorrow. I’m curious: is this a direction Mudita would be open to exploring for a future device? Even a “we’re aware of this and it’s on our radar” from the team would be useful to know.
I think the philosophical alignment between the two projects is strong, and the practical model (open base + closed product layer) is one Mudita already uses.
I believe that Mudita should go 100% in this direction: use GrapheneOS for the underlying OS but with their own EInk UI (similar to how on Linux you can have different window managers off the same base OS).
Clearly the device will become more expensive due to the hardware required but building on GrapheneOS has the potential to lead to a device that can definitely be the only device one needs for most people.
GrapheneOS starting work on their own RCS client is just another example of that. They also have the exposure and the brand to entice more banking / payment apps to work on their platform.
That would be awesome and I’m 200% behind the idea.This would also give a lot more exposure to Mudita in a niche which is probably a good one for the product (the fact that, each time I post that the Mudita is degoogled, many people ask me “what is the Mudita? Hey, I want one too” demonstrate that their is a lot of potential customer in a growing niche that cannot be reached through Facebook ads (which are not very mindful anyway)
But I don’t know if Mudita has the engineering ressources to do that It means working with GrapheneOS team and probably paying them. I’m convinced that, in the long term, that would be beneficial but that would require an extra effort and should probably be also considered as a marketing effort.
Based on what @michalstasiuk said in Call for Transparency - Critical Security and Bug Tracker - #3 by michalstasiuk , we can infer that Mudita is following the NIH route (which is probably not a good thing given that Mudita has probably not too much engineering resources). Switching to GrapheneOS would then require a huge change of mindset followed by a total reorganaization of the engineering. So we can safely assume it is not realistic and will not happen.
Instead of taking an existing OS, trusting it and modifying only the minimal they could, the managed to do it in such a way that they can’t upgrade the OS and have to be everything in-house, probably thinking “at least we have full control” (where, in reality, you are probably lost in the amount of work required)
Kompakt: Simple phone for minimalists, the Mudita OS supports basic needs. Will the company offer a bare bones phone or do we accept the Kompakt as a complete system?
GraphieneOS enthusiasts are looking for a piece of hardware as a home for their preferred OS.
I’ve choose Mudita as a whole package (software and hardware). Over the years, Mudita Team was able to deliver very unique product. The reason why I choose Mudita over the others, was that I believe They will continue to flow this route and I am safe with Them. I do not need all those “upgrades” from GrapheneOS. I am using only stock apps from Mudita and couple additional from f-droid or Mudita community. No internet browser, no emails, no social apps, no banking apps. Just Calm and peace of mind when I am away from my laptop. I do not need anything else. If I ever start to install all other apk, then it is pointless to use Mudita and it will be the time to go back to regular smartphone.
I think GrapheneOS has different principals, goals and It is totally fine. I like when people have a choice to choose proper hardware for them, however it doesn’t mean that all hardware out there should be compatible with certain software.
I love Mudita and I think that idea behind is good. Please let’s keep it that way. If You find that Mudita is too limited, maybe this means that You are looking for something else then?