Can someone help me with step 21
Where are you stuck?
Place the file "sush" in the same folder as adb.exe and follow those commands from command prompt. You need to have root privileges to do this.
Thanks for all of your work!just put this on my to do list.
JuiceDefender doesn't cut it anymore.
Just to be on the safe side am I suppose to have screen on/off and droidwall-on.sh in tasker? Sometimes when using the phone from sleep, 3g or wifi doesn't work. I'll have to reboot to make it work. Any suggestions?
Sent from my LG-VM670 using Tapatalk
This is a stock Optimus V ROM and Kernel.What about when you run them through SL4A?
You need sush, otherwise SL4A can't run them as root. SL4A can't run anything as root by design. Try downloading sush again. Maybe it became corrupt while you were moving it into position the first time.
Also, which rom are you running? I've used this on almost all of the Froyo roms, but I haven't tried it on Gingerbread.
Here is an explanation of what is happening with this setup:
Tasker detects the screen turns on. It then notifies SL4A to run the screen-on script. SL4A runs the screen-on script. The screen-on script tells your system to run the droidwall-off script as root through sush. Droidwall-off behaves the same as droidwall and removes all the entries from the ip-tables.
FYI, droidwall-old stores the script in a different folder. If you installed old on top of the new droidwall, then the scripts you are copying over are just left over from the previous version. I think it is in the /data/data/com.googlecode.droidwall/cache folder or something like that.
I've been using this for a while now. It should work. Something is wrong with your setup, and I'm not sure what. Maybe you want to start from the beginning and re-download everything.
This is a stock Optimus V ROM and Kernel.
I think the problem is around my root'ing of the device. I had to improvise as I have only computers running Ubuntu.
The fact that DroidWall works at all must mean I was successful in root'ing. I installed Root Check to check my work and it reports, "Congratulations! You have root access1" On the Advanced check it had said I was missing /system/xbin/su and permission denied to /sbin/su.
I copied over su from SuperOneClick to /system/xbin and the first error went awy, but I still have the permission denied to /sbin/su (which is alot like the sush error).
What do you get when running the Advanced Root check?
Ran the Ginger Break, it did something as the reboot was much longer than usual, like after I did the root by hand on it. But afterwards, same problem.Hmmm, do you have superuser installed?
Try gingerbreak: GingerBreak.apk
It will do all the rooting stuff for you and install superuser. Then run su or sush once, and give root permission to it. Place the apk on your sdcard, install it with a file browser by double clicking it. Then run the app and select "root device". It will do everything for you and then reboot when it is done.
As far as the prerequisite of root'ing that I did from Ubuntu, this was the outline I followedAwesome! I'm glad it worked out. I'm going to bookmark your setup. That was clever. Security wise, you are probably safe. I doubt a virus is going to be written in hopes of catching the 12 people that have a similar setup in the world.
Since it uses the iptables, it only effects new connections. So what you experienced was normal. Make sure to keep droidwall on hand for when you install new apps. I suggest using a blacklist for screen on, and a whitelist for screen off. That way your new apps will function when the screen is on, unless you choose to block them, and the reverse will be true for screen off.
I also have a gscript script on hand that copies and renames the droidwall scripts for me. It has been very handy.
Juicedefender also has a setting where you can enable/disable an app's net access.
Based on the screen being on or off?