Age | Commit message (Collapse) | Author |
|
9007389] into qt-release
Change-Id: I10d7f5b7ccd28effeb39bbbbb7a454d819e1f93d
|
|
Big corner radii would cause problems at lower precision because
computing a vector norm would overflow. But since highp tanks
performance, instead scale down and back up by a power of 2 during the
normalization operation, so that a higher precision is not required.
Bug: 137191934
Test: eyeballing systrace when opening Photos, GPU seems to take shorter
time and no jank is observed
Test: Stepping through frames from a Pixel 3 XL screenrecording shows
that the beginning of the app opening animation is rounded instead of
square
Change-Id: Ie7a39bd0f992f7f42414ef49de9873775cc34409
Exempt-From-Owner-Approval: Approved in qt-r1-dev
(cherry picked from commit f941c1ea7e58e5bbe050e871165050f86b79f107)
|
|
8732114, 8738495, 8738319, 8736743, 8738320, 8738496] into qt-release
Change-Id: Ifa7fcd336a982ffb454544253f701374a34e072b
|
|
To decrease jank while rotating.
Test: Rotate screen
Bug: 138083790
Change-Id: I2b0d63bbf4143b9273a502ced451867f69e42636
Merged-In: I2b0d63bbf4143b9273a502ced451867f69e42636
(cherry picked from commit ef4b6013811b15086a6010edb61ac3413184fe5b)
|
|
In some devices where SF misses a frame in GL comp, HWC queue may
get stuffed. This causes application to block longer on dequeueBuffer
which leads to jank.
Test: 1. Open Camera
2. Swipe horizontally to go back to previous app.
Bug: 138083790
Change-Id: I4c5963cb7ba7f9b10254c77dc7117ca3acac81cf
(cherry picked from commit 4658e11cbe1abae691454ddcf93a06763d1bf828)
|
|
8660602, 8662138, 8660127] into qt-release
Change-Id: I0aa80da9a91e001b83bc2531ac9f3a0857b433c2
|
|
We need /data/media/obb on devices with old kernels. Since that folder
is present, we should check if there are contents there before migrating
data.
This also fixes the check for if the kernel supports the unshared_obb
option. If it does, it only does the migration if there is data to
migrate.
Test: Boot with GSI over P, boot normal Q, with and without data at
/data/media/obb. With data, it should migrate. Without data it
shoud skip the migration. On GSI on P it should skip the
migration.
Bug: 136199978
Change-Id: I41b0ec7a8a6b57b2ea6a530630d56c00f758009a
(cherry picked from commit c0439c785eafbbc1e2e88b94e15bae6e92e6c51b)
|
|
This prevents migrating the obb folder if the device's kernel does not
support the new location.
Test: Run script on kernel with support for the unshared_obb option, and
without, i.e. P kernel and Q kernel
Bug: 136199978
Change-Id: I3ff3e7653d9c9c6cdda4d17bafc853b5602597cf
(cherry picked from commit 8b6bff42b8cf7f8596278f3b34652deb3c7cdde2)
|
|
8558886, 8558887, 8558888, 8558889, 8558071, 8558072, 8556231] into qt-release
Change-Id: If94b5583cacf7855e75758a6998568eefa39026b
|
|
SurfaceFlinger can occasionally leak graphic buffers.
The leak happens when:
1) a transaction comes in and is placed in a queue
2) Chrome crashes
3) the parent layer is cleaned up
4) the child layer is told to release its buffer because it is
no longer on screen
5) the transaction is applied with sets a callback handle on the
layer which has a sp<> to the layer
To fix this, the callback handle should not have a sp<> to layer.
It is safe for the callback handle can have wp<> to the layer.
The client side has a sp<> so during normal operation, SurfaceFlinger
can promote the wp<>. The only time the promote will fail is if the
client side is dead. If the client side is dead, there is no one
to send a callback to so it doesn't matter if the promote fails.
Bug: 135951943
Test: https://buganizer.corp.google.com/issues/135951943#comment34
Change-Id: I756ace14c90b03a6499a3187d235b42d91cdd05a
(cherry picked from commit 0e24a8385a63be6a799da902e1d5ffcbb7519c2a)
|
|
Change-Id: I080ba81059f6c0f32d01e35f2f5dc554c0ba08b1
|
|
hiddenByPolicy." into qt-dev
|
|
Change-Id: I5cc45456c9b15eb5f05be3bf065c3b7e6d40901b
|
|
"am-76da18a1-f110-471a-a87f-39868ce95109" into oc-dev am: 10819cc391 -s ours am: 42805fd050 -s ours am: f3f9cff353 -s ours
am: 32615136ae -s ours
am skip reason: change_id If7421c452b5893ab2567323d265503a1ce304482 with SHA1 8bbd6f4f0d is in history
Change-Id: Ib858c40c3bbaa7ac3e4dd7d9050abbbcb2859634
|
|
"am-76da18a1-f110-471a-a87f-39868ce95109" into oc-dev am: 10819cc391 -s ours am: 42805fd050 -s ours
am: f3f9cff353 -s ours
am skip reason: change_id If7421c452b5893ab2567323d265503a1ce304482 with SHA1 231a12189b is in history
Change-Id: I941b32aad8dc7e209f0f5146bea8a2860f8a86d8
|
|
"am-76da18a1-f110-471a-a87f-39868ce95109" into oc-dev am: 10819cc391 -s ours
am: 42805fd050 -s ours
am skip reason: change_id If7421c452b5893ab2567323d265503a1ce304482 with SHA1 231a12189b is in history
Change-Id: I8e5068b97ca52d46623fb729986713c476d96759
|
|
|
|
"am-76da18a1-f110-471a-a87f-39868ce95109" into oc-dev
am: 10819cc391 -s ours
am skip reason: change_id If7421c452b5893ab2567323d265503a1ce304482 with SHA1 231a12189b is in history
Change-Id: I333ce1ee5ff2f0e261713e969c4e0722d12a3692
|
|
* changes:
[automerger] Fix race between SensorManager ctor and callback am: 4b23ed10ae am: c88995f5d8 am: 2cd1ad424e am: 648bed8273 skipped: d0a1025778
[automerger] Fix race between SensorManager ctor and callback am: 4b23ed10ae am: c88995f5d8 am: 2cd1ad424e am: 648bed8273
[automerger] Fix race between SensorManager ctor and callback am: 4b23ed10ae am: c88995f5d8 am: 2cd1ad424e
[automerger] Fix race between SensorManager ctor and callback am: 4b23ed10ae am: c88995f5d8
[automerger] Fix race between SensorManager ctor and callback am: 4b23ed10ae
Fix race between SensorManager ctor and callback
|
|
Change-Id: If452edf5c6ace43c0964adbd9d58eb4d00c4a808
|
|
231a12189b am: 4245ab3a0f am: ade39600c5
am: 4158f80438 -s ours
am skip reason: change_id If7421c452b5893ab2567323d265503a1ce304482 with SHA1 8bbd6f4f0d is in history
Change-Id: I66f7d1c8289030ddfb1dcad68f6d8bc54946332e
|
|
am: ade39600c5
Change-Id: I027ea10e13f9cabad72fe96739a8e25fe0b69881
|
|
am: 4245ab3a0f
Change-Id: I41b42796fb21641af2f8bc14733212f189520995
|
|
am: 231a12189b
Change-Id: Id272955770700f18cb113c68f807728c4a1f0802
|
|
Now that we are using relative Z for the SurfaceView background we
encounter yet another edge case. During Surface preservation we reparent
the SurfaceView from one WindowStateAnimator to a second. When we reparent
it we hide the old surface and show the new one. However at this time
the background is still relative to the OLD surface, which is Z ordered
on top of the new Surface. To fix this we ensure that if a layers relative
Z parent is hidden by policy the layer is also invisible.
Bug: 136061599
Test: TransactionTest#HideRelativeParentHidesLayer
Change-Id: I941fb9060dab79dba89300a5c86d6ea1a69f577d
|
|
am: c88995f5d8 am: 2cd1ad424e am: 648bed8273 skipped: d0a1025778
Change-Id: I4b7f7433805aa3297d823bae9fbc75db79e076b9
|
|
am: c88995f5d8 am: 2cd1ad424e am: 648bed8273
Change-Id: I2daed7ee8ab62787f4dda1f0fdc629356a8bf9ea
|
|
am: c88995f5d8 am: 2cd1ad424e
Change-Id: Ib67db083237bef98dc44674483340f5b95a8e4eb
|
|
am: c88995f5d8
Change-Id: Ifd8e06c0a18b17df30295017d86bb7fcb2ffef94
|
|
Change-Id: I6ffcf79d2a61f35ac859b6702ee3582375f0c83b
|
|
Avoids potential invalid memory access if system server crashes during
initialization.
Bug: 132927376
Test: confirm sensors initialize
Change-Id: If7421c452b5893ab2567323d265503a1ce304482
Merged-In: If7421c452b5893ab2567323d265503a1ce304482
|
|
Avoids potential invalid memory access if system server crashes during
initialization.
Bug: 132927376
Test: confirm sensors initialize
Change-Id: If7421c452b5893ab2567323d265503a1ce304482
Merged-In: If7421c452b5893ab2567323d265503a1ce304482
|
|
|
|
Avoids potential invalid memory access if system server crashes during
initialization.
Bug: 132927376
Test: confirm sensors initialize
Change-Id: If7421c452b5893ab2567323d265503a1ce304482
|
|
realloc on resize am: edd3e3d8f4 am: c0394a6662 am: fbdb526a6a am: 40d0133f6d am: 5ab710e476 am: c1aa15f04d am: bfb94faeac am: f658b2d8b3
am: 5b788aa514 -s ours
am skip reason: change_id I82e7e8c7b4206fb45b832a71d174df45edb62710 with SHA1 6af27a8325 is in history
Change-Id: I61c367b9c11fa13a6c3de8a3ed2f173f3ed4dde5
|
|
edd3e3d8f4 am: c0394a6662 am: fbdb526a6a am: 40d0133f6d am: 5ab710e476 am: c1aa15f04d am: bfb94faeac
am: f658b2d8b3
Change-Id: Ib5613a17fa841e618c04030c4aebbe20fbb30107
|
|
edd3e3d8f4 am: c0394a6662 am: fbdb526a6a am: 40d0133f6d am: 5ab710e476 am: c1aa15f04d
am: bfb94faeac
Change-Id: I5a79edc66eb729715b4752774463d7906a348318
|
|
edd3e3d8f4 am: c0394a6662 am: fbdb526a6a am: 40d0133f6d am: 5ab710e476
am: c1aa15f04d
Change-Id: Ia0d05a58b9558e56fa598ffaf908f7fda7b19549
|
|
Change-Id: Icb51f0d92e54a3b41893d61efeb7253ccfe5000a
|
|
qt-dev
|
|
Prevously when App Activity launches, we send GpuStats on the main UI thread.
The async binder to send the stats only takes 30us. However, to get the
gpuservice, the sync binder takes around 1.5ms because of the massive binders
on CPU at Activity launch. Thus we just move the stats sending to a separate
thread off the main UI thread. Now it's just 50us cost on the main UI thread.
Bug: 136228448
Test: systrace and check
Change-Id: Iff47dbc6a26a9d62ad33e92f93c079ac74fb3ea2
|
|
edd3e3d8f4 am: c0394a6662 am: fbdb526a6a am: 40d0133f6d am: 5ab710e476
Change-Id: I2c585ccff7d630ac4f329f2c4ccc4d6c8540f43c
|
|
edd3e3d8f4 am: c0394a6662 am: fbdb526a6a am: 40d0133f6d
Change-Id: I85737c8144061c40d52a73b11a2562ac196dac2e
|
|
edd3e3d8f4 am: c0394a6662 am: fbdb526a6a
Change-Id: I8fa8c7a64666f44daa3ca4cab5398fd725fac950
|
|
edd3e3d8f4 am: c0394a6662
Change-Id: I45753b4f096ee379fc4a3708cc2e4fc2375d034b
|
|
edd3e3d8f4
Change-Id: Icc56d6f932b8220118f57328113d19184617c4dc
|
|
Bug: 134168436
Bug: 133785589
Bug: 34175893
Test: atest CtsOsTestCases:ParcelTest#testObjectDoubleFree
Change-Id: I82e7e8c7b4206fb45b832a71d174df45edb62710
Merged-In: I82e7e8c7b4206fb45b832a71d174df45edb62710
|
|
This tracepoint is used to log changes to the GPU clock speed
which is useful for developers and should be available in user
builds.
This tracepoint is used by Perfetto (see bug for details).
Bug: 136062452
Merged-In: If7e43bcf95e0f2162af618b20d3c26aad3264f97
Change-Id: Id7f57d659c6f52649a8516d8ede3ce0f7b2f497e
|
|
Change-Id: Ic056e15d0f8e4d55078146df310f109dc528d806
|
|
|