Allows an admin user to selectively install packages into a Guest user
by displaying a list of available packages that are installed in the
admin, but not in the Guest, and letting the admin choose to copy those
apps to the Guest.
Test: atest SettingsLibTests:com.android.settingslib.users.AppCopyingHelperTest
Test: Manual: install some apps in user 0, create a guest, uninstall
some system apps from it. Now, open this panel. Request some of those
apps be installed in the Guest and verify it worked.
Bug: 193281439
Change-Id: I4e6874a4ee93cd7bba96e1f6c8d04ed95873c1a2
This CL is the base framework for creating and adjusting TARE factor
values. TareFactorDialogFragment sets the basic outline for a factor
that uses a DialogBox to adjust the value. It takes the "title" or name
of the factor, the key that will be associated with the factor, and an
initial value for the factor; then sets up everything so that the factor
value can be easily changed and stored. These factors are also
registered into the settings observer class.
Bug: 195055619
Bug: 193238774
Test: Manual (Made a temporary class instance of the DialogFragment and
showed it in inactive apps onResume())
Change-Id: I3bb67717175e70eab3bbb11f4a42ee63a42f60bc
Add logic to properly handle blobs and leases that never expire.
Also add the relevant strings required in this package.
Fixes: 194439893
Test: make RunSettingsRoboTests ROBOTEST_FILTER=SharedDataPreferenceControllerTest
Test: manual (visual)
Change-Id: Ifeb216a92a3be8d1db3574b4f63e2d04adace4ea
A Job Scheduler policy page is needed in the TARE developer options
settings to allow developers to both view and edit the current values of
all the factors under the job scheduler policy. The page uses a dropdown
so that the user can easily switch between the different policies. For
the factors with subfactors, the user simply clicks on the factor and
the subfactors wil pop up under it.
Bug: 191877052
Test: Manual (open Settings > System > Developer Options > TARE >
JobScheduler and verify all factors are there)
Change-Id: Icea6cda5e4b59d1736f85defcb9532839c3720f5
An alarm manager policy page is needed in the TARE developer option
settings to allow developers to both view and edit the current values of
all the factors under the alarm manager policy. The page uses a dropdown
so that the user can easily switch between the different policies. For
the factors with subfactors, the user simply clicks on the factor and
the subfactors will pop up under it.
Bug: 191876714
Bug: 191876567
Test: Manual (open Settings > System > Developer Options > TARE > Alarm
Manger and verify all factors are there)
Change-Id: Ie036e26df80947d23041bedfd5b1385e48069b6b
Clarify the strings used for the TARE homepage. Update
comments so that the translators understand that TARE is not
translatable and that AlarmManager and JobScheduler are Android system
services.
Bug: 191876567
Test: Manual (open Settings > System > Developer Options > TARE and
verify tabs and menus are there)
Change-Id: I935cd0ab9e8e6e5591875a1e7f8ed9f58d8abd9c
A TARE button is needed in the developer options in settings to allow
users and developers to change the default settings it will come with.
When clicked, it opens an activity of the TARE homepage with a toggle
and the two policies (Alarm Manager and Job Scheduler) to choose between. It also contains a revert to default settings button.
Bug: 191876567
Test: Manual (open Settings > System > Developer Options > TARE and
verify tabs and menus are there)
Change-Id: Id14bc9c1dcbaaf2aeb74ba7efb0168ab424f5d0c
Bug:192987269
Test: Manual test
Test: make RunSettingsRoboTests
ROBOTEST_FILTER=NetworkProviderSettingsTest
Change-Id: I3892386f8fe2e5c3e29cd7e91f88db65c3693990
- Increase string length limit from 30 to 75
Bug: 191952712
Test: modify comment only, Verified the maximum length string in the UI.
Change-Id: I5c8e6e5cb34358280aa0c3594a75cd545c70a483
Goal: Improve readability which is a bit difficult because of string concatenation for accurate translation.
Root cause: In some locales, framework features name would be a word rather than a product name. Hence it need to be in the different position in a sentence.
Solution: Use whole sentence to translate instead of concatenating the string could solve this issue.
Bug: 185478543
Test: Manually testing
Change-Id: Iced1fe7db81e4e78ddfed30ab947d449b5f9c735
1. Add gesture preference controller for gesture navigation
2. Auto update the preview illustarion when screen reader is on
3. Auto update accessibility button title for system navigation
Bug: 190563948
Test: make RunSettingsRoboTests ROBOTEST_FILTER=AccessibilityButtonGesturePreferenceControllerTest ROBOTEST_FILTER=AccessibilityButtonPreviewPreferenceControllerTest ROBOTEST_FILTER=AccessibilityLayerDrawableTest ROBOTEST_FILTER=AccessibilityPreferenceControllerTest ROBOTEST_FILTER=AccessibilityButtonFooterPreferenceControllerTest
Change-Id: Ifa98fc029430d86d3143133b3203b239340f2e41
This button will be on by default now, so remove the switch
Bug: 185618694
Test: build
Test: make RunSettingsRoboTests -j ROBOTEST_FILTER=com.android.settings.display
Change-Id: Iecbeb590a5b750ec2fcf9c31fece5814241200b1
Goal: Improve readability which is a bit difficult because of string concatenation for accurate translation.
Root cause: In some locales, framework features name would be a word rather than a product name. Hence it need to be in the different position in a sentence.
Solution: Use whole sentence to translate instead of concatenating the string could solve this issue.
Bug: 185478543
Test: make RunSettingsRoboTests ROBOTEST_FILTER=AccessibilityFooterPreferenceControllerTest
Change-Id: Id198805329be9c773df87f38a074ae956e4d0cdb
Adds an additional message about the "Require eyes to be open" setting
for Face Unlock to the intro/consent screen of enrollment, gated by a
config flag.
Test: Manual
Bug: 192272785
Change-Id: Idcd2395a290b74f4578898fdfebd05b81cd74075
