NetworkPolicyManagerService (NPMS) manages 4 type of network restriction
when apps are running on background:
- Data Saver Mode (data usage restriction on metered-networks)
- Battery Saver Mode (power restriction on all networks)
- Doze Mode (power restriction on all networks)
- App Idle (power restriction on all networks)
These restrictions affects 2 parts of the system:
- Internal framework state on NPMS which is propagated to other internal
classes.
- External firewall rules (managed by netd).
Although each of the power-related restrictions have their own external firewall
rules, internally apps are whitelisted to them through the same
whitelist, and the current code is only updating the internal state (and
notifying the internal listeners) when Battery Saver Mode is on.
As a consequence of this problem, there are scenarios where an app
correctly does not have internet access (because the firewall rules are
properly set), but the NetworkInfo state returns the wrong state (like
CONNECTED / CONNECTED).
This CL fixes this problem by splitting the power-related logic from
updateRulesForRestrictBackgroundLocked() into its own
method (updateRulesForPowerRestrictionsLocked()), and making sure such
method is called whenever the firewall rules are updated.
Externally to this change, the CTS tests were also improved to verify
the apps get the proper connection state; it can be verified by running:
cts-tradefed run commandAndExit cts -m CtsHostsideNetworkTests \
-t com.android.cts.net.HostsideRestrictBackgroundNetworkTests
BUG: 28521946
Change-Id: Id5187eb7a59c549ef30e2b17627ae2d734afa789
We are notifying windows of resize as the frame moves (even though the
size does not change) during the pinned animation, confusing and
upsetting the client. We do want to notify it of the one resize
at the beginning or end of the animation, so we can't just block
reportResized on bounds animating. Luckily the other area that adds
windows to reportResized (Task) is smart enough to only do so if the
size has actually changed and not just movement, so we let those reports
go through and block ones initiating from here (which doesn't perform
a check that the size has actually changed).
Bug: 28559097
Change-Id: If1f983e7cc875175ce1d098c385478a9922dea67
am: 18e9f13b24
* commit '18e9f13b24867fb4a41391c5512376db413449a8':
Don't disrupt a11y state when user is unlocked.
Change-Id: Ic5ad0d452e5296edecec98bdfc08b6ea8ad3c9da
Adding building for billions guide to Distribute>Essentials section
covering content on building for low-bandwidth and low-cost.
Bug: 27643355
Change-Id: Icb5089fe5528265f4e00b9b9e390a6743c691549
(cherry picked from commit a9884af1e6)
The reported that:
- Name should be Koni_c_a Minolta
- kmkmkm should not be used as a mDNS identifier
Change-Id: I1ab1910f9a54a396c3bfa109266f6e805349d036
Otherwise the following can happen:
- The progressController is _not_ running and we are running through
an update.
- Then onUpdateCompleted is called which cancels the not running
progressController. This then reset whatever state was previously
stored as mPreviousState leaving the PrintActivity in a weird state.
Fixes: 27945565
Change-Id: Id46b8853ba634634198a74921c8a1790c435678c
am: 3f84c5cb34
* commit '3f84c5cb34cf15ad7c324ff9063f3f5850682791':
Adding the sdk_vars centralized file back to fix the ndk download page links
Change-Id: I6b8e6a3d00d6aad1b049978374c34a7e66d1396f
am: 9b22357c09
* commit '9b22357c098963fb791ee86434b31fab0d8523d2':
Adding the sdk_vars centralized file back to fix the ndk download page links
Change-Id: I69362b0be69702e2be57873254ef6d4599dc16c6
am: 220f09fb4f
* commit '220f09fb4f6509bec1c344dda542fe3fd04cd997':
Adding the sdk_vars centralized file back to fix the ndk download page links
Change-Id: I92dc8597a28eacf4d3766ee08473d56ab0e2c006
am: 77e85d32d6
* commit '77e85d32d61ce3f0e356a789b8d2dcd907913c1b':
Adding the sdk_vars centralized file back to fix the ndk download page links
Change-Id: Ib9d0ef5df501970bbca82b6ee59fb8e4c1959df0
