Hi Mark, I am not familiar with the semantics of some of the constructions that you use, but your use of AsyncTask() makes me wonder if you have safeguarded (e.g. copied) the image data[] by the time that onPictureTaken() returns, because image data[] has no guaranteed lifetime beyond that.
I would also not have put the camera.startPreview() preview restart inside the onPictureTaken() callback, because typically one is not allowed to put system-related function calls inside callbacks. Regards On Nov 28, 2:18 am, Mark Murphy <[email protected]> wrote: > blindfold wrote: > > Did you try any other picture taking apps from the Market for > > comparison? > > No, because I wasn't sure how I'd tell Camera#takePicture() from > launching the camera Intent. > > > I cannot tell because I have no Droid to test with, but my app does a > > takePicture() when key 'p' is pressed, so it is among the apps that > > you could try. > > Well, taking a picture didn't blow up. It must be there's some parameter > I need to set for the DROID that causes the SIGSEGV if I don't set it. > I'll have to poke around. > > Thanks! > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://twitter.com/commonsguy > > _Android Programming Tutorials_ Version 1.0 Available! -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
