First off, thank you for all your feedback on the Messages app. Your reports have been really helpful in tracking down issues and improving stability. We wanted to give you a quick update on a few additional fixes that will be included with the upcoming September release (Version 1.3.0).
Fix for crashes in long message threads
We have identified a primary cause of crashes when conversations contain a large number of messages. With this patch, we’ve improved the overall stability of the app, so navigating through longer threads should now feel smoother and more reliable.
In conflict with sideloaded messaging apps
We’ve also confirmed a conflict affecting users who install sideloaded messaging apps. For those comfortable with using ADB (Android Debug Bridge) commands, we’ve shared a temporary workaround in our recent announcement. At the same time, we’re working on a long-term solution, which will arrive in a future release after Version 1.3.0.
These fixes are separate from the main feature updates planned for September, but they’ll roll out alongside them in Version 1.3.0.
Thanks again for helping us improve.
Your feedback continues to guide the way we refine the app!
I really hope that with the next update, the SMS app will be back to normal. Since I rely on the SMS app, or rather, it is one of my main means of communication, I have suspended the 1.2.0 update. After so many new bugs were reported here after the update, I just didn’t dare to install it. (And the removal of the Mudita logo from the lock screen, which is not okay with me. The lotus flower is simply part of it! Bring it back!) I really hope that the Mudita team has learned from this and will wait a few days longer before releasing updates and test them very thoroughly. It’s not nice to use customers as beta testers
I would also like to see updates separated in general. Bug fixing updates and those that bring new features. That way, everyone can decide for themselves whether they need and want new features. Often, you’re just waiting for a specific fix (SMS, camera, alarm clock) and you might be happy with the rest, or you might not want any other changes.
So, it wouldn’t be a bad idea to separate them into bug fixes, security updates, and those that bring new features.
And right now, Mudita should really focus on not introducing new bugs with new updates, and just make the existing apps properly usable first. Similar to the Maps app with the navigation function. So please continue with the music player, etc…
Whether the meditation timer (which I use every day) now has its settings somewhere else should be secondary for now.
So please fix the serious bugs and make your apps properly usable
Everything else can follow afterwards. Because when I look at some of the surveys here about what other features users would like to see, it seems that the wrong priorities are being set.
Why remove the lock screen logo instead of addressing other important issues?
I hate to say this, but because: it was no effort to remove the lock screen logo.
And I agree with you on how the updates were managed/tested. I know we’re a small number of users on this phone but the OTA should rollout first only to some testers that use this phone daily.
During 1.2.0 update they mentioned the update will go to the NA variant first, and the next day to the Global version to catch any issues. I was happy with that, if there was an issue they can stop the update rollout make a hot-fix and proceed updating.
Even though some of the issues like sms-crashing were reported very quickly after the NA update, they knew about it and they still continued to roll-out the Global update the next day with the same issues.
I waited 7 days to update mine, just to find out they had accidentally stopped the accessibility permissions.
That’s exactly what bothered and surprised me. After the first reports of new bugs, especially for something as important as the SMS app, they should have stopped distribution of the global version the next day. Instead, they watched as the majority of users downloaded the update, knowing full well that they would no longer be able to use the Kompakt as usual.
So why the delayed release of the update? I really hope they’ve learned from this and will do things differently next time. I just want a device where the basic functions and pre-installed apps work without having to install alternatives via sideloading.
