am: 2e63b8f
* commit '2e63b8fdd908f91d508f7fe95eb8599ee5d08b88':
Show cascading popup menus if screen is big enough.
Change-Id: Iddd564294d1f075819225ed60fe48ff71204d6b5
am: 306ceb8
* commit '306ceb84b4c8833eaa46093fbba7638378eee456':
Accommodate NaN in new context menu methods.
Change-Id: Iddd48717534ab7ce5ef93aab0016190a50c42e9b
am: 6ba6820
* commit '6ba68207a3474bed3333038cd59120ab924ca967':
Show cascading popup menus if screen is big enough.
Change-Id: I91bebc9226ab008ccd42256928641d671ac2d448
am: 1fab8d9
* commit '1fab8d995e74de2128b45d9cae294c8d5ccf2fc6':
Accommodate NaN in new context menu methods.
Change-Id: Ifaf625d13b5dc57cf69f10ef1af99aef4acfecb6
am: fb24d4f
* commit 'fb24d4f07793df29d999819d5394b6000d140c0a':
Fix onPrepareActionMode() not being called
Change-Id: I933be0d2b28dd9d2f1dce17e2b746dadf3b9e764
am: 9412176
* commit '94121762ff47728fd8080f45f04cafb55b92079d':
Fix onPrepareActionMode() not being called
Change-Id: Ic6f51f65f9d82b490ef26c89725b228f0568bdd9
Happens because mActionMode was set at the end
of the call, which means that invalidate() doesn't
actually do anything.
BUG: 28392319
Change-Id: Ifdc97c03dc43bfbe74790f90764d1575bd9ca951
Prior to this CL, the cascading implementation would evaluate the
contents of the menu to determine whether to show an icon for this case.
However, the policy we have upheld is that top level menus should
never show an icon for this case. (Unless setForceShowIcon(true) was
called.)
Bug: 28275346
Change-Id: I09423596d49742aa7a9ba7245702c099581c0b48
am: 334a936
* commit '334a936e154fd18a301f7df860322e456ec0486e':
Avoid instantiations of Boolean that are immediately unboxed.
Change-Id: I626df98f9cea04e782e837e6ddf0d37690306b70
Replaced Boolean.valueOf() -> parseBoolean() across frameworks/base
(not including Am.java, which I'm leaving for a separate change).
Also fixed a couple of other valueOf()s in SyncStorageEngine.
Bug: 28289401
(cherry-picked from commit ca01820735)
Change-Id: I2c6fb39a465885e7e625ed8894b1b9f8a30da5bc
am: 5acf0f0
* commit '5acf0f071da967926d8e473df13d4404f3b98a9b':
BatteryStats: use the same timestamp for comparing intervals
Change-Id: I81f64a0d5bea38b8426e96eb7a52da05fea36d8f
am: 6a4d9a3
* commit '6a4d9a3c9f7cbd30a7093f5088a72271a5e504c7':
BatteryStats: use the same timestamp for comparing intervals
Change-Id: I0c32c75176bd1e154ed0286f8426807d0221204a
am: 9aff58d
* commit '9aff58d6204d58c04b4257519f8dfeab1fd00033':
Remove dependencies on Activity from common Fragment superclasses
Change-Id: I6c6e35c552fb7699e3d44a364f18624b888011df
am: d2285b1
* commit 'd2285b1f40a714a49602dab5645c194af0eac880':
Remove dependencies on Activity from common Fragment superclasses
Change-Id: Ic0da5094cae15e03f139eae6ed2760a6cd126e0c
SamplingTimer has been losing some data, as well as not correctly handling
entries that have gone away and come back with less data (reset).
This change correctly ends a SamplingTimer sample by adding the accumulated amount
to the total, then reseting the running counter to accept new values.
This is also triggered automatically when the incoming data is less than what is currently
recorded.
Bug:25695597
Change-Id: I6b540906e6be527578d1003485384a75ba211b52
* introduced a new intent DISMISS_KEYBOARD_SHORTCUTS and
and new public API in Activity (which sends a broadcast
to KeyboardShortcutsReceiver) which applications can
use to dismiss the keyboard shortcuts.
* plumbing and implementation for a new call to dismiss
keyboard shortcuts from PhoneWindowManager and used it:
** when starting activities invoked via Search+key
** when starting activities invoked via META
** when starting activities via application launch keys
* removed unused variable in
Activity#onProvideKeyboardShortcuts
Note that for apps started via touch (aka non-shortcut)
like tapping the Settings gear icon from the notification
bar the menu is not automatically dismissed.
Bug: 28012198
Change-Id: I83a8d4f342bb8a08115a648648834d0d2bac19fd
am: 344bd5c63d
* commit '344bd5c63dfbe9a6aaef68144d04d3613563c080':
Framework: change the TTS text to use the current locale
Change-Id: I23d1acfd0b53fddeec4e9ad183d90d1cf7a9708e
In particular, don't try to call the k/v wallpaper restore helper's
onRestoreFinished() if we are actually doing a full-data restore.
Bug 28132784
Change-Id: I2eaf748f6d54601f0ca195ae2781aa177daf0b93
am: c708cf6340
* commit 'c708cf6340e623202e562992e6ef4062ace84cab':
BatteryStatsHelper: Include screen on baseline power draw
Change-Id: I6ba6f66ebc9d4ffebc8e6f5444957d0a345da4fd
This change takes an app's shared libraries specified by <uses-library>
and passes it through to dex2oat to be used during compilation.
Part of a multi-project change.
Bug: 26880306
Change-Id: I26ac0e055ee71eb6e2d92598115c46d3ca364d03
am: 150553756f
* commit '150553756f89a51cc70b24cd9dbab4bdfba0fc59':
Increase the max binder thread pool size for system_server.
Change-Id: I8312e28eac4b6b00b94af85d0e887448ec849652
There are two types of IMEs:
A. IMEs that have one or more subtypes
B. IMEs that have no subtype
The initial implementation to update hardware keyboard layout per
subtype change of layout (See Bug 25752812) has supported IMEs in the
category A only, and IMEs in the category B are just ignored in both
system and Settings app.
In order to support IMEs in the category B, InputMethodSubtypeHandle and
related methods need to accept null InputMethodSubtype. Technically
this is a straightforward change, because in InputMethodManagerService
we have already used InputMethodUtils.NOT_A_SUBTYPE_ID for those IMEs in
the category B. We also need to update Setting App, which will be done
by a different CL [1].
[1]: I46b9c5b018f08e3eaa4614a0893db0be91652f3c
Bug: 28182650
Change-Id: Ia013784a594ad3beaf30976d047f5ac0fa8185be
