Develop Bugs

FIXED: Evo 4G SMS Timestamp Issue

UPDATE: I've found a fix for this issue - AWESOME!
Just go to the Android Market and install the SMS Time Fix app by Matt Precious.
http://www.androlib.com/android.application.com-mattprecious-smsfix-pAFq.aspx
It works perfectly, and updates the time stamp on all messages to relfect PHONE time and not network time. HINT: Make sure the "Last Resort" option is checked in the settings and offset is set to zero. This little app now makes the Evo Messages app usable. Finally...
Hope this is helpful info
So, I've been reading and experiencing several issues with SMS timestamps on the Evo 4G.
It seems there are three distinct issues with SMS timestamps on the the Evo and I believe they all have the same root cause.
Issue 1: When roaming texts are received with the wrong time stamp, offset by several hours (typically 4 or 5 hours off). This causes them to not be threaded in the conversation correctly. Very annoying.
Issue 2: When receiving SMS messages on any network (Sprint or roaming), the time stamp is off by an hour. The result is the same as Issue 1, but a less extreme example.
Issue 3: When texting back and forth in quick succession, SMS messages are not logged in the order in which they are received, and received text messages ALWAYS appear before sent text messages if they are sent during the same minute, regardless of which one was actually sent first. This is also very annoying.
I believe the root cause is that the native Sense UI messaging app is using the timestamp of the tower of each SMS rather than using the time stored on the phone. To prove this, if you use Handcent and set it to use "phone time" and ignore the tower time, it works perfectly. The thing is that I don't want to use Handcent and I want to use the native app. Is there a setting that can be tweaked to fix this? Has anyone talked to HTC or Sprint about the issue and is a fix in the works?
For such a major problem, I am surprised more people haven't come forward. It's a pretty significant bug...
Thanks,
Matt_TX.
Click to expand...
Click to collapse

Trying updating your Profile and PRL.
if that doesn't fix it, dial #2

I also have noticed issue #1. I even called Sprint to ask about it and they referred me to a 3rd party app in the marketplace to fix the timestamp.
I have been using Handcent ever since to get around the issue.

Updated First Post...

trying updating your Profile and PRL.

agix said:
I also have noticed issue #1. I even called Sprint to ask about it and they referred me to a 3rd party app in the marketplace to fix the timestamp.
I have been using Handcent ever since to get around the issue.
Click to expand...
Click to collapse
Its the tower issue mentioned at the top of this topic. Updating your PRL, (Preferred Roaming Location), is usually helpful when you are traveling and lose signal, this will help catch another carriers tower or at least one a bit closer, also, updating your Profile, (Data profile), only will refresh from your device the settings matching your NAI (ID address) with your carrier and refresh your data settings...ie > HCM/SPS>OMA, these tactics are unnecessary, and you can do both with a quick power cycle. The best thing for timestamp correction is to use your phone time as the stamps source & to make sure only to use for future time dated messages. As for dialing *2 or #2 as in this thread, it will get you no where with the issue, they will only refresh your device in their system, in this case meaning Sprint, you can do the same, unless, of course you are running specific roms which clear Carrier IQ, you may then run in to some trouble with those device self updaters, but as mentioned earlier a power cycle will do the same all at once.
The Time Stamp Fix, from the Market works just fine

Does this fix work for when you have your phone off or in Airplane mode? I hate getting my text messages when I turn my phone back on are they are all timestamped to when I turned my phone back on not to when they were actually sent.

thank god i saw this, i have a vzw prl and my timestamp is always 4 hours in the future. works great.
Oddly my sms timestamp is fine on aosp roms, just on sense it is off...

[Q] Cyanogen CM6 SMS only converting to MMS after 3x160 characters, not splitting

Hello,
Running Cyanogen CM6 RC1 here. I've been having trouble sending long text messages, which I initially diagnosed as a problem sending MMS.Specifically whenever I tried to send a long text message (longer than 160 chars) it would just hang and say "sending" for like 5 minutes before I get a failure report. Curiously, I had no trouble sending or receiving messages with multimedia content, like images.
After some additional tinkering and web searching, I discovered that MMS was working fine. Rather, my phone is trying to send text messages between 161 and 480 characters as SMS without breaking them apart into the appropriate number of parcels. Above 460, or 3x160, the phone is converting them to MMS and it goes through just fine.
Is there a way to change the threshold before which SMS are converted to MMS? I think all the EVO owners are pretty much on the same plan which gives us unlimited media messaging, therefore there is no point in not sending any SMS over 160 chars as an MMS. Is there a way we could change the threshold to 1? I imagine this is what HTC did in their messenger that was installed with Sense.
*Temporary solution:* If anyone else out there is having this problem, but doesn't have a solution, I have a temporary one. Simply download and use the free Handcent SMS application, and in the settings (settings>send message settings>Split 160) change the value from "Don't split" to "Simple Split". This will automatically break up messages between 161-460 into 2-3 parcels of 160 chars or less.

