On Thu, Feb 26, 2009 at 11:36, Ludwig <[email protected]> wrote:
> Now, what happens is that entries under /proc/bus/usb/001 are create > rw-rw-rw- for ugo and my user-space app can take control of this device. > The downside is of course that any app could do this, with the possibility > of data corruption or even an app taking pictures with my camera without me > knowing (it somehow has to solve the problem of connecting the cables as > well). > > Anyway, I tought I share this with you in the hope it might be useful. I > will post additional libraries sometime today. > Great ! :-) Regarding the permissions problem, (but I still have to better understand android way of doing this), I have the same problem with control of system properties such as usb charge max current. For now I also allowed full rights for any app... Wouldn't the correct way of doing this be : - grant filesystem rights to user system - have a "service" running as system (system apps / library ? I do not know how it works...) which will access these resources, and publish via its API the wanted functions. But it will also check Android security rights. (ie to access USB, define something like USB_HOST_FULL_CONTROL permission) - So Android applications cannot access directly the resource, but must use this library, and will need the correct android permission. _______________________________________________ android-freerunner mailing list [email protected] http://android.koolu.org/listinfo.cgi/android-freerunner-koolu.org
