| 31484af10181a60785287b25bc3970446c3e3253 |
|
22-Mar-2017 |
Stephen Chen <stewchen@google.com> |
Remove ACTION_CONFIGURE_WIFI_SETTINGS and ACTION_WIFI_SAVED_NETWORK_SETTINGS.
ConfigureWifiSettings page will instead use WIFI_IP_SETTINGS intent.
Intent for SavedAccessPointsSettingsActivity is unused and can be
removed.
Bug: 34392691
Bug: 36516068
Test: make
Change-Id: I86547df387b41241d531e361014581d0763008ee
/frameworks/base/core/tests/coretests/src/android/provider/SettingsProviderTest.java
|
| d891f01d96cbaa3b1329c3d476084f3fedb30a89 |
|
19-Jan-2017 |
Mark Rathjen <mrathjen@google.com> |
Roll forward SSAID Migration to be Per App/User Unique Values.
SSAID is currently shared across all applications for each
user on the device, giving developers the ability to track
users across multiple applications. Using SSAID for tracking
is an abuse of the original intention of the SSAID and has
inherent privacy concerns.
This change will make the SSAID unique per application, per
user on a device. To not affect applications installed prior
to this change they will retain the legacy SSAID value until
uninstalled and reinstalled again.
Across subsequent installations the application will receive
the same SSAID as long as the package name and signature remain
consistent.
Tested manually the following cases:
- App retains the legacy sssaid after OTA.
- App gets a new ssaid upon post-OTA installation.
- App retrieves same ssaid across post-OTA unistall/reinstalls.
- Different Apps receive different ssaids.
- Factory reset removes ssaid data and generates a different
ssaid after App install.
- System retains legacy ssaid.
Bug: 34395671
Test: CTS tests passed, Manual testing passed
This reverts commit be43257005d086ff7d93c15dae22ac40bc0d545e.
Change-Id: Ibf20e7949304c30d65bb8aa24cdbbe6e104b1002
/frameworks/base/core/tests/coretests/src/android/provider/SettingsProviderTest.java
|
| be43257005d086ff7d93c15dae22ac40bc0d545e |
|
19-Jan-2017 |
Mark Rathjen <mrathjen@google.com> |
Revert "SSAID Migration to be Per App/User Unique Values."
This reverts commit 5514fb7aba781d8eabbbfc27a5d27a6b3a447b40.
Change-Id: I0d6b9b9ef3ecda3b7ec1b7160c492ec16c65b125
/frameworks/base/core/tests/coretests/src/android/provider/SettingsProviderTest.java
|
| 5514fb7aba781d8eabbbfc27a5d27a6b3a447b40 |
|
12-Jan-2017 |
Mark Rathjen <mrathjen@google.com> |
SSAID Migration to be Per App/User Unique Values.
SSAID is currently shared across all applications for each
user on the device, giving developers the ability to track
users across multiple applications. Using SSAID for tracking
is an abuse of the original intention of the SSAID and has
inherent privacy concerns.
This change will make the SSAID unique per application, per
user on a device. To not affect applications installed prior
to this change they will retain the legacy SSAID value until
uninstalled and reinstalled again.
Across subsequent installations the application will receive
the same SSAID as long as the package name and signature remain
consistent.
Tested manually the following cases:
- App retains the legacy sssaid after OTA.
- App gets a new ssaid upon post-OTA installation.
- App retrieves same ssaid across post-OTA unistall/reinstalls.
- Different Apps receive different ssaids.
- Factory reset removes ssaid data and generates a different
ssaid after App install.
- System retains legacy ssaid.
Bug: 30979321
Test: CTS tests passed, Manual testing passed
Change-Id: I4acc190c14ec249e6365e05e7943148ed6f17f71
/frameworks/base/core/tests/coretests/src/android/provider/SettingsProviderTest.java
|
| 46bea2e685915fe45d372389b0a90815e6067feb |
|
06-Dec-2016 |
Bartosz Fabianowski <bartfab@google.com> |
Link from Quick Settings to Enterprise Privacy page
This CL updates the information shown in Quick Settings when a device
is managed by a Device Owner and adds a "learn more" link that takes
the user to the Enterprise Privacy page in Settings.
Bug: 32692748
Bug: 25779452
Test: runtest --path frameworks/base/packages/SystemUI/tests &
runtest --path frameworks/base/core/tests/coretests
Change-Id: I8cbb6f2bb5c6da29ae581b6dcf7a01b1a4f2af2b
/frameworks/base/core/tests/coretests/src/android/provider/SettingsProviderTest.java
|
| 28d89393140143dc5c7847b10fcbd3aa741e2eab |
|
15-Nov-2016 |
Stephen Chen <stewchen@google.com> |
Add ACTION_WIFI_SAVED_NETWORK_SETTINGS to Settings.
Exposes an activity that deep links into saved network Settings.
Bug: 32738882
Test: gts test
Change-Id: Idfd45a8ab424a5508012675058e3498ebbc5e228
/frameworks/base/core/tests/coretests/src/android/provider/SettingsProviderTest.java
|
| 43765b77a0286403fd9f7f5305219f0d9a10c953 |
|
31-Aug-2015 |
Xiaohui Chen <xiaohuic@google.com> |
Cleanup USER_OWNER in SettingsProvider[Test]
Fixed up the tests and re-enabled it.
Still suppressed one test because what it relies on Settings.Bookmarks
is broken because Settings query format changed.
Fixed a bug in SettingsProvider that the package query is using the
wrong user id.
Bug: 19913735
Change-Id: Ied86a261defba2706f726a13bc32f385f7d93787
/frameworks/base/core/tests/coretests/src/android/provider/SettingsProviderTest.java
|
| f90177629a5b69ca3a80466c0ab55abfeb6d26b2 |
|
01-Aug-2015 |
Abodunrinwa Toki <toki@google.com> |
Turn off failing tests in FrameworksCoreTests.
We want a green state so we can confidence in tests we write
going forward.
Change-Id: I2c8db848897b56d0c64202ad28861eb4a7572e07
/frameworks/base/core/tests/coretests/src/android/provider/SettingsProviderTest.java
|
| d2726582f135383e56661bc41d750966642dab45 |
|
04-Feb-2013 |
Maggie Benthall <mbenthall@google.com> |
Fix for SettingsProvider to query for correct user.
insertForUser takes a specified user and attempts to adjust that user's
settings, first looking at their existing settings to determine the difference.
However it was querying the settings for the calling user, rather than for
the user whose settings were being changed.
Also add a test that exercises the fix.
Change-Id: I6ed6fd79154ac1b6e6ab880769ac9081dfff6b80
/frameworks/base/core/tests/coretests/src/android/provider/SettingsProviderTest.java
|
| 78d2a66ac12e4c8f1303225514f573fb53af1dd9 |
|
14-Sep-2012 |
Christopher Tate <ctate@google.com> |
Fix Settings writes to a different user
Oops. Stacked bugs: first, the desired user handle was not properly
being passed from the call() entry point to the database operations;
then on top of that, the client-side cache management was still
looking in the local user's cache for the data, so a request to read
a different user's settings would return the local user's instead if
that key was already known to the local user's cache.
Reads and writes of a different user's settings are now uncached,
so they're relatively much slower. They're rare, however, so this
is not something to worry about unless we encounter a real world
case where it's a significant factor.
This CL also adds a bit of cross-user settings read/write testing
to the existing provider suite. These new tests caught both the
known wrong-user-write bug and discovered the client-side cache
bug, so yay.
Finally, the existing wholesale mutual-exclusion approach would
deadlock in certain circumstances due to the fact that the
settings database creation code might have to call out to the
Package Manager while populating the bookmark/shortcut table,
and the Package Manager would then call back into the settings
provider in the course of handling that request. The synchronization
regime has been significantly tightened up now: now the database
code [which is known to deal with concurrency itself] is allowed
to cope with multiple parallel openers of the same db; this
allows the settings provider to avoid calling out to other parts
of the system even implicitly while its internal lock is held.
Change-Id: Ib77d445b4a2ec658cc5c210830f6977c981f87ed
/frameworks/base/core/tests/coretests/src/android/provider/SettingsProviderTest.java
|
| fe62e31914bef645851e11418ddaee279c845e99 |
|
18-Aug-2011 |
Brian Muramatsu <btmura@google.com> |
Test for Settings Intent
Bug 4983978
Change-Id: I4d366bbcacdc12e5d86d22f5fab0e934e4ef66db
/frameworks/base/core/tests/coretests/src/android/provider/SettingsProviderTest.java
|
| c2591c14f77366f30cc83e9c6a2abf9d9cd12a5e |
|
22-Apr-2010 |
Kenny Root <kroot@google.com> |
Add tests for SettingsProvider.parseProviderList
Change-Id: Id5c1597cd94b80e0d20ca415b5b7ba32200c1a03
/frameworks/base/core/tests/coretests/src/android/provider/SettingsProviderTest.java
|
| d0ca3379c2dd0f987af328baa3fdad69d0a8d70a |
|
08-Mar-2010 |
Amith Yamasani <yamasani@google.com> |
Fix a SettingsProvider test : 2377540
/frameworks/base/core/tests/coretests/src/android/provider/SettingsProviderTest.java
|
| 1a44d5dcabc18cd5ef111f732ccff91683a1a093 |
|
13-Jan-2010 |
Neal Nguyen <tommyn@google.com> |
Phase 2 of test cleanup: moving test files from AndroidTests closer to their sources.
Most of these are file moves; a couple notable exceptions are the changes due to the move, and fixing up test code:
- database/DatabaseCursorTest.java
- database/DatabaseStatementTest.java
- net/UriTest.java
/frameworks/base/core/tests/coretests/src/android/provider/SettingsProviderTest.java
|