I am not sure if I am the only one, but noticed a slight problem regarding to SMS display.
It's regarding the sender's and mine timestamp. Not sure why, but SMS's I recieved from a friend who was responding to my SMS got timestamp lower than my original SMS. I would understand if it would be some seconds, but the difference there was ~2 minutes. So basically his reply to my sent message was put above my message. Seemed like it would be sorting the messages according to sent time from my friend's telephone
Anybody else noticed such glitch? Any workaround ?
It's a known issue for some people. It's a problem with the timestamps on the messages themself but can sometimes be remedied by altering you phone's time. Do you have the date and time settings as "automatic" or are they manually configured by you?
am on automatic. And I don't really see a point of going away from ntp syncing. Is it possible to mark incomming SMS's with current timestamp of MY phone ?
Related
I have a Mio A701 with WM5, the latest official ROM.
Whenever you write more than 160 characters (or 80 in Unicode, I've disabled the Unicode option anyway), that message will be sent in multiple sms.
The thing is, whenever I pass that limit (160 characters), aka need to send a multiple sms message, I just can't send it. I always get the error "Your text message cannot be sent".
So, is this a bug, an option that can be checked/unchecked? The logical thing would be windows sending it automatically, wouldn't it?
yeah it should auto split it into 2 and send them both it works for me
so it could be an issue with the rom you are using or the operator but then
people with other phones would get the same prob
I also thought that maybe was some kind of configuration I had to do because of the operator, because with other cellphones I could always send text messages like that without any problem. I've asked this in many places but never got a reply
No one really knows a solution to this? Or at least that it happened to someone here? I'm still stuck with splitting the messages manually I've changed my rom to WM6.1, but it's still the same! With generic cellphones this never happened, so I don't really know where the problem is coming from.
I've thought that maybe it's because the sending timeout is too short... Can that be changed in the registry?
I'm back again! And still with the problem
I've found out that with SMS Chat v1.05, I can send messages normally. With any more recent version, or any other program, the same problem occurs. Any idea on why?
Whenever I get a SMS from someone overseas, the time shown on the SMS is in their timezone, rather than mine. This is a bit confusing and also means that new SMSes from other countries are listed below other messages I've already read. Is there a way to get Windows Mobile to show all times in my time zone?
Bump...
Am also having this problem with my new HTC Touch Pro, except the times are totally off (the person that's messaging me is way behind my timezone, yet their messages appear two hours ahead of my timezone?)
Anyone know how to fix this? It's pretty annoying
I've tried with "search" but I cannot match the keyword ....
So, there was a time when restoring your contacts from pimbackup was harmful to the sms app, I cannot send text message longer than 160 chars (I can send them, no errors, but they are not received)
Anyone knows how to solve this issue? I've this bug on my HD2 from various roms, so, I think that it's related with the stored contacts
Maybe there's something with the tags that HTC Sense stores in the "notes" tab of each contact, in this case, there is a way to wipe all the notes of each contact automatically?
Oh yes you can!!!
As far as I know, it's nothing to do with you having imported contacts etc. from PIMbackup......it's just the way it goes....
By default, the messaging application is set to "use Unicode when necessary" which results in long messages being broken into several chunks of 160 characters or less. The messages are delivered (eventually) to the recipient, but their order is not guaranteed.
To "fix" the problem, go to the Messaging tab, tap All Messages, then Menu, then Settings, then Options and un-tick the "Use Unicode when necessary" option, tap Done.....and that's it - problem "fixed"!!
Now, when you send a long message, it is sent as a whole message to your network where it is broken up into 160 char chunks before being sent. The recipient, assuming their network supports long SMS messages, receives your message just as you sent it.
Hope that helps,
Mark.
PS. There is some sort of history to this "feature"; back in days of the HTC Hermes (and others), having Unicode switched on meant that you could only send 70 characters even though the messaging app thought you'd used 160 characters. People were sending a 150 char message and getting charged for three messages - two of 70 chars and one of 10 chars....
Thanks man;
My network supports long sms, but I can't seem to be able to send them anyway :/
I'll make another test
Edit: Nope, no luck, they are not received, and the target can receive sms longer than 160chars, for sure
I am SURE that there was a bug with restoring contacts with some sense/manila bug, I've read about it right here, on XDA
Sorry for the double post, but I've foud out that it's an issue with stored contacts;
I've tried to send an sms to myself, and I received it with no problems...
I too am facing the this issue (HTC HD2 TMOUS) with sending sms more than 160 characters. this is not related to stored contacts in my case.
I did a hard reset and tried to send a sms more than 160 characters still facing same issue. I tried with 3 different Network Operators, still the same persists. However I have no problem with sending sms lesser than 160 characters. Anyone found a fix for this ?
P.S.: I know its a old thread, but... no fix yet.
This has happened twice now. The first time I thought it was a fluke, now a second time in two days I am getting concerned. I am using Google Messenger for SMS/MMS. The problem is that somebody sends me a text message and I reply to their message. My reply goes to a completely different person and the original sender never receives my reply. These are not group messages, just a single SMS.
Anybody else having this issue? I will have to switch back to my Nexus 6 if this keeps happening.
Known bug. Use Hangouts for SMS until it's fixed.
I got a text from amazon that my packaged was shipped at it showed coming from my brother. I too am using messenger. I don't like hangouts...
Yep same here, it's broken. I would say use Textra for a similar feel to messenger. Hangouts is broken too, but in a different way. It will send photos sideways if you use the paper clip in a message thread. If you use the share function in gallery it will send it fine.
I have been using Google Messenger since it came out on two other devices and have never experienced this issue until using it on the S6. I have found if I clear the app data for Messenger messages show up from the correct sender temporarily. WTF?
I came here to post something similar. I set up my dad's S6 the other day, and today he told me that if he goes into the Contacts app, selects a contact, and hits the text icon, it picks the wrong contact to send to. I tried this on numerous contacts, and it happens on all of them. If he adds them manually to a message through the Messenger app, this doesn't happen. Bizarre bug. Any ideas?
Happened again yesterday. A coworker sent me a text and it showed up from a completely different person. Guess I have to back to hangouts for now ugh...
Recurring Problem
I highly doubt the problem will be fixed soon. This bug has been blatant in all Samsung products I have had since 2007; however, it happens somewhat seldom and slightly random and the only idea I have for reproduction is:
Receive a message from person A
Read message from person A
Receive message from person B.
Open message from person B while still in the thread with person A's SMS.
reply to person B.
Watch as person A reads your reply to person B and person B never gets anything.
I'm not sure if this always reproduces it, but when I saw this happen AGAIN with my new S6 I was instantly reminded of my past with Samsung products - even prior to Android.
Same Issue--- Almost 2018 Now
I use a fully updated LG RIsio (low grade phone I know), and and the latest version of FB Messenger app for SMS. Several times in the past few months I have constructed a text for a recipient, with the intended recipients name on display as a write, hit send, and suddenly the completed text is sent to a seemingly random contact in my phone, and the deed is done.
This is insane. How do I stop this. I am gripped with the fear of something incriminating going to a family member or a coworker or manager. Why am I not hearing more about this in 2017? Most of the posts on it are from 2010. Did it never get fixed? Did it come back?
Please advise. This is the kind of oversight that can potentially ruin lives and merit a class action lawsuit.
I am working on a project that detects an event, and sends an alert text message to users. I'm trying to work out the latency between an event occurring and the arrival of the alert on a users phone. I was wondering if anyone knows if there is a way to get an arrival time for SMS messages that is down to the second?
Messaging apps show timestamps in the HH:MM format, but I am looking for HH:MM:SS timestamps or a Unix Epoch timestamp for the arrivals.
Does anyone have any idea on if this is possible, and if so where the more detailed timestamps could be found on the phone?
J-Blo said:
I am working on a project that detects an event, and sends an alert text message to users. I'm trying to work out the latency between an event occurring and the arrival of the alert on a users phone. I was wondering if anyone knows if there is a way to get an arrival time for SMS messages that is down to the second?
Messaging apps show timestamps in the HH:MM format, but I am looking for HH:MM:SS timestamps or a Unix Epoch timestamp for the arrivals.
Does anyone have any idea on if this is possible, and if so where the more detailed timestamps could be found on the phone?
Click to expand...
Click to collapse
Hi,
I can't answer the timestamp but I had an idea reading this and felt like sharing it with you. You could, instead of using the SMS arrival timestamp, include in the message the time HH:MM:SS. It would solve two problems :
1- Fining a suitable timestamp format
2- Solving the SMS latency problem (the SMS take some time to get to your phone when it's on, and when it's off you'll have to turn it on to get the message, and you'll get a wrong timestamp.
Hope this helped
Raiz said:
Hi,
I can't answer the timestamp but I had an idea reading this and felt like sharing it with you. You could, instead of using the SMS arrival timestamp, include in the message the time HH:MM:SS. It would solve two problems :
1- Fining a suitable timestamp format
2- Solving the SMS latency problem (the SMS take some time to get to your phone when it's on, and when it's off you'll have to turn it on to get the message, and you'll get a wrong timestamp.
Hope this helped
Click to expand...
Click to collapse
Hey,
Thanks for your response. I could add the time that the message was written in the message itself, but I want to include the sms message transmission time in my latency analysis.
The problem is that there is not much time between the event, and the warning that needs to be issued for the warning to be effective. We want to simulate multiple events to get an idea of how quickly a user could possibly get an alert. Latencies of 1-3 seconds would be a big deal so including the SMS transmission time in the latency analysis is important.