FS#10610 - Calendar

Attached to Project: Rockbox
Opened by Clifford Bressette (cliffbressette) - Thursday, 17 September 2009, 17:01 GMT
Last edited by Michael Chicoine (mc2739) - Sunday, 01 November 2009, 04:06 GMT
Task Type Bugs
Category Plugins
Status Closed
Assigned To No-one
Operating System iPod 5G
Severity Low
Priority Normal
Reported Version Version 3.3
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


The calendar is offset by one day
This task depends upon

Closed by  Michael Chicoine (mc2739)
Sunday, 01 November 2009, 04:06 GMT
Reason for closing:  Out of Date
Additional comments about closing:  No response
Comment by Nils Wallménius (nls) - Friday, 18 September 2009, 16:01 GMT
hi, i'd like some more details about your problem.
Are you sure you've set the corect year?
Is the *weekday* off? and if so i which direction, is a wednesday said to be tuesday or thursday?
Does the "Set time and date screen show the correct day or is it off too?
Comment by Eric Farmer (databat) - Tuesday, 29 September 2009, 21:01 GMT
I have noticed this same issue with the Sansa e260 V2. However, mine is off two days. By that I mean, today is really a Tuesday, the 29th. However, the calendar shows it's on a Sunday. (yes my day, month and year are all set correctly) Perhaps someone goofed in calculating leap years?
Comment by Clifford Bressette (cliffbressette) - Wednesday, 30 September 2009, 17:46 GMT
I'm sorry I took so long to respond. I actually lost my ipod for a bit. I found I am off by one day..Today is Monday, but shows as a Tuesday...I've noticed that along the top where the days are labled (M, T, W...) It's not quite normal...I'm not sure if it's different internationally, but in the US anyway, most calendars start on a Sunday. The one here starts on a Monday, but if it were to start on a Sunday and the dates were left alone it would be least on mine, I'm not sure about yours databat.
Comment by Michael Chicoine (mc2739) - Sunday, 11 October 2009, 19:11 GMT
Please report back if you are still seeing this. There have been changes to the real time clock code with r22839 and r23037 that may have fixed this problem.