1) Time/Date 11/01/2011 - 13:10:00
2) Response time
3) Product MC5574
4) OS Version WM61 BSP35
5) Clarify Case # 2486894 Time sensitive issue Attached is eMscript logs of issue Clock is being pushed back 2 hours during DST. TA is requesting sequence of events (on an OS level) of what occurs within WM61 when DST occurs With this information, TA feels the customer will be able to understand what is occuring on the device within their application.
8 Replies
I am forwarding all responses received to the TA as suggestions including the fix for SPR 17909 will keep ECRT informed if that resolves the issue
Hi, Even though it doesn't the exact same issue as in SPR 17909, I think you should try it's fix.
I think the should dump the notification database and time zones before and after the automated time change. I'm thinking somesetting may be a little off or a double event is somehow queued. In any case, please update this forum if this is resolved as DST is hitting soon here :)
Glenn, Is it the same issue as in SPR 17909?
Hi Yosi, Based on the description, it does not sound like the same issue. The spr specifies that when the clock hit 2am, the clock was set back to 1 am and the process looped. From the customer's description and the Resource.csv eMscript log, the clock is being reset back to midnight (12 am), not 1am as expected.
30/10/11 17:55:20
100
4143
-106
27
255
0
Auto
2
34
73826304
3.66E+08
25075712
26
20
MCKiosk.exe
UTC - CES UK [SOTI KIOSK WINDOWS CLASS]
1
1
NOT_FOUND
NOT_FOUND
574
984
0
0
1
GSM GPRS EDGE
13
55
Cell ID: 39391 ::Location Area Code: 835::Mobile Network Code: 30::
0
0
0
Not Found
N/A
0
########
6
3D
GPS
4.8
2.4
4.1
53.77651
-2.47593
182.9
1.53
10.17528
12
20::32::1::17::11::23::31::14::4::13::28::12
11::1::17::23::32::20::0::0::0::0::0::0
18::18::23::16::30::30::0::0::15::0::0::0
202
DC Power
30/10/11 17:55:36
100
4123
-227
27
255
0
Auto
3
34
73826304
3.66E+08
25071616
26
20
MCKiosk.exe
UTC - CES UK [SOTI KIOSK WINDOWS CLASS]
1
1
NOT_FOUND
NOT_FOUND
574
984
0
0
1
GSM GPRS EDGE
13
55
Cell ID: 39391 ::Location Area Code: 835::Mobile Network Code: 30::
0
0
0
Not Found
N/A
0
########
5
3D
GPS
8.8
3.6
8
53.77654
-2.47599
178.3
0.57
6.406688
12
20::32::1::17::11::23::31::14::4::13::28::12
11::1::17::23::32::0::0::0::0::0::0::0
18::17::22::20::30::31::0::0::0::18::0::0
101
Heartbeat
31/10/11 00:00:00
92
4098
-50
27
255
0
Auto
100
34
73560064
3.66E+08
25067520
26
24
MCKiosk.exe
UTC - CES UK [SOTI KIOSK WINDOWS CLASS]
0
1
NOT_FOUND
NOT_FOUND
574
984
0
0
1
GSM GPRS EDGE
0
100
Cell ID: 65063 ::Location Area Code: 502::Mobile Network Code: 30::
0
0
0
Not Found
N/A
0
No Fix
0
Unknown
Unknown
No Fix
No Fix
No Fix
No Fix
No Fix
No Fix
No Fix
No Fix
-1
No Fix
0::0::0::0::0::0::0::0::0::0::0::0
No Fix
102
System Time Changed
31/10/11 16:05:07
100
4071
145
22
255
0
Auto
10
34
73809920
3.66E+08
25055232
26
20
MCKiosk.exe
UTC - CES UK [SOTI KIOSK WINDOWS CLASS]
1
1
NOT_FOUND
NOT_FOUND
574
984
0
0
1
GSM GPRS EDGE
31
100
Cell ID: 65063 ::Location Area Code: 502::Mobile Network Code: 30::
0
0
0
Not Found
N/A
0
No Fix
0
Unknown
Unknown
No Fix
No Fix
No Fix
No Fix
No Fix
No Fix
No Fix
No Fix
-1
No Fix
0::0::0::0::0::0::0::0::0::0::0::0
No Fix
101
Heartbeat
31/10/11 16:05:09
100
4071
145
22
255
0
Auto
3
34
73809920
3.66E+08
25055232
26
20
MCKiosk.exe
UTC - CES UK [SOTI KIOSK WINDOWS CLASS]
1
1
NOT_FOUND
NOT_FOUND
574
984
0
0
1
GSM GPRS EDGE
31
100
Cell ID: 65063 ::Location Area Code: 502::Mobile Network Code: 30::
0
0
0
Not Found
N/A
0
No Fix
0
Unknown
Unknown
No Fix
No Fix
No Fix
No Fix
No Fix
No Fix
No Fix
No Fix
11
11::1::32::19::20::14::28::22::17::9::3::0
0::0::0::0::0::0::0::0::0::0::0::0
0::0::0::0::0::0::0::0::0::0::0::0
203
Power resumed. Reason RTC1: Suspended at 30/10/2011 17:56:17 Suspend Reason: Inactivity Timeout Time suspended emGetSuspendTime : 0 days 6:3:56
Might be possible that MS set the clock back one hour due to DST, and there clock sync app also set the clock back one hour for DST resulting in 2 hours total set back.
I don't think it will be possible to give step by step what Microsoft does. From our understanding, Microsoft will register for notification at a certain time. When that time hits, Microsoft will check if we are currently in DST and need to change to Standard time, (or vice versa for the other time of the year), change the time by 1 hour if needed and set a flag in the registry to indicate the device is set to DST or Standard time. Looking at the resource csv and the backup file, I am not sure what is happening or when the time change is supposed to happen. When does DST end in the UK (date and time?). What else does the customer have whcih is syncronizing clocks? Dave
Thank you for that explanation, I told the TA and he is going to give that to the customer. As per TA the software that is being used to set the time is Astea FXMobile. The DST occurred Oct 30th - > 31st @ Sun 2am