Slow rendering when lots of messages for a contact

[jrd]

I have hundreds (maybe thousands) messages with a contact.
For what I understand, only the last hundreds are displayed (for optimization reason). But among them there are also MMS messages and I think 100 is too much to handle for my device (FP2).
What I see:

• when I open the contact, It takes about ~6s before I can see the history, before that the UI is responsive but I have an empty history.
• when I send a message, It takes about ~5s before I can see my message in the history.

What I expect in quick fix:

• show a loading element in the UI indicated a rendering is currently happening (could be tricky to do it if the delay is especially in Android UI rendering)

What I expect in the long term:

• UI refresh within the second. But I suppose it requires a full rewrite of that activity.

The good news: It's been a while, but I can help code if needed. I've done Android apps at work before.

I'm also interested if other people experience slow rendering too… For information, the delay is <0.5s using OEM application (Google Messages)

[juckel]

I suggest to display only the most recent 50 (or 100) messages. That way the rendering should be quick. One could add a "load more message" button at the top of a conversation, if it is longer than the display limit.

[Lurux]

I experience this problem too. @tibbi, would it be possible showing less messages by default for people using lower-end devices ? Maybe add an option for that ?

[tbart]

I had this on a OnePlus3 as well. I don't see any delay in the stock app and I can scroll through hundreds of messages without any delay. With SMS Messenger it took several seconds. However, half an hour later it only takes around 1s for the bigger conversations.
I think some indexing might be going on which takes some time to finish. So if you just installed the app, probably wait a little.

[Lurux]

@tbart, I had it installed for over a month, I don't think it's that. Other applications seem to first sync the messages with a local (app) database, and use that instead of fetching the messages from the (SIM card ?) every time. I think fetching the messages is what makes it lengthy, hence the suggestion to load less messages at once.

[CivBase]

Unfortunately, the SMS Messages app is currently useless for me because it takes too long to load my most frequented conversations (upwards of a minute). Conversations with only a few dozen messages load in a second or two, so this seems to be the problem.

In addition to loading fewer messages up front, could the app also cache messages from the most recent conversations? That could help shave off even that second or two I notice with smaller conversations.

[dumblob]

It seems SimpleMobilTools are generally highly unoptimized and having "extreme" latencies (I experienced the same with Contacts, Calendar, Drawing app, Camera - now discontinued IIRC, ...).

Anyway, this issue is among the 8 most upvoted feature requests in this tracker: https://github.com/SimpleMobileTools/Simple-SMS-Messenger/issues?q=is%3Aissue+is%3Aopen+reactions%3A%3E3 (out of 87 opened as of today).

Any chance this becomes part of the roadmap?