When CameraSource do connect(),lock(),camerasource(MediaServerPID) holds the CameraClient.
After unlock(), it will lose the hold ofCameraClient.
ThenRecordingProxywill do connect() and start/stop recording, App Process begins to hold theCameraClient, it won’t lose the hold during recording.
In App, if startVideoRecording() is called afterstop_preview(),calling sequence is out of order. App’s self thread destroyed the camera device byCameraClient::disconnect(), so when recording thread do start recording, it will fail with –ENODEV.