This discussion is archived
1250 Views 3 Replies Latest reply: Jun 1, 2008 10:50 AM by Barry Woods1
Currently Being ModeratedJul 12, 2006 10:45 AM (in response to Barry Woods1)Hi,
I've noticed that too. I sync with a Nokia 6230. I've noticed that a few Birthdays do get sync'd but most do not. The ones that get sync'd have recent birth years e.g. 2001. Most of my contacts birth years are througout the 70's and none of those get sync'd.
I guess I could put the true birthyear as a note and then give them all a birthyear of 2005 which I know will work hopeufully for the life of the phone. Perhaps my next phone will work around this age problem.
Powerbook G4, 1.25 Ghz, 1GB Ram, 15in Mac OS X (10.4.2)
Currently Being ModeratedJul 12, 2006 2:12 PM (in response to Barry Woods1)The root of this issue lies with someone at Symbian who realized that a significant amount of space could be saved when storing agenda entries if an an alternative to the traditional TTime API was available.
TTime stores values representing dates and times as the number of microseconds since midnight, January 1st, 0 AD on the Gregorian calendar. The alternative TUint16 API imposes a highly restricted date range: only values from January 1, 1980 through December 31, 2100 are stored, where each value is calculated in a similar manner from the start of the range. Great for one-time events within the range, but lousy for birthdays and similar recurring events, many instances of which clearly fall outside of it.
So along come those responsible for writing Symbian code for mobile handsets, and many of them latch onto TUint16, or use library routines or programming samples created by others who did. So now, recurring or non-recurring events, outside of the January 1, 1980 through December 31, 2100 window cannot be handled properly by many [probably most] Symbian OS-based mobile handsets and smartphones. That's why you see this across a range of handsets from several manufacturers, but not all handsets from any one manufacturer are adversely affected.
Because this issue involves the mobile OS and calendaring applications themselves, there is no workaround available to users hoping to display the disallowed dates. Only a rewrite of the calendar code for a mobile handset would correct the problem.
A perfect example of a seemingly clever idea with an unintended outcome.
Let's see: 120 years. If only they had picked an earlier start date…PowerBook G4 12 867 MHz 640 meg 40 gig SuperDrive, Mac OS X (10.4.7), Does anybody really know what TTime it is?
Currently Being ModeratedJun 1, 2008 10:50 AM (in response to Barry Woods1)Yeah, answered question. And I've chnaged my phone now anyway.. stuff works fine. Thanks.