isDefaultActiveApp is called on every package. We can cache default
dialer and default sms package in a list, and check if the list
contains target package name.
Fixes: 140279638
Bug: 151233929
Test: manual, make RunSettingsLibRoboTests
Change-Id: I81f5ccb7aed1ebec797a21af6094971e05f456a7
(cherry picked from commit 19c2bbccfd)
CachedBluetoothDevice#getProfiles() only returns a
Collections.unmodifiableList which isn't thread safe. Use a copy in
BluetoothControllerImpl so we can avoid a CME
Test: atest SystemUITests
Bug: 146828136
Change-Id: I451a746836c67b8b82f26f4f39b5363ac5e0ea79
This allows callback classes to remove themselves or add additional
callbacks in response to state change dispatches.
Bug: 129060225
Bug: 144357642
Test: build and deploy, pair multiple devices, switch users
Change-Id: I8eed81bbc9c12321ec41b2491d006764e2e483d6
Merged-In: I8eed81bbc9c12321ec41b2491d006764e2e483d6
1. In AccessPoint#updateBestRssiInfo, if bestResult is available, cache if it’s transition mode at new variables.
2. Remove SECURITY_PSK_SAE_TRANSITION & SECURITY_OWE_TRANSITION since we will cache if an Wi-Fi AP is transition mode.
3. Enhance getSecurity(ScanResult result).
For a PSK/SAE transition mode ScanResult, return SAE.
For a open/OWE transition mode ScanResult, return OWE.
4. Enhance all AccessPoint#matches methods
5. Use enhanced AccessPoint#matches to replace AccessPoint#isKeyEqual
6. In WifiTracker#updateAccessPoints, it associates an AccessPoint with a configured WifiConfiguration
I. If an AccessPoint is PSK/SAE transition mode, update it with a configured network
of the same SSID and PSK/SAE security if it’s available. (SAE has higher priority).
II. If an AccessPoint is Open/OWE transition mode, update it with a configured network
of the same SSID and open/OWE security if it’s available. (OWE has higher priority).
Bug: 144320676
Bug: 144320649
Bug: 144325162
Bug: 144321574
Test: atest SettingsLibTests
manual: In Wi-Fi picker
1. Save a PSK network, click a PSK/SAE transition mode AP of the same SSID,
it should connects.
2. Save a SAE network, click a PSK/SAE transition mode AP of the same SSID,
it should connects.
3. For 1. and 2., the transition mode AP should show 'Saved'.
4. For 1. and 2., looking at saved network page, each saved network should
shows correct connection status of the transition mode AP.
Change-Id: Ida858af791bc60f0ccb11025901de2a79eacba3c
Merged-In: I9688f51f4a4b8e3d5c080fb0d0103abb4e3fd79b
Reason for revert: Incomplete fix that causes additional issues which were not anticipated earlier.
Change-Id: I383273509797ed95a7f9ece780ec52abb1341292
Merged-In: Iff36d5a10e6c8ee8978a5842af8f19efc10c0a91
Fix WPA3-Personal in transition mode issues. Current
solution will create an upgraded WPA3 connection if
there is a WPA2 saved network and AP is in transition
mode.
Bug: 143843364
Test: Manual tests
Test: atest com.android.server.wifi
Change-Id: Idadbd1d155ddd617e61063e64e186abec478f5ff
Merged-In: I53b278e846828198fb1953b075d86e16fac6d795
Provide a method to submit a Callable for execution in the shared
background thread pool.
Bug: 143434413
Test: manual, robotest
Change-Id: I149b5926f20acd0e43c4071cc35520c6bc50efef
Merged-In: I149b5926f20acd0e43c4071cc35520c6bc50efef
(cherry picked from commit ab21b8a838)
We had accidental usages of the PermissionChecker for cases where no
private data was provided to the app but the checkPermission API on
the latter also did blame data access on the app. The PermissionChecker
was designed to handle IPC calls and not for generic API checks.
To avoid future accidental incorrect PermissionChecker usages this
change renames the existing APIs of the latter to clearly indicate
that they should be used for data delivery and also adds sibling
methods for doing the same permission checks for preflight purposes.
Also the documentation is improved to furhter assist developers.
In addition, this change fixes accidental permission checker usages
that blame when they should not by using the new preflight flavor
of the permission check APIs.
Test:
atest com.android.settingslib.location.RecentLocationAppsTest
atest CtsPermissionTestCases
added: LocationAccessCheckTest#notificationOnlyForAccessesSinceFeatureWasEnabled
added: LocationAccessCheckTest#noNotificationIfFeatureDisabled
added: LocationAccessCheckTest#noNotificationIfBlamerNotSystemOrLocationProvider
added: LocationAccessCheckTest#testOpeningLocationSettingsDoesNotTriggerAccess
bug:141028068
Merged-In: I65c71569d0dd8a40bc6fecabb22c5373dd6e806e
Change-Id: I65c71569d0dd8a40bc6fecabb22c5373dd6e806e
one
When there's no users' choice to tell us whether to share their
phonebook information to the Bluetooth device, set the phonebook access
permission to ACCESS_REJECTED.
Bug: 138529441
Test: Manual test
Change-Id: Iefabeb731b941f09fe1272ac7b7cd2feba75c8df
Merged-In: Iefabeb731b941f09fe1272ac7b7cd2feba75c8df
(cherry picked from commit 810c6d2117)
On each WifiTracker scan, existing Passpoint AccessPoints are updated
by update(config) with a WifiConfiguration returned by the framework
and then updated with fresh scan results through setScanResults().
Since the Passpoint WifiConfigurations given to update(config) have
null SSID, the call to setScanResults() sets the config.SSID to the
SSID of the strongest scan result. However, update(config) also sets
AccessPoint.ssid to config.SSID, which means the UI may display a blank
SSID before the call to setScanResults() sets it to the correct SSID.
Thus, update(config) should not set AccessPoint.ssid to config.SSID if
the AccessPoint is for Passpoint.
Bug: 137282522
Test: manual - connect to Passpoint network, validate SSID in network
details page.
Change-Id: I2218c1217de3e4fe48e40114a3ea8ceab3d845f2
Bug: 135105735
Test: test app. Apply grouping and call the new API, to make sure
it returns correct values.
Change-Id: I99586976d3421d4b35be465201ee33cbb2dfd1d9
