For application style permissions, what you generally do is define a new gid
that your device is published under (so it is not world readable/writeable),
add an entry to etc/permissions.xml mapping that gid to a permission string,
and add an item in the frameworks AndroidManifest.xml describing tha
On Dec 7, 8:36 pm, "Dianne Hackborn" <[EMAIL PROTECTED]> wrote:
> For application style permissions, what you generally do is define a new gid
> that your device is published under (so it is not world readable/writeable),
How to define a group statically? (Maybe editing kernel files? Is
there a
Thank you for the tip. I'll check it out.
On Dec 7, 8:36 pm, "Dianne Hackborn" <[EMAIL PROTECTED]> wrote:
> For application style permissions, what you generally do is define a new gid
> that your device is published under (so it is not world readable/writeable),
> add an entry to etc/permissions
On Mon, Dec 8, 2008 at 4:50 AM, Luca Belluccini <[EMAIL PROTECTED]>wrote:
> How to define a group statically? (Maybe editing kernel files? Is
> there any file containing group ids?)
The meaning of groups is purely defined by user space. There is a
system/init header that defines the standard gr
If I want to create a new device, conforming to Android HAL, I should
use one of the following approaches:
1. App - Runtime Service - lib
2. App - Runtime Service - Native Service - lib
3. App - Runtime Service - Native Daemon - lib
Except for the existing devices, it is not easy to ident
