It seems like the browser you are using has JavaScript disabled. As a result, the site will not function properly. We really want you to enable it so you may experience our site as we intended it. If you have no idea what we are talking about or if you need help, visit http://www.enable-javascript.com×
This website uses cookies. By continuing to browse this site you are agreeing to our use of cookies. Find out more on our cookie page.×

Oops, it seems like you're using an old browser that we do not fully support. If you're able to, please upgrade your browser here.×
This website uses cookies. By continuing to browse this site you are agreeing to our use of cookies. Find out more on our cookie page.×

The function call failed because an invalid camera_handle_t value was used.

CAMERA_EACCESS

The function call failed because the necessary permissions to access the camera are
not available.

CAMERA_EBADR

The function call failed because an invalid file descriptor was used.

CAMERA_ENODATA

The function call failed because the requested data does not exist.

CAMERA_ENOENT

The function call failed because the specified file or directory does not exist.

CAMERA_ENOMEM

The function call failed because memory allocation failed.

CAMERA_EOPNOTSUPP

The function call failed because the requested operation is not supported.

CAMERA_ETIMEDOUT

The function call failed due to communication problem or time-out with the camera.

CAMERA_EALREADY

The function call failed because an operation on the camera is already in progress.

In addition, this error can indicate that a call could not be completed because it
was invalid or completed already. For example, if you called the camera_stop_video() function but
the camera had already stopped recording video, this error code would be returned.

CAMERA_EBUSY

The function call failed because the camera is busy.

Typically you receive this error when you try to open a camera while the camera or
its required resources are in use.

CAMERA_ENOSPC

The function call failed because the disk is full.

This typically happens when you are trying to start a video recording and less than
the system-reserved amount of disk space remains.

CAMERA_EUNINIT

The function call failed because the Camera library has not been initialized.

CAMERA_EREGFAULT

The function call failed because the registration of a callback failed.

CAMERA_EMICINUSE

The function call failed because the microphone is already in use.

CAMERA_EDESKTOPCAMERAINUSE

The function call failed because the operation cannot be completed while the camera
CAMERA_UNIT_DESKTOP is in use.

CAMERA_EPOWERDOWN

The function call failed because the camera is in the power down state.

Since: BlackBerry 10.2.0

CAMERA_3ALOCKED

The function call failed because a 3A lock is active.

Since: BlackBerry 10.3.0

CAMERA_EVIEWFINDERFROZEN

The function call failed because the viewfinder freeze flag was set on the device for
privacy reasons.

Since: BlackBerry 10.3.0

CAMERA_EOVERFLOW

The function call failed due to an internal overflow.

Since: BlackBerry 10.3.0

CAMERA_ETHERMALSHUTDOWN

The function call failed because the camera is in power down state to prevent damage
due to excessive heat.

Since: BlackBerry 10.3.0

Library:

libcamapi (For the qcc command, use the -l
camapi option to link against this library)

Description:

If you receive an error code which is not enumerated in
this list, consult the system-wide list of error codes in errno.h.

Last modified: 2014-06-24

Got questions about leaving a comment? Get answers from our Disqus FAQ.

1. Download the tools

Before you start developing, you'll need to visit the Downloads tab. Here you'll find downloads for the BlackBerry 10 Native SDK, BlackBerry 10 Device Simulator, and some other useful tools.

2. Try the sample apps

Now featuring a filter control, the Sample apps tab allows you to search for samples by name or by feature.

Select either the Core or Cascades radio buttons to display the samples relevant to you.

3. Educate yourself

The Documentation tab contains tons of examples, tutorials, and best practices to guide you along the path towards building an awesome app.

You can access all the documentation that you need in the left-hand navigation.

4. Start developing

The Reference tab is where you'll find essential details about how to use our APIs.

You can use the left-hand navigation to choose how you would like to browse the reference: by module, by topic, or alphabetically. If you have an idea of what you are looking for, start typing it in the Filter box.