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.