I have Google Voice integration set up via Sprint (and I'm using the default text message handler).
For some reason when I have a conversation actually open on the screen I can get a text message (sound and vibration), and the message bar at the top will preview it, but it's not showing in the actual conversation.
I've missed several MMS this way (as well as normal texts).
Craysh said:
I have Google Voice integration set up via Sprint (and I'm using the default text message handler).
For some reason when I have a conversation actually open on the screen I can get a text message (sound and vibration), and the message bar at the top will preview it, but it's not showing in the actual conversation.
I've missed several MMS this way (as well as normal texts).
Click to expand...
Click to collapse
yea, if i read your post right, it sounds like the same bug i've been experiecing. def an odd bug in the htc sense messaging app they provide as stock software. i'm also using gv thru sprint integration. usually hitting the back arrow to exit the conversation and move back to the sms inbox then allows the new message to populate.
because of this bug i've now developer the habiting of exiting all conversations and going back to the inbox before turning the screen off or switching programs.
if you're experiencing a different bug, could you perhaps provide more detail?
Pretty much the exact same thing except it never comes back, even if I hit back and go back into it.
I'll give another messaging app a try.
Craysh said:
Pretty much the exact same thing except it never comes back, even if I hit back and go back into it.
I'll give another messaging app a try.
Click to expand...
Click to collapse
oh how odd the message doesn't appear when you exit the conversation..
perhaps there is an issue with the sms-mms database the app is using. the only easy solution there would be to wipe the database it is using and start fresh. i don't think there are any tools for analyzing the sms-mms database used by the htc messaging app as the sms-mms databased used by the aosp messaging app is different.
if wiping the database doesnt clear the issue, then it would appear most definitely to be a htc messaging app bug.
also, the nice option with google voice is you can check the gv app on your device to see whether or not the actual message came all the way through. if it appears in gv, but not in htc stock messaging app, thats def a bad sign for the htc messaging app (assuming you have good cell signal).
perhaps one of the developers might be encouraged to take a look into the app and see if its a bug they're able to fix through decompiling and recompiling the app.
Handcent seems to have fixed the issue.
I wouldn't be able to check Google Voice since the issue seems to have been most prevalent on MMS messages.
I've had lots of issues with Google Voice integration. I would randomly stop getting text messages for 1-2 hours at a time, every 2-3 days. If I checked Google Voice the messages were there, but they never came in on my phone. I could send messages to other carriers just fine. I couldn't get their messages though. Sprint was no go both ways.
After I deactivated Google Voice, the issue went away. Sucks, I'd love to use the application.
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.
My wife has had a Note 3 for a month or so now. She's on stock unrooted 4.3. When she uses the default messaging app and writes an SMS message longer than 160 characters (I haven't counted, but presume this is an SMS 160 character limit issue), only the first 160 characters send, and the rest of the message never gets to the recipient. The app gives no indication that anything unusual has happened. We only figured this out by sending messages back-and-forth and comparing the results. I use a Galaxy S4, rooted stock 4.2.2, and the default messaging app doesn't have the same problem. Using Handcent fixes the issue on her phone, but she prefers to use the stock messaging app. I've searched here, the Sprint Community, and on Google and don't see anyone else having this same issue. Any ideas?
Auto combination checked?
Thanks for taking the time to reply...turns out the issue is with my S4, not the Note (I haven't figured out what it is yet)...please feel free to delete this thread.
Chops it up on both Verizon and Sprint s4's I have also.
In case anyone comes across this later with a similar problem, unchecking that auto combination box in the messaging app on my S4 fixed the problem...I have Handcent set as the default SMS app, but I guess that check box still affects the handling of large SMS.
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.
Im having this strange issue where the google messages app wont send or recive MMS.
The native huawei messages app has no issue with either sending or receving MMS messages.
I have checked the APN, but as the native app is working, this is prolly not the issue.
I have checked the permissions, and given permission to everything.
I have checked the battery settings for the app, and everything looks good.
Does anyone have any clue what is going on?
After having investigated further, i have now found others with similar issues.
I have not found the cause, but installing ChompSMS and putting it in Legacy mode makes MMS work in Chomp, no other 3rd party messanging apps work.
Is there really no one else experiencing something similar?