SimpleMobileTools
App becomes unresponsive (black screen) when selecting conversation
I've repeatedly encountered the following behavior: I'll bring up SMS Messenger, and from the view that lists conversations (those with most recent activity first), select a conversation (it doesn't seem to matter which one). I will then get a black screen while the whole phone becomes unresponsive. Sometimes the phone will give me the prompt to wait or kill the app. If I kill the app by any means (such as Force stop) and open the app again, the same thing will happen. It seems like only restarting the phone lets be get back into one of the conversations. I've tried waiting multiple minutes for the app to respond, without luck.
Today I tried something a little different. It occured to me that perhaps something was going on in the conversations list view that was not finished when I try to open a conversation. After getting that black screen and then killing the app, I tried scrolling all the way to the bottom of the conversations list first...there seemed to be something odd going on because the system ui was being sluggish to respond...I could not get the system buttons (home, etc) to appear, and after waiting some time, I got that dialog from the system about "System UI being unresponsive with the options to wait or kill it. I waited, and after waiting many minutes it seemed to clear up, and I was able to select a conversation without a problem.
Is there some task that starts (or can start) when you open the conversation list screen? Maybe something that runs through all your data? (I do have many years of conversation history on my phone).
(Version 5.17.2 running on android 8.0.0)
I should mention that this behavior has only started fairly recently (in the last few days). Possibly it started when I upgraded from 5.17.1 to 5.17.2.
I should also clarify this doesn't happen all the time. Sometimes I can go into the conversation list, and then open a conversation right away, and everything is snappy. I haven't been able to notice a pattern in something leading to it getting into this "mode".
Hello, I have the same behavior when I try to enter a conversation in which I responded via the notification area of my phone
App 5.17.13 Honor 20 Android 12
Similar to https://github.com/SimpleMobileTools/Simple-SMS-Messenger/issues/445#issuecomment-1424955290
I do think that when this bug happened to me I had recently done as @EVOTk just described, replied to a text via a notification.
I have not had the problem in a while, and I assumed that was because of an update, but I don't think I've replied via notification recently either.
I've noticed that it freezes the app when you interact with the app via any of the notification buttons - both replying and simply marking as read causes the issue for me and requires a phone restart.
Same for me, 5.18.1 doesn't solve the issue. The issue described by @noodlejetski above is what I am am experiencing as well. Also if I use any of the notification buttons, I can open the app but it freeze if I want to open a conversation with someone.
I am also experiencing this issue, v5.18.2. Additionally the app is extremely sluggish to respond to changes in message status (sending, sent). Sometimes when I enter a conversation, my recent sent texts don't appear for some time. It will just be the last ten or so received texts. After ten or fifteen seconds, my replies show up and interleave themselves with the received ones.
Seconding @noodlejetski's and @mortyam's experience on my Pixel 3 any time I use the "Mark as Read" functionality from a notification.
First noticed this in mid-March, and still have experienced it this week under v5.18.2 (via F-Droid) on Android 12 (build SP1A.210812.016.C2).
