[jakspro]

I upgraded to 3.0GM on my 2G iphone running on the T-mobile network and I suddenly have timestamp errors on my text messages.

To elaborate, text messages coming from T-mobile users display the correct time, however, messages from non-Tmobile networks display about 5 hours off. To complicate matters worse, I had two friends each send me a text message at the same time, both came in at the same time (immediately), yet there was a 6 min differential between the messages (on top of the 5 hour lag).

Anyone else experience this phenomenon?

[jmano0o]

Hey, i am having the EXACT same problem and its extremely annoying, it only started happening this past week and its very confusing... anyone know any fixes for this?

and did you calll tmobile to ask?

[BoneCrif]

I've been having timestamp errors too, except I didn't update to 3.0.

[benjovi]

same problem here but i havnt seen it at all today

[Ticko]

i have had exact same error yesterday/today and no upgrade yet still on 2.21

[jmano0o]

anybody know how to fix this? its really annoying...

[ohsoferrety]

Seriously. I'm on EST, but all my texts are four hours behind. Anyone figure this out?

[jakspro]

Haha, Damn and I thought I was crazy for having this problem...

Well, I'm going to re-pwn the phone and see if this corrects any problems. I will say that I did NOT experience this on previous FW versions, only after the upgrade via iTunes.

[97vrsix]

Hey all, Nope it does not have to do with 3.0, or 2.2, or 2.2.1... Nope, It's a T-Mobile problem, and other networks.. Call and start the ********, I will be!! Right after 3.0 get's installed!

Same time frame.. About a week.. Please, Start to put your location..

New England, Western Mass... Area code 413... T-mobile.. FW:2.2 2G 8Gig Iphone. BlackBerry Plan..

[ohsoferrety]

New England, Central Mass, Area code 508, T-Mobile, FW: 2.2.1 AND 3.0 $5.99 plan

[jakspro]

Damn. Well, I just re-pwned the phone. No luck. And now I'm restoring the phone... But if you're right, that it is a T-mobile problem, it still won't work. Bummer. Let me know if you're able to get T-Mobile to fix this.

Texas; Area code 832; FW 3.0

[blkcadi]

Don't really believe it's a T-Mo problem. More like a computability problem with the pwnage perhaps. Not 100% sure, but I have been reading this quite a bit on the forum.
Many users are have reported this problem.

[BoneCrif]

Updated to 3.0, still having this problem.
Screen shot:

[crazystraws]

this is most definitely a t-mobile issue. first off, let's be real here. this is a widespread issue, that started beginning only a week ago, regardless of OS. yes, it is coincidental that 3.0 came out a week ago THEN this issue started happening, but lets not assume its an individual phone thing that can be cured by swapping firmware versions or the like. second, it was only two months ago that t-mobile made some changes to their infrastructure, causing issues with their voicemail systems and the way they were notifying non-branded phones (iphones included). perhaps t-mobile wasn't finished with their network upgrades, and this is another problem that will be fixed shortly? third, i can confirm this is happening across a variety of phones, branded or not. yes, my iphone's sms timestamps are acting up, but so is my brother's samsung gravity's timestamps, my dad's motorola razr's and my old (semi-working) t-mobile dash. additionally, a quick google search brings up scores of other people with this problem, mostly on branded phones.

therefore, it is only logical to think this issue lies with t-mobile themselves, and not with any of our phones. you all can stop the mad upgrading and downgrading

[blkcadi]

well, that's good info, but my question would be, why isn't effecting everyone. I know of a ton of people that are not having the problem. Perhaps go to T-MO live support chat and see if T-Mo is aware.