id 1000+root must be whitelisted on Android 5.0/lollipop

[GoogleCodeExporter]

This is perhaps more a question than a bug. It appears that on lollipop, 
Android uses a process that runs as app ID 1000 to detect if the network is 
online, and won't enable the network connection unless it can do so.  This is a 
departure from Android 2.x (I never owned a phone with 4.x so can't compare 
there).  If I leave 1000 and root applications blocked in DroidWall, no other 
app can communicate either, and I get the white exclamation point indicating 
bad network connection.

Is there a way around this new network detection behavior?  I think it is part 
of lollipop's "don't use this network unless we know it is good" feature, but I 
don't like because I now have to let "Android System" run free with data usage.

What version of the product are you using? On what operating system?
DroidWall 1.5.7
Android 5.0 stock rooted on Moto X (2014/2nd gen)

Original issue reported on code.google.com by [email protected] on 8 Dec 2014 at 11:36

[GoogleCodeExporter]

After further investigation, only root needs to be unblocked, OR log enabled 
(which also adds a rule to allow DNS queries).  Because on Lollipop, DNS 
requests are all made as uid 0 instead of the app, so it makes it look like 
apps can't communicate with the data network when actually they just can't do 
DNS lookups.

uid 1000 is responsible for detecting the network connection, but it does not 
need to be unblocked for applications to connect to the data network.  However, 
the connection indicator will show "!" instead of the type of connection (E, H, 
LTE, etc), except in the settings pulldown where it will show both "!" and the 
type of connection.

Original comment by [email protected] on 16 Feb 2015 at 5:16