So we can test system APIs in cts.
Bug: 201017875
Test: atest android.settings.cts.SettingsMultiPaneDeepLinkTest
Change-Id: I8bedd571a4d3385042533fe7dd5ded250894d14a
Merged-In: I8bedd571a4d3385042533fe7dd5ded250894d14a
It's unnecessary to throw exception when failed to query call
log in PeopleService. So catch this exception to avoid system
server crash.
Bug: 204923224
Test: PeopleServiceTest
Change-Id: I77ee31ff456455721c3401f36d4a79390db2f9b5
SignalStrengthUpdateRequest is designed to not allow null nor empty
signal thresholds for public apps.
To support system privileged app (Bluetooth) which is only interested
in requiring to report system thresholds while idle. An exemption was
made (aosp/1569861) which was to allow empty thresholds but the null
thresholds was also allowed by mistake. This will cause Bluetooth
crash if no signal thresholds are set.
To fix the issue, we only allow Bluetooth to set EMPTY thresholds
but not null one.
Bug: 205585585
Test: atest SignalStrengthUpdateRequestTest
Change-Id: I245ecb87ab807a6005b32fa320c8820a2c0b1a9e
If after a factory reset, APEX modules are updated, duplicate package
names are returned from the API - factory packages are added first and
then inactive factory packages leading to duplication.
After updating APEX modules, inactive factory packages would always be a
subset of factory packages. The fix adds inactive packages only if there
was no factory reset done.
Bug: 200519752
Bug: 200120056
Test: atest 'PackageManagerTest#testGetInstalledPackages_WithFactoryFlag_ContainsNoDuplicates'
Change-Id: I5b5469fc6879bbeee4dc2ea47b2046ab011a65ce
Merged-In: I5b5469fc6879bbeee4dc2ea47b2046ab011a65ce
Port concept is introduced to support MEP feature. Refactoring UiccController, UiccCard, and
UiccProfile to add UiccPort between UiccCard and UiccProfile. Most of the UiccCard functioning is
moved to UiccPort.
Added default port index value of uicc card.
Bug: 199559346
Test: Manual
Change-Id: Iaf6af6d5573976a6f85a36570900fb03778e1909
Merged-In: Iaf6af6d5573976a6f85a36570900fb03778e1909
This matches behaviour described in:
https://developer.android.com/training/articles/perf-jni#extended-checking
All output from CheckJNI state was disabled as part of quietening
logspam, but now we log a message only if CheckJNI is
enabled. CheckJNI is off by default and only used as a developer
correctness tool.
Bug: N/A
Test: adb root; adb shell stop; \
adb shell setprop dalvik.vm.checkjni 1; \
adb shell start; adb logcat -d | grep CheckJNI
Change-Id: I93bc2d097a8769b7768c633b705b29fc1aac634a
Bug: 197723951
Bug: 200295570
Test: run with a null HbmProvider on a UDFPS device
Change-Id: Ia184978d453dc449a6f9f8882cf2b4205c14c1d6
Merged-In: Id89552d3228b4770331e0eda558f0f97101ad8ca
registerImsStateCallback and unregisterImsStateCallback are
added to ImsMmTelManager, ImsRcsManager, and SipDelegateManager.
Those are used to receive updates about the connection state
of the underlying ImsService.
Bug: 178016400
Test: atest ImsStateCallbackTest
Change-Id: If547ce637725d4f98942b0b554187a0ba91f60de
Merged-In: If547ce637725d4f98942b0b554187a0ba91f60de
Merged-In: I3ac14cc3bcb28f5f966a1b3c215727784527e475
Change to using ISO 8601 duration formatting for LocalLog local
timestamps, which makes it consistent with other time / time zone
detection dumpsys for easier comparison.
LocalLog is used by NetworkStack code as a standalone library, so
therefore has to depend on public SDK APIs, hence the use of Duration.
The local timestamp logging mode is only currently used for time / time
zone detection, which is low-frequency logging.
Bug: 204855374
Test: atest core/tests/coretests/src/android/util/LocalLogTest.java
Change-Id: Idce0d39c59670facdf48deca852b862ff0d71991
This commit switches the ordering of ReferenceWithHistory.dump() so the oldest
entries are output first followed by newer ones, i.e. traditional log ordering.
Tests are updated to confirm ReferenceWithHistory dump output.
Bug: 204855374
Test: atest services/tests/servicestests/src/com/android/server/timedetector/ReferenceWithHistoryTest.java
Test: adb shell dumpsys time_zone_detector
Change-Id: Ia098492fc6056fdbb8ef9d8ca1128bf0f51d113b
Previously trace processing's threading is handled on the native side
while the report creation's threading is on the framework side. Move
them all to the frameworks side to reduce complexity.
Test: build
Bug: 183487233
Change-Id: I5dd405b7a73e5be9e0141c20c6c100acbc6defa9
