@agent_libre We’re happy that you’re happy 
We have some AMAZING news! MuditaOS goes from Developer Preview to FULLY Open Source & we’ve also open sourced Mudita Center code!
And that’s not all! I’m not sure if any of your rememmber, but last year, when we made our our initial announcement of going Open Source with MuditaOS, we stated that we’re going to award the people who contribute the most with an actual Mudita Pure phone. We are keeping our promise.
The five Mudita Pure phones will be awarded to the following Open Source contributors (drumroll please
) :
I think we have some forum community members among the winners! Make yourself known & come forward
@sandra is one of the winners! And I see @l1ghthouse made the list as well!
A MASSIVE CONGRATS! is definitely in order!
We are honored by the dedication of these extremely talented contributors and immensely grateful for the time, commitment and enthusiasm involved in undertaking such a project for the benefit of the entire Mudita Community.
Join me in congratulating all the contributors!
A good simple open source OS will also make it easier for other phone manufacturers to make more safe dumb phones. And that’s a good thing.
It will also make it easier for people who still want to use their phones for banking, receiving packages (just like having a key), and maybe even having a simple map.
There are some nice dumb phones out there that I could probably use, but I just don’t trust the OS enough, so I’m really happy about you not only creating this one, but also open sourcing it 

Thank you @urszula!
@Wojciech_Cichon told me about this over email. I had no idea this kinda reward was coming, pretty awesome! I haven’t had time to work on the repo since I got a new day job that I love (but I did just put a new quick PR in this weekend).
@sandra We were so honored that our Mudita Community members were so dedicated & that you were one of the winners!!
If Mudita did add a feature that you didn’t like, there is the possibility to disabling it and compiling the binary for your own device. But it depends how modular their code is, otherwise it could be quite difficult.
Open Source means different things to different people.
For all the talk of developing features, you’ll know as a developer just what it takes to make an app robust, even for a single platform. The best that could be hoped for would be a proof of concept from a forked codebase, the skeleton code for a solid feature, then testing in the wild, with all the bug reports to sift through. Every one and their dog knows that Apple pilfer the black-market community that develops for their iDevices, that’s why they didn’t shut it down - they need to come up with 100 new features each year !
I have been at the sharp end of a company purchased out by another only to find my hardware bricked. Were the source code available I could have revived it (although it did require a third party login, but I could have possibly gotten around that), and if the phone is built well enough, and the demands not too high, the phone should last for a long time.
Then there are the updates that nobody likes, rolling back is impossible in the iOS ecosystem, so don’t discount it. But then again, the code does not need to be open for that, just keep an archive of the version releases available for download.
I would request that features be modular, and easy to disable, or perhaps include, allowing for the user to create a light weight OS. I don’t want a Calendar and a Calculator and all that, just a phone, not much else.
Security auditing costs money and the code does not need to be open for it to be valid (so long as it is a reputable auditing firm), so the main reason for open source for me is to keep the phone alive, after it’s been discontinue or some other unforeseen event.
Hi, thanks for the explanation!
I’d like to tell you that our code is more-or-less modular, so it shouldn’t be much effort to disable particular apps. When it comes to apps, it should be very easy to do in my opinion
- I really recommend taking a look at our GitHub repository and taking a journey into our code.
@Bartosz_sp2fet @urszula Will MuditaOS be open sourced for the Kompakt as well?
Its not really open sourced for Pure and Harmony, but lets hope
(there is github, but its old version and seems not compliable) and not open for modifications
(e.g. improving Pure features)
This is indeed very nice and I am glad to see there are contributors outside company
@tet MuditaOS is the operating system in Mudita Pure & Mudita Harmony. Mudita OS K is the operating system in Mudita Kompakt. So, they are two different systems. At this time, we do not have plans to open-source the Mudita Kompakt operating system. However, if things change in the future, we will definitely let out community know.
That makes sense that they’re two different systems and understandable from the company’s perspective as Mudita certainly wants a very curated experience for the users and this is their flagship product after all.
The hardware does seem to be solid and build to last but with Android ecosystems, it’s usually it’s the software falling out of date that makes devices unusable really.
I do still hope Mudita does consider open sourcing OS K, at least near the end of the device’s 3 year software service lifetime so that the community can continue supporting it. No further Android updates isn’t just not having the odd feature or two not working but we’re talking being unable to sideload most apps or running in to very scary situations where just being connected to the internet is a security risk, reducing the Kompakt to being a cut-down ebook reader really.
The Kompakt ending up being an unusable brick after a while like all the other out of vendor support Android devices would be very sad indeed.
I wasn’t able to find out a definitive answer if the bootloader is unlocked so that’s the other thing, well even if it is I imagine it would be difficult to build a typical community ROM for it due to all the custom e-ink stuff no doubt Mudita had to code in but it’s still an option to rescue the phone.
At least the device has that build-in networking kill switch to safeguard itself whenever that does happen and anyone can do it so that’s a big plus.
With Mudita building up their brand as a sustainable business that supports the right-to-repair and trying to contribute to having less waste in general.e I think building up that reputation that hey, we’re not like everyone else in the Android space that expects you to buy a new phone in 3 years and then the next one and the next one not out of necessity, because you’re forced to so you’re not hacked just by turning it on but out of choice because it’s a good product… it would really solidify the commitment to this and word would spread that Mudita cares.
@tet Thank you for such a well-considered and thoughtful post. You’ve touched on some really important points that we at Mudita are also reflecting on internally. We completely understand the concerns about long-term software support, and we share your belief that sustainability shouldn’t just be about hardware, but also about the longevity and usability of the whole product, software included.
I’m not sure if you know from my previous posts, I actually own & still USE my BlackBerry Q10 from 2013 ![]()
It still takes some pretty nice pix!
Understandable. But since claim for original MOS (Harmony, Pure) is that its open source, please let us know when full latest version open to modifications (in way coders can enhance Pure and Harmony features and test that) is avail.
To my understanding, current situation is that part of OS is open for public at github, while critical components are close sourced, not allowing significant modifications.
This approach was good for user contribution in development phase, but EOL by Mudita could leave it to community enhancements.
Both apps would be most welcome enhancements to Pure
