Quote:
|
Originally Posted by leemcc
Let's just face facts, the patch is not working for everyone. It seems to work well for some, and is just a regular pooch screw for others. If I had known I would have had these problems I would have just adjusted the time manually last Sunday and then readjust it when the old daylight savings time made it change again.
But hey, in the grand scheme of things its not so bad. One bad patch should not make us forget all the wonderful information and tweaks/patches we have received over these last couple years.
|
You need to be talking to MS about that. The cab I created worked for me (I did load it right after a hard reset too). And I know lots who did use it, and those that aren't getting it working, seem to also have issues with any of the patches, mine of MS. My CAB was created with the Microsoft file, so if it doesn't work, you need to blame MS, Samsung and Verizon, since they have known about this for quite some time.
Now out of the 27 devices I have updated, this is the process I have used:
1. First sync to make sure all of the information is off of the device.
2. Disconnect from the computer.
3. Turn off the phone radio.
4. Update Windows with the DST patch, reboot.
5. Update Outlook with it's DST patch, reboot.
6. Have the mrailing DST patch and load it on the phone. Change the time zone, soft reset.
7. After soft reset, change time zone back correct zone, then Soft Reset
8. Manually remove the partnership from the phone and from the computer.
9. Sync the phone creating a new partnership, and syncing the information back to the device.
All 27 devices (12x 6700, 5x i730, 6x Moto Q, 4x Samsung BlackJack) have updated correctly and been fine after the update.
The main reason I recreated the partnership and then pushed all the appointments back to the device is part of the Outlook tool is scanning all of the appointments and making sure they are updated to the correct time zone, and I wanted to make sure all of that was correct on the devices.
So out of the 27 I have done, I still haven't had a failure yet, and all 27 (including mine) were on different computers for 9 different companies, with totally different setups.
So hopefully that process with help some of you that are still having problems. Mine is the only device I did after a hard reset, and it has worked fine as well.