When the app doesn't set IN_SCREEN and INSET_DECOR but the window is
still full-screen, we force SYSTEM_UI_FLAG_LAYOUT_FULLSCREEN but then
we still need to communicate the content insets to the DecorView.
In DecorView, we consume these insets in this mode and set it as
layout params so this behavior is completely transparent for the
app.
Bug: 26464646
Change-Id: Ib7332b845767a5bbc0266c380bf6240e322db943
Stashing SyncSettings for accounts not added by SUW Restore time
and restoring these settings whenever the account is added.
Bug: 26181613
Change-Id: Ia83e3fd43385a05424a8991115aa21ac90f4cd49
This is needed from Settings to show a message informing the user
of the number of attempts before their work profile gets wiped
when using ConfirmDeviceCredentials.
Bug: 26677759
Change-Id: I4b16f7dc2f415d0ce0215a3b7a646f98fabece33
am: be0537a4e1
* commit 'be0537a4e133d29848efd2458acf12f995a5823b':
Adding view debug annotations to simplifying debugging state.
Disallow launching third party apps in safe mode.
Drawing thumbnail background color for empty space in view.
* changes:
Adding view debug annotations to simplifying debugging state.
Disallow launching third party apps in safe mode.
Drawing thumbnail background color for empty space in view.
Don't show the ChooserTargetService targets until we have all
responses in, or we hit our timeout. This helps prevent targets from
jumping around under the user's finger. We still give bonuses to
services that respond faster.
Bug 26790940
Change-Id: I8a19e19e08eeb502ccc4b4feaa1710ca3315e9f6
In split-screen the light status bar flag for one side of the
status bar can be different from the other side.
SYSTEM_UI_FLAG_LIGHT_STATUS_BAR is now reported for both
the fullscreen stack and docked stack, but not anymore in the
"default" SysUI visibility field when reporting a visibility
change to SystemUI. The change also reports the docked stack
and the fullscreen stack bounds, so SystemUI can guard tinting
the icons on whether the icon is one of the areas.
When calculating the light status bar flag in PWM, we keep track
of the top fullscreen opaque window state for the docked and
fullscreen stack separately.
Bug: 24365214
Change-Id: Id2240a86d75bf96e0138ec7652a4793859f56e3c
This was done by the SetupWizard to suggest the default locale
before the SIM was detected.
It is also handy for devices without SIM (tablets).
Bug: 26784450
Bug: 26882058
Bug: 26939651
Change-Id: Ia1d3b2ef4756121cf6ca13d5d7280215df060a8f
In case of writing single character, check against the buffer length,
not the maximum buffer size.
Bug: 27099774
Change-Id: I83d49ea74cc3d25342ec540b654d3dc68e4e802e
FLAG_FULLSCREEN is really the wrong flag for determining whether
to subtract the window insets in the decore view and layout
it with a reduced size - FLAG_LAYOUT_IN_SCREEN suits these needs
much better.
Bug: 26014496
Bug: 26984057
Change-Id: I5c7a0fb7468d3981b91b23aa4c8b1e4841202131
And set the drawable's callback to null during drag-resizing, since
we use multi-threaded renderer, will do not want to schedule draws
to the ViewRootImpl's thread.
bug: 26729953
Change-Id: I6e5f94a5a6ba15edc2d391dd11d8fee3c657d337
This makes the animation when exiting docked mode a bit nicer
when you fling the divider towards to the navigation bar. However,
since the divider ends at the navigation bar, we need to immediately
dismiss it instead of fading out when the divider is fully occluded
by the navigation bar.
Change-Id: Ic5432fd118cb71be36485667b2c537caf5065ce5
When relaunching an activity while preserving the window, the content
view was put on top of the status bar background, making it disappear
in case of translucent status bar backgrounds.
Change-Id: I1edff29c10616bf5386e982d7336327135f0f7a0
Whitelist two more legacy intent actions, and don't enforce the
StrictMode checks when resolving intents that might be coming from
legacy apps. Newer apps would have already been yelled at directly
before getting to the resolver.
Bug: 26976516, 26977622
Change-Id: Ibf72a361ed68c52cfaac16c32ab40e79005a42e7
When dragging the divider in a way such the task size goes through
the following transition
- Half size
- Full screen
- Half size
the surface wasn't clipped off anymore. This was because in full
screen configuration, computeDragResizing() == false thus when
going full screen -> half size, we reset the draw state to
DRAW_PENDING to get notified when it has finished drawn. However,
this also broke clipping.
In order to fix this, we always put the window into a resizing mode
no matter whether the bounds are fullscreen or not.
However, this introduces an ugly flickering on the navigation bar,
when going into docked mode, because the app doesn't draw navigation
bar background in resize mode.
To fix that, we calculate the presence of navigation bar whether the
window is fullscreen, and not just whether it's resizing. For that,
we need to calculate the presence in BackdropFrameRenderer, by using
the insets just sent by window manager.
Change-Id: Idf56df4ae7fefe67d068bc2eeda8dc4d83bbefb7
Only allow one row's worth of targets from any one
ChooserTargetService and lower the weight for app recency in resolver
sorting. Along with a previous change to only consider the past 1 week
of app activity, this is to help improve the quality of direct share
targets shown.
Bug 26562857
Change-Id: I0f9a8ca8ccfb655261421e29fef7909cadd318f1
Fixed a bug which caused a null pointer exception on restore
in deleteDirectoryContents() method.
Also made other cosmetic changes.
Change-Id: I75712ec585fdfdbca462c468acf2229a47331b59
Since the title in the region selector should be the language name,
the standard Preference logic is bypassed. So the normal Preference
implementation cannot update the title automatically.
This makes sure we set the title at the right time.
Bug: 26715311
Change-Id: Ifa3d70b8504b093ae17baba8c179ebf55e3c7be2
- Take insets into account for calculating dismissing fraction,
but don't dim into 100% when the device has insets at that
side.
- When applying parallax to the top side, apply less.
Change-Id: Id1af37e6f7af43ec3682dad4ad1ce68034301b4d
When the langage selected in the first step is right-to-left the
localized region names should also be rendered right-to-left,
regardless of the UI language of the system itself.
We only need this to happen for the sub-locale because all labels
are localized in the same language (the parent one), so it is all
consistent, not the mixture we have in the language selection.
Bug: 26278041
Change-Id: I54c4306763458be691a1ba0c2bc2dba613beb8c5
