The text messages API was rushed and has major limitations that blocks 3.0.0 * Setting messages as unread is plain broken, so they stay red forever * All text messages are loaded during startup, this freezes the app on slow HDD and mobile devices * Memory usage is out of control (dozens of useless megabytes are allocated for nothing) * Clearing doesn't work * There some polling timers that eat battery life I have to be careful with the fixes as they will impact future features and maintainability. This needs to be implemented right and by taking into consideration all use cases. I settled on a second layer of serialization to keep track of the metadata separately from the text recordings themselves. This will enable more lazy loading and reduce startup time. The text recordings themselves will be moved to use shared pointers to avoid keeping everything in memory. The API is being reworked to move the recorcing states (including voicemails and in call recording) to a finite state machine. Some other work is being done to improve the recording API.
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!