Thanks to all the tips, particular Jason who managed to send me a stack trace which pin pointed the issue to the camera. I have a fix in place now and comments from Droid users on the market indicate that is it working for them.
Thanks everyone, Mike On Jan 9, 7:54 am, Sena Gbeckor-Kove <[email protected]> wrote: > If you implement Flurry analytics you can see remote Exceptions by device and > location. > > S > > --- > > Sena Gbeckor-Kove > CTO/Founder - imKon > > UK : +44 7788 146652 > NL : +31 62 434 1290 > [email protected] | www.imkon.com > > Asia (Singapore) : > 35 Selegie Road, #09-14/15 Parklane Shopping Mall, 188307 Singapore, Singapore > > Europe (London) : > 145-157 St John's St, EC1V 4PY London, UK > > On 8 Jan 2010, at 22:38, Jason Proctor wrote: > > > there's a Droid user sitting right here, i will try to get him to install > > the app and log the crash to my ddms. then i'll send it on. > > > At 1:34 PM -0800 1/8/10, Matt Kanninen wrote: > >> Do you specify a target SDK in your manifest? Do you use any Droid > >> specific layouts? > > >> What firmwares do you support? > > >> You can throw giant try catches around problematic code, log the > >> exception to local file, and upload them to your servers. Although > >> you might want to warn users you do this in your terms of service, > >> especially if you aren't really a networked app. > > >> On Jan 8, 12:07 pm, MJB <[email protected]> wrote: > >>> Hi Dianne, > > >>> That's the difficulty, only end-users see the crash so I can't see the > >>> stack trace. If I had my own Droid to try it on, it should be > >>> relatively easy to work through the bug. Unfortunately, I don't have > >>> a Droid and even if I wanted one, they are not available in my > >>> country. > > >> > The app I'm referring to specifically is Andrometer (2nd place in ADC2 > >>> misc. category). > > >>> Thanks, > >>> Mike > > >>> On Jan 7, 4:37 pm, Dianne Hackborn <[email protected]> wrote: > > >>> > What is the stack crawl of the crash? > > >>> > On Thu, Jan 7, 2010 at 1:12 PM, MJB <[email protected]> wrote: > >>> > > Hi All, > >>> > > I'm having a problem where my app crashes on the Droid and seems to > >>> > > work fine on the G1. We have a G1 dev phone but do not have access to > >>> > > a Droid phone, so the issue is difficult to debug at this stage. > > >>> > > The app loads up the main screen okay, but once the user moves beyond > >>> > > the main screen, the app crashes. Moving beyond main screen initiates > >>> > > the following: > > >>> > > - GPS signal acquired > >>> > > - Accelerometer sensor listener active > >>> > > - Geomagnetic sensor listener active > >>> > > - Camera preview active > > >>> > > I have a suspicion that the issue may be related to the camera > >>> > > preview. With the G1, it didn't seem to matter how I set the camera > >>> > > preview size, so I just made it fit the size of the view. > > >>> > > Camera.Parameters parameters = mCamera.getParameters(); > >>> > > parameters.setPreviewSize(w, h); //where w, h are the width and > >>> > > height. > > >>> > > One possibility is that with the Droid having a larger screen > >>> > > resolution to the G1, it may be setting the preview size to something > >>> > > that is not supported. I plan on addressing this, but I have a few > >>> > > questions that I was hoping someone could shed some light on. > > >>> > > 1. If the app attempts to set a preview size that is not supported, > >>> > > will it just be ignored or will the app crash? > >>> > > 2. If the preview size is smaller than the surface that is holding the > >>> > > preview, will the image be stretched to fill the surface? > >>> > > 3. Can anyone think of anything else that may be related specifically > >>> > > to the Droid that could be causing me problems? > > >>> > > Thanks, > >>> > > Mike > > >>> > > -- > >>> > > 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]<android-developers%[email protected]> > >>> > > For more options, visit this group at > >>> > >http://groups.google.com/group/android-developers?hl=en > > >>> > -- > >>> > Dianne Hackborn > >>> > Android framework engineer > >>> > [email protected] > > >>> > Note: please don't send private questions to me, as I don't have time to > >>> > provide private support, and so won't reply to such e-mails. All such > >>> > questions should be posted on public forums, where I and others can see > >>> > and > >>> > answer them.- Hide quoted text - > > >>> > - Show quoted text - > > >> -- > >> 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 > > > -- > > jason.vp.engineering.particle > > -- > > 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 > > > > smime.p7s > 3KViewDownload
-- 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
