Hello all,
This is the first time I write here. I guess that you guys have come across /e/ OS and Lineage OS.
In /e/ OS forum I suggested that they supported Mudita Kompakt (along with other e-ink phones) because I saw that their /e/ OS supports Revolut and some banking apps that I use in the Czech Republic.
They asked: “Did those vendors share their source code?“
I sent them these 2 links: GitHub - mudita/MuditaOS-K-Kernel-opensource · GitHub and GitHub - mudita/MuditaOS: Mobile operating system based on FreeRTOS™ optimized for E Ink displays - developed for Mudita Pure minimalist phone · GitHub .
Is there anything else to share? I think you could consider to partnering with them because some people might be interested in getting Mudita and using it with /e/ OS to get access to the banking apps.
I think a dedicated E Ink device for smartphones, like the Bigme Hibreak E Ink would be a better fit than the Mudita Kompakt. Strangely enough, what makes the Kompakt so special are precisely its limitations. If I had /e/ OS on the Kompakt, I’d fall back into my digital addiction in no time. On the other hand, there are enough people that want the Mudita Kompakt as a replacement for their smartphone, so there will certainly be interest in it. Cheers! 
Thanks for your comment. Yes, I’m also considering Bigme (with an opensource OS). Also, suggested the Bigme Hibreak e-ink in the /e/ OS forum. I have a similar problem with the digital addiction. I’d like the banking of a smartphone, only. They have a list of banking apps that work with /e/ OS. So, that is why I got interested.
My friend, I don’t know how to say this in simple terms, but it’s ain’t gonna happen.
They haven’t bothered to fix two things that they broke in vendor after 1.1.1. They added three SELinux labels and forgot to register them, or chose not to (every label has to be declared usable for file labelling, or the policy won’t compile).
Any other ROM rebuilds the policy at boot, hits them, and refuses, which kills plain AOSP GSIs. LineageOS gets past that fine and still won’t finish booting on anything newer than 1.1.1, while the same image boots on 1.1.1 without complaint. So you’re stuck downgrading boot, dtbo and vendor back to 1.1.1, which is a lot to ask of a beginner.
Today I manually downlaoded the 1.6.0 update. (don’t ask how). My IMEI hasn’t been picked for the rollout yet, so I tried ADB sideload instead (on a locked bootloader). And can you believe it, the device won’t flash Mudita’s OWN signed OTA.
I started messing with LineageOS GSI recently, and managed to patch the UI/Settings pretty well to remove all animations, smooth scrolling and the pastel shades. LineageOS Became super usable. I was thinking of starting a proper Kompakt LineageOS GSI build, but as I lack a an x86 Linux machine with a lot of RAM, and the existing issues mentioned above I’m not gonna bother.
p.s The Open Sourced Kernel is not full, they only open sourced the things they’re required (as some drivers might be propritery from MTK/E-ink corporation).
Hey, thank you. Mmm, it’s a shame that it could not be done. I’m not a developer myself, but, I suspect accomplishing what I’m asking would require a big effort.
The source code release thing is also a bummer.
Maybe Mudita could partner with /e/ OS and the Murena and release this as an official support and maybe that way they do not need to release the full code. But, I don’t know. This is a comment coming from a beginner.
The fixes that I mentioned they could do are much simpler, and they haven’t done done them. So I’m suggesting you to keep your expectations low or you’ll get super disappointed. 
Hi Guys,
I am not super detailed in the technical aspects, but a few general comments:
-
We are quite busy with a big improvement coming later this year. Some of the needs should be addressed there. This is keeping us quite busy these days :-/
-
However, the improvements mentioned here, especially broader compatibility with apps like banking apps, are not addressed in the nearest upcoming things we are working on.
-
And one more “however”: broader compatibility is on our priority list after the big stuff coming soon. This has already been decided. As of today, it is still not decided which route we will take, but the topic will be addressed. Just not within the nearest 2 to 3 months, as we have some quite big and, I hope, amazing updates coming in other vital areas.
I am tempted to say more, but I don’t want to spoil the surprise. More information will appear very soon, as the update will be revealed at IFA Berlin in early September.
I hope my answer helps a bit.
I’m one of those who says that compatibility with banking apps or apps that require google play service shouldn’t be in your shoulder at all. I’d even say just make it more obvious to users straight away so they don’t get confused. It seems to me a lot of Kompakt users came straight from Apple, so a DISCLAIMER would help a lot. Same with RCS vague replies, just be straightforward that it doesn’t depend on you.
I have stopped making requests here since pretty much any QOL improvements I’ve shared had been ignored (minus bringing back accessibility permission which came back after a lot of whining).
However I do think you should really fix the compatibility issues that have been caused by 1.2.0-1.6.0 builds. Installing a GSI / LineageOS shouldn’t be this hard. So i really hope you tell your team to fix SELinux policy and other things that broke third-party rom compatibility. (at the moment it requires downgrading to 1.1.1 to be able to do so). Or at least extracting some of the partitions from your OTA builds and flashing only those while keeping the super at current version. (a simpler quicker way, that I’m still not sharing with the public because beginners might brick their devices).
And please fix the “non-editable” Bluetooth and Device names (which you can’t even edit with ADB) because it will restore it’s Kompakt name after a reboot. This is not mindful at all, it’s a privacy/security issue.
Lastly I must say I’m a big fan of your other work/companies. With CD projekt red and GOG I’ve gotten world-class quality products, with the Kompakt I don’t think it comes even close.
@Michal_Kicinski Any hints? Is the big improvement some sort of microg integration? Update to the android version? I’m very curious