| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Bug: 13415624
Change-Id: Ia2ed4b5bc7289f8d8ab6e6a431746b43c81842bc
|
|
|
|
|
|
|
|
|
|
|
| |
Add a test to test multiple stream configuration: one preview stream, one small
size YUV burst capture stream, and one large size YUV burst capture stream.
Also cleanup the code.
Bug 10325342
Change-Id: I676484cc0034055caa8f2a8788100ed34b4cefbb
|
|
|
|
| |
Change-Id: Ibf73106f8be63cf433fafe9510c8477f74b7ac41
|
|\ |
|
| |
| |
| |
| | |
Change-Id: Ie13b251d6bfadd533fa045ec5d3299ee8ae752af
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
By default, this test runs through a range of application-set
exposure, frame duration, and sensitivity values, and verifies
that the duration of capture, and in some cases the brightness,
match what's expected.
Optionally, it can use environment variables to specify the
burst parameters, and to enable dumping the captured YUV images
to flash for later debugging.
Change-Id: I647d360344ef3684e99c86c369e96ac82e62fc96
|
|
|
|
| |
Change-Id: Ie11270cc8cf301ec94795b595f0517ee3bad2817
|
|
|
|
| |
Change-Id: Ibc2917a18163f07b5e37eb83abb3d1ef919a5766
|
|
|
|
| |
Change-Id: I7e066569edcab84c0d61fe7a4ae5c3e2683f63eb
|
|
|
|
| |
Change-Id: Iff197c557c06673a1ad85a9bbd36caa38efb88b7
|
|
|
|
|
|
|
|
|
|
| |
This fixes a segfault in the HAL where it was trying to write to a locked buffer
that disappeared from underneath it.
Any users of CameraModuleFixture should now call SetUp/TearDown explicitly.
Other classes remain unchanged until we need a custom TearDown order for them.
Change-Id: I9aa8c2d86492a76f2c01c1ad4cbe0cf91e5c7916
|
|
|
|
| |
Change-Id: I0adfda42e861d7e5a85801f7e0c3f0b3950b6e0e
|
|
|
|
| |
Change-Id: Idc1a3ebb26d0e189a543435f7f9be5f6376963d6
|
|
|
|
|
|
|
| |
Use CAMERA2_TEST_FORKING_DISABLED=1 environment variable to override this
behavior (e.g. when wanting to attach gdb to the test app).
Change-Id: Ib639885bdb827fc2415c878cbcb1b2d84dff687b
|
|
Change-Id: I1f1afd5afc346d5493d5019af35c3026efcf19b5
|