In this loop the continue statement skips over incrementing
dexPathIndex. In effect the classloader context that reported for a
given dex file may be incorrect (specifically in the situation when the
user loads a primary dex file and a secondary dex file in the same
ClassLoader)
Bug: 147089377
Test: atest com.android.server.pm.dex.DexManagerTests
Change-Id: I7d3df507787f758537625b702131a2f4f76190e6
* changes:
DO NOT MERGE Fix AppOpsServiceTest
DO NOT MERGE Don't throw exception in AppOpsManager.checkOp
DO NOT MERGE Remove unnecessary internal APIs.
DO NOT MERGE SetMode: Don't call into PM with AppOps lock held
* changes:
[SP09] Remove NetworkStatsService @hide usage in Tethering
[SP08] re-calculate interface quota when limit reached
[SP07] Remove reference of NetworkStatsService in IpServer
[SP06.1] Add UPDATE_DEVICE_STATS permission to Tethering
[SP06] Use system API to communicate with NSS in OffloadController
Use Context#getSystemService to get network stack binder
This method is used by Telephony Module for permission checking.
Test: manual; cts; unit tests in other CLs
Bug: 145688189
Change-Id: Ie706e05e6a69e570331c1fe08a8df9677e0d9c8a
Merged-In: Ie706e05e6a69e570331c1fe08a8df9677e0d9c8a
Merged-In: If3adcd17916be2e81497061120d1f350bfb8026d
(cherry picked from commit 145294168f)
Rename CACHE_FILTER_* constants to SCORE_FILTER_*
and expose them as @SystemApi so they can be used
by the Wifi module.
Bug: 135998869
Test: compiles
Change-Id: I9eab2e84d0b00fada7629a104566c1099f8b1288
Merged-In: I9eab2e84d0b00fada7629a104566c1099f8b1288
In Q we handled the case where the op does not match the package name by
returning the default state. NoteOp and StartOp returned errored.
Fix up these scenarios.
Test: - atest CtsAppOpsTestCases
- backported new test to Q to verify the behavior is the same in Q
and master
Bug: 132885449
Bug: 146463528
Bug: 146590200
Bug: 147649036
Change-Id: I5b94e92af759580f2d2644ece49f159bd006b31c
StringNetworkSpecifier is widely used to specify subscription id for
the NetworkRequest. The raw string field introduce ambiguity and leave
large space for bugs. With TelephonyNetworkSpecifer, we are able to
settle down the type and value of the fields (although currently only
one) and introduce validation to detect the bug in the beginning.
Bug: 145993724
Test: atest FrameworksNetTests FrameworksTelephonyTests &
make offline-sdk-docs
Change-Id: Iefbad9b1deb3de2c0b262d9ce5ae0704a50d08a6
Existing annotations in libcore/ and frameworks/ will deleted after the migration. This also means that any java library that compiles @UnsupportedAppUsage requires a direct dependency on "unsupportedappusage" java_library.
Bug: 145132366
Test: m && diff unsupportedappusage_index.csv \
git diff HEAD^ HEAD | grep '^[+-][^+-]' | grep -v '.import'
Merged-In: I853372f3c6fef905553bb31be4f1bb48df735f7a
Change-Id: I853372f3c6fef905553bb31be4f1bb48df735f7a
When data saver enabled, tethering would be OFF.
Currently settings would not allow user to turning tethering back.
After aosp/1181583 is merged, user can turn tethering back without
turning data saver OFF.
Bug: 145711175
Bug: 142374233
Test: atest TetheringTests
OFF/ON tethering when data saver ON
Change-Id: I59e662ba771a563f5f1766ba29e05246b8280220
Some providers might hit the limit reached event prior to
others. Thus, re-calculate and update interface quota for
every provider is needed.
This change also removes the lock that held by NPMS while
requesting NSS force update, which seems unnecessary and
might cause potential deadlock in future.
Test: atest NetworkStatsServiceTest
Test: atest NetworkPolicyManagerServiceTest
Bug: 130855321
Change-Id: I84a08ecfb14c61023fa9f1c98af73d3ee90acef6
In the setmode paths do not call into package manager with the app-ops
lock held. Otherwise we might get dead-locks then someone calls into
app-ops manager with the package manager lock held.
Test: Booted and saw no errors from the changed code
Bug: 124731615
Bug: 146463528
Bug: 146590200
Bug: 147649036
Change-Id: If074bed1bd246a81791a7d9fd656f42f1a755495
(cherry picked from commit ec142a52fe)
Device fresh rate (60.0024) is larger than USER_SETTING_PEAK_REFRESH_RATE(60)
The difference is more than EPSILON (0.001), which will make the mode invalid the cts-on-gsi case : android.display.cts.DisplayTest#testModeSwitch will fail
Change-Id: Ie8adaf2d00280560111486d63ff774f47c2eace2