Handcent i think has those setting parameters.
also, this is a known issue already, and has already been greatly discussed.

infamousjax said:
Handcent i think has those setting parameters.
also, this is a known issue already, and has already been greatly discussed.
Click to expand...
Click to collapse
Sorry, I was typing an edit as you made the mention about handcent. However, I haven't found the setting that allows you to change the threshold--only to make the message split. Also, it will allow to turn off conversion altogether. Am I not seeing it?
Also, perhaps I'm not so savvy here, but I've been unable to find any solutions on forums or anywhere. If this issue is already very well discussed, any chance you provide me with a link please?

I have this same problem which is VERY annoying! Like you said I have not seen it discussed before either!

It's not a CM6 issue.
It's an Android issue.
https://code.google.com/p/android/issues/detail?id=2318
[/thread]

drmacinyasha said:
It's not a CM6 issue.
It's an Android issue.
https://code.google.com/p/android/issues/detail?id=2318
[/thread]
Click to expand...
Click to collapse
So it would appear then that there is no solution to this?

yeah, there is a solution. use handcent. chomp probably does it too.
btw, you may want to post your questions in the 'questions' section

timothydonohue said:
yeah, there is a solution. use handcent. chomp probably does it too.
btw, you may want to post your questions in the 'questions' section
Click to expand...
Click to collapse
Ah, next time I'll use the questions section. Regarding Handcent, does this actually allow me set the threshold, or just break up longer messages into multiple SMS--I mean, does Handcent present another solution other than the one I specified in my initial post?

AFAIK, SMS length is an agreed upon standard that probably in the near future won't be changed. longer messages will be broken up into transmissable lengths of 160 chars, until a message is long enough that it is actually simpler on the network to send the whole thing as a single MMS loaf.

FIXED: SMS Timestamp Issue in HTC Sense Froyo

UPDATE: I've found a fix for this issue - AWESOME!
Just go to the Android Market and install the SMS Time Fix app by Matt Precious.
http://www.androlib.com/android.application.com-mattprecious-smsfix-pAFq.aspx
It works perfectly, and updates the time stamp on all messages to relfect PHONE time and not network time. HINT: Make sure the "Last Resort" option is checked in the settings and offset is set to zero. This little app now makes the Evo Messages app usable. Finally...
Hope this is helpful info
Does anyone know if this issue has been fixed in the HTC Sense Froyo Update?
Matt_TX said:
So, I've been reading and experiencing several issues with SMS timestamps on the Evo 4G.
It seems there are three distinct issues with SMS timestamps on the the Evo and I believe they all have the same root cause.
Issue 1: When roaming texts are received with the wrong time stamp, offset by several hours (typically 4 or 5 hours off). This causes them to not be threaded in the conversation correctly. Very annoying.
Issue 2: When receiving SMS messages on any network (Sprint or Roaming), the time stamp is off by an hour. The result is the same as Issue 1, but a less extreme example.
Issue 3: When texting back and forth in quick succession, SMS messages are not logged in the order in which they are received, and received text messages ALWAYS appear before sent text messages if they are sent during the same minute, regardless of which one was actually sent first. This is also very annoying.
I believe the root cause is that the native Sense UI messaging app is using the timestamp of the tower of each SMS rather than using the time stored on the phone. To prove this, if you use Handcent and set it to use "phone time" and ignore the tower time, it works perfectly. The thing is that I don't want to use Handcent and I want to use the native app. Is there a setting that can be tweaked to fix this? Has anyone talked to HTC or Sprint about the issue and is a fix in the works?
For such a major problem, I am surprised more people haven't come forward. It's a pretty significant bug...
Click to expand...
Click to collapse
Click to expand...
Click to collapse

no it has not, ive been having problems with this, ALOT.

Updated First Post...

Disappearing text messages

I've noticed an issue on my Galaxy Nexus (Stock Rooted 4.0.4, VZW) where randomly a text message will disappear.
I don't have any idea what is causing it and its so sporadic, it happens maybe once every 1,000 texts.
The only way I know I'm even missing a text is if I see it appear in the notification bar but not be there when I go into the messaging app (Using stock messaging) or, because I have mightytext installed, I'll see the message forwarded to my browser but I'll notice its gone from my phone.
I was able to pull a logcat after it happened most recently, so if someone thinks they would be able to decipher some information from it, let me know.
I'm posting because I'm wondering if I'm the only one seeing this issue or if others are in the same boat.
Thanks in advance and let me know if anyone would like some more info...I've been trying to nail this thing down for months now.

