A new 1.4 ROM coming

[snakekiller]

Any progres?
May i tested?

[artural]

Any progres?
May i tested?

http://www.freaktab.com/showthread.php?242-GoClever-R93-Custom-ROM-by-Finless-with-Market3-4-4-Version-1-4

[snakekiller]

http://www.freaktab.com/showthread.p...-4-Version-1-4

This is for 10g2 right? Just for sure

[Finless]

This is for 10g2 right? Just for sure

No this ROm is for the GoCLever tablet. See the Arnova forum for 1.4 for the 10G2.

Bob

[snakekiller]

No this ROm is for the GoCLever tablet. See the Arnova forum for 1.4 for the 10G2.

Bob

Ok, are these scripts already build in for the 10g2?
Can you cook one for me please with these scripts?

[Finless]

You don't need to have these cooked in a ROM with these scripts. You are fully rooted if you installed my 10 G2 1.4 ROM. Just do what Arturial did and apply them since you are fully rooted!

Bob

[Finless]

Artural, you still around?

Any idea how to make a script run on first boot but not run again after that?

Bob

[petrus]

just an idea about it. That may be not unfeasible, but try simply rm the script itself at the end. Maybe the script cannot be deleted while executing.

[Finless]

just an idea about it. That may be not unfeasible, but try simply rm the script itself at the end. Maybe the script cannot be deleted while executing.

I tried that actually

I was unable to delete a script that was running using Terminal Emulator or sl4a....

BUT... I can delete a script that called a script!

Problem is battery.sh will always try to call a dead scripts every boot. It logs it in logcat and complains

So I tried this already.... It can work but filling logcat with errors is not a elegant way to do this.

Bob

[petrus]

I tried that actually

I was unable to delete a script that was running using Terminal Emulator or sl4a....

BUT... I can delete a script that called a script!

Problem is battery.sh will always try to call a dead scripts every boot. It logs it in logcat and complains

So I tried this already.... It can work but filling logcat with errors is not a elegant way to do this.

Bob

to do it cleanly, if you can modify battery.sh, try :

if [ -e "the_srcipt_you_want_to_call.sh" ]; then
# call your script
fi

That will launch your script only if it exists

[Finless]

As I said Petrus... YOUR a scripting GENIUS!

I will try it.

Bob

[artural]

Artural, you still around?

Any idea how to make a script run on first boot but not run again after that?

Bob

Yes I'm still here but I have not much time (much work in my job),
If I good understand your problem - I'm not sure this

if [ -e "the_srcipt_you_want_to_call.sh" ]; then
# call your script
fi

work good, becouse if You have more scripts in init.d you must check every script (if exist script A.sh then script B.sh then C.sh.....).

[petrus]

Yes I'm still here but I have not much time (much work in my job),
If I good understand your problem - I'm not sure this

work good, becouse if You have more scripts in init.d you must check every script (if exist script A.sh then script B.sh then C.sh.....).

In fact, if you launch the scripts by their name like ./init.d/A.sh you can test if present before calling. If you simply launch every script that is present, the problem of launching a trying to launch a missing script won't occur, I think.

[absurd2]

Sorry to revive this topic but I'd make a suggestion.

Why not use a for loop? Find all files in a directory and run.

I tried the following:

for n in $(ls /system/bin/); do echo $n; done

List all files in the directory. If no files does not cause any output, it does so only if there is no directory. On the other hand you could also set the execution priority preceding numbers to file names, as linux does.

Would be something like:
for n in $(ls /system/init.rd/); do exec $n; done.

I have not tried it, just right on my tablet to test the results and show files as expected, but can't be sure if file will be executed.

Thank you for your attention.

Greetings.

Edit: I have found that ls sort files "randomly", to sort by name we need "busybox ls <dir>".