Writing code that captures videos on Android

Although the Google guys did a good job on the Android documentation, the explanation on how to write code that captures videos is somewhat short.
In this tutorial, we are going to write an activity that is able to preview, start and stop video capturing, and give more explanation on it than the basic documentation does.
We are going to do this for Android 2.1, but after that, we will discuss differences with 2.2.
Finally, we will be illustrating how the undocumented 2.1 non-public api on MediaRecorder can be called through reflection.
This article is aimed at Android developers.

Setting the permissions

Since we are going to use the camera, the following line will definitely need to be declared in our AndroidManifest file:

<uses-permission android:name="android.permission.CAMERA" />

If we dont specify this, we will get a “Permission Denied” exception as soon as we try to access the camera from our code.

It is good practice to tell the app what features of the camera we are going to use too:

The main thing we are doing here is implementing a SurfaceHolder.Callback. This callback enables us to intervene when our surface is created, changed(format or size changes) or destroyed. Without this callback, our screen would just remain black.
After the surface is created, we obviously want to display what the camera is seeing. First, we are getting a reference to the camera by calling the static method Camera.open(). We only need to do this once, so we put this in the surfaceCreated method.
The actual start of the preview happens in the surfaceChanged method. This is because this method will not only be called right after surface creation(the first “change”), but also everytime something essential to the surface changes, and we want to stop previewing then, change some parameters and restart the preview. For example, we are using the passed width and height to set the preview size. By putting all of this in the surfaceChanged method, we are making sure our preview always remains consistent with our surface.
When the surface is destroyed(this happens for example at onPause or onDestroy of the activity), we are releasing the camera again, because otherwise other apps, like the native camera app, will start giving “Camera already in use” exceptions.

On a final note,

surfaceHolder.setType(SurfaceHolder.SURFACE_TYPE_PUSH_BUFFERS);

means the surface is not going to own its buffers, and this surface type is typically used for camera stuff.

Note: Instead of making the activity implement the surface callback, you could also make a class that extends SurfaceView, make that one implement the Callback and use that subclass in the layout xml instead of the SurfaceView. If your activity is getting very long in terms of code, this might be a good thing to do.

Capturing the video

We are now adding the following method to our activity, which will be called when the user decides to start recording:

In this method we are preparing the MediaRecorder with all the necessary details.

First, we unlock the camera so we can pass it in a usable state to another process, in this case the recording process. We are doing this in the third line of the code.

Then we are setting all the properties of the MediaRecorder.
Two things are important here.
The order in which the methods are called is the first one. For example, we need to set the sources before setting the encoders and we have to set encoders before calling prepare.
The second important and less documented one, is that ALL properties have to be set. Prepare is a very sensitive and obscure method. The implementation is a native function that just returns an error code in case something goes wrong. So, for example, if you forget to set “maxDuration” on the above mediaRecorder, you will get some obscure “prepare failed” error on most devices, which will not give you any hint at all you didnt set the maxDuration property. Many people assume that these properties are not required at all, and are getting these hard to debug errors.

After preparing the recorder, we start the actual recording.

Stop recording

Then we stop recording in the following method:

public void stopRecording(){
mediaRecorder.stop();
camera.lock();
}

which speaks for itself.

Note: To finish the activity, our methods still need to be linked to button actions. We are leaving this to the reader. The easiest way is probably to add stop and start buttons to the layout xml file with the surfaceview, whose onClick attribute points to some action on the activity that calls respectively the startRecording and stopRecording method.

Android 2.1 vs 2.2

At the time of this writing, most Android devices are still running on 2.1 and most developers are aiming their apps to be compatible with 2.1 and above. Which makes sense, if one looks at some Android platform distribution information.

The reference documentation is already updated for 2.2 though.

If we take a look again at the official instructions again,

we notice that we have gone through all the steps mentioned there. We clarified some steps, like “passing a fully initialized SurfaceHolder” and we also took care of the “see Media recorder information” part.

