title: Catch a crash-n-reboot of an Android device
body: <p>I'm writing an application. It has a Service which is started using a receiver of <code>android.intent.action.BOOT_COMPLETED</code>.</p>
  
  <p>One of my app's users is reporting a strange problem (by the way, he is using LG Optimus One device with original 2.2 firmware) - after some interactions with my app (adding some data to a database which is used somehow by a Service) and after that resetting a device (hardware off and then on) device is going to infinite reboot just after 10 second after start.</p>
  
  <p>I think this crash-n-restart is related to my app or it's service ('cause there is not such crash after hard-reset and using a phone without my app).</p>
  
  <p>The question is.</p>
  
  <ol>
  <li>Is there any known bugs with LG Optimus One related to on-boot-starting a crashing service?</li>
  <li>How can i catch this bug? Is <code>adb logcat</code> is suitable here (is logcat is accessible right after the phone is powered on, when the BOOT_COMPLETED broadcast is sent?)</li>
  <li>I there any other debug techniques which i can use in my case?</li>
  </ol>