On Mon, May 9, 2011 at 4:45 PM, Droid <[email protected]> wrote: > Probably an image is too big (too many?) (over 1800 pixels triggers > MOM in some cheaper phones) and/or the change of screen orientation > tends to trigger MOM errors for large images. > I had to switch it off with; android:screenOrientation="nosensor" >
Note that using android:screenOrientation does not ever fix something. If you are using it to fix something, you are just making your problem less likely to happen. For example in your case here, if the phone has a lid that flips to show a keyboard, you will still get restarted due to a different config change from the keyboard being shown/hidden. As you keep trying to say you shouldn't be restarted due to config changes, you will find other cases where you still are, until you reach ones where you really do need to be restarted. The android:screenOrientation is only for optimization. For all other issues, you need to fix the underlying problem in the app. -- Dianne Hackborn Android framework engineer [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
