DHCP timeouts should not be logged at DHCPClient level but as a timeout
event in IpManager.
Bug: 28204408
Change-Id: Ia12619e3bf71102cf289cbbcdec53fd5e7e8efff
We need to ensure that the InputMethod ends up
after the docked divider so it will have a higher
Z-order for input.
Bug: 28184654
Change-Id: Ifbe943312a82a79e850f106cc906f3749737710d
Dialer recreates activity inside onConfigurationChange
when configuration changes significantly. Recreated
activity in this case was initialised with old base version
which resulted in incorrect configuration in split-screen.
This CL updates configuration when activity is created from
override config.
Bug: 27976063
Change-Id: I0ac002a5661154ec25f2d5aba3d44070b683ba2f
am: 1ed0c12
* commit '1ed0c12a657eb3f569cfcc5329ef4532e83d0f87':
Fixed a few issues when adapting the dpi
Fixed a few issues with status bar density changes
Change-Id: Iba70347a8fa9ea1f22e236e9c1f1d388e1c4d772
am: 3af18ca
* commit '3af18caf8e31afe87ee82bb2710876bdcc1d9a06':
Fixed a crash when changing density with HUN visible
Change-Id: I1d231c00a65ec911c6c04755caf1135da1c6feca
am: 7d5c695
* commit '7d5c6955208e82157e6e5ba42ba1d5f1507c6eb6':
Use .equals() to compare two UUIDs in SoundTriggerHelper, rather than ==
Change-Id: I3a34b43b8e69fcb99fe88558a705d2a6435179a1
am: 87574b7b1a
* commit '87574b7b1a26ca1c26a26016ff1cee286404d84c':
Hiding clear-all button on drag start.
Adding hint text for drop targets.
Fixing animation spec animation problem.
Making the dismiss animation feel smoother.
Fixing issue with gap between task views.
Adding desired undocking animation.
Change-Id: Ie5f454617fb4a3e0f4fa23fc2dc96c5cfb5f659b
* changes:
Hiding clear-all button on drag start.
Adding hint text for drop targets.
Fixing animation spec animation problem.
Making the dismiss animation feel smoother.
Fixing issue with gap between task views.
Adding desired undocking animation.
- 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
am: 3e38e6a
* commit '3e38e6accf5586d350581a301e1ecfcadaf03b93':
Checks for existence of vr components before trying to disable them.
Change-Id: I8ef723826494b230f747f94a3d5149bd1d7fac69
am: 3eefb4c
* commit '3eefb4c313d0269f7e8bd226bdcc2d039f9e5608':
Use right starting window resource in multi-window mode.
Change-Id: If799a1a7c93de62e0a954af70c5f244f02688a16
am: de7b2ed
* commit 'de7b2ed881d75cb7f21ae2199b9af68ae019becf':
Be bug-compatible with Fragment#setUserVisibleHint < N
Change-Id: Id9374c29e6f241e377b75acd4ae7b11c8324c54f
The proxy object was being used to match when adding or removing objects.
But they are different each time. So now we use an asBinder() object.
Bug: 28153736
Change-Id: I1bccebf1e9464668db757ff08b41902d0cf0e3a7
Signed-off-by: Phil Burk <philburk@google.com>
Prior to Android N we were simply checking if a fragment had a
FragmentManager set before we would trigger a deferred
start. Unfortunately this also gets set before a fragment transaction
is committed, so if setUserVisibleHint was called before a transaction
commit, we would start the fragment way too
early. FragmentPagerAdapter triggers this situation.
Unfortunately some apps relied on this timing in overrides of
setUserVisibleHint on their own fragments, and expected, however
erroneously, that after a call to super.setUserVisibleHint their
onStart methods had been run.
Bug 28184671
Change-Id: Ie40d5f6963d312c2fad4a48fb4f992d33e65c83b
am: ecf094a
* commit 'ecf094ae9d715ac3cff6213fae4c904f9dd791e8':
Fixed ScriptGroup finalizer for old API
Change-Id: Icd420a0023b7c614d7dd2104a38acfb62f66d450
If a notification is updated to be non clearable but is in the middle of
being dismissed then it is snapped back into place. Part of the ways to
check if it was being dismissed is by checking the translation of the
notification.
In the case that the notification was translated to display the gear, then
when it was updated it would be snapped back over the gear. This CL fixes
this issue by snapping back to the gear instead of 0 in this situation.
Bug: 28019486
Change-Id: Ic6c4c29b0adee15d7b358fcdbc8446e8a4cd9f82
