| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Hacky prototype needs a private API to enable
Change-Id: I21e0ddf3cdbd38a4036354b5d6012449e1a34849
|
|
|
|
|
|
|
|
| |
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
|
|\
| |
| |
| |
| |
| |
| | |
casting." into klp-dev
* commit 'e5ae0bfdf7933d7ea8bec94f0c7e25347c423710':
Finalize assets for screen casting.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
|\ \
| |/
| |
| |
| |
| |
| | |
Conflicts:
tools/layoutlib/bridge/src/android/view/IWindowManagerImpl.java
Change-Id: I9fd35ea9166ec73ce1f9f6154aa4ec87e79e20cb
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
|\ \
| |/
| |
| |
| | |
* commit '9ffc4a65e51ae8695be0531c6fae0d33301ded60':
UI tweaks.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
|\ \
| |/
| |
| |
| |
| |
| | |
integrate with remote displays." into klp-dev
* commit 'c2b652fd4d386b79dc99af249b6ad3844e53fdf1':
Add media router service and integrate with remote displays.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| |
| |
| | |
This reverts commit 52d8aa79a31c5042d2b43d06f08fa28489b27d1b.
Change-Id: Ic706e0fb469931664499d00fa3a221726b258673
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Change to add "throws IOException" to android.media.MediaCodec
(createByCodecName|createDecoderByType|createEncoderByType). The exception was
previously thrown through the native JNI, but not explicitly declared.
Requires changes to existing code for declaration compatibility.
Bug: 11364276
Change-Id: Ia0d3481397285cb1503bedde37d4651934b3a481
Signed-off-by: Andy Hung <hunga@google.com>
|
|\ \
| |/
| |
| |
| |
| |
| |
| |
| | |
I536021b9,I6eb541c9,I6ac08eca into klp-dev
* commit '09de7975fead1b47ea78f6f812a2f649e5dfb31d':
SmartCamera: Fix to build against latest camera2 api
Camera2Tests: update SmartCamera for async api
Camera2Tests: Add SmartCamera App
|
| |
| |
| |
| |
| | |
Bug: 10818732
Change-Id: I536021b9663331532e2f4c21a4fc0f3de5da9aa9
|
| |
| |
| |
| | |
Change-Id: I6eb541c96ee50756c35e7785fdae63e8e45e2726
|
| |
| |
| |
| |
| | |
Bug: 10818732
Change-Id: I6ac08ecab3a1e04116be2f7764d0d5d4f29c5cd9
|
|\ \
| |/
| |
| |
| |
| |
| | |
into klp-dev
* commit '13e9158bc224bb94f5fef3644635a2f38953b26d':
Delete BrowserTestPlugin.
|
| |
| |
| |
| |
| |
| |
| | |
The new WebView doesn't support plugins.
Bug: 10427705
Change-Id: I4678bf4771d402bec882193c7a2f3d05d918f042
|
|\ \
| |/
| |
| |
| |
| |
| | |
HttpHeaderTest.testCacheControlMultipleArguments.
* commit '2101df58f975b352a289505351a029ed9fa4edbd':
Delete HttpHeaderTest.testCacheControlMultipleArguments.
|
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
|\ \
| |/
| |
| |
| | |
* commit '033837dd6bf32b33d9a67d340efd167f94bf80cf':
Make fading transitions work better
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
|\ \
| |/
| |
| |
| |
| |
| | |
manual camera2 test apps" into klp-dev
* commit 'a7dd66a4709353cd27b4482be73d2b3804cbeaa6':
Camera2Tests: create new directory for manual camera2 test apps
|
| |
| |
| |
| |
| | |
Bug: 10818732
Change-Id: Idbc7e370d43a95e8f647541ab1e20071c212382d
|
| |
| |
| |
| |
| |
| |
| | |
The wildcard imports interfered with the new typedef annotations (and
99% of the tests were using explicit imports anyway.)
Change-Id: I3784b9d700131fe4a0ba30283f052820b2fa5122
|
|\ \
| |/
| |
| |
| |
| |
| | |
klp-dev
* commit '913c023387c319f6c7b1e4878a4d0d07f8624f78':
Add exclude() methods to Transition
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
|\ \
| |/
| |
| | |
Change-Id: I1ce1b48a9fb954caf4fd15237f2f608ac9c478fe
|
| |
| |
| |
| |
| |
| |
| | |
Issue #10460684 KLP API Review: android.view.transition and android.animation
Issue #10570740 Transitions: inflate transition targets from xml
Change-Id: I7a3f6d3aece2fcafc5efd555d033f79e86635c98
|
|\ \
| |/
| |
| |
| |
| |
| | |
into klp-dev
* commit 'cfb0048b714fa52e8bfb9884357d36c1490a3edc':
Remove WebViewClassic specific test code
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Bug: 10427705
These tested internals of WebViewClassic and will no longer build when
that is removed
Change-Id: I42af538dcb0343e9eff0b3fa85d7ff39f19c7c61
|
|\ \
| |/
| |
| |
| |
| |
| | |
PathCache::trim() Bug #10347089" into klp-dev
* commit 'c1acf7994a975903320ec8146c62118b651debc4':
Second attempt at avoiding infinite loop in PathCache::trim() Bug #10347089
|
| |
| |
| |
| |
| |
| | |
Bug #10347089
Change-Id: I70f5a3933e848632473acc6636c88be5dc6ac430
|
|/
|
|
| |
Change-Id: I3d035d24a75e09db13d136a22bd7dbd326d0ce36
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
See external bug #58344
Change-Id: Iecd6c41fc8076cd76add2335d3442a6dd8878f12
|
|
|
|
| |
Change-Id: I8e7b6dd092442f3870aa1a36bd2a7cd974177146
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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 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
|
|
|
|
| |
Change-Id: Iac5035f9c5884a9f9d5acb38132bb128d7a55249
|
|
|
|
| |
Change-Id: I516e333ca85c0e3c08c8fffc157a9e0360af02e5
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
Change-Id: I69b0539df704d80a34cc8f22096657210f5d78ad
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
| |
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
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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 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
|