As discussed in ag/1192965/ we have a special case for rotation
animation selection in launch from double tap. This was set to
ROTATION_ANIMATION_CROSSFADE as the goal was just to avoid
ROTATION_ANIMATION_ROTATE on the viewfinder surface and
seamless rotation in launch scenarios was initially descoped. Now we
are aiming at fixing this though, and ROTATION_ANIMATION_CROSSFADE
does not quality for seamless rotation. ROTATION_ANIMATION_JUMPCUT
also would not be a good choice because in the situation that the
rotation occurs before the app starting window appears, then we would
jump cut from unrotated wallpaper to rotated app, I think we want
a crossfade in this scenario. To this end introduce and use a new @hide constant
ROTATION_ANIMATION_SEAMLESS which qualifies for seamless but falls back
to CROSSFADE if seamless can't occur.
Bug: 30171992
Change-Id: If1945b17b5159be4cd5ba0b139d6bea9f7fcca33
When creating a new remote conference, there was a missing call to
"setConnectionProperties". This would prevent remote conferences from
being created with the correct properties as defined in the actual
conference.
Bug: 30383741
Change-Id: I335e35c222ae18b0d6ea7e750b91bcc36aa40ece
Some transitions can have no animation, in which case
isReadyForDisplayIgnoringKeyguard() will wait for VIEW visibility
to become VISIBLE. But if we have a saved surface, the transition
could have already started. This causes exiting app to be hidden,
while entering app's performShowLocked() still hold back waiting
for the relayout to visible.
If we started animating with saved surface, it should also count
as transition animation started.
b/30855380
Change-Id: I6260a323b48e57d8337267d9136f630226a48dc8
The summary is supposed to just hold enough data to continue counting
once the device has reset. Since kernel stats reset when the device
resets, and the first update is ignored to account for soft resets where the
kernel continues running, SamplingTimer should not be recording the last value
it saw from /proc/wakelocks in the summary.
Bug:30575302
Change-Id: Ic193bc5af9a0ede514e3abc8146523d7316c47d3
Previously, if there were problems generating the boot image, we would
display a notification saying the device is out of storage space,
regardless of whether the device was actually out of storage.
This change makes it so we only display the notification if the device
has less than 250MB when the boot image is missing.
Test: Verify the following sequence does not display the notification:
$ adb shell stop
$ adb shell rm /data/dalvik-cache/arm/*.oat
$ adb shell setprop dalvik.vm.extra-opts -Xnoimage-dex2oat
$ adb shell start
Test: Verify the following sequence does display the notification:
$ adb shell stop
$ adb shell rm /data/dalvik-cache/arm/*.oat
$ adb shell setprop dalvik.vm.extra-opts -Xnoimage-dex2oat
$ adb shell setprop debug.freemem 104857600
$ adb shell start
Bug: 28931369
Change-Id: Ia2291bf674af063a55f339d2a0411e670ca16ba2
Stepping the animation can lead to WindowStateAnimator#finishExit,
which can lead to WindowManagerService#removeWindowInnerLocked, which
can immediately call WindowSurfacePlacer.performSurfacePlacement. From
here we will directly modify mExitingAppTokens for each stack and remove
tokens where exiting is complete. I think removeWindowInnerLocked making
a direct call to performSurfacePlacement is questionable...but changing
semantics there is very risky. For now, simply avoid processing tokens
in the animator if the surface placer has removed them. It seems all we
would want to do is trigger a layout pass, which has just occured anyway.
Bug: 30813094
Change-Id: Iaff77d227e09839f7e6edda6b8f188d164e6da74
Add carrier config option to determine if carrier supports downgrade to
audio.
Add new telephony Connection events to signal Dialer that there was a
downgrade to audio, and why.
Bug: 30702393
Change-Id: Idd5272aafd71601e92291644640f52afe200208e
The latest assets which matches up with that in the App.
Also the matches up with sizes with icons the nexus launcher.
BUG:30388078
Change-Id: Iffac75b86c3d736392fa7a1809ffdf921d610b3d
When double tapping Recents, need to reinvestigate.
b/30831873
b/30790402
Revert "Clear WS.mDestroying on AWT.clearAnimatingFlags"
This reverts commit c2661e52eae3161ac8c02e831290ad50ad395be2.
Revert "Some fixes for transition animation selection"
This reverts commit 73e9bc3f1557f0320c8af843dfb051f27187361d.
As an optimization, we typically only run restorecon when
seapp_contexts changes. This CL checks a property that can be used
to always force a restorecon to help investigate boot timing.
Bug: 30213213
Change-Id: I4d65c1a4e4a0830ef4a32cd2fae1d3ab188b65cc
Substantive changes:
- Add discussion of reduction kernels.
- Use RS_KERNEL in place of __attribute__((kernel)).
- Discuss "context" special argument.
- Special arguments x, y, z may be of type int.
- Discuss multiple inputs for mapping kernels.
- Mention that script-side global writes are not visible in Java.
- Rewrite part of discussion regarding when to use support library.
- Change minimum device version for support library from Android 2.2 (API level 8)
to Android 2.3 (API level 9).
Stylistic changes (better conformance with style guide):
- Proper use of <i> (italic) versus <em> (emphasis).
- Proper case for headings.
- Proper pattern for Android version numbers.
- Do not use e.g. or i.e.
- Prefer active rather than passive voice.
- Prefer present rather than future tense.
Miscellaneous minor editorial changes.
Bug: 27299393
Bug: 30000147
Change-Id: Ie0a26152714cf8f619d4914218f7262d675bb25f
(cherry picked from commit 05eef3040e)
