Opened 5 years ago

Closed 5 years ago

#397 closed defect (fixed)

SetWakeupTime differs with GetWakeupTime

Reported by: avanc Owned by: daniel
Priority: major Milestone:
Component: framework/odeviced Version: milestone5
Keywords: Cc:

Description

GetWakeupTime returns time with 1 hour difference to the value set with SetWakeupTime:

mdbus -s org.freesmartphone.odeviced /org/freesmartphone/Device/RealTimeClock/0 org.freesmartphone.Device.RealTimeClock.SetWakeupTime \'1237463865\'

mdbus -s org.freesmartphone.odeviced /org/freesmartphone/Device/RealTimeClock/0 org.freesmartphone.Device.RealTimeClock.GetWakeupTime

returns 1237460265.0

Maybe a problem of UTC vs. local time?

Change History (2)

comment:1 Changed 5 years ago by daniel

  • Owner changed from mickey to daniel
  • Status changed from new to assigned

comment:2 Changed 5 years ago by daniel

  • Resolution set to fixed
  • Status changed from assigned to closed

Fixed in commit f7e40ab0c79528e065c75ca938645bb7ba5a7294

odeviced: Fix time and format problems in the RTC interface

This fixes FSO bug #374 and brings the RTC interface in line with the
spec. Also fixes the time offset some people (probably everyone not in
UTC) experienced between calls of SetWakeupTime? and GetWakeupTime?.
See http://docs.python.org/library/time.html for the different
conversions "seconds since the epoch" <-> "{local,UTC} time".

Note: See TracTickets for help on using tickets.