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.
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?
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 ?
I use my device for work. I coordinate/schedule jobs in which there are many people who can work certain slots. So, I'll send out one text message to about 75-84 individuals. Then the ones who can work reply. Later, I send out another mass SMS advising of remaining slots to be filled.
My issue is this. In the Android code a section checks for the number of text messages send within the last hour. If you exceed 100 messages - then, Android throws an error for every message afterwards within that hour and the user has to select "OK" to send an SMS. So, at times I have to sit there and select "OK" over and over again for several minutes while the over limit SMS's are sent....
I found an old record on how to fix this issue here.
However, this APPEARS to be an old solution. I was unable to find this setting or the table "gservices" in "/data/data/com.android.providers.settings/databases/settings.db
Does anyone know where this was moved or how to change this setting?
My device is a an LTE Galaxy Nexus.
I'm running AOKP-build 33. But, I would think this setting would be generic to all of the current ICS ROMs.
Thanks for any advice.
BTW - I found some very old posts related to this same issue. Note:
1) Using an app will not address this issue (I use Chomp SMS) as this is coded within Android.
2) Google Voice will not work as it doesn't recognize "groups" for the "to" box.
3) Pulling the battery will just prevent all the texts from going out.
I'm just hoping someone knows where the file/code is located that I need to modify.
All other suggestions will not resolve this issue.
Hello,
I am looking to send a rather long text message of about 3,300 characters to a person who I can only reliably reach via text message at this time. I realize that SMS stands for Short Message Service, and 3,300 characters is by no means short, but please understand that if there was a better way to send this message to this person, I would choose that method instead. I have the Samsung Galaxy Nexus on T-Mobile, and the standard Messaging application allows me to type up to 2,000 characters for an SMS message. So, my first thought was to just break the message up into two segments of about 1,650 characters each and send them as two separate messages consecutively. This would be fine, however I realized something else. Messages over about 160 characters are broken up into multiple messages on some carriers, meaning that even if I broke my message up into two large segments of 1,650 characters each, it may still be broken up further into multiple smaller segments when sent to the recipient. As you could imagine, I would rather not have the recipient be inundated with 20 or so separate text messages at once, unless they would only receive one notification instead of 20 separate ones.
To give some background, my intended recipient has an iPhone, though I don't know what carrier they use (if that matters in how messages get broken up). One other possibility was to send two MMS messages of 1,650 characters each instead, but would that be split up into multiple 160-character fragments, as well? Also, even if MMS messages do not get split up like this, would my recipient be able to receive such a large MMS message (containing just text)?
Please feel free to suggest any solutions to this problem or any alternatives. I would e-mail this person, instead, but I have no idea how frequently they check their e-mails and I feel as though sending this over text message is the best way to quickly communicate this to them and ensure that they actually receive it. Thanks in advance for any help!
TomCatullo said:
Hello,
I am looking to send a rather long text message of about 3,300 characters to a person who I can only reliably reach via text message at this time. I realize that SMS stands for Short Message Service, and 3,300 characters is by no means short, but please understand that if there was a better way to send this message to this person, I would choose that method instead. I have the Samsung Galaxy Nexus on T-Mobile, and the standard Messaging application allows me to type up to 2,000 characters for an SMS message. So, my first thought was to just break the message up into two segments of about 1,650 characters each and send them as two separate messages consecutively. This would be fine, however I realized something else. Messages over about 160 characters are broken up into multiple messages on some carriers, meaning that even if I broke my message up into two large segments of 1,650 characters each, it may still be broken up further into multiple smaller segments when sent to the recipient. As you could imagine, I would rather not have the recipient be inundated with 20 or so separate text messages at once, unless they would only receive one notification instead of 20 separate ones.
To give some background, my intended recipient has an iPhone, though I don't know what carrier they use (if that matters in how messages get broken up). One other possibility was to send two MMS messages of 1,650 characters each instead, but would that be split up into multiple 160-character fragments, as well? Also, even if MMS messages do not get split up like this, would my recipient be able to receive such a large MMS message (containing just text)?
Please feel free to suggest any solutions to this problem or any alternatives. I would e-mail this person, instead, but I have no idea how frequently they check their e-mails and I feel as though sending this over text message is the best way to quickly communicate this to them and ensure that they actually receive it. Thanks in advance for any help!
Click to expand...
Click to collapse
This may sound obvious but why not email the long message and then text them and tell them to check their email?
Otherwise a long message is usually converted to an mms if it is very long.
Dave
( http://www.google.com/producer/editions/CAownKXmAQ/bigfatuniverse )
Sent from my LG P920 using Tapatalk
mistermentality said:
This may sound obvious but why not email the long message and then text them and tell them to check their email?
Otherwise a long message is usually converted to an mms if it is very long.
Dave
Click to expand...
Click to collapse
I'm thinking that this may just be my best option, although I'd prefer to send it directly to their phone. However, this is not a complete necessity.
I am curious, though, about MMS. Would just sending my message broken up into a few text-only MMS messages run into any potential problems? I don't know much about the iPhone and the reliability of sending and receiving MMS messages from Android to iPhone or from T-Mobile to another network, but is sending multiple MMS messages rather unreliable? I suppose I could always request a delivery report on each MMS message to see if they were received successfully, but I also wonder how reliable delivery reports are. What do you think about this? Thanks.
What are you composing from? Why not make a pdf and mms it? Or a jpg?
Hello,
I have a Nokia 3.1 phone running Android 8.1.0. My phone uses the default Google Messages app to send and receive text messages. The Messages app was working perfectly until recently. I was a recipient of a text message sent to about 6 people. When I replied to the message that was sent, all of the other recipients received a private text message containing my reply, as well as my reply being in the original mass text message. This has never happened before.* Can anyone tell me why this is happening and how I can fix the problem?
Thank you
Did it show up on your device as individual messages as well? It sounds like your group text option is set to send individual threads. I believe there are only two options with this, one that sends group texts and replies as one MMS and one that sends them out as individual threads. The latter keeps them from going out as MMS which for some counts against their data usage. If you haven't modified your settings or made any other data saving changes I'm not sure why this would have changed for you, unless the message originator changed something in their settings.
VidJunky said:
Did it show up on your device as individual messages as well? It sounds like your group text option is set to send individual threads. I believe there are only two options with this, one that sends group texts and replies as one MMS and one that sends them out as individual threads. The latter keeps them from going out as MMS which for some counts against their data usage. If you haven't modified your settings or made any other data saving changes I'm not sure why this would have changed for you, unless the message originator changed something in their settings.
Click to expand...
Click to collapse
VidJunky, thank you very much for your reply.
In the Group Messaging settings, there are 2 options:
1. Send an SMS reply to all recipients and get individual replies (mass text)
2. Send an MMS reply to all recipients (group MMS)
Option 1 was selected on my phone, but I have switched to option 2.
Still not quite sure how that happened (I have had this phone for quite a while and never had this problem), but thank you very much for your reply!
No problem. It may have happened during an update. Thank you for your kind words.