Related
My wife's Infuse was running Serendipity VII. She was having some minor problems with it (such as the camera's flash not working consistently) and some apps crashing. So we decided to go with Zeus. Then the problems really started pouring on.
I flashed Zeus without doing a factory reset. I just wiped the cache partition and the Davlik cache. It was OK for a day or two, then it started misbehaving. More crashes, sluggish, when she sent a text message she'd get a "Message not sent" error (so she'd keep trying until she didn't get the error, meanwhile every attempt was actually being sent so people were getting her texts multiple times), Mobile AP would turn itself off (we do pay for the Mobile AP plan with AT&T).
So I did a factory reset/wipe user data, wiped the cache areas, and re-flashed Zeus. Restored everything with Titanium Backup. No change in behavior.
So, I used Odin to flash back to stock UCKD5 (using this). Things were OK for a day or so except that the time was displaying UTC time instead of local time. (I started another thread about that.) Then, the mobile AP started shutting off again, now with a message saying we don't have a Mobile AP plan. But we do. I flashed a new modem (UCKL2) last night hoping that would clear up both issues. It fixed the time problem, but Mobile AP is still saying we don't have a plan. And now she's also getting the "message not sent" error again when sending text messages (although the messages ARE being sent).
Any ideas on what the heck happened and what I could do to get her going again? Using the "Mobile AP" is essential as it is our only home internet connection (no cable or DSL available and we ditched satellite a few months back) and our kids are enrolled in an online school.
Would flashing another ROM clear things up? Maybe try stock again with the "ultimate unbrick" package or the Heimdall one? Or maybe try Zeus again? Or CatyRom?
I reflashed to stock again using ultimate unbrick. (Wiped cache, factory reset, Odin to stock.) Mobile AP gave same errors. Texting seemed fine, but with Mobile AP not working I didn't test it long. Flashed Zeus again (Rooted, installed CWM, wiped cache, factory reset, formatted internal SD, installed the Zeus zip, rebooted and waited about 15 minutes before touching it.)
Mobile AP is fine (for now anyway) but texting is flaky. Some texts go through, but most don't. She just gets an error saying "Message not sent."
Any ideas out there???
HeathicusF said:
I reflashed to stock again using ultimate unbrick. (Wiped cache, factory reset, Odin to stock.) Mobile AP gave same errors. Texting seemed fine, but with Mobile AP not working I didn't test it long. Flashed Zeus again (Rooted, installed CWM, wiped cache, factory reset, formatted internal SD, installed the Zeus zip, rebooted and waited about 15 minutes before touching it.)
Mobile AP is fine (for now anyway) but texting is flaky. Some texts go through, but most don't. She just gets an error saying "Message not sent."
Any ideas out there???
Click to expand...
Click to collapse
Idk..maybe you need and apn change.
Go to settings. Wireless. Apn.
Menu to bring up 2 stock apn.
create a new one. it's around..check my sigs line. After you write it in, menu and save. Select the new apn.
Reboot
Found the APN info in the first link. Thanks! Does the name matter? I noticed it is "AT&T WAP" on my Captivate but "AT&T 310 410" on her Infuse.
HeathicusF said:
Found the APN info in the first link. Thanks! Does the name matter? I noticed it is "AT&T WAP" on my Captivate but "AT&T 310 410" on her Infuse.
Click to expand...
Click to collapse
no..you can call it what you want.
HeathicusF's 310 410
but just for s&g's, I would call it "AT&T 310 410"
Did it fix your issue?
I haven't made any APN changes yet. She uninstalled GoSMS (which had been restored with TiBu) and reinstalled it from the market. That was a "grasping at straws" solution since the problem was happening in both GoSMS and he stock SMS application. So far, no problems. But there have been other little spans of time with no problems then it would start acting up again. So I'm just keeping an eye on it right now. There are some differences between her APN settings and the ones listed, but I don't want to change anything if it really is working now.
OK she has narrowed it down to a problem with long text messages. Anything over 160 characters will fail. That is why she thought it was flaky and working for a while each time we made a change. She'd send a lot of short "testing" type messages, which would go through and she would think everything was good. Then eventually she would write a long "real" message and it would fail and she would think the problem had "returned". Not having any problems like that before, she never associated the problem with the message length.
Based on some quick research, I think that is a modem problem.
If we can fix this issue, she'll be all good again.
HeathicusF said:
OK she has narrowed it down to a problem with long text messages. Anything over 160 characters will fail. That is why she thought it was flaky and working for a while each time we made a change. She'd send a lot of short "testing" type messages, which would go through and she would think everything was good. Then eventually she would write a long "real" message and it would fail and she would think the problem had "returned". Not having any problems like that before, she never associated the problem with the message length.
Based on some quick research, I think that is a modem problem.
If we can fix this issue, she'll be all good again.
Click to expand...
Click to collapse
lol..click on my sigs -link #1. Read post #2.
it has to do with a modem ucki3.
She has UCKL2.
EDIT: I misunderstood and thought you were saying the problem was with the UCKI3 modem. Should have looked at that post you pointed me to first. I see now that UCKL2 is the problem and UCKI3 is the solution.
HeathicusF said:
She has UCKL2.
EDIT: I misunderstood and thought you were saying the problem was with the UCKI3 modem. Should have looked at that post you pointed me to first. I see now that UCKL2 is the problem and UCKI3 is the solution.
Click to expand...
Click to collapse
..........
I've searched the forums and Google'd this, but nothing seems to give any resolve to my issue. I am showing a voicemail notification icon in my status bar, but after calling my voicemail it says I have no new messages (nor do I have any archived, saved, etc. messages).
This just happened to show up two days ago after missing two calls from the same individual. Both calls had voicemails for each, and I deleted both, but the notification icon still shows.
Sorry if this is a repost or similar, but I just can't seem to find a fix. I tried to look up AT&T's voicemail pilot numbers but no luck there either...
As always, thanks in advance for your replies!
I use google voice for my vmails.
That way I can read them like a text instead of listening. Never had a false signal from them.
Also, keep in mind if you flash new roms a lot and use TIB to restore your data, the restore of the data specifically will send a false notification once. Or so I have noticed.
Sent from my MB865 using xda premium
Fall of Enosis said:
I use google voice for my vmails.
That way I can read them like a text instead of listening. Never had a false signal from them.
Also, keep in mind if you flash new roms a lot and use TIB to restore your data, the restore of the data specifically will send a false notification once. Or so I have noticed.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
I haven't backed up any data from TIB or otherwise, just in setting up the phone after a freah data wipe checked the "back up from Google servers whatever thing" and maybe that's what's causing it.
I'm going to try to wipe again and NOT check that as my option...
I had this problem. Usually for me calling voicemail again would fix the issue. After the voicemail service said that I did not have any voicemails I would hang up and the notification would go away.
I switched to Youmail voicemail service because I got tired of this problem and haven't had a problem with false notifications since.
I'm going to try a couple of other things. I've seen this before in other forums, but no one seems to have a good resolution for this. Get back with y'all...
Okay, super weird. I just booted into CWM and wiped data, cache, Dalvik and restored my current rom I've been using (Lithium v1.3) and without checking the 'back up from Google server' option, went to check if the rogue voicemail notification was still there, and it wasn't!
So, I guess it was a glitch in the "backup" that Google had for my device that when clicking to enable it to backup from Google held that false voicemail in the status bar, but once I opted to NOT back up from Google there wasn't one.
Had this happen to me recently and called AT&T. Was told that this sometimes spuriously happens and they can clear this from their side.
This can also happen sometimes with Google Voice...even if you don't use it as your default voicemail (which I didn't to begin with) if you have the app installed and didn't clear the initial "message" that comes in your inbox (which I didn't) then you can sometimes end up with a VM notification...it's actually correctly reading that you have an unread voicemail, just from the wrong app.
Now that I use Google Voice (and don't have any unread voicemails) I don't have this happen anymore.
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.
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.