am: 853304c
* commit '853304c0b11921db142a3945ab66fae5f0cc7d8a':
Show work challenge in if user in docked stack is locked
Change-Id: I6a35ac189e1bbb5fcb2b2ce28d2d2c9300cd82e6
Register docked stack listener in ActivityManagerService.
If the docked stack is leaving minimized state, check whether the user
of the docked stack is locked. If yes, show credential confirmation.
Also, we now show work challenge in home task.
And we now scan the entire top task to handle the case the work app is
somewhere in the middle of the task. (eg: open personal camera in work app)
Bug: 27565539
Bug: 28094505
Change-Id: Iaf0738f43ae916a535b17949ec0f322bbfb194dc
The following screens will be affected:
- Settings app > data usage
- Settings app > Developer options > Running services
Bug: 28064677
Change-Id: I3aec5ddd8c8daaab4172fcc614fb6e4787fc51bc
In order to capture profiles for apps which share the same VM and for
splits loaded without restart we need to move the profile registration
closer to where we create the class loaders (since bindApplication is
not called multiple times).
Moving the registration after class loader creation also allows us to
not profile apks which are already fully compiled.
Bug: 27539488
Bug: 27893309
Bug: 28012567
Change-Id: I6333f026f4f0680ca28e989f1686e3eac1145339
Which owns the native UidRange.cpp, so it makes more sense for the
declaration to live there since frameworks/base depends on netd but not
vice versa.
Bug: 26694104
Change-Id: I0efda77713ee6f0ec8070fb0e09a694b95f6cd25
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
am: 520ae86
* commit '520ae86666164adce825131703db42af5f2beaa6':
Avoid APF JNEBS instruction with R1 as it doesn't work
Change-Id: I45b0356dda8be726b07c28362b434c0a6fa7ea1b
am: 6aff67b
* commit '6aff67bfcb9dcca6e3f26ff04dbe8f9806e5e8a5':
Register the UI Thread as a sensitive thread to the runtime
Change-Id: Ic272fa836f573f3565bd81068f437e972cbfcdcc
There are two lock task modes: pinned and locked.
Pinned mode is the one that one that need users action to accept the pinned
request. For locked mode, it is triggered by DPM.
We should not allow user to stop locked mode by user action.
Please notice that it does not happen before because the action to dismiss
lock task mode is pressing both back and recents button and recents button
is hidden in locked mode. But it becomes a problem after the user action
is changed to long pressing back button.
So changes are as follows:
1. Only stop lock task mode if it is pinned mode in
stopLockTaskModeOnCurrent
2. Remove the permission checking in stopLockTaskModeOnCurrent. I can't
see the reason we are having this because there is no permission
checking to in stopLockTaskMode when it is in pinned mode. So you
can always stop pinned lock task mode anyway by calling
stopLockTaskMode directly.
Bug: 28184751
Change-Id: I610cc1dfade7737e0b08fc9a13dad29e62e09a32
* MtpEvent: Remove public constructor since properties cannot be set
directly.
* MtpEvent: Move event constants from MtpConstants to MtpEvent class.
* getPartialObject64: the byte[] must have indices of Integer.MAX_VALUE
at most. Document as such.
* sendObjectInfo: what happens if the transfer doesn’t succeed? How is
the app notified? If there is a reason for the failure communicated,
how does the app find this out? Add docs.
* Add isOperationSupported(int) and isEventSupported(int) helpers.
Change-Id: Ifd80016d2ddd3b66d5c45f6da76b6133f0c9a617
Fixes: 28146379
When raising the layer of the input method window we also
have to raise the layer of its assosciated dialogs which
thankfully are already collected for us.
Bug: 28138068
Bug: 28186814
Change-Id: I4e63a642199c5aad3b3322e773df287ced80d641
This patch changes how Event classes are organized:
- Base IpConnectivityEvent class does not implement Parcelable because
it cannot be final (has children). It also becomes abstract because
it is not supposed to be instantiated and logged directly.
- All children classes becomes final because they are Parcelable.
- All constructors of all children classes become private, because they
are supposed to be instantiated with their associated logEvent()
methods.
- All instance fields of all children classes become public final.
Rational: if private, the ConnectivityMetrics app cannot read
their data.
Bug: 28204408
Change-Id: I1a4689c422230c6ed034307dec54a61daf8a6598
This patch moves the event logging of DHCP response packet parse errors
to DHCPClient in a single place. It also logs receive IO errors as
DHCPErrors instead of DHCPClientEvents.
BUG=28197345
Change-Id: I7ad666cff4d8b97915880477347fbb3f588fdb2a
Otherwise animateDimLayers can occur before
updateDimLayers and we can show the dim at the
wrong size.
Bug: 26908486
Change-Id: Ifd664e48f3daa77900a7f0bffa58a379efa6b53c
This CL fixes that physical keyboard layout is not changed when user
changes it in settings. This happened because we compare
InputDeviceIdentifier instances by using Object#equals to choose
specified input device. However, one of them has been serialized and
deserialized, so it never be true.
Bug: 27747115
Change-Id: Ied84c510ccb8e2de919ba8bb326e0355a065e604
- Ignore calls to resize the docked stack due to it detaching while we are
already resizing stacks due to the docked stack switching to fullscreen mode.
- Defer resuming activities in a stack we are resizing to fullscreen when the
docked stack is going away. The activities may not be the top most activity
anymore since the activity in the docked stack might be moved on top of it.
- Removed call to ensure configuration in ASS.positionTaskInStackLocked.
This isn't needed as the ensure activities visible call will make sure
the activity is in the right configuration if it is going to be visible and
we don't want to be relaunching it if it isn't going to be visible.
Bug: 28196862
Change-Id: I26460dd9c649b8ec1bf296d5182e9ff6cafe6df0
We are not sending override configuration changes to activities if the change in
configuration is not significant enough (i.e did resources will not be reloaded
due to the change). This breaks apps that rely on getting onConfigurationChanged()
call whenever the config changes regardless of if resources will be reloaded.
We no deliver all configuration changes to the activity.
Bug: 28177873
Bug: 23904868
Change-Id: Icc979dabb8bc93ae8a976ef6074cd2559aedca67
- Briefly delay unBinding VrListenerService and making HAL calls
when leaving VR mode Activity in case subsequent activity will
be immediately re-entering VR mode.
Bug: 28115931
Change-Id: I3f362131ed2beb6a29ce78fe01e9301d8b396520
Fixes a bug where the disable flags were
always applied to user 0 instead of the current
user because the user switch dispatch from
WindowManager was broken.
Change-Id: Ib2faf0777c5367af5bf07cb2d11c51ed0222d65c
Fixes: 28062568
