Indeed this is an old known issue (1578) http://code.google.com/p/android/issues/detail?id=1578 and only restarting the phone helps. You can try to minimize occurrences by properly releasing the camera yourself when an exception occurs in your app.
On Jan 25, 10:41 pm, Joe McCann <joseph.is...@gmail.com> wrote: > So while developing a custom camera application I've realized on rare > occasions and on various devices if the app has to force close, it > does not always release the camera resource. > > Is there a way to find/detect the process that is holding onto this > resource and kill it? Or some other technique? It is rather > difficult bug to reproduce (for me anyway), but ultimately the device > has to be restarted. > > Thanks! -- 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
