Thanks for this added info!
On Sep 22, 11:27 pm, Brad Davis wrote:
> Just a few more notes. If you don't use the "oneshot", you don't need
> the fork() (init restarts the service if it fails). This is not how
> Unix/Linux services are written (one of the differences between
> Android and Linux)
Just a few more notes. If you don't use the "oneshot", you don't need
the fork() (init restarts the service if it fails). This is not how
Unix/Linux services are written (one of the differences between
Android and Linux).
The reason you don't normally want to use "oneshot" is because Android
can
The problem is in the init.rc, the app runs with no problem when
manually executed/called in the shell. The init.rc inside the device
cannot be edited because the original file stays in rom and will
replace itself in the directory everytime the device reboots. And Yes
Sir for all the method above,
init.rc is in the ramdisk image, a disposable copy of which becomes
the root filesystem onto which /system, /data, etc are mounted. You
have to learn how to modify that (sequence of cpio commands one can
never remember) and repackage it with the kernel. Rebuilding the whole
android is likely wasti
First of all: check if the problem is in your app or init.rc is not
updated.
I would start from something trivial - hello world should be enough.
If it a simple app works then check all system calls if they are
really supported in bionic, run your app from the command line, use
gdb, etc.
If it stil
