Remove the vestigial llndk_library and replace it with properties
in the llndk clause of the implementation cc_library.
Bug: 170784825
Test: m checkbuild
Test: compare out/soong/build.ninja
Change-Id: I960d7592fc71482e547f3617d0e55503c36cb63a
In #dumpQueries, it uses appId as UID. This results in that it only
queries for appId on user 0. If the given appId is only installed
on the other user, we would fail to get the package name.
Bug: 165901712
Test: manually install an application on the secondary user, and use
'dumpsys package queries' to check whether '[app id <AID> not
installed]'(previous '[unknown app id <AID>]') still exists.
Change-Id: I783aec7f8b52099519365b75acddffe59dd50003
With this, we don't need to add the whole no cutout packages every time
when a new device that need the emulations.
All we need to do is just to update the device_xxx.mk
Bug: 186177228
Test: make
Change-Id: Ib244dc4be789a58fe66a0d2bc9b54f31031bfeec
Address API review feedback to:
- Rename NetworkAgent#setTeardownDelayMs to
NetworkAgent#setTeardownDelayMillis
- Use getters instead of fields in VpnTransportInfo
- Rename registerDefaultNetworkCallbackAsUid to
registerDefaultNetworkCallbackForUid in ConnectiivityManager
Bug: 183972850
Bug: 185246410
Fix: 184735863
Test: make update-api
Test: atest FrameworksNetTests
Test: atest CtsNetTestCasesLatestSdk
Change-Id: I5e8c4bed8bda40d507afa894c359b5e24ee5d868
Merged-In: I5e8c4bed8bda40d507afa894c359b5e24ee5d868
It is possible for a media session to be destroyed without updating the
playback state or removing the notification, in which case the
controller will no longer be valid. So we can treat this like
resumption, and re-register the controller and re-activate the controls
if we later get an event where the media is playing.
Fixes: 185899440
Test: MediaTimeoutListenerTest
Change-Id: If8b8922b436261ccf703ee9e1e3c0294171a6c2e
Migrate resource usage to the connectivity resource package.
For framework resources that have known overlays, keep a fallback until
the overlays can be migrated.
Bug: 182125649
Test: atest FrameworksNetTests
Merged-In: I778d94a5aac0c4e20e78b1ba3a002495c17a38a0
(clean cherry-pick)
Change-Id: I778d94a5aac0c4e20e78b1ba3a002495c17a38a0
clients of fingerprint sensor state changes
Implements FingerprintStateCallback class to receive notifications of
changes in fingerprint state, and updates ServiceProvider method
signatures and Fingerprint21 accordingly to use this callback type for
authentication, enrollment, and other side fps events. Also defines
FingerprintStateListener class to forward state changes in
fingerprint-related events from FingerprintService to the
SideFpsEventHandler, which defines logic for interactions
between power button state and side fps state.
Test: adb shell dumpsys fingerprint
Bug: 183997671
Change-Id: I9a44e2f31648590c0d0d4d065b68c39c9f204051
Per-app APIs in ConnectivityService will now have their fallback
request which tracks the system default be of type TRACK_DEFAULT
as opposed to REQUEST. Existing tests which expect this fallback request
to be sent to network factories need to be updated to validate this
change.
Bug: 180452284
Bug: 176494815
Test: atest FrameworksNetTests
Change-Id: I5125755b3ed1ec535494e2d7a48c0860710ed056
sensor.
DeviceStateProviderImpl would thrown an exception when constructed if
the config it is based on required the presence of a Sensor that did not
exist. This changes the provider to ignore states with conditions that
have unknown sensors. If there are no states with known conditions it
defaults to the state with the lowest identifier.
Fixes: 186166148
Test: atest DeviceStateProviderImplTest
Change-Id: Iec73e33e2b464680fb9404863d11a26e9643248b