Hi Diane,

The issue I'm talking about was already logged as issue 5009 <http://code.google.com/p/android/issues/detail?id=5009>. Logcat does indeed show a useful stacktrace, however I had a very hard time cross-referencing the stack trace line numbers with the actual source code. The phone I was testing on was running an eclair build at the time, so I checked all the eclair revisions but no matter which revision I looked at, the numbers never seemed to match up. Is there any way to easily determine which revision of the source code is being used by a build on a specific device?

Pepijn

On 07/02/2011 18:57, Dianne Hackborn wrote:
Please file bug reports for any such crashes.

Note the output of logcat is extremely useful -- in most cases, if the system crashes, it is due to a Java crash, which will be printed to the log prior to it rebooting. This may help you understand what is going on; it is *extremely* helpful in a bug you file since the engineer can very likely tell what the problem is and how to fix it from the log.

On Mon, Feb 7, 2011 at 9:15 AM, Pepijn Van Eeckhoudt <[email protected] <mailto:[email protected]>> wrote:

     On 04/02/2011 22:12, mot12 wrote:

        Any suggestion as to why a phone may reboot are highly welcome.

    I've only been able to make phones reboot by triggering a
    crash/exception in a system process. This is standard Android
    behavior as far as I can tell.

    This happened to me when I was implementing a SyncAdapter. I had
    implemented the account part, but not yet the sync adapter.
    Creating an account would cause a NPE in the sync process which
    instantly rebooted the phone. This was a real PITA to debug as the
    phone would reset itself before I even had a chance to capture any
    debug information.

    Best of luck hunting down this one.

    Regards,

    Pepijn


-- 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]
    <mailto:[email protected]>
    To unsubscribe from this group, send email to
    [email protected]
    <mailto: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] <mailto:[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.

--
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

--
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

Reply via email to