Does anyone know of (reproducible) reasons for device reboot? My app-under-development will run for hours if the device is not charging, but with USB connected it will reboot, usually within minutes. No exceptions shown, just a reboot.
The app has one activity, which (via a WakefulIntentService [from CommonsWare]) sets up alarms that will trigger at different intervals (4mins to half a day). The alarms are cancelled when the activity is destroyed. When an alarm goes off, a BroadcastReceiver starts a WakefulIntentService, which pulls some data from a server and saves it in a file. That service starts another service, which provides a cache of the data in the file to the activity. The start of the cache service is afaik the simplest way of providing a simple notification. It is most likely already running, as it is bound by the activity. This could most likely be done smarter, but it seemed like a fair compromise when I want the app to work offline, too. Does anyone know of an interaction between USB/charging and wakelocks / alarms / services ? Logcat does not provide much help. Seems that the log is cleared at reboot. Any hints for debugging this apart from logcat (will adb bugreport provide more history than logcat?) Just for the record, I have seen the device (HTC Desire running 2.2) reboot when it gets hot (hot environment, lots of voice/data traffic while or just after charging), but it's running pretty cool in this scenario. -- 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
