incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chip Matthes (Commented) (JIRA)" <>
Subject [jira] [Commented] (CB-193) Android camera bug, caused by out of memory error?
Date Mon, 30 Jan 2012 20:09:10 GMT


Chip Matthes commented on CB-193:

Two more reports of this issue:

> Android camera bug, caused by out of memory error?
> --------------------------------------------------
>                 Key: CB-193
>                 URL:
>             Project: Apache Callback
>          Issue Type: Bug
>    Affects Versions: 1.3.0
>         Environment: Android
>            Reporter: Steve Gill
>              Labels: android
> We have a guy on our support forms who has been running into issues with the android
camera. I am going to paste some of his findings below. 
> We've done a bunch of testing, and it looks like the problem is not specifically with
the Droid X, but rather with how PhoneGap handles memory management for the Camera API.
> If lots of other apps are running, then the app restarts after the camera API is called,
a picture taken, and "saved". If only a few apps are running (i.e. there is more free memory),
then the camera API works as designed and the user is returned to the app after taking and
saving the picture.
> The Android Camera issues are becoming a show-stopper for us. We've tried installing
the latest nightly builds that supposedly fix the problems, but Phonegap still crashes on
a Droid when taking a picture.
> This problem is not at all isolated to us. For now, it seems that Phonegap is unusable
as an app platform for Android if the camera is involved.
> Are there any plans to escalate this issue so Android Apps using the camera can be deployed?
> Here's how widespread this issue is:
> Seems like he is having the issue mainly with Droid X (Android 2.3)
> I will send him this link and get him to come give more details on the issue.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message