It looks like there was a regression where #onNewIntent() was called
before the FLAG_ACTIVITY_BROUGHT_TO_FRONT flag was set. This
change updates the code so we set the flag properly.
BUG: 33034247
Change-Id: I61959a289dc5af14ee9d3d7bfa213191238efc88
Test: Compared to OpenGL pipeline and sanity checked
with understanding of the drawing pipeline. Also
wrote a unit test.
BUG:32370375
Change-Id: Iab397d21f0def725fa89551d48c764c67fd2bda8
Instead of hardcoding or assuming a path for testdata,
allow the testdata path to be specified via the command
line.
Test: make libandroidfw_tests
Change-Id: Ideae880b21c157b70a11bb5a90a94556771aead6
At a high level I had two sorts of goals:
1. To remove the weird pinned logic in setSurfaceBoundariesLocked
2. To seperate base crop calculation, and animation exceptions, between
window state and window state animator.
Itemized changes are as follows:
1. Rename updateSurfaceWindowCrop and calculateSurfaceWindowCrop to
applyCrop/calculateCrop. It doesn't feel that "SurfaceWindow" was
adding much.
2. Split screen space and window space (final v non) clip rect
computation, to make clarity about when each one should be used.
3. Eliminate weird case for pinned stack in setSurfaceBoundaries by
building it in to calculateFinalClipRect.
4. Extract calculateSystemDecorRect to WindowState as it mostly accesses
window members.
5. Extract part of calculateCrop to WindowState as
"calculatePolicyCrop". This was the part that fills mSystemDecorRect.
6. Extract wallpaper animation logic outside of calculatePolicyCrop
Test: bit FrameworksServicesTests:com.android.server.wm.WindowFrameTests
Change-Id: I8ff1dc6ec1206a34994f50ba44d765ab619efbff
Bug 32864127
When a fragment creates a view that is either invisible or gone,
it should remain that way. This means that the fragment won't have
any animations. When transactions are optimized, transitions
will avoid invisible and gone fragment views, but unoptimized
transactions will lead to failed transitions because none of the
views will be visible.
Test: Ie71902d1b5f5f647c758a1bd60cdfd6814cda29d
Change-Id: If952f81859227a28569d234d8232ff6bb100e74c
The base Activity resources need to be created differently so that
other configuration contexts can be rebased properly.
Bug:33166230
Test: cts-tradefed run cts --module CtsAndroidAppTestCases --test android.app.cts.ApplyOverrideConfigurationTests
Change-Id: I86def4e2414dc366dd1d5cbc9104c5d0c06a4d61
The display might not be added yet or be already detached when
config is updated.
Bug: 32983305
Test: android.media.cts.EncodeVirtualDisplayWithCompositionTest
Test: #testVirtualDisplayRecycles
Change-Id: I3b0e52e8ebb93a57ab6b0e80c0599db33ce2ae03
The new missing-service behavior was mostly added for core system
components, so don't wtf() when normal apps ask for missing services.
Continue to emit one-line log for third-party apps so they know why
getSystemService() might be returning null.
Test: builds, boots
Bug: 33109365
Change-Id: I3a6118a3db570d796a26da5b8d63015b13e53a87
The shelf doesn't need to be reinflated but should
reload its properties. Recreating lead to a bunch
of crashes.
Change-Id: I4628e0469f74c1a0201f7b1e6e86d187ad0e548d
Test: Change font size, observe no crash
Fixes: 33189282
This will fix issue when linting Java 8 default methods on interfaces,
e.g. Ie46a876dcb14b46b8b2584735c106c25655ec6cf.
Test: Manualy tried that the linter no longer gives the error.
Change-Id: I68ade6ba6401439667408076a5454caef77ef72d
Developers will be able to use PreferenceDataStore to replace default
SharedPreferences to store / retrieve the data.
Test: Separate CTS CL being submitted along this one, see the topic.
Change-Id: Ie46a876dcb14b46b8b2584735c106c25655ec6cf
Test: m
Test: angler boots
Test: Turn on Multiprocess WebView in Developer Options and launch the WebView
Shell. The sandboxed_service parent process is the webview_zygote.
Bug: 21643067
Change-Id: I9dab548853372fd91f6bbe204cc8686ef2e94448
Bug 32952142
When doing activity transitions, a window is temporarily translucent
during the transition. When a view hierarchy completely covers the
window, the background is never seen and applications can use a
null background to avoid overdraw. However, during the activity
transition, the underlying activity is seen during the transition.
With a null background, the buffer isn't properly cleared and
the uncleared buffer will show strange effects.
This CL forces a transparent background temporarily during the
activity transition to avoid this problem.
Test: manual testing using test application
Change-Id: I63f24dba3c2f810944bcbf07faf309f9f1c5889a
Test: Unlock with fingerprint, observe icon
Test: Unlock with fingerprint while collapsing panel, make sure
icon reappears after 800ms.
Change-Id: I8b081445bdaaa68741e4bab57a6f79f6e12f1d54
Fixes: 30507748
(cherry picked from commit 8dea48c87e)
Statically includes core-junit-static into legacy-test target so
that legacy-test can be used in place of core-test. Once that
switch over has been done then android.test classes that are
being removed from the public API can be safely moved into here.
Bug: 30188076
Test: make legacy-test and check contents of generated legacy-test artifacts
Change-Id: I75488303067c4ac34c46279bfce9a51273adcc34
