Android app crashing after incoming call

Question

I've had a bug report that when a user is playing my game and an incoming call is received, after the call is finished with my app is crashing.

The problem is I've tried to recreate the error - I've been sitting here all morning running it and phoning in - and it always resumes without any problems. I can't see any error reports relating to this problem either. I've been quite exhaustive too, calling it during various stages (ie. entering highscores, on the splash screen, during gameplay) and never any problems.

It's weird because I have had this bug reported before a while ago, and then the user said it was okay now. So I guess it must be intermittent.

I'm guessing the problem is somewhere in my onCreate() method. I thought this was the entry point when resuming an app.

Does anyone have an idea how to debug this "blind" without a crash report?

hey what is the solution? please post answer your self if u found .. — Shabbir Dhangot, Mar 04 '14 at 10:39

score 2 · Answer 1 · answered Feb 08 '11 at 14:42

2

You are probably looking for onStart rather than onCreate. Take a look at the Activity life cycle diagram in the Android Developer Reference for Activity

answered Feb 08 '11 at 14:42

Lucas B

11,793
5
37
50

score 0 · Answer 2 · answered Feb 08 '11 at 15:09

0

What do your configChanges look like in the manifest?

Make sure you handle onConfigurationChanged correctly.

Orientation changes are the cause of many similar problems.

answered Feb 08 '11 at 15:09

DKIT

3,471
2
20
24

I don't allow orientation changes, its fixed to landscape. – Kevin Feb 10 '11 at 23:15

score 0 · Answer 3 · edited May 23 '17 at 11:47

I think I fixed this. The problem was that I was creating a new draw thread in the surfaceCreated method, without stopping the previous thread. Not good and eventually causing a exception due to out of memory. When I used the DDMS to look at the threads I could see multiple draw threads building up. In the game I could see everything slowing down each time the app is sent into the background.

This answer helped a lot with the solution programming with thread strategy

That method advocates killing the thread when sending the app into the background. In the end, though, I decided to cause the thread to pause when the app sleeps, because it seemed a more logical approach. Nothing complex other than a wait loop inside the thread.

        while (run) {
            while ( paused ) {
                try {
                    Thread.sleep(200);
                } catch (InterruptedException e) { }
            }

I just set paused to true on the onStop() method.

Android app crashing after incoming call

3 Answers3