Age | Commit message (Collapse) | Author |
|
|
|
Revert submission 29890736-anativewindow-setframerateparams
Reason for revert: removing API to be landed in another release.
Reverted changes: /q/submissionid:29890736-anativewindow-setframerateparams
Change-Id: I366030e9bcb4b468e728cf425c1c22360700fe71
|
|
This already exists in AIDL, and will exist in the SDK
Bug: 355264141
Flag: EXEMPT NDK can't be flagged!
Test: builds
Change-Id: I32fd0e9d5c58363393d5217211d1f5fe9e14f86b
|
|
The new overload uses same plumbing and same logic as the other
setFrameRate-like functions. This plumbing and logic will be upgraded to
accommodate new parameters in a future CL.
Bug: 362798998
Test: atest SetFrameRateTest
Flag: EXEMPT NDK
Change-Id: If29c32a92b48c36fe06c70db5505f73cea482637
|
|
Also fix that some ADataSpace enum values were not prefixed
with ADATASPACE_*
Test: atest AHardwareBufferTest
Bug: 315475131
Change-Id: Ie92f416a209501fa8fdc9b3593ea6d3bb68eaa48
|
|
This reverts commit 265f96fb55dcacb3dc038ef5b2f9d9387c9fc037.
Reason for revert: Fixed underlying issue
Bug: 276807477
Test: atest android.graphics.cts.ANativeWindowTest#testSetBuffersDataSpace
Change-Id: I101c246f673bf279c3c441759b82bdc607794b75
|
|
This reverts commit e4f832e21dbad52f7b455d557584d8baad66dd6f.
Reason for revert:
DroidMonitor: Potential culprit for Bug b/277122111 - verifying through ABTD before revert submission. This is part of the standard investigation process, and does not mean your CL will be reverted.”
Change-Id: I0fc4f98eb83448562c57433aa68018bcfee746bf
|
|
Bug: 276807477
Test: SilkFX demo
Change-Id: I3d11924199b4eb18cd0ec3fbddc88ed7d5c42a6e
|
|
Bug: 268427650
Test: atest android.graphics.cts.ANativeWindowTest
Change-Id: I19d7390998edbad960fe8812ec1d57e5a725b4e6
|
|
Bug: 246597190
Test: m
Change-Id: Ia11f47de9b52ecfc41119fcf2605b5ac56b07275
|
|
Bug: 251850069
Test: m
Change-Id: Ia47a5c6a83a7c51b4034c901f6ffc9813d3a6eb3
|
|
This API is same as using setFrameRate with 0 as frame-rate value. But
this causes confusion, as the remaining two arguments are ignored, when
frame-rate is 0.
Bug: 241096917
Test: android.graphics.cts.SetFrameRateTest#testClearFrameRate
Change-Id: I469e41cc1a15abf4c0b402caca12a9f6db4cdb71
|
|
This is useful for ANGLE (OpenGL ES implementation layered on top
of Vulkan) which needs to the know the default dataspace to pass
along to Vulkan when creating a surface/swapchain for an
ANativeWindow.
See http://aosp/q/topic:cuttlefish-angle-colorspace
Bug: b/229286407
Test: lunch aosp_cf_x86_64_phone-userdebug &&
m &&
cts -m CtsMediaCodecTestCases
Change-Id: Ie7a0c4b4f409f730f5c70bd88485644cfa03f10d
|
|
Bug: 235218604
Test: builds
Change-Id: Ia2b4be4ac2936b6e136d58d107ec0fe4f5b41a0e
|
|
Bug: 205034862
Test: builds
Change-Id: I1ac30853a873744027c2ea0aac731ecb76ca3b34
|
|
|
|
Bug: 201535612
Test: builds
Change-Id: I0851a5fcf8afaa8cf9f9f8a6d15da3f60e601fd5
|
|
Bug: 201535612
Test: build pass
Change-Id: Iecde54a4ba554f16bcb381ab65c8d9d8f22222bb
|
|
Bug: 201539996
Test: build pass
Change-Id: I91b65470567d243213cf7e1dbabec5ff41130371
|
|
Bug: 200309580
Test: build pass
Change-Id: Ibe184ca6edcbd61677d2cdf5d45e0ad24161ee30
|
|
Previously when we switch to only expose VNDK header, the
ANativeWindow_query doesn't properly recognize
ANATIVEWINDOW_QUERY_BUFFER_AGE as a VNDK query and hence a -EINVAL was
returned. This patch makes sure it is identified and skipped to complete
the actual query.
Bug: b/189551931
Test: manual
Change-Id: I9d4ef74dec3315e661e5a01e7b34a9f97f41fe78
|
|
Change the shouldBeSeamless parameter to an enum
in order to make the API easier to understand.
This changes
- SurfaceControl.setFrameRate
- Surface.setFrameRate
- ANativeWindow_setFrameRateWithChangeStrategy
- ASurfaceTransaction_setFrameRateWithChangeStrategy
Bug: 179116474
Test: atest SetFrameRateTest
Change-Id: I28a8863ea77101f90b878fbda5f00d98e075b7cc
|
|
This CL adds a new parameter shouldBeSeamless to the existing
setFrameRate APIs. This parameter indicates whether the desired
refresh rate should be achieved only seamlessly or also switches
with visual interruptions for the user are allowed. The default
value of the new parameter is "true".
Test: atest RefreshRateConfigsTest
Test: atest SetFrameRateTest
Test: atest libsurfaceflinger_unittest
Test: atest libgui_test
Bug: 161776961
Change-Id: I0df16e09f77c8c198fd3733fb581a2aaadfed685
|
|
|
|
Add a compatiblity param to the setFrameRate() api, so the system has
more info to decide the device frame rate when there are multiple
competing preferences.
I also changed the plumbing for setFrameRate() to go directly to surface
flinger, instead of through buffer queue. We're trying to avoid changes
to buffer queue code, to avoid disturbing the prebuilts.
Bug: 137287430
Test: Added new cts tests to verify behavior of the compatibility param.
cts-tradefed run commandAndExit cts-dev --module CtsGraphicsTestCases --test android.graphics.cts.SetFrameRateTest
Test: /data/nativetest64/SurfaceFlinger_test/SurfaceFlinger_test --gtest_filter='SetFrameRateTest.*'
Change-Id: Ibe75a778fb459d4138a1446c1b38b44798b56a99
|
|
* move ANativeWindow_getFrameId to a platform api, as
native_window_get_frame_timestamps is not stable and therefore the
associated api surface is not complete enough to be stable.
* Adjust documentation for returned errors. In most cases errors aren't
returned in practice. In the case of ANativeWindow_setDequeueTimeout the
errors are enumerated explicitly.
Bug: 148962594
Test: builds
Change-Id: I1ff5113d91fdcfc4679b2862af72fbf811171253
|
|
* rename allocateBuffers to tryAllocateBuffers to reflect that its a
best-effort API
* promote to public NDK
Bug: 148962594
Test: builds
Change-Id: Iff73c2eb7bb07d28ef26b95202257950e9da4627
|
|
Stable API for getNextFrameNumber. Here the naming is mirroring the
existing EGL api for eglGetNextFrameIdANDROID.
Bug: 137012798
Test: builds
Change-Id: I8bf6fb198055a295b8aa68d3b9db2577376d39b1
|
|
|
|
|
|
Bug: 137012798
Test: builds
Change-Id: Ibe2afe83d48adb583bfbda088376fcf402050814
|
|
This is to support HWUI's ReliableSurface.
Test: builds
Test: Hook up with HWUI and manually verify with settings app
Change-Id: I3a1d75dbd993dde1771930ad25212d8e4e7d94a0
|
|
setFrameRate() is a new api in Android 11 that will enable apps to
specify their intended frame rate.
Bug: 143912624
Bug: 137287430
Test: Added a new CTS test - android.graphics.cts.SetFrameRateTest.
Change-Id: I0150055fbffd37f2d644829e9dadbfc517045d8e
|
|
In order to allow NDK image decoding to access more color spaces, extend
ADataspace to match Named.ColorSpace as many as possible.
BUG: b/140635413
Test: build
Change-Id: I8e06071060ab19b103900ff04d60f1c3d3fccda9
|
|
Use perform() instead in query() to retrieve dequeue/queue durations for
nanosecond resolution.
Bug: 137012798
Test: atest
Change-Id: I894a8784f3321d4ab6f538d7e7fc1457de26f289
|
|
HWUI and media both require setting a dequeue timeout so that dequeue
calls don't hang.
Bug: 137012798
Test: libnativewindow_test
Change-Id: Ic85b07096d490918ae4a722516b8c4b6cb0ab678
|
|
Also adding private query64 hook so that timing queries can have
nanosecond precision. Otherwise with a 32-bit width we can only have
millisecond precision for timestamps and microsecond precision for time
intervals, and really we shouldn't need to be less precise if we can
help it.
Bug: 137012798
Test: libnativewindow_test
Change-Id: I62233a588eee80f7ea70b74824c8e47461a3be81
|
|
Bug: 137012798
Test: libnativewindow_test
Change-Id: I46d5ab9c11161923ebbbc67400b10b2e7c0c6b61
|
|
* Add ANativeWindow_getLastDequeueDuration as proof of concept
* Add ANativeWindowTest harness
* apex/ include directory for code living in apex modules, so that vndk
or system apis aren't pulled in
* TEST_MAPPING configuration for presubmit
Note that we're not piggybacking off of the existing Surface_test
harness, as those tests assume that the libgui Surface is The
ANativeWindow surface implementation, which means that those tests may
test implementation details that the harness defined in this change
should not attempt to test. Further, if an alternative implementation is
provided (e.g. an ANativeWindow -> BLAST adapter), we should be able to
parameterize the tests here. For now, however, we'll keep the assumption
that Surface is the only relevant surface implementation so that nonzero
tests may be written.
Bug: 137012161
Bug: 137012798
Test: libnativewindow_test
Change-Id: I0dddc348563ba95530fb1bd04bde66080755a91d
|
|
This change adds an option for the producer to set auto pre-rotation on the
buffers to be allocated. When auto pre-rotation is enabled, if the current
buffer size is driven by the consumer and there's 90 or 270 degree rotation
specified in the transform hint currently used by the producer, then the
dimension of the buffers to be allocated will be additionally swapped upon
buffers pre-allocaton or dequeueBuffer.
Auto prerotaion will be cached at Surface producer side, and will be
reset to false upon Surface disconnection.
Bug: 129422697
Test: atest libgui_test:SurfaceTest#DequeueWithConsumerDrivenSize
Change-Id: I01ddf3e00d5951935e557d18932ea9869f36b5d6
|
|
Explicitly cast enum type to int for value comparison.
Bug: 72330874
Test: m checkbuild
Change-Id: Ic0403fbb525c47a19c7d788686857f60ffb89990
|
|
For OpenGL based camera viewfinder implementations, we want to let them
read the Transform bit off the original camera API provided image and
forward it to their OpenGL surface so they can achieve the same rotation
functionality.
Bug: 74400997
Test: Manual
Change-Id: Idccd977e6d885b1b12de019faa98b564cc7baf48
|
|
Previously, ANativeWindow_setBuffersDataSpace is only available in VNDK. This
patch exposes it in NDK so that display mode for NativeWindow buffer can be set
through NDK. The API will remain available in VNDK of NativeWindow since VNDK
is the super set of NDK.
BUG: 62482961
Test: bit CtsGraphicsTestCases:.ANativeWindowTest
Change-Id: I576c4b87296e168d4b7360c437a32bbbbff690a5
|
|
Revert "Revert "use 64-bits usage bits almost everywhere""
This reverts commit 1671de0068de40f57288628d4b757a1c84962a62.
Test: manual, build
Bug: 33350696
Bug: 38466700
Change-Id: Ia2f51b97137dba754b1938dfb1e235f4babc8a88
|
|
Bug: 38466700
This reverts commit 175d98757d7d9003d4f64756cf4c2b366ba77e97.
Change-Id: I5f08a4ca91511775cd52250d10a0220b258b8368
|
|
Test: manual, build
Bug: 33350696
Change-Id: Ida33c2a902155044651158467bb99d664e958c41
|
|
Bug: 37647680
Bug: 37648355
Test: compile, manual
Change-Id: I9631beea52e23ebb519411f943c6f5062aedd2e5
|
|
Bug: 33350696
Test: compile, boot device, cts
Change-Id: I2f078cf4bbdf0db49f2e914b051f55629fb37eb6
|
|
this is to allow vendors to use AHardwareBuffer’s
lock/unlock on buffer dequeued from an
ANativeWindow.
Test: compiled
Bug: 36866217
Change-Id: If630105572ae0e57f6fda19c13e82150f415ed6b
|
|
Converting from ..graphics.allocator@2.0 usage to gralloc0 usage isn't
quite as simple as ORing and truncating, which is what the default
implementation was doing. Switch to using library functions that do it
correctly.
Test: boot bullhead
Change-Id: Ibe644b53655e191b9bca9d619825a8918e8fc365
|