But some things we did different too. We are looking at the 2.2 instructions, and some methods are not yet available in 2.1.
In general, the camera API has been changing/improving at lightning speed. The downside to this is that old apis are getting deprecated very fast and that you cant just use the latest api, since you would seriously hurt your potential number of customers on the market.

Portrait orientation

In 2.2, the setDisplayOrientation method is there, but it isnt in 2.1. Actually, portrait mode for capturing videos through the api is only supported since 2.2, as clearly stated in the New Developer APIs paragraph of Android 2.2 highlights.
So, for our activity, it is necessary to specify

android:screenOrientation="landscape"

Otherwise, it is likely that the camera will have a 90 degrees discrepancy with what the user is seeing(which can be changed by setting the rotation parameter on the camera, but hacking into the code to make the camera work with portrait mode on 2.1 is outside the scope of this tutorial).

Reconnect

Another method that is not there yet in 2.1, so we are obviously not calling it.

PixelFormat.JPEG

This constant, which we are using in our activity above, is already deprecrated in 2.2. But since ImageFormat.JPEG, the suggested replacement, is not there yet in 2.1, we are forced to use the deprecated api.

Calling the undocumented setParameters method on MediaRecorder

In 2.2, there are setters for the properties videoBitrate, audioBitrate, audioChannels and audioSamplingRate on MediaRecorder.
In 2.1, these properties cant be set officially.

Unfortunately, although it is present on all 2.1 devices as far as I know, the setParameters method is not part of the public API, so 2.1 developers are left in the cold there.
Luckily, there is a workaround.

Through reflection, we are iterating over the available methods on the MediaRecorder. If we find the setParameters method, we invoke the found method for the same effect as in the camera app for the android 2.1 source code.

Hi DeltaFlux,
Can you help me with an ‘unexpected application stopped’ failure. I pretty much did how you described? My application just does not start, I am not sure how to go about debugging if my app does not even start.

Did you do anything different? I noticed that the Camera calls (lock, unlock) are reversed to how it is described in google doc, but then I could be wrong.

Hi u mention about onOptionsItemSelected and onCreateOptionsMenu this sounds familiar from another website.. So i decide to integrate it into the code above but it seems like there’s lot of error, can u tell me how should i integrate the above code in this web to onOptionsItemSelected and onCreateOptionsMenu to make my app work..

Hey, anyone know why i allways have “prepare failed” ? on emulator i can’t runn my app but device it’s work with bugs.. Video with green or purple lines/bloky (((( . And i run my app on 2 devices : on first app record video with bugs on second crashed on “startRecording button ”

Great tutorial! Could you give some advice on how to capture without preview and how to record video in the background? I’m wondering about a use-case where I enable preview manually (during application setup when I fix the device) and then on I start/stop recording using a widget (so I can interact with other apps). Thank you!

Is there something else i forgot to do in the .manifest file because i kept getting error when i run the file, if so what is the steps i should perform to solve it? And by the way the codes under Capturing the video, where should i code it, is it under the same activity??

Phone crash problem. I have tried this example and written my own and have the same problem. The problem
seems to be related to the MediaRecorder. When I open the Video Recorder app and make multiple recordings after 10 or more recordings the shutter button sound will stop. After this happens if you press the volume key the phone will crash. Does anyone have an idea about this? In LogCat there will be an AudioFlinger “cannot create track”

I am using a Samsung Galaxy S with Android 2.2 running. If this issue is similar to one you have had please respond, I can give more info if needed.

Note that I have also written an app that only does sound and I have no problems. ALSO, if I do not actually start recording, but do run MediaRecorder.prepare() there are no problems.

Hello,
is it possible record a video from within a background service without a preview?
I’m trying to do so, but it always leeds to bugs. If I don’t set a preview for camera and media recorder, I get a media server died , camera died, ICamera died and error 100. If I try to use a dummy view which is not shown for mVideoCamera.setPreviewDisplay(fakeView.mHolder) this leads to an exception which tells that a null was passed as surface! But I have created the fakeView . What can I do with Android 2.3.3? Please help.