| 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
|