summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2018-10-20Merge cherrypicks of [5317808, 5317809, 5318498, 5317873, 5318338, 5318195, ↵android-9.0.0_r30android-9.0.0_r22android-9.0.0_r21android-9.0.0_r20android-9.0.0_r19pie-qpr1-s3-releasepie-qpr1-s2-releasepie-qpr1-releaseandroid-build-team Robot
5318499, 5317874, 5317875, 5317876, 5318243, 5318244, 5318537, 5318538, 5318539, 5318540, 5318541, 5318542, 5318543, 5318544, 5318545, 5318546, 5315210, 5317756, 5318557, 5318558, 5318559, 5318560, 5318561, 5318339, 5318547, 5318548, 5318549, 5318562, 5318563, 5318564, 5318565, 5318566, 5318172, 5318173, 5318174, 5318550, 5318401, 5318196, 5317889, 5318175, 5318176, 5318577, 5318578, 5318579, 5318580, 5318581, 5318503, 5318390, 5318505, 5318341, 5318551] into pi-qpr1-release Change-Id: Ie695cbef0f3680af38bdf883b52548a4be967548
2018-10-20libui: add boundary check to GraphicBuffer::unflattenChia-I Wu
Commit cb496acbe593326e8d5d563847067d02b2df40ec removed the boundary check by accident. Bug: 114223584 Test: manual Change-Id: I057bc02d5807e438530d1a5327c2e02b9d154151 (cherry picked from commit bf8d7210c4bbbdc875e9695a301cdf9c3b544279)
2018-08-23Snap for 4972147 from cf39b7bcad8c4d099b29ad42c6d524837fe3b2ea to ↵android-9.0.0_r16pie-qpr1-s1-releaseandroid-build-team Robot
pi-qpr1-release Change-Id: Ib136e79d83908bb78ebcd3372d1ffdab1d492646
2018-08-22DO NOT MERGE Apply scissor in render engine for main displayYiwei Zhang
Bug: b/113041377 Test: manually Change-Id: I651357d456f13ff67961b75d3630aca91aa512ac
2018-08-22Merge "Get screencap working correctly in landscape mode" into pi-devTreeHugger Robot
2018-08-22Merge "Add getDisplayViewport for screenrecord tool" into pi-devTreeHugger Robot
2018-08-22Fix a typo when checking a touch is within the physical frame.Michael Wright
Bug: 112876936 Test: enable notchless simulation, try seascape apps, try swiping down Change-Id: I8a155e16c19c474e605cb5a8d938e04461646027
2018-08-22Get screencap working correctly in landscape modeYiwei Zhang
Bug: b/112869712 Test: adb shell screencap in all screen rotations Change-Id: I62b38775f8253bea85a1870ad63cd27715754656 Merged-In: I62b38775f8253bea85a1870ad63cd27715754656
2018-08-22Snap for 4969136 from 22f1e9cfb73cc53b0417d3a27b901cccb2b4b4bc to ↵android-build-team Robot
pi-qpr1-release Change-Id: Idb5ca2d6a0f313ccc04fab1aeb42f78e7d55acfa
2018-08-21Add getDisplayViewport for screenrecord toolYiwei Zhang
Bug: b/112869712 Test: adb shell screenrecord Change-Id: I9f3f99de1a5bafc5318b24484f1916d28dcdfaa7 Merged-In: I9f3f99de1a5bafc5318b24484f1916d28dcdfaa7
2018-08-21Merge "Make sure that touches are within the physical frame." into pi-devTreeHugger Robot
2018-08-21Make sure that touches are within the physical frame.Michael Wright
Right now we just check that touches are within the reported axis bounds, but really we should be checking whether they're in the physical frame before notifying the rest of the system about them. Also, fix a bug in touch transformation code where translations were being incorrectly applied. We should only apply top and left translations when we're in portrait and landscape orientations, as in seascape and upside down orientations they'll just exceed their stated maximum naturally. Bug: 112876936 Test: enable notchless simulation, try seascape apps, try swiping down Change-Id: I0f2119d5bdae10d6197bee942829fd0eed3f5dfa
2018-08-20Get screenshot to exclude black cutoutYiwei Zhang
Bug: b/112869712 Test: long press power button to take screenshots && adb shell screencap && apps to take screenshots and check Change-Id: Ieb83373c9103f9847775eca5788358b567a05b24 Merged-In: Ieb83373c9103f9847775eca5788358b567a05b24
2018-08-20Snap for 4963492 from 99b4619cfeb1e8ed899ca0a4c72154be6263a98c to ↵android-build-team Robot
pi-qpr1-release Change-Id: I81bdfaf735a3fcfa8684edbf06534ce717965a08
2018-08-17surfaceflinger: silence misleading virtual display errorsChia-I Wu
Do not call HWComposer:: getColorModes getRenderIntents getHdrCapabilities getSupportedPerFrameMetadata getLayerReleaseFence when the display id is invalid. This happens with virtual displays when mUseHwcVirtualDisplays is false. Bug: 112082244 Test: screenrecord Change-Id: Ifd8a85fc15e1628744bf21277bd8fe3e2c322e46 Merged-In: Ifd8a85fc15e1628744bf21277bd8fe3e2c322e46
2018-08-13Snap for 4949382 from da1217f5fedc6e6ec9c4aed4f96be8b47ecf3ec4 to ↵android-build-team Robot
pi-qpr1-release Change-Id: If166dae2e53450d79a0c0c5bf84a41e0e070c58b
2018-08-10[automerger skipped] Merge "AOSP builds do not support Device ID ↵Eran Messeri
attestation" into pie-vts-dev am: 78c0e32983 -s ours Change-Id: I72a673a29f979ef87d789af4993a80c81bdb67d8
2018-08-10Merge "AOSP builds do not support Device ID attestation" into pie-vts-devandroid-vts-9.0_r9android-vts-9.0_r8android-vts-9.0_r7android-vts-9.0_r6android-vts-9.0_r5android-vts-9.0_r4android-vts-9.0_r12android-vts-9.0_r11android-vts-9.0_r10Treehugger Robot
2018-08-10AOSP builds do not support Device ID attestationEran Messeri
AOSP builds have different product & brand values than the ones flashed onto the device's Keymaster in the factory. As a result, Device ID attestation will not work on them correctly because there is a mismatch between the values sent to Keymaster by the platform and the values Keymaster is expecting to attest to. Mark AOSP builds as not having this feature since it would affect all AOSP builds on all devices. Bug: 110361822 Test: atest com.android.cts.devicepolicy.MixedDeviceOwnerTest#testKeyManagement Merged-In: I55e7c68b3e082af465c19cf18aeeeecffc4eb356 Change-Id: I55e7c68b3e082af465c19cf18aeeeecffc4eb356 (cherry picked from commit 4260ee9282f9666821dbdb4e7dda6c65f605a6b2)
2018-08-03Snap for 4930082 from 56eb975447788a58b3a8f858655c964d35e0ba75 to ↵android-build-team Robot
pi-qpr1-release Change-Id: Ib548805caedaf8afdb2f4d7a45fc67a62b0b89f5
2018-08-01SF: Layer children should call parents' onFirstRefDan Stoza
Classes which inherit indirectly from Layer and which override onFirstRef need to also call their parents' onFirstRef to ensure that Layer is initialized correctly. Bug: 111854867 Test: atest UiAutomationTest#testWindowContentFrameStats Change-Id: I5e29b6619d1a2e48277ad465a64d1f13bb92905c Merged-In: I5ceb531a5d59587ab489342d0b19a42c1a286402
2018-07-27Snap for 4916303 from bde9db506f38bb8caa6df016ca25fef5410b88b4 to ↵android-build-team Robot
pi-qpr1-release Change-Id: I6a6f14ff9f5c416859d174b0c05e622807ecbad9
2018-07-20Merge "SF: Add GL texture pool" into pi-devpie-dr1-devTreeHugger Robot
2018-07-17Do not block on allocating buffersJorim Jaggi
There is really no point in doing that because this can be done in an async way such that the first and subsequent dequeueBuffer still don't block because at that point allocation is very likely done. Furthermore, avoid calling setAsyncMode initially, as it will also block RT on buffer allocation. However, the default is false in any case, so we really don't need to call it. Also, only allocate one buffer at a time and don't block in dequeueBuffer on allocating buffers. It will likely have one buffer available already, and there is no point in waiting for other buffers to be allocated. Test: Press home with memory contention, observe less delay. Test: General smoke testing for increased jank Bug: 111517695 Change-Id: I9deb435013b2503178d2fe032151c1aaedd667af
2018-07-11Add current frame and barrier layer info to protobuf.chaviw
Added more info to the protobuf to help identify the root cause of the bug. Bug: 111062294 Test: go/winscope Change-Id: Ife93907482ad89341b20a5508acce04ad4a5b32e Merged-In: Ife93907482ad89341b20a5508acce04ad4a5b32e
2018-07-09Add SF proto dump to bugreportchaviw
Bug: 111062294 Test: adb bugreport Change-Id: I40aa5f75d40b401b4f0eef5390106b3dac62ef43
2018-07-03Merge changes from topic "boot-splash" into pi-devChia-I Wu
* changes: surfaceflinger: default to DisplayColorSetting::ENHANCED surfaceflinger: signalRefresh after boot animation starts
2018-07-03Merge "atrace: make 'lowmemorykiller' directory optional for memreclaim" ↵TreeHugger Robot
into pi-dev
2018-07-03surfaceflinger: default to DisplayColorSetting::ENHANCEDChia-I Wu
DisplayColorSetting works like a hint. On devices that do not support RenderIntent::ENHANCE, RenderIntent::COLORIMETRIC will be picked. Bug: 79434305 Test: Pixel 2017 and 2018 boot animations Change-Id: Ie85cca6eae75cf6ada3a4a364c402d09dc2920f9
2018-07-03surfaceflinger: signalRefresh after boot animation startsChia-I Wu
Assume BootStage::BOOTLOADER initially. Switch to BootStage::BOOTANIMATION on first buffer latch and switch to BootStage::FINISHED after bootFinished is called. Do not invoke signalRefresh when in BootStage::BOOTLOADER. We do not want to replace bootloader splash by a blank screen. This saves HWC from workarounds that may or may not work reliably. Bug: 79434305 Bug: 110772452 Test: reboot and observe Change-Id: I9e892e629303177431acd2cfe23f0f984ca6866e Merged-In: I9e892e629303177431acd2cfe23f0f984ca6866e
2018-07-03Merge "[SurfaceFlinger] Avoid querying Power HAL until switching color ↵TreeHugger Robot
mode." into pi-dev
2018-07-02atrace: make 'lowmemorykiller' directory optional for memreclaimCarmen Jackson
The 'lowmemorykiller' directory isn't used for lmk tracing on devices that have userspace lmk. Bug: 110999121 Test: The memreclaim option is available in Traceur on a device with userspace lmk. Change-Id: I5dadb5c6c55cb04b6fe079b5f10a3dc35f1ee3f1
2018-07-02[SurfaceFlinger] Avoid querying Power HAL until switching color mode.Peiyong Lin
Previously, SurfaceFlinger would query Power HAL speculatively at the first time color mode is set when device is booted. Howerver, Power HAL is not necessary started before SurfaceFlinger and it's not necessary to query Power HAL when color mode is not switched. As a result, the boot time is very long because SurfaceFlinger needs to wait for Power HAL to start. Thus, in this patch, we avoid querying Power HAL until color mode is switched, which won't happen until we enter wide-color-gamut Apps. BUG: 110112323 BUG: 111009852 Test: Build, flash and boot device, check hardware.power output with adb logcat Change-Id: Ia581461ba7861784bff35cac6fbeca9bac92b8fa
2018-06-29[SurfaceFlinger] Apply legacy saturation matrix globally for Display P3.Chia-I Wu
We disallow legacy saturation matrix since this commit. For those do have such a matrix, instead of applying it between sRGB->P3 conversion, we apply it on P3. This means P3 and HDR tone mapped to P3 are also saturated. Bug: 110840428 Test: See red/orange scene through Camera ViewFinder, take a picture, check the picture in Photos App, the red/orange should have similar saturation. Change-Id: I335b39888a76c7e411d9e03d9ad71448cbd7c05f Merged-In: I335b39888a76c7e411d9e03d9ad71448cbd7c05f
2018-06-27Merge "Add new PowerAdvisor interface for SF to pass hints to the power ↵TreeHugger Robot
HAL." into pi-dev
2018-06-26Add new PowerAdvisor interface for SF to pass hints to the power HAL.Michael Wright
GPU composition is slow with FP16 wide color gamut. In this patch, we try to mitigate this issue by boosting the GPU to higher frequency when SurfaceFlinger is going to switch to Display P3 color mode by sending the new PowerHint::EXPENSIVE_RENDERING to PowerManager. BUG: 110112323 Test: adb shell cat /sys/class/kgsl/kgsl-3d0/devfreq/cur_freq to verify GPU frequency with/without WCG content. GPU frequency should be high with WCG content, and should be reset without WCG content. Change-Id: I3758bcf9940e71d4b6d122d8916b7ad7f10f5397 Merged-In: I3758bcf9940e71d4b6d122d8916b7ad7f10f5397
2018-06-26Merge "AOSP builds do not support Device ID attestation" into pi-devEran Messeri
2018-06-26Merge "Don't access system properties from vendor code." into pi-devMartijn Coenen
2018-06-26SF: Add GL texture poolDan Stoza
Adds a pool of GL texture names. Prior to this change, Layer creation was forced to run on the SF main thread because it would need to call into RenderEngine to generate a new texture name. By creating a pool of pre-generated texture names, this operation no longer needs to run on the main thread, which unblocks the rest of the system during operations such as fingerprint unlock. Bug: 110477323 Test: SurfaceFlinger_test + manual: examine systrace and observe that layer creation no longer blocks on access to the main thread Change-Id: I9d68874d6c6f704c8884676454e84d916cd86507 Merged-In: I9d68874d6c6f704c8884676454e84d916cd86507
2018-06-25Merge "SurfaceFlinger: Fixes around rotation and cropping." into pi-devTreeHugger Robot
2018-06-25SurfaceFlinger: Fixes around rotation and cropping.Robert Carr
SurfaceFlinger's renderer is not prepared to handle cropping in the face of arbitrary rotation. To see the problem observe that if we have a square parent, and a child of the same size, then we rotate the child 45 degrees around it's center, the child must now be cropped to a non rectangular 8 sided region. We can fix this problem in the future (b/109894387), but for now we are lucky. SurfaceControl is private API, and the WindowManager only uses rotation in one case, which is on a top level layer in which cropping need not be an issue (this case is the screen rotation animation, where all the windows are rotated together). However given that the abuse of rotation matrices could lead to surfaces extending outside of theire intended crop, we need to prevent non root-clients without permission ACCESS_SURFACE_FLINGER (a.k.a. everyone except WindowManager and tests) from setting non rectangle preserving transformations. Our sad story continues, with the implementation of computeBounds. Notice the intersection with the parent window is done in screen space by applying and then inverting the transformation. However since the transformation doesn't preserve rectangles, we get a different, in-correct, and larger result from applying and inverting the transformation. We don't need to be performing this computation in screen space, it's enough to apply the local transform relative to the parent and then intersect with the parent's computed bounds in the parent space. When we write the logic this way it means we will only produce incorrect results for children who rotate outside of their visible region. In the case of the WindowManager rotation animation it rotates top level layers which do not have parents, and so we will not produce incorrect results. We lock down other cases and clients as described above. Unfortunately our story continues, since our implementation of final crop was relying on transforming Layers up to screen-space, this will no longer work with the new implementation of compute bounds. We have to change setFinalCrop to crop in parent-space rather than the final screen space. This is a semantic change, but luckily there is only one user of setFinalCrop and it is on a layer whose parent (The WM animation Layer) is already in screen space, so it's not a semantic change for any actual clients. Test: Manual. Bug: 69913240 Bug: 109894387 Change-Id: I522e258cee03ac8e3609a40f53461119b7c45532
2018-06-25Don't access system properties from vendor code.Martijn Coenen
A recently introduced optimization reduces the service polling interval to 100ms during boot. For this it uses the boot completed system property. However, vendor code isn't allowed to access system properties. This change keeps the behavior as it was, while not accessing the system prop. We can investigate later if we can do something similar for vendor code. Bug: 80153956 Test: builds, sailfish boots Change-Id: Ic52039516ae3e912ff2ec7c8dced4951696678df
2018-06-22AOSP builds do not support Device ID attestationEran Messeri
AOSP builds have different product & brand values than the ones flashed onto the device's Keymaster in the factory. As a result, Device ID attestation will not work on them correctly because there is a mismatch between the values sent to Keymaster by the platform and the values Keymaster is expecting to attest to. Mark AOSP builds as not having this feature since it would affect all AOSP builds on all devices. Bug: 110361822 Test: atest com.android.cts.devicepolicy.MixedDeviceOwnerTest#testKeyManagement Change-Id: I55e7c68b3e082af465c19cf18aeeeecffc4eb356
2018-06-21Allow for more flexible vsync-offsetsJorim Jaggi
The issue with just one single sf early offset is that this may be too early in case of steady rendering, i.e. when a Wide-Color-Gamut window is on screen. Instead, we allow for separate offsets in case we are in GL comp but the transaction wasn't marked as early, and when the transaction is marked as early. In addition to that, we also allow the app-vsync to be adjusted in these scenarios. Bug: 110112323 Change-Id: I26d73b88b4e9e609ceedb604e8338452d9a89093 Merged-In: I26d73b88b4e9e609ceedb604e8338452d9a89093
2018-06-07Merge "Camera: update tonemap curve images" into pi-devpie-devTreeHugger Robot
2018-06-07Merge "libbinder: fix using destroyed mutex warning." into pi-devYabin Cui
2018-06-07Camera: update tonemap curve imagesYin-Chia Yeh
Bug: 74942037 Merged-In: I2b4bffd685ddcb8899fb427b14c8a0ab937725c3 Change-Id: I2b4bffd685ddcb8899fb427b14c8a0ab937725c3
2018-06-06Merge "surfaceflinger: prime shader cache for P3 conversion" into pi-devChia-I Wu
2018-06-06Merge "surfaceflinger: force client composition for Y410" into pi-devChia-I Wu
2018-06-06surfaceflinger: force client composition for Y410Chia-I Wu
When the pixel format is Y410 masquerading as RGBA_1010102, always force client composition. Bug: 80509363 Test: no effect on Pixel devices Change-Id: I31996eeda1559b0557a5acb53d593fd4f395ccaf Merged-In: I31996eeda1559b0557a5acb53d593fd4f395ccaf
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-05 05:04:59 +0000