Ticket #2113 (closed defect: fixed)

Opened 10 years ago

Last modified 10 years ago

[Suspend/resume] suspend time come up right after you change the time

Reported by: wendy_hung Owned by: jeremy, matt
Priority: normal Milestone:
Component: E - Illume Version:
Severity: normal Keywords: Om2008.11
Cc: testing@… Blocked By:
Blocking: Estimated Completion (week):
HasPatchForReview: no PatchReviewResult:
Reproducible: always


[use the testing image]
if you set up suspend time, after change the time setting, it will bring up suspend time.

Tested date:2008.11.10
Update Date:2008.11.10
Installed list:as attach

Steps+current results:
1) set up suspend time 30/60 sec.
2) go change clock time with Setting
3) press "back" to set the time
4) the suspend time came up
5) not every time work the same, i think it depends on what time you change

Change History

comment:1 Changed 10 years ago by marek

  • Reproducible changed from sometimes to always
  • Component changed from Settings to E - Illume

I checked the issue and its rather an illume/ompower bug (not sure who is doing what).
I guess the function that checks the idle time before going into suspend uses the system time as reference which is problematic whenever you change the system time.
I suggest using the system ticks (aka uptime) as reference to avoid this problem.

comment:2 Changed 10 years ago by jeremy

It's Xglamo, we should enable MONOTONIC_CLOCK for Xglamo, then GetTimeInMillis? function will use clock_gettime instead of GETTIMEOFDAY function to make this issue fixed.

comment:3 Changed 10 years ago by jeremy

  • Status changed from new to in_testing

MONOTONIC_CLOCK is enabled in 9b28d998424c77fbc057dd3a022ccbb122793a52 rev of xglamo. Change to testing.

comment:4 Changed 10 years ago by wendy_hung

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

testing image:openmoko-asu-om-gta02.rootfs.jffs2 (2008.nov.27)

check with this problem, not anymore.

Note: See TracTickets for help on using tickets.