On May 1, 9:57 pm, blindfold <seeingwithso...@gmail.com> wrote:
OK, moving from Proguard 4.1 to 4.3 seems to bring much improved
stability as far my current testing goes, although I still managed to
get the dreaded camera lock once after a stressful transition
(quitting my app while it was resetting its state). Apparently Cupcake
does not have some independent daemon running that checks if the
camera is still locked when no camera app is running, in order to
remove the floating lock? That might offer a solution to the G1 camera
(or its firmware) not being quite stress proof.
Regards
> I must then reboot the phone to get the camera back. I'm currently
> investigating if my use of Proguard perhaps has anything to do with
> it, because things seem stable until I prepare a release APK.
>
> Regards
>
> On May 1, 5:00 pm, Dave Sparks <davidspa...@android.com> wrote:
>
> > Can you repro this with the camera application?
>
> > On May 1, 6:22 am, blindfold <seeingwithso...@gmail.com> wrote:
>
> > > I found that the old bug reported
> > > inhttp://code.google.com/p/android/issues/detail?id=1578
> > > where only a power cycle brings back the camera still persists with
> > > the official Cupcake firmware on my ADP. When it happens - and I've
> > > encountered it several times in a few days now - no camera application
> > > can access the camera. A power cycle is needed to recover from this
> > > locked camera state.
>
> > > Regards
>
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
