Hi Anil, if you are building system images from android codebase then u can run android application to run under uid system by making few modification to your application.
add sharedUserId=" android.uid.system" in your AndroidManifest.xml <manifest xmlns:android="http://schemas.android.com/apk/res/android"; package="your.app.package.name" android:sharedUserId="android.uid.system"> and LOCAL_CERTIFICATE := platform to you Android.mk file of your project. Thanks, Vishnu. On Oct 16, 10:49 am, Anil <[email protected]> wrote: > > > An Android program is typically run as a non-privileged process (with > > > unique > > > user ID) from the perspective of the Linux kernel. > > > As a result, one solution to allow the program to access the device driver > > > is to grant read/write permission to the device files or sysfs files. > > > For example, assume you have the device file named /dev/my_devfile. Set it > > > with the following command: chmod 0666 /dev/my_devfile. > > Yes, the driver had rw------ > I changed it and it worked. > However, I had to to connect a usb cable, adb shell and then chmod. > Is there a way for the program to access the device driver by > mentioning permissions in the AndroidManifest.xml? > I tried using FACTORY_TEST and HARDWARE_TEST permissions, but they > dont get installed under settings. > Anil -- unsubscribe: [email protected] website: http://groups.google.com/group/android-kernel
