Motorola's fix doesn't work in version .08P either.
Ah well. I just left it on auto-update and changed the timezone it thinks it's in.
Maybe there's another firmware that provides for the change?
I am running H2.06P version and trying to set daylight savings time on my phone. I found a page on Motorola's site that described a setup feature allowing you to manually change when dst starts/ends but I don't see it in my version. I guess its not for the H2 versions. Anyone have the correct way of doing this. I guess posting dst changes for any version would be useful to other readers. But it would be nice to know if there is a way of doing this for my version.
To get around it, I disabled setting Automatic Network Time and changed it manually. Guess I get to measure drift for now.
BTW - the Motorola page I found is here:
http://direct.motorola.com/hellomoto...SavingTime.asp
PuppyKhan
http://ww.NYCMongol.com
Motorola's fix doesn't work in version .08P either.
Ah well. I just left it on auto-update and changed the timezone it thinks it's in.
Maybe there's another firmware that provides for the change?
I believe its a carrier thing.. They should have a fix within the next two weeks... Thats what i have heard at least from cingular.
~Alpha~
-Alpha The Legend-
Hmmmph . . . so DST starts three weeks early, they say two weeks to fix it. . . sounds to me like they don't want to fix it, so are just waiting fur the regular DST settings to catch up so they can claim to have fixed it.Originally Posted by Alpha43
I called T-Mo about it and first they said it was my phone, not their network. I called back and a different rep (with a major attitude) said it was because they hadn't finished updating their "system." So I asked "You mean this is a network-wide problem?" She got very agitated and said "I didn't say it was our network."
She was tripping over herself left and right trying to deny that she had just said that T-Mo was having problems with the update.
I'm an IT manager, and I managed to upgrade hundreds of PC's and servers with ZERO issues, I wonder why they can't manage to do the same.
My phone updated itself I'm running oent 2.2.6 24P
I don't think our A1200 not update to correct DST time has anything to do with service provider...
All the other phone that I own, either unbranded or branded phone, with both T-Mobile and Cingular, has updated itself during the weekend.
A1200 has pre-build in DST information for all timezone and cities, if you manually change your A1200 to let's say April 12, 2007. The DST symbol will appear in world clock and correct DST time will show..
I think the reason that 24P can display proper time is because motorola modified the DST information on that firmware while other firmware like 08P, still have the old pre-2007 DST information stored...
Yes, it's nothing to do with network carrier. The DST handling is built in the phone's firmware.
You can see in the readonly directory of:
# ls /usr/SYSqtapp/worldclock
ezx_dst.cfg ezx_zone.cfg worldclock
#
Interesting. I'm going to see if I can figure out a way to modify those to use the updated DST settings.Originally Posted by bulica
Maybe if I modify the .lin files I already have to update the .cfg files for realplayer (i.e. change the referenced folders and filenames, etc.). I'm a novice at linux, but I'll see what I can figure out. If I can make it work, I'll post the lin files later.
Edit:
This may be more difficult than I thought. I'm trying to decipher what the cfg files mean, for instance, this is a sample of the ezx_dst.cfg file content:
Asuncion,0.0.0.7.3.10,0.0.0.7.2.3,1
Athens,0.0.3.7.5.3,0.0.4.7.5.10,1
Atlanta,0.0.2.7.1.4,0.0.2.7.5.10,1
Auckland,0.0.2.7.1.10,0.0.2.7.3.3,1
Azores,0.0.0.7.5.3,0.0.1.7.5.10,1
Baghdad,0.0.3.7.1.4,0.0.4.7.1.10,1
Baku,0.0.1.7.5.3,0.0.1.7.5.10,1
Bangalore
Bangkok
Barbados
Beijing
Belgrade,0.0.2.7.5.3,0.0.3.7.5.10,1
Berlin,0.0.1.7.5.3,0.0.2.7.5.10,1
Bogota
Bombay
Boston,0.0.2.7.1.4,0.0.2.7.5.10,1
Brasilia,0.0.0.7.3.10,0.0.0.7.3.2,1
Bratislava,0.0.2.7.5.3,0.0.3.7.5.10,1
I have NO idea what the numbers represent, so don't know what to change. I thought that the ezx_dst file would contain DST info, but I'm not really sure what this info means.
if I had to guess this woul dbe my guess
Bratislava,0.0.2.7.5.3,0.0.3.7.5.10,1
Bratislava, <- place followed by a comma
0.0.2.7.5.3, <- this is the daylight start
0.0.3.7.5.10, <- this is the daylight end
1 <- amount to adjust by
now the break down of the start and end
a.b.c.d.e.f
a <- ?
b <- ?
c <- week of the month 2 = second, 3 = third
d <- week day to start and end on 7 = Sunday (guessing)
e <- Guessing this is the time of that day to adjust on
f <- month to start and end on 3 = March, 10 = October
so 0.0.2.7.5.3 would = second sunday of March at 5am
and 0.0.3.7.5.10 would = third sunday of October at 5am
But this is just my guess, but it's a start at least. Hope it helps a little.
--TS
That makes complete sense to me, I'm just hoping that I don't foul things up too badly.
I guess I can try it and see what happens.
I'm not sure your breakdown is correct though, as previously (I'm just quoting another website with start/end dates of DST):
"In 1986, a law was passed that shifted the starting date of daylight time to the first Sunday in April, beginning in 1987. The ending date of daylight time was not subject to such changes, and remained the last Sunday in October. The Energy Policy Act of 2005 changed both the starting and ending dates. Beginning in 2007, daylight time starts on the second Sunday in March and ends on the first Sunday in November."
So, your breakdown puts the change in the wrong week.
Let's look at Boston for instance
0.0.2.7.1.4,0.0.2.7.5.10,1
Would be the 2nd Sunday in April at 1:00 AM using your breakdown.
edit again: I had another breakdown I thought might be it, but it doesn't work out).
edit yet again: I think it goes like this:
0 - ?
0 - ?
2 - Time of day
7 - Day of week
1 - Week of month (i.e. 1st Sunday in X) (use a 5 to represent the LAST ocurrence of a day in the month
4 - Month
So, in the Boston example:
0.0.2.7.1.4 is 2:00 AM on the Second Sunday in April
0.0.2.7.5.10 is 2:00 AM on the last Sunday in October.
The final ,1 would be the difference in time between those two times.
I'm almost positive that's it, and it fits with the info found at http://support.microsoft.com/kb/914387 which states that the start time is 2:00 am in the US:
"Beginning in the spring of 2007, the start dates and end dates for daylight saving time (DST) will change to comply with the Energy Policy Act of 2005. DST dates for 2007 in the United States and Canada will start three weeks earlier (2:00 A.M. on the second Sunday in March), and will end one week later (2:00 A.M. on the first Sunday in November)."