When an intent with action android.settings.SCREEN_TIMEOUT_SETTINGS is
launched, ScreenTimeoutSettings should be shown in settings
Bug: 293813663
Test: manual and local build verify
Change-Id: I1340cd3c233aa5d36f45b53b0fd2b6924f3a1d75
Bug: 313775893
Test: Trigger the intent with action "android.settings.REQUEST_MEDIA_ROUTING_CONTROL" and package name in the data uri
Change-Id: If65ea61a058b465dc44836eff9c7d3fb25425ec4
Bug: b/307632045
Test: Pair a watch with companion app > Settings > Apps > Special app access > enter "Change Media Output" > Find the companion app > Ensure the special app access is Allowed > ensure companion app is able to call remote media routing APIs > come back to the settings > revoke the access > ensure that now companion app is NOT able to call the remote media routing APIs.
Change-Id: I35487660365ef05f3b998e8ecf13aaed7ba844a9
From DevelopmentSettingsActivity, this action used to inject developer
options into Settings itself, since we display this directly instead of
inject, we no longer need this.
Bug: 311604902
Test: manual - open Developer options from System
Change-Id: I3ea26464954d8711e7aecc031daf09ad30362d70
Also the SpaAppBridgeActivity.
Could be tested by,
adb shell am start -n com.android.settings/.ManageFullScreenIntent
adb shell am start \
-a android.settings.MANAGE_APP_USE_FULL_SCREEN_INTENT \
-d package:com.android.settings
adb shell am start -n com.android.settings/.UsageStatsActivity
Bug: 309075424
Test: manual - on tablet
Test: unit test
Change-Id: I778443e9d21d165904e415c66c03aafc7ac81372
Use to highlight the "System" of the left activity on the tablet.
Can be tested with,
adb shell am start -a android.settings.APPLICATION_DEVELOPMENT_SETTINGS
Bug: 311604902
Test: manual - tested with adb
Change-Id: If9eea47f3bd6d2ab7bbce0a10c56d1cd14784140
- It can improve performance because we use less injected item
- Also use RestrictedPreference instead just checking restrictions,
so we follow policy transparency.
Note: Renamed DevelopmentSettingsDashboardActivity to
DevelopmentSettingsActivity,
because DevelopmentSettingsDashboardActivity could in disabled state
even after Settings upgrades, use a new name to prevent this issue.
Bug: 311604902
Test: manual - turn on / off Developer Options
Test: unit test
Change-Id: I17be117ae59e59410687e6d08fd5edd034d0508f
This API was already deprecated and not supported for a few years. The
API was completely removed in Android U (see b/236980291).
Bug: 307352220
Test: Verified NFC settings works correctly
Merged-In: I40974a26d170cf3eeec18e6a07a21f6c420eca9e
Change-Id: I40974a26d170cf3eeec18e6a07a21f6c420eca9e
This API was already deprecated and not supported for a few years. The
API was completely removed in Android U (see b/236980291).
Bug: 307352220
Test: Verified NFC settings works correctly
Change-Id: I40974a26d170cf3eeec18e6a07a21f6c420eca9e
This includes changes for
1. To add auto avancing screens to PS setup
2. Screen to set a different Private profile lock or use existing lock
3. Success screen on setup completion
4. Shows Error screen if profile creation failed for some reason
5. Send intent towards launcher, show a Toast message to access PS from bottom of All apps and exit.
Bug: 299069146
Test: Manual setup
Change-Id: If4e5dd5a42abb11259bc40506189c7c750324139
This change handles as below based on if private space already exists on device:
1. If PS doesn't exist then start the setup flow which shows a PS education screen. On setup button creates the private space.
2. If PS already exists on device then display PS settings page.
Bug: 299069146
Test: atest PrivateSpaceSettingsAuthenticatorTest
Change-Id: I46bdbaeb0210fd5b41a426f852e3f455b62c1c29
[Root Cause]: Intent.ACTION_TIME_CHANGED is listened in the java code, but it is not registered in the AndroidManifest.xml.
Bug: 304700667
Bug: 303352170
Fix: 304700667
Fix: 303352170
Test: manual
Change-Id: I326c525c4a370493e8caa70258580b6bd9dfe357
When an intent with action android.settings.MANAGE_USER_ASPECT_RATIO_SETTINGS
and data with scheme "package:" is launched, the UserAspectRatioDetails
is shown in settings
Fix: 296564769
Test: Manual
Change-Id: I3667ece595ad76c694342de934051893e1e0a1d3
redundant face unlock header.
In AndroidManifest.xml to apply Theme.Settings.NoActionBar theme
attribute to avoid action_bar appears accidentally.
Bug: 293978245
Test: manually check UI with reproducible steps:
Pre-Condition:
1) enroll face
2) enable auto rotate
Procedure:
1) go to settings > security > face & fingerprint unlock
2) enter screen lock
3) click face unlock
4) rotate device into landscape mode and then back to portrait mode
5) check the UI
Change-Id: I065ff5821a91eb8060dd98b373fce34cae769c66
This commit removes the obsolete QS development tile for Winscope
tracing as now Winscope traces can be collected via Traceur.
Bug: 295816837
Test: N/A
Change-Id: I7658537579cd054af092945aab553a4e17997273
This change adds an entry point for Remote Auth enrollment and
navigation through the flow.
Bug: b/293906345
Test: make RunSettingsRoboTests -j40
Change-Id: I9bc803e24c4181ed73a0ef90b171897c677e71d1
These permissions used to guard code in Android Authenticator which doesn't exist now. There is no GSF code in V+.
Bug:280072910
Change-Id: Ib2fceca51c324f107be6b9e2f9e6001431cc3f08
