I've been having a recurring problem with SMS which I think might be related to the ongoing Lollipop memory leak problems. I have tried trimming back old messages but it's still happening at least a few times a week.
Basically at some point I get a text message and when I go into my SMS client - currently EvolveSMS but the same thing happens in all clients - the conversation list is either blank or only contains 1-3 entries. Any attempt to access text messages in any app fails and it just shows no conversations. When I do a logcat search for SMS I find this message:
The connection pool for database '/data/data/com.android.providers.telephony/databases/mmssms.db' has been unable to grant a connection to thread 100 (Binder_A) with flags 0x1 for 180.01302 seconds.
And it keeps showing up again and again with the number of seconds incrementing. The thread number and binder letters change as well as perhaps multiple different processes are trying to access the texts.
If I reboot it continues happening but eventually goes away on its own and I can see my whole conversation list again. Sometimes if I swipe away every recent app and wait a few minutes it goes away too.
I once had this problem in KitKat after restoring a large number of messages to a newly purchased Nexus 5. However it only occurred once - after I allowed the error to resolve itself over some extended period of time, the problem went away and never came back. On Lollipop I am experiencing this with quite some regularity and it's very disruptive because I'll receive a text and then find myself locked out of being able to respond to it for 10 or more minutes.
Any thoughts, ideas etc?
Related
I've noticed that my texts aren't immediately sending. I've only had the phone for a few days, but I had this problem on the stock rom and also on flashed rom's.
For example, I sent a text about two hours ago, but I just checked my messages and the time beside it shows a couple of minutes ago.
Anybody know what's up?
i've never experienced that but have have got the message notifying me that it was unable to send the message and asks if i want to try again. And usually when i do click try again the message pops up a second time and later i find out that the recipient has received the message multiple times.
Have you tried calling your provider and seeing if there experiencing any network issues in your area?
I use my device for work. I coordinate/schedule jobs in which there are many people who can work certain slots. So, I'll send out one text message to about 75-84 individuals. Then the ones who can work reply. Later, I send out another mass SMS advising of remaining slots to be filled.
My issue is this. In the Android code a section checks for the number of text messages send within the last hour. If you exceed 100 messages - then, Android throws an error for every message afterwards within that hour and the user has to select "OK" to send an SMS. So, at times I have to sit there and select "OK" over and over again for several minutes while the over limit SMS's are sent....
I found an old record on how to fix this issue here.
However, this APPEARS to be an old solution. I was unable to find this setting or the table "gservices" in "/data/data/com.android.providers.settings/databases/settings.db
Does anyone know where this was moved or how to change this setting?
My device is a an LTE Galaxy Nexus.
I'm running AOKP-build 33. But, I would think this setting would be generic to all of the current ICS ROMs.
Thanks for any advice.
BTW - I found some very old posts related to this same issue. Note:
1) Using an app will not address this issue (I use Chomp SMS) as this is coded within Android.
2) Google Voice will not work as it doesn't recognize "groups" for the "to" box.
3) Pulling the battery will just prevent all the texts from going out.
I'm just hoping someone knows where the file/code is located that I need to modify.
All other suggestions will not resolve this issue.
Hey guys...been having some issues, was wondering if anyone could tell me what's going on.
I'm on CM10, and i've had the same issue on several different daily builds. I noticed that I wasn't receiving a certain number of incoming text messages. I have been using (not at the same time) DeskSMS and Mighty Text to text via my computer, and I noticed I would recieve a text on there sometimes several minutes before it would show up on my phone. It seems that texts in both directions are going very slowly, because conversations are disjointed and out of order. When a large text is split into several smaller ones, they come sometimes a minute or two apart.
I have tried wiping my cache, installing different builds...everything aside from a full data wipe. Is that the next step, or is this a Verizon issue or something? Thanks!
Might be a slow work day, so I'm hoping I can get rid of some the little bugs that have been bothering me....
1. Sometimes I will receive the same text message multiple times, up to about 10 but it's usually only one or two duplicates. This can happen over a period of about 20 minutes.
2. Messages get delivered several hours later or only after a reboot. There is not usually any indication that the sms failed to deliver. I sent a text yesterday to my brother, and it seemed to go out fine with no error message. After rebooting my phone today, I shortly thereafter received a confused text asking what I was talking about. The text I thought I had sent yesterday now appeared in our conversation with a timestamp of when I restarted my phone.
3. The stock messaging app doesn't give me any notifications at all. Obviously, that's not acceptable, so I'm stuck using a 3rd party sms app (handcent). Don't know if this is related, but I use Google Voice for my voicemail and that also doesn't give me notifications (have my voicemails sent to my gmail account as a workaround on that). If I open the apps my voicemails and texts are there, just no notification from the phone.
I know at least the first two issues could be an issue with the carrier (at&t), but I had none of these problems with an iphone prior to switching or when using the mediocre AT&T Messages app on this phone.
I was hoping these problems would magically disappear after rooting and installing a new ROM (viperXL), but that hasn't been the case.
Thanks for any help!
Anyone else having this issue.
Group text randomly sends messages to each individual user in MMS group when using Samsung Messages. It's been happening for months. Most environments are mixed and Android and iPhone users. RCS is turned on for me. Happens several times a day and I get no indication of it happening until someone responds to me separate from the group. My message for me shows correctly sent in the group.
This does not happen with any other messaging program such as Google or Textra. If I switch to Google after this happens I can see the message I sent 3 times in the group thread if there are 3 other users In it. But no individual threads.
Like I said this has been happening for months and every time I switch back to samsung messages after an update it's the same issue that makes me move away from it. The group settings are toggled correctly, data is on correctly, I've cleared storage, reset my phone (after UI3 update) and yet this still occurs.
I'm currently on the U1 Note 20 Ultra, on One UI 3 with a T-Mobile Sim.