camerax

Replace CameraDevice and CameraCaptureSession callbacks with ProcessCameraProvider bound to a LifecycleOwner, and swap ImageReader flows for ImageCapture and ImageAnalysis use cases. Use Camera2Interop.Extender when you still need specific CaptureRequest options like CONTROL_AE_MODE.

Use CameraXViewfinder with a SurfaceRequest and CoordinateTransformer to map tap offsets, then create a metering point with SurfaceOrientedMeteringPointFactory and call cameraControl.startFocusAndMetering. Avoid wrapping PreviewView in an AndroidView, which causes resizing issues.

PendingRecording.withAudioEnabled returns a new instance rather than mutating the existing one, so ignoring the return value silently drops audio. Chain the call or reassign the variable before calling start, and verify RECORD_AUDIO permission is granted.

Prefer MlKitAnalyzer from the camera-mlkit-vision artifact, which automates coordinate mapping and multi-format support over manual ImageAnalysis.Analyzer implementations. Always close each ImageProxy and use STRATEGY_KEEP_ONLY_LATEST to avoid queuing stale frames.

Yes, combine Jetpack WindowManager FoldingFeature detection with ViewPort updates so tap-to-focus and capture coordinates stay accurate across tabletop and book postures. Avoid spanning the preview across the hinge and prefer PreviewView scaling over rebinding use cases during fold events.

Camera tests often fail because virtual camera initialization is slow or asynchronous lifecycles are not awaited. Use fakes instead of Mockito, Google Truth assertions, explicit RunWith annotations, IdlingResource or CountDownLatch for binding, and GrantPermissionRule to bypass permission dialogs.