Re: [FSO] the Display resource
2010/1/8 Michael 'Mickey' Lauer mic...@vanille-media.de Am Donnerstag, den 07.01.2010, 21:57 +0100 schrieb Michal Brzozowski: Sorry this has been documented somewhere. I'm playing with the 'Display' resource, and I'm totally confused. I can understand that. The semantics of the Display (and CPU) resource is somewhat different from the semantics of the other peripherals. The display resource is _not_ controlling the display. What it does instead is modifying the way the Idle Notifier works. When you claim the display resource, then the Idle Notifier IDLE_DIM (and subsequent states, such as LOCK and SUSPEND) will no longer be sent, hence the display will stay on and the device will not go into suspend. Thanks! That explains everything :-) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[FSO] the Display resource
Hi, Sorry this has been documented somewhere. I'm playing with the 'Display' resource, and I'm totally confused. If I make this call: org.freesmartphone.Usage.GetResourceState Display, and it returns 'true', does it mean that the phone's display is supposed be on? If I put this into /etc/freesmartphone/oevents/rules.yaml: while: PowerStatus() filters: Not(HasAttr(status, discharging)) actions: -OccupyResource(Display) -OccupyResource(CPU) Does it mean that if the phone is plugged in the display will be always on, and the phone will not suspend ? What's the right way to tell frameworkd that I've modified rules.yaml? pkill -HUP frameworkd or /etc/init.d/frameworkd restart? Thanks, Michal ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [FSO] the Display resource
2010/1/7 Michal Brzozowski ruso...@poczta.fm Hi, Sorry this has been documented somewhere. I'm playing with the 'Display' resource, and I'm totally confused. If I make this call: org.freesmartphone.Usage.GetResourceState Display, and it returns 'true', does it mean that the phone's display is supposed be on? Ok, I found out that the answer to this question is yes. However, here's a case where it doesn't work (I'm using SHR-testing from 16.12.09) // At this point the display is off, the policy is 'auto' r...@om-gta02 ~ $ dbus-send --type=method_call --system --print-reply --dest=org.freesmartphone.ousaged /org/freesmartphone/Usage org.freesmartphone.Usage.GetResourceState string:'Display' method return sender=:1.6 - dest=:1.82 reply_serial=2 boolean false r...@om-gta02 ~ $ dbus-send --type=method_call --system --print-reply --dest=org.freesmartphone.ousaged /org/freesmartphone/Usage org.freesmartphone.Usage.SetResourcePolicy string:'Display' string:'enabled' method return sender=:1.6 - dest=:1.84 reply_serial=2 r...@om-gta02 ~ $ dbus-send --type=method_call --system --print-reply --dest=org.freesmartphone.ousaged /org/freesmartphone/Usage org.freesmartphone.Usage.GetResourceState string:'Display' method return sender=:1.6 - dest=:1.85 reply_serial=2 boolean true // The display continues to be off, even after a long time I can't find a reliable way to turn the display on from the console. Any ideas? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [FSO] the Display resource
2010/1/7 Michal Brzozowski ruso...@poczta.fm // The display continues to be off, even after a long time However, when I tap the screen, the display turns on and never goes off again. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [FSO] the Display resource
Am Donnerstag, den 07.01.2010, 21:57 +0100 schrieb Michal Brzozowski: Sorry this has been documented somewhere. I'm playing with the 'Display' resource, and I'm totally confused. I can understand that. The semantics of the Display (and CPU) resource is somewhat different from the semantics of the other peripherals. The display resource is _not_ controlling the display. What it does instead is modifying the way the Idle Notifier works. When you claim the display resource, then the Idle Notifier IDLE_DIM (and subsequent states, such as LOCK and SUSPEND) will no longer be sent, hence the display will stay on and the device will not go into suspend. If I put this into /etc/freesmartphone/oevents/rules.yaml: while: PowerStatus() filters: Not(HasAttr(status, discharging)) actions: -OccupyResource(Display) -OccupyResource(CPU) Does it mean that if the phone is plugged in the display will be always on, and the phone will not suspend ? Yes, that's the idea. What's the right way to tell frameworkd that I've modified rules.yaml? pkill -HUP frameworkd or /etc/init.d/frameworkd restart? I'm afraid the current frameworkd needs a restart after modifying the rules. I promise to fix this in the FSO2. Cheers, -- :M: ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
