38b46f82f718891de608ca31e49034d824a88a12 |
|
27-Mar-2018 |
Brad Stenning <stenning@google.com> |
Add an option to display HVAC temp values in sysui Bug: 77148007 Test: on device that has a real HVAC unit Change-Id: I97b303dd947858157ede72c5d537ae6a1e40cc67
/frameworks/base/packages/SystemUI/tests/Android.mk
|
e53f749995373f6271ae4a9ac7b3c6007aabd8e9 |
|
01-Mar-2018 |
Lujiang Xue <rogerxue@google.com> |
add car volume dialog Bug: 73134851 Test: manually tested Change-Id: Ia95a8aa48789652d6af67a542f62353a7bf13607 (cherry picked from commit 4d2a3ef6e9ec3da1c1c5bf5e93b61d2ac89f47b6)
/frameworks/base/packages/SystemUI/tests/Android.mk
|
d137c872cdc5e157c0ff65076689f7c4552a9013 |
|
23-Feb-2018 |
Anton Hansson <hansson@google.com> |
frameworks/base: Set LOCAL_SDK_VERSION where possible. This change sets LOCAL_SDK_VERSION for all packages where this is possible without breaking the build, and LOCAL_PRIVATE_PLATFORM_APIS := true otherwise. Setting one of these two will be made required soon, and this is a change in preparation for that. Not setting LOCAL_SDK_VERSION makes the app implicitly depend on the bootclasspath, which is often not required. This change effectively makes depending on private apis opt-in rather than opt-out. Test: make relevant packages Bug: 73535841 Exempt-From-Owner-Approval: Global cleanup Change-Id: I26458e41ecb84de91ac9a356a5d4bafb44f463c1
/frameworks/base/packages/SystemUI/tests/Android.mk
|
1fc931a38a9335b3b4b498c7cc31d37a777c7a5a |
|
14-Dec-2017 |
Jason Monk <jmonk@google.com> |
Switch to inline mockito for a bunch of tests So we can mock final stuff Test: The tests Change-Id: Ia3a47c6655c4b0b9af0aea0ee6f8f6cb9ebaab09
/frameworks/base/packages/SystemUI/tests/Android.mk
|
fdbc6115025c892754f9e497a3318475e2b8d11c |
|
06-Feb-2018 |
Narayan Kamath <narayan@google.com> |
SystemUI: Remove obsolete dependency on android.car. Car related functionality was removed in efa42d2cc59bf63a1e0bae31b. Test: make Change-Id: Ieb54aa23a3d028705bf70a707406041fa2a6a0d4
/frameworks/base/packages/SystemUI/tests/Android.mk
|
a43e216e3eb8b9cfe011cb92ab00aea11fa9da29 |
|
27-Jan-2018 |
Aurimas Liutikas <aurimas@google.com> |
Use the correct prebuilts for lifecycles. This change should have no effect on the app. It is simply unifying some of the prebuilts. Bug: 72566647 Change-Id: Ic748f8f425e8c8e44bacf62ea61b9af307774911
/frameworks/base/packages/SystemUI/tests/Android.mk
|
6bd8601e9f79598096ee31441e536fecdd415191 |
|
06-Dec-2017 |
Lucas Dupin <dupin@google.com> |
New keyguard slice data structure Using androidx package and new API, also splitting content into multiple views for better animation support. Bug: 64155983 Test: visual, see data from provider propagate to AoD Change-Id: I74b5511d582e7ec1f6ffe5dbc5595f54b9ccb202
/frameworks/base/packages/SystemUI/tests/Android.mk
|
b866307f99c35252dcb76e9269bb57d97c3c4b86 |
|
08-Dec-2017 |
Paul Duffin <paulduffin@google.com> |
Stop statically including legacy-android-test Statically including legacy-android-test leads to duplicate classes which causes build time problems (with Proguard) and runtime problems on older SDK versions. This change: * Stops statically including legacy-android-test. * Adds compile time dependencies on andoid.test.base, android.test.mock and android.test.runner where necessary. * Adds <uses-library android:name="android.test.runner"/> to any affected package to ensure that the classes that were included by legacy-android-test are still available at runtime. That also adds a dependency on android.test.base and android.test.mock. The following change descriptions were generated automatically and so may be a little repetitive. They are provided to give the reviewer enough information to check the comments match what has actually been changed and check the reasoning behind the changes. * apct-tests/perftests/core/Android.mk Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in CorePerfTests results in duplicate classes which leads to build time and compile time issues. Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because CorePerfTests's source depends on its classes and because of these changes they are no longer present on the compilation path. * core/tests/ConnectivityManagerTest/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because ConnectivityManagerTest's source depends on its classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in ConnectivityManagerTest results in duplicate classes which leads to build time and compile time issues. * core/tests/bandwidthtests/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because BandwidthTests's source depends on its classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in BandwidthTests results in duplicate classes which leads to build time and compile time issues. * core/tests/bluetoothtests/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because BluetoothTests's source depends on its classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in BluetoothTests results in duplicate classes which leads to build time and compile time issues. * core/tests/hosttests/test-apps/DownloadManagerTestApp/Android.mk Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in DownloadManagerTestApp results in duplicate classes which leads to build time and compile time issues. Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because DownloadManagerTestApp's source depends on its classes and because of these changes they are no longer present on the compilation path. * core/tests/hosttests/test-apps/ExternalSharedPerms/Android.mk Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in ExternalSharedPermsTestApp results in duplicate classes which leads to build time and compile time issues. * core/tests/hosttests/test-apps/ExternalSharedPermsBT/Android.mk Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in ExternalSharedPermsBTTestApp results in duplicate classes which leads to build time and compile time issues. * core/tests/hosttests/test-apps/ExternalSharedPermsDiffKey/Android.mk Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in ExternalSharedPermsDiffKeyTestApp results in duplicate classes which leads to build time and compile time issues. * core/tests/hosttests/test-apps/ExternalSharedPermsFL/Android.mk Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in ExternalSharedPermsFLTestApp results in duplicate classes which leads to build time and compile time issues. * core/tests/notificationtests/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because NotificationStressTests's source depends on its classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in NotificationStressTests results in duplicate classes which leads to build time and compile time issues. * keystore/tests/Android.mk Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in KeystoreTests results in duplicate classes which leads to build time and compile time issues. * media/mca/tests/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because CameraEffectsTests's source depends on its classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in CameraEffectsTests results in duplicate classes which leads to build time and compile time issues. * media/tests/MediaFrameworkTest/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because mediaframeworktest's source depends on its classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in mediaframeworktest results in duplicate classes which leads to build time and compile time issues. * nfc-extras/tests/Android.mk Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in NfcExtrasTests results in duplicate classes which leads to build time and compile time issues. * packages/CarrierDefaultApp/tests/unit/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because CarrierDefaultAppUnitTests's source depends on its classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in CarrierDefaultAppUnitTests results in duplicate classes which leads to build time and compile time issues. * packages/ExtServices/tests/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because ExtServicesUnitTests's source depends on its classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in ExtServicesUnitTests results in duplicate classes which leads to build time and compile time issues. * packages/MtpDocumentsProvider/tests/Android.mk Added 'android.test.base' and 'android.test.mock' to LOCAL_JAVA_LIBRARIES because MtpDocumentsProviderTests's source depends on their classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in MtpDocumentsProviderTests results in duplicate classes which leads to build time and compile time issues. * packages/SettingsLib/tests/integ/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because SettingsLibTests's source depends on its classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in SettingsLibTests results in duplicate classes which leads to build time and compile time issues. * packages/SettingsProvider/Android.mk Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in SettingsProvider results in duplicate classes which leads to build time and compile time issues. * packages/SettingsProvider/AndroidManifest.xml Add uses-library for android.test.runner because otherwise this change would change the set of files available to SettingsProvider at runtime. * packages/Shell/tests/Android.mk Added 'android.test.base' and 'android.test.mock' to LOCAL_JAVA_LIBRARIES because ShellTests's source depends on their classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in ShellTests results in duplicate classes which leads to build time and compile time issues. * packages/SystemUI/shared/tests/Android.mk Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in SystemUISharedLibTests results in duplicate classes which leads to build time and compile time issues. * packages/SystemUI/tests/Android.mk Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in SystemUITests results in duplicate classes which leads to build time and compile time issues. Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because SystemUITests's source depends on its classes and because of these changes they are no longer present on the compilation path. * packages/WAPPushManager/tests/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because WAPPushManagerTests's source depends on its classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in WAPPushManagerTests results in duplicate classes which leads to build time and compile time issues. * sax/tests/saxtests/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because FrameworksSaxTests's source depends on its classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in FrameworksSaxTests results in duplicate classes which leads to build time and compile time issues. * tests/BrowserPowerTest/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because BrowserPowerTests's source depends on its classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in BrowserPowerTests results in duplicate classes which leads to build time and compile time issues. * tests/CanvasCompare/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because CanvasCompare's source depends on its classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in CanvasCompare results in duplicate classes which leads to build time and compile time issues. * tests/CoreTests/android/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because CoreTests's source depends on its classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in CoreTests results in duplicate classes which leads to build time and compile time issues. * tests/DataIdleTest/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because DataIdleTest's source depends on its classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in DataIdleTest results in duplicate classes which leads to build time and compile time issues. * tests/FrameworkPerf/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because FrameworkPerf's source depends on its classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in FrameworkPerf results in duplicate classes which leads to build time and compile time issues. * tests/HierarchyViewerTest/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because HierarchyViewerTest's source depends on its classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in HierarchyViewerTest results in duplicate classes which leads to build time and compile time issues. * tests/ImfTest/tests/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because ImfTestTests's source depends on its classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in ImfTestTests results in duplicate classes which leads to build time and compile time issues. * tests/Internal/Android.mk Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in InternalTests results in duplicate classes which leads to build time and compile time issues. * tests/MemoryUsage/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because MemoryUsage's source depends on its classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in MemoryUsage results in duplicate classes which leads to build time and compile time issues. * tests/NetworkSecurityConfigTest/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because NetworkSecurityConfigTests's source depends on its classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in NetworkSecurityConfigTests results in duplicate classes which leads to build time and compile time issues. * tests/SoundTriggerTests/Android.mk Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in SoundTriggerTests results in duplicate classes which leads to build time and compile time issues. Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because SoundTriggerTests's source depends on its classes and because of these changes they are no longer present on the compilation path. * tests/SurfaceComposition/Android.mk Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in SurfaceComposition results in duplicate classes which leads to build time and compile time issues. Added 'android.test.runner.stubs' to LOCAL_JAVA_LIBRARIES because SurfaceComposition's source depends on its classes and because of these changes they are no longer present on the compilation path. * tests/TtsTests/Android.mk Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in TtsTests results in duplicate classes which leads to build time and compile time issues. Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because TtsTests's source depends on its classes and because of these changes they are no longer present on the compilation path. * tests/WindowAnimationJank/Android.mk Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in WindowAnimationJank results in duplicate classes which leads to build time and compile time issues. * tests/permission/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because FrameworkPermissionTests's source depends on its classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in FrameworkPermissionTests results in duplicate classes which leads to build time and compile time issues. * tests/testables/tests/Android.mk Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in TestablesTests results in duplicate classes which leads to build time and compile time issues. Added 'android.test.base' and 'android.test.mock' to LOCAL_JAVA_LIBRARIES because TestablesTests's source depends on their classes and because of these changes they are no longer present on the compilation path. Bug: 30188076 Test: make checkbuild Change-Id: Iacfc939c97415314366ed61c5f3b7aa1a40f0ec9
/frameworks/base/packages/SystemUI/tests/Android.mk
|
6519c1b0fe85c5f25115539e936e4333e8537098 |
|
14-Oct-2017 |
Winson Chung <winsonc@google.com> |
Moving some recents logic into the shared lib. - Creating com.android.system.shared library with recents model code and corresponding recents tests - Removing notion of blacklisted apps since that is now obsolete. Bug: 67510855 Test: It builds, Recents runs Change-Id: Ib1f5eefa6e4d4964366061246002509e2e15b19e
/frameworks/base/packages/SystemUI/tests/Android.mk
|
8443dd0e7680e489509e8a9bf0bb5fcefd7a8c3e |
|
25-Aug-2017 |
jackqdyulei <jackqdyulei@google.com> |
Hook up AOD knobs to Settings.Global This cl creates AlwaysOnDisplayPolicy, which get values for the following knobs(go/aod-experiments) from Settings.Global: 1. screen_brightness_array 2. dimming_scrim_array 3. prox_screen_off_delay 4. prox_cooldown_trigger 5. prox_cooldown_period Also update code to make sure AlwaysOnDisplayPolicy is used everywhere. Bug: 64899561 Test: runtest -x AlwaysOnDisplayPolicyTest Change-Id: I2e83ff980771e67177e4964bd83aa68b2bdca65f
/frameworks/base/packages/SystemUI/tests/Android.mk
|
7224c1eca2afa13f2b975447db537038446e4177 |
|
06-Jul-2017 |
Lucas Dupin <dupin@google.com> |
Moving color extraction classes Fixes: 62220212 Test: make Test: runtest -x tests/Internal/src/com/android/internal/colorextraction/ColorExtractorTest.java Test: runtest -x tests/Internal/src/com/android/internal/colorextraction/types/TonalTest.java Test: runtest systemui Change-Id: I7c4cf5c40a88555e81fbad9bec2b32c55c927468
/frameworks/base/packages/SystemUI/tests/Android.mk
|
afc4f9313c281e07efbfa20846d83f0c1c77f5ad |
|
09-May-2017 |
Selim Cinek <cinek@google.com> |
Merge changes from topic 'background_inflation' into oc-dev am: 03fbdbe6ff am: cc360f9b69 Change-Id: I456f81ff6300792e8639733d0115d878683d1694
|
0f66a4cc16ec1a927c90ac559c73c80ddcb5ee71 |
|
29-Apr-2017 |
Selim Cinek <cinek@google.com> |
Moving Row inflation to the background too Previously only the contentview inflation was on the background, now the inflation of the row is too. Test: runtest systemui Bug: 34888292 Change-Id: I3adc6b3311217421c9de5c37794397b8a3fd665d
/frameworks/base/packages/SystemUI/tests/Android.mk
|
c926a5ee1a2b0e5f951bd1126d071c8ebe9f21e1 |
|
02-May-2017 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "Color extraction on scrims"
|
8da8f2e9dd73911cdea257b7ae9918340a05f1b5 |
|
21-Apr-2017 |
Lucas Dupin <dupin@google.com> |
Color extraction on scrims Consuming color extraction library to add wallpaper colors to sysui scrims. Handles both lock screen and notification shade. Bug: 36856508 Bug: 37013527 Test: runtest --path frameworks/base/packages/SystemUI/tests/src/com/android/systemui/statusbar/ScrimViewTest.java Change-Id: I8d964c978a766243d90bbfb3432d19eebf1a2056
/frameworks/base/packages/SystemUI/tests/Android.mk
|
5fb73f86299d9cc616ca741f8c7c4af2485cc273 |
|
21-Apr-2017 |
Selim Cinek <cinek@google.com> |
Extracting the notification colors based on the album art Media notifications are now extracting the background and foreground colors from the album art. Test: manual, play different songs Bug: 36561228 Merged-In: I9c3c962fa59eb70ef9b2d4893b939be6e1ee1ab0 Change-Id: I9c3c962fa59eb70ef9b2d4893b939be6e1ee1ab0
/frameworks/base/packages/SystemUI/tests/Android.mk
|
fb49ffc96a724c196fbc3624cca5f7e20e64e10e |
|
21-Apr-2017 |
Selim Cinek <cinek@google.com> |
Extracting the notification colors based on the album art Media notifications are now extracting the background and foreground colors from the album art. Test: manual, play different songs Bug: 36561228 Change-Id: I9c3c962fa59eb70ef9b2d4893b939be6e1ee1ab0
/frameworks/base/packages/SystemUI/tests/Android.mk
|
1cbf5fbd7ac47a3cbcb4a8910a1dcdd7b7845373 |
|
30-Mar-2017 |
Jason Monk <jmonk@google.com> |
Switch cast over to support library dialog Makes UI more consistent and removes the cast detail panel from QS. Test: visual Change-Id: I9a70b9695511c5f1e4235a838a071079506963a6 Fixes: 35407111
/frameworks/base/packages/SystemUI/tests/Android.mk
|
a7773c2fb1aa168ba57b2bb12b300b11ff5f0a66 |
|
14-Mar-2017 |
Paul Duffin <paulduffin@google.com> |
Change dependency to standard mockito-target-minus-junit4 The mockito-updated-target-minus-junit4 target was added because some tests needed a later version of mockito than was available through mockito-target-minus-junit4. Since the latter has now been upgraded to 2.7.13 that is no longer true and so users of mockito-updated-target-minus-junit4 can be switched to use mockito-target-minus-junit4 instead. Bug: 32912773 Test: make checkbuild && runtest systemui Change-Id: If7e4dd26d7d0e93731856e9739a048c89a835333
/frameworks/base/packages/SystemUI/tests/Android.mk
|
587b60282e4d9f9cb4bd02df0bb13e69d098b0db |
|
16-Mar-2017 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "frameworks/base: Add APCT tests to the device-tests suite."
|
473a16e492f0e0b0f726d4351214783458466d2c |
|
15-Mar-2017 |
Simran Basi <sbasi@google.com> |
frameworks/base: Add APCT tests to the device-tests suite. This CL adds the APCT tests within this project to a similar suite as CTS known as device-tests. The current method of running APCT tests in the infrastructure is unaffected. Bug: 35882476 Test: `make dist device-tests -j` and local builds of continuous_instrumentation_tests & continuous_native_tests Change-Id: Ifa382fe691842c1cd76897775b9e2a1653449eb5
/frameworks/base/packages/SystemUI/tests/Android.mk
|
340b0e5216b4fcc435e0459b1ca46155a572100d |
|
08-Mar-2017 |
Jason Monk <jmonk@google.com> |
Move out test utilities to a Testables library Test: runtest --path frameworks/base/tests/testablets/tests && runtest systemui Change-Id: Ideef4aef5f26136b1741c556b9be5884f38842a0
/frameworks/base/packages/SystemUI/tests/Android.mk
|
af736c9e996a8b0dcf287e6ff264c5a1f8ac50e8 |
|
18-Feb-2017 |
Colin Cross <ccross@android.com> |
resolve merge conflicts of e86b78a57404 to master Test: none Change-Id: I8bf02f8198d003c4453cc59b7a3bccdff688ca15
|
254a418e97e02f43d1f25ea801d67e1bdf498d65 |
|
20-Jan-2017 |
Colin Cross <ccross@android.com> |
Enable multidex for SystemUITests Test: builds Change-Id: I82aa81405f635165716c39191082836dae8ce819
/frameworks/base/packages/SystemUI/tests/Android.mk
|
23f85ec14dab49b2c525dc266d2a1f74f7f9d07c |
|
31-Jan-2017 |
Jason Monk <jmonk@google.com> |
Move Keyguard to SystemUI Test: make Change-Id: I3abb67e2b022737d2aa0226bb07f3966ad68fff7
/frameworks/base/packages/SystemUI/tests/Android.mk
|
27a52fa86bd279407575192fc9842b6a54624cfb |
|
01-Feb-2017 |
Chris Wren <cwren@android.com> |
port status bar logs to Tron V2 Bug: 33303260 Test: runtest --path frameworks/base/core/tests/coretests/src/com/android/internal/logging/legacy/ && runtest --path frameworks/base/packages/SystemUI/tests/src/com/android/systemui/statusbar/phone Change-Id: I7746b846247e930617f0b440217635e71ed58bb5
/frameworks/base/packages/SystemUI/tests/Android.mk
|
ccb04450279c53eda250ac3e20b75cd07bcd1f7e |
|
10-Jan-2017 |
Paul Duffin <paulduffin@google.com> |
Prepare for removal of legacy-test from default targets In preparation for removing junit classes from the Android API the legacy-test target will be removed from the TARGET_DEFAULT_JAVA_LIBRARIES. This change adds explicit dependencies on junit and/or legacy-android-test to ensure that modules will compile properly once it is removed. (cherry picked from 6387604f9e672ece85e07c4bcbd7be396867f06f) Bug: 30188076 Test: make checkbuild Merged-In: I13e88297731253420e4e5f5291d503f13a39a156 Change-Id: I58446eb8c45d8ac2bcdbc9fa40d1321e811bdd4b
/frameworks/base/packages/SystemUI/tests/Android.mk
|
8aeb59ebcd50a510d024dc082fa17b192074c63d |
|
10-Jan-2017 |
Paul Duffin <paulduffin@google.com> |
Prepare for removal of legacy-test from default targets In preparation for removing junit classes from the Android API the legacy-test target will be removed from the TARGET_DEFAULT_JAVA_LIBRARIES. This change adds explicit dependencies on junit and/or legacy-android-test to ensure that modules will compile properly once it is removed. Bug: 30188076 Test: make checkbuild Change-Id: I13e88297731253420e4e5f5291d503f13a39a156
/frameworks/base/packages/SystemUI/tests/Android.mk
|
26ad85a646a2480336c4947ff143f0c5d2fbf63d |
|
08-Dec-2016 |
Jason Monk <jmonk@google.com> |
Switch sysui to updated mockito target Some updates required for tests to pass. Also did a little cleanup of bad verify matching. Test: runtest systemui Change-Id: I75b9f34ab7e9af111dafd5a648840893e1cee434
/frameworks/base/packages/SystemUI/tests/Android.mk
|
4f70b9cfd408a94330024c79643124cca25987b4 |
|
26-Oct-2016 |
Jason Monk <jmonk@google.com> |
Faster plugin updating from UI control Send a broadcast back and forth to speed up the rate at which plugins are enabled or disabled. Also update make files to handle exclude tests better. Test: Manual Change-Id: Ic8f45c663c3a5e5fd4b3e9e2f79480e155845c14
/frameworks/base/packages/SystemUI/tests/Android.mk
|
d05651790af7c3dced153876de6db00366f9f9e5 |
|
16-Sep-2016 |
Jorim Jaggi <jjaggi@google.com> |
Add latency tracking for checking PIN (1/2) Also move tags to Keyguard as we need it in Keyguard. Change-Id: I718581cb4081830da1c3a2f4ad9b9f0ec6f09ae5
/frameworks/base/packages/SystemUI/tests/Android.mk
|
fcdcf7f636ada244a635328e25fdc03959468c8e |
|
19-Sep-2016 |
Jason Monk <jmonk@google.com> |
Merge "Plugins for sysui"
|
86bc33188948e7b6beb07dbb5ddba59b5ea3c1fc |
|
16-Aug-2016 |
Jason Monk <jmonk@google.com> |
Plugins for sysui Why this is safe: - To never ever be used in production code, simply for rapid prototyping (multiple checks in place) - Guarded by signature level permission checks, so only matching signed code will be used - Any crashing plugins are auto-disabled and sysui is allowed to continue in peace Now on to what it actually does. Plugins are separate APKs that are expected to implement interfaces provided by SystemUI. Their code is dynamically loaded into the SysUI process which can allow for multiple prototypes to be created and run on a single android build. ------- PluginLifecycle: plugin.onCreate(Context sysuiContext, Context pluginContext); --- This is always called before any other calls pluginListener.onPluginConnected(Plugin p); --- This lets the plugin hook know that a plugin is now connected. ** Any other calls back and forth between sysui/plugin ** pluginListener.onPluginDisconnected(Plugin p); --- Lets the plugin hook know that it should stop interacting with this plugin and drop all references to it. plugin.onDestroy(); --- Finally the plugin can perform any cleanup to ensure that its not leaking into the SysUI process. Any time a plugin APK is updated the plugin is destroyed and recreated to load the new code/resources. ------- Creating plugin hooks: To create a plugin hook, first create an interface in frameworks/base/packages/SystemUI/plugin that extends Plugin. Include in it any hooks you want to be able to call into from sysui and create callback interfaces for anything you need to pass through into the plugin. Then to attach to any plugins simply add a plugin listener and onPluginConnected will get called whenever new plugins are installed, updated, or enabled. Like this example from SystemUIApplication: PluginManager.getInstance(this).addPluginListener(OverlayPlugin.COMPONENT, new PluginListener<OverlayPlugin>() { @Override public void onPluginConnected(OverlayPlugin plugin) { PhoneStatusBar phoneStatusBar = getComponent(PhoneStatusBar.class); if (phoneStatusBar != null) { plugin.setup(phoneStatusBar.getStatusBarWindow(), phoneStatusBar.getNavigationBarView()); } } }, OverlayPlugin.VERSION, true /* Allow multiple plugins */); Note the VERSION included here. Any time incompatible changes in the interface are made, this version should be changed to ensure old plugins aren't accidentally loaded. Since the plugin library is provided by SystemUI, default implementations can be added for new methods to avoid version changes when possible. ------- Implementing a Plugin: See the ExamplePlugin for an example Android.mk on how to compile a plugin. Note that SystemUILib is not static for plugins, its classes are provided by SystemUI. Plugin security is based around a signature permission, so plugins must hold the following permission in their manifest. <uses-permission android:name="com.android.systemui.permission.PLUGIN" /> A plugin is found through a querying for services, so to let SysUI know about it, create a service with a name that points at your implementation of the plugin interface with the action accompanying it: <service android:name=".TestOverlayPlugin"> <intent-filter> <action android:name="com.android.systemui.action.PLUGIN_COMPONENT" /> </intent-filter> </service> Change-Id: I42c573a94907ca7a2eaacbb0a44614d49b8fc26f
/frameworks/base/packages/SystemUI/tests/Android.mk
|
fd61ccfb75b7b038691f90be248843842e61eba0 |
|
01-Sep-2016 |
Allen Hair <allenhair@google.com> |
Fine tune code coverage filters for SystemUI tests. am: 8fef05f2c1 am: 2d0504edbf am: dcb4f1aaaa Change-Id: Ie817b5126c3d9e18385aa8ea8471fcd629bb7cfa
|
a946492d04853370714a19ff616cc58929f2c47e |
|
31-Aug-2016 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "Fix systemui tests on APCT."
|
33c623677d14bc49a7f2a0e47d9545917275ab55 |
|
31-Aug-2016 |
Geoffrey Pitsch <gpitsch@google.com> |
Fix systemui tests on APCT. Different mockito library for junit4. This causes class loading failures for them but not our builds. Change-Id: Iae4ba584f83e0ab78505fa822a74f5998fbca395
/frameworks/base/packages/SystemUI/tests/Android.mk
|
8fef05f2c11e6f9f90e8c139bb7af42581941f4f |
|
29-Aug-2016 |
Allen Hair <allenhair@google.com> |
Fine tune code coverage filters for SystemUI tests. Bug: 28269038 Change-Id: Iece993a76b39873170c4ae0b2d1cd2dd5445e3c2
/frameworks/base/packages/SystemUI/tests/Android.mk
|
63180a075424eb886b686724b0872aa7362e20a9 |
|
30-Aug-2016 |
Allen Hair <allenhair@google.com> |
Configure code coverage filters. am: 02fd609460 am: 15b70213a4 am: 8b931e08d0 Change-Id: If94db4d01eb5ff4a9f463200d529b0054899bcd5
|
2c403db659db615831d8bd02661f8769c7762241 |
|
26-Aug-2016 |
Geoffrey Pitsch <gpitsch@google.com> |
Convert SysUI tests to use JUnit4 Run tests with android.support.test.runner.AndroidJUnitRunner, modification to runtest target in separate CL. No longer inherit from TestCase, stripped unneeded code from SysuiTestCase, which now assigns mContext via InstrumentationRegistry.getTargetContext(). Can no longer create Handlers with default constructor, Looper.myLooper() was never able to receive messages in tests and it is now enforced that you pass the Looper.getMainLooper(). Change-Id: I13f499175a459cef1a554431911f4b21126e126e
/frameworks/base/packages/SystemUI/tests/Android.mk
|
02fd60946005e5f64650032057029f089ae49e60 |
|
26-Aug-2016 |
Allen Hair <allenhair@google.com> |
Configure code coverage filters. Bug: 28269038 Change-Id: If4dfb769d543e70faea7200dc1da15c50a83270f
/frameworks/base/packages/SystemUI/tests/Android.mk
|
38e89667e30063d29bb56bea23c1976c062dc631 |
|
25-Jun-2016 |
Adam Lesinski <adamlesinski@google.com> |
Build SystemUI and Keyguard with AAPT2 Bug:29462255 Change-Id: I0bd6da7da21927d185ff230c81aac390cfa8029d
/frameworks/base/packages/SystemUI/tests/Android.mk
|
8138058a46323a9ca83a1eb33f64a0d83c4d5503 |
|
01-Jul-2016 |
Adam Lesinski <adamlesinski@google.com> |
Revert "Build SystemUI and Keyguard with AAPT2" Looks like SystemUI's manifest may be corrupt. This reverts commit 91f576081fe67f2742980f75c17d11e36f7c60e1. Bug:29939875 Change-Id: I06e5f3cbc4629a67d254a8fcfcb9749b317aef5f
/frameworks/base/packages/SystemUI/tests/Android.mk
|
91f576081fe67f2742980f75c17d11e36f7c60e1 |
|
25-Jun-2016 |
Adam Lesinski <adamlesinski@google.com> |
Build SystemUI and Keyguard with AAPT2 Bug:29462255 Change-Id: I9a886b4d17a7dbc4cfd7b4f8d398138f00df04a7
/frameworks/base/packages/SystemUI/tests/Android.mk
|
634acb9712f2627acf9279a78d120ea2da1e0464 |
|
14-Apr-2016 |
Yao Chen <yaochen@google.com> |
Add CarVolumeDialogController in SystemUI for Android Auto. Cars usually have an external audio module. When Android is serving as the car's headunit, users should be able to adjust the car's volume through SystemUI. The following changes are made to make it work: + Load VolumeDialogController from SystemUIFactory + Added CarSystemUIFactory + Added CarVolumeDialogController which extends VolumeDialogController and it uses CarAudioManager as source of truth for volume controls. + Some refactor in VolumeDialogController to make it easier for subclasses to override volume controls. Note that CarAudioManager does not completely replace AudioManager. Majority of code in VolumeDialogController still applies in the car use case, so I made CarVolumeDialogController a subclass of VolumeDialogController instead of making them peers. Bug: 27595951 Change-Id: Id4adec7281e41aa71f3de034e5b88a32a89be305
/frameworks/base/packages/SystemUI/tests/Android.mk
|
4cc2a58ed2b3e53f6fe8c182f239d08df1caac38 |
|
25-Feb-2016 |
Adrian Roos <roosa@google.com> |
Fix duplicate eventlogtags warnings Moves the protos and event log tags into a library, so the build system doesn't think they're duplicates. Bug: 27151225 Change-Id: Ic96b6b811d4813a4c48940081ea77b12fb23f0bc
/frameworks/base/packages/SystemUI/tests/Android.mk
|
b58c46acec2e270f24ca587a64298f06cefb09cb |
|
27-Jan-2016 |
Sid Soundararajan <ssoundar@google.com> |
Initial Commit of a Horizontal Grid View based recents UI for TV. Change-Id: I048210e6fc91abafa41300ccb219b7bb9c84e835
/frameworks/base/packages/SystemUI/tests/Android.mk
|
87ccd55e8a90ff5d1c30f852941d523a83ab735a |
|
12-Dec-2015 |
Jason Monk <jmonk@google.com> |
Switch Tuner to support prefs (and some improvements) Change-Id: I2ef62c0c56d4af69f9f34e1cfd297999d59b7da6
/frameworks/base/packages/SystemUI/tests/Android.mk
|
c29ff0025bf0b1f43b34fe3e2dd6f043b61421ef |
|
21-Nov-2015 |
Winson <winsonc@google.com> |
Adding history view. - Initial changes to show a history view within Overview (behind tuner flag) - Restoring the task view dim in the stack Change-Id: I0503d11768736c86f3145942404391dfacd0ddd6
/frameworks/base/packages/SystemUI/tests/Android.mk
|
190fe3bf88388fcb109af64571e3baa0d01f1c37 |
|
20-Oct-2015 |
Winson <winsonc@google.com> |
Refactoring secondary user recents logic. - Removing old broadcasts in favor of direct aidl interface between system and secondary users. Also moving user specific implementation into RecentsImpl, allowing Recents to handle proxying between users. Change-Id: I4bd5ef1d1ee47309b7c754f50a5e8b2e2aab988f
/frameworks/base/packages/SystemUI/tests/Android.mk
|
7232332dc963c2ce55dda1a3a0367080d5494503 |
|
24-Jul-2015 |
Blazej Magnowski <johnasselta@google.com> |
System to track touch and sensor events before unlocking the phone Added a new component which tracks touch and sensor events and also events like showing the bouncer tapping a notification and others. The collection is enabled when the screen is turned on and is disabled after the phone is unlocked. The data is saved in a protobuf file in internal storage in a directory called "good_touches". There is also an option to collect events which end with the screen turning off. These are saved in the "bad_touches" file. Everything is hidden behind the ENABLE_ANALYTICS flag which is set by default to false and can be turned on only if Build.IS_DEBUGGABLE is true. Also behind the ENFORCE_BOUNCER flag the class shows the bouncer before expanding a notification, showing quick settings or launching an affordance from one of the bottom corners. Change-Id: Iaeae0fb7a0d9c707daf7a270201fa5b1cd84c74a
/frameworks/base/packages/SystemUI/tests/Android.mk
|
2ba4ce6a064e29ee3415ff8c2b4a9bbcff937a6c |
|
13-Jan-2015 |
Jason Monk <jmonk@google.com> |
Create SettingsLib This will hold common code that SystemUI and Settings (and others) will share. Bug: 19180466 Change-Id: I6614b31d6c3b0a2d426a2aa8ce66725245339d22
/frameworks/base/packages/SystemUI/tests/Android.mk
|
29f7a7b0ae2264651c176ef50cc21cf9131247e3 |
|
17-Nov-2014 |
Jason Monk <jmonk@google.com> |
SysUI Tests: Make tests not break SysUI Now you can run the tests without getting the blank broken sysui. The tests instrument themselves so they include all of the source they need to run rather than piggybacking on the sysui process. A couple of changes were needed for this. The xml files cannot reference com.android.systemui, instead they must use res-auto. The tests can no longer make privileged calls, so some restructuring to avoid those calls was needed. Bug: 18222975 Change-Id: I67b794af854f1420583d48960bd6e52ca753b56d
/frameworks/base/packages/SystemUI/tests/Android.mk
|
f13b4b39f266e43239e40e3bf7d6997600555068 |
|
07-Nov-2014 |
Jason Monk <jmonk@google.com> |
SysUI: Add basic test coverage for signal levels Add some tests that verify for varios wifi, and mobile signal strengths and types that the correct icons are sent out in the callbacks. Still in prep for MSIM refactoring. Bug: 18222975 Change-Id: I477bf9a90e5c32fb1cba9c150ec6314f4b707108
/frameworks/base/packages/SystemUI/tests/Android.mk
|
e0cdb6079e9e9e8b87a71d67ef5aa1dc0e3e6840 |
|
05-Nov-2014 |
Jason Monk <jmonk@google.com> |
Prepare for testing the NetworkControllerImpl This will allow us to add some test cases to verify that under certain phone/signal conditions we get out the icons we expect. This will let us break less things when refactoring for MSIM. Bug: 18222975 Change-Id: I7bd3e66e7de6b30fede72e40fb6aa37dd523336c
/frameworks/base/packages/SystemUI/tests/Android.mk
|
caf30a18b52471ebfbc6ae5e853c9a0b9d44905b |
|
29-Jul-2011 |
Brett Chabot <brettchabot@android.com> |
Add functional test for screenshots. Change-Id: Ice2cbc656f9814da7d0634644a250c1af9243ad1
/frameworks/base/packages/SystemUI/tests/Android.mk
|