Possibly found the culprit. In several activities, I call this:
setContentView(R.layout.main);
switch (Preferences.getPrefOrientation(this, Screen.MAIN))
{
case 0:
if
("1".equals(Settings.System.getString(getContentResolver(),
Settings.System.ACCELEROMETER_ROTATION)))
setRequestedOrientation(ActivityInfo.SCREEN_ORIENTATION_SENSOR);
break;
case 1:
setRequestedOrientation(ActivityInfo.SCREEN_ORIENTATION_PORTRAIT);
break;
case 2:
setRequestedOrientation(ActivityInfo.SCREEN_ORIENTATION_LANDSCAPE);
break;
Basically this fixes the screen orientation to portrait or landscape,
or tells Android to use the rotation sensor again to determine the
screen orientation. This code works fine except on the DroidX. Even on
the DroidX fixed orientation works fine (protrait only, landscape
only) but if I set the orientation to be tied to the sensor, resuming
such an activity and then changing the sensor orientation causes the
reboot. My app works fine if I take this single line of code out.
Of course, this is completely unsatisfying. The line itself doesn't
cause an immediate blowup but it seems to be the cause for blowups
later. Maybe this is a firmware bug. Maybe it is something entirely
different and all this is just circumstantial. I don't have the
resources to spend more time on this issue now but if anybody has an
idea on how to make sense of this, I would love to learn.
--
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
