As far as I can tell, this is the only place where soong is used
to build renderscript.
Bug: 137365032
Test: make checkbuild
Test: cd frameworks/compile/slang/tests
./slang_tests.py
Test: atest CtsRenderscriptTestCases
Test: CtsRsCppTestCases
Change-Id: I10a23ceee696df7fe363cc5d825e45100565cbdf
Merged-In: I10a23ceee696df7fe363cc5d825e45100565cbdf
Currently, an input surface to an encoder is created in the codec
process, but the queue operation has to be issued from the application
process. This CL allows an input surface to be created in the
application process, hence reducing the number of IPCs issued per frame.
This option can be chosen by setting "debug.stagefright.c2inputsurface"
to -1. (If the property is not set, it defaults to 0, which picks the
current behavior.)
Test: adb shell setprop debug.stagefright.c2inputsurface -1
Then, record a video.
Bug: 131800183
Bug: 134017277
Change-Id: Idbf2ba87689e1e876a215850aa0260539183a4ee
(cherry picked from commit 1858832f47)
am: b693081b7a -s ours
am skip reason: change_id I273f77aac2b80ba9be70197cc3842f83a11bbd1c with SHA1 9c4eec2bb2 is in history
Change-Id: Id3d1beeebe2bcecabbd996c22f70500afb8234c4
unlinkToDeath is no longer required, (this change in behavior is to
avoid leaks) so holding onto ActivityManager here (still calling
unlinkToDeath to avoid a log, but may for instance remove all
unlinkToDeath calls in the future).
Exempt-From-Owner-Approval: approval received on AOSP CL, only
whitespace difference here.
Bug: 134576445
Test: boot
Change-Id: I273f77aac2b80ba9be70197cc3842f83a11bbd1c
Merged-In: I273f77aac2b80ba9be70197cc3842f83a11bbd1c
(cherry picked from commit 2f34814d1b)
unlinkToDeath is no longer required, (this change in behavior is to
avoid leaks) so holding onto ActivityManager here (still calling
unlinkToDeath to avoid a log, but may for instance remove all
unlinkToDeath calls in the future).
Exempt-From-Owner-Approval: approval received on AOSP CL, only
whitespace difference here.
Bug: 134576445
Test: boot
Change-Id: I273f77aac2b80ba9be70197cc3842f83a11bbd1c
VTS component test currently fails for multiple release and reset APIs
This fail is because of ASSERT on the return type of these APIs.
However these multiple release/reset APIs need not always return C2_OK.
Test: VtsHalMediaC2V1_0TargetComponentTest -I default -C c2.qti.avc.decoder
Bug: 132403160
Change-Id: I6e0f2e227c82c522dd590b9c683add206b41eac0
QTI components were failing VTS under following conditions :
1) unsupported resolutions.
2) fetchGraphicBuffer failed
In all these cases, test should be skipped instead of getting marked as FAILED.
Test: VtsHalMediaC2V1_0TargetVideoEncTest -I default -C c2.qti.avc.encoder -P /sdcard/res/
Bug: 132405032
Change-Id: Icd020135ee735f9f976a3a2cadf8a7ef5e378feb
unlinkToDeath is no longer required, (this change in behavior is to
avoid leaks) so holding onto ActivityManager here (still calling
unlinkToDeath to avoid a log, but may for instance remove all
unlinkToDeath calls in the future).
Bug: 134576445
Test: boot
Merged-In: I273f77aac2b80ba9be70197cc3842f83a11bbd1c
Change-Id: I273f77aac2b80ba9be70197cc3842f83a11bbd1c
Original logic was comparing an overridden format int, switch
to use a const original format.
Test: partner device, Pixel 3 CTS
Bug: 136456900
Change-Id: I03d6e190770ee05e40446c417e323f546fdc2689
Jeff Vander Stoep
android-build-team Robot
Wonsik Kim
Pawin Vongmasa
Steven Moreland
Treehugger Robot
Xin Li
Manisha Jajoo
Yin-Chia Yeh
Dongwon Kang
Praveen Chavan