This CL included the follow change:
1. Change getPreferredNetworkTypeBitmap to
getPreferredNetworkTypeBitmask [b/126552419]
2. Change setPreferredNetworkTypeBitmap to
setPreferredNetworkTypeBitmask [b/126552419]
3. Add @IntRange annonation to CellIdentityNr.getNrarfcn() [b/126552419]
4. In javadoc, explain the acronym NR to say: (New Radio 5G)
[b/126552559]
5. Mark CellInfoNr.getCellSignalStrength and CellInfoNr.getCellIdentity
as @NonNull [b/126699572]
6. Mark CellIdentityNr.getMncString() and CellIdentityNr.getMccString()
as @Nullable [b/126702744]
Bug: 126552419
Bug: 126552559
Bug: 126699572
Bug: 126702744
Test: build
Merged-In: I133075a3688c3fa7550c8a2f43bc13d8b25999b2
Change-Id: I133075a3688c3fa7550c8a2f43bc13d8b25999b2
The GNSS capabilities in the gnss@2.0 HAL have been refactored
(b/128028791, b/127434062, b/128309220). The sub-HAL capabilities
in the top level IGnssCallback.hal have been moved into their
respective sub-HALs. Consequently, the getGnssCapabilities()
method in LocationManagerService is hereby modified to include
the capabilities from all sub-HALs and the top level HAL.
A new GnssCapabilities class needs to be added so that we don't
expose the implementation details of the capabilities (a Java
int bitmask of capability flags) to the LocationManager client.
Bug: 128913861
Test: TBD
Change-Id: I5ed90332c7c0e783de771f573a58f79d1d6d89ff
The CL updates Magnifier#getPosition() and Magnifier#getSourcePosition()
to return coordinates relative to the main application window, rather
than relative to the surface backing it. Working with window relative
coordinates is the better approach for public APIs. The CL also makes
View#getLocationInSurface public. Magnifier CTS tests still need it,
when testing MAX_IN_SURFACE behavior.
Bug: 124012182
Test: atest CtsWidgetTestCases:android.widget.cts.MagnifierTest
Change-Id: I684f27aa466e0390c7801b616331f4682784c423
There was an optimized code path that is hit if the op
has not been accessed that does not write the uid state
information which did not add the closing tag which
resulted in producing a malformed XML.
Test: atest android.app.appops.cts.AppOpsTest#testNonHistoricalStatePersistence
bug:128872367
Change-Id: Iaddcce09b41f3e124e1838b65731d8dac9ca64e3
This is important when deciding whether or not to create
a hidden app detail activity or within AppInfo in Settings
application.
Bug: 119440359
Bug: 124556507
Test: build and test with Settings app
Change-Id: I02324e5c0a146f4df4cc4a5b1b62059bc9153d23
This reverts commit 821f43aa64.
Reason for revert: better fit:
- restrict the Package Manager feature flags to features for which the app developer would need to "target"
- typically hardware types should be mutually exclusive to each other
Bug: 124406307
Test: make checkbuild
Change-Id: Ie247a21eb8bbc83efad833ca8db675fd11e7ea4e
Per API council feedback, we are making changes to include only the
namespace in the system API defined in DeviceConfig.java. Strings which
define property names should be defined in code local to the feature
instead.
Bug: 126411407
Test: atest FrameworksCoreTests:DeviceConfigTest
Change-Id: I751254a183c8a9d150022d964539fb997c1d89fa
Expose getOverlayInfo API on OMS in order to
implement additional AppInfo UI for resource
overlay in Settings app.
Bug: 124556507
Bug: 124540315
Test: make RunSettingsRoboTests ROBOTEST_FILTER=AppButtonsPreferenceControllerTest
Change-Id: Ib2cc257fe628e9cc855047cce7ed81a9786b2635
