1. Send PROXY_CHANGE_ACTION broadcast when any network's proxy changes,
not just the default network.
2. When a process is bound to a particular Network, update the proxy
system properties to those for the bound Network, and keep them
updated when PROXY_CHANGE_ACTION broadcasts are received.
3. Make Network.openConnection() use the proxy for the Network.
bug:17905627
bug:17420465
bug:18144582
(cherry-pick of https://android-review.googlesource.com/#/c/115170)
Change-Id: Ia2819985e6108a8c121e74c683a5646becfd0a97
Tune sampling periods:
- Lower minimum sample interval when in test mode.
- Add a check when sampling pss to make sure this is at least 1
second since the pss changed, to reduce the amount of bad
data (very small pss samples) that we see.
Change-Id: I624a7d0480f3f6b22d229744e028d13a2c7b0e89
This causes crashes on all devices that disable the BluetoothHeadset
service when disabling bluetooth and thereby trying to unbind all
services.
Bug: 18669882
Change-Id: I48978a1556ead967c848c5bd9f6e001d38754b8d
http://ag/261732 introduced an optimization where we only take
the activity screenshot if is is not the activity we took a
screenshot for last. This causes us to display a stale screenshot
for activities that change their display content (using fragments)
without going through the pause/resume cycle. It should be safe
to always take a screenshot when we are pausing since the code
path is only called once per pause/resume cycle.
Bug: 18682160
Change-Id: Ie5c43cfd806286808af4233c5917ae7071908ebb
(cherry picked from commit eacdf2ce04)
Previously the policy change would always re-enable the keyguard,
but that would break the current state. Instead, when the keyguard
is disabled, we need to recalculate the allow state immediately
and only re-enable it if necessary.
Bug: 18430385
Change-Id: Id9e701df2db765031e177c8bc8d3730cfb7f162a
Fixes a regression that prevents the user from being fully shutdown
after being stopped. Wasn't killing all user processes.
Bug: 7462778
Change-Id: Iee7231f7c8a167e8a61549b149294b2dbef071c1
If an accessibility service opts-in for the new window introspection APIs
when calling into a window for accessibility node infos we compute the
window's interactive region, i.e. the portion that is touchable and not
covered by other touchable windows, in roder to deterine whether these
nodes are visible, i.e. the user can interact with them. There was a bug
in the interactive region computation what we were not ignoring accessibility
overlay windows which are intended to not change what an accessibility
service can "see" and are put by such a service.
bug:18652374
Change-Id: I24ce54069087af9bc308e0c6a7b2aa6b952a6136
You can now do "adb shell dumpsys procstats --start-testing" to
enable high frequency pss sampling.
Also improved the low on RAM mem reporting to separate out RAM
from memtrack, in case the data we are getting from that is bad.
And fixed meminfo --oom to work correctly again.
Change-Id: I7af17eab110a82298bd7b0ce381f8fa5c96c1f6a
INSTALL_FAILED_UPDATE_INCOMPATIBLE is a better description of the
real underlying cause when signatures don't match.
Bug: 18413784
Change-Id: Ib81591df7d0d79f6725a4fa7300ae4e20958f004
