RESOLVED: Turns out it was GO SMS causing all the problems. The most recent update fixed all my problems. Still have no clue why this would cause my stock messaging app to crash *shrugs*
I have an HTC Evo3D, which had been working fine until this morning. Any app that deals with SMS messages now hangs up and freezes my entire phone, requiring me to take out my battery and restart my phone. I normally use GO SMS, but the default Messenger app crashes as well. Usually the app will load, and I'll see my list of conversations, but if I try to load a conversation or send a new text, everything freezes up and I'm left beating my head against the wall while my phone restarts. I tried to install an SMS backup app, but it froze up as well. Cleared the app data for GOSMS, but no luck.
My phone number is integrated with Google Voice, so I'm willing to erase all my SMS messages if I need to, but I have no idea how to do this without access to a messaging app. Needless to say, this is pretty frustrating
Any protips, Android Gods?
EDIT: I just realized that the GO SMS popup shows up when I get a new text, but if I try to reply or open the conversation--crash, crash, crash. This makes me think there might be something wrong with my SMS archive, but I'm clueless how to fix it.
Related
Ever since the ICS upgrade, one contact's message thread refuses to open and is stuck on "O Loading" with that little circle revolving.
I downloaded go sms pro before and I was able to access his thread through that and the message count wasn't over the maximum limit per contact. I've since gone back to the stock app as he's out of the country and it's faster than go sms pro but he recently txted me and caused the problem to occur with other contacts (though a reset of the phone solves their issue)
Does anyone have a solution and failing that, advice? I should say right now that deleting his message thread is the last resort.
and HTC sensation
Android 4.0.3
Software 3.32.401.5
You could try to backup your messages (you can find some apps for that in the market), then delete all your contacts, and afterwards restore them again~
Though no idea if it will work :/
burningwipf said:
You could try to backup your messages (you can find some apps for that in the market), then delete all your contacts, and afterwards restore them again~
Though no idea if it will work :/
Click to expand...
Click to collapse
Aye I could try it with a contact whose messages I don't mind losing and seeing if that works, thanks for the tip!
You can also use Google Voice, and have it copy all the messages to your Gmail account.
Sent from my Galaxy Nexus using Tapatalk 2
So I started backing up and restoring and I was able to open all contacts' threads. The backup never fully restores all messages though and I have to keep hitting "restore" so that it'll restore them all up to the present day. Don't know why it's doing it this way.
Just now I've checked and that one contact won't open again. What I might do is try and restore all to the present, delete loads of messages I don't want, and backup this new message history.
I know this is most likely far too late but I was having the same problems and found this thread while trying to sort it and hope it will help anyone else in future who has the same problems. I tried backing up and restoring (Using both the default and sms back-up and restore) deleting the thread and restoring, eventually I solved it by installing handscent, deleting the messages sent/received back to when the problem started in that thread and a few before, then went in settings, apps, then all, messages cleared the cache, restarted and it is sorted!!
3dd1 said:
I know this is most likely far too late but I was having the same problems and found this thread while trying to sort it and hope it will help anyone else in future who has the same problems. I tried backing up and restoring (Using both the default and sms back-up and restore) deleting the thread and restoring, eventually I solved it by installing handscent, deleting the messages sent/received back to when the problem started in that thread and a few before, then went in settings, apps, then all, messages cleared the cache, restarted and it is sorted!!
Click to expand...
Click to collapse
Yeah it never resolved itself but I love the customisation of go sms pro so much that I don't mind anymore. Pity go sms pro crashes every so often and I think it slows the phone down.
I was going to start a new thread but see that this is the same problem I have.
I have a mt4gs (Doubleshot) and the problem described in this thread has happened twice. Both times i was receiving a text message and did something else with the phone at the same moment, and it seems to have jammed up the receipt of that text. The first time, i sent a text to the person at the same moment i received one. The second time, i locked the screen at the moment one arrived. Now that thread never loads, and loading other threads or contacts takes much longer than it should. In fact, i don't think contacts would ever load if i were willing to wait forever.
The first time I backed up the texts, reset the device, and restored, and everything worked fine, but that's a really time-consuming process and it seems like a ridiculous workaround for some broken buffer or queue in Android messaging.
It seems that there must be a direct fix for this. If it's easy enough to break messaging that it has happened to me twice, it must be a fairly common problem. But a search has turned up nothing but people saying there are too many messages or to use an alternative app for messaging. That's (1) incorrect and (2) again an ugly workaround for a problem with core functionality.
Stock, unrooted Nexus S. All of a sudden at about 4:30pm this afternoon, Google Talk started force closing every time I click someone's name to send that person a chat. I can open up the app, sign in and out, open settings, etc., and it all works just fine. But as soon as I tap someone's name to open up an actual chat window, it force closes.
Any ideas? Thanks.
same problem. clearing gtalk and google services framework data and rebooting didn't help. however, after starting and stopping videochat the problem seems to be gone...
it looks like there is a problem with some messages because now when i scroll up to look through the history, gtalk just FC's again. it seems that one of the messages is a sort of broken and gtalk can't display it properly.
if my theory is correct, you can just start/stop videochat a couple of times to fill the screen with service messages or send some messages via PC
123RaZoR321 said:
same problem. clearing gtalk and google services framework data and rebooting didn't help. however, after starting and stopping videochat the problem seems to be gone...
it looks like there is a problem with some messages because now when i scroll up to look through the history, gtalk just FC's again. it seems that one of the messages is a sort of broken and gtalk can't display it properly.
if my theory is correct, you can just start/stop videochat a couple of times to fill the screen with service messages or send some messages via PC
Click to expand...
Click to collapse
Mine somehow fixed itself after several hours. Hasn't happened again since.
Sent from my Nexus S using xda app-developers app
Using Go SMS Pro for texting, but I am sending duplicate, or double, of sms messages. It's not every text, approx one in every 4. Running CM10 on the vzw SGS3.
Here's what I've attempted:
Disable all notifications in the AOSP Messaging app
Froze Messing apk in Titanium
Set "Stock SMS unistalled" in Go SMS Pro settings
Re-flashed the VRLF2 modem
Seems others have this problem, but no solution other than "use the messaging app". I've got 2 theories, but I am opening this up to discussion and if anybody has an angle I'm not seeing.
-I'll try using Handcent. If this works, it points there's a bug in Go SMS Pro. Else, it's across third-party apps meaning its either the AOSP .apk or ... radio?
additionally, this has only been occuring since I flashed CM10.1, lost data, and odin back to TW and back to normal on CM10. Been having spotty data and I am thinking this may be associated? I am certainly open to suggestions.
sweeds said:
Using Go SMS Pro for texting, but I am sending duplicate, or double, of sms messages. It's not every text, approx one in every 4. Running CM10 on the vzw SGS3.
Here's what I've attempted:
Disable all notifications in the AOSP Messaging app
Froze Messing apk in Titanium
Set "Stock SMS unistalled" in Go SMS Pro settings
Re-flashed the VRLF2 modem
Seems others have this problem, but no solution other than "use the messaging app". I've got 2 theories, but I am opening this up to discussion and if anybody has an angle I'm not seeing.
-I'll try using Handcent. If this works, it points there's a bug in Go SMS Pro. Else, it's across third-party apps meaning its either the AOSP .apk or ... radio?
additionally, this has only been occuring since I flashed CM10.1, lost data, and odin back to TW and back to normal on CM10. Been having spotty data and I am thinking this may be associated? I am certainly open to suggestions.
Click to expand...
Click to collapse
You could try clearing GO SMS Pro's app cache (Settings->Application Manager->All->GO SMS Pro->Clear Cache) or running a fix permissions utility. Uninstalling then re-installing may also fix it. While the above suggestions may not fix it, I figured I would give you some more possibilities to try.
Hmm so I downloaded 8sms as I thought it might be a suitable replacement. It looked great, just like the stock messaging app. Made it default. Came back and I just got a blank white screen that says "Loading conversations.". Rebooted and it looked fine. Then opened it a second time and again lost my conversations. Switched back to Hangouts and my messages were still missing after a reboot. Opened 8sms again and my threads were there, went back to Hangouts and my threads were there.
Switch back to 8sms and I get a notification for 8305 new messages. Opened the notification and it's again "Loading conversations".
Something very strange is going on with the 3rd party functionality in KitKat. In logcat I get messages like:
"The connection pool for database '/data/data/com.android.providers.telephony/databases/mmssms.db' has been unable to grant a connection to thread (###) (Binder_#) with flags 0x# for 150.003 seconds" where the #s are a bit different with each entry.
Running pure stock rooted here. Any thoughts? I know that there is some sort of database transfer when switching in and out of Hangouts, but this is really disconcerting.
Given this instability, I guess I will be back to Hangouts for now until I can figure out what will work consistently.
Any thoughts on this, anyone?
Sent from my Nexus 5 using Tapatalk
Hi,
Could you please check your mms settings are correct?
http://8s.ms/mms-settings
It shouldn't be related, but I've heard from other users of weird phone behaviour when this is not configured correctly.
You might also want to try an uninstall-and-reinstall as well. There are a few reports of phones also behaving strangely which then fix themselves after a second install.
Other than that ...
"The connection pool for database '/data/data/com.android.providers.telephony/databases/mmssms.db'
Click to expand...
Click to collapse
That sounds like an Android problem.
That's the database which stores the sms and mms messages. You can think of it as a "server" and 8sms (and Hangouts) are just clients to the server.
Hence, the database is managed by Android, not by 8sms (nor Hangouts) which is why I think this is an Android problem .
I know that there is some sort of database transfer when switching in and out of Hangouts, but this is really disconcerting.
Click to expand...
Click to collapse
There is no "database transfer". Both apps read from the same database, but only one (the default sms app) is allowed to write to it.
When the default sms app is changed, no data copying takes place, it's just a change of a simple string setting (to remember which is the default sms app and is allowed to write to the databse), and is instantaneous.
Hence again, this is why I think it's an Android problem.
Perhaps you have file system corruption or a problem with your Nexus 5?
Thanks, yes my MMS settings are correct. I would be surprised to see any corruption as I only just got this phone Friday. Anyways I haven't had any problems keeping it set to Hangouts.
Sent from my Nexus 5 using Tapatalk
Well, please try the reinstall I suggested above.
Then, another suggestion ... what about you force stop both apps (8sms and Hangouts) before you change the default sms app (via the Android settings)?
Perhaps in your previous switch, Hangouts was still writing data to the messages database?
(Just a random wild guess)
didnt they change how sms/mms worked in 4.4.
I think the app needs to be updated for it to be compatible no? correct me if im wrong, probably i am.
expertzero1 said:
didnt they change how sms/mms worked in 4.4.
I think the app needs to be updated for it to be compatible no? correct me if im wrong, probably i am.
Click to expand...
Click to collapse
Yes, but 8sms has already been updated to work in 4.4, and there are lots of instances of it working on other Nexus 5 phones.
bengtan said:
Well, please try the reinstall I suggested above.
Then, another suggestion ... what about you force stop both apps (8sms and Hangouts) before you change the default sms app (via the Android settings)?
Perhaps in your previous switch, Hangouts was still writing data to the messages database?
(Just a random wild guess)
Click to expand...
Click to collapse
OK: Tried uninstalling/reinstalling 8sms. Then force closed Hangouts and 8sms each. Then changed default sms app via Android settings.
Then launched 8sms. Everything looked fine. Then opened a conversation and everything was blank. Backed out to the conversation list and got "Loading conversations" again.
I have taken a logcat filtered for anything mentioning sms. Removed identifying phone numbers from it. I have attached it here, starting with the time when 8sms is reinstalled. You can see at 01:47:05.776 the SMS app is switched to Messaging (8sms). At time 01:47:52.886 the first SQLiteConnectionPool error message appears. The messages appear every 30 seconds.
Oh! Interesting. After 10 minutes (01:57:23.016) the last error message is seen. Two seconds later we see an "onQueryComplete finished" message from 8sms. From this point on I was able to open 8sms and see my messages again.
So for a span of 10 minutes, something went on that was locking me completely out of seeing messages, and then it stopped and everything worked. I rebooted to see one more time if it was still working, and yes it does. Perhaps in order to reproduce this error you need to have a big pile of messages already present. Obviously not a lot of Nexus 5 users have this because they just got their phones, but I do because I restored a large archive of messages from my last device.
Hi,
I recognise the query "UPDATE sms SET seen=? WHERE seen=0". It's 8sms marking the messages or threads as seen. Perhaps you had a lot of messages or threads that weren't marked as seen.
Or else, maybe there was a big delay because the database was optimising itself for it's first run or something like that.
In any case, it looks like the problem is fixed now?
Yes it looks like it. However it might be worth looking into whether this problem commonly occurs when switching Kitkat to your client while a large number of messages is present. I believe I had something on the order of 17000 messages in a hundred or so threads. Yes I should probably clean up a bit
Sent from my Nexus 5 using Tapatalk
I had a similar issue. Deleted all my messages (kept the backup file though) and uninstalled and reinstalled. It worked fine.
I plan on restoring over the next few days doing it in chunks.
This is a generic question. I'm not looking for specific help tracking down the problem cuz there seem to be way too many variables. Just wondering if anyone else has experienced/noticed it. Or has any info numerous Google searches has not revealed.
So, every once in a while, a text message sent to me seems to not show up on my phone. The only way I know I got it is because Pushbullet syncs it to my PC and Firefox extension. But when I look in my messaging app (Google Messenger) it is not there. And if I do a backup using SMS Backup and Restore Pro it is not included in the backup.
So my phone must be receiving the message if Pushbullet mirrors it. Which makes me assume it is not a cell service issue. But it is not on my phone, messaging app, or SMS backups. Rebooting, switching SMS apps (tried 8SMS and Textra too), clearing app caches, etc. doesn't reveal said missing SMS's.
Background: Nexus 5, PAC-MAN rom 4.4 RC3, Google Messenger as main SMS app, various Xposed modules (but none that affect SMS), T-Mobile service.
It's only been a couple so far. But could have been more when my PC isn't on. And the reason I am concerned is cuz said SMS's are from pretty girls. So obviously I NEED to receive them
If anyone has any advice/info/sarcastic remarks/etc., I would appreciate it. Thxs!
ghagiel said:
This is a generic question. I'm not looking for specific help tracking down the problem cuz there seem to be way too many variables. Just wondering if anyone else has experienced/noticed it. Or has any info numerous Google searches has not revealed.
So, every once in a while, a text message sent to me seems to not show up on my phone. The only way I know I got it is because Pushbullet syncs it to my PC and Firefox extension. But when I look in my messaging app (Google Messenger) it is not there. And if I do a backup using SMS Backup and Restore Pro it is not included in the backup.
So my phone must be receiving the message if Pushbullet mirrors it. Which makes me assume it is not a cell service issue. But it is not on my phone, messaging app, or SMS backups. Rebooting, switching SMS apps (tried 8SMS and Textra too), clearing app caches, etc. doesn't reveal said missing SMS's.
Background: Nexus 5, PAC-MAN rom 4.4 RC3, Google Messenger as main SMS app, various Xposed modules (but none that affect SMS), T-Mobile service.
It's only been a couple so far. But could have been more when my PC isn't on. And the reason I am concerned is cuz said SMS's are from pretty girls. So obviously I NEED to receive them
If anyone has any advice/info/sarcastic remarks/etc., I would appreciate it. Thxs!
Click to expand...
Click to collapse
I'd be looking at Pushbullet if I were you. Xposed is always a possibility.
Do the texts show up if you reboot the phone?
ghagiel said:
And the reason I am concerned is cuz said SMS's are from pretty girls. So obviously I NEED to receive them
If anyone has any advice/info/sarcastic remarks/etc., I would appreciate it. Thxs!
Click to expand...
Click to collapse
Umm, forward them to me for safekeeping?
Sorry, no helpful insight here. =\
Aerowinder said:
I'd be looking at Pushbullet if I were you. Xposed is always a possibility.
Do the texts show up if you reboot the phone?
Click to expand...
Click to collapse
Nope. Tried that the second time I noticed and no luck. Also tried clearing cache/dalvik (just cuz).
Wakamatsu said:
Umm, forward them to me for safekeeping?
Sorry, no helpful insight here. =\
Click to expand...
Click to collapse
Haha, nice try
Update: reflashed my ROM, set everything back up from scratch (hate doing that) except for Pushbullet. Bought a Sony Smartwatch 3 and using Coffee to txt from it. Got a txt this morning, and when scrolling thru it on my watch noticed a message that was not on my phone again.
I'm wondering if it's Messenger at this point. Gonna switch messaging apps and see how that goes.
Try switching to hangouts or something, also do you set the setting for default sms handler in settings?
lolcakes203 said:
Try switching to hangouts or something, also do you set the setting for default sms handler in settings?
Click to expand...
Click to collapse
I've switched to 8SMS from Messenger. I also went back to stock 4.4.4 and didn't let Google restore any app data. Messenger was the default SMS app. The only time I ever switched it was to restore a SMS backup for whatever reason and switched it right back. I didn't check at the time of missing texts if the default was changed, tho.
I just think they must've been deleted for whatever reason since they didn't show up in a backup. Been on stock with 8SMS for a few days and haven't noticed it so far. Maybe just a weird glitch with Messenger and letting the app data be restored when I reset the first time brought it back? Idk.