What you can try first is to factory reset the phone, sometimes this helps. If you are unhappy with the system, you can switch to KompaktOS. You get a way more grown-up phone with a lot of good functions and a fast support. Also you can use Android Auto, if your car is equipped with this function.. Just be sure to backup the phone before, so you can switch back to Mudita OS K easily.
If even KompaktOS is not satisfying for you, then you can wait for Mudits OS K 2.0 or of course have a look for another device. Question is, what you expect from it to be. Should it be a modern and powerful E-Ink device, look for Boox Palma 2 Pro or Bigme Hibreak series. If you care more for the compact form factor, then Unihertz Titan 2 Elite, Clicks Communicator or Minimal Phone MP02 can be interesting for you.
But to be true, there is actually no device on the market like Mudita Kompakt, that combines the small form factor together with the daylight readability from an E-Ink screen.
Thanks for flagging this. I reached out to our team with your case. I know factory reset could potentially solve this issue, BUT I know that’s a very dramatic step- so I would prefer that you should not have to do that
“But to be true, there is actually no device on the market like Mudita Kompakt, that combines the small form factor together with the daylight readability from an E-Ink screen.“
Additional difficulties - the install for mtkclient page at:
also fails to mention that UsbDkController, once installed, is not found either.
Now when I go to the actual directory and invoke it thusly (I pre-pended the “.\” otherwise it didn’t work):
.\UsbDkController -n
The Kompakt does not show up (it is turned on, connected, USB debugging allowed).
I do get four USB devices.
The instructions on the install page say the Kompakt should report as “0x0E8D 0x0003”.
That format can only be said to vaguely resemble any of the identifiers that show up (certainly yes in that they are also composed of letters and numbers, but are of varying length and composition); none match.
Found 4 USB devices:
0. FilterID: 1, Port: 5, ID: 1bcf:2b96, Configs: 1, Speed: 3
USB\VID_1BCF&PID_2B96 5
Descriptor for configuration #0: size 767
Not sure why bluetooth is not working for you. Connects to my SUV and I can make and receive calls. Strange you are having issues hopefully you get get it sorted
“Not sure why bluetooth is not working for you. Connects to my SUV and I can make and receive calls. Strange you are having issues hopefully you get get it sorted”
The car connected seamlessly to the previous phone - several times, some after reboots of both it and the car electronics.
Phones have had bluetooth for 25 years, it shouldn’t be that hard.