**** BEGIN LOGGING AT Thu Nov 01 02:59:58 2012
Nov 01 22:00:40 <jeepingben__> I was thinking of looking at SHR bug #1020, is anyone else doing that already?
Nov 01 22:01:02 <jeepingben__> (1020 is the buttons in the contact manager not working)
Nov 01 22:36:09 <Nkokem1> Hi. on SHR: how can I change WifiPower from automatic to manual(on/off) ? I mean through shell/python whatever, not through the settings app.
Nov 01 22:39:57 <jeepingben__> Nkokem1, does fsoraw do what you need?
Nov 01 22:40:30 <jeepingben__> wiki.openmoko.org/wiki/FSO_Resources
Nov 01 23:07:13 <DocScrutinizer51> hah, seems fsoraw been one of my best inventions ;-)
Nov 01 23:08:05 <DocScrutinizer51> and complemeted by lsfsor
Nov 01 23:09:46 <DocScrutinizer51> though I always thought devices should power on as long as /dev/$device is open by a filehandle
Nov 01 23:11:31 <DocScrutinizer51> but for what we got with fso resource management - and that's not that bad at all - fsoraw is just as smart as sliced bread
Nov 01 23:11:42 <DocScrutinizer51> ;-D
Nov 01 23:14:12 <DocScrutinizer51> Nkokem1: note that switching a resource to permanently on or off is definitly deprecated
Nov 01 23:21:24 <Nkokem1> right. the thing is that with fsoraw I don't really get the connection to wpa-wifi. i only get it going by turning wifi manually on (and then only after a few tries)
Nov 01 23:34:25 <DocScrutinizer05> there's no difference in WIFI stae, whether turned on via fsoraw or via permanent setting
Nov 01 23:34:29 <DocScrutinizer05> state*
Nov 01 23:39:54 <DocScrutinizer05> only difference is: fsoraw will automatically power down resp release the resource at quit, while manually you need to take care about that yourself, and you're running into concurrency problems
Nov 01 23:40:21 <DocScrutinizer05> >> Especially recommended for WiFi since due to the bugs in the firmware and the driver full power-cycle of the module is often advantageous. << (about fsoraw, in http://wiki.openmoko.org/wiki/FSO_Resources)
Nov 01 23:43:36 <DocScrutinizer05> Nkokem1: if you encounter problems with WiFi using fsoraw, you maybe wanna use a sleep 10 before starting the actual app needing the WiFi
Nov 01 23:44:49 <DocScrutinizer05> instead of >>  fsoraw -r WiFi -- wpa_supplicant -ieth0 -Dwext -c/etc/wpa_supplicant/wpa_supplicant.conf  << as of wiki, 
Nov 01 23:45:18 <DocScrutinizer05> you do >> fsoraw -r WiFi -- sh -c 'sleep10; wpa_supplicant -ieth0 -Dwext -c/etc/wpa_supplicant/wpa_supplicant.conf' <<
Nov 01 23:48:00 <DocScrutinizer05> though actually I wonder WTF wpa-supplicat isn't started automatically e.g. via udev or whatever, when powering up WiFi
Nov 01 23:49:39 <DocScrutinizer05> the basic idea of fsoraw isn't to start the device 'driver' (or handler) via fsoraw to allocate the device, but rather apps like e.g. web browser allocate a resource like WiFi and starting/powering up WiFi should load and start the needed drivers transparently
Nov 01 23:50:56 <DocScrutinizer05> IOW: if WiFi doesn't include wpa_supplicant, then we need a resource WPA that includes WiFi
Nov 01 23:52:24 <DocScrutinizer05> seriously though, wpa_supplicant shouldn't need to get started manually, rather it should come up automatically whenever WLAN got enabled
Nov 02 00:09:41 <jeepingben_> on SHR issue #1020, it looks like if I change the edit icon in contacts to an edit button, it works.  Any known issue with assigning callbacks to an elm_icon?
**** ENDING LOGGING AT Fri Nov 02 03:00:00 2012