tags:

views:

97

answers:

4

I'm trying to guess why a user would report "Force quits every time I load"

The problem does not occur for all users, especially not me.

The system constructs a database when it first loads. I suspect that user's phone does not have enough memory.

Questions: How can I verify that the system has enough memory to store a small database? What else might cause a user's particular system to force quit on startup?

Wrong answers or things I've tried thus far:

  • The user's hardware is probably different than mine
  • The user's software and available memory is likely different as well
  • The data is already loading in its own thread, with a progress dialog showing
A: 

Sounds quite odd, does a freshly booted phone give the same error? Also ask the user to check available storage, might be out if space.

Fredrik Leijon
A: 

The most important question is: "Is the user's phone different from your test phone (hardware, API version? " Regards, Ari

BeMeCollective
A: 

If the UI thread gets frozen for a period of time, then it will show that dialog. Try running the task in the background using an AsyncTask.

Edit: I'm assuming it's this error message.

FryGuy
Good time. However, the data is already loading in another thread
gregm
+1  A: 

Add some smarts to your app to send you stack traces when the app crashes in the field. That'll narrow down the specific problem and can help you tailor your efforts to clear it up.

CommonsWare
I started a new question to discuss various techniques for this: http://stackoverflow.com/questions/1809586/how-do-i-show-a-dialog-after-the-thread-has-encountered-an-uncaught-exception
gregm