summaryrefslogtreecommitdiff
path: root/core/java/android/view/Window.java
Commit message (Collapse)AuthorAgeFilesLines
* Merge tag 'android-13.0.0_r52' of ↵George Zacharia2023-08-021-0/+5
|\ | | | | | | | | | | | | https://android.googlesource.com/platform/frameworks/base into t13.0 Android 13.0.0 Release 52 (TQ3A.230605.012) Change-Id: Ic80f318636f1f70bbd009504352ddde511d0dead
| * Change AudioManger getMode() binder call to addOnModeChangedListener()Bishoy Gendy2023-03-031-0/+5
| | | | | | | | | | | | | | | | | | - Remove binder call from running each time with clicking on volume up and down keys. Replace it with listener instead. Bug: 240705522 Test: Manual using Signal App / Youtube and Sample MediaRouter App. Change-Id: I842133770a583217940ebc929d8d929f4cd27a51
* | base: Add support for window ignore secure [1/2]LibXZR2023-02-191-0/+6
|/ | | | | | Feature: yt/KSCOPE-23 Change-Id: Ia9447ca17f6b24152b64526c25710a77e1388ce6 Signed-off-by: LibXZR <i@xzr.moe>
* Merge "Fix doc issue linking internal class" into tm-devJorim Jaggi2022-04-121-3/+1
|\
| * Fix doc issue linking internal classJorim Jaggi2022-04-111-3/+1
| | | | | | | | | | Fixes: 148043444 Change-Id: If43ebe0ec38cc00379d8db79481ef2c3116ce867
* | Remove OnBackInvokedDispatcherOwner interface.Shan Huang2022-04-011-0/+9
|/ | | | | | | | Test: m -j update-api. Build and flash and test back behavior throughout the system. Bug: 227500290 Change-Id: Ibdb13d02e044741d05d99f1cad96e43dc0129fe4
* Support floating IMEs even when IMEs render the nav buttonsYohei Yukawa2022-01-311-0/+28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As discussed in Bug 201375975, the nevigation bar handling for floating IMEs is a bit tricky. This CL tweaks DecorView behabior only when InputMethodService#canImeRenderGesturalNavButtons(), is true and the IME is floating in the gestural navigation mode. Fix: 215550296 Test: Manually tested with ThemedNavBarKeyboard sample 1. Build aosp_coral-userdebug and flash it 2. adb root 3. adb shell setprop \ persist.sys.ime.can_render_gestural_nav_buttons true 4. adb reboot 5. make -j ThemedNavBarKeyboard 6. adb install -r \ $OUT/system/app/ThemedNavBarKeyboard/ThemedNavBarKeyboard.apk 7. adb shell ime enable \ com.example.android.themednavbarkeyboard/.ThemedNavBarKeyboard 8. adb shell ime set \ com.example.android.themednavbarkeyboard/.ThemedNavBarKeyboard 9. Open the Dialer app 10. Focus in the top edit field. 11. Tap "FLOATING MODE" mode 12. Make sure that the navigation buttons are visible. Change-Id: Ia54499a3c2ac6e33e72f625eba3477fd81649d32
* Introduce Window.DecorCallbackYohei Yukawa2022-01-311-11/+34
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is a follow up CL to my previous CL [1], which introduced a hidden callback method into Window.Callback. This CL does not change any observable behavior but consolidate that hidden callback into a newly introduced Window.DecorCallback interface. In this approach, we no longer need to worry about accidental method name collision in Window.Callback implementations classes. Here is the new callback chain. ViewRootImpl#performTraversals() -> DecorView#onSystemBarAppearanceChanged() -> Window.dispatchOnSystemBarAppearanceChanged() -> NavigationBarController.Impl#onSystemBarAppearanceChanged() [1]: I08566034bebfafff6777ce0152cd6ca1f66f6cad 678ddce11c131a8e6746fe386c40ddc8d99d01c3 Bug: 215549533 Test: Manually tested with ThemedNavBarKeyboard sample 1. Build aosp_coral-userdebug and flash it 2. adb root 3. adb shell setprop \ persist.sys.ime.can_render_gestural_nav_buttons true 4. adb reboot 5. make -j ThemedNavBarKeyboard 6. adb install -r \ $OUT/system/app/ThemedNavBarKeyboard/ThemedNavBarKeyboard.apk 7. adb shell ime enable \ com.example.android.themednavbarkeyboard/.ThemedNavBarKeyboard 8. adb shell ime set \ com.example.android.themednavbarkeyboard/.ThemedNavBarKeyboard 9. Open the Dialer app 10. Focus in the top edit field. 11. Tap "EXTENDED LIGHT NAVIGARION BAR" mode 12. Make sure that the navigation button color is optimized for light navigation bar. 13. Tap "STANDARD LIGHT NAVIGARION BAR" mode 14. Make sure that the navigation button color is optimized for light navigation bar. Change-Id: I5168f76dfc9526e925c565dbfa87597b5543fcdc
* Support light navigation barYohei Yukawa2022-01-271-0/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In order to propagate the information about whether the IME is using light navigation bar or not from android.view.ViewRootImpl to android.inputmethodservice.NavigationBarController within the same process, this CL adds a new @hide method to Window.Callback as follows. ViewRootImpl#performTraversals() -> DecorView#onSystemBarAppearanceChanged() -> Window.Callback#onSystemBarAppearanceChanged() -> SoftInputWindow#onSystemBarAppearanceChanged() -> NavigationBarController#onSystemBarAppearanceChanged() Button color transition will be implemented in a subsequent CL. Bug: 215549533 Test: Manually tested with ThemedNavBarKeyboard sample 1. Build aosp_coral-userdebug and flash it 2. adb root 3. adb shell setprop \ persist.sys.ime.can_render_gestural_nav_buttons true 4. adb reboot 5. make -j ThemedNavBarKeyboard 6. adb install -r \ $OUT/system/app/ThemedNavBarKeyboard/ThemedNavBarKeyboard.apk 7. adb shell ime enable \ com.example.android.themednavbarkeyboard/.ThemedNavBarKeyboard 8. adb shell ime set \ com.example.android.themednavbarkeyboard/.ThemedNavBarKeyboard 9. Open the Dialer app 10. Focus in the top edit field. 11. Tap "EXTENDED LIGHT NAVIGARION BAR" mode 12. Make sure that the navigation button color is optimized for light navigation bar. 13. Tap "STANDARD LIGHT NAVIGARION BAR" mode 14. Make sure that the navigation button color is optimized for light navigation bar. Change-Id: I08566034bebfafff6777ce0152cd6ca1f66f6cad
* Merge "Add windowIsFloating to window blur documentation" into sc-devGalia Peycheva2021-05-181-2/+3
|\
| * Add windowIsFloating to window blur documentationGalia Peycheva2021-05-171-2/+3
| | | | | | | | | | | | Bug: 182567575 Test: m doc-comment-check-docs Change-Id: I3ee71c82416e359d077750ae7d0ba8b1b7fbfb29
* | Draw splashscreen edge to edgeRiddle Hsu2021-05-141-0/+5
|/ | | | | | | | | | | | - Switch from PhoneWindow to FrameLayout - Ensure the Action bar is not shown on the splashscree - Do not show the contrast scrim under the system bars - Use the latest insets API to layout fullscreen Test: Updated CtsWindowManagerDeviceTestCases:SplashscreenTests Bug: 181852475 Bug: 184941669 Change-Id: Ifc04bd2227394415cc74c20d2974f4726ec9c789
* AttachedSurfaceControl: Respond to API feedback.Robert Carr2021-05-051-3/+4
| | | | | | | | | | | "Root" is eliminated from the interface name as it is a property of the object and not the interface, but remains highlighted in the getters to express the relationship between the called and returned object. Bug: 185365821 Test: Existing tests pass Change-Id: I163fc23f2c37c984ef3ffeb7514c4d8c1c1a3f90
* Merge "Fix paragraphs in blur javadocs" into sc-devGalia Peycheva2021-03-311-5/+7
|\
| * Fix paragraphs in blur javadocsGalia Peycheva2021-03-291-5/+7
| | | | | | | | | | | | Bug: 181149137 Test: m doc-comment-check-docs Change-Id: I0f2e7cf5f1f5970060dc845b74b9c2e67d7248dd
* | Expose API for using SurfaceControl with ViewRootImplRobert Carr2021-03-301-0/+10
|/ | | | | | | | | | | | This API is appropriately called "ViewRoot". So far we just expose an API surface to reparent SurfaceControl to the ViewRoot (but without exposing the ViewRoot's SurfaceControl, to encourage developers not to shoot themselves in the foot) and to synchronize with the drawing of the ViewRoot SurfaceControl. Bug: 173463039 Test: ViewRootSyncTests Change-Id: I8ce0ed4b3efe50cdb3b71ae0f05ce25438d42368
* Splits up internal binder api for scroll captureMark Renouf2021-03-161-2/+2
| | | | | | | | | | | | | | | Splits the connection callback out from the session callbacks. Use ListenableFuture at the ScrollCaptureClient layer to safely chain together futures, provide a better exception handling/reporting path, and allow for cancellation of background tasks. Bug: 180671218 Test: atest ScrollCaptureClientTest ScrollCaptureConnectionTest Test: atest ScrollCaptureFrameworkSmokeTest Change-Id: Ibc8536d12a5554f62b3d7e1f4f717d3589ec45e0
* Merge changes from topic "add-runtime-blur-disabling" into sc-devGalia Peycheva2021-03-021-1/+10
|\ | | | | | | | | | | * changes: Create listener for dynamic blurEnabled changes Make WM.LP.blurBehindRadius a setter+getter
| * Create listener for dynamic blurEnabled changesGalia Peycheva2021-03-011-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This CL exposes an API to let apps know when the blur has been enabled or disabled dynamically. This could be due to battery saving mode turned on, tunnel mode being used, minimal post processing requested, etc. This adds a WindowManager.addCrossWindowBlurEnabledListener, which allows apps to add/remove a listener for blur enabled state changes. The listeners are registered in a CrossWindowBlurListeners, which receives updates from WindowManagerService when blurEnabled changes. CrossWindowBlurListeners only registers a remote listener if the client initializes it. I.e. if the app is not interested in blurs, the CrossWindowBlurListeners won't get initialized and won't register a remote listener. WindowManagerService holds a RemoteCallbackList, which holds listeners for each client process and notifies them when there are updates. If any of the listeners' process dies, the entry is removed from the list. Bug: 177524486 Test: m CTS-Coverage-Bug: 179990440 Change-Id: I3fe8f2d2008171d6b069e8ee6f3b47e5b5d60cfa
| * Make WM.LP.blurBehindRadius a setter+getterGalia Peycheva2021-03-011-1/+2
| | | | | | | | | | | | | | Bug: 181014794 Test: m && atest BlurTests CTS-Coverage-Bug: 179990440 Change-Id: I3d8ceddcf1219df8decbbb0bf9a6bbb9d41799fb
* | Long screenshots framework update and API unhideMark Renouf2021-02-251-2/+0
|/ | | | | | | | | | | | | | This change includes a series of API review changes. The most significant update is the addition of cancellation signals to API methods where needed. Renames some internal classes and interfaces to support the API changes and to simplify tests and improve quality. Test: numerous presubmits Bug: 175830670 CTS-Coverage-Bug: 180419562 Change-Id: I9b1b950a2779fc902ecf4d6394e3c35171926700
* Add window background blur public apiGalia Peycheva2021-02-121-0/+24
| | | | | | | | | | | | | | | | This CL exposes Window#setBackgroundBlurRadius as public Api. It creates a region behind the window (with the dimensions of the window background drawable), which is blurred with the given radius. It also adds windowBackgroundBlurRadius dimension as an xml attribute on Window. Bug: 167166562 Bug: 177524486 Test: m Test: m doc-comment-check-docs Test: atest BlurTests Change-Id: I5c0ff3c7fc7a64e6b2e2339eccc23374ec3b5fd9
* Allow 3p apps to hide non system overlay windowsLinus Tufvesson2020-12-101-0/+25
| | | | | | | | | SAW permission is added to the shell to allow it to create TYPE_APPLICATION_OVERLAY windows during testing. Test: atest CtsWindowManagerDeviceTestCases:HideOverlayWindowsTest Bug: 159616727 Change-Id: I503cd8da24ff4d2b928f930ac61090e6782c1546
* Move activity client operations to a separate interfaceRiddle Hsu2020-12-021-2/+1
| | | | | | | | | | | | | | This CL focuses on the methods used by Activity and ActivityThread. Also remove getUriPermissionOwnerForActivity, notifyActivityDrawn notifyLaunchTaskBehindComplete notifyEnterAnimationComplete because they are only used between ATMS and WMS. Bug: 174041144 Bug: 174040691 Test: CtsWindowManagerDeviceTestCases Change-Id: I5a30ec30cf6acd9ae4c908e524141fd17a4e54ff
* Suppress all hidden abstract methods in constructable classes.Aurimas Liutikas2020-11-111-0/+5
| | | | | | | | | | | | | Having a hidden abstract method for a class that can be extended means that public implementors cannot implement these hidden methods posing a risk that custom implementations will not have required abstract methods resulting in an exception. Bug: 151134792 Test: make update-api Change-Id: I758d12465fabc671be19bedeeceb16885de23c87 Exempt-From-Owner-Approval: large scale suppression of existing issues, no-op in terms of behavior
* Add maxTargetSdk restriction to unused APIs.Mathew Inwood2020-10-291-3/+3
| | | | | | | | | | | | | | | | | | | These are APIs that have @UnsupportedAppUsage but for which we don't have any evidence of them currently being used, so should be safe to remove from the unsupported list. This is a resubmit of ag/12929664 with some APIs excluded that caused test failures; see bugs 171886397, 171888296, 171864568. APIs excluded: Landroid/bluetooth/le/ScanRecord;->parseFromBytes([B)Landroid/bluetooth/le/ScanRecord; Landroid/os/Process;->myPpid()I Landroid/os/SharedMemory;->getFd()I Landroid/hardware/input/InputManager;->INJECT_INPUT_EVENT_MODE_WAIT_FOR_FINISH:I Bug: 170729553 Test: Treehugger Change-Id: I8285daa8530260251ecad6f3f38f98e263629ca7
* Revert "Add maxTargetSdk restriction to unused APIs."Hongwei Wang2020-10-281-3/+3
| | | | | | | | | This reverts commit 72f07d6a8a32db4a0dedd7682a0b3385be2b9cd6. Reason for revert: Droidcop-triggered revert due to breakage https://android-build.googleplex.com/builds/quarterdeck?testMethod=testAppZygotePreload&testClass=android.app.cts.ServiceTest&atpConfigName=suite%2Ftest-mapping-presubmit-retry_cloud-tf&testModule=CtsAppTestCases&fkbb=6936597&lkbb=6936969&lkgb=6936551&testResults=true&branch=git_master&target=cf_x86_phone-userdebug>, bug b/171886397 Bug: 171886397 Change-Id: Ibe0f0430a3451477c1ee8ef56a596e91ea1e7672
* Add maxTargetSdk restriction to unused APIs.Mathew Inwood2020-10-271-3/+3
| | | | | | | | | | These are APIs that have @UnsupportedAppUsage but for which we don't have any evidence of them currently being used, so should be safe to remove from the unsupported list. Bug: 170729553 Test: Treehugger Change-Id: I4c8fd0006f950de9955242e93968fb0996ceb372
* Refactor names of internal scrollcapture interfacesMark Renouf2020-10-191-5/+6
| | | | | | | | | | | | | | | Renames to better align with use and existing naming patterns. Using 'connection' to avoid confusion as to control flow or roles. (A connection is direct from SystemUI --> App process) IScrollCaptureClient -> IScrollCaptureConnection IScrollCaptureController -> IScrollCaptureCallbacks Test: atest FrameworksCoreTests:ScrollCaptureConnectionTest \ FrameworksCoreTests:ScrollCaptureTargetResolverTest \ ScrollCaptureTest Change-Id: I9afd33109f6718b61d172ce3e4b3bb5d71a2897e
* Annotating context in framework baseCharles Chen2020-08-031-1/+4
| | | | | | Bug: 151414704 Test: build & run Change-Id: I42c8ab699433c51158a1af201da0521413d74dcd
* Add test api getStatus/NavigationBarBackgroundView.Yuncheol Heo2020-05-041-0/+19
| | | | | | | | | | Introduces new test api to access the background view of status bar and navigation bar. Bug: 154720832 Test: atest WindowInsetsPolicyTest Change-Id: If38d3f57edfbb2631d4c1e47ed5347a332edacfb
* Scroll Capture FrameworkMark Renouf2020-04-201-0/+27
| | | | | | | | | | | | | | | | | | | | | | | This is an implementation of long screenshots supporting interactive, incremental capture of scrolling content using a cooperative API between the app process and the system. Design goals: - Provide for tile based incremental screenshots of scrolling content - Support existing apps without developer action - Provide support for non View-based Apps & UI toolkits Bug: 148131831 Test: atest \ FrameworksCoreTests:android.view.ScrollCaptureClientTest \ FrameworksCoreTests:android.view.ScrollCaptureTargetResolverTest \ FrameworksCoreTests:com.android.internal.view.ViewGroupScrollCaptureTest \ FrameworksCoreTests:android.view.ScrollViewCaptureHelperTest \ WmTests:com.android.server.wm.DisplayContentTest Merged-In: I6c66a623faba274c35b8fa857d3a72030a763aea Change-Id: I6c66a623faba274c35b8fa857d3a72030a763aea
* Make caption a insets sourceYunfan Chen2020-03-261-4/+1
| | | | | | | | | | | | | | | | | | | | | | | This patch introduced setCaptionInsets, and set the Insets in ViewRootImpl when dispatch the insets if there's a caption. Modification is made in Window and DecorCaptionView to make caption overlay with the app content, and pass the value to ViewRootImpl to apply when dispatch. It is necessary to trigger a dispatch when caption enabled status chanaged, otherwise sometimes it will not be updated. Because caption is now updated locally on the client side. Some old logic to deal with the overlay caption without insets are removed, including the touch event dispatch override, the color override. Bug: 134531136 Test: go/wm-smoke Test: Manually change the value in dispatchApplyInsets, can observe a blank content area when there's a caption bar. Test: atest InsetsStateTest Test: atest InsetsControllerTest Change-Id: I356344a13c8569512d8f51f7ea19a5603f778252
* Merge "Make ActivityInfo.preferMinimalPostProcessing a flag" into rvc-devGalia Peycheva2020-03-051-1/+1
|\
| * Make ActivityInfo.preferMinimalPostProcessing a flagGalia Peycheva2020-03-031-1/+1
| | | | | | | | | | | | | | | | Bug: 149420259 Test: atest CtsWindowManagerDeviceTestCases:MinimalPostProcessingTest Change-Id: I250669158a532316bebed8fa8c17e009b9293ecb
* | PhoneWindow: Fix potential memory leakAdrian Roos2020-02-271-1/+2
|/ | | | | | | | | Fixes an issue where PhoneWindow and thus Activity can be leaked through AttachInfo through the OnContentApplyWindowInsetsListener. Fixes: 148799801 Test: make droid; atest WindowTest Change-Id: I1de5518c84fd7e6d1aa1542a9252b1c600f5712d
* Replace OnContentApplyWindowInsetsListener with simple booleanJorim Jaggi2020-02-011-30/+18
| | | | | | | | | | | | | The concept will move into the support library (androidx), so in the framework we only need a simple boolean to toggle the default behavior. Also remove redundant methods on WIC to control IME. Bug: 143556682 Bug: 118118435 Test: WindowTest CTS Change-Id: I30fbffdfbe79a57b0f4166f0657c78370c7bcf02
* Introduce Window.setContentOnApplyWindowInsetsListenerJorim Jaggi2020-01-221-46/+52
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When root-level content containers fit insets, they used to just apply and consume the entire system insets. However, with the new Inset APIs, and with deprecating ADJUST_RESIZE IME flag, we want to give apps an easy way to customize this behavior. For that, we introduce Window.setOnContentApplyWindowInsetsListener that returns what kind of margins/padding should be applied and what should be dispatched to the content views. This is essentially a replacement for SYSTEM_UI_FLAG_LAYOUT_* as well as SOFT_INPUT_ADJUST_RESIZE: It allows apps to choose which insets should be handled on the window level vs view level. For that, we mark the window decor views as FRAMEWORK_OPTIONAL_FIT_SYSTEM_WINDOWS, in order to distinguish the case when support library calls makeOptionalFitSystemWindows(). This is because of two reasons: - We don't want the listener to be invoked twice. - We can not do the compat ping-pong between onApplyWindowInsets and fitSystemWindows. This is because during the ping-pong, the result of the OnContentApplyWindowInsetsListener would be lost. However, we still need to do the compat ping-pong for ActionBarOverlayLayout in the support library (until that gets migrated to use onApplyWindowInsets), so we have this separate dispatching path that only gets used for framework optional fitting views. Test: WindowTest Bug: 118118435 Change-Id: I4b514addd9e094163062d651972f85615b4a35db
* Add minimal post processing API to frameworkGalia Peycheva2019-12-231-0/+38
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This API allows applications to instruct the connected display to do minimal post processing on the produced image or video frames. This will switch the display to a low latency mode (ALLM, Game mode or some other custom implementation thereof), reducing lag in the final images. Thus, minimal post processing would greatly enhance performance for gaming and video conferencing applications. It would not, however, suit applications that prioritise image quality over performance. This CL adds 2 public method: - Window.setPreferMinimalPostProcessing() (this can also be set in WindowManager.LayoutParams.preferMinimalPostProcessing) If minimal post processing is preferred, the connected display will be requested to go into low latency mode, which reduces image processing, resulting in better performance for gaming applications. If the Display sink is connected via HDMI, the device will begin to send infoframes with Auto Low Latency Mode enabled and Game Content Type. This will switch the connected display to a lower latency mode (if available). For more information, see HDMI 2.1 specification. If the Display sink has an internal connection or uses some other protocol than HDMI, effects may be similar but implementation-defined. - Display.isMinimalPostProcessingPreferred() Returns true if the connected display supports either Low Latency Mode (ALLM or some other custom low latency implementation) or Game content type. Bug: 135116095 Test: make -> flash on ATV OTT device -> open an activity which requests minimal post processing -> check SurfaceControl logs -> verify correct signals are passed to native Change-Id: I5508bb9e5c138b0f2b42d8f8fab10e1915ba3cb6
* Use new UnsupportedAppUsage annotation.Artur Satayev2019-12-181-1/+1
| | | | | | | | Existing annotations in libcore/ and frameworks/ will deleted after the migration. This also means that any java library that compiles @UnsupportedAppUsage requires a direct dependency on "unsupportedappusage" java_library. Bug: 145132366 Test: m && diff unsupportedappusage_index.csv Change-Id: I5be7335b23a92b8ac80d2fd890198273b66ad644
* Merge "API update for insets"Taran Singh2019-12-171-2/+3
|\
| * API update for insetsTarandeep Singh2019-12-161-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - Rename WindowInsetsAnimationListener to WindowInsetsAnimationCallback - Make onAnimation WindowInsetsAnimationCallback.onStarted hierarchical by giving the client a chance to consume AnimationBounds, which then will be dispatched to its children. - Clarify that WindowInsetsAnimationController insets are always relative to the window. - Introduce progress variable for inset animations. Since DecorView will be consuming insets, apps still need a way to calculate the full progress. Instead of also dispatching the root insets, we offer a animation progress instead. Bug: 111084606 Test: CTS will be added in the future Change-Id: I7df27581d01c1db0118eef469ec089249012ba5f
* | Window Manager Flag Migration (7/n)Tiger Huang2019-12-161-0/+56
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Introduce new APIs in Window/WindowManager.LayoutParams for developers to decide which types of insets at which side a window should avoid: setFitWindowInsetsTypes(@InsetsType int types) setFitWindowInsetsSides(@InsetsSide int sides) setFitIgnoreVisibility(boolean ignore) The existing logic in DisplayPolicy.layoutWindowLw uses combinations of window types, window flags, and system UI flags to decide what frames a window should have, which is very complex, difficult to maintain, and should be replaced with the new APIs. Bug: 118118435 Test: atest InsetsSourceProviderTest InsetsStateControllerTest InsetsPolicyTest WindowStateTests CommandQueueTest RegisterStatusBarResultTest InsetsFlagsTest LightBarControllerTest RegisterStatusBarResultTest ViewRootImplTest DisplayPolicyLayoutTests DisplayPolicyInsetsTests DisplayPolicyTests TaskSnapshotSurfaceTest Change-Id: I06ddc9d0d2887ba4ded7bb8adbf9c9c0da4bf7b4
* | Merge "Revert submission"Robin Lee2019-12-141-38/+0
|\ \ | |/ |/|
| * Revert submissionHansong Zhang2019-12-131-38/+0
| | | | | | | | | | | | | | | | Based on Forrest run with earlier base build 6069142, the build with this submission failed apct/bluetooth/instrumentation_test Reason for revert: Break tests Bug: 146198238 Change-Id: I65060ca389bf3ae1f107552ca828bfc1e7baa7c1
* | Merge "Add minimal post processing API to framework"Galia Peycheva2019-12-131-0/+38
|\|
| * Add minimal post processing API to frameworkGalia Peycheva2019-12-061-0/+38
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This API allows applications to instruct the connected display to do minimal post processing on the produced image or video frames. This will switch the display to a low latency mode (ALLM, Game mode or some other custom implementation thereof), reducing lag in the final images. Thus, minimal post processing would greatly enhance performance for gaming and video conferencing applications. It would not, however, suit applications that prioritise image quality over performance. This CL adds 2 public method: - Window.setPreferMinimalPostProcessing() (this can also be set in WindowManager.LayoutParams.preferMinimalPostProcessing) If minimal post processing is preferred, the connected display will be requested to go into low latency mode, which reduces image processing, resulting in better performance for gaming applications. If the Display sink is connected via HDMI, the device will begin to send infoframes with Auto Low Latency Mode enabled and Game Content Type. This will switch the connected display to a lower latency mode (if available). For more information, see HDMI 2.1 specification. If the Display sink has an internal connection or uses some other protocol than HDMI, effects may be similar but implementation-defined. - Display.isMinimalPostProcessingPreferred() Returns true if the connected display supports either Low Latency Mode (ALLM or some other custom low latency implementation) or Game content type. Bug: 135116095 Test: make -> flash on ATV OTT device -> open an activity which requests minimal post processing -> check SurfaceControl logs -> verify correct signals are passed to native Change-Id: Id09160ba1513fef4dac979162bcda3bfeaace0e6
* | Removing remnants of menu keySunny Goyal2019-11-181-10/+0
|/ | | | | | Bug: 131763491 Test: Everything compiles Change-Id: I43207f4835b295123d6eb2a9a06c90cd5ed29174
* Merge "Remove FEATURE_SWIPE_TO_DISMISS functionality"Jorim Jaggi2019-11-111-17/+3
|\
| * Remove FEATURE_SWIPE_TO_DISMISS functionalityJorim Jaggi2019-11-051-17/+3
| | | | | | | | | | | | | | | | Not used anymore by any product. Bug: 143346248 Test: Boots Change-Id: I21286e62f73ec34f7d5ca040cd614838c9cd4276
generated by cgit v1.2.3 (git 2.25.1) at 2025-12-20 20:54:49 +0000