We were quite surprised to get a user report that our app was getting a
force-close on startup in 2.3.3. After upgrading our Nexus One to 2.3.3 we
can finally confirm that something incredibly odd and blatant has happened
with the way the camera works.
Odd because there isn't a single change t
On Fri, Mar 18, 2011 at 6:37 PM, Zach wrote:
> I filed bug 15112 but believe that I was far too narrow in scope as I first
> thought the behavior was limited to what was called in onPreviewFrame. The
> actual problem appears to be global in scope.
What are your symptoms for the "global in scope"
>
> What are your symptoms for the "global in scope" part?
>
Global in scope meaning that no matter where we get/set camera parameters, a
subset of those parameters are now always null (on get) where before they
were not. The most noticeable parameter is the preview size.
Also related is we've
On Fri, Mar 18, 2011 at 7:14 PM, Zach wrote:
> Your sample code is incredibly similar to ours for the basic tasks of
> getting the optimal preview size and initializing/pausing the camera. The
> main functional difference is the use of autofocus & callback for
> processing.
If you haven't done s
>
> If you haven't done so already, try my apps on your Nexus One, and see
> what happens. I would do it myself, but my Nexus One's backlight is
> pushing up daisies...
>
I'll do some testing Monday morning and post my results.
--
You received this message because you are subscribed to the Googl
I've had some opportunity to test. Mark, I tested your code but it seems
this issue is tied to using autofocus and preview callbacks.
I've created a minimalistic sample that reproduces the problem. The
following code will run on all of my Android devices that are < 2.3.3 but
not on 2.3.3.
s
You will also need the manifest properties:
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubsc
If you haven't done so already, post this on http://b.android.com.
Also, have you compared your code to that of Barcode Scanner? That app
uses auto-focus and preview callbacks (AFAICT, as an end user, haven't
looked at their code) and does not crash on 2.3.3 the way you describe
here.
On Mon, Mar
I posted http://code.google.com/p/android/issues/detail?id=15112 a while
back. We originally based our app structure on the zxing libraries which I
believe Barcode Scanner is using. I have it on my to-do list to check that
source and see if it has changed how it deals with the camera in 2.3.3.
On Mon, Mar 21, 2011 at 8:09 PM, Zach wrote:
> We are going to
> manually update our Nexus S to 2.3.3 and see whether the behavior
> is consistent or device specific.
I'm surprised your Nexus S isn't already on 2.3.3. That update got
pushed out by T-Mo a few weeks ago, IIRC.
--
Mark Murphy (a C
>
> I'm surprised your Nexus S isn't already on 2.3.3. That update got
> pushed out by T-Mo a few weeks ago, IIRC.
>
Unfortunately, most of our development phones do not have data plans.
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To p
I can now confirm that this problem only exists on the Nexus One on 2.3.3.
I've updated our Nexus S to 2.3.3 and it does not have these problems.
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android
12 matches
Mail list logo
