Crashing internally without a force-close window

[GoogleCodeExporter]

What steps will reproduce the problem?
1.simply boot
2.apply rules
3.read log
4.enable/disable app internally or via the widget

What is the expected output? What do you see instead?
Expecting smooth applying of the rules, instead the device locks vibrates once 
a few seconds pass with the device staying locked up, then it quickly vibrates 
twice and resumes normal operation without any warning.

What version of the product are you using? On what operating system?
Droid Wall 1.4.2, Galaxy S on froyo 2.2 tested on multiple firmware versions: 
JPM, JPK, JP6 with the same outcome.

Please provide any additional information below.
Sometimes rules don't get applied for a newly installed app or trying to apply 
them to the new app breaks the whole program.
Using Chainfire's root v1.2 with busybox 1.17
http://forum.xda-developers.com/showthread.php?t=788108

Original issue reported on code.google.com by vadimpe...@gmail.com on 21 Oct 2010 at 4:51

[GoogleCodeExporter]

Tried:
Running 
droidwall.sh 
from
cd /data/data/com.googlecode.droidwall/cache
with root explorer and had the same result. I checked the permissions and all 
of them were enabled...

Original comment by vadimpe...@gmail.com on 21 Oct 2010 at 5:00

[GoogleCodeExporter]

Dirty fix from post 51 worked!

cp iptables_g1 iptables_g1_old
cp iptables_n1 iptables_g1
./droidwall.sh

Original comment by vadimpe...@gmail.com on 21 Oct 2010 at 5:23

[GoogleCodeExporter]

Seems to be the same problem from issue 51 - I am still researching a solution.

Original comment by rodrigo...@gmail.com on 21 Oct 2010 at 11:23

• Changed state: Accepted

[GoogleCodeExporter]

Closing this just to keep everything on issue 51.

Original comment by rodrigo...@gmail.com on 23 Oct 2010 at 12:52

• Changed state: Duplicate