Is it advisable to add a Thread.sleep(1000L) after camera.release() to make life easier on the camera service to prevent the unbound camera lock situation? Of course that is not a fix, but I'll go with whatever gives me good stability with Cupcake.
On May 1, 11:09 pm, blindfold <seeingwithso...@gmail.com> wrote: > No I do not use the camera unlock() method anywhere. In fact I did not > even know this method existed. Seems undefined for the type Camera. > Did you perhaps mean camera.release()? I do use that, to be polite > against other camera apps when going in paused state, and when > quitting. Any recommendations on what I could do? > > Thanks! > > On May 1, 10:52 pm, Dave Sparks <davidspa...@android.com> wrote: > > > Are you using the camera unlock() method? There is a known issue where > > if the application calls unlock() and then exits for any reason, it > > can leave the camera service in a state where it will reject any > > subsequent attempts to reconnect. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
