The best bet for developers who cannot afford to buy all popular/ latest phones is to upload the stacktrace from the user's phone when a crash occurs. See http://stackoverflow.com/questions/601503/how-do-i-obtain-crash-data-from-my-android-application for a lead.
I develop on ADP1 and had many crash reports from Droid users until I used this approach to obtain crash reports. Regards On Jan 8, 9:07 pm, MJB <mbrennan8...@gmail.com> 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 <hack...@android.com> wrote: > > > What is the stack crawl of the crash? > > > On Thu, Jan 7, 2010 at 1:12 PM, MJB <mbrennan8...@gmail.com> 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 android-developers@googlegroups.com > > > To unsubscribe from this group, send email to > > > android-developers+unsubscr...@googlegroups.com<android-developers%2bunsubscr...@googlegroups.com> > > > For more options, visit this group at > > >http://groups.google.com/group/android-developers?hl=en > > > -- > > Dianne Hackborn > > Android framework engineer > > hack...@android.com > > > 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 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
