Sorry, but you were forced to use GPL license for the Pure OS, or am I wrong? It’s based on freeRTOS which was GPL. Because the way you wrote it sounded like you did it voluntarily.
This reminds me to ask some questions again, which no-one from the leading staff, dev or design has answered me, even though one of the most popular topics on this forum since the release of the phone.
Are you guys going to release E-ink modes so we can control the display modes in per-app bases?
Are you guys going to release an SDK so we can access the E-ink modes for the community apps?
(i know you mentioned you’re releasing the design system, but that means nothing to me if it doesn’t explicitly include controlling E-ink modes).
Are you guys going to release the modified Kernel sources, which are an obligation from AOSP?
You guys seem to ignore that most of us bought this phone for the Hardware, and when I say hardware I don’t mean the mt6761 or the 3gb of ram. We bought it for the compact size, e-ink display. And the E-ink display it’s not being utilized to its capabilities.
I’ll tell this one bluntly too:
I don’t think there’s a customer out there waiting for the song search to come in Early 2026. And there’s no other manufacturers out there waiting in line to get the source code of your music player either.
So make your developers life easier, make your customers experience better and use GPL licensed apps.
I think FreeRTOS is under MIT, not GPL. Still, when it comes to GPL, the decision point is at the moment of selecting the baseline project.
The E-Ink driver includes proprietary parts from hardware manufacturer, so we cannot release it.
Having an SDK and a strong developer community around Kompakt is an ideal scenario for us. However, creating and maintaining an SDK requires significant resources, so we’re taking it one step at a time. We’ll begin by releasing the design system and gathering feedback, to see how many developers adopt it. Based on its popularity and impact, we’ll decide how to proceed. I hope we reach the SDK stage.
Of course, we will comply with all license obligations. We’ve reviewed all software licenses used in Kompakt, but I’ll double-check whether there are any kernel changes we’re required to release but we haven’t yet.
I believe this is technically feasible. We’ll need some time to analyze the idea. The development team is currently fully focused on versions 1.2.0 and 1.3.0, so we hope you’ll be patient with us .
You’re correct it seems it’s MIT now, but it was GPL v2 originally so I stand corrected.
With this I meant if you’re going to include the function inside Mudita OS so we can set the modes within the Mudita OS K. Like I can set Gamma mode to Signal so text can be clear but it will still be fast like in Mudita Launcher, and then set reading mode to RSS feeder because It has not animation and it doesn’t need the “fast” mode. Other manufacturer allow to set the refresh rate mode sometimes: Fast, Medium and Slow (like reading mode), and some I forget which brand allow it on per app basis.
I’m not a developer so I may be speaking out of my mind here, but I de-compiled your Mudita Center app, I read through the code with my designer knowledge and was able to include E-ink modes in an app, but obviously they won’t work without the correct signing keys (limited to only your Mudita apps). I see no reason on this limitation, I’m not asking you to give me the driver sources for the E-ink controller, I’m asking if I want to call Reading mode or high contrast (gamma) mode on my app I should be able to do so without having to root my phone and lose the warranty in process.
The only way I’m able to access the meink service is using ADB. It looks amazing, but it only works if you don’t exit/refresh the app or lock the phone.
This bring me back to the essence of the this topic. A lot of the open source apps would be more usable in Mudita Komapkt if you allowed us to designate E-ink modes. Why hasn’t this been a thing from the start I’ll never understand.
This wasn’t even a feature I thought I need to ask your support if it will be there, I took it as a given that E-ink modes will be there on the device.
Are you guys going to release E-ink modes so we can control the display modes in per-app bases?
please correct me if I’m wrong, but isn’t this functionality that’s already facilitated by a service written by Mudita? The Mudita apps must be registering themselves for different e-ink modes, considering that maps operates in a different mode than say chess or settings or etc. It would just need a frontend for users.
The eink controller is already there in the Mudita Service app.
The E-reader is the only one that has the reading mode, the other Mudita apps get the Fast mode with High Gamma, the rest of sideloaded apps only get fast mode.
Which is horrible with the Material Design that most sideloaded apps have, a lot of gray fonts just look so fuzzy it’s hard to read them sometimes…
my point is that I believe that the functionality we want has already been written and it’s how the mudita apps are able to set their display modes. All it would need is a user level stub.
One of the points I would counter and perhaps didn’t make clear in my earlier post is that I don’t just want this phone for the hardware and I don’t think I’m alone. I was specifically looking for a minimalist phone with an integrated approach of design, hardware, operating system and software oriented towards minimalism and intentional usage. While I’m interested in the idea of a design system being released and to develop apps myself for the device, I didn’t buy want to buy a hobby / ‘project’ device, I wanted a finished product and that is what I feel I have with the Kompakt. I’m really happy that Mudita are investing in the OS and software but also open minded to third party apps / contributions. But I appreciate user types and motivations will vary. Just wanted to try to put that point across, as I feel like there is a degree of some people expressing sentiments on behalf of other users when it is clear there are some different type of customer on here. Hopefully Mudita can support as many of them as possible, but they are going to have to make some calls that people aren’t going to agree with.
Just to add on the eink modes - it sounds like there may be a way forward on this. So far from using the Kompakt it’s not even been on my radar as a problem. I’m quite comfortable with the idea supporting sideloaded apps is not a high priority. But they are working towards it with the changes that are coming and it sounds like this eink mode requirement may eventually be satisfied. I just really don’t want this device to become something that is easy to install and use loads of apps on (or easy to hack into doing something it’s not designed for), it’s not what I bought it for, though again I appreciate some may want to install more apps and want them to work better than I do.
.