am: 761f59c
* commit '761f59c19f1a0e527bb533df16abee7fac166dbd':
Hide children in ViewGroup.createSnaphost via internal flag and add test for it.
Change-Id: Ia6abc695ad05362245d25aa6d8b36fc72c508c3a
am: 394d3df
* commit '394d3dfb2d9ccd2ca2fd7aad06ef2e9a8458a0c7':
Hide children in ViewGroup.createSnaphost via internal flag and add test for it.
Change-Id: Iab1265b6a4c4ff5291259f7e5d9b96c217ee3141
am: a140391
* commit 'a140391f3d9e83361fca23f53e8eda8294f08e66':
Revert "Run cleanup before end actions of ViewPropertyAnimator."
Change-Id: Iaf2b975c7c0f0bfd064b8bde54e812f83d0198a5
am: 6bb61e2
* commit '6bb61e25a2831dc14b604327a995c36309dfcbc9':
Revert "Run cleanup before end actions of ViewPropertyAnimator."
Change-Id: I2254f4f2dfa19711fac8ed90e72addb94f4e26b8
am: 1a10817
* commit '1a108171ae7d55684c8590cb78a1ef3cb27c0335':
Uses bw_happy_box and bw_penalty_box for Data Saver.
Change-Id: I5252e6280887e46f84ad1aaf42a4123cb133f9c7
am: a6f98af
* commit 'a6f98afbdeda4da14d07b0fed5b6586b08cc5e38':
Uses bw_happy_box and bw_penalty_box for Data Saver.
Change-Id: I9d6e593ee2b57902c8ca98cbeb6eed212d2c6d82
am: 308b84e
* commit '308b84e87afe92168d3c47c0fa884cbc67ddfe9b':
Update print preview when option is changed and clear ranges when they layout changes
Change-Id: I4ce1a5aa59dd24fb3d01eede821fc810b02dab7c
bw_penalty_box is a blacklist-based firewall chain used to determine
which UIDs do not have access to metered interfaces. It can be used
alone or with bw_happy_box, which is a whitelist-based chain: when
bw_happy_box is enabled, it's included in the bw_penalty_box chain.
Currently, NMPS and NMS uses just bw_penalty_box for both blacklist and
whitelist, so when Data Saver is turned on, it has to build a extensive
list of UIDs to be blacklisted, which can take seconds (since it makes
dozens of iptables, and which forks an iptables process)
This CL changes this behavior so it uses both chain (plus a new
bw_data_saver chain, which is added to the end of bw_happy_box), in
which case the Data Saver switch is much faster (around 120-160ms),
since it requires just 1 or 2 iptables calls (one to switch the
bw_data_saver rule, and another to whitelist the foreground app if it's
not whitelisted yet).
BUG: 27127112
BUG: 26685616
Change-Id: If10222aef9f49a924b07b978d4bdccdd92f9acdb
am: 456f1e3
* commit '456f1e33b808052377a79b91d34091a356652f2c':
Update print preview when option is changed and clear ranges when they layout changes
Change-Id: I3fcb5c9041ce0268751010e84fb2e94a0a723b29
This reverts commit e9a4f87852.
This revert is to test to see if the gralloc lock problems are caused by this CL.
Change-Id: I395fd3675dd430c44a5d29b050ba248f3f2bf4cd
Previously it was assumed that one Resources object per Activity would be fine.
This proved to be incorrect, as methods like Context#createConfigurationContext()
expect to create a new Resources object that gets updated whenever the Activity Resources
get updated.
To fix this issue, there exists a master override configuration for each Activity. Subsequent
Resources created for an Activity will be based off that master override configuration, and
will be updated accordingly.
Bug:27644297
Bug:27604953
Change-Id: Idb3d851f55ee7981eec4e3fe28e2ea8d55f1192d
Add content to Settings and SettingsLib to add a checkbox for PBAP
client profile, and remove the box for PBAP server profile when the
client profile is enabled.
Bug: 27642222
Change-Id: I125559904a8e017a01ae90b1f6425129a87cbee3
It turns out that BaseInputConnection has still depended on a private
API named BaseInputConnection#reportFinish(), which was introduced
4 years ago to work around a UI freeze due to an unbalanced batch edit
count [1]. Note that such an unbalanced batch edit count cannot always
be avoidable. It can easily occur in the following situations.
- The current IME crashed during batch edit.
- The user changed the View focus during batch edit.
- The current IME called IMM#switchToNextInputMethod() during batch
edit.
The remaining problem is that #reportFinish() is still an internal API
and only subclasses of BaseInputConnection can implement it, and IMM
calls it when and only when the current InputConnection is
BaseInputConnection or its subclass. InputConnectionWrapper and any
other InputConnection implementations will never receive such a callback
to clean up InputConnection#{begin, end}BatchEdit(), which is considered
to be a major contributor to UI freeze.
To address the above issue, we unhide BaseInputConnection#reportFinish()
as InputConnection#closeConnection() so that application developers can
receive an appropriate callback to clean up internal state including
unfinished batch edit.
[1] I5525d776916f0c42d5e6d4a4282aed590d7f0e9a
9d69ecbf61
Bug: 24688781
Bug: 25332806
Change-Id: I234309c5880c9fe0b299b8bd0f8862796d4dda0d
