1. Added some clarification how a developer can use the
same provide with different historical files in a
context dependent manner.
Change-Id: I2a3390ade7e4b8b1170d381668e1439e52c17b7e
Deliver new intents to an existing parent from the calling uid obtained from
the applicationInfo instead of the process record, since the process record
might be dead.
Stoopid monkeys.
Bug 6328725
Change-Id: I4371a5705ccd7004f0dfe11da7c48d1563fb8dac
Propagate the return value from onNavigateUp as the result of
onMenuItemSelected. This fixes a bug where the action bar Up nav
button clicks would not be propagated to support lib FragmentActivity
or other activity subclasses that rely on processing otherwise
unhandled onMenuItemSelected events.
Change-Id: Id879dd1756ed06b8a7b720ebf0eae2a8ddc66ca8
1. Implementing text content navigation at various granularities.
For views that have content description but no text the
content description is the traversed at character and word
granularities. For views that inherit from TextView the
supported granularities are character, word, line, and page.
bug:5932640
Conflicts:
core/java/android/view/View.java
Conflicts:
core/java/android/view/View.java
Change-Id: I66d1e16ce9ac5d6b49f036b17c087b2a7075e4c0
Hot TTTF is about 5 seconds, so don't cycle the GPS hardware until
the interval is 10 seconds.
Also add some more dumpsys logging.
Bug: 6367964
Change-Id: I39402fc61f34458a1639c8814610a02606a8eb79
Bug 5731093
Replace TextView by EditText to make it cleaner.
Had to force the text color, although the TextAppearance should
handle it. Maybe something is wrong with the theme.
Also added a hint for consistency.
Change-Id: Icd7170a0ef3757d0313e0799873f2dd375b02f2f
Detect when a vsync message was significantly delayed which may
indicate that a frame was skipped. When this happens, update
the frame time to reflect the approximate start time of the
current frame instead of the start time of the frame that was
skipped a long time ago.
Removed an unnecessary call to getCurrentPlayTime() in the
animator framework. The result was always zero and the call
just made the code confusing.
Bug: 6443611
Change-Id: I92b24f7ffd74c59b75a727b6bfc0bb51fc92a73a
Handle the edge cases a bit better. Deal with padding. If a smooth
scroll begins, the list is empty, but a data change is pending, try
again on the next looper pass.
Bug 6453837
Bug 6434713
Change-Id: I53f22ebacdcbc5d981a6c8055c4fd3fc1ef140f6
This change replaces CopyOnWriteArrayList with a custom CopyOnWriteArray.
The new CopyOnWriteArray only allocates when a concurrent modification
is detected. Only one loop can iterate over CopyOnWriteArray at any
given time and the class is not thread safe.
Change-Id: Ie67a1ec20ff095350bf3c5d4f87cdb231ad57221
1. The model is using a package monitor to observe changes in
packages (adding/memoving/etc) to update its internal state
for which it then notifies its clients. However, the monitor
is called from a binder thread and the work has to be off
handed on the thread that created the model. Hence, clients
do not need to worry about using the the model from the UI
thread since the change callback may touch the UI from
another thread.
bug:6386152
Change-Id: I882a0f4104907f64de64a95ece585052bba457d6
Also don't retain the source bounds in recent tasks, since it
has no meaning there and it would be better when relaunching an
activity to have a new bounds set based on wherever it is now
being launched from.
Change-Id: Ia90c04ee98a888a7f725b038abe23d71e2b12800
...without onPause() in between
There was a bug in the handling of "always finish activities" where we
would go through destroying activities while in the middle of updating
the activity stack. This would result in the activity behind the
non-full-screen activity being created and then immediately destroyed,
which things were not expecting.
Change-Id: Idaa89089f7b1af7eb747d7b8f9f394beeb2d23fa
