Now that we live in an FBE world, we need the user to be involved
with every package move to ensure that CE storage is unlocked. This
means that a package upgrade session that would require moving an
app between storage devices cannot be satisfied.
Bug: 27147501
Change-Id: I274d85cbed727d9185178b77bfc6cef196df17f5
This change adds
- Open/close the disambig shade with a featured app
- Open/close the disambig shade with no featured app
- User selected "Always" for the featured app
- User selected "Just Once" for the featured app
- User chose a non-featured app
Bug: 26108706
Change-Id: I4d2c99cee1a784aa1cab156939c57c83d35a4aa5
Also increase the event buffer size to 100, and implement
it as a real ring buffer. And put that implementation in
a generic class for use in other places.
Change-Id: I06936984e2c253fb5f0eb5d15faf0019ec73d4e2
am: bd1708a19d
* commit 'bd1708a19da3ae205c4da3f22d0682c9bd1f76fe':
Fixes several animation issues related to a dismissing task.
Pipe the dismiss button logic through the touch handler.
Skip scroll-to animation when undocking and there are no tasks.
Fixing issue with docking being disallowed for secondary user.
Change-Id: Ib97a145fc6ff4e761a7220979913ed5be9e8fb71
* changes:
Fixes several animation issues related to a dismissing task.
Pipe the dismiss button logic through the touch handler.
Skip scroll-to animation when undocking and there are no tasks.
Fixing issue with docking being disallowed for secondary user.
This CL allows getChildVisibleRect to optionally always call the
view's parent. The previous version attempted to optimize the call
by not calling further up the view heirarchy when the rect isn't
visible in the current view.
The call is hidden and the previous behaviour is preserved to limit
the bits of code that this change affects.
Bug: 28514727
Change-Id: I49550ed4082bcbdcfe4643b962b50f3308092525
The unit for the battery charge counter is in micro-Ampere-hours, not coulombs.
We store the value as uAh but display it in dumpsys as mAh.
Bug:27174034
Change-Id: Ib5cc1ee1c5c191336a3e1f18dbb12c38e833f8d0
The FloatingToolbar popup wrongly assumes that the main content panel
is wider than the overflow panel. In situations where this assumption
fails, the toolbar popup is positioned wrongly within it's container
window and items appear truncated. This CL fixes this issue.
Bug: 28550367
Change-Id: I41669b1deed7dd34f0b2bd060d14452482d3d36c
am: 33f39a96cb
* commit '33f39a96cb40850b645833528d275c455898f4d2':
Fixed a bug where the image and the text were overlapping
Change-Id: I23bbae6c0115326c03171f227c2d4a8217f28ae5
am: 9cb7652fb1
* commit '9cb7652fb19256fe61d81c7770fe729fc6b67481':
Make sure all Notification actions are shown
Change-Id: I2fd99fc5be798e97b6e8ebc20fe1d2097d2d7c8c
am: d971a9d5f2
* commit 'd971a9d5f2f945d89728af7fffe1e692c1c91e3b':
Ensure FloatingToolbar is not rendered at negative x, y coordinates.
Change-Id: Id07efe487b3fe01d9df7968afb66ec4b45ae2c6c
am: d1c30db548
* commit 'd1c30db548da90d5bc092821c6fee4b4ef060bbb':
ShortcutManager: When app's data is cleared, remove all shortcuts,
Change-Id: I798a064e17a628999568a3a68634318ff1126bf4
Ensures each action gets at least its minimum width to prevent
an overly long action from squeezing out the others.
Change-Id: Ifb6253051b556bbab4738abef12dad0bb6f3c3d6
Fixes: 27996783
am: 0f01857
* commit '0f018570fff044bb68b8009815ae7e5c397d09fd':
Prevent pinned stack from having extra elevation
Change-Id: If115698ec6168bfced727b7488cc38b833d4618a
The current mechanism to sync InputMethodService#mIsFullscreen to
InputMethodManager#mFullscreenMode is really fragile because
1. Currently the state change is notified via
InputConnection#reportFullscreenMode(), where InputConnection is
designed to be valid only while the IME has input focus to the
target widget.
2. In favor of performance InputMethodService (IMS) calls
InputConnection#reportFullscreenMode() only when #mIsFullscreen
changed. If InputConnection#reportFullscreenMode() failed, there
is no recovery mechanism.
3. Screen oriantation change is likely to cause Window/View focus
state change in the target application, which is likely to
invalidate the current InputConnection.
What our previous workaround [1] did for Bug 21455064 was actually
relaxing the rule 1 only for InputConnection#reportFullscreenMode().
However, my another CL [2] made the lifetime check of InputConnection a
bit more strict again, which revived the issue as Bug 28157836.
Probably a long-term fix would be to stop using InputConnection to sync
that boolean state between IMS and the application. However, it's too
late to do such a refactoring in N, hence this CL relaxes the rule 1
again keeping it as secure as possible.
The idea is that we allow InputConnection#reportFullscreenMode() to
update InputMethodManager#mFullscreenMode regardless of whether
InputConnection is active or not, as long as the InputConnection is
bound to the curent IME. Doing this as a short-term solution is
supporsed to not introduce any new risk because the active IME is
already able to mess up the InputMethodManager#mFullscreenMode by
calling InputConnection#reportFullscreenMode() on any other active
InputConnection. Bug 28406127 will track the long-term solution.
[1]: Id10315efc41d86407ccfb0a2d3956bcd7c0909b8
da589dffdd
[2]: If2a03bc84d318775fd4a197fa43acde086eda442
aaa38c9f1a
Bug: 28157836
Change-Id: Iba184245a01a3b340f006bc4e415d304de3c2696
Pinned stack doesn't have focus, so there's no need for setting extra
elevation to show shadow for focused case.
This removes extra eleavtion for pinned stack, and improves the PIP
animation quality by preventing extra surface size change
at the end of animation.
Bug: 27364161
Change-Id: Id099a78de48b2e038a69600c94454b5cbfe0628f
