Opened 9 years ago

Closed 9 years ago

#401 closed defect (wontfix)

org.freesmartphone.Device.RealTimeClock do not work

Reported by: misc Owned by: daniel
Priority: major Milestone:
Component: Frameworkd / FSO Version: SHR-unstable
Keywords: Cc:

Description

It seems that this method does nothing :

$ date ; mdbus -s org.freesmartphone.odeviced "/org/freesmartphone/Device/RealTimeClock/rtc0" org.freesmartphone.Device.RealTimeClock
.SetCurrentTime 1 ; date ;         
Fri Apr 17 03:31:32 CEST 2009
Fri Apr 17 03:31:35 CEST 2009

The dbus method however return 1, meaning success, according to the code of pyrtc.

Change History (5)

comment:1 Changed 9 years ago by misc

That's strange, because in the log, i can see :

[13028.645000] pcf50633-rtc pcf50633-rtc: RTC_TIME: 1.0.70 0:0:1
[13028.645000] pcf50633-rtc pcf50633-rtc: PCF_TIME: 01.01.70 00:00:01

Date however work well to change the date and time.

comment:2 Changed 9 years ago by daniel

This only affects the RTC, not the system time. Please use hwclock to get the RTC time, not date.

comment:3 Changed 9 years ago by misc

Indeed, this work. But that also mean that there is no way to set the time using dbus ?
( this also mean that the patch on #400 is wrong )

comment:4 Changed 9 years ago by daniel

That's correct, but this is a simple operation anyway (and one that only very specific apps should be allowed to perform) so I don't quite see the need for a DBus interface.

comment:5 Changed 9 years ago by spaetz

  • Resolution set to wontfix
  • Status changed from new to closed

Closing bug as per Daniel's comment above. Please reopen if you disagree. Perhaps the above can be added to the FSO specs (setting of RTC doesn't affect system time and 'date')?

Note: See TracTickets for help on using tickets.