Closed GoogleCodeExporter closed 8 years ago
Please clear DroidWall log, try to access/send an MMS and check the log again.
What do you see in it?
Note that you need to reboot your phone after uninstalling DroidWall to
completely purge any remaining iptables rules - no need to Factory reset.
Original comment by rodrigo...@gmail.com
on 23 Nov 2010 at 3:20
The reason I did a factory reset was even after uninstalling and rebooting
multiple times, I still had no MMS. Just after restoring, my MMS was fine. I
will try to test this out later today and post the results.....
Original comment by jeremy.m...@gmail.com
on 24 Nov 2010 at 1:51
Are you sure you didn't install any other application that could possibly block
the MMS (such as APNdroid or similar)?
If you uninstall DroidWall and reboot, there is no way it could have affected
any kind of connection, since it just uses iptables rules, and those rules are
not persistent (they go away on reboot).
Original comment by rodrigo...@gmail.com
on 24 Nov 2010 at 2:01
Just so I know the correct procedure, would you like for me to communicate
with you directly in this email thread or would you like for me to continue
to post on google code......?
Original comment by jeremy.m...@gmail.com
on 24 Nov 2010 at 2:05
Please use the google code tracker, just to keep a history and knowledge base.
Anyway, google detects the e-mail thread and adds comments here in the issue
tracker.
Original comment by rodrigo...@gmail.com
on 24 Nov 2010 at 2:31
Here's the deal. I have restored again but this time from SPrecovery (I know
you don't believe that my MMS doesn't work and I understand why it should but
it didn't). After doing a full restore with SPrecovery, Droid Wall seems to be
operating correctly. After the last restore, I couldn't even apply rules
without getting "Error applying iptables rules. Exit code:1". I will continue
to monitor and report back if it happens again. I wonder if something was
applied back to my phone with Google's cloud restore.....
Original comment by jeremy.m...@gmail.com
on 24 Nov 2010 at 2:32
Glad to know it is working now. This kind of weird things happens sometimes on
Android, and it is hard to track down the exact cause.
I'm closing this issue, but feel free to comment here again if necessary an I
will re-open it.
Original comment by rodrigo...@gmail.com
on 24 Nov 2010 at 3:59
Original issue reported on code.google.com by
jeremy.m...@gmail.com
on 23 Nov 2010 at 2:10