Hi all, I'm just wondering if anyone can help me figure out this problem.
I can't seem to find a timestamp on SMS messages for any days other than the current day. So if I received a message at 7.01am today I can see "07:01", however if I want to look at a message I received a few days ago, all I can get is "Oct 3", and bringing up the menu and clicking "View message details" still only shows "Oct 3".
Is there a way to show the entire timestamp? This seems like a terrible oversight if it's not possible to see what time an SMS was sent/receieved for any day other than the current day.
+1. Incredibly annoying "feature".
I am sure it is available in the sms logs, it is just not being shown.
I guess they did it to remove clutter, in the assumption that people wouldn't care about the timestamp of messages from yesterday, but that is just not true. Particularly when it has just gone past midnight!
It is the recency of the message that is important, not whether it arbitrarily happened today or yesterday.
How about ChompSMS and those other SMS apps, do they show them?
Yep!
Handcent SMS is the way forward. The stock messaging app just doesn't cut it...
Ok, I've looked around and what I'm looking for doesn't seem to exist, I was wondering if it was because it is technically impossible/very hard to do or because nobody try it yet.
This is my understanding of how things work:
After receiving an SMS message, the recipient mobile phone will send back a message delivery report to the SMS center to inform whether there are any errors or failures (example causes: unsupported SMS message format, not enough storage space, etc). This process is transparent to the mobile user. If there is no error or failure, the recipient mobile phone sends back a positive delivery report to the SMS center. Otherwise it sends back a negative delivery report to the SMS center.
If the sender requested a status report earlier, the SMS center sends a status report to the sender when it receives the message delivery report from the recipient.
Click to expand...
Click to collapse
What I'm thinking about is way to do this: Once a phone receives the SMS, it sends a spoofed "Storage full" or "Message format not supported error" to the SMS center instead of a positive delivery report.
That way you could receive and read SMS but to the sender it appears you haven't received it. In short this gives you plausible deniability.
I've had it happened to me recently because my phone memory was full. My phone sent a "Memory full" message to the network and the sender did not receive a message report. If a phone can legitimately refuse to receive a message it means it could also be possible to fake that "memory full" message.
Any thoughts?
I love the idea, but the only time I would see having the need for this kind of plausible deniability (i.e. a court of law), the person questioning the receipient of the text message could simply ask for a record of the phone bill which, in most cases (if requested), could provide the time and date of all text messages sent and received. lol. Just curious, but do you mind if I ask what you would use it for? (sorry for the run-on sentence)
I like this idea..maybe a reverse engineering hack of SMS Counter or another counter type widget/app?
t-mo123 said:
Just curious, but do you mind if I ask what you would use it for? (sorry for the run-on sentence)
Click to expand...
Click to collapse
There would be several uses for that kind of app.
One of the scenarios (the one that got me thinking about it) is someone receiving unwanted messages from a specific individual, for example from someone abusive. Even if the victim trashes the messages without reading them (they are several apps available that allow you to do that), through message reports, the abuser is still able to know that his messages were at least received by his target. If he keeps receiving "undelivered" statues, he'll simply stop sending texts.
I know that in those kind of situations the victim is expected to change her/his phone number, but that's the whole idea, not having to change your phone number just because of unwanted text messages.
Still no way? Any app to do this?
I have recently purchased an S3 and I am quite happy with it except it is showing one unread message and when you open messages there is not any unread messages.
I have managed to clear it by rebooting my phone and then when I receive another SMS it goes back one unread even though I have read.
How do I clear this annoyance.
sandy0810 said:
I have recently purchased an S3 and I am quite happy with it except it is showing one unread message and when you open messages there is not any unread messages.
I have managed to clear it by rebooting my phone and then when I receive another SMS it goes back one unread even though I have read.
How do I clear this annoyance.
Click to expand...
Click to collapse
Are you using the stock messaging app? I bet you're not... If you have a third-party SMS app, the stock messaging app will continue to register and notify about new messages received, even if they've been read in the third-party app.
To resolve this, just switch off notifications in the stock messaging app.
This is a bug in the firmware, it has been fixed you just need to wait for the OTA to be pushed to your phone
anthropolyte said:
Are you using the stock messaging app? I bet you're not... If you have a third-party SMS app, the stock messaging app will continue to register and notify about new messages received, even if they've been read in the third-party app.
To resolve this, just switch off notifications in the stock messaging app.
Click to expand...
Click to collapse
No. This is a problem with some S3s. Check this: http://forum.xda-developers.com/showthread.php?t=1705015
My colleague had this issue and I played around with it on Friday without success but she says that the issue was resolved on Friday and she has received several messages and calls but the 1 is not stuck on the icon after reading the message anymore. I am at a loss as to what I did...
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.
Has anyone else been having issues with messaging iphones requiring a read receipt request lately?
This didn't happen for the first few months. Recently been getting this pop-up every time I receive a message from iPhone users.
Is apple trying to get into RCS and it's causing issues?
Tried all the combinations of settings, chat, SMS, MMS, or otherwise within default SMS app settings. Checked settings on iPhone test phone (couldn't find a "request read receipt" setting), still happens. Group message or otherwise.
The only workaround I've found is using the chat bubble (or using G.messages) . However the read receipt pops back up if I ever open the thread in the default SMS app.