am: 479c9bb
* commit '479c9bbaf971aab9d3ac50acebe41158e53ee342':
Tethering and Data Saver: There Can Be Only One!
Change-Id: I184d03847abe86dd2f5e10c10bd12f90f7cc14d8
am: 0db93ce
* commit '0db93cea0fef6aa73caa0ef422b8e0a4e45a24e5':
Tethering and Data Saver: There Can Be Only One!
Change-Id: I876c9a30e9451b1c346296c233068bdfb579f584
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: I90b8fe98181dc2b7d00f0c9d320acce316d637e9
List items are always positioned using the divider height, even if there
is no divider drawable, so we should account for that when calculating
list height.
Bug: 28402970
Change-Id: I14b8d3b04a369749ff4b7e6f1e6e003ac08f6b7f
am: 864bc48
* commit '864bc48e0104451e20281258429677a9ebbab9ac':
Support to pass <uses-library> option through to dex2oat.
Change-Id: Ia276b7594e31177f0295e03982aae96267367887
am: 8435e68
* commit '8435e68e0ea5401300e2bfb03252b172bdf6be5b':
Give guidance on alternatives to deprecated locale field
Change-Id: Ic75d9c8e440a9a77faf71d48ebde2b3ee3415b00
ViewRootImpl may be null at this point if
we didn't preserve. Sorry about the churn.
Bug: 28413589
Change-Id: Iebfd819490252b52332d94ccefbddfae160087cf
am: 78dd08d
* commit '78dd08d5dd49ba3e054e1416849606a22064b389':
Give guidance on alternatives to deprecated locale field
Change-Id: Ibb3a28940ac9c2baeb3f31c760e651633a39a43f
