I have a stock phone, 2.3.6 no root, no custom rom. All of a sudden, if I try to send an SMS message in anything but the stock Touchwiz SMS app, the send will fail. Have tried Handcent and GoSMS. Both fail. Resend in the Touchwiz app - no problem. They previously worked as designed. I don't 'think' I changed anything.
Can receive, read and everything in any of the apps...
Ideas? If not, I will probably reset the phone.
Thanks in advance.
Try and wipe data in the 3rd party app. It may not be communicating with your RILD properly
Thanks... Tried that... Removed Handcent and Go SMS. Deleted any named directories I found for those apps. Power cycled the phone... sent a message from the Touchwiz app -- fine... Reinstalled Go SMS - fail... Resend from TW app... goes right through...
last step would be to reflash modem... if not, wipe data.
Actually (my) last night. I did a few "factory resets" and SD format on my phone to no avail. Even installed GoSMS as the second program after the reset. Same problem. Touchwiz SMS app works fine. 3rd will not send.
I will probably try again today and be sure I am not doing something stupid to reintroduce the problem.
Solution (I Guess)
Not sure why sending SMS didn't fail altogether. Probably doesn't say much for the carriers in Thailand, but that is a continuing and different story.
Using a couple phones and multiple SIMs, I finally decided to look at the settings on another SIM, same carrier. The SMS Message Center property was not set on mine but had a number in the other SIM on another phone. Adding the number fixed the problem with GoSMS. Not sure why it works in the Touchwiz SMS app without the property, but oh well. Not even sure how I 'lost' it.
Thanks for the help anyway.
Chris
Related
Hi Guys, I have few messages in my inbox that are blank and shows its from 31-Dec-1969. It shows up in both Chomp and android message inbox. I cant delete them in either programs. I have no cache to clear in either and I tried clearing data. Anyone have this or know of a fix? Thanks!
SGK128 said:
Hi Guys, I have few messages in my inbox that are blank and shows its from 31-Dec-1969. It shows up in both Chomp and android message inbox. I cant delete them in either programs. I have no cache to clear in either and I tried clearing data. Anyone have this or know of a fix? Thanks!
Click to expand...
Click to collapse
Back in 1969, they weren't sending too many SMS's around, so SMS functionality was pretty unrefined, and didn't have the delete option.
Ok, sorry. that wasn't very helpful.
k1sr said:
Back in 1969, they weren't sending too many SMS's around, so SMS functionality was pretty unrefined, and didn't have the delete option.
Ok, sorry. that wasn't very helpful.
Click to expand...
Click to collapse
hahahah......
k1sr said:
Back in 1969, they weren't sending too many SMS's around, so SMS functionality was pretty unrefined, and didn't have the delete option.
Ok, sorry. that wasn't very helpful.
Click to expand...
Click to collapse
Equally as helpful...
I tore all my 1969 messages up and burned them.
You tried wiping data using Titanium Backup?
Assuming you have a rooted X10?
yup, tried that.. I have like 7 messages now. All blank and from 31-Dec 1969 and from different people that Ive deleted messages.
Ok so the closest thing I got to your error was when I was using 2.2 with mms settings as Android.
When a png file was being sent I would recieve a blank text with a timestamp.
Saying that though I could do a long press on the thread and delete the thread.
They aint old emails that you deleted from your email server are they?
Saw somewhere that you delete you gmail contacts from your phone then resync from gmail via the gmail web page.
Might be barking up the completely wrong tree though. Sorry!
yeah, Ive read about those phantom emails as well.. non of those fixes work for the messages.
try a repair with SEUS or flash tool and they will be gone i think
I am trying to avoid flashing the firmware... that will be my last option.
I started having this problem just a couple days ago, not sure what started it but I ended up with four threads dated 1969 that I couldn't delete. I read through various forums which suggested a number of fixes but nothing worked.
I did mange to fix it myself though, or at least it's fixed for now. I did this about an hour ago and have rx/tx about 50 SMS since then with no return of the bug.
Download SMS Backup & Restore and back up your messages if you want to keep any of them, this fix will wipe EVERYTHING from the messaging app.
From the Messaging app thread list, press Menu and select Delete Threads. It will ask you to confirm that you want to delete all threads. Say "yes" obviously and bye bye stuck threads from 1969. Of course, bye bye to all the other threads too but that's why you made a backup. From SMS B&R, restore your messages and you should get everything back, minus the 1969 threads.
Your mileage may vary on this one so try it at your own risk. Don't complain to me when you delete that thread with the hottie from the bar the other night. You know, the one with all the pictures she sent you?
i think it maybe happened cuz u took the car from Back to the Future... and while u recieved an sms u were warping back to history. which made this impossible to have and been stuck...
now this how you fix it, go back to the time u warped with the car and stop urselve! else you will mess up much more, u are not allowed to change the past mate.... u mess up the future......
@Coffeedragon, thanks a lot for the tip. It worked. I had originally going to try something like that but I figure the back up would of backed up the blank as well.
oh no...
So I just tried this fix... (Back up messages/settings with Titanium; select all messages and delete) But now ALL my messages are turned into ghosts!!! Also, something many people haven't pointed out yet:
In the stock app, they are ghost messages. In chompSMS, they appear to be changed from SMS to ghost MMS upon deletion.
HTC Inspire 4G
MIUI.us 1.11.18
stock/chompSMS
Got this resolved with some help at the miui.us chat.
1. backed up messages and settings (using MIUI backup, as it was suggested that Titanium is not always great.)
2. Renamed (could delete) mmssms.db
3. rebooted
4. restored messages and settings via miui backup
perfect.
Sent from my HTC Inspire 4G using XDA App
My wife and I both grabbed new S2's on Sunday. Since then when text each other our messages often come through as emails, and the from number is often in a weird format. This is irregular, and I have found no solution. I have called and gone int he store, and neither avenue has given me any form of solution.
This only happens when my wife and I send each other messages. Messages are absolutely fine with everyone else.
Here is an example, I will create a new message to "Jessica" I will send the message. That message will likely show up on her phone in proper SMS format from me. She will reply, I usually receive that one fine as well. I then reply back, this time the message has switched into a strange email syntax type format. It will also show up as a new thread from my cell number @txt.att.net instead of from my cell number or contact name. Often instead of it coming through as the above example the number will change into a different number all together, 1410000021 which in no way resembles our actual numbers.
It doesn't matter if I initiate the conversation or it she does. We have cleared all message threads, history, and contact information attempting to flush out errors. We have tried other SMS apps, such as Handcent, still no luck. I have also tried a different SMSC number.
Any suggestions?
Try a factory reset?
Stock rom? Rooted?
Sent from my SAMSUNG-SGH-I777
we have not done a factory reset, we are new to android, if we did that would we lose all of our contacts, media, and installed apps?
They are both stock.
tgmm82 said:
we have not done a factory reset, we are new to android, if we did that would we lose all of our contacts, media, and installed apps?
They are both stock.
Click to expand...
Click to collapse
Do you have AT&T's new-ish (at least to me it is, had never heard of it till i got my SGS2) messages app, that incorporates all your phone calls, texts, voicemails into one app? It uses MMS to send you transcribed voicemail in a visual voicemail type layout. I haven't played with it myself, but my wife is using it (on her sgs2). I'm wondering if it could be a setting in there somewhere that is triggering duplicate messages?? My wife isn't getting duplicates, but just tossing it out there....
I don't believe we have the messaging app you mention. I am not sure though as we are new to Android so I am unable to know if this is the newish app. It does not have voice-mail included in it though. We have tried using both the stock app and Handcent, neither fix the solution. Also, its not duplicates we are receiving, we are only getting one copy of each message, they are just showing up as emails.
Hey,
I'm having an issue and I'm not sure how to debug or where to seek for solution. Sender told me, that she sent me two messages, received reports, but I had received none. This is really hard to pick out, because if sender gots the report then he usually dont send the message again or tell me about it, unless it was an important message. I just installed Ghostly SMS app, but I'm not sure if it is the case, as my SGS should not be missing of ram, and I wasn't doing anything that would be using ram excessively (probably phone was just at the pocket at this time).
Any ideas how to find the source of such behaviour? My sim card is new, and I'm running omega v43.1 with stock kernel.
Thanks
Usually that is caused by your or the sender's network provider and not one of your device's.
I always notice it wheo sending from Germany to Luxembourg. I get SMS' like 8 hours later (if ever) but sender almost immediately gets the notification.
Sent from my GT-I9300 using xda premium
Problem is that I'm not using a lot of sms so it is difficult to catch some regularities in such behaviour. But maybe there is something for which I could look in logcat?
If it's caused by your provider as I suspect then your device does not get the sms. Unless you have access to your provider's logs you can't read them.
I've had people call me on sim cards that were not in a device and have it ring through or Sms that were "received" by devices which were not powerd on for months. So yeah =)
Sent from my GT-I9300 using xda premium
Ok, ghostly SMS just managed to restore 2 messages which didn't show in default messaging app. That makes me sure, that the phone actually receives these messages, so it's not the fault of the provider or sim card.
These 2 messages were received in a different time. After I noticed first one missing, I texted the sender to ask if she wrote me anything else, but she didn't and her answer was also received as a ghost sms. No huge resource consumming apps were running at this point - phone was on the desk with nothing running and screen turned off.
You could try a non-stock Sms app with a priority receiver, such as Go sms.
Sent from my GT-I9300 using xda premium
Thanks, will give it a shot. But do you think that I should keep the default sms app? There's an option in go sms pro that it can handle messages if the stock app is uninstalled - I could do this using titanium backup or something and restore it in case of problems.
Ok, I did two things:
1. Tried installing Go sms pro along with stock message app - problem still occurs.
2. Tried uninstalling stock sms app and making go sms pro the only app which has to handle sms sending-receiving. But honestly I'm not sure about the results... First because ghostly sms is not working in such scenario, so I had no feedback from this app. Second is that nobody told me that I missed some messages and didn't answer.
So I'm stuck again and have no idea what to do. It happens on different network trans-receivers (I mean its not location dependent), also it is not sender-dependend (I miss even spam messages) and it's not sim-related because I had my sim changed. I believe that there must be something with the stock sms app, otherwise there wouldn't be apps like ghostly sms.
I have had similar issues chronically. Likewise found ghostly sms has received some that stock didn't receive.
In past I have found Go did no better. However, I have not rooted and did not remove stock app.
Among "power but non-root users", I don't think of myself as having lots of apps, but compared to more "normal" users, it is a lot. So I suspect that like me, you may encounter more memory issues than you are aware. I regularly run: facebook, fb messenger, accuweather, hacker keyboard, nitro touchdown, stock email (couple accounts), mypod, xabber, business calendar, stock browser.
Another observation though is the bloat that occurs in the messages database. I receive probably 20-50 messages each day that I can quickly delete (from automated monitor system). If I go to settings -> applications -> all, then I can see data and cache size for Messages is perhaps several MB. Clearing these, I then open Messages and it apparently rebuilds the database, as data size now quite reasonable. No messages lost. If I also reboot, it may send messages that it apparently thinks were not successful (sometimes it is correct, sometimes recipient reports it is a duplicate). However, after this, message delivery seems more reliable for a while.
Now, it doesn't take long for the unreliability to return, at least not 100%, so I will continue running ghostly. But with the occasional rebuild, I no longer have the situation where it seems I am losing most of my incoming, which I have seen.
So, it would seem that the messaging database can get corrupt or performance becomes so poor that it is effectively corrupt.
YMMV, obviously, but hopefully these observations help someone find the real problem. This is a very annoying and serious issue.
Sent from my ADR6325 using xda app-developers app
Hey,
I've almost forgot about this thread. I managed to deal with the problem by removing V6 supercharger script from the Omega rom which I use and it seems that for a few weeks now I havent lost any message.
However in your case this must be something different. In information about messaging app I have that the app takes 4.17MB, Data takes 16kB and cache is 0B. Version of my messaging app is reported as 4.1.2.-I9300XXELLC
Garreth88 said:
Hey,
I've almost forgot about this thread. I managed to deal with the problem by removing V6 supercharger script from the Omega rom which I use and it seems that for a few weeks now I havent lost any message.
However in your case this must be something different. In information about messaging app I have that the app takes 4.17MB, Data takes 16kB and cache is 0B. Version of my messaging app is reported as 4.1.2.-I9300XXELLC
Click to expand...
Click to collapse
I'm using Omega rom too and I have the same problem. I got all SMS with Ghostly SMS. I notice the problem appear after doing a Nandroid restore or Omega upgrade without full wipe. I will now remove supercharge to see what happen.
---------- Post added at 04:11 PM ---------- Previous post was at 04:07 PM ----------
cgaylord said:
I have had similar issues chronically. Likewise found ghostly sms has received some that stock didn't receive.
In past I have found Go did no better. However, I have not rooted and did not remove stock app.
Among "power but non-root users", I don't think of myself as having lots of apps, but compared to more "normal" users, it is a lot. So I suspect that like me, you may encounter more memory issues than you are aware. I regularly run: facebook, fb messenger, accuweather, hacker keyboard, nitro touchdown, stock email (couple accounts), mypod, xabber, business calendar, stock browser.
Another observation though is the bloat that occurs in the messages database. I receive probably 20-50 messages each day that I can quickly delete (from automated monitor system). If I go to settings -> applications -> all, then I can see data and cache size for Messages is perhaps several MB. Clearing these, I then open Messages and it apparently rebuilds the database, as data size now quite reasonable. No messages lost. If I also reboot, it may send messages that it apparently thinks were not successful (sometimes it is correct, sometimes recipient reports it is a duplicate). However, after this, message delivery seems more reliable for a while.
Now, it doesn't take long for the unreliability to return, at least not 100%, so I will continue running ghostly. But with the occasional rebuild, I no longer have the situation where it seems I am losing most of my incoming, which I have seen.
So, it would seem that the messaging database can get corrupt or performance becomes so poor that it is effectively corrupt.
YMMV, obviously, but hopefully these observations help someone find the real problem. This is a very annoying and serious issue.
Sent from my ADR6325 using xda app-developers app
Click to expand...
Click to collapse
I tried the same thing (Clear data) for the SMS app didn't help.
Ghostly SMS work.
Like I just mention I will try to disable supercharge to see what happen.
Hello hello,
I updated my Note 3 on ATT via the OTA update to 4.4.2. I did the factory data reset. I restored my sms via the SMS backup and restore app. All the messages are here but the app seems to be working slow and laggy. The SMS Backup+ did not really work. What are my other options?
Thanks!
How many text messages did you restore? Did you test before and after you restored the messages? But seems like you have a couple choices, 1 - try it without restoring the messages. If you have 1000s, that could be why. 2 - try a 3rd party SMS app and see if the problem exists there or just stock.
Thanks for the response. SMS backup+ says I have 14000 items. The app works great before the backup.
I am a little disappointed with Android right now. iTunes was restoring everything to exactly where I left off. I surprised Android does not have a working sms restore function. Kies does not even offer it. How about manually copying the sms database file that I saved.
I guess I still have to try a 3rd party app but I prefer the stock one.
Cheers.
es0tericcha0s said:
How many text messages did you restore? Did you test before and after you restored the messages? But seems like you have a couple choices, 1 - try it without restoring the messages. If you have 1000s, that could be why. 2 - try a 3rd party SMS app and see if the problem exists there or just stock.
Click to expand...
Click to collapse
panxpany said:
Thanks for the response. SMS backup+ says I have 14000 items. The app works great before the backup.
I am a little disappointed with Android right now. iTunes was restoring everything to exactly where I left off. I surprised Android does not have a working sms restore function. Kies does not even offer it. How about manually copying the sms database file that I saved.
I guess I still have to try a 3rd party app but I prefer the stock one.
Cheers.
Click to expand...
Click to collapse
That amount of text messages will make many things lag (and take FOREVER to restore). But there are quite a few different ways to back up and restore texts so I guess Android doesn't think it's necessary to include it? I backup and restore texts all the time as I am a serial flasher and never have issues like that, but I also don't have any reason to keep 1000s of texts messages on my phone.
On my Galaxy S5, running Android 6.0.1., when I try to send a text message to a number that does not have a saved conversation, the app I'm using always crashes, gives me an error, or does nothing instead of sending the message. The built in Messages app and Facebook's Messenger app both crash, while Google Messages gives me an error saying it couldn't create the conversation, and Go SMS Pro seems to work at first, but actually does nothing.
I've also deleted caches/data and removed old texts/conversations, and nothing seems to work.
This is clearly not a problem with one app, but rather something larger at play. What could possibly be causing this?
Sounds like something corrupted your SMS data base and it will take a wipe to fix it. Go SMS pro is the normal cause for corruption. It's a male are ridden app that users here stopped using years ago.
Darn, is there any other way to fix something like that? I use my phone for work, so I don't really want to wipe it and spend a bunch of time updating/reinstalling.
Go SMS Pro was just a last attempt to try any other SMS app, rather than one I've had, so it's probably not the culprit.
If you had root you could try to wipe the data base file.
Give textra a try. They use their own separate SMS data base. So that might help.
Other then that you might spend an evening backing up and flashing a stock clean build.