From d2f1ca8c27871b2b2d2cf37da138a2d3723375c8 Mon Sep 17 00:00:00 2001
From: Luis Hector Chavez <lhchavez@google.com>
Date: Wed, 15 Aug 2018 07:17:03 -0700
Subject: [PATCH] Whitelist com.android.proxyhandler for power

There are some scenarios under which com.android.proxyhandler is
considered by the framework as never being launched (e.g. if a PAC proxy
is added after a long wait time after an upgrade), which makes all of
its network traffic to be blackholed, due to it being subjected to the
fw_standby firewall chain. Given that all of the outgoing packets from
this app are being dropped, whenever Chrome WebView (or most other apps)
uses a PAC proxy for its networking, it is completely unable to initiate
outgoing connections.

This change whitelists com.android.proxyhandler so that this does not
happen.

Bug: 110762695
Test: dumpsys usagestats' | grep proxy
      ...
      package=com.android.proxyhandler u=0 bucket=5 reason=d ... idle=n

Change-Id: I9e4debc876cbdd2f6ba35928faff8c0beca77ae1
---
 data/etc/platform.xml | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/data/etc/platform.xml b/data/etc/platform.xml
index b3f05dc9fc98d..f467eef08824c 100644
--- a/data/etc/platform.xml
+++ b/data/etc/platform.xml
@@ -204,6 +204,11 @@
     <allow-in-power-save-except-idle package="com.android.providers.calendar" />
     <allow-in-power-save-except-idle package="com.android.providers.contacts" />
 
+    <!-- The PAC proxy process must have network access, otherwise no app will
+         be able to connect to the internet when such a proxy is in use, since
+         all outgoing connections originate from this app. -->
+    <allow-in-power-save-except-idle package="com.android.proxyhandler" />
+
     <!-- These are the packages that are white-listed to be able to run as system user -->
     <system-user-whitelisted-app package="com.android.settings" />