Adds new proto message type to record PNO scan stats in each device
mobility state.
Bug:120097108
Test: compiles, frameworks/opt/net/wifi/tests/wifitests/runtests.sh
Change-Id: I67473a402a2e58d8aec36801667234f925339453
* changes:
[automerger skipped] Merge changes from topic "move sched_policy functions" am: 2a2b4eec35 am: ef974c1a36 am: 6cc4c4ff65 -s ours am skip reason: change_id Ia8bc5b447efa568fd1c822746919fa1496cc42a6 with SHA1 3b3a1c8622 is in history
[automerger skipped] Add libprocessgroup dependency and fix sched_policy include am: 09a29e161f am: 2d74e0de16 am: d74cebf0d6 -s ours am skip reason: change_id I98a7a6f9a9d6be8595b3604fb73dafc05412c482 with SHA1 e44332655b is in history
Add new field to LocationRequest that allows clients to ignore location
settings, and validate this field. Support returning location to clients
with this field even when location settings are turned off.
Bug: 118883513
Test: Manual + CTS
Change-Id: Idf4449ae7c20d03f42410936c35fadc602e83d11
am: 6cc4c4ff65 -s ours
am skip reason: change_id Ia8bc5b447efa568fd1c822746919fa1496cc42a6 with SHA1 3b3a1c8622 is in history
Change-Id: I8bcd6014e39baef6eb45b352f045029abb42bc92
am: d74cebf0d6 -s ours
am skip reason: change_id I98a7a6f9a9d6be8595b3604fb73dafc05412c482 with SHA1 e44332655b is in history
Change-Id: I131f72ace70c146dad073feb7032101ab8b6a031
Upgrade LOCATION_MODE setting from previous LOCATION_PROVIDERS_ALLOWED
setting. This should remove the necessity for fallback behavior in
LocationManagerService.
Test: manually
Change-Id: I24a546d91906fcf00c41b2e5191bf75f27f3a759
This is needed if internal component wants to listen to
precise call state change.
Bug: 117980553
Test: unittest
Change-Id: Id5a60519cbf1d724f939fc10b1f03cccfe5c1b5c
Test Harness Mode is a feature for device farms that want to wipe
their devices after each test run. It stores the ADB keys in the
persistent partition (used for Factory Reset Protection) then performs
a factory reset by broadcasting the MASTER_CLEAR intent.
Upon rebooting, the Setup Wizard is skipped, and a few settings are set:
* Package Verifier is disabled
* Stay Awake While Charging is enabled
* OTA Updates are disabled
* Auto-Sync for accounts is disabled
Other apps may configure themselves differently in Test Harness Mode by
checking ActivityManager.isRunningInUserTestHarness()
Bug: 80137798
Test: make && fastboot flashall -w
Test: adb shell cmd testharness enable
Change-Id: I91285c056666e36ad0caf778bffc140a0656fcfa
am: 25696ef82e -s ours
am skip reason: change_id I7b63d3e117a1bd1eb17dab8e1a7b1dfec1a8abe8 with SHA1 fc33a42309 is in history
Change-Id: I52a07a554c79b628c776ec23394ca9266230ac4e
When callers are inserting or updating raw "_data" paths, we need to
sanity check them to make sure they're not "crossing the streams"
between storage devices. For example, it would be really broken to
insert a file on the SD card into the "internal" storage volume.
This also enforces that callers don't "cross the streams" between
multiple storage volumes on devices that support them, since
otherwise they'd end up with very confusing behavior, such as
the same underlying file being inserted into multiple databases.
Also, the "internal" storage volume should really only be used for
common media (such as ringtones), and it shouldn't be allowed to
point into private app data directories, since MODE_WORLD_READABLE
has been deprecated for many years now.
Bug: 117932814
Test: atest MediaProviderTests
Test: atest cts/tests/tests/media/src/android/media/cts/MediaScanner*
Test: atest cts/tests/tests/provider/src/android/provider/cts/MediaStore*
Change-Id: I267eacd45bbd270b8ce9b28de9d6e209f780f31a
If a non-persistent service is being restarted and it was killed due to
low memory previously, instead of restarting the service in one second,
we now restart it based on its last known oom_adj value. The backoff
logic of consistent restarts remains the same.
Additionally, when the service is due to restart, if the memory pressure
is still considered to be critical, the new logic will further delay the
service restart.
Initial test results: # of restarts dropped by 40-50% on average with
the optimized logic when the memory pressure was gradually increased.
Tested manually via memeater. Increased the memory pressure by 500 mb
at a time via the following command: adb shell memeater 500
On a 4gb device, no significant restarts were noticed when memory
pressure was increased by 2gb in total. When increased by 3gb in total,
services started to restart and the above results were observed via
the logged output over a 5 min period.
Bug: 79848281
Test: manually (steps listed above)
Change-Id: Idcd1300882321c6033e569736150a8bf7889678b
