Thread: Time Problem
View Single Post
  #1 (permalink)  
Old 06-01-2010, 07:22 AM
marvdmartian's Avatar
marvdmartian
N00b
Offline
 
Join Date: Apr 2010
Posts: 31
Reputation: 0
marvdmartian is a n00b
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Smile Time Problem

hey guys.. i have a sprint touch pro 2, and i installed energy rom this morning.

i have this problem that wasnt present before i flashed energyrom. my previous rom was the stock sprint WM6.5 with sense 2.5.


the clock is wrong because the time zone keeps changing to GMT when i live where it's supposed to be GMT +8

here's what i noticed:

1. for example, the exact time here is 8:30am (GMT+, the phone always changes the time zone to GMT and using my local time, but the minutes are slightly off. (8:19am GMT+0) So when i change the time zone to +8, it becomes (4:19pm)

2. everytime i sync with my computer, the time corrects itself, and all i need to do on the phone is to change it to the correct time zone, and it's all fine.

3. the time becomes incorrect everytime i restart the phone, or turn flight mode off and back on.

4. when i remove the sim card and turn on the phone without the sim card, the time remains correct!

5. i concluded that it has something to do with the network. i went to settings->phone, and theres something there about time synchronization. unfortunately, i dont know why, but when i disable it on my energy rom, the time still updates.

6. i tried using the same sim card on another windows mobile device. i turned on time sync on that device, and when i restarted the device, the time became incorrect also! but on this phone, when i turn off time sync, it obliges, and the time no longer syncs to the network, unlike my touch pro 2.

7. the culprit here is the network. the phone syncs with the network's time, which is minutes early, and the time zone is set incorrectly.

why doesnt my touch pro 2 obey when i tell it not to sync time with the network?

i cant text because the time is messed up and the message gets lost in the recepient's mailbox.

i hope this gets resolved soon. i've been searching for a definite fix but i found none.

Thanks
Reply With Quote