The status bar icons can all be optionally scaled by the scale factor in
dimens. The phone stat icons had not been updated to include this
scaling logic.
Also allow the spacing between the icons in the mobile signal group to
be adjusted.
Change-Id: I12b35d462599f8a0747477fb280a974ffa77d01c
Instead of resizeable attribute. resizeableActivity is what is used
for multi-window. The code currently works because it targets N :/
Change-Id: I82f1b1b46f66ea39ae682ed1d45f97bc6247b0bd
This change logs the following user actions:
- Interactive bug report initiated from power menu.
- Full bug report initiated from power menu.
- Bug report canceled using system notification.
- Bug report details screen open using system notification.
- Additional Bug report screen shot taken using system notification.
- User changed bug report name using the details screen.
- User changed bug report title using the details screen.
- User changed bug report description using the details screen.
- Changes made on bug report details screen were saved by user.
- Changes made on bug report details screen were canceled by user.
BUG: 26759986
Change-Id: I1aae98b87a4dea66a1030a024dd799b97c25dd6d
We previously changed the touch logic to always fling even when
the panel is fully expanded, but that lad to an issue when it didn't
even start to expand.
Bug: 26255211
Change-Id: I8c991a0a19b49eb405b8efc2d69baf29c709b363
The menu key was not unlocking the keyguard properly
and didn't hide the notifications.
Bug: 26539875
Change-Id: I9dd89767f00d29c15d1d4e840a1ab22d59e58c8d
If the general setting is not to hide sensitive information
we allow the user to dismiss it.
Bug: 26328503
Change-Id: Ibea5d94e544291f00d8a2923b8cbf14170510bd8
Public notification titles were incorrectly modified when
the notification wasn't autoredacted (i.e screenshot).
This also lead to the doze mode not working correctly anymore
as notifications were colored.
Bug: 24866646
Change-Id: I3d4cdb0e13cfbf3fb8082b930936260d7c4749af
Alternate lock screen shows UNLOCK button in the middle of an
empty screen before any user has been created. See the screenshot
in the bug.
This fixes it. The approach is similar to the check in
KeyguardViewMediator.handleHide().
Bug: 27109342
Change-Id: I25536364b2c456d6fd55c79de7f25d2b0667e26f
Also...sorry, snowball, don't automatically open folders
that are created in Files app. Only do this in DocumentsActivity.
Change-Id: I271655fd3566496eced4aaa7a44d5110233150a0
For system user, there should be no atempt to dismiss keyguard,
but only if system user is split (i.e. not a meat user).
Change-Id: Ia2c1e7a3e197c5be72446f21b3883e853485ff26
(cherry picked from commit aa401afb4cdfd5bab441e633aee801c2a127aec2)
Some bouncers might allow showing keyguards for users that are not
currently active (e.g. before any user is signed in, in which case the
system user is active). Make sure that keyguard is not dismissed
without showing bouncer in these cases.
Change-Id: I0e037b2d4e095d49c1f0d06a9fe1b9a6233421b0
(cherry picked from commit aa69fd417f32435d7d7c06f8d033efa7fa21475a)
First attempt to to refactor fragments handling, state and app lifecycle.
The goal was to simplify code by using android built lifecycle
mechanism, eliminate bugs caused by multiple creation of the fragment,
see the performance impact and give some fundament for refactoring of
fragments and activities in the app.
Search view manager:
* Remove curentSearch from state
* Restore search from saved state (ex. after rotation)
* Rename file to give the better overview of its purpose
Directory fragment:
* Store selection state in a bundle
* Remove double creation of fragment
* Use loaders to reload content when possible
* Keep info about state inside the object
* Refactor available types of fragment to be normal and recents
* Make search type a mode possibly available in all types
* Remove search being invoked from refresh method
* Do search by reloading fragments content instead of recreation as
an example
Other:
* Fix window title maybe
Bug: 26968405, 27101786
Change-Id: I58f36cd0a3e3a6ec98996cd8aac16e10e425e1fe
