onCreateOptionsMenu
Initialize menu presenters early enough to respond to expanding an
action view within onCreateOptionsMenu.
Have SearchView show the IME as an async post to handle attempts to
show it while the UI is still in initial setup.
Change-Id: I77f3a94ed4397737edb5a7a15bf54993b6723f5e
This was added to simplify some logic in the provider and app, as
there are places that can simply compare the concatenation of the
account type and data set.
Also added a DATA_SET extra for contact creation, to allow for this
value to be passed around via intents.
Bug 5077096
Change-Id: Ia0634cfcf4590fd90ccb5cb99360c38c86f08d25
Fix cases that weren't batching menu presenter changes correctly.
Have FragmentManager invalidate the options menu less often.
Change-Id: Ia66fcd09ada8b0a084ad6b08d4340a8fa0c8fc5d
bug:5008210
Still has the following issues:
* colors are always black & white
* ignores centering, word wrap from text area
* gray background text (such as with instant search) and other textfield effects
aren't shown
The DebugFlags.DRAW_WEBTEXTVIEW can still be used to overlay red text over the
input box.
Change-Id: I7f22321c31b9edbc5351cac13f2e17b0ee19d563
Teach NetworkPolicy limits to "snooze" when requested by user, and
notify with both dialog and notification. Register for network alerts
through NMS to trigger updates immediately instead of waiting for
next stats update.
Enforce that all NetworkPolicy are unique on a template basis, and
move SCREEN_ON/OFF broadcasts to background thread. Launch SystemUI
and Settings directly instead of using actions, and include full
NetworkTemplate in extras.
Tests to verify notification and snooze behavior.
Bug: 5057979, 5023579, 4723336, 5045721
Change-Id: I03724beff94a7c0547cb5220431ba8d4cd44d077
It's at a very high priority currently - and will trump
foreground processes (and UI threads) which it shouldnt.
bug:5076001
Change-Id: I0d71c2941950782491ae31526a47ea6f97c38ffb
...apk reinstall; affects user privacy
Disconnecting a ServiceConnection after an app is torn down could
impact the bookkeeping of the same service if it has been started
for the app.
Also address issue #5073927: GSF process can't be killed
A new flag allows the systems location manager service to tell
the activity manager to not pull bound services up forever into
the visible adj level.
Change-Id: I2557eca0e4bd48f3b10007c40ec878e769fd96a8
1. Events not generated by the user can change the interrogation allowing window
unpredicatably. For example when a ListView lays out its children it fires an
accessibility events and changes the currently active window while the user
interaction may be happening in another window say a dialog. Now the interrogation
allowing window is changed when a new window is shown or the user has touch
explored it.
bug:5074116
Change-Id: I8dde12bbec807d32445a781eedced9b95312b3e2
Also, the onActionViewCollapsed needs to be called before detaching
the action view, so that the action view can dismiss the keyboard properly.
Fixes the Gmail search case where the keyboard doesn't disappear on hitting
the "up" affordance after a search.
Change-Id: I3c2f3f90f0edf6473404e6ceae3fa08866cad736
1. Find viewsWithText does not respect if the current view group is a root name
space and keeps its traversal. This is inconsistent with the other findView*
methods. Also only visible views are returned witch is inconsistent with the other
findView* methods.
2. AccessibilityNodeInfo reports children it the source is root namespace. This is
not correct since thi flag denotes the beginning of a logically separate view
hierarchy.
bug:5082601
Change-Id: I9c7ca51f284d04728828d5e656112257c9a2c6e2
During maybeStartNextSyncLocked(), check the network connectivity for
the target UID, and skip when disconnected.
Bug: 4519115
Change-Id: I8adee8e04521cb878624b19e557d01869f984c4c
This changes adds an API for system applications
to enable bluetooth without all the side effects like
auto connection to headsets etc.
Also some tweaks to the adapter state machine
Change-Id: Ib9f22d548a26d72334b300101c8eb0d80f08a4bb
We had initially decided to merge the NEW field (from the call log) and
IS_READ field (from the voicemail contract) into the single NEW field
already present in the call log.
However, it turned out that the meaning of the two fields is slightly
different: NEW means the items has just been inserted (and the user is
not aware of it) while IS_READ represents whether the user has read this
specific message (or heard, in case of voicemails).
This change makes the IS_READ field public, as well as deletes the NEW
field from the voicemail contract, since it is no longer needed there.
The NEW field in the voicemail contract (in fact the entire voicemail
contract) has never been released (this feature is new in ICS).
Bug: 5036195
Change-Id: I740c51c1a8e6d2460050eaab9943fb38b1565058
The input reader needs this information so that it knows how to
interpolate touches on an external touch screen.
Changed Display so that it asks the WindowManager what the real
display size is (as opposed to the raw display size). This means
it now takes into the forced display size set by
adb shell am display-size.
Replaced all calls to getRealWidth() / getRealHeight() /
getRealMetrics() in the WindowManager and replaced them with direct
usages of the mCurDisplayWidth / mCurDisplayHeight so that the WM
doesn't end up making a reentrant Binder call into itself.
Fixed the table status bar HeightReceiver so that it updates the
height on all configuration changes since it is possible that the
display size changed independently of an external HDMI display
being plugged / unplugged.
Improved the Display class documentation to make the distinctions
betweeen the various sizes clearer.
Change-Id: I3f75de559d3ebffed532ab46c4ae52c5e7f1da2b
Added TOOL_TYPE_ERASER.
Refactored the InputReader to share more code between the
various input mappers that handle button states and to
simplify the accumulator implementations by having each
one only handle a single type of input.
Removed the concept of direct/indirect tool types from the API.
If we add it back, it should be done in a manner that is orthogonal
to the tool type itself, perhaps as a flags field on the pointer.
The device source may well provide sufficient information anyhow.
Change-Id: I811c22d95e8304269b6ee4f6d11a6b04f3cfc1b2
