this kind of tips may represent three issue:
1. your system is compiled as user-tag.
to change the security flag , you can modify your ramdisk/default.prop
ro.security to 0 , you will have the authority as root,
this is the shortest way to hack compared to compile the system as eng-tag.
2. your console(ttyUSB or ttySx) is configured as shell . this is set
from your init.rc file. (grep "console" in your init.rc :? )
3. if you use adb shell , please use adb remount first.
good luck~
On 2011年11月15日 14:59, arvr wrote:
Yes am executing as root. This is what I do (& the results) after the
device boots up at the command line(through the terminal)
$ ls /sys/class/leds
green
battery-led
lcd-backlight
keyboard-backlight
$
$
$
$ echo 1> /sys/class/leds/keyboard-backlight/brightness
cannot create /sys/class/leds/keyboard-backlight/brightness:
permission denied
$
$ echo 1> /sys/class/leds/green/brightness
cannot create /sys/class/leds/green/brightness: permission denied
I understand that by default device will boot up in root permission.
In the init.rc I see that the devices are "chown"ed to system system
chown system system /sys/class/leds/keyboard-backlight/brightness
So I am trying to understand this part of the world and how to get
things done.
Any information or links will be highly appreicated.
Thanks and Regards,
ARVR.
On Nov 15, 2:09 am, Earlence<[email protected]> wrote:
are you executing this as root?
-earlence
On Nov 14, 2:47 pm, arvr<[email protected]> wrote:
Hi,
I am trying to access leds from command line (through the terminal),
but I am getting "Permission Denied" error and am struck on similar
issues.Can you please help me to understand what's wrong.
Environment:
a. OMAP 4430 Panda board
b. Linux 2.6.36 and Android GB 2.3.3
c. I have integrated the leds and it is visible to me as "/sys/class/
leds/green/"& "/sys/class/leds/keyboard-backlight".
When I perform,
echo 1> /sys/class/leds/green/brightness
or
echo 1> /sys/class/leds/keyboard-backlight/brightness
kernel tells me "Permission Denied". I use the regular init.rc file as
given in the OMAPPedia website, with the changes done by commenting
the line "#mount rootfs rootfs / rw remount" etc.
Similar to this, I am executing the "yavta" tool
(https://www.gitorious.org/omap4-v4l2-camera/yavta) and that too is not
executing the command, kernel reports me that no such file or folder
is present. The tool is copied in the same folder and I run it as
yavta -h
What could be reasons? Please help me out.
Thanks,
ARVR.
--
unsubscribe: [email protected]
website: http://groups.google.com/group/android-kernel
