This is a clean up CL, move the apn settings related class from settings'
root to network's directory.
Bug: 77339683
Test: make ROBOTEST_FILTER=ApnEditorTest -j40 RunSettingsRoboTests
Change-Id: I751a6c2a27c9a1e08d7308407d75ccb355f295aa
Also update the shortcut:
1. Change the name to "Devices"
2. Change it point to "Connected device" page
Bug: 74806595
Fixes: 69926683
Test: robo test still pass
Change-Id: Ic57756fc955dc622cc22d0be64f02b5ae07a2915
This CL removes PowerUsageSummaryLegacy and PowerUsageAdvancedLegacy
and their related layouts and strigns.
Also remove the isBatteryV2Enabled method in feature provider.
Change-Id: I1ec30f713d733ed24335a3e698fb515751232948
Fixes: 76027338
Test: robo test still pass
The index implementation is optional and left up to the OEM.
Test: Open settings, see content in index
Test: robo tests
Bug: 68378569
Bug: 76102600
Change-Id: Idb8bb1e0cabbbe92e7a852e2eadbdcd8c2ab7d56
Add intent filters for the new, public DATA_USAGE_SETTINGS action.
SystemUI's Quick Settings are already hooked up to use this intent.
Test: Visually
Bug: 73586207
Change-Id: I8638c067f557765c505500a57a3cd7a6cd3fc40d
1. Move the config update to jobscheduler, so config is checked and
updated every day.
2. Before the update, always delete the old config.
3. Move uploadIntent method to BatteryTipUtils.
Bug: 74997752
Fixes: 74564143
Test: RunSettingsRoboTests
Change-Id: If88759595d57a562b25542082f895fe8f207acdb
- fix the typo in the manifest that reference the zen mode fragment.
Change-Id: Iae6975d015174fabb98033b917290c954c5483c2
Fixes: 74577539
Test: make SettingsUnitTests
Create the notion of an official platform slice.
This includes:
- Adding a second authority to the provider
- tagging slices in xml with a platform slice flag
- Including authority in the getUri method
Bug:73359139
Test: robotests
Change-Id: I5382be138a262dbc5a8324c34aab131c5d0d5516
Merged-In: I581ee6dfcdf935f452a15e89e5d055e375ff1877
Add a new platform-only permission for being able to change
app ops mode, so nothing outside of the platform can do this.
Bug: 62342672
Test: Booted, ran, settings works, shell works, apps install
Change-Id: I2447ce04c3a90e66125ca02bb9dc1d365163c339
Bug: 74010481
Test: Manually check; sending an Intent with package:// scheme works, if
originated from app of same cert.
Change-Id: I5700e495d259d0197421f40594861bc43e3c154c
(cherry picked from commit 8e2f5a758b)
- Discovered a few more fragments that weren't whitelisted, so I
whistlisted those as well.
- Also found ZenModeExternalRuleSettings is misconfigured in manifest
and no longer needed, so deleted all artifacts about this activity.
Fixes: 74060141
Test: atest
Change-Id: I159e403bfa6707e2939d075ecc2b8d2f13514153
Old usb pages have been replaced by UsbDetailsFragment
and UsbDefaultFragment. Old connected devices has
been replaced by new connected devices.
Bug: 70848054
Test: Passes
Change-Id: I538cbb88d4f878449a83da9a4a0381e74e840c6a
1. Invoke it in BOOT_COMPLETED
2. Set it periodic
3. Change the anomaly history from 3 days to 30 days
Bug: 72385333
Test: RunSettingsRoboTests
Change-Id: Ib59a85f3dffd6c094ff400a75bec44d4c65bce44
If it is excessive bg anomaly and auto restriction is on, then
restrict the anomaly in receiver and store it in database.
Also in this cl we move the anomaly logic to a JobService, so all
works are done in a background thread and won't interfere the main
thread.
Bug: 72385333
Test: RunSettingsRoboTests &&
Will add auto restriction test once robo framework is updated(b/73172999)
Change-Id: Id0ec5fb449ce26bf19a292bcbe63838d621cfd8e
- Trigger both traces using a new Winscope Trace Tile
Bug: 73496681
Test: make RunSettingsRoboTests ROBOTEST_FILTER=WinscopeTraceTest
Test: flash and manually click on new tile
Change-Id: I3e05f625a983c382e58cc797d293a695223c630a
This receiver receives the following intent:
1. android.app.action.STATSD_STARTED
2. android.intent.action.BOOT_COMPLETED
Also it does:
1. Check whether to upload/update config(future cl)
2. Send PendingIntent to StatsManager
Bug: 72385333
Test: Will add robo test once robo framework is updated(b/73172999)
Change-Id: Iff7240663ecc1e080581683743b3027093945566
This BroadcastReceiver is triggered when anomaly happens. Inside it
we need to extract anomaly info and store it in the database.
Bug: 72385333
Test: Will add robo test once robo framework is updated(b/73172999)
Change-Id: Ib36af377fa2dff8026e7f0fcbec9575366e39cf9
This permission is required to access the ScopedAccessProvider. Although
Settings doesn't currently needs it because it has implicit access because
it runs as UID 1000, it's better to explicitly grant it.
Bug: 72055774
Test: atest CtsAppSecurityHostTestCases:ScopedDirectoryAccessTest#testResetDoNotAskAgain,testResetGranted
Change-Id: I843d7e4a1f674b4e012ac7f744d6ffccadde5a24
We don't want SHOW_ADMIN_SUPPORT_DETAILS intent to be handled
by other apps.
Bug: 69981936
Test: make -j32 RunSettingsRoboTests
Test: manual - Install another app which handles SHOW_ADMIN_SUPPORT_DETAILS
intent and verify that when SHOW_ADMIN_SUPPORT_DETAILS intent is
triggered, Settings activity gets launched.
Change-Id: I6f764fe53b32559da829d515dd448c817b6bf7c9
Steps:
1. Take any photo/picture and share it via Bluetooth
2. Before choosing remote device in Device Picker Activity, rotate
the device.
Expected result:
File transfer should complete after selecting the device.
Actual result:
The dialog "Bluetooth share: File Unknown file not sent" is shown and
file sharing fails.
Fix:
Add configuration related check in manifest to avoid activity restart during
orientation change.
Test: File transferred successfully after step 2
Fixes: 72715713
Change-Id: I045c2940d3788059c9313e5501a7957608d8879c
...because dynamic tile is a lot harder to index correctly.
- Removed metadata that makes PrintSettings a dynamic tile.
- Added PrintSettings into connected_device xml.
- Added a new PreferenceController - all summary updating logic is
copied from PrintSettingsFragment
Change-Id: I41e7c9d23e97ecd5a043ac7c33f2d404260c92e7
Fixes: 73128944
Test: robotests
- Moved fragments into wifi sub-package.
- Cleaned up inheritance for WifiCallingSettings
- Attach help and search action menu controller correctly.
Change-Id: I0bc8ab99df5d8c5ea64fb64de5ae70c2c9bd6f31
Fixes: 72958674
Test: robotest
This is needed to fix nav-up button for these activities.
- Change taskAffinity for homepage to "com.android.settings.root".
- Change taskAffinity for many activities to "com.android.settings", and
set partent to homepage.
-- General rule: if activity has not been exported, don't set
affinity or parent.
-- If activity is exported and can be launched with an action, set
affinity and parent to homepage
-- If activity is exported but expects additional parameters, don't
set affinity or parent.
-- If the activity affinitiy is com.android.setupwizard, don't touch
it.
With this change, when a setting page is launched via intent (eg, from
QS), nav up button will be able to find parentActivity, and launch it in
a different task affinity. If the acitivity is a launched within
settings, nav-up has no change, it just navigates back to where it came from.
Change-Id: I3a2b64ed13d437f6818f6c7374e994b4192b6fa0
Fixes: 72337421
Fixes: 72829142
Test: manual
Test: atest
Creates a new fragment DataUsageSummaryLegacy, which is used
instead of DataUsageSummary when the feature flag is off (default
behavior).
Copies the current DataUsageSummary.java, data_usage.xml, and
DataUsageSummaryActivity to create the legacy versions. This
change allows for uninterupted development of new features in the
DataUsageSummary fragment.
Test: manual
Test: make RunSettingsRoboTests
Bug: 70950124
Change-Id: I9d79e108bbfc1c8ec620f86c0183f4ed3f41c9d7
