| 2efd6be69a00b55bd2c20f27a99039b5ac2c5ff3 |
|
31-Mar-2017 |
Shuzhen Wang <shuzhenwang@google.com> |
Camera: Use slowJpeg if JPEG minimum duration is less than preview fps
If the minimum duration of JPEG is less than the frame duration derived
from maximum fps, enable slowJpeg mode so that JPEG doesn't slow down
preview.
Cap the default max fps to 30 so that the switch between different
sensor modes can be minimized while still allowing the app to go higher
than 30fps.
Test: Camera1 CTS
Bug: 36692074
Change-Id: If4d367ac587c0f4d3620ca2d25063c5a12ebfceb
/frameworks/av/services/camera/libcameraservice/api1/client2/Parameters.h
|
| 0ba7cd85016caac178ee8e52f067ca9c42511dc3 |
|
10-Apr-2017 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "Camera: Don't advertize zoom in case max digital zoom is 1" into oc-dev
|
| 5b3570dcede02e7427b0bf3350499974ec8c75c7 |
|
04-Apr-2017 |
Emilian Peev <epeev@google.com> |
Camera: Don't advertize zoom in case max digital zoom is 1
Mark immediate zoom as not supported in case the camera has
maximum digial zoom close to 1. This will avoid corner
cases wehere we can have 'NUM_ZOOM_STEPS' all equal to 1.
Bug: 33093106
Test: Complete CameraTest CTS package
runtest -x cts/tests/camera/src/android/hardware/cts/
Change-Id: I039276385de74192375f36b1504dd89cb8ae0c52
/frameworks/av/services/camera/libcameraservice/api1/client2/Parameters.h
|
| 2638f7216de92f254a50dd55be1539f1c6b23552 |
|
04-Apr-2017 |
Emilian Peev <epeev@google.com> |
Camera: Advertise AE/AWB locks in case they are supported
AE/AWB lock availability is present in the camera static metadata.
Check whether they are supported before advertising them in Camera
Parameters.
Bug: 33091727
Test: Complete CameraTest CTS
runtest -x cts/tests/camera/src/android/hardware/cts/
Change-Id: I9a8cc8ffcc28b6b476904c3c011ab0ec65b162c9
/frameworks/av/services/camera/libcameraservice/api1/client2/Parameters.h
|
| 3b5fa81889299181f3463504ddff9e091846e1ba |
|
02-Nov-2016 |
Zhijun He <zhijunhe@google.com> |
Camera API1: don't pick wrong preview fps value am: 49aac43b4a am: 73952713b5
am: 341d2236fa
Change-Id: I504588f8f97a44c00725685a3808a312b98ca899
|
| 49aac43b4a323a8702d93b7cf878252905dc3987 |
|
01-Nov-2016 |
Zhijun He <zhijunhe@google.com> |
Camera API1: don't pick wrong preview fps value
Bug: 32556975
Change-Id: I69eb18abe191ae0f1e76f8b62daaf5717cce9669
/frameworks/av/services/camera/libcameraservice/api1/client2/Parameters.h
|
| 2e6d8d607fb3bd38d87fb7c1274680bbc4424398 |
|
27-Oct-2016 |
Zhijun He <zhijunhe@google.com> |
Camera API1: filter out the unsupported preview fps range am: 4f5dc7799f am: c4bea30beb
am: 34b27bc05f
Change-Id: I0593a3e694e6f8fa41b396cfbaaf4c7a4893ce7a
|
| 4f5dc7799f082d77e399d8beee7b017a02755cf6 |
|
26-Oct-2016 |
Zhijun He <zhijunhe@google.com> |
Camera API1: filter out the unsupported preview fps range
The advertised supported preview fps ranges need to be supported
by all preview sizes. This change does the check to make sure the
API1 doesn't over-advertise its capability.
Bug: 32360340
Change-Id: Iccd13967305f1d0a62b89da87070591bfb973bbf
/frameworks/av/services/camera/libcameraservice/api1/client2/Parameters.h
|
| 7bc559a13c14acb3e74ffc08fd0d898b4d494d4d |
|
12-Aug-2016 |
Chih-Hung Hsieh <chh@google.com> |
resolve merge conflicts of 70066d9 to stage-aosp-master am: 311f99eade
am: f671d5bbf8
Change-Id: I80d1494c33d33a5ebe784dd894148d90747ae726
|
| 311f99eade1222575bc65a2fcbd9f9a5a40d2024 |
|
12-Aug-2016 |
Chih-Hung Hsieh <chh@google.com> |
resolve merge conflicts of 70066d9 to stage-aosp-master
Change-Id: I9af1ace904388c91e6ce885e8a6d3540eb57bb4a
|
| 5404ee174dd6b5e312d3a97bc63c2bc8d142012b |
|
09-Aug-2016 |
Chih-Hung Hsieh <chh@google.com> |
Fix clang-tidy warnings in camera.
* Add explicit keyword to conversion constructors.
Bug: 28341362
* Use const reference type for read-only parameters.
Bug: 30407689
* Use const reference type to avoid unnecessary copy.
Bug: 30413862
Test: build with WITH_TIDY=1
Change-Id: I71d3008da843ba5f1df1a73a320fb2af6ceffa16
Merged-In: I71d3008da843ba5f1df1a73a320fb2af6ceffa16
/frameworks/av/services/camera/libcameraservice/api1/client2/Parameters.h
|
| c451d0f8098c9efd21d796e32f739af1915f9aba |
|
01-Jul-2016 |
Eino-Ville Talvala <etalvala@google.com> |
Camera: API1: Improve ZSL mode activation heuristics
- Don't engage ZSL if picture size is too small
- Don't engage ZSL if picture size matches preview size
- Include ZSL choice in dumpsys
Bug: 29620318
Change-Id: Ie8e0c5a9e1ed9f177d701f22996c4c1f4b81a71e
/frameworks/av/services/camera/libcameraservice/api1/client2/Parameters.h
|
| 8cca0750a84c2d97224c0cfef7cf255308ee80b3 |
|
14-Nov-2015 |
Chien-Yu Chen <cychen@google.com> |
Camera: Support BufferQueue between Camera and StageFright
Use a BufferQueue between Camera and StageFright to pass video
buffers for Camera HALv3 devices.
CameraSource in StageFright will try to use "buffer queue" mode
if it is supported by the camera device. In "buffer queue" mode,
CameraSource creates a buffer queue and a listener thread to recieve
video buffers from camera device. CameraSource then wraps the
ANWBuffer in MediaBuffer. If the camera device doesn't support
"buffer queue" mode, it falls back to "metadata in video buffer"
mode or "real YUV data" mode.
"Metadata in video buffer" mode is removed from Camera2Client and
only "buffer queue" mode is supported.
Bug: 24511454
Change-Id: Ice833b57bcd8d91852d6415402013f56f3e3970a
/frameworks/av/services/camera/libcameraservice/api1/client2/Parameters.h
|
| d309fb9c8a2c4564d88fffba19c4e3688e4b862b |
|
25-Nov-2015 |
Eino-Ville Talvala <etalvala@google.com> |
CameraService: Remove device HALv2 support, other cleanup
HALv2 only ever shipped with Nexus 10, and has been fully superceded by
HALv3. Remove it to allow for various code simplifications and cleanup.
- Remove Camera2Device
- Remove various special-case codepaths for supporting Camera2Device
- Remove CameraDeviceFactory, since it only creates Camera3Devices now
- Remove BurstCapture and associated CaptureSequence/Parameters code
- Remove old ZslProcessor and simplify ZslProcessor hierarchy to be
just ZslProcessor3, which is renamed to just ZslProcessor
- Add service-init-time check for unsupported device versions
- Fix assorted compiler warnings, some old, some new
- Remove references to HALv2 when possible
Bug: 25866588
Change-Id: Ia1063264d315f9b742ec5cdd0483539310894f5e
/frameworks/av/services/camera/libcameraservice/api1/client2/Parameters.h
|
| 355d9c6b74cd22a88fc7d1c9ba2e928ba566c69e |
|
25-Feb-2015 |
Yin-Chia Yeh <yinchiayeh@google.com> |
Camera2Client: handle slower jpeg stream sensor
If largest jpeg stream cannot sustain 30 FPS, don't
create jpeg stream until takePicture is called and remove
it after still capture is done.
Also, disable video snapshot for such sensors so video snapshot
won't slow down video recording.
Bug: 22231605
Change-Id: I2b34d2537c224694ae10f2006b5a46be45a1b1a6
/frameworks/av/services/camera/libcameraservice/api1/client2/Parameters.h
|
| d48521fc2f7c34623a745728a07dad728da49254 |
|
30-Apr-2015 |
Eino-Ville Talvala <etalvala@google.com> |
Camera: API1 shim: Don't tightly apply crop region
Due to older HAL compatibility, we have been setting a tight crop region
that just bounds the current output streams. However, this did not take
into account any possible ZSL output stream, so correct application of
our stream cropping rules to ZSL results in double-crop scenarios, if
the ZSL stream aspect ratio does not match the aspect ratio of the other
output streams.
Since all current HALs follow the correct stream cropping rules (or
at least sufficiently ignore them for ZSL), simplify the cropping
substantially - now either calculate the crop region based purely
off the active array dimensions and zoom factor, or purely off
the preview stream and zoom factor. The former is used for setting
the request crop, and the latter is used for converting coordinates
for metering regions.
Bug: 20316691
Change-Id: I5a0bc2e7c09cf60fbae4220566540ca9e674d652
/frameworks/av/services/camera/libcameraservice/api1/client2/Parameters.h
|
| d0e12a161471823d1ab269cb608be3f3b0a71ed1 |
|
21-Nov-2014 |
Dan Albert <danalbert@google.com> |
am 902dc42d: am 07715ac3: Merge "C++11 compatibility."
* commit '902dc42d79b075395d484ce1c71f215b199aaa2a':
C++11 compatibility.
|
| 36802bd18b7b4e8c87fa019c7e3068bee330d174 |
|
20-Nov-2014 |
Dan Albert <danalbert@google.com> |
C++11 compatibility.
* Fix string literal concatenation to not be interpreted as UD
literals.
* Add constexpr compatibility for non-integral static members.
* Use __typeof__ instead of typeof (should become decltype once this
actually becomes C++11).
* Add an appropriate cast for atomic_uintptr_t, since moving to C++11
means moving from <stdatomic.h> to <atomic>, which has better
typechecking (hooray for not macros!).
Bug: 18466763
Change-Id: I9561dcb2526578687819ff85421ba80d8e1a9694
/frameworks/av/services/camera/libcameraservice/api1/client2/Parameters.h
|
| 03181012beab17e145ca8b9bedbcc08d117df1cb |
|
19-Nov-2014 |
Yin-Chia Yeh <yinchiayeh@google.com> |
Merge "Camera2Client: remove recording stream if necessary" into lmp-mr1-dev
|
| 092d49c26d77fafad5170bf709c2a716ec335855 |
|
07-Nov-2014 |
Yin-Chia Yeh <yinchiayeh@google.com> |
Camera2Client: remove recording stream if necessary
Bug: 17495165
Change-Id: I11b763fde8f9448f4bddec3fe6c81581e7699edb
/frameworks/av/services/camera/libcameraservice/api1/client2/Parameters.h
|
| 5e15b80e801a0110bc1bad1190f02cb9c7d22e37 |
|
13-Nov-2014 |
Chien-Yu Chen <cychen@google.com> |
CameraService: normalize face rectangles properly
Use android.scaler.cropRegion reported in the capture result to
normalize face rectangles instead of using the one in current capture
request.
Bug: 11460393
Change-Id: Id21834bf6ae1f7cc106b4dffb98f9f249a75034b
/frameworks/av/services/camera/libcameraservice/api1/client2/Parameters.h
|
| a4c95a6bc3b801bf41ca841440e9124f947e53fe |
|
13-Sep-2014 |
Eino-Ville Talvala <etalvala@google.com> |
Camera: Allow larger preview resolutions in API1 for >= HALv2 devices
Limit preview resolutions to a max of 1920x1920 instead of 1920x1080p,
so that any aspect ratio with a 1920 as the larger dimension can be used.
Also improve the initial preview/video size selection logic, to ensure
that the selected size is both a valid preview and video size, and not
too large.
Bug: 17458832
Change-Id: Iea006fadb5fbf0f03d23c3c5babb5b3611469688
/frameworks/av/services/camera/libcameraservice/api1/client2/Parameters.h
|
| 3ea3fcd0822b2f43d87f1d8f67d7bf145864b201 |
|
05-Sep-2014 |
Yin-Chia Yeh <yinchiayeh@google.com> |
Camera2: reconfigure video snapshot size if needed
When recording fails to start due to stream configuration failed,
try configure stream again by setting jpeg stream to video size.
Bug: 16162133
Change-Id: Ib20271e787ae07719ce419f0b15c7f86434f7ebb
/frameworks/av/services/camera/libcameraservice/api1/client2/Parameters.h
|
| 0b88a62d4d5ac1e515721e587cdf9bcec191812b |
|
19-Mar-2014 |
Igor Murashkin <iam@google.com> |
camera: Fix setParameters for Preview FPS single/range values
As a workaround, duplicate CameraParameters into CameraParameters2 to
prevent ABI break for some camera HALs that directly link into
CameraParameters.
CameraParameters2 implements the real fixes needed in the framework,
while CameraParameters is left in to satisfy older camera HALs.
Bug: 12609188
Bug: 16654949
Change-Id: I82ea6f5de2183dd046d4bf5683600c97f37ab4da
/frameworks/av/services/camera/libcameraservice/api1/client2/Parameters.h
|
| cd8fce8fbe0f515e53a0ea0f50b739cf42ee57a4 |
|
18-Jun-2014 |
Yin-Chia Yeh <yinchiayeh@google.com> |
Camera2: get stream configs by device verison
Starting from device version 3.2, the following tags:
ANDROID_SCALER_AVAILABLE_FORMATS
ANDROID_SCALER_AVAILABLE_JPEG_MIN_DURATIONS
ANDROID_SCALER_AVAILABLE_JPEG_SIZES
ANDROID_SCALER_AVAILABLE_PROCESSED_MIN_DURATIONS
ANDROID_SCALER_AVAILABLE_PROCESSED_SIZES
ANDROID_SCALER_AVAILABLE_RAW_MIN_DURATIONS
ANDROID_SCALER_AVAILABLE_RAW_SIZES
are deprecated and replaced by:
ANDROID_SCALER_AVAILABLE_STREAM_CONFIGURATIONS
Change-Id: Iadc34af0ea985a16a25759d7a9a3eb4845c486fd
/frameworks/av/services/camera/libcameraservice/api1/client2/Parameters.h
|
| 0cbfbf3624c67cf40a18d5405a46d002aa12a048 |
|
28-May-2014 |
Zhijun He <zhijunhe@google.com> |
Camera3: Separate the video and preview size filtering
Supported video sizes were generated from supported preview sizes, which
effectively filtered out sizes larger than 1080p. This change filters the
supported video sizes based on the media profiles supported h.264 max video
frame width and height.
Bug: 15287656
Change-Id: Ifbd9d37fb775371e2a4ee5cf80abbf83a75ffd65
/frameworks/av/services/camera/libcameraservice/api1/client2/Parameters.h
|
| ce6249980434dd04e0eac397083d917cdc4452e9 |
|
24-Jan-2014 |
Ruben Brunk <rubenbrunk@google.com> |
camera3: Update maxRegions tag.
Change-Id: I22501cbf7f941d9626b88182e2dda8a13a620d01
/frameworks/av/services/camera/libcameraservice/api1/client2/Parameters.h
|
| d8a62e25ba6520c2531c7a3d32cc8066e1dab776 |
|
14-Nov-2013 |
Eino-Ville Talvala <etalvala@google.com> |
Camera2: Rework the FPS range vs. FPS single setting detection
Give up on current approach of writing out consistent FPS values
into parameters that will be read back by the app.
- Preserve app's latest set parameters exactly, and compare against
them when detecting if a new FPS range or single FPS value has been
selected.
- Since get() returns exactly what was set(), it doesn't matter if the
app calls getParameters() before its next setParameters(), in terms
of retriggering FPS selection logic. Before, the behavior varied
depending on whether the app re-read the parameters.
- As before, if app changes both range and single FPS in a single set
call, the range set wins. Otherwise, the value that has changed more
recently is used.
Bug: 11570973
Change-Id: I72b5e60c3f60e88d55127dd1bda87e26eaf929c6
/frameworks/av/services/camera/libcameraservice/api1/client2/Parameters.h
|
| fd6ecdd39bd83ea020f78b425e96310380d66c35 |
|
11-Oct-2013 |
Eino-Ville Talvala <etalvala@google.com> |
Camera HAL3/API1: Add support for the partial result quirk.
- Camera2Client:
- Detect partial result quirk
- Camera3Device:
- Accumulate all partial results together
- Fire off 3A-only result once all 3A states are available
- FrameProcessorBase:
- Filter out partials, don't send to listeners
- FrameProcessor:
- Skip face detect on partials
- Make sure to only handle a 3A update for a given frame once
- Trigger AF notifications when AF mode or trigger changes, to
properly detect all AF transitions.
Bug: 11115603
Change-Id: Iea8aa73c568701562a46071f7ea100624251d10b
/frameworks/av/services/camera/libcameraservice/api1/client2/Parameters.h
|
| 2b07e0207da44d7b3cc63c369fd10c9f12a5e2cd |
|
11-Oct-2013 |
Eino-Ville Talvala <etalvala@google.com> |
Camera2/3: Add more tracing for API1
- AF state
- Async autofocus completion
- Async takePicture completion
- Stages of takePicture
Bug: 10570497
Change-Id: Ida9fedd81aa4ee3ae3fb8dfada858a3bc3c213a3
/frameworks/av/services/camera/libcameraservice/api1/client2/Parameters.h
|
| 9fc79c6fccc41255bb4f3538e2a21b01db8dc2dc |
|
30-Sep-2013 |
Zhijun He <zhijunhe@google.com> |
Camera: Set default thumbnail size with matched aspect ratio
Make default thumbnail size match the default still capture size aspect ratio.
Bug: 10885012
Change-Id: If46da9508d3b71992f0e14a35c600b7e8d347f4e
/frameworks/av/services/camera/libcameraservice/api1/client2/Parameters.h
|
| 70b054021a3a22622c2710267362c5e235ed73bd |
|
21-Sep-2013 |
Eino-Ville Talvala <etalvala@google.com> |
Camera2/3: Properly disambiguate FPS range vs. single FPS setting
The camera1 API allows for either setPreviewFrameRate or
setPreviewFPSRange, so both values may or may not change in a single
setParameter call.
The disambiguation of which setting has been changed since the last
setParameter() call was not fully correct, so a sequence of changes
that only changed setPreviewFPSRange or didn't change either could be
interpreted as as a change to setPreviewFrameRate.
Bug: 10842868
Change-Id: I40baeced80a58f09f8a1742ece8dd5e141e9c1e3
/frameworks/av/services/camera/libcameraservice/api1/client2/Parameters.h
|
| 0181fde7bd20238cb13ae2665f0e5bfe7c2d9ac8 |
|
20-Sep-2013 |
Eino-Ville Talvala <etalvala@google.com> |
Camera2/3: For still captures, use widest FPS range available.
Instead of using the application-selected preview FPS range for still
captures, select the widest FPS range advertised by the device and use
it for still captures instead, to give the HAL the widest range of exposure
values to choose from possible.
Bug: 10842868
Change-Id: I0e24f5eb713a4f8df116cd5979a84390cc0974d7
/frameworks/av/services/camera/libcameraservice/api1/client2/Parameters.h
|
| 3ef464e095da6c5d1acb5723dbc4b9f7cfd4ecf8 |
|
12-Sep-2013 |
Zhijun He <zhijunhe@google.com> |
Camera: Limit supported preview sizes
The ANDROID_SCALER_AVAILABLE_PROCESSED_SIZES can provide sizes as large
as jpeg sizes, which could cause potential issues when trying to do
full size still capture and full size preview. This is not supported
by many devices due to hardware limitation. This change limits the
preview (as well video) size to no more than 1080p.
Bug: 10625115
Change-Id: I9467ab843553ec06e8249b4a17c0ecf4c6d6f04e
/frameworks/av/services/camera/libcameraservice/api1/client2/Parameters.h
|
| 7b82efe7a376c882f8f938e1c41b8311a8cdda4a |
|
26-Jul-2013 |
Eino-Ville Talvala <etalvala@google.com> |
Camera: Rename new API to camera2, rearrange camera service
- Support API rename from photography to camera2
- Reorganize camera service files
- API support files to api1/, api2/, api_pro/
- HAL device support files into device{1,2,3}/
- Common files into common/
- Camera service remains at top-level
Change-Id: Ie474c12536f543832fba0a2dc936ac4fd39fe6a9
/frameworks/av/services/camera/libcameraservice/api1/client2/Parameters.h
|