>From my experience, the DroidX doesn't call onMemory, it just starts destroying and restarting apps when the device gets low. There is no FC when it does this. I'd start there with checking your usage. Of course, that shouldn't cause the entire device to reboot, but DroidX doesn't handle resources like other devices.
Shane On Fri, Feb 4, 2011 at 1:12 PM, mot12 <[email protected]> wrote: > Hello group, > > My app seem to cause reboots on DroidX phones. No force close or > unusual behavior before the reboot is reported. Closing the last > activity seems to cause the reboot. Unfortunately, there's no log as > the log data gets cleared with the reboot. I have supplied a special > version to one DroidX user that writes all log data into a file; this > allowed me to see that the app seemingly ended correctly with the last > activity's OnDestroy being called. > > Does anybody experience similar issues? > > I will now give this user a stripped down version to see if the > problem still exists, then add code piece by piece until the problem > reappears or the user gets fed up, whichever comes first. > > Any suggestion as to why a phone may reboot are highly welcome. > > Martin > mobitobi > > -- > 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]<android-developers%[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
