I’m sorry but these phones have been ready to ship in Poland for months, they’ve had MONTHS of time before the devices were built to develop the handful of apps they have, getting a working keyboard is not rocket science, it isn’t anything special, you are giving them too much credit.
I will only be frustrated by things that should be done correctly, there really isn’t anything new whatsoever about the software here, so your comment is completely misplaced
I have never done what they have done so I am not going to assume anything my friend. 
My sense is you are not going to be happy with the journey you will have to take with this device, maybe best to look elsewhere my friend
I have no issue about your complaint that the software is not “yet” there. I can see the issues myself. However you making it sound so easy to develop in “MONTHS” is just funny.
Just because something exists in a different phone doesn’t mean that you can copy the code and ship it on your OS. It has to be rewritten to comply with copyright/licenses.
There are a few solutions:
Personally don’t care how good Mudita can make their keyboard, I will still side load something that I am used to. You make it sound so tragic.
Totally agree with on all of this, I have never done this so I am not going to assume anything, if it upsets him this much like I told him move on and get another phone, life is too short to get this worked up over a phone lol.
If I see another update to MuditaOS K (beyond 1.1.1) before my 14-day trial ends OR if I anticipate another update to MuditaOS K soon thereafter, then I will NOT return my Kompakt for a refund.
I got it for the lowest possible price (as Kickstarter backer #42), so returning it only to buy it later at full price does not make financial sense to me.
It has almost enough functionality for me already to decide to keep it.
The one thing that still bugs me is the hypersensitivity of the fingerprint-sensor when I put the Kompakt – in Offline+ mode, by the way – in my pocket and Kompakt opens the “Enter passcode” screen with that ‘touchy’ [Emergency] button. Here in the USA we can get into legal trouble by calling our emergency number (911) when there is no emergency. Plus, I certainly would not want to pocket-dial 911 even if this were not the case.
@kirkmahoneyphd does this happen if you have fingerprint disabled and just use PIN code? Also where is the emergency button??
No, it does not happen with fingerprint-sensor disabled. The [Emergency] button is in the lower-right corner of the “Enter passcode” screen.
I think this pretty well summarizes my situation as well. Maybe some (very high level) acknowledgment of an initial roadmap, in the event that no updates are shipped would keep me on board. I just want some signal to give me confidence that this phone will improve at a reasonable pace
@kirkmahoneyphd Let me see if I understand this correctly: YOUR FINGERPRINT reader is hypersensitive when you have the OFFLINE+ mode turned on? Is it always hypersensitive? Or just when the OFFLINE+ more is on?
for me, I think the issue isn’t so much that its hyper sensitive, it works as expected. I think the issue is that it works when its not supposed to work, like when it’s in your pocket. it should use the proximity sensor to tell its covered and not to unlock with the finger print.
the issue is made particularly sensitive because the screen responds to any type of touch, not just fingers, so when it is accidentally unlocked in your pocket, your pocket its self starts pressing icons and buttons, phoning people and typing random messages.
these two things I think make the issue particularly problematic, but as far as im aware quite fixable.
It is always hypersensitive. @eden has posted a good description, too.
IS there an option to just turn it off and use the pin? I hope there is because that would be annoying it constantly unlocking in the pocket
Sometimes, my fingerprint reader will only activate if I physically click the unlock button first. I’m not sure exactly what actions cause it to switch to this mode (maybe after a certain number of failed attempts?). Regardless, the experience works much better with this setup. I really think the best fix here is just to not have the fingerprint reader “active” until the button is clicked.
Since the fingerprint reader is exactly where most people would grip the phone, we will otherwise face this issue constantly. It’s different than say an older iPhone or Light Phone 3, where the fingerprint reader is in a location where you’ll likely only hit it intentionally.
Yes, you can unlock with the six-digit PIN instead of the fingerprint sensor or delete the PIN, too. My Sunbeam Wireless F1 Orchid (from which I am trying to move) has a four-digit PIN, and I was looking forward to using the Kompakt’s fingerprint sensor as the reliable way to unlock it.
Yeah that has to be annoying, until it is fixed I will just use the unlock code, or not even use the code at all
I completely understand the use of a fingerprint or pin if you have some important data on your phone. Personally, I don’t use fingerprint or pin and it saved me from losing my phone recently. I forgot my phone in the park and the person who found it called my mom to pick it up from him. I was really happy.
Yeah I was thinking this as well, there is not like there is anything on the phone for anyone to steal. Just think if it had a code on it your phone would have been lost basically and all that money down the drain!
I prefer a locked cellphone with a message on the lock screen that says, “If found, please call such-and-such number.”
Google Android and AOSP-based (deGoogled) operating systems such as CalyxOS let users create lockscreen messages.
My AOSP-based Orchid, which runs on what Sunbeam calls BasicOS, does NOT support the creation of a lockscreen message. However, I created my own lockscreen graphic that does say, “If found, please call …”
Ok, that make sense, never heard about this possibility.
AOSP 12 supports this, it would just need exposed in the UI and probably added to the K OS lock screen.
similar to things like encrypted dns, its supported in the device, just needs exposed in the UI