ukanth/afwall#122: Fix non-escaped apostrophies in strings.xml
ukanth/afwall#122: Fix incorrect preference defaults
ukanth/afwall#122: Fix summary on color picker preference
ukanth/afwall#4: Add new (Tethering) special uid to create dnsmasq DHCP + DNS rules
ukanth/afwall#4: Use new addRuleForUser() helper to simplify dhcp/wifi code
ukanth/afwall#124: Fix inconsistent coloring on special apps
ukanth/afwall#140: API: Check return status from SU.run()

If SU.run() returns null, it means the command failed.  It is incorrect
to report exitCode == 0 in this case.
ukanth/afwall#140: libsuperuser: Hack up library to check exit status

Surprisingly, this isn't supported in the stock library.  A better long
term solution would be to ask the maintainer to fix the API.
ukanth/afwall#142: Remove StartupService.java

As far as I can tell, nobody even tries to start this service, so the
code serves no apparent purpose.
ukanth/afwall#142: Fix a couple of warnings in the libraries
ukanth/afwall#142: Rename "firstseem" to "firstseen"
ukanth/afwall#141: UI: Add new LAN icon
ukanth/afwall#141: UI: Add LAN control items to UI and preferences

Unfortunately this is largely a copy&paste effort...
ukanth/afwall#141: Introduce new InterfaceTracker class to watch active interfaces

Use the ConnectivityChangeReceiver for more than just roaming: any time
the system notifies us that the network configuration has changed, see if
any of the parameters relevant to AFWall+ have changed.  If so,
recalculate and reapply the firewall rules.

This should also address ukanth/afwall#134 (OUTPUT rules left wide open
after tethering is disabled).
ukanth/afwall#141: API: Use common interface lists from InterfaceTracker.java
ukanth/afwall#142: API: Make 'logcat -s "AFWall:*"' work
ukanth/afwall#141: API: Set up firewall rules for LAN access
ukanth/afwall#141: Update TODO list re: LAN support
ukanth/afwall#142: MainActivity: Sort list based on all checkboxes, not just wifi+3G
ukanth/afwall#141: Move interface change handling into BackgroundIntentService

Applying new rules directly from ConnectivityChangeReceiver (as was done
for roam change events in the past) may have been a cause of UI
responsiveness problems.  This commit represents the first steps toward
centralizing the apply*IptablesRules operations in
BackgroundIntentService, which will serialize the requests.