Play Services Network Requests on Android O Builds

[securesearch]

Noticed that alongside the Google connectivity check that was also present in builds based on Android N, Android O builds also attempt to connect to play.googleapis.com every time a network interface is enabled. Haven't narrowed down the process making the requests, but just seems unnecessary when CopperheadOS does not use or need Play services.

[xbtc-im]

that's in frameworks/base/services/core/java/com/android/server/connectivity/NetworkMonitor.java
private static final String DEFAULT_OTHER_FALLBACK_URLS =
"http://play.googleapis.com/generate_204";

all connectivitycheck servers are there ... they can be changed from source or maybe an user configurable option could be added at some point ...

[xbtc-im]

that's in frameworks/base/services/core/java/com/android/server/connectivity/NetworkMonitor.java
private static final String DEFAULT_OTHER_FALLBACK_URLS =
"http://play.googleapis.com/generate_204";

all connectivitycheck servers are there ... they can be changed from source or maybe an user configurable option could be added at some point ...

[thestinger]

https://copperhead.co/android/docs/usage_guide#default-connections-made-by-copperheados

[thestinger]

https://copperhead.co/android/docs/usage_guide#default-connections-made-by-copperheados

[thestinger]

@xbtc-im They are user configurable via adb shell but I doubt you want to point them at something else, it wouldn't improve privacy. It would only make the device behave uniquely instead of fetching the same URLs as billions of other devices. They are empty GET requests.

[thestinger]

@xbtc-im They are user configurable via adb shell but I doubt you want to point them at something else, it wouldn't improve privacy. It would only make the device behave uniquely instead of fetching the same URLs as billions of other devices. They are empty GET requests.

[thestinger]

They also need to return a 204 status, not something else. It detects captive portals from the captive portal sending a 200 request, etc. instead.

[thestinger]

They also need to return a 204 status, not something else. It detects captive portals from the captive portal sending a 200 request, etc. instead.

[xbtc-im]

Yes, it expects a 204 No Content. As far as i know captive portal detection can even be disabled via adb shell, but it can prove useful for captive portals, splash pages, spent data plans, etc. It works as intended.

[xbtc-im]

Yes, it expects a 204 No Content. As far as i know captive portal detection can even be disabled via adb shell, but it can prove useful for captive portals, splash pages, spent data plans, etc. It works as intended.

[thestinger]

The internet connectivity checking is also used to fall back to other networks when one isn't providing working internet access.

[thestinger]

The internet connectivity checking is also used to fall back to other networks when one isn't providing working internet access.