You're welcome to put it up on pastebin or something and post it, but I would first eliminate MightyText as the first possible problem. Uninstall it and see if it still happens.

I had the same problem when still on 4.0.2 stock, unrooted. Only ever used the stock messaging app. It happened very sporadic, with the same symptoms you described.
Messages popped up in notification bar but could be nowhere to be found in messages app.
Since upgrading to 4.0.4 it never happened again, or at least I didn't notice.
As you are on 4.0.4 already, that's probably not comforting.
Sent from my Galaxy Nexus using Tapatalk 2

Yeah, it happens so infrequently that I'm not surprised you haven't noticed it since updating, but nice to know someone else has the same issue.
Do you have mighytext installed or can we rule that out as a culprit?

Do you have any SMS Backup applications installed?
If not, I recommend the "SMS Backup +" by Jan Berkel.
Works amazing on my ICS.
Does backups of SMS, MMS and Call Logs (if you want.)

Yes, I do have that installed, but thats not really relevant to the issue I described here.
Thanks.

gbenj said:
Yes, I do have that installed, but thats not really relevant to the issue I described here.
Thanks.
Click to expand...
Click to collapse
Sorry - I realized I never finished my train of thought. Got "distracted" as someone walked into my office.
To continue, when your texts disappear from your phone, do they also disappear from your Gmail SMS label?
As per every 1000 texts - I assume you get a TON of texts per day?
I ask - because my cousin who is a promoter also gets/sends 1000's of text messages a week, and he made a funny comment yesterday about how some of his incoming texts "vanished."
He doesn't have SMS Backup+, so I couldn't verify it for him at the time. I'm wondering if you and him have the same problems?
Regards,
var

I also have SMS Backup + installed, but not Mighty text. When a disappearing text arrived, it never even had a time to kick in, even though I'm on wifi and it's said to backup upon arrival. The text is just gone, right after the notification vanishes.
But hard to investigate as it happens really very sporadic... And yup, I get hundreds of messages each day in a developing country, where sometimes also sms are not delivered, so everybody knows and it's not that big of a problem.
Sent from my Galaxy Nexus using Tapatalk 2

Major SMS Issues - Advanced Messaging?

Hi I am hoping someone might have some ideas of how to address my problem.
I am on a stock S9 on AT&T. I have had it for about 9 months...but about a month ago I started having a very problematic issue where I occasionally just dont receive a text message from someone. Its not always from the same person, and its sometimes in group texts but sometimes not. Its sporadic but often enough that its very problematic because I sometimes miss important messages without realizing.
I have been using Textra. At first I thought perhaps the problem is with Textra. But I logged in to MyAT&T portal and you can see there a log of all texts you have sent and received - the missing texts are never even showing as having been sent to me from the user.
I havent had much success figuring out what the issue is although after researching, I have noticed that some people think the culprit may be AT&T's "Advanced Messaging" function and they advise disabling it.
So I am now doing that to see if it works. The problem there though is it can only be disabled from within the stock Samsung Messages app, which I dont want to use. And if I go into that app to disable, and then switch to another Messaging app after, then every time I reboot, Advanced Messaging is on again.
If anyone has further advice on 1) understanding what the issue may be and 2) how I can permanently disable Advanced Messaging - I am desperate to receive it! Thank you.

lirong said:
Hi I am hoping someone might have some ideas of how to address my problem.
I am on a stock S9 on AT&T. I have had it for about 9 months...but about a month ago I started having a very problematic issue where I occasionally just dont receive a text message from someone. Its not always from the same person, and its sometimes in group texts but sometimes not. Its sporadic but often enough that its very problematic because I sometimes miss important messages without realizing.
I have been using Textra. At first I thought perhaps the problem is with Textra. But I logged in to MyAT&T portal and you can see there a log of all texts you have sent and received - the missing texts are never even showing as having been sent to me from the user.
I havent had much success figuring out what the issue is although after researching, I have noticed that some people think the culprit may be AT&T's "Advanced Messaging" function and they advise disabling it.
So I am now doing that to see if it works. The problem there though is it can only be disabled from within the stock Samsung Messages app, which I dont want to use. And if I go into that app to disable, and then switch to another Messaging app after, then every time I reboot, Advanced Messaging is on again.
If anyone has further advice on 1) understanding what the issue may be and 2) how I can permanently disable Advanced Messaging - I am desperate to receive it! Thank you.
Click to expand...
Click to collapse
You might have to adb push and remove advanced messaging from your system partition
([emoji813]9/[emoji725]/9[emoji813])