If you opened a new topic and posted that I wouldn’t have said anything. You came into a bug report page and started talking about ethos.
I’m here almost everyday to help users answering their questions about issues they’re facing.
You’re here just to spread “positivity”. I think you should be the one to get out.
@felensis Thank you so much for sharing this. Your message truly captures the spirit of what we’re building with Mudita Kompakt, and more importantly why.
We’re incredibly grateful for your support, your thoughtful perspective, and your understanding of our long-term vision. As you know that it’s not always easy to swim against the current in today’s smartphone-obsessed world, but messages like yours remind us why it’s worth it. I totally get it why some users might be upset & we are trying our best to work through it. We know there’s still work ahead, and we deeply appreciate the patience, kindness, and constructive feedback from users like you who believe in this journey with us. Let’s keep moving forward, together-calmly and intentionally. 
This is a friendly reminder to let’s keep it civil 
@ovy Regarding your point about the empty release notes. Could you please try again and click refresh in the Settings → Software update settings. If you could record this and let us know if the issue still persist. Additionally you can DM me your IMEI1. number so we can research more.
@urszula Disrespect comes into many shapes.
Just because they didn’t use the F word like I did doesn’t mean they’re not intentionally or unintentionally being disrespectful to some users.
I don’t consider civil coming into a topic of bugs and talking about mindfulness.
Just because their good experience doesn’t translate to other people’s issues doesn’t give them the right to come and preach us.
@gezimos I completely understand. I just want to make sure that we keep things respectful & enjoyable- for everyone, on whatever side we are.
I appreciate the perspective, but respectfully, it comes off as fairly patronizing. Not every user has the same needs, and just because the phone is meeting your own needs, doesn’t mean that that things are great or that other feedback is unreasonable.
To address a few points:
Since the update yesterday, many people cannot open SMS conversations on their phones. IMO, this is a fair complaint, and falls under the category of “basic needs” for this type of phone.
Not being able to pair bluetooth headphones is also a fair complaint, because this was advertised as a feature that would be present from day 1. I need to use the phone while I’m commuting, and I cannot use any hands free calling with my car, because the bluetooth has not been fixed after several months, isn’t planned for a few more months, and the speakerphone isn’t loud enough to hear in my car.
The fingerprint sensor opening if you just brush it with your finger unintentionally is also a complaint shared by many users, and affects the basic usability of an advertised feature. It’s also causing pocket dialing of emergency services for myself and other users. Another reasonable thing to push for a timely fix.
The ‘point of this phone’ for me, is probably not the same as the point of this phone for you or any other user. I don’t use group SMS or voicemail for example, but I can empathize with others expecting quick improvements in these areas before working on games and meditation. You don’t need a meditation app to meditate, but you need to be able to open your SMS conversation to send an SMS.
I am willing to be patient, as are many others. But I think it’s fair to voice complaints that some basic functions within SMS, voicemail, keyboard, network settings, etc. are not working well, yet the developers are spending time playing with the chess app, meditation app, and making sideloading functions on the mudita center. These are certainly not necessary for “serving basic needs” yet they’ve been prioritized over many other painful bugs in the first release. This is the frustrating part. Not telling the Mudita team to go faster, but challenging what I see as some very illogical prioritization given a scarcity of developers.
@brendxn @gezimos The points regarding basic functionality are absolutely valid. No discussion. To subordinate the devs they would prioritize the Chess or Meditation app over these basic functions is a tough thing though. I think they are quite aware about the open issues, requests etc. since this community is very vocal about it and @urszula is doing an outstanding job as community manager as well. At the end of the day it is all a matter of time, resources and priorities. Nothing more and nothing less. This is what I meant with my post earlier. It is ok to tell the devs via this forum or directly via a support ticket (probably the preferred method over this forum) about those things. It is not ok to subordinate mean things and create pressure or be rough against other users which just empathize with the team and want to try keeping this conversation civil.
@urszula I think at this point the best thing would be to split the update cycle into bugfixing and feature releases with the former maybe on a monthly schedule and the latter like on a bimonthly schedule. This has been suggested already by some users. The other thing helping could be an offiical communication (i.e. blog) from the Mudita team to clarify on open issues and give an outlook how and when they will be fixed. Just a suggestion to improve things. Maybe you can take this feedback for internal discussion 
@ovy Thanks for the video. I am asking the team as to what could be happening.
@felensis I don’t think anyone is taking shots at Urszula, everyone is aware that Urszula is doing the impossible, she’s the one holding this community by the thread.
The shots are at the dev team or person (have no idea, they had an android dev that is gone from the team page) and the higher-ups who are the ones making these decisions.
There are basic things done wrong:
Most of these can be fixed by having a: “Know Issues” page.
Am I being more clear now?
Yes, of course and agreed. I don’t think the devs aren’t aware about the most urging bug reports and feature requests. In this context I think they for sure don’t prioritize the Chess or Meditation app over reported bugs and feature requests like suggested by some users here. This is just mean and seems more like out of sheer frustration.
If you work in IT you probably understand what I meant with it is all about time, resources and priorities. They most likely have all those things on their agenda, but have to juggle on how, when and in which order they tackle all those things with their limited resources.
I fully understand the frustration over i.e. the BT issues, but since they’ve reported in their changelog it is fixed and now it turns out some users still have issues for sure isn’t because they tried to trick someone. They did their best and there seems to be some blind spots in fixing this which they haven’t discovered yet. Accusing them instead about this is just not the right way in my opinion.
No offense gezimos, I’m just saying this in general.
@gezimos Thank you for the kind words. Just to make sure we are all on the same page:
Here’s my question to the community, so that I can better understand your needs:
Would it be more helpful if the community had clear feedback from the Kompakt DEV team about which bugs/features have HIGH priority vs. Medium Priority?
Additionally, from all the threads I’ve read, I know that people have expressed interest in KNOWING WHEN they can expect a specific feature to be added or a bug fixed, however, do you care about the justification for the timeline, or is it more about: “Just tell me when this will be done.”
This is false and actually fairly easy to prove. Check in the first update, to see if they included
a) Added side loading to Mudita center, changes to the chess app, changes to the meditation app, or:
b) Fixed the issue connecting to previously paired bluetooth devices, added voicemail notifications, group SMS, etc.
@urszula Ideally something like this would make it easier for the issues to be presented to the public. It should stop using from reporting the same thing over and over. Especially if it has a search functionality and a secondary dialog window with details/screenshots.
If that’s not possible then a simple google sheets public document where users can see the list of the reported bugs, and which are being considered a priority.
Personally I care to see which issues are getting priority more than to know when it’s going to be fixed. I know not everything can be fixed at once.
It seems that a clear differentiation needs to be made between core release functionality bugs and side-load related bugs. Core release functionality should receive priority.
The core release bugs should be in the control of Mudita, and impact basic functionality of the device. Most users will be affected by these bugs, whether they are vocal about it or not.
All sorts of external issues could be affecting the performance of side-loaded apps, some in the control of Mudita and likely many not. Even providing side-loading capability in the Mudita Center does not guarantee that side-loaded apps will work., depending on the app and how it is designed. Fixing these side-loaded app bugs is an additional service being provided by Mudita, and should be appreciated as such. Some apparently feel that anything they side-load into the Kompact should just work fine, which is very unrealistic.
Completely agree with all of this.
I don’t think there are side-loaded app bugs.
What doesn’t work is not a bug, it’s usually just an app that requires Google Play Services.
Mudita has no responsibility to support those as it never claimed they will. They should add an auto-response for such claims to stop wasting time.
If us the community users can help our fellow Kompakt owners find solutions, it’s ok.
But, Mudita should solely focus in system bugs (bluetooth, carrier selection), and major default apps like: launcher, phone, sms. Everything else is a luxury until these are ironed out.
However… I’ll be annoying and repeat this for like the 100th time.
Supporting E-ink modes, would make sideloaded apps more usable, which should make users complain less, ask for less new features in non-core apps.
Indirectly allowing Mudita to focus more on the core default apps.
And can’t forget that e-ink modes would be useful for the default apps as well. I for one, want slower refresh rates (with full screen) refresh because I don’t want to experience ghosting.
@gezimos Thank you so much for sharing this. I will make sure the team sees this. I totally get that need to see where the progress is. After all, our users are the ones for whom we create our mindful tech products.
Kudos Mudita team! Everything seems to be working for me, delivery, hardware, software and ethos. I read and watched reviews and info so knew what was buying into. I delayed downloading the update until I was confident from the feedback about it. I did struggle a bit getting aurora downloaded(success at the third attempt tho’ I’m not sure I did anything different), so that I could load whatsapp; the main way my family communicate so necessary. I want as few apps as possible. No problem loading ebooks and music into the standard apps. Will be looking for most hassle free way of listening to audio books and podcasts on the device, but that I think will be it. I managed this as a technical numpty so it can’t be that hard. I’m sorry some people are having issues but I thought you should know there are some happy punters. Thanks Team Mudita;-)
