- We were always using the stack layout to get the task transforms, but
when we are animating to a given task position (ie. hitting recents
while the home->recents transition is happening), we would start the
animation with the final task rect, instead of the current task rect.
Instead, use the current transform of the task view, and transform
that to screen coordinates and use it.
Bug: 27154882
Change-Id: I25af8fad97ee78669c952dd81708e6cee5dfab05
- Now that we changed the way the landscape tasks clipped, we no longer
have to worry about the aspect ratio scaled height.
Bug: 27921659
Change-Id: I86b10805e92decb9995caa3790649f9f7d211784
The statusbar is now behaving nicer and other
parts are behaving similar as if they had been inflated
that way. The signalclusterview is now properly recreated
ensuring that it's scaled correclty.
Fixes: 26844819
Change-Id: Id1aab629204d03c079815358e7a5eb12d2a4e557
Reinflated the brightnessmirror to have the propper layouting.
Also fixed the height of the heads up scrim.
Bug: 26844819
Change-Id: Idb24dbd40f071a2a722c59cc202ae46c5ace2da8
The Quick settings page indicator was trying to access views that
don't exist yet.
Fixes: 27927374
Change-Id: I1600ce8432b6550268da20443d32193b1d2debe4
In normal circumstances, StorageVolume can only be obtained through
StorageManager and hence it will contain a valid path internally. But
the path could be invalid in at least 2 occations:
- App maliciously changed it using reflection.
- Mounted volume was ejected.
This change improves OpenExternalDirectoryActivity so it returns a
RESULT_CANCELED upon receiveving an invalid path.
BUG: 27962875
Change-Id: Ide43968babaa37961c7b704bd289f44eac952e94
One of the changes in the 'interactive bugreport' bugreport workflow
introduced on N is that the initial screenshot was taken right away (by
Shell, not dumpstate).
Unfortunately, such initial screenshot is often delayed when the system
is overload. Also, if the user is not interested in a screenshot, it
would be adding more load on the system unnecessarily.
Given these issues, and the fact that the user can still easily take an
initial screenhsot by selecting the proper notification action, the
initial screenshot is being removed.
BUG: 28167977
Change-Id: I2cf6616ce3124102b62ec9a36dc5a0ce6455a909
The following screens will be affected:
- Settings app > data usage
- Settings app > Developer options > Running services
Bug: 28064677
Change-Id: I3aec5ddd8c8daaab4172fcc614fb6e4787fc51bc
1. Changed list title from body1 (14sp, regular) to
body2 (14sp, bold).
2. Reduced spacing between list title and first list item
by 3dp
3. Reduced height from divider line to list by 20dp (I had
this in redlines as 20dp, but I think that added an
additional 20dp to the component so it ended up being
40dp in implementation)
4. Reduced padding between app icon and app name from 32dp
to 24dp (this is a change from original redlines so that
the text aligns 72dp from the edge of the dialog which is
a standard Material keyline)
Bug: 28169928
Change-Id: I01b92486353fa990158819a2d18b16cd910d7ded
Also fix an issue where resize was not called.
And make the translation a bit larger, because the
animation is longer.
Bug: 27870534
Change-Id: Ia6128db8108fe57bee96816fc95fd0811d941ffb
When having an app docked and then going home, and then launching
the app from the homescreen, we had a wrong transition because
getTopMost task was already set to the launched app, because
getRunningTasks doesn't exclude the docked stack. Instead of adding
flags for getRunningTasks, which sounds risky, we just pass a "force"
value when we launch recents in this state.
Bug: 27154882
Change-Id: Iee4512fed13115dbbe8b74413ff1fa9b87afa0ef
When tests run for the first time, the list of activities that can
handle ACTION_SEND_MULTIPLE might not be scrollable, which was cause the
scrollForward() method to fail.
BUG: 27431998
Change-Id: I5992bc9fec6291c74c4af7887ee66eb4f96e87c0
Case was omitted in dialog, resulting in UnsupportedOperationException.
Remove a redundant flag check.
Bug: 28204292
Change-Id: I313d61c72596d4a127f61d557af7300f50d26bf0
When quiet mode is disabled for a user and that user is not currently
decrypted, we show a confirm credentials screen to trigger decryption
of that user. Only if that was successful, do we actually disable quiet
mode.
Bug: 27764124
Change-Id: Ib1f649194d89e225dad62c14f3ddba1fa3d79da2
The number didn't apply the contrast computations
and wasn't scaling when density changed.
Change-Id: Ibde116f176c3a8d20de28ab432a80d9219f75581
Fixes: 28073460
