Animators that are created with Object values may have undefined
behavior when those objects are changed outside of the animator itself.
For example, an animator created with a start Rect and end Rect
will animate the bounds between those two objects. But if the caller
changes either the start or end rect before or during the animation,
that will affect the values used on every frame of the animation.
Issue #28304520 Strange interpolation of property values holder values
Change-Id: Id6ac19c8369ae34450e6b53d68f5e492b27c577e
For non-persistent debug settings, mDebugApp and mWaitForDebugger flags
will only be restored when we get attachApplication. If the process is
already running, we can't wait for debugger and there will be no
attachApplication calls coming.
We should leave the settings unmodified, otherwise after two such calls,
both mDebugApp and mOrigDebugApp will point to the same app, and the
debug settings can never be restored.
bug: 27931552
Change-Id: Id53e21bbe154f45bf2ca12bb5d7fd56279bae653
- We were incorrectly setting the OnClickListener to null to try to do
this, which still causes the touch event to be consumed by the button
view, so instead we should just set the clickable state directly.
Bug: 27859552
Change-Id: Ida3b4a467c6f325ce8fe5a90b0b77c2bdda5a936
We used the system proterties as a shared memory mechanism
to propagate information to local settings caches when the
content has changed and the cache should be cleared. The
system properties are unfortunately updated asynchronously
leading to cases where clients may read stale data.
This change adds a simple int array data structure backed
by shared memory which guarantees individual values are
atomically read and updated without memory tear. Multi-
index opearations are not synchronized between each other.
The settings provider is using the new data structure to
propagate the settings generation which drives when caches
are purged.
We have a single memory array keeping the generation for
different settings tables per user. Since memory array is
not a compact data structure and the user space exceeds
the memory array size we use an in-memory map from keys
to indices in the memory array where the generation id of
a key is stored. A key is derived by the setting type in
the 4 most significant bits and the user id in the 28 least
significant bits.
The mapping from a key to an index is cleared if the user is
removed and the corresponding index in the memory arry is
reset to make it available for other users. The size of the
memory array is derived from the max user count that can be
created at the same time.
bug:18826179
Change-Id: I64009cc5105309ef9aa83aba90b82afc8ad8c659
am: 86c6f97
* commit '86c6f97bce6beb84e826af02e26e4fd256b385f8':
Update the N Preview docs now that Studio 2.1 is stable. bug: 28342771
Change-Id: I9d1d81f463768db9f841fe639229702fbca807e6
When setting the vertical location of the gear we need the collapsed
height of the parent, the parent might not be fully laid out so move
setting the vertical location into onLayout instead
Bug: 28390732
Change-Id: I7c1bf14a54e9f1ef0a693fa13e1a6533f5967631
am: 39a59d0
* commit '39a59d0c45df2fd724dde27caaab7622f1994673':
Update the N Preview docs now that Studio 2.1 is stable. bug: 28342771
Change-Id: I24fe1b61520c956e61c490b96ae8bd98b5aed017
If an application(in /data) that other user installed it initially
is appended as system app later, owner user can not use the system app.
The reason this issue occurs is that the owner user's installed flag
is set false when the application was installed by other user
and the installed flag is not updated when the application is appended
as system app later.
So, we fix like as setting the installed flag to true
when the application is appended as system app.
Bug: 28183865
Change-Id: I0b4da5e0bb77fb3baf86d0453e6637a230b104ba
am: 96e6abb
* commit '96e6abb248938118fede112304ef80b3b9f70084':
Update the N Preview docs now that Studio 2.1 is stable. bug: 28342771
Change-Id: If270f5a042c29b62fcb0834e153277ea3c1619ee
Usually wallpaper target gets updated when some wallpaper target window
finishes drawing. However in some cases, Recents app could be set to
visible again before its stopped. (Which could happen when we started
opening transition into some app with a saved surface, but the app draws
so slow so that when user pressed Recents button again, the app still
hasn't delivered first frame.) In this case, the surface is already
drawn and we won't get a finish drawing again. We need to make sure the
wallpaper target is updated.
bug: 27742244
Change-Id: I8ff53f15f95bae8a99a5a0fd11e24e0186dc3345
Fine tune the audio gain for Bluetooth Absolute Volume.
Use 50%, 70% and 85% for lowest volume steps 1, 2 and 3.
Thus the volume change sounds smoother, more linear.
When remote end tune volume out of mute, we should also
tune the audio gain for the lowest volume steps.
Bug: 26694114
Change-Id: I298a334a4b40ddb87495fda1935349bfce8b0537
am: f2f64b7
* commit 'f2f64b73444a7f06423e26c8fd465b82da718b23':
docs: Added entry in USB vendor ID table for HP.
Change-Id: I89e5ec7da0a2c585ccf1cd5b899196a157ccebe0
am: 599796e
* commit '599796ecef67e28c1c52dc06b1bf7401d9f77a33':
docs: Added entry in USB vendor ID table for HP.
Change-Id: I94a442b96b7b9b838c27179233b09bef5298d800
am: b8767b7
* commit 'b8767b7f6d70b21f024613c5d933ff62cf2e0918':
docs: Added entry in USB vendor ID table for HP.
Change-Id: I7ccd56011ba1199b64ffab85d966910ffb9e91be
