Text message timestamps and daylight savings

Forums › 2degrees (including Slingshot, Orcon, Flip, Stuff Fibre, MyRepublic, 2talk and Vocus) › Text message timestamps and daylight savings

aw

296 posts

Ultimate Geek
+1 received by user: 30

#90605 25-Sep-2011 10:37

Is it me, or have the 2d SMS servers jumped forward TWO hours instead of one for DST?

It's 10:30 and texts I receive are timestamped 11:30.

johnr

19282 posts

Uber Geek
+1 received by user: 2526
Inactive user

#525516 25-Sep-2011 10:40

Have you checked the time zone on your handset time and date settings?

vita

68 posts

Master Geek

#525522 25-Sep-2011 11:19

As John said, check the time zone - handset timzone settings and DST settings issues comeup twice a year.... it's always the handset causing it

1080p

1332 posts

Uber Geek
+1 received by user: 152
Inactive user

#525566 25-Sep-2011 16:29

I have two devices; both are displaying the date and time correctly and have been hard rebooted. They both show messages received as an hour later than messages sent. What should I check settins-wise?

froob

698 posts

Ultimate Geek
+1 received by user: 233

Lifetime subscriber

#525583 25-Sep-2011 17:25

I've noticed this on an iPhone and a HTC running Android, on 2degrees and Vodafone respectively. Both are displaying the time correctly. I'm thinking not a problem with the phones' time settings?

Edit: Actually the phones showing the incorrect times are older models- could just be that their software is a bit out of date.

Guide: Installing Network Cabling in New Zealand Homes

johnr

19282 posts

Uber Geek
+1 received by user: 2526
Inactive user

#525584 25-Sep-2011 17:27

1080p: I have two devices; both are displaying the date and time correctly and have been hard rebooted. They both show messages received as an hour later than messages sent. What should I check settins-wise?

Make sure they have the latest firmware / software

Zeon

3926 posts

Uber Geek
+1 received by user: 759

Trusted

#525606 25-Sep-2011 18:52

Havign the same problem here on 2degrees /HTC desire.

Speedtest 2019-10-14

Mighty Ape

Shop now at Mighty Ape (affiliate link).

vita

68 posts

Master Geek

#525652 25-Sep-2011 22:03

try turning off auto network update of time and date and ensure that" NZ daylight saving" is the selected time zone. (GMT+13 at the moment).
Then turn back on the network auto update

profrink

257 posts

Ultimate Geek
+1 received by user: 52

#525734 26-Sep-2011 12:16

Having the same issue here with a HTC Sensation. SMS time stamps being a hour ahead.

All my time settings are correct and phone auto-updated to show the correct time. Tried all the suggestions here but no luck.

Thought it may have been my Go SMS Pro app fudging things up, however I have checked the native android sms app and the time stamps are incorrect in that also.

Update:

Just asked around a few people with varying levels of phones (basic candy bar Nokia's to high end smartphones) and they currently have the same issue with the timestamps.

lokhor

2858 posts

Uber Geek
+1 received by user: 171

Trusted

#525783 26-Sep-2011 13:21

I think it must be a 2Degrees thing, it's affecting me an my Fiance's HTC ensations and my mum's SGS is also being affected. It is very annoying.

All comments are my own opinion, and not that of my employer unless explicitly stated.

snowwilliam

6 posts

Wannabe Geek

#525814 26-Sep-2011 14:21

Having this issure on iPhone 4 on 2 Degrees. Friend on iPhone 3gs on 2 degrees is fine. Any ideas?

2degreesCare

1537 posts

Uber Geek
+1 received by user: 274

Trusted

2degrees

#525906 26-Sep-2011 17:15

Hi all,

Just heard back from our technical team, and we'll be deploying a patch tonight to rectify this. Sorry about the confusion!

^MD

Lenovo

Shop now for Lenovo laptops and other devices (affiliate link).

aw

296 posts

Ultimate Geek
+1 received by user: 30

#528728 3-Oct-2011 21:15

2DegreesCare: Hi all,

Just heard back from our technical team, and we'll be deploying a patch tonight to rectify this. Sorry about the confusion!

^MD

I wasn't confused, not at first, I knew it was a carrier issue until someone else said above "it's always the handsets"... :P