"org.freesmartphone.Usage.SetResourcePolicy CPU disabled" affects "PolicyDisplay"

[dagger]

When I enable only PolicyDisplay? screen does not go blank. Exactly as expected (btw should enabling this policy turn backlight on automatically?).

2009.02.07 13:39:44 frameworkd.resource INFO setting resource status for Display from disabled to enabling
2009.02.07 13:39:44 frameworkd.resource INFO setting resource status for Display from enabling to enabled
2009.02.07 13:39:44 ousaged INFO Enabled Display in 0.1 seconds
2009.02.07 13:39:45 odeviced.idlenotifier INFO odeviced.idlenotifier state change to busy
2009.02.07 13:39:45 oeventsd.action INFO DebugAction? : dbus trigger test
2009.02.07 13:39:45 oeventsd INFO Receive IdleState?, status = busy
2009.02.07 13:39:46 oeventsd.action INFO call dbus signal /org/freesmartphone/Device/Display/0 SetBrightness?((90,))
2009.02.07 13:39:46 oeventsd INFO Receive IdleState?, status = busy
2009.02.07 13:39:46 oeventsd INFO Receive IdleState?, status = busy
2009.02.07 13:39:46 oeventsd.action INFO signal SetBrightness? responded : ()
2009.02.07 13:39:56 odeviced.idlenotifier INFO odeviced.idlenotifier state change to idle
2009.02.07 13:39:56 oeventsd.action INFO DebugAction? : dbus trigger test
2009.02.07 13:39:56 oeventsd INFO Receive IdleState?, status = idle
2009.02.07 13:39:56 oeventsd INFO Receive IdleState?, status = idle
2009.02.07 13:39:56 oeventsd INFO Receive IdleState?, status = idle

Every thing as expected. Right now let's enable and than disable CPU.

2009.02.07 13:41:59 frameworkd.resource INFO setting resource status for CPU from disabled to enabling
2009.02.07 13:41:59 frameworkd.resource INFO setting resource status for CPU from enabling to enabled
2009.02.07 13:41:59 ousaged INFO Enabled CPU in 0.1 seconds 2009.02.07 13:42:06 frameworkd.resource INFO setting resource status for CPU from enabled to disabling
2009.02.07 13:42:06 odeviced.idlenotifier INFO odeviced.idlenotifier state change to idle
2009.02.07 13:42:06 frameworkd.resource INFO setting resource status for CPU from disabling to disabled
2009.02.07 13:42:06 oeventsd.action INFO DebugAction? : dbus trigger test
2009.02.07 13:42:06 oeventsd INFO Receive IdleState?, status = idle
2009.02.07 13:42:06 oeventsd INFO Receive IdleState?, status = idle
2009.02.07 13:42:06 oeventsd INFO Receive IdleState?, status = idle
2009.02.07 13:42:06 ousaged INFO Disabled CPU in 0.2 seconds

Since I didn't touch DISPLAY policy, I expect display to stay highlighted all the time. Unfortunately CPU policy somehow "resets" DISPLAY and it goes blank:

2009.02.07 13:42:26 odeviced.idlenotifier INFO odeviced.idlenotifier state change to idle_dim
2009.02.07 13:42:26 oeventsd.action INFO DebugAction? : dbus trigger test
2009.02.07 13:42:26 oeventsd INFO Receive IdleState?, status = idle_dim
2009.02.07 13:42:26 oeventsd INFO Receive IdleState?, status = idle_dim
2009.02.07 13:42:26 oeventsd.action INFO call dbus signal /org/freesmartphone/Device/Display/0 SetBrightness?((20,))
2009.02.07 13:42:26 oeventsd INFO Receive IdleState?, status = idle_dim
2009.02.07 13:42:26 oeventsd.action INFO signal SetBrightness? responded : ()
2009.02.07 13:42:38 odeviced.idlenotifier INFO odeviced.idlenotifier state change to idle_prelock
2009.02.07 13:42:38 oeventsd.action INFO DebugAction? : dbus trigger test
2009.02.07 13:42:38 oeventsd INFO Receive IdleState?, status = idle_prelock
2009.02.07 13:42:38 oeventsd INFO Receive IdleState?, status = idle_prelock

I have to manually disable and re-enable it to have this effect:

009.02.07 13:53:40 frameworkd.resource INFO setting resource status for Display from enabled to disabling
2009.02.07 13:53:40 odeviced.idlenotifier INFO odeviced.idlenotifier state change to lock
2009.02.07 13:53:40 frameworkd.resource INFO setting resource status for Display from disabling to disabled
2009.02.07 13:53:40 oeventsd.action INFO DebugAction? : dbus trigger test
2009.02.07 13:53:40 oeventsd INFO Receive IdleState?, status = lock
2009.02.07 13:53:40 oeventsd INFO Receive IdleState?, status = lock
2009.02.07 13:53:40 oeventsd INFO Receive IdleState?, status = lock
2009.02.07 13:53:40 ousaged INFO Disabled Display in 0.2 seconds
2009.02.07 13:53:47 frameworkd.resource INFO setting resource status for Display from disabled to enabling
2009.02.07 13:53:47 frameworkd.resource INFO setting resource status for Display from enabling to enabled
2009.02.07 13:53:47 ousaged INFO Enabled Display in 0.1 seconds

I think it's a bug (although it might be intentional) and PolicyDisplay? once enabled should not allow display to go blank unless explicitly disabled.

[mickey]

This seems to work for me after fixing #336 and #343.

Keep in mind that it could be confusing at times, if you 'disable' the 'Display' resource, you say, the display is not absolutely necessary, which means the normal behaviour is active.

We could discuss whether this is intentional or whether 'disabling' the 'Display' resource should mean the display will never be enabled.

More comments, folks?

[daniel]

I would vote for the following behaviour:

• "enabled" -> Display stays on
• "auto" -> Normal behaviour, display is on when busy and off otherwise
• "disabled" -> Display stays off. This is useful i.e. if you have a GPS logger running in your pocket.

[daniel]

It looks like Jan is currently working on this issue (see commit [516f48762ab7afa4e4702a0ba01bc0a004ae4c60])

[mickey]

AFAICT we can consider this being fixed. Please reopen, if you disagree.