android_frameworks_ex - Unnamed repository; edit this file 'description' to name the repository.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Check isZoomSupported before any zoom ratio calculations.	Alan Newberger	2014-10-05	1	-1/+1
\| \| \| \| \| \| \| \| \| \|	Per API doc, isZoomeSupported should be checked before calling getZoomRatios or getMaxZoom. Moving zoom calculation into isZoomSupported check fixed crash in front camera with no zoom support, where a HAL/fwk returns a null list of zoom ratios. Bug: 17863266 Change-Id: I80b5f7a431e7bbe4d50e5d062628e38eda3fd0a6
*	camera2-portability: Switch to ratio-based zoom interfaces	Sol Boucher	2014-08-21	1	-3/+4
\| \| \| \| \| \| \| \| \|	This eliminates the deprecated index-based CameraSettings zoom methods in favor of floating-point ratio based versions, and includes the plumbing to make those work for both the camera1 and camera2 underlying framework APIs. Bug: 17016658 Change-Id: I0567a53cd57bfa6d53604e3c5457a39ef49e3cb4
*	add TORCH support to camera1 portability library	Alan Newberger	2014-07-30	1	-0/+2
\| \| \| \| \| \| \|	In the move to the portability library, TORCH mode got dropped. Bug: 16680156 Change-Id: I3878c2399246bdb5cc80311c49533971c0c4c3d2
*	camera2-portability: Add support for previews using the camera2 API	Sol Boucher	2014-07-08	1	-239/+2
\| \| \| \| \| \| \|	At the moment, only SurfaceTextures (and not SurfaceViews/SurfaceHolders) are supported. The tests still only cover Stringifier and IntegralStringifier. Change-Id: Ie643c58f8383cd3b9f59c16e0b79239df0ca068d
*	Add various supports in settings and capabilities.	Angus Kong	2014-06-18	1	-0/+2
\| \| \| \| \| \| \| \| \| \|	1. View angles in capabilities. 2. Preview formats setting. 3. Photo formats setting. 4. Recording hint for video recording preview setting. 5. JPEG thumbnail size setting. Change-Id: Ib8e33cf838859ae76a662fffcc496250ad85c203
*	Refactor out Camera.Parameters.	Angus Kong	2014-06-18	1	-48/+85
\| \| \| \|	Change-Id: Ibc1ddac509381530e887b7491069e6367e9a6088
*	First Step: CameraCapabilities intead of Parameter	Angus Kong	2014-06-18	1	-0/+451
	To get rid of Camera.Parameters, we need to provide our own interfaces. Camera.Parameters actually consists of 2 parts: capabilities and settings. We'll provide two interfaces and will just use Camera.Parameters inside of CameraManager implementations. Change-Id: I53922b6d740835412d74365374a6a0382129564e