I solved a problem with my custom ROM (WanamLite) on Galaxy SII I9100.
When I sent a SMS and the recipients mobile was offline at that time, my SMS gets marked as 'sent unsuccessful' about 10 minutes later. These messages had to be resent manually and if the recipient was still offline, the game starts again. On top of the inconvenience most providers charge every single unsuccessful delivered SMS!
There is one setting in SMS apps 'request delivery report' or similar, but this means to receive a report if a SMS is received successfully or unsuccessful by the recipient.
The time how long the provider tries to to deliver a SMS is quite an other thing. As far as I know there is no possibility in Android or any SMS app to set this validity period.
As a former developer of a Fleet-Management-System I remembered that there are settings in the SMS message format for this. Also some old phones have options for it. As far as I recall, the time span can be set from some minutes up to 7 days.
Long story short, I flashed Siyah Kernel and - all problems magically dissolved ... SMS are delivered up to 7 days after sending ...
Related
Hello,
I seem to be having an issue with the time stamps on my text messages. The ones that I send are okay, however the ones that I receive all have different times on them. For example:
If I send a text at 8:15PM and receive a reply right away, it'll show my text sent at 8:15PM, but the reply will have a back dated time... Maybe 5PM, 4PM... something like that.
Any ideas why?
Thanks!
I find this but its by no means universal. some messages I recive are an hour ahead others are not. I recived two messages at almost the same time & one of them had the wrong time. I can't wait for the new update to fix all of these little issues
I've seen this problem since my G1. It's still suffering from it, as is my Magic and my Hero.
I'm still having the same issue.
My received text messages show a time of 4 hours behind.
So if I send a text at 6:30 and receive a reply at 6:32, it shows 2:32 as the received time.
Does anyone know if there's a fix for this? I have updated to the latest (leaked) firmware, but still no luck.
Thanks!
Are you all on the same network? Might not be the phone because i've never noticed this
kadison said:
Are you all on the same network? Might not be the phone because i've never noticed this
Click to expand...
Click to collapse
Was just going to ask this... What network are you on, have you set network location to automatic by carrier, if so, set it manually to the city / country you are in.
I'm on O2 and have been using the network provided values.
I've set it to manual and text someone at 12:44. The reply came in a little while after and was stamped 12:45 so no issue there it seems. Strange.
I'm now getting issues now with texts in fairly quick succession.
The time stamps can be the same i.e. 21:17 but a reply from someone will sometimes appear before my original text in thread view.
Also a reply came in to one of my texts with a time stamp before my original text. This was displayed "correctly" as before my text, but the fact its timestamped in this way can't be right.
Anyone else seen this?
It's like the phone is looking at minutes for accuracy, not seconds. Also taking the timestamp of when a text was sent from the other person's phone as the time received to my phone. Hm :/
I get this on Orange when I receive a message from the US. All my outgoing messages are listed at the bottom of the conversation, while the one received from the US are at the top.
UK based conversations are all threaded correctly.
Ok thanks.
It never used to be like this so I'm wondering after prolonged use the sms database gets a bit corrupted somehow?
For me it seems to behave like this: for outgoing (sent) messages I see the time that is set on Hero. For incoming messages, however, Hero shows the time on the network provider.
I assume there is some header in SMS message containing the time, and Hero uses that instead of using the time Hero has when the message arrives.
I started using the Network Provider time (automatic) to get rid of this.
Hi guys,
I've been having issues with sending text messages in the past few days, and it has come on since being at my parents. At first I thought it might have been a problem in the local area, but today I travelled out of the area and my texts aren't getting through still.
I have the delivery report turned on, and each time i send a message that is greater than 160 characters, it comes back saying "The message sent to <recipientname> is not reachable". I've done a bit of googling but I haven't found anything useful. I only really text my girlfriend and we quite often send messages that are 160 characters in length. \
Any ideas what a cause may be? I will be trying to contact the mobile operator (T-Mobile) but I want to be sure it isn't the phone being silly.
Much appreciated if you guys can help
could be a simple hangup between area antennas.
Have you done a soft reset ? If yes, simply run the com wizard again and it should work.
A soft reset has done the trick, thanks
I am having a similar issue except that any text message above 159 characters is not received by one particular person I send it to. I am using my HD2 on O2 contract and the person I am texting is using an LG 910 on Virgin Mobile PAYG. They can send me long text messages fine but they just can't receive them from me.
Also, other people using different phones on different networks can receive long text messages ok from me. Also the person I am texting can receive long text messages from other people.
If I send a long text message with the *0# sequence to request an SMS delivery notification I get a confirmation back saying it was delivered but the person I sent it to never receives the text.
I am wondering if this is some compatibility issue between the HD2 SMS messaging software and the LG 910 phone. Its all very annoying!
Also a soft reset doesn't make any difference either.
Many thanks,
Richard.
Hi guys
I'm using our good old Galaxy Spica with CyanoGen 6.3. My issue is that I need an accurate (to the minute) timestamp when an SMS was sent and delivered. So far I have tried Go SMS, Handcent SMS, Delivery Reports+ and few other apps - the first two show delivery report time equal to sending time even if the actual offset is like 5 minutes (tested by sending messages to my other phone while it was off) and the third app didn't even want to work.
So my question is: does anyone know either an app or hack that would allow me to get accurate delivery report times?
As you all now, we can't send sms to more than 20 people at a time. To solve that problem, I downloaded handcent app and I'm able to use group sms now. But, I had two really big problems with messaging.
1) I always receive this message asking me if I want to allow:
"Messaging is sending a large amount of SMS messages. Do you want to allow this app to continue sending messages?"
The thing is, I receive this notification for at least 5 times in a row, while I'm sending group messages and it's just unbearable.
2) I sometimes receive notification from handcent that my messages are not delivered and those times, it's almost 10 messages, making the phone unusable for me. I read that it's a problem with smsc settings, but I receive "This application does not work on this device." error when I want to go to Phone info. My service center address is correct, so I don't know if that is the problem.
I really want to solve this issues, so here is my question. If I install a custom rom, will it solve the "not being able to send to more than 20 people at a time" problem for me, therefore solving all my other problems? And if so, will any custom rom will do, or should I install something specific.
Sorry to keep it long, thanks in advance.
Initial Notes:
Using a rooted Verizon S5 with stock KitKat ROM (NK2), but this problem also persisted on a rooted Lollipop ROM (OA8).
This problem persists on the stock messaging app as well as all messaging apps I have downloaded from the Play Store so it seems to be an issue with the phone itself. I'm currently using Chomp.
------------------------------------------------------
Problem:
For the longest time, my MMS messages would come and go at what seemed to be the most random times, but I've finally come to notice that the only way I can get an MMS (including group texts) to send or receive is if I send more than 1 at a time.
For example, if I try to send my wife a single pic, it will hang indefinitely, literally for days sometimes. However, if I send another pic to ANYONE (including myself), the pic that was 'stuck' waiting to send to my wife will then finally send.
Also, if I long-press the stuck outgoing MMS, and choose 'resend' it will usually send, but then the recipient also gets 2 copies.
I've also noticed that when the stuck MMS finally does send, I frequently RECEIVE multiple pics or group messages from friends who sent them long ago. It's as if successfully sending an MMS from my phone has somehow unlocked a stuck setting somewhere in the network, which then allows all existing MMS to send/receive.
Also, I've noticed that if I attempt to send 3 pic messages, sometimes only 2 will actually go through. If I want to send the 3rd, I have to generate a 4th pic message also to any recipient. I've gotten to the point where I just decide in order to make MMS work, I have to do one of the following:
- Send 2 pics to the intended recipient
- Send 1 pic to recipient, and then forward that same message to myself.
- Send 1 pic to recipient, and then also forward it to someone else.
So I have come to learn that I do have a work-around of sorts, but it's incredibly inconvenient, and just flat-out weird to me. So it's obvious my MMS can work on this phone, but why do I have to send them in pairs?
Sent from my SM-G900V using XDA Free mobile app