It would seem that it sorts the thread by the time on the message for incoming texts, but by the time on the device for outgoing texts. This means it relies on the clock on the device being spot on when sorting the messages in the thread. It turns out mine was a couple of minutes fast, so it meant that in a fast-paced conversation I just had, it was placing replies before the questions, because the timestamp on the message coming in was a minute earlier than the timestamp on the question going out.
Sure, I'll make sure my clock is correct (can't the device do that for itself, from the carrier?), but it's still potentially an issue because it only has to be a minute out.
Related
I've got some small issues with the messages for the phone.
I noticed that frequently, I have been receiving sms that have a time stamp of 1-3 hours later than i actually received it.
for example, it's 1am now and I can receive sms that was apparently sent at 2 or 3am same day.
Another thing is, although most sms displays the correct time for that day. How do i show the exact time for older sms ? sometimes i need to check when exactly I receive the sms from senders.
thanks.
tarui04 said:
I've got some small issues with the messages for the phone.
I noticed that frequently, I have been receiving sms that have a time stamp of 1-3 hours later than i actually received it.
for example, it's 1am now and I can receive sms that was apparently sent at 2 or 3am same day.
Another thing is, although most sms displays the correct time for that day. How do i show the exact time for older sms ? sometimes i need to check when exactly I receive the sms from senders.
thanks.
Click to expand...
Click to collapse
HELLO. PLease note that if you searched you would have found these answers. Try search for SMS Time Stamp Incorrect.
My threaded sms displays the correct time. However, I cannot see the time for older sms within the same thread from the previous days. Anyone?
redbandana said:
My threaded sms displays the correct time. However, I cannot see the time for older sms within the same thread from the previous days. Anyone?
Click to expand...
Click to collapse
I don't recall anyone finding a way to fix this.
About the nexus randomly refusing to send texts when I have full bars and 3g, is there a way I can make my superphone send text messages again without a reboot? And is there something done by the user that causes it or is it just another screw up? I ran a search :
http://www.google.com/m?hl=en&gl=us...droid-browser-key&q=nexus+one+texts+wont+send
but all of the posts I found included failed calls but I'm pretty sure I can still make calls so I don't know if my issue is different. Thanks
P.S. is this considered a bug in that we can expect a fix from Google? And is there an organized system open to the public not just of all the bugs but of all the bugs we can expect Google to address? I think I've seen it before but I can't remember how to find it. I ran a search but this is as close as I got.
http://www.google.com/support/forum/p/android/thread?tid=2a024bb25d4496ff&hl=en
Thanks
I don't have an answer as I have this issue randomly also.
I didn't have it for a few weeks and this week suddenly it happens everyday. Besides rebooting, nothing I do fixes it.
One weird thing is I can still send text messages through Google Voice, but sms and "sometimes" phone calls don't work. It's sooooooo frustrating!!
i have not ever experienced this issue, but i read about it alot. is it because you guys are using the stock messaging app, and i have been using handcent since day 1?
possibly. ive used the native messaging app almost exclusively, but chomp had the same issue for me.
Lately, after a few failed attempts I can get the message to send without a reboot maybe 25% of the time, on the other hand the problem seems to be becoming more frequent for me...wish i knew more about this stuff.
I've had this problem a couple times now, and specifically three or four times in the past six hours.
With the stock Messenger App, auto delete set to occur after threads have reached 200, again this is all the stock settings. I'll get the standard notification sound that a new message has been received. But instead I get a notification that says something along the lines of:
'Incoming message blocked, message limit reached'.
After this occurred the first time tonight I deleted all my longer threads (all of which were still under 200 messages). This is what I did the first time months ago when it first occurred, and haven't had issues since. Anyway the problem persisted this time, and I ended up having to delete all my messages and threads, not to mention I didn't receive upwards of 4 messages tonight, which really could end up screwing things up for me.
It appears that either there's an overall limit for maximum messages regardless of thread length, which is being reached, or maybe a maximum amount of threads. Either way it sucks.
I would have thought this to be a pretty common problem, but wasn't able to find anything.
Look at your free space in /data partition (free space for apps). Did you notice "low on space" notification? You probably had less than 20MB left, and under this condition incoming SMS are blocked.
I have an XT1095 Rooted on stock 6.0 and the stock text messaging app has the annoying habit of not playing a notification sound, or vibrating, if the messaging app is open. This means that if I'm typing in landscape mode I have no idea if the person I'm sending a text to sends another message to me because I can't see or hear it. Their new message could possibly negate whatever it is that I'm typing so I waste time typing out a message that I end up erasing and starting over. This happens frequently. Even more annoying is when I finish sending a text message and set the phone down without locking it and without closing the text app. Since the back of the phone is curved it usually rocks to the side slightly as I set it down which puts it into landscape mode with the keyboard showing, totally covering the screen, and then I have no clue if/when I receive a new message during the time that the phone is waiting to timeout. I've waited an hour for a reply to a message that had already come during the 30 second timeout period and I had no clue it was there.
I've searched everywhere for how to turn on text notifications even when the app is open but I can't find anything. There's another thread on here where the person has a problem where they don't get text notifications when they're on a phone call. I have that same problem but it doesn't bother me that much. That's the closest thing I could find here. On some other site someone had the same problem with Lollipop on a Samsung, but the reply was that it was Samsung's tweak and there was nothing they could do about it. Am I also stuck with it since there don't seem to be any settings for it? Or am I having a moron moment?
Hi! I've searched lots and yet haven't found any info about it, maybe it's my original idea then. Is anyone of you aware of an Xposed/Magisk module/App that could merge several consecutively received SMS' into one, or at least use one sound notification for them? I will tell you what I need based on my case: I have an alarm at home, it is divided into three zones (ground floor, 1st floor, garage), for each arming/disarming, this "stupid" module notifies me with a text message for each zone, of course I can switch off SMS for two zones and leave only one but that's not the goal. So what I get is:
SMS #1: Alarm ON - ground floor
SMS #2: Alarm ON - 1st floor
SMS #3: Alarm ON - garage
same for OFF. I'd like to find a solution that could work on my phone for this particular phone number from which I get those, to merge the 3 SMS into one, or at least for each of them (sent with a difference let's say up to 10 seconds) give me one sound notification. It's just a bit annoying to get three instead of one message each time I leave or come back home. So... "Necessity is the mother of invention".