summaryrefslogtreecommitdiffstats
path: root/tests
Commit message (Collapse)AuthorAgeFilesLines
* Add support for custom TXT records in NSDChristopher Lane2014-04-141-0/+163
| | | | Change-Id: I8e6dc9852ad4d273c71ad6a63a7fbd28a206806d
* Plumb display power state through display manager.Jeff Brown2014-04-101-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Declare a new method, Display.getState() to retrieve the actual power state of a display. Improved documentation for Intent.ACTION_SCREEN_ON and Intent.ACTION_SCREEN_OFF to clarify what they really mean in terms of the interactive state of the device. Deprecated PowerManager.isScreenOn() and replaced it with PowerManager.isInteractive() with a more suggestive name and better documentation. Redirect display power state changes to go through the display manager first and only then head over to the power manager for legacy compatibility. Eliminated the bright here and woke here policy flags since they were unused. Simplified the input dispatch policy somewhat. Ensure that screen wake locks are respected up until the point when dozing really begins. Fixed a regression in DreamService where onDreamingStarted might be called before onWindowAttached. Bug: 13133142 Bug: 13472578 Bug: 13929355 Bug: 13760290 Change-Id: Iabef96921dd554ce3768fb18619cefc3230b5fb0
* resolved conflicts for merge of c45ff35f to klp-modular-devChristopher Tate2014-03-053-0/+18
|\ | | | | | | Change-Id: Id1799e49891dc72e2e9c55fd9f418ceee94a7875
| * am 1efc6e52: am 1d13f13d: Merge "Adapt to underlying changes in the PBKDF2 ↵Christopher Tate2014-03-053-0/+18
| |\ | | | | | | | | | | | | | | | | | | implementation" into klp-dev * commit '1efc6e52d65389463ad52c32df02d68493df0f48': Adapt to underlying changes in the PBKDF2 implementation
| | * Merge "Adapt to underlying changes in the PBKDF2 implementation" into klp-devChristopher Tate2014-03-053-0/+18
| | |\
| | | * Adapt to underlying changes in the PBKDF2 implementationChristopher Tate2014-03-033-0/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We need to specify "PBKDF2WithHmacSHA1And8bit" now in order to get precisely the same output as was previously generated with "PBKDF2WithHmacSHA1". We also now try both when it's ambiguous which was used to generate the archive checksums. Bug 12494407 Cherry-pick from master. Change-Id: I2d6081dd62f50f7d493045150b327ed120de7abd
* | | | am 818f83d9: am bf7b64bd: am be659185: use min app launch time in AppLaunch ↵Guang Zhu2014-03-041-9/+12
|\ \ \ \ | |/ / / | | | | | | | | | | | | | | | | | | | | perf test * commit '818f83d965be3cc1af88a1c700115bff0dccf3a3': use min app launch time in AppLaunch perf test
| * | | am bf7b64bd: am be659185: use min app launch time in AppLaunch perf testGuang Zhu2014-03-041-9/+12
| |\ \ \ | | |/ / | | | | | | | | | | | | * commit 'bf7b64bd30bc1e7fabcfc7f46132f504b30ba97c': use min app launch time in AppLaunch perf test
| | * | use min app launch time in AppLaunch perf testGuang Zhu2014-03-041-9/+12
| | |/ | | | | | | | | | | | | Change-Id: Id3a5872ff29fba5daeff058f0842fd011e50a0a1 (cherry picked from commit 2861a89bed9066e206917c41357a5e589e8482cb)
* | | Add a new "doze mode" based on Dream components.Jeff Brown2014-02-207-0/+280
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When a doze component has been specified in a config.xml resource overlay, the power manager will try to start a preconfigured dream whenever it would have otherwise gone to sleep and turned the screen off. The dream should render whatever it intends to show then call startDozing() to tell the power manager to put the display into a low power "doze" state and allow the application processor to be suspended. The dream may wake up periodically using the alarm manager or other features to update the contents of the display. Added several new config.xml resources related to dreams and dozing. In particular for dozing there are two new resources that pertain to decoupling auto-suspend mode and interactive mode from the display state. This is a requirement to enable the application processor and other components to be suspended while dozing. Most devices do not support these features today. Consolidated the power manager's NAPPING and DREAMING states into one to simplify the logic. The NAPPING state was mostly superfluous and simply indicated that the power manager should attempt to start a new dream. This state is now tracked in the mSandmanSummoned field. Added a new DOZING state which is analoguous to DREAMING. The normal state transition is now: AWAKE -> DREAMING -> DOZING -> ASLEEP. The PowerManager.goToSleep() method now enters the DOZING state instead of immediately going to sleep. While in the doze state, the screen remains on. However, we actually tell the rest of the system that the screen is off. This is somewhat unfortunate but much of the system makes inappropriate assumptions about what it means for the screen to be on or off. In particular, screen on is usually taken to indicate an interactive state where the user is present but that's not at all true for dozing (and is only sometimes true while dreaming). We will probably need to add some more precise externally visible states at some point. The DozeHardware interface encapsulates a generic microcontroller interface to allow a doze dream for off-loading rendering or other functions while dozing. If the device possesses an MCU HAL for dozing then it is exposed to the DreamService here. Removed a number of catch blocks in DreamService that caught Throwable and attempted to cause the dream to finish itself. We actually just want to let the process crash. Cleanup will happen automatically if needed. Catching these exceptions results in mysterious undefined behavior and broken dreams. Bug: 12494706 Change-Id: Ie78336b37dde7250d1ce65b3d367879e3bfb2b8b
* | am dcbde1b0: Merge "libcore_to_document and junit_to_document are no longer ↵Ying Wang2013-12-051-2/+2
|\ \ | |/ |/| | | | | | | | | functions." * commit 'dcbde1b02ad69c18509afd87974c72c3a22f45dd': libcore_to_document and junit_to_document are no longer functions.
| * libcore_to_document and junit_to_document are no longer functions.Ying Wang2013-12-041-2/+2
| | | | | | | | | | | | | | | | They are evaluated only once in the corresponding export .mk file. This fixes build log spam reported in: https://code.google.com/p/android/issues/detail?id=63184 Change-Id: I549eb052272bbdebef8fca697822f5eaa0fe5764
* | Finalize assets for screen casting.Jeff Brown2013-11-132-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | Extend wifi display connection timeout. Show a notification while connecting to wifi display. Ensure that remote display providers are really trusted before connecting to them. Bug: 11257292 Change-Id: Iad0caaa30d7946df818bc75ade071f2e377f8a53
* | Relayout windows that handle their own config change.Craig Mautner2013-11-121-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If a window claims to handle its own configuration change then we won't destroy and recreate its window on a configuration change. Normally that recreation triggers the first layout following orientation change because mHaveFrame is false. Windows that handle their own configuration changes never got a relayout pass following a change in orientation. This change passes the configuration changes that an application handles into the AppWindowToken. If the app says it handles orientation or screen size changes then a relayout will occur when the configuration has changed. Fixes bug 11647107. Change-Id: Ie8d49fd050442ebbdcf0b805087894e3a2fc4be9
* | UI tweaks.Jeff Brown2013-11-111-4/+85
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Hide disabled routes from the chooser. Fix layout of chooser dialog when the settings button is visible and the list is very long to prevent truncation of the settings button. Fix an issue when we fake the route connecting status when a route is selected. The route changed notification needs to be propagated to apps. Fake it better. Immediately disconnect from a route when the connection is lost or a connection attempt fails. Added a few new test displays for this case. Bug: 11257292 Change-Id: I360ab5dc937ad60d97592eab54b19f034519645e
* | Add media router service and integrate with remote displays.Jeff Brown2013-11-077-0/+337
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | This change adds a new media router service whose purpose is to track global state information associated with media routes. This service publishes routes to the media router instance in application processes and handles requested state changes such as selecting or unselecting global routes. The service also binds to remote display provider services which can offer new remote display routes to the system. Includes a test application for manually verifying certain aspects of the operation of the media router service. The remote display provider interface is essentially a stripped down media route provider interface as defined in the support library media router implementation. For now, it is designed to be used only by first parties to publish remote display routes to the system so it is not exposed as public API in the SDK. In the future, the remote display provider interface will most likely be deprecated and replaced with a more featureful media route provider interface for third party integration, similar to what is in the support library today. Further patch sets integrate these new capabilities into the System UI and Settings for connecting remote displays. Bug: 11257292 Change-Id: I31109f23f17b474d17534d0f5f4503e388b081c2
* SmartCamera: Fix to build against latest camera2 apiIgor Murashkin2013-10-153-7/+9
| | | | | Bug: 10818732 Change-Id: I536021b9663331532e2f4c21a4fc0f3de5da9aa9
* Camera2Tests: update SmartCamera for async apiIgor Murashkin2013-10-152-10/+20
| | | | Change-Id: I6eb541c96ee50756c35e7785fdae63e8e45e2726
* Camera2Tests: Add SmartCamera AppBenjamin Hendricks2013-10-15148-0/+20290
| | | | | Bug: 10818732 Change-Id: I6ac08ecab3a1e04116be2f7764d0d5d4f29c5cd9
* Delete BrowserTestPlugin.Torne (Richard Coles)2013-10-1513-1162/+0
| | | | | | | The new WebView doesn't support plugins. Bug: 10427705 Change-Id: I4678bf4771d402bec882193c7a2f3d05d918f042
* Delete HttpHeaderTest.testCacheControlMultipleArguments.Torne (Richard Coles)2013-10-151-38/+0
| | | | | | | | This test depends on internals of the old WebView to work which have already been removed. It doesn't appear to be testing anything useful. Bug: 10427705 Change-Id: I5e93b212c33f22776050b6e1ec639e23f41a1d4a
* Make fading transitions work betterChet Haase2013-09-265-17/+29
| | | | | | | | | | | | | | | | | | | | | | | | | Previously, a Fade transition would only affect a view if its parent hierarchy was not also affected between the start/end states. This caused problems for views which were removed from their parents between scenes when their parents' visibility also changed between those scenes. The effect would be that the transition would fade the parent... but the child would no longer be in that parent, so the user would just see the child view blink out. This fix ensure that views are faded appropriately by fading them regardless the parent hierarchy; if a view is removed from its parent, fade it out. Additionally, if that view has not been removed from its parent, but its parent is no longer parented *and* scene being transitioned from is based on a layout resource file (and thus the views are considered temporary after transitioning), then it is removed from its parent to be faded out in the overlay. Also, renamed TextChange to ChangeText to be more consistent with other transition class names. Change-Id: I4e0e7dfc9e9d95c7a4ca586534b6d204c4f3bae0
* Camera2Tests: create new directory for manual camera2 test appsIgor Murashkin2013-09-181-0/+1
| | | | | Bug: 10818732 Change-Id: Idbc7e370d43a95e8f647541ab1e20071c212382d
* Add exclude() methods to TransitionChet Haase2013-09-1114-43/+43
| | | | | | | | | | | | | | | It would be useful for a transition to declare not just which targets it wants to be run on, but also which targets it wants to avoid. For example, you may not want to animate the items of a ListView, or some other specific target in the view hierarchy. This change adds various exclude*() methods which make it possible to alter a transition to automatically ignore specific views, ids, or classes in the hierarchy. Issue #10692794 Transitions: Need API for excluding targets Change-Id: If38025cdbee537a545e5a4268cbbd763af4622c5
* Transition API changes from API council recommendationsChet Haase2013-09-0446-433/+410
| | | | | | | Issue #10460684 KLP API Review: android.view.transition and android.animation Issue #10570740 Transitions: inflate transition targets from xml Change-Id: I7a3f6d3aece2fcafc5efd555d033f79e86635c98
* Remove WebViewClassic specific test codeJonathan Dixon2013-08-2569-21198/+0
| | | | | | | | | Bug: 10427705 These tested internals of WebViewClassic and will no longer build when that is removed Change-Id: I42af538dcb0343e9eff0b3fa85d7ff39f19c7c61
* Second attempt at avoiding infinite loop in PathCache::trim()Romain Guy2013-08-211-2/+7
| | | | | | Bug #10347089 Change-Id: I70f5a3933e848632473acc6636c88be5dc6ac430
* Support public virtual displays.Jeff Brown2013-08-021-2/+2
| | | | | | | | | Refactor the new private virtual display API to also support creating public virtual displays with various characteristics. This feature requires special permissions and is only intended for use by the system. Change-Id: I44dd19f37cf76ea6d6e313afe42f4a412bd96663
* Fix region clipping bugsRomain Guy2013-08-011-4/+2
| | | | | | See external bug #58344 Change-Id: Iecd6c41fc8076cd76add2335d3442a6dd8878f12
* Fix issue #10115327: MapCollections need to implement equalsDianne Hackborn2013-07-311-0/+59
| | | | Change-Id: I8e7b6dd092442f3870aa1a36bd2a7cd974177146
* Add path ops APIRomain Guy2013-07-302-1/+98
| | | | | | | | | | | | | | | | | | | | | | | | Path ops can be used to combine two paths instances in a single path object. The following operations can be used: - Difference - Reverse difference - Union - XOR - Intersection To use the API: Path p1 = createCircle(); Path p2 = createRect(); Path result = new Path(); result.op(p1, p2, Path.Op.DIFFERENCE); This code will subtract the rectangle from the circle and generate the resulting path in "result." Change-Id: Ic25244665b6691a7df0b0002a09da73d937b553b
* Fix TTS tests.Przemyslaw Szczepaniak2013-07-291-32/+6
| | | | | | | | | | | Fix breakages steaming from recent changes: - onGetLanguage is no longer called anywhere (it's used in API <= 17), tests for it no longer apply. - onLoadLanguage is called as item on synthesis thread queue. To return value to client asap, onIsLanguageAvailable is called as well - added missing expectations for mocks. Change-Id: I205bc406f085e2c2f7e98f8495ddb96ad3701b97
* Okay, I give in, add null key support to ArrayMap and ArraySet.Dianne Hackborn2013-07-251-10/+18
| | | | Change-Id: Iac5035f9c5884a9f9d5acb38132bb128d7a55249
* Fix FrameworkPermissionTests buildColin Cross2013-07-191-1/+1
| | | | Change-Id: I516e333ca85c0e3c08c8fffc157a9e0360af02e5
* Fix minor transition bugs and add capabilitiesChet Haase2013-07-125-0/+238
| | | | | | | | | | | | | | | | | | Some view changes require more flexible transitions than the defaults provided by Crossfade and TextChange - this change supplies some of that flexibility. Also, starting a new transition on a hierarchy undergoing a transition caused the first to get canceled, then the start values to be retrieved. The new transition should actually get the start values from the intermediate state of the views, so we now cancel the previous transition only after the start values have been captured. Issue #9756349 Transitions: Crossfade does not handle interruption/reverse correctly Issue #9295863 Transitions: Add behavior API/flags to various transitions Issue #9275859 Transitions: Improve mechanism for transition interruption Change-Id: I5a8c5a12466ddcab9e84e4880930563fa1216f3b
* Fix minor transition bugsChet Haase2013-07-103-0/+103
| | | | | | | | | | | | | | TransitionGroup.setDuration() was not propagating the new duration to future child transitions correctly. Also, Fade should restore a fully-opaque value when a transition ends, to prevent the problem of mid-stream canceled transitions causing vie3ws to get stuck with partially faded-in alpha values. Issue #9755995 Transitions: TransitionGroup.setDuration() not handled correctly Issue #9756655 Transitions: handle fading cancelation better Change-Id: Id44569c6f4152a26ee382d04c30a2f035a1ebcf3
* Remove NearestImageView from CanvasCompareChris Craik2013-07-093-48/+2
| | | | Change-Id: I69b0539df704d80a34cc8f22096657210f5d78ad
* Refactoring/simplifying Transition code/APIChet Haase2013-06-214-0/+163
| | | | | | | | | | | | | | | | | | | Transitions used to be three phase: - captureValues(): get all relevant property values in the affected view targets - setup(): set appropriate start values for affected views prior to any transitions being played - play(): create/play Animators for affected views Now the second and third phases have been collapsed (and named "play()"). This single step sets initial values for target views and creates any Animators that should be played during the transition. The transition mechanism stores these Animators and then starts them at the appropriate time in the overall transition. Issue #9507585 Transitions: Simplify Transition.play() design Change-Id: I3fc67599b38fe49eee885dc5d32444db90b7703b
* Fix transitions on disappearing view hiearchiesChet Haase2013-06-203-0/+100
| | | | | | | | | | | | | | | | | | | | | | | | Previously, Fade transitions did not work correctly on hirearchies; they only handled individual views. in particular, they would side-effect all fading views by removing them from their parent to fade them out in the overlay of the scene root. This worked for the fade-out transition itself, but caused problems when those same hierarchies were added back in and another Fade was run on the hierarchy, because now all of the views inside that parent node had been removed, so they didn't fade in at all. The fix was to add logic in Visibility to detect when a disappearing view was inside a hierarchy that was also disappearing, and to skip the fade on the views inside that hierarchy, leaving only the top-most disappearing view to be faded out, thus preserving the hierarchy under that faded-out group. Along the way, there were various cleanups, fixes, and refactorings in the transition code, and slight API modifications. Issue #9406371 Transitions: Removing view hierarchy not working correctly Issue #9470255 Transitions: Separate different transitions by Scene Root Change-Id: I42e80dac6097fee740f651dcc0535f2c57c11ebb
* Add test for streaming display contents to an accessory.Jeff Brown2013-06-1834-0/+3005
| | | | | | | | | | There are two applications: a source and a sink. They should be installed on two separate Android devices. Then connect the source device to the sink device using a USB OTG cable. Bug: 9192512 Change-Id: I99b552026684abbfd69cb13ab324e72fa16c36ab
* Merge "ArrayMap is great, so how about ArraySet!"Dianne Hackborn2013-06-121-56/+150
|\
| * ArrayMap is great, so how about ArraySet!Dianne Hackborn2013-06-111-56/+150
| | | | | | | | | | | | | | | | | | | | | | | | Also a few little tweaks to the ArrayMap implementation. Note that these are fairly parallel implementations; I looked at what I could abstract out as a base class, but there isn't really all that much without making the resulting code more general and thus slower. If we kept the data structure for ArraySet the same as map, where the array has two values per entry, then they could probably share a lot of code. I couldn't really bring myself to do that at this point, though... Change-Id: I9e0dd8baa8e1febcc1033ecef61623ad59ce4aae
* | Add dynamic scene creation/transition capabilityChet Haase2013-06-103-0/+88
|/ | | | | | | | | | Add TransitionManager.beginDelayedTransition() to handle starting a transition on the next frame for a given scene root based on all changes that take place between the first call to that method and the next animation frame. Issue #9321937 Transitions: consider batching up multiple scene actions Change-Id: I3fc92b6b4ec5ff42b1e678bcfd385703e32eba2a
* Merge "Additional functionality and performance for ArrayMap"Chet Haase2013-06-071-0/+68
|\
| * Additional functionality and performance for ArrayMapChet Haase2013-06-061-0/+68
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Added equals() and hashCode() to ArrayMap to allow equals() tests of maps with the same key/value pairs to return true. Changed putAll() to handle the case of an empty map faster, just copying the arrays instead of adding elements one by one. Added to ArrayMapTests to test new equals() and copy constructor functionality. Issue #9299310 Optimize ArrayMap copy constructor Change-Id: I1186a0eddd1fd53a0f380c2f3972fc1942cdf879
* | Remove unnecessary allocationsRomain Guy2013-06-061-5/+1
| | | | | | | | Change-Id: Ia561a0a312ca2737d5afa742184f5392bb2f29a3
* | Fix CrossFade transitionChet Haase2013-06-061-0/+2
|/ | | | | | | | Small fixes in CrossFade to handle more general situations. Also, added API to CrossFade to enable different behaviors during the transition. Change-Id: I12d17ab8f8f96be370c070373112ad8a62df9115
* Fix in transition canceling logicChet Haase2013-06-045-7/+40
| | | | | | | | The logic that canceled underlying animations caused a problem when there were more than one animation in the list (due to removing items from a list that was currently being processed elsewhere). Change-Id: Ie207f340b5d7de4ffcf56a26c05ec394abb80224
* Various fixes/cleanup in Scenes and TransitionsChet Haase2013-06-039-2/+182
| | | | | | | | | | | | | | | | setDuration() wasn't handled correctly for TransitionGroup; it should propagate the value to its children. Also, videos with no ids were not being handled correctly. The transition code was using the default id on those views (-1) to store start/end data about the view, causing multiple non-id views to clobber values in the hashmaps. The correct approach should be to ignore default id values - only store information about the view instances, not about the unset ids. Also, added a new test InterruptTest to be used to fix the current behavior of not handling situations where new transitions start while old ones are still taking place. Change-Id: I4e880bdbb33cc26d487bceb0d56e463e72f7621f
* Fix build; update framework tests for WindowManager API changeAdam Powell2013-05-311-1/+1
| | | | Change-Id: I801c455184f2a6771f50e29dc147402db48f9fb7
generated by cgit v1.1 at 2025-02-03 19:13:44 +0000