am: c7984b5
* commit 'c7984b5d62b511a17f3030641d44efc2b147a776':
Update the N Preview docs now that Studio 2.1 is stable. bug: 28342771
Change-Id: I01396349b0ec8e88be46888f8a44f8f93c4c0f8d
am: c78400e
* commit 'c78400e09598850ff9404933f2d3cfc887a92339':
docs: Added entry in USB vendor ID table for HP.
Change-Id: I6d69fbd8324c77dc64bf87e0878c249a9cd099e0
am: 0a33248
* commit '0a33248b1fe6a109bf33dbdf65497b00f12cba35':
Update the N Preview docs now that Studio 2.1 is stable. bug: 28342771
Change-Id: I91e30aadca32f5cef8f00e8cd52f6e8aa90b2dd9
am: 8f00192
* commit '8f001929cdf8c4aedc544da3ec99c7c1555351de':
Docs: Added that Method References work with earlier API levels
Change-Id: I913b328242d944be6b4718cc3c32d095dc4b386d
am: 1d52e49
* commit '1d52e49be27be077fafb16fcf700da80d7abc87b':
Docs: Minor fix and restructuring to Vulkan validation-layer doc to prevent devs from corrupting their NDK install.
Change-Id: I6c0cb2412f8a84d90718bbcc99773328a2ca7389
We now have a null object instead of null values and
there was a place where we returned null instead of
the correct null object.
bug:28423485
Change-Id: I2626768acdf8d19fc94aa5e978eb057818450fa5
Clarifying region used for magnification as "magnificationRegion",
both in the public API and in the code. There's been significant
confusion about what "magnfifiedRegion" means. Removing
"availableRegion" from everywhere except where it's required, as
that region was identical to magnified/magnification region.
Trying to shut down magnification was a complex situation where
animations in progress and new magnification requests were tricky to
handle correctly. It was not possible to guarantee that the
magnification callbacks were unregistered consistently. There were
at least two situations that led to phone restarts:
1. If a triple tap was detected between unregistering the callbacks
and shutting down the input filter. In this case the magnification
request would go through.
2. If an animation had just started when magnification was turned
off, so the current magnification was 1.0 but the animator was
about to change it. In this case the callbacks would be unregistered,
and then the animator would start changing the magnification.
This change makes registering and unregistering magnification atomic.
It also makes MagnificationController stick around indefinitely once it
is created, registering and unregistering as needed to support
magnification gestures and services that control magnification. Services
that merely query the status of magnification no longer register for
callbacks.
One part of shutting down is turning off the animation and guaranteeing
that it won't try to make further changes. Adding a flag to
SpecAnimationBridge and a lock in that class so we can guarantee that
nothing happens when we aren't registered for magnification callbacks.
Also reconfiguring all accessibility options when a service stops to
make sure that only the features required by the current configuration
are enabled.
Bug: 27497138
Bug: 27821103
Change-Id: If697cbd34b117d82c8eee1ba7d0254089ee4241d
Framework edition
If a loader is already started when we try to rollback a content
change, force a new load instead of simply setting the flag to refresh
next time.
Bug 28406183
https://code.google.com/p/android/issues/detail?id=208278
Change-Id: If11d79088d30dd2dc48cf1b3d2882f3712b6cddb
am: 2c3f2c4
* commit '2c3f2c4da90613bafc93ed34e53867da10084212':
Only log when system UID finds missing data paths.
Change-Id: I45b729a18db114af24beb17d93243c4d32203236
