Bug 10159 - android:screenOrientation ignored in styles.xml file
Summary: android:screenOrientation ignored in styles.xml file
Alias: None
Product: Android
Classification: Xamarin
Component: Mono runtime / AOT Compiler ()
Version: 4.6.x
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2013-02-08 07:45 UTC by Paul Johnson
Modified: 2017-06-28 21:22 UTC (History)
3 users (show)

Tags: bb clb
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Paul Johnson 2013-02-08 07:45:27 UTC
The following XML should lock the screen to portrait

  <style name="Theme.Normal" parent="android:Theme">
    <item name="android:windowBackground">@drawable/background</item>
    <item name="android:windowNoTitle">true</item>
    <item name="android:screenOrientation">portrait</item>

If use this theme in an app and turn the device to landscape, the app turns to landscape.

However, ScreenOrientation = Android.Content.PM.ScreenOrientation.Portrait will lock to portrait
Comment 1 Cody Beyer (MSFT) 2017-06-28 21:22:11 UTC
The same behavior occurs when using Java and Android Studio. I am closing this bug as invalid, as it is not specific to Xamarin.Android