Provide a specifc notification to let users know that device
has no internet is because it really doesn't have internet access
or it's caused by private DNS resolution failed.
Bug: 113242081
Test: atest FrameworksNetTests
Change-Id: I710c88a4742f5fd56c39fc797d7fa3ad36dba553
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
Change-Id: I89f4add79a55c3c8d6fbe8d57decaa78fe12f0f9
Merged-In: I65c71569d0dd8a40bc6fecabb22c5373dd6e806e
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
Change-Id: I4a74d4906f92e323fbd30b9b25011129895afc9a
Merged-In: I89f4add79a55c3c8d6fbe8d57decaa78fe12f0f9
Merged-In: I65c71569d0dd8a40bc6fecabb22c5373dd6e806e
The libcore.timezone APIs may form the basis for some
new SystemApis. Before starting that process the API
surface is being rationalized to establish the core
use cases.
Test: Treehugger
Bug: 139091367
Change-Id: Ib615976fae76ceb98873a33e1e995542e691c9d0
Merged-In: Ib615976fae76ceb98873a33e1e995542e691c9d0
(cherry picked from commit babab5cd6a)
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
Use old API to be consistent with NetworkPolicyManagerService
Bug: 135105735
Test: RunSettingsLibRoboTests & Manual test
Change-Id: I5d04cfd962c3d09cac7d33a97f847771074ab258
HidHostService allow to connect when priority is PRIORITY_UNDEFINED.
HidProfile should return ture when priority is PRIORITY_UNDEFINED.
Otherwise, the "Input device" toggle in off state when HID device
connected.
Bug: 132456322
Test: manual
Change-Id: Id7bae694c57aec17e019d591c0a677e3cb64f845
- Use config resources to specify svg path and cutout width / height
- Specify these resources for all 3 themes
Fixes: 133343689
Test: mp res sysuig; demo mode; manually change themes
Change-Id: Ic29e5da541330c1aa99b0e82e46a14dbb10d7940
As long as the String can be converted to an integer
Test: atest SharedPreferenceLoggerTest
Fixes: 135937584
Change-Id: If58077c9c7b10373c4c2459d275add25a5bcdc05
When enrolling Wi-Fi network with Settings Wi-Fi QR code scanner,
it will compare Wi-Fi network information between QR code and
all reachable Wi-Fi networks before connecting.
This change supports to enroll Wi-Fi networks from a Wi-Fi AP
of transition mode.
Bug: 134706055
Test: Scan a QR code of open network, verify connection
Scan a QR code of OWE network, verify connection
Scan a QR code of WPA3 network, verify connection
Scan a QR code of WPA3 network, verify transition mode connection
Change-Id: Ifc470cbcde7f33ffd76c9f6a8606cabda78a88cd
This regression was introduced by ag/7248138. Previously, changes to the
level always caused drawable invalidation, but currently invalidation
only occurs on signal level changes (not cutout or carrier change state
changes). This change fixes this behavior to invalidate the signal
drawable on all level changes.
Fixes: 134621165
Test: sysui demo mode
Change-Id: I5e14480a61fde5a0f7fdce781ae4a42a97e5d88a
If wifi verbose logging is enabled, the main thread may iterate through
the scan result list while the worker thread updates it, resulting in
an ArrayIndexOutOfBounds exception. This change adds a lock to every
iteration through mScanResults and mExtraScanResults.
Bug: 134098126
Test: atest WifiTrackerTest && atest AccessPointTest
Change-Id: If42a9ad8031ff66b1732a79772ba441185f7a18f
Autoconnected carrier wifi should display "Connected via <carrier>"
in the wifi picker even if the network has not been saved.
Bug: 134525097
Test: atest AccessPointTest
Change-Id: Id28daec3f80124f5329386ef5ff2b32cda505355
This CL is built to make CBRS show correct data usage, by merging
all subscriberId under same groupuuid
Bug: 133865338
Test: RunSettingsLibRoboTests
Change-Id: I1c5084ff98ac9a71655cc93698f3e02268654977
This moves the config files for determining the inflateSignalStrength
boolean into frameworks/base/core/res, and adds a utility method in
SettingsLib for retrieving it. This is needed so we can display
per-subscription signal strength icons in the DSDS header on the
Settings Network & internet page that match what SysUI shows.
Bug: 128855095
Test: manual, existing tests should pass
Change-Id: I57032f022439b2de3f7bf57757b2a49dc7eccfe1
This just adds a centralized place to query for the last update
time so that people don't implement it with different defaults
or something like that.
Test: in sister CL
Bug: 132751712
Change-Id: I10769eaa2e4c2ec613397988a264228a9474d1d6
The code allows to also whitelist only a select set of permissions, but
this is not yet exposed in the API.
Also: Fix up shell commands for restricted permissions
Fixes: 132368462
Test: - Enabled app via device admin in secondary profile
-> verified that permissions were whitelisted
- Installed existing and new app using --restrictpermissions and
not
-> verified that permissions were whitelisted or not
atest AppRestrictionsHelperTest
RestrictedPermissionsTest
Change-Id: I9cd76c555b40663f2e25ad86e8a54991baae346c
Merged-In: I9787e63d8beb8f6b1ba2d15532d4c0f69dbdf863
Modules may not necessarily be hidden, but we would still like to
prevent them from being disabled as they may contain critical system
functionality.
Bug: 131927465
Test: atest ApplicationsStateTest
Change-Id: I38995ecce7f517642c51a1145b1fd294638cb786
Support OWE in transition mode for devices with OWE support
and devices without OWE support. Scan results will return a
new type of network for OWE in transition networks on devices
that support OWE, and Open for devices that don't support OWE.
Handle the case where Open network is manually added to a device
that supports OWE.
Bug: 132139642
Test: Device with OWE: Connect to Open, OWE-Transition, OWE networks
Test: Device without OWE: Connect to Open, OWE-Transition
Test: Manually create Open network, connect to OWE-Transition
Change-Id: I29e69eaae2672562420ee7c6393bf2cc4d7f1b91
This CL uses merged NetworkTemplate so that it shows correct
data for carrier which is a virtual that has multiple
subscriberId under the hood.
By doing this, this CL also adds several hidden API so settings
can query by NetworkTemplate directly.
Fixes: 120566366
Test: RunSettingsLibRoboTests
Change-Id: I8b747697933c75b48b14387adafb5ac9ca165926
