droidwall.sh: not found about droidwall

[GoogleCodeExporter]

P.S. The version I used before was 1.3.8; 
for the time being I've reverted to that.

Original comment by [email protected] on 16 Sep 2010 at 4:28

[GoogleCodeExporter]

Could you try to clear the application cache and try again please?
Go in the System Settings, Manage Applications (or similar), find Droid Wall 
and click on "Clear cache".

Original comment by [email protected] on 16 Sep 2010 at 6:13

[GoogleCodeExporter]

I gave it a try: first the "clear cache" button was not enabled,
but after choosing "clear data" and re-starting the app,
I was able to select "clear cache".
Still, the reported problem remains :-(

Original comment by [email protected] on 16 Sep 2010 at 6:36

[GoogleCodeExporter]

Okay, so maybe the application is being somehow blocked from modifying the file 
permissions.
Could you open a terminal emulator an issue the following command:
ls -la /data/data/com.googlecode.droidwall/cache/droidwall.sh

Then post the ouput here? thanks!

Original comment by [email protected] on 16 Sep 2010 at 6:45

[GoogleCodeExporter]

The output of ls -l (not: ls -la) is:
-rwxrwxrwx app_118 app_118 12 2010-09-16- 21:00 droidwall.sh

Original comment by [email protected] on 16 Sep 2010 at 7:03

[GoogleCodeExporter]

Interesting... permissions are good. Could you try the attached development 
version for me, please?
Thanks

Original comment by [email protected] on 16 Sep 2010 at 7:17

Attachments:

• droidwall-dev.apk

[GoogleCodeExporter]

Unfortunately, my phone refuses to install, though unknown sources enabled.

Original comment by [email protected] on 16 Sep 2010 at 8:49

[GoogleCodeExporter]

Update: After *uninstalling* version 1.3.8, 
I was able to install both 1.4.0 and your 1.4.1 dev version. 
Yet both of them exhibit the same problem reported above.
BTW, after uninstalling, all my selections were gone :-(

Original comment by [email protected] on 17 Sep 2010 at 8:12

[GoogleCodeExporter]

Update: Problem solved :-)

So far I did not mention that the reported error message talking about
/data/data/com.googlecode.droidwall/cache/droidwall.sh actually starts
with "Could not acquire root access. You need a rooted phone to run Droid Wall"
I suspected that something was wrong with the superuser privileges.
This turned out not actually be the problem, but trying to install 
a later version of Superuser.apk, I got a further error which lead me to
http://alldroid.org/archived/threads/15330.html 
This contained a very helpful remark:
  someone replaced /system/bin/sh with a link to the busybox sh. 
  That really should be undone: shell scripts which don~t start with 
  "#!/system/bin/sh" (or some other interpreter) 
  don't get launched correctly by busybox's shell.
The system variant I use did replace the standard shell with ash/busybox
and after restoring the original sh, the recent Droidwall versions work fine!

Maybe the problem can also be avoided by adding "#!/system/bin/sh" to 
Droidwall's shell script?

Original comment by [email protected] on 22 Sep 2010 at 9:16

[GoogleCodeExporter]

Good that the problem is solved.
I will add the "#!/system/bin/sh" anyway ;)

Original comment by [email protected] on 23 Sep 2010 at 11:58

• Changed state: Done