The LEDs are just off. In frameworkd.log I see: 2011.01.16 15:03:01.511 oeventsd.fso_triggers INFO Receive PowerStatus, status = charging 2011.01.16 15:03:01.532 oeventsd INFO turn led gta02_orange_power on 2011.01.16 15:03:01.579 oeventsd.fso_triggers INFO Receive PowerStatus, status = charging 2011.01.16 15:03:01.656 oeventsd.fso_triggers INFO Receive PowerStatus, status = charging 2011.01.16 15:03:01.677 oeventsd.fso_triggers INFO Receive PowerStatus, status = charging 2011.01.16 15:03:01.720 oeventsd ERROR DBus call returned an error 2011.01.16 15:30:44.693 oeventsd.fso_triggers INFO Receive PowerStatus, status = full 2011.01.16 15:30:44.705 oeventsd INFO turn led gta02_orange_power off 2011.01.16 15:30:44.721 oeventsd.fso_triggers INFO Receive PowerStatus, status = full 2011.01.16 15:30:44.743 oeventsd.fso_triggers INFO Receive PowerStatus, status = full 2011.01.16 15:30:44.757 oeventsd INFO turn led gta02_blue_power on 2011.01.16 15:30:44.779 oeventsd.fso_triggers INFO Receive PowerStatus, status = full 2011.01.16 15:30:44.795 oeventsd ERROR DBus call returned an error 2011.01.16 15:30:44.802 oeventsd ERROR DBus call returned an error
However, I'm able to set the LEDs by hand with mdbus2 -s org.freesmartphone.odeviced /org/freesmartphone/Device/LED/gta02orangepower org.freesmartphone.Device.LED.SetBrightness 100 I've looked into /usr/lib/python2.6/site-packages/framework/subsystems/oeventsd/leds_actions.py but I can't see from where the LED-names are made of. And while someone fixes this, is it possible to get a more talkative message rather than "DBus call returned an error"? _______________________________________________ Shr-User mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-user
