Quote:
Originally Posted by Kolano
Quote:
Originally Posted by luv2chill
In fact I'm so sure this is the problem I'm just going to go ahead and remove all time zone settings from all of the carrier provxml files.
|
Instead, could you add the missing registry entries that break the timesync (and possibly other) functionality. I really liked not having to set my timezone with each reset.
|
@Kolano - I explained this earlier. If you don't want to have to set your time zone you should add the required entries (I even provided the two keys you need) to an RGU file in your own customize OEM package. Everyone should make one of these once they are comfortable enough with how the kitchen works. Make sure your customize OEM has a UUID that starts with several "f"s (at least three, up to the first eight digits if you want). This ensures that your entries will be the "last in" and won't be overwritten.
I don't want the time zone to be in the provxmls (at least the North America ones) because it's just causing too many problems with the DST stuff, plus everyone here has a different time zone preference--there's no reason for Verizon to default to Eastern over any of the other US time zones. MS defaults to pacific, and that's how the kitchen will be. If you don't want to set your time zone each time just set it once, export those two registry keys, and add them to an rgu. It is extremely easy and is the "right" way to go about this IMHO.