Don't set the callback until we're all done making changes.
Bug: 30902893
Change-Id: Ia1560692a83ecb2c50f5e77fa4d1e8155a78a204
(cherry picked from commit b46ba3b2b0)
Bug: 26385112
This threshold has previously been 0.1 degrees and somehow has taken
on the phone threshold of 2.0 degrees, likely by over-merging.
Change-Id: I6201cfa74b7901a958a1cd9d7d35a5b6f56d9870
Some existing apps treat drawable visibility notifications as a signal
to crossfade from a placeholder to the new image for the purposes of
scrolling onscreen via a recycling collection view or similar. Since
dispatchVisibilityAggregated is now called for window visibility
changes and ImageView informs its drawable of the visiblity change,
the extra call triggers a repeat fade-in in some existing apps when
you return them to visibility.
These apps should pay attention to the second parameter of
Drawable#setVisible, which signals that animations should not restart
in response to a visibility change. Updating to targetSdkVersion=24+
will enable the new behavior.
Bug 30216207
Change-Id: I27ce9f09bc7544863f7f7980c273650949db21cc
Checking mSurfaceControl!=null is not enough to ensure the surface is
valid. tryStartExitingAnimation() could destroy/save the surface before
app is stopped, if it decided the surface is no longer needed.
Use WSA.hasSurface() to check if the surface control is really valid.
bug: 30766796
Change-Id: I7724f1929d4ebc3f9a7a3b19eec638d7a7d7b910
These are not yet ready for updating in the unicode data, so we patch
them in code until they are.
Bug: 30594617
Change-Id: Ib4c8568aa4840341474eb0c0c95674d640473f4d
(cherry picked from commit 2b8b819fee)
Apply a bunch of improvements to the acceleration classifier:
- When dragging from the edges, we get some delay without
movement between the DOWN and MOVE, which confounds the
classifier. Now discounts data segments where the delay
does not match the expected 16ms.
- The distance ratio did not compensate for differences
in sampling. If it does it's equivalent to the speed
ratio however. The distance ratio was removed and the
impact of the speed ratio score doubled.
- If we cannot calculate the ratio, no longer penalize
the traces for this.
Bug: 27405075
Change-Id: I067eb4d478593afbb20354e5c85a05353e2b4184
(cherry picked from commit 6b312a09fc)
The flag indicate whether the root needs network access or not. MTP
should be LOCAL_ONLY root.
Bug: 30867267
Change-Id: Ia272d4a389cc1ca628d7b963caa37f3dbb6747e3
(cherry picked from commit 83c679e722)
SCHED_FIFO threads shouldn't be able to arbitrarily create more
SCHED_FIFO threads.
bug 30898724
Change-Id: I3704b47b88b573313e9b1610556648c8595d4108
(cherry picked from commit 38ee337f45)
Bug 30786309
If the Activity used in makeSceneTransitionAnimation isn't
the same one used in the startActivity call, a NullPointerException
could be thrown.
Change-Id: Id21c54fcf99b353feab62f7fc160997ed06e7d23
(cherry picked from commit 3289bfa289)
(cherry picked from commit a3edbf6a5d)
We cannot hold mPackages when calling into generatePackageDexopts().
This method takes Package Manager's mInstallLock. By holding mPackages,
we have lock inversion and hilarity ensues.
Change-Id: Ia11a158677051e3511702f38cde6780e75b256fb
Fixes: 30927731
(cherry picked from commit a8d4f48997)
+ When Vodafone Italy sim (mccmnc = 22210) is roaming in Spain on any
network, consider it to be roaming.
Bug: 29493858
Change-Id: I7ab1576012ab72a96e366c0ff1bcdf894a9e64de
Fixed some race conditions around wakelock and sensor control, which
if hit, would have left a sensor enabled when thought to be disabled
or possibly released a wakelock it didn't intend to release.
Bug: 30262052
Change-Id: Ieae26b2a2a7731ad299cd2c2426676295ffa768e
