txt message time problem

[MrJoseSanchez8330]

I'm having a problem with my sent and received times for my txts. I'm currently 2 hrs ahead of my hometown where I get most of my txts from and when I go to check them they are so out of order that I spend most of my time looking back to see what time the txt got in to read it. Can anyone help me solve this problem?

 

[highwayman1224]

This is happening to me too, & it sucks big time!!!!! It was happening before the update, so the update isn't what did it. This is what i was hoping the update WOULD fix. Still love my hero though.

 

[MrJoseSanchez8330]

Well I thought the update would fix it too. That's what I meant by me updating. It didn't fix it. I hope there is a solution. Sometimes it will put it in order but other times it doesn't.

 

[highwayman1224]

Yep, seems like the first couple of texts I receive are in order, then the trouble begins.

 

[VinnyD]

Hmm, weird, my text are in order in which they're received

 

[MrJoseSanchez8330]

But its only when there is a time difference between the people.

 

[VinnyD]

when you're going between time zones? Or people from other time zones? Because mine shows the stamp of where I'm at. And I travel between MSP and Vegas pretty often... maybe I'll take a closer look when I return back home to Vegas after Turkey Day

 

[highwayman1224]

The people i text are in the same city as i am, & their texts always show an hour behind mine.

 

[VinnyD]

It probably has to do with the automatic time setting, where you're phone is probably set to the Arizona Time Zone (AZ doesn't adjust for Daylight Savings Time), and theirs might be set to the PST, therefore capturing the wrong time stamp.

 

[MrJoseSanchez8330]

Well thats kinda like mine. I'm in the virgin islands and home is Chicago so they are currently 2 hrs behind me because the6 don't have daylight savings down here.

 

[jordanreichmann]

I would download Handcent SMS. I was having this same problem, and when I switched to Handcent, it fixed the problem.

 

[wolf1989#AC]

I had this problem and had to call Sprint. They opened a ticket and fixed the problem for me.