My team contacted Verizon EDS about this. EDS seems to think that the problem will be handled automatically on 3/11 as soon as all devices complete time sync. Time syncs are done during a roaming profile update (*22899) or at other times when the device connects to the network. If this is true, I guess the device time would be correct even though the DST settings stored in the registry are incorrect. Question is: would not applying MS's registry settings have any other negative affect? We manage hundreds of WM devices in the field (including many i730s) so whether or not to deploy the CAB is a major decision. Thanks for a great forum.
My team contacted Verizon EDS about this. EDS seems to think that the problem will be handled automatically on 3/11 as soon as all devices complete time sync. Time syncs are done during a roaming profile update (*22899) or at other times when the device connects to the network. If this is true, I guess the device time would be correct even though the DST settings stored in the registry are incorrect. Question is: would not applying MS's registry settings have any other negative affect? We manage hundreds of WM devices in the field (including many i730s) so whether or not to deploy the CAB is a major decision. Thanks for a great forum.
Actually no. Pocket PC devices do NOT look to Verizon for Date/Time information. It is kept on it's own, and synced and updated when connected to the computer. If they make a change in their tower, it will not affect you. This is because of the stored calendar items on the device. If you changed a time zone and made an appointment, then the phone wouldn't know which time zone the appointment was part of or which time zone it should be scheduled in. So the PPC's need you to manually set the time zone and time so it doesn't mess with appointments.
I did a big discussion of this at one time, and I know there are LOTS of discussions on this online. Your i730 and other Pocket PC devices will NOT automatically update when time is changed, other phones on Verizon's network will, but Pocket PC devices don't receive the update from the service provider, which is why they released this patch information.
Yes your time will update when connected to the computer, but it also might try changing again when it "thinks" the time should be updated again, so you might get a double change, and it won't fix itself until connected to the computer again.
It would be best, as advised by Microsoft (since they know more about there devices than Verizon does), to run the update, either in your own created CAB, or the one I provided...
__________________
-Michael
Need help setting up your i730/i830 or other WM2003/WM5 Phone, as well as the other hacks I have done, check out the MRailing Guides and Links
Thanks for the reply. Try the following on your WM5 i730:
(1) Set the time and date incorrectly in the Clocks & Alarms screen
(2) Run an OTA update (*22899)
(3) This should re-sync time and date
Note that, as you implied, time zone is never altered by the carrier -- the user is responsible for updating this according to his location. However, time zone (at least as displayed in Clocks & Alarms) does not change during DST. It stays set to GMT-X based on your location and does its recalc internally according to registry settings. Therefore, as long as the device syncs to the carrier, the date and time will be correct. This is essentially the case Verizon is making.
Thanks for the reply. Try the following on your WM5 i730:
(1) Set the time and date incorrectly in the Clocks & Alarms screen
(2) Run an OTA update (*22899)
(3) This should re-sync time and date
Note that, as you implied, time zone is never altered by the carrier -- the user is responsible for updating this according to his location. However, time zone (at least as displayed in Clocks & Alarms) does not change during DST. It stays set to GMT-X based on your location and does its recalc internally according to registry settings. Therefore, as long as the device syncs to the carrier, the date and time will be correct. This is essentially the case Verizon is making.
But you had to do an update on your device to the tower, and then what happens when the time change happens AGAIN on the incorrect LATER date, it will again change, causing appointments to be wrong because it will double change the time.
All other phones pull the date/time from the tower, without having to do an update. Although the i730 might pull a time when doing a full program (*22899), it doesn't change the time while driving down the road, or simply just by getting it from the tower, like all other devices do. Trust me, it will cause issues when this happens, and I am sure that there will be lots of people trying to figure out what's happened...
__________________
-Michael
Need help setting up your i730/i830 or other WM2003/WM5 Phone, as well as the other hacks I have done, check out the MRailing Guides and Links
mrailing... I must be totally blind, but I'm still not seeing the CAB that you've said you've posted.
Yes you are blind, re-read post#1, and when you do, pay CLOSE attention to the text right above the TXT available for download....
__________________
-Michael
Need help setting up your i730/i830 or other WM2003/WM5 Phone, as well as the other hacks I have done, check out the MRailing Guides and Links
Because this edits registry settings for specific time zones, is this ok to push out to all Windows Mobile devices? We have ~300 Windows Mobile devices, but they are not all in the US. I'm wondering if we have to only make this change to devices in the time zones affected... or if I can just push it out based on OS.
Ran the file on my trusty Samsung i600 from Sprint and got a message that said the program is not digitally signed. So what do we Sprint users do to account for the change in DST
I, too, checked yesterday and today on the windowsmobile site to see if I could find the official fix; it still wasn't posted. I have since decided to run the hack posted here, hoping it works; but I'm going to continue checking the Microsoft official site for their fix just in case.
The hack here works fine on my i730, even checking by changing the date/time on both my PC and on the PDA to be hours before the time zone change, and then letting it roll over. I got the notification that it changed the DST, so I do know that my file works.
Once MS posts it, I will place the official right next to mine, but as of now, it's still not available.
__________________
-Michael
Need help setting up your i730/i830 or other WM2003/WM5 Phone, as well as the other hacks I have done, check out the MRailing Guides and Links
Ummm, yeah, it's been updated in the first post of this thread since Wednesday, Feb. 14... Check out the BIG RED LETTERS in the first post...
__________________
-Michael
Need help setting up your i730/i830 or other WM2003/WM5 Phone, as well as the other hacks I have done, check out the MRailing Guides and Links
I read the article and there are no mentions of Vista. Is the problem corrected in Vista (and communicates the solution to my device) or do I still need to update my device?
Your device is independent of Vista and needs to be updated whether the OS is fixed or not...
__________________
-Michael
Need help setting up your i730/i830 or other WM2003/WM5 Phone, as well as the other hacks I have done, check out the MRailing Guides and Links
I cannot get the CAB from microsoft to install on a Pocket PC 2003 devices (I've tried several different ones). Keep getting the error "...is not a valid Windows CE Setup file".
The original CAB file from this thread does work.
anyone else had the same problem on older devices?
I know I can hack this myself, or download another hack to do it, but was wondering if anyone has seen the official one?
Technically the original CAB file linked in this thread isn't a hack. It is exactly what Microsoft suggested to do. It's about time they decided to build a CAB install for it.
Technically the original CAB file linked in this thread isn't a hack. It is exactly what Microsoft suggested to do. It's about time they decided to build a CAB install for it.
http://support.microsoft.com/kb/923953: "If you own a device that is running Microsoft Windows Mobile for Pocket PC or Microsoft Windows Mobile for Smartphone, do not try to edit the registry. The registry modifications that are mentioned in this article are intended only for device manufacturers." "End-users should check whether this update is available from the device manufacturer." "OEM device manufacturers can use the following listing to create an .inf file that is contained in a .cab file."
If the manner in which you installed it left an entry in Remove Programs, you could go to the Start, Settings, System, Remove Programs to see evidence of it's installation.
It is exactly what Microsoft suggested to do. It's about time they decided to build a CAB install for it.
Login
Panel
