Change the measurement order of elements in the action bar. Custom
views are now deemed more important and may truncate title/subtitle.
Change-Id: I150862f8e48b36bcbd892f49d78c2962c5001ab1
An earlier fix nooop'd invalidate calls on non-visible views. This
caused an issue where changes to the view while it was not visible
(such as changing the text of a TextView) would not get picked up
by the invalidation process.
The fix is to automatically invalidate() a view when it becomes
visible, to account for any changes that may have occurred to its
content while it was not visible.
Change-Id: Ia0f8fb42ca627b5a38f08761fa622b23f2dfa38b
It looks like this is caused by the change in HC to stop activities when
the screen is off. ViewRootImpl (a.k.a. ViewRoot) has special code to
avoid doing work when it is stopped, and it is now stopped when the screen
is off. The problem here is if the window's activity is stopped when the
window is first displayed, then it would never do the initial fitSystemWindows()
with the status bar offsets given by the window manager, and never do this
again until the status bar changes.
Also included here is some re-arranging of the code dealing with the offsets
changing, because it was dealt with in two places and only one had a bunch of
code dealing with HW accelerated drawing and performing the fade transition
between states. Now all of that is unified into one place.
Change-Id: I9828f02664cc622dbf186effb1f685a8aa4456a1
Account name and account type are being retrieved from the
cursor for the contact, but account dataset, which is the
3rd value to uniquely distinguish an account is missing.
Bug: 5210676
Change-Id: I85f93b3fa19839734e4e22928382e0f786ed8ee2
The content retrieval APIs are synchronous from a client's
perspective but internally they are asynchronous. The client thread
calls into the system requesting an action and providing a callback
to receive the result after which it waits up to a timeout for that
result. The system enforces security and then delegates the request
to a given view hierarchy where a message is posted (from a binder
thread) describing what to be performed by the main UI thread the
result of which it delivered via the mentioned callback. However,
the blocked client thread and the main UI thread of the target view
hierarchy can be the same one, for example an accessibility service
and an activity run in the same process, thus they are executed on the
same main thread. In such a case the retrieval will fail since the UI
thread that has to process the message describing the work to be done
is blocked waiting for a result is has to compute! To avoid this scenario
when making a call the client also passes its process and thread ids so
the accessed view hierarchy can detect if the client making the request
is running in its main UI thread. In such a case the view hierarchy,
specifically the binder thread performing the IPC to it, does not post a
message to be run on the UI thread but passes it to the singleton
interaction client through which all interactions occur and the latter is
responsible to execute the message before starting to wait for the
asynchronous result delivered via the callback. In this case the expected
result is already received so no waiting is performed.
bug:5138933
Change-Id: I382e2d8689f5189110226613c2387f553df98bd3
Visually center a single text menu item in the split action bar even
when an overflow button is present.
Fix a bug in allocating space in the split action bar.
Change-Id: I54eff86bf35197030c9c1656ebd71297e3c8b62b
When recording data usage, measure the actual active time, since
buckets can be quite long. Offer incrementOperationCount() version
that reads thread stats tag for caller. Rethrow any NPE as ISE
during stats parsing, which callers already handle.
Bug: 5171812, 5184508, 5180659
Change-Id: I6da80ccc0162be68bee279529e3a23b6f98ebd87
These settings can never be written to by engines and apps
anyway, and reading them does not serve any useful purpose.
The only code that needs to read these settings are the framework
TTS classes.
bug:5149036
Change-Id: I1f95977d241eb6b550105f45d29fee889da3fbd1
These columns store additional information about the contact associated
with a call log entry and are needed by the new functionality present in
the call log.
The information is used only internally by the call log, so these column
do not need to be part of the public API.
Bug: 5101753
Change-Id: Ie2160a157497f10ba5fc95c5fcf3b4095a99753a
and forth.
Also have the SwitchPreference's Switch widget's onClick listener
toggle the switch rather than invoke the preference's own onClick
method. This will allow subclasses to assign different behavior to
clicking the preference itself if desired.
Change-Id: I97e3b7a786e9f0e8bdc03c0ed6001caa7dcd991b
