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
am: 9412176
* commit '94121762ff47728fd8080f45f04cafb55b92079d':
Fix onPrepareActionMode() not being called
Change-Id: Ib8accfd3ffafefd963a7d2d8b09e3a2d5cf26a34
am: f71d7fe
* commit 'f71d7feef22db9e0cab2f32edc7440aedb86fdfe':
Ensure local settings caches are not stale
Change-Id: Iab7ff4dbfb4961b131b8ab82656b99bf45ed29bf
- 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: 9444231
* commit '94442315502026a7b3a8a8c1ed74e7794670b0b0':
Bluetooth: Fine tune audio gain for Absolute Volume case
Change-Id: I4686722e2cc9d1d059ba240902aa84fffb7b7831
am: 34510eb
* commit '34510eb2933b98f0c8c73f9a7be5eae911a14210':
Don't opt-out of warning dialog by default on user builds.
Change-Id: I4cb37a050cbed326ca78e9d3ace672819059e825
