So when someone repeatedly points out that an overpriced product we purchased from Mudita isn’t working the way it should, the thread is being shut down ?
Just to support my fellow forum member, I would like to bring up the “solutions” I received from the support (via email).
When I wasn’t able to post on the forum:
“I’m very sorry for the delay. I’ve requested priority for your case, though I can’t make any guarantees.
That said, it should be a matter of only a few more days at worst, rather than weeks.”
(September 26th, 2025)
Browsers not displaying websites when entering an URL directly:
“I just wanted to follow-up with you via support to say that your problem has our team super stumped”
(October 28th, 2025)
I’ve been receiving spam that is supposedly blockable on the Kompakt, but in reality it still comes through:
“Thank you for your patience and cooperation in addressing this matter.
At this point, I’ll need to escalate the issue to our IT team and wait for their assistance. I’ll reach out to you as soon as I have more information.”
(November 6th, 2025)
I’ve also been asked to provide the following, although Mudita should have all this info, since they sold this phone!
“Your Kompakt phone’s serial number and both IMEI numbers”
Since then: no more reply. So is this the best the team can do ?
First I have to provide a lot of info (why and what for ?), only to receive empty phrases or no help at all ?
Maybe shut down ALL the threads or even close the forum. New customers can then draw their own conclusions. I more and more regret that I ever bought this phone.
Threads are NOT being closed because users report issues or express dissatisfaction. WE DO NOT shut down discussion because products are criticized. Many critical threads remain open on this forum, and support-related feedback is welcome when it is constructive and stays within scope.
I know which particular thread you are referring to and it was closed because it stopped being a technical discussion and turned into repeated accusations, escalation, and references to unrelated matters that cannot be responsibly addressed in a public forum.
Individual support cases, response timelines, and internal escalations cannot be resolved or audited here. Sharing fragments of private support correspondence without full context does not move issues forward and puts both users and the team in an unproductive position.
If you have unresolved support cases, the correct and effective path is to continue through official support channels, where cases can be tracked, escalated, and answered properly. The forum cannot be the place to pressure or confront individual team members.
We understand frustration when issues take longer than expected. What we won’t accept is turning the forum into a space for accusations, personal attacks, or coordinated escalation.
It does not help anyone to have discussions in this manner. I hope our members can understand that.
That’s what I did! The above quotes are ALL taken from the emails I received. Yet it all stopped in November, nobody got back to me with a solution, and it is obvious I am not the only one. Fixes take forever, sometimes half a year or longer, if they are being addressed at all. That’s not an accusation, it’s a fact. If Mudita can’t handle the workload, hire more people, for God’s sake. I honestly have never seen such a slow and incompetent way of handling updates or customer inquiries. There are way smaller teams on the market, but they work ten times faster than you guys (not you specifically @urszula , I know you are trying hard). But trying is not enough, especially when the forum is swamped with complaints and error reports and still nothing is being done to catch up with this mess. The Kompakt requires constant fixing and workarounds. This is NOT the “calm” or “mindful” way, it’s the opposite. So why the continuous mincing of words ?
Also, what about the sentry service and the RF spikes when locking the screen ? This is not privacy at all. Those should have been fixed LONG ago.
Oopsie. I have encountered this kind of situations in the past – both regarding free & closed software. Also regarding some somewhat niche plateforms like the Remarkable or Boox tablets…
Some fixes might seem trivial to us but might have unexpected implications or need underlying refactoring… We don’t know the workload of the team. We don’t know the situation of the company. etc etc. I think it’s already quite good we can have a public roadmap & indirect chat with the team.
I don’t know if it’s possible to have some kind of bugtracker for closed software, which would enable users to see that work is being done, but prioritized, with a rough expected fix version ?
As for me, I have not encountered significant bugs for the time being. Just a couple of finetuning needed for slightly off-road use-cases.
I guess 1.5 is coming soon ? Considering the amount of improvements in version 1.4, tons of stuff might be improved
PS : no intention to make the code open at all ? Considering the people making great contributions here Maybe not for core elements ?
