thanks so much for all your research and feedback! I'm not sure where I stand with the database stuff - it seems to me hairy to start messing around in there...
let me know if i should change the summary to point to a solution, nevertheless...
Right now, I am still using the "fake-usb-connect" hack that pops up a dialog asking the user confirmation. it's ugly, but it works, but technically (the library is re-read) but also, and more interestingly, from a usability perspective: I tell people (in the documentation and in person) that it's a hack, and they just need to tap that and things will work. so it's kind of okay.
my next hurdle, at this point, is to fine-tune the *run* trigger, ie. when do i run my sync program. right now it triggers on any udev aactivity:
Code:
KERNEL=="eth*", RUN+="/usr/local/bin/wallabako-run"
KERNEL=="wlan*", RUN+="/usr/local/bin/wallabako-run"
... which is not so great. first, it also runs when the connection goes down (which is silly) and second, it requires the user to "turn wifi off and on again" which is klunky. the first reaction of the user, in my test here, was to tap that neat little "sync" tile on the home screen - is there a way to hook into that?
