blocks|key|463896|text|您描述的是默认行为。必须自己检测和处理这些事件，方法是添加：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|463897|android:configChanges|code-block|syntax|javascript|463898|你的清单，然后你要处理的更改。因此，对于定向，您可以使用：|463899|android:configChanges="orientation"|463900|对于正在打开或关闭的键盘，您将使用：|463901|android:configChanges="keyboardHidden"|463902|如果您想同时处理这两种情况，只需使用管道命令将它们分开，如下所示：|463903|android:configChanges="keyboardHidden%7Corientation"|463904|这将在您调用的任何活动中触发onConfigurationChanged方法。如果重写方法，则可以传递新值。|463905|希望这能有所帮助。|463906|entityMap^0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|10|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|12|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|13|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|14|8|@]|9|@]|A|$]]|$1|Q|3|R|5|D|7|15|8|@]|9|@]|A|$E|F]]|$1|S|3|T|5|6|7|16|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|17|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|X|$]]

What you describe is the default behavior. You have to detect and handle these events yourself by adding:

<pre><code>android:configChanges
</code></pre>

to your manifest and then the changes that you want to handle. So for orientation, you would use:

<pre><code>android:configChanges="orientation"
</code></pre>

and for the keyboard being opened or closed you would use:

<pre><code>android:configChanges="keyboardHidden"
</code></pre>

If you want to handle both you can just separate them with the pipe command like:

<pre><code>android:configChanges="keyboardHidden|orientation"
</code></pre>

This will trigger the onConfigurationChanged method in whatever Activity you call. If you override the method you can pass in the new values.

Hope this helps.

blocks|key|1998092|text|使用应用程序类|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1998093|根据您在初始化过程中所做的事情，您可以考虑创建一个扩展Application的新类，并将您的初始化代码移动到该类中重写的onCreate方法中。|offset|length|style|CODE|1998094|public+class+MyApplicationClass+extends+Application+{
++@Override
++public+void+onCreate()+{
++++super.onCreate();
++++//+TODO+Put+your+application+initialization+code+here.
++}
}|code-block|syntax|javascript|1998095|只有在创建了整个应用程序时，应用程序类中的onCreate才会被调用，因此在方向或键盘可见性更改上重新启动的活动不会触发它。|1998096|很好的做法是将该类的实例公开为单例，并公开使用getters和setter初始化的应用程序变量。|1998097|注意:您需要在清单中指定新应用程序类的名称，以便注册和使用：|1998098|<application
++++android:name="com.you.yourapp.MyApplicationClass"|1998099|响应配置更改的()+[UPDATE:这是从API+13；http://www.androiddesignpatterns.com/2013/04/retaining-objects-across-config-changes.html中删除的]|BOLD|1998100|作为另一种选择，您可以让应用程序侦听可能导致重新启动的事件--比如方向和键盘可见性更改--并在您的活动中处理它们。|1998101|从将android:configChanges节点添加到活动的清单节点开始|1998102|+<activity+android:name=".MyActivity"
++++++android:configChanges="orientation%7CkeyboardHidden"
++++++android:label="@string/app_name">|1998103|或者是Android+3.2+(API级别13)和更新版本|1998104|<activity+android:name=".MyActivity"
++++++android:configChanges="keyboardHidden%7Corientation%7CscreenSize"
++++++android:label="@string/app_name">|1998105|然后，在活动中重写onConfigurationChanged方法，并调用setContentView强制在新的方向上重新执行GUI布局。|1998106|@Override
public+void+onConfigurationChanged(Configuration+newConfig)+{
++super.onConfigurationChanged(newConfig);
++setContentView(R.layout.myLayout);
}|1998107|entityMap|0|LINK|mutability|MUTABLE|url|http://www.androiddesignpatterns.com/2013/04/retaining-objects-across-config-changes.html|1|https://stackoverflow.com/a/9550231/2291^0|0|R|B|1O|8|0|0|L|8|0|0|0|0|7|1|S|2H|0|0|0|2|L|0|0|3|Q|1|0|0|9|M|11|E|0|0^^$0|@$1|2|3|4|5|6|7|1L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1M|8|@$D|1N|E|1O|F|G]|$D|1P|E|1Q|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|1R|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|1S|8|@$D|1T|E|1U|F|G]]|9|@]|A|$]]|$1|O|3|P|5|6|7|1V|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1W|8|@]|9|@]|A|$]]|$1|S|3|T|5|J|7|1X|8|@]|9|@]|A|$K|L]]|$1|U|3|V|5|6|7|1Y|8|@$D|1Z|E|20|F|W]]|9|@$D|21|E|22|1|23]]|A|$]]|$1|X|3|Y|5|6|7|24|8|@]|9|@]|A|$]]|$1|Z|3|10|5|6|7|25|8|@$D|26|E|27|F|G]]|9|@]|A|$]]|$1|11|3|12|5|J|7|28|8|@]|9|@]|A|$K|L]]|$1|13|3|14|5|6|7|29|8|@]|9|@$D|2A|E|2B|1|2C]]|A|$]]|$1|15|3|16|5|J|7|2D|8|@]|9|@]|A|$K|L]]|$1|17|3|18|5|6|7|2E|8|@$D|2F|E|2G|F|G]|$D|2H|E|2I|F|G]]|9|@]|A|$]]|$1|19|3|1A|5|J|7|2J|8|@]|9|@]|A|$K|L]]|$1|1B|3|-4|5|6|7|2K|8|@]|9|@]|A|$]]]|1C|$1D|$5|1E|1F|1G|A|$1H|1I]]|1J|$5|1E|1F|1G|A|$1H|1K]]]]

Using the Application Class

Depending on what you're doing in your initialization you could consider creating a new class that extends <code>Application</code> and moving your initialization code into an overridden <code>onCreate</code> method within that class.

<pre><code>public class MyApplicationClass extends Application {
 @Override
 public void onCreate() {
 super.onCreate();
 // TODO Put your application initialization code here.
 }
}
</code></pre>

The <code>onCreate</code> in the application class is only called when the entire application is created, so the Activity restarts on orientation or keyboard visibility changes won't trigger it.

It's good practice to expose the instance of this class as a singleton and exposing the application variables you're initializing using getters and setters.

NOTE: You'll need to specify the name of your new Application class in the manifest for it to be registered and used:

<pre><code>&lt;application
 android:name="com.you.yourapp.MyApplicationClass"
</code></pre>

Reacting to Configuration Changes [UPDATE: this is deprecated since API 13; <a href="http://www.androiddesignpatterns.com/2013/04/retaining-objects-across-config-changes.html" rel="noreferrer">see the recommended alternative</a>]

As a further alternative, you can have your application listen for events that would cause a restart – like orientation and keyboard visibility changes – and handle them within your Activity.

Start by adding the <code>android:configChanges</code> node to your Activity's manifest node

<pre><code> &lt;activity android:name=".MyActivity"
 android:configChanges="orientation|keyboardHidden"
 android:label="@string/app_name"&gt;
</code></pre>

or for <a href="https://stackoverflow.com/a/9550231/2291">Android 3.2 (API level 13) and newer</a>:

<pre><code>&lt;activity android:name=".MyActivity"
 android:configChanges="keyboardHidden|orientation|screenSize"
 android:label="@string/app_name"&gt;
</code></pre>

Then within the Activity override the <code>onConfigurationChanged</code> method and call <code>setContentView</code> to force the GUI layout to be re-done in the new orientation.

<pre><code>@Override
public void onConfigurationChanged(Configuration newConfig) {
 super.onConfigurationChanged(newConfig);
 setContentView(R.layout.myLayout);
}
</code></pre>

blocks|key|765323|text|即使您更改了android的onCreate，仍然会调用orientation方法。因此，将所有繁重的功能转移到此方法将不会对您有所帮助。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|765324|entityMap^0|E|8|S|B|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

The <code>onCreate</code> method is still called even when you change the <code>orientation</code> of android. So moving all the heavy functionality to this method is not going to help you

blocks|key|464006|text|我刚发现这个传说：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|464007|要通过更改方向来保持活动的活力，并通过onConfigurationChanged、文献资料和上面的代码示例处理它，请在Manifest文件中提出如下建议：|offset|length|style|CODE|464008|<activity+android:name=".MyActivity"
++++++android:configChanges="orientation%7CkeyboardHidden"
++++++android:label="@string/app_name">|code-block|syntax|javascript|464009|它有一个额外的好处，那就是它总是有效的。|464010|额外的好处是，省略keyboardHidden似乎是合乎逻辑的，但它会导致模拟器(至少是Android2.1)出现故障:只指定orientation有时会使模拟器同时调用OnCreate和onConfigurationChanged，而其他时候只会调用OnCreate。|464011|我还没有在设备上看到故障，但我听说过其他设备的仿真器失败。所以值得记录。|464012|entityMap|0|LINK|mutability|MUTABLE|url|http://developer.android.com/guide/topics/resources/runtime-changes.html#HandlingTheChange|1|https://stackoverflow.com/questions/456211/activity-restart-on-rotation-android/456918#456918^0|0|J|M|16|4|0|1B|7|1|0|0|0|9|E|1R|B|2D|8|2M|M|3I|8|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@$D|14|E|15|F|G]]|9|@$D|16|E|17|1|18]|$D|19|E|1A|1|1B]]|A|$]]|$1|H|3|I|5|J|7|1C|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|1D|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1E|8|@$D|1F|E|1G|F|G]|$D|1H|E|1I|F|G]|$D|1J|E|1K|F|G]|$D|1L|E|1M|F|G]|$D|1N|E|1O|F|G]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1P|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z]]|10|$5|V|W|X|A|$Y|11]]]]

I just discovered this lore:

For keeping the Activity alive through an orientation change, and handling it through <code>onConfigurationChanged</code>, <a href="http://developer.android.com/guide/topics/resources/runtime-changes.html#HandlingTheChange" rel="noreferrer">the documentation</a> and <a href="https://stackoverflow.com/questions/456211/activity-restart-on-rotation-android/456918#456918">the code sample above</a> suggest this in the Manifest file:

<pre><code>&lt;activity android:name=".MyActivity"
 android:configChanges="orientation|keyboardHidden"
 android:label="@string/app_name"&gt;
</code></pre>

which has the extra benefit that it always works.

The bonus lore is that omitting the <code>keyboardHidden</code> may seem logical, but it causes failures in the emulator (for Android 2.1 at least): specifying only <code>orientation</code> will make the emulator call both <code>OnCreate</code> and <code>onConfigurationChanged</code> sometimes, and only <code>OnCreate</code> other times.

I haven't seen the failure on a device, but I have heard about the emulator failing for others. So it's worth documenting.

blocks|key|1998165|text|我所做的..。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1998166|在清单中，在活动部分中添加：|1998167|android:configChanges="keyboardHidden%7Corientation"|code-block|syntax|javascript|1998168|在活动代码中，实现了：|1998169|//used+in+onCreate()+and+onConfigurationChanged()+to+set+up+the+UI+elements
public+void+InitializeUI()
{
++++//get+views+from+ID's
++++this.textViewHeaderMainMessage+=+(TextView)+this.findViewById(R.id.TextViewHeaderMainMessage);

++++//etc...+hook+up+click+listeners,+whatever+you+need+from+the+Views
}

//Called+when+the+activity+is+first+created.
@Override
public+void+onCreate(Bundle+savedInstanceState)
{
++++super.onCreate(savedInstanceState);
++++setContentView(R.layout.main);

++++InitializeUI();
}

//this+is+called+when+the+screen+rotates.
//+(onCreate+is+no+longer+called+when+screen+rotates+due+to+manifest,+see:+android:configChanges)
@Override
public+void+onConfigurationChanged(Configuration+newConfig)
{
++++super.onConfigurationChanged(newConfig);
++++setContentView(R.layout.main);

++++InitializeUI();
}|1998170|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

what I did...

in the manifest, to the activity section, added:

<pre><code>android:configChanges="keyboardHidden|orientation"
</code></pre>

in the code for the activity, implemented:

<pre><code>//used in onCreate() and onConfigurationChanged() to set up the UI elements
public void InitializeUI()
{
 //get views from ID's
 this.textViewHeaderMainMessage = (TextView) this.findViewById(R.id.TextViewHeaderMainMessage);

 //etc... hook up click listeners, whatever you need from the Views
}

//Called when the activity is first created.
@Override
public void onCreate(Bundle savedInstanceState)
{
 super.onCreate(savedInstanceState);
 setContentView(R.layout.main);

 InitializeUI();
}

//this is called when the screen rotates.
// (onCreate is no longer called when screen rotates due to manifest, see: android:configChanges)
@Override
public void onConfigurationChanged(Configuration newConfig)
{
 super.onConfigurationChanged(newConfig);
 setContentView(R.layout.main);

 InitializeUI();
}
</code></pre>

blocks|key|464056|text|您还可以考虑使用Android的方式在方向变化中持久化数据：onRetainNonConfigurationInstance()和getLastNonConfigurationInstance()。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|464057|这允许您在配置更改中持久化数据，例如您可能从服务器获取的信息或在onCreate中或此后计算的其他信息，同时还允许Android使用xml文件重新布局您的Activity，以适应现在正在使用的方向。|464058|见这里或这里。|464059|应该注意的是，这些方法现在被废弃了(尽管比处理方向更灵活，正如上面大多数解决方案所建议的那样，改变自己)，建议每个人都切换到Fragments，而不是在您想要保留的每个Fragment上使用setRetainInstance(true)。|464060|entityMap|0|LINK|mutability|MUTABLE|url|http://android-developers.blogspot.com/2009/02/faster-screen-orientation-change.html|1|http://developer.android.com/guide/topics/resources/runtime-changes.html^0|U|Y|1T|X|0|W|8|25|8|0|1|2|0|4|2|1|0|1Q|9|2C|8|2N|N|0^^$0|@$1|2|3|4|5|6|7|V|8|@$9|W|A|X|B|C]|$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|10|8|@$9|11|A|12|B|C]|$9|13|A|14|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|15|8|@]|D|@$9|16|A|17|1|18]|$9|19|A|1A|1|1B]]|E|$]]|$1|J|3|K|5|6|7|1C|8|@$9|1D|A|1E|B|C]|$9|1F|A|1G|B|C]|$9|1H|A|1I|B|C]]|D|@]|E|$]]|$1|L|3|-4|5|6|7|1J|8|@]|D|@]|E|$]]]|M|$N|$5|O|P|Q|E|$R|S]]|T|$5|O|P|Q|E|$R|U]]]]

You might also consider using the Android platform's way of persisting data across orientation changes: <code>onRetainNonConfigurationInstance()</code> and <code>getLastNonConfigurationInstance()</code>.

This allows you to persist data across configuration changes, such as information you may have gotten from a server fetch or something else that's been computed in <code>onCreate</code> or since, while also allowing Android to re-layout your <code>Activity</code> using the xml file for the orientation now in use.

See <a href="http://android-developers.blogspot.com/2009/02/faster-screen-orientation-change.html" rel="noreferrer">here</a> or <a href="http://developer.android.com/guide/topics/resources/runtime-changes.html" rel="noreferrer" title="Handling Runtime Changes">here</a>.

It should be noted that these methods are now deprecated (although still more flexible than handling orientation change yourself as most of the above solutions suggest) with the recommendation that everyone switch to <code>Fragments</code> and instead use <code>setRetainInstance(true)</code> on each <code>Fragment</code> you want to retain.

blocks|key|765381|text|要在Android清单中进行的更改如下：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|765382|android:configChanges="keyboardHidden%7Corientation"+|code-block|syntax|javascript|765383|应增加的内部活动如下：|765384|public+void+onConfigurationChanged(Configuration+newConfig)+{
++++super.onConfigurationChanged(newConfig);

++++//+Checks+the+orientation+of+the+screen
++++if+(newConfig.orientation+==+Configuration.ORIENTATION_LANDSCAPE)+{
++++++++Toast.makeText(this,+"landscape",+Toast.LENGTH_SHORT).show();
++++}+else+if+(newConfig.orientation+==+Configuration.ORIENTATION_PORTRAIT)+{
++++++++Toast.makeText(this,+"portrait",+Toast.LENGTH_SHORT).show();
++++}
}|765385|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Changes to be made in the Android manifest are:

<pre><code>android:configChanges="keyboardHidden|orientation" 
</code></pre>

Additions to be made inside activity are:

<pre><code>public void onConfigurationChanged(Configuration newConfig) {
 super.onConfigurationChanged(newConfig);

 // Checks the orientation of the screen
 if (newConfig.orientation == Configuration.ORIENTATION_LANDSCAPE) {
 Toast.makeText(this, "landscape", Toast.LENGTH_SHORT).show();
 } else if (newConfig.orientation == Configuration.ORIENTATION_PORTRAIT) {
 Toast.makeText(this, "portrait", Toast.LENGTH_SHORT).show();
 }
}
</code></pre>

blocks|key|766310|text|onConfigurationChanged+is+called+when+the+screen+rotates.+
(onCreate+is+no+longer+called+when+the+screen+rotates+due+to+manifest,+see:++
android:configChanges)|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|766311|清单的哪个部分告诉它“不要调用onCreate()"？|unstyled|offset|length|style|CODE|766312|此外，谷歌的文档说要避免使用android:configChanges+(除了作为最后手段)。但他们建议的替代方法都使用android:configChanges。|766313|根据我的经验，模拟器总是在旋转时调用onCreate()。|766314|但是我运行相同代码的1-2个设备.别说了。(不知道为什么会有任何不同。)|766315|entityMap^0|0|F|A|0|E|L|1O|L|0|I|A|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|T|8|@$G|U|H|V|I|J]]|9|@]|A|$]]|$1|K|3|L|5|F|7|W|8|@$G|X|H|Y|I|J]|$G|Z|H|10|I|J]]|9|@]|A|$]]|$1|M|3|N|5|F|7|11|8|@$G|12|H|13|I|J]]|9|@]|A|$]]|$1|O|3|P|5|F|7|14|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|F|7|15|8|@]|9|@]|A|$]]]|R|$]]

<pre><code>onConfigurationChanged is called when the screen rotates. 
(onCreate is no longer called when the screen rotates due to manifest, see: 
android:configChanges)
</code></pre>
What part of the manifest tells it &quot;don't call <code>onCreate()</code>&quot;?
Also,
Google's docs say to avoid using <code>android:configChanges</code> (except as a last resort). But then the alternative methods they suggest all DO use <code>android:configChanges</code>.
It has been my experience that the emulator ALWAYS calls <code>onCreate()</code> upon rotation. 
But the 1-2 devices that I run the same code on... do not.
(Not sure why there would be any difference.)

blocks|key|1998255|text|Android+3.2及更高版本的更新：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1998256|警告：从Android3.2+(API级别13)开始，当设备在纵向和横向之间切换时，的“屏幕大小”也会改变。因此，如果希望在为API级别13或更高级别开发时(如minSdkVersion和targetSdkVersion属性声明的那样)时由于方向更改而防止运行时重新启动，则除了"orientation"值之外，还必须包含"screenSize"值。也就是说，您必须声明android:configChanges="orientation%7CscreenSize"。但是，如果应用程序的目标是API级别12或更低，那么您的活动总是自行处理此配置更改(即使在Android3.2或更高的设备上运行，此配置更改也不会重新启动您的活动)。|blockquote|offset|length|style|BOLD|CODE|1998257|来自http://web.archive.org/web/20120805085007/http://developer.android.com/guide/topics/resources/runtime-changes.html|1998258|entityMap|0|LINK|mutability|MUTABLE|url|http://web.archive.org/web/20120805085007/http://developer.android.com/guide/topics/resources/runtime-changes.html^0|0|0|2|16|B|3V|D|4H|C|55|1A|0|2|36|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|U|8|@$E|V|F|W|G|H]|$E|X|F|Y|G|H]|$E|Z|F|10|G|I]|$E|11|F|12|G|I]|$E|13|F|14|G|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|15|8|@]|9|@$E|16|F|17|1|18]]|A|$]]|$1|L|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]]]

Update for Android 3.2 and higher:
<blockquote>
Caution: Beginning with Android 3.2 (API level 13), the &quot;screen size&quot; also changes when the device switches between portrait and landscape orientation. Thus, if you want to prevent runtime restarts due to orientation change when developing for API level 13 or higher (as declared by the minSdkVersion and targetSdkVersion attributes), you must include the <code>&quot;screenSize&quot;</code> value in addition to the <code>&quot;orientation&quot;</code> value. That is, you must declare <code>android:configChanges=&quot;orientation|screenSize&quot;</code>. However, if your application targets API level 12 or lower, then your activity always handles this configuration change itself (this configuration change does not restart your activity, even when running on an Android 3.2 or higher device).
</blockquote>
From <a href="http://web.archive.org/web/20120805085007/http://developer.android.com/guide/topics/resources/runtime-changes.html" rel="nofollow noreferrer">http://web.archive.org/web/20120805085007/http://developer.android.com/guide/topics/resources/runtime-changes.html</a>

blocks|key|464147|text|尽管它不是“Android方式”，但我通过自己处理方向更改并简单地将小部件重新定位到考虑到更改的方向，获得了非常好的结果。这比任何其他方法都要快，因为您的视图不需要保存和还原。它还为用户提供了更无缝的体验，因为重新定位的小部件完全相同，只是移动和/或调整大小。这样不仅可以保留模型状态，还可以保留视图状态。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|464148|对于需要不时调整方向的视图来说，RelativeLayout有时是一个很好的选择。您只需为每个子部件提供一组纵向布局参数和一组美化布局参数，并在每个子部件上具有不同的相对定位规则。然后，在onConfigurationChanged()方法中，将适当的调用传递给每个子节点的setLayoutParams()调用。如果任何子控件本身需要内部重定向，则只需调用该子控件上的方法来执行重定向。该子控件类似地对其任何需要内部重定向的子控件调用方法，等等。|offset|length|style|CODE|464149|entityMap^0|0|G|E|2M|O|3T|H|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]|$D|N|E|O|F|G]|$D|P|E|Q|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|I|$]]

Even though it is not "the Android way" I have gotten very good results by handling orientation changes myself and simply repositioning the widgets within a view to take the altered orientation into account. This is faster than any other approach, because your views do not have to be saved and restored. It also provides a more seamless experience to the user, because the respositioned widgets are exactly the same widgets, just moved and/or resized. Not only model state, but also view state, can be preserved in this manner.

<code>RelativeLayout</code> can sometimes be a good choice for a view that has to reorient itself from time to time. You just provide a set of portrait layout params and a set of landscaped layout params, with different relative positioning rules on each, for each child widget. Then, in your <code>onConfigurationChanged()</code> method, you pass the appropriate one to a <code>setLayoutParams()</code> call on each child. If any child control itself needs to be internally reoriented, you just call a method on that child to perform the reorientation. That child similarly calls methods on any of its child controls that need internal reorientation, and so on.

blocks|key|464180|text|与其试图完全阻止onCreate()被触发，不如尝试检查传递到事件中的Bundle+savedInstanceState，看看它是否为空。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|464181|例如，如果我有一些在真正创建Activity时应该运行的逻辑，而不是在每个方向上更改时运行，那么只有当onCreate()为null时，我才在savedInstanceState中运行该逻辑。|464182|否则，我仍然希望布局重新绘制正确的方向。|464183|public+void+onCreate(Bundle+savedInstanceState)+{

++++++++super.onCreate(savedInstanceState);

++++++++setContentView(R.layout.activity_game_list);

++++++++if(savedInstanceState+==+null){
++++++++++++setupCloudMessaging();
++++++++}
}|code-block|syntax|javascript|464184|不确定这是否是最终的答案，但这对我有用。|464185|entityMap^0|8|A|Z|6|16|I|0|E|8|1F|A|1Z|I|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]|$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Z|8|@$9|10|A|11|B|C]|$9|12|A|13|B|C]|$9|14|A|15|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|16|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|17|8|@]|D|@]|E|$M|N]]|$1|O|3|P|5|6|7|18|8|@]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|19|8|@]|D|@]|E|$]]]|R|$]]

Instead of trying to stop the <code>onCreate()</code> from being fired altogether, maybe try checking the <code>Bundle</code> <code>savedInstanceState</code> being passed into the event to see if it is null or not. 

For instance, if I have some logic that should be run when the <code>Activity</code> is truly created, not on every orientation change, I only run that logic in the <code>onCreate()</code> only if the <code>savedInstanceState</code> is null. 

Otherwise, I still want the layout to redraw properly for the orientation.

<pre><code>public void onCreate(Bundle savedInstanceState) {

 super.onCreate(savedInstanceState);

 setContentView(R.layout.activity_game_list);

 if(savedInstanceState == null){
 setupCloudMessaging();
 }
}
</code></pre>

not sure if this is the ultimate answer, but it works for me.

blocks|key|766363|text|我只是简单地说|type|unstyled|depth|inlineStyleRanges|entityRanges|data|766364|+++++android:configChanges="keyboard%7CkeyboardHidden%7Corientation"|code-block|syntax|javascript|766365|在清单文件和中，没有在我的活动中添加任何onConfigurationChanged方法。|offset|length|style|BOLD|CODE|766366|所以每次键盘滑出或者什么都没有发生。|766367|entityMap|0|LINK|mutability|MUTABLE|url|http://www.coboltforge.com/2012/08/tech-stuff-prevent-android-app-from-restarting-after-sliding-out-the-hardware-keyboard/^0|0|0|6|C|K|M|0|0|H|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Y|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Z|8|@$I|10|J|11|K|L]|$I|12|J|13|K|M]]|9|@]|A|$]]|$1|N|3|O|5|6|7|14|8|@]|9|@$I|15|J|16|1|17]]|A|$]]|$1|P|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|Q|$R|$5|S|T|U|A|$V|W]]]]

I just simply added 

<pre><code> android:configChanges="keyboard|keyboardHidden|orientation"
</code></pre>

in the manifest file and did not add any <code>onConfigurationChanged</code> method in my activity.

<a href="http://www.coboltforge.com/2012/08/tech-stuff-prevent-android-app-from-restarting-after-sliding-out-the-hardware-keyboard/">So every time the keyboard slides out or in nothing happens</a>.

blocks|key|464290|text|这种方法很有用，但在使用片段时是不完整的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|464291|片段通常在配置更改时重新创建。如果你不希望这种情况发生，请使用|464292|片段构造函数中的setRetainInstance(true);|offset|length|style|CODE|464293|这将导致在配置更改期间保留片段。|464294|http://developer.android.com/reference/android/app/Fragment.html#setRetainInstance(boolean)|464295|entityMap|0|LINK|mutability|MUTABLE|url|http://developer.android.com/reference/android/app/Fragment.html#setRetainInstance%2528boolean%2529^0|0|0|8|O|0|0|0|2J|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|X|8|@$F|Y|G|Z|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|10|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|11|8|@]|9|@$F|12|G|13|1|14]]|A|$]]|$1|N|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U]]]]

The approach is useful but is incomplete when using Fragments.

Fragments usually get recreated on configuration change. If you don't wish this to happen, use

<code>setRetainInstance(true);</code> in the Fragment's constructor(s)

This will cause fragments to be retained during configuration change.

<a href="http://developer.android.com/reference/android/app/Fragment.html#setRetainInstance%28boolean%29" rel="noreferrer">http://developer.android.com/reference/android/app/Fragment.html#setRetainInstance(boolean)</a>

blocks|key|464318|text|我发现这样做的方法是使用onRestoreInstanceState和onSaveInstanceState事件在Bundle中保存一些东西(即使您不需要保存任何变量，也只需在其中放置一些东西，这样Bundle就不会为空)。然后，在onCreate方法上，检查Bundle是否为空，如果为空，则执行初始化，如果不是，则执行初始化。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|464319|entityMap^0|C|M|Z|J|1L|6|2R|6|38|8|3M|6|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]|$9|Q|A|R|B|C]|$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|U|8|@]|D|@]|E|$]]]|G|$]]

The way I have found to do this is use the <code>onRestoreInstanceState</code> and the <code>onSaveInstanceState</code> events to save something in the <code>Bundle</code> (even if you dont need any variables saved, just put something in there so the <code>Bundle</code> isn't empty). Then, on the <code>onCreate</code> method, check to see if the <code>Bundle</code> is empty, and if it is, then do the initialization, if not, then do it.

blocks|key|1998473|text|修复AndroidManifest.xml中的屏幕方向(景观或肖像)|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1998474|android:screenOrientation="portrait"或android:screenOrientation="landscape"|1998475|为此，不调用onResume()方法。|1998476|entityMap^0|2|J|0|0|10|11|11|0|6|A|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|T|8|@$9|U|A|V|B|C]]|D|@]|E|$]]|$1|J|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|K|$]]

Fix the screen orientation (landscape or portrait) in <code>AndroidManifest.xml</code>

<code>android:screenOrientation="portrait"</code> or <code>android:screenOrientation="landscape"</code>

for this your <code>onResume()</code> method is not called.

blocks|key|1998493|text|将下面的代码放在Activity中的Android+Manifest中。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1998494|android:configChanges="orientation"|code-block|syntax|javascript|1998495|当您改变方向时，这不会重新启动您的活动。|1998496|entityMap^0|8|8|I|G|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|T|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|U|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|N|$]]

Put this below code in your <code>Activity</code> in <code>Android Manifest</code>.

<pre><code>android:configChanges="orientation"
</code></pre>

This will not restart your activity when you would change orientation.

blocks|key|1998531|text|注意:如果将来有人和我一样面临同样的问题，我会发布这个答案。对我来说，下面这句话是不够的：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1998532|android:configChanges="orientation"|code-block|syntax|javascript|1998533|当我旋转屏幕时，没有调用‘`onConfigurationChanged(Configuration+)方法。|1998534|解决方案：--我还必须添加"screenSize“，即使问题与方向有关。因此，在AndroidManifest.xml+-文件中，添加以下内容：|1998535|android:configChanges="keyboardHidden%7Corientation%7CscreenSize"|1998536|然后实现方法onConfigurationChanged(Configuration+newConfig)|CODE|1998537|entityMap^0|0|19|0|0|0|1J|0|0|20|0|0|0|1H|6|1B|0^^$0|@$1|2|3|4|5|6|7|V|8|@$9|W|A|X|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|Y|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|Z|8|@$9|10|A|11|B|C]]|D|@]|E|$]]|$1|M|3|N|5|6|7|12|8|@$9|13|A|14|B|C]]|D|@]|E|$]]|$1|O|3|P|5|H|7|15|8|@]|D|@]|E|$I|J]]|$1|Q|3|R|5|6|7|16|8|@$9|17|A|18|B|C]|$9|19|A|1A|B|S]]|D|@]|E|$]]|$1|T|3|-4|5|6|7|1B|8|@]|D|@]|E|$]]]|U|$]]

Note: I post this answer if someone in the future face the same problem as me. For me the following line wasn't enough:
<pre><code>android:configChanges=&quot;orientation&quot;
</code></pre>
When I rotated the screen, the method `onConfigurationChanged(Configuration new config) didn't get called.
Solution: I also had to add &quot;screenSize&quot; even if the problem had to do with the orientation. So in the AndroidManifest.xml - file, add this:
<pre><code>android:configChanges=&quot;keyboardHidden|orientation|screenSize&quot;
</code></pre>
Then implement the method <code>onConfigurationChanged(Configuration newConfig)</code>

blocks|key|1998568|text|您可以使用以下代码锁定屏幕的当前方向.|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1998569|int+currentOrientation+=context.getResources().getConfiguration().orientation;
++++++++if+(currentOrientation+==+Configuration.ORIENTATION_PORTRAIT)+{
++++++++++++((Activity)+context).setRequestedOrientation(ActivityInfo.SCREEN_ORIENTATION_PORTRAIT);
++++++++}+else+{
++++++++++++((Activity)+context).+setRequestedOrientation(ActivityInfo.SCREEN_ORIENTATION_LANDSCAPE);
++++++++}|code-block|syntax|javascript|1998570|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

You can lock to the current orientation of the screen using this code...
<pre><code>int currentOrientation =context.getResources().getConfiguration().orientation;
 if (currentOrientation == Configuration.ORIENTATION_PORTRAIT) {
 ((Activity) context).setRequestedOrientation(ActivityInfo.SCREEN_ORIENTATION_PORTRAIT);
 } else {
 ((Activity) context). setRequestedOrientation(ActivityInfo.SCREEN_ORIENTATION_LANDSCAPE);
 }
</code></pre>

blocks|key|765522|text|将这一行添加到您的清单中:-|type|unstyled|depth|inlineStyleRanges|entityRanges|data|765523|android:configChanges="orientation%7Ckeyboard%7CkeyboardHidden%7CscreenSize%7CscreenLayout%7CuiMode"|code-block|syntax|javascript|765524|这个活动片段是:-|765525|@Override
++++public+void+onConfigurationChanged(Configuration+newConfig)+{
++++++++super.onConfigurationChanged(newConfig);
++++++++getWindow().setFlags(WindowManager.LayoutParams.FLAG_FULLSCREEN,
++++++++++++++++WindowManager.LayoutParams.FLAG_FULLSCREEN);
++++}|765526|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Add this line to your manifest :- 

<pre><code>android:configChanges="orientation|keyboard|keyboardHidden|screenSize|screenLayout|uiMode"
</code></pre>

and this snippet to the activity :-

<pre><code>@Override
 public void onConfigurationChanged(Configuration newConfig) {
 super.onConfigurationChanged(newConfig);
 getWindow().setFlags(WindowManager.LayoutParams.FLAG_FULLSCREEN,
 WindowManager.LayoutParams.FLAG_FULLSCREEN);
 }
</code></pre>

blocks|key|464442|text|将下面的代码放入<activity>标记中的Manifest.xml中|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|464443|android:configChanges="screenLayout%7CscreenSize%7Corientation"|code-block|syntax|javascript|464444|entityMap^0|8|A|M|C|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|L|$]]

Put the code below inside your <code>&lt;activity&gt;</code> tag in <code>Manifest.xml</code>:

<pre><code>android:configChanges="screenLayout|screenSize|orientation"
</code></pre>

blocks|key|765538|text|使用orientation侦听器在不同的方向执行不同的任务。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|765539|@Override
public+void+onConfigurationChanged(Configuration+myConfig)+
{
++++super.onConfigurationChanged(myConfig);
++++int+orient+=+getResources().getConfiguration().orientation;+
++++switch(orient)+
++++{
+++++++case+Configuration.ORIENTATION_LANDSCAPE:
++++++++++setRequestedOrientation(ActivityInfo.SCREEN_ORIENTATION_LANDSCAPE);
++++++++++++++++++++break;
+++++++case+Configuration.ORIENTATION_PORTRAIT:
++++++++++setRequestedOrientation(ActivityInfo.SCREEN_ORIENTATION_PORTRAIT);
++++++++++++++++++++break;
+++++++default:
++++++++++setRequestedOrientation(ActivityInfo.SCREEN_ORIENTATION_UNSPECIFIED);
++++}
}|code-block|syntax|javascript|765540|entityMap^0|2|B|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

Use <code>orientation</code> listener to perform different tasks on different orientation.

<pre><code>@Override
public void onConfigurationChanged(Configuration myConfig) 
{
 super.onConfigurationChanged(myConfig);
 int orient = getResources().getConfiguration().orientation; 
 switch(orient) 
 {
 case Configuration.ORIENTATION_LANDSCAPE:
 setRequestedOrientation(ActivityInfo.SCREEN_ORIENTATION_LANDSCAPE);
 break;
 case Configuration.ORIENTATION_PORTRAIT:
 setRequestedOrientation(ActivityInfo.SCREEN_ORIENTATION_PORTRAIT);
 break;
 default:
 setRequestedOrientation(ActivityInfo.SCREEN_ORIENTATION_UNSPECIFIED);
 }
}
</code></pre>

blocks|key|464518|text|经过一段时间的反复试验，我找到了一个适合我在大多数情况下需要的解决方案。以下是守则：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|464519|报表配置：|offset|length|style|BOLD|464520|<?xml+version="1.0"+encoding="utf-8"?>
<manifest+xmlns:android="http://schemas.android.com/apk/res/android"
++++++++++package="com.pepperonas.myapplication">

++++<application
++++++++android:name=".App"
++++++++android:allowBackup="true"
++++++++android:icon="@mipmap/ic_launcher"
++++++++android:label="@string/app_name"
++++++++android:supportsRtl="true"
++++++++android:theme="@style/AppTheme">
++++++++<activity
++++++++++++android:name=".MainActivity"
++++++++++++android:configChanges="orientation%7CkeyboardHidden%7CscreenSize">
++++++++++++<intent-filter>
++++++++++++++++<action+android:name="android.intent.action.MAIN"/>

++++++++++++++++<category+android:name="android.intent.category.LAUNCHER"/>
++++++++++++</intent-filter>
++++++++</activity>
++++</application>

</manifest>|code-block|syntax|javascript|464521|MainActivity:|464522|import+android.content.res.Configuration;
import+android.os.Bundle;
import+android.support.v4.app.Fragment;
import+android.support.v4.app.FragmentManager;
import+android.support.v4.app.FragmentTransaction;
import+android.support.v7.app.AppCompatActivity;
import+android.util.Log;
import+android.view.View;
import+android.widget.Button;

public+class+MainActivity+extends+AppCompatActivity+implements+View.OnClickListener+{

++++private+static+final+String+TAG+=+"MainActivity";

++++private+Fragment+mFragment;

++++private+int+mSelected+=+-1;


++++@Override
++++public+void+onCreate(Bundle+savedInstanceState)+{
++++++++super.onCreate(savedInstanceState);
++++++++Log.d(TAG,+"onCreate++"+%2B+"");

++++++++//+null+check+not+realy+needed+-+but+just+in+case...
++++++++if+(savedInstanceState+==+null)+{

++++++++++++initUi();

++++++++++++//+get+an+instance+of+FragmentTransaction+from+your+Activity
++++++++++++FragmentManager+fragmentManager+=+getSupportFragmentManager();
++++++++++++FragmentTransaction+fragmentTransaction+=+fragmentManager.beginTransaction();

++++++++++++/*IMPORTANT:+Do+the+INITIAL(!)+transaction+only+once!
++++++++++++*+If+we+call+this+everytime+the+layout+changes+orientation,
++++++++++++*+we+will+end+with+a+messy,+half-working+UI.
++++++++++++*+*/
++++++++++++mFragment+=+FragmentOne.newInstance(mSelected+=+0);
++++++++++++fragmentTransaction.add(R.id.frame,+mFragment);
++++++++++++fragmentTransaction.commit();
++++++++}
++++}


++++@Override
++++public+void+onConfigurationChanged(Configuration+newConfig)+{
++++++++super.onConfigurationChanged(newConfig);
++++++++Log.d(TAG,+"onConfigurationChanged++"+%2B
+++++++++++++++++++(newConfig.orientation
++++++++++++++++++++==+Configuration.ORIENTATION_LANDSCAPE
++++++++++++++++++++?+"landscape"+:+"portrait"));

++++++++initUi();

++++++++Log.i(TAG,+"onConfigurationChanged+-+last+selected:+"+%2B+mSelected);
++++++++makeFragmentTransaction(mSelected);
++++}


++++/**
+++++*+Called+from+{@link+#onCreate}+and+{@link+#onConfigurationChanged}
+++++*/
++++private+void+initUi()+{
++++++++setContentView(R.layout.activity_main);
++++++++Log.d(TAG,+"onCreate++instanceState+==+null+/+reinitializing..."+%2B+"");
++++++++Button+btnFragmentOne+=+(Button)+findViewById(R.id.btn_fragment_one);
++++++++Button+btnFragmentTwo+=+(Button)+findViewById(R.id.btn_fragment_two);
++++++++btnFragmentOne.setOnClickListener(this);
++++++++btnFragmentTwo.setOnClickListener(this);
++++}


++++/**
+++++*+Not+invoked+(just+for+testing)...
+++++*/
++++@Override
++++protected+void+onSaveInstanceState(Bundle+outState)+{
++++++++super.onSaveInstanceState(outState);
++++++++Log.d(TAG,+"onSaveInstanceState++"+%2B+"YOU+WON'T+SEE+ME!!!");
++++}


++++/**
+++++*+Not+invoked+(just+for+testing)...
+++++*/
++++@Override
++++protected+void+onRestoreInstanceState(Bundle+savedInstanceState)+{
++++++++super.onRestoreInstanceState(savedInstanceState);
++++++++Log.d(TAG,+"onSaveInstanceState++"+%2B+"YOU+WON'T+SEE+ME,+AS+WELL!!!");
++++}


++++@Override
++++protected+void+onResume()+{
++++++++super.onResume();
++++++++Log.d(TAG,+"onResume++"+%2B+"");
++++}


++++@Override
++++protected+void+onPause()+{
++++++++super.onPause();
++++++++Log.d(TAG,+"onPause++"+%2B+"");
++++}


++++@Override
++++protected+void+onDestroy()+{
++++++++super.onDestroy();
++++++++Log.d(TAG,+"onDestroy++"+%2B+"");
++++}


++++@Override
++++public+void+onClick(View+v)+{

++++++++switch+(v.getId())+{
++++++++++++case+R.id.btn_fragment_one:
++++++++++++++++Log.d(TAG,+"onClick+btn_fragment_one+"+%2B+"");
++++++++++++++++makeFragmentTransaction(0);
++++++++++++++++break;

++++++++++++case+R.id.btn_fragment_two:
++++++++++++++++Log.d(TAG,+"onClick+btn_fragment_two+"+%2B+"");
++++++++++++++++makeFragmentTransaction(1);
++++++++++++++++break;

++++++++++++default:
++++++++++++++++Log.d(TAG,+"onClick++null+-+wtf?!"+%2B+"");
++++++++}
++++}


++++/**
+++++*+We+replace+the+current+Fragment+with+the+selected+one.
+++++*+Note:+It's+called+from+{@link+#onConfigurationChanged}+as+well.
+++++*/
++++private+void+makeFragmentTransaction(int+selection)+{

++++++++switch+(selection)+{
++++++++++++case+0:
++++++++++++++++mFragment+=+FragmentOne.newInstance(mSelected+=+0);
++++++++++++++++break;
++++++++++++case+1:
++++++++++++++++mFragment+=+FragmentTwo.newInstance(mSelected+=+1);
++++++++++++++++break;
++++++++}

++++++++//+Create+new+transaction
++++++++FragmentTransaction+transaction+=+getSupportFragmentManager().beginTransaction();

++++++++//+Replace+whatever+is+in+the+fragment_container+view+with+this+fragment,
++++++++//+and+add+the+transaction+to+the+back+stack
++++++++transaction.replace(R.id.frame,+mFragment);

++++++++/*This+would+add+the+Fragment+to+the+backstack...
++++++++*+But+right+now+we+comment+it+out.*/
++++++++//++++++++transaction.addToBackStack(null);

++++++++//+Commit+the+transaction
++++++++transaction.commit();
++++}

}|464523|和样本片段：|464524|import+android.os.Bundle;
import+android.support.v4.app.Fragment;
import+android.util.Log;
import+android.view.LayoutInflater;
import+android.view.View;
import+android.view.ViewGroup;

/**
+*+@author+Martin+Pfeffer+(pepperonas)
+*/
public+class+FragmentOne+extends+Fragment+{

++++private+static+final+String+TAG+=+"FragmentOne";


++++public+static+Fragment+newInstance(int+i)+{
++++++++Fragment+fragment+=+new+FragmentOne();
++++++++Bundle+args+=+new+Bundle();
++++++++args.putInt("the_id",+i);
++++++++fragment.setArguments(args);
++++++++return+fragment;
++++}


++++@Override
++++public+View+onCreateView(LayoutInflater+inflater,+ViewGroup+container,+Bundle+savedInstanceState)+{
++++++++Log.d(TAG,+"onCreateView++"+%2B+"");
++++++++return+inflater.inflate(R.layout.fragment_one,+container,+false);
++++}

}|464525|可以在github上找到。|464526|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/pepperonas/AndroidTest^0|0|0|5|0|0|0|D|0|0|0|6|0|0|3|6|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|15|8|@$D|16|E|17|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|18|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|19|8|@$D|1A|E|1B|F|G]]|9|@]|A|$]]|$1|O|3|P|5|J|7|1C|8|@]|9|@]|A|$K|L]]|$1|Q|3|R|5|6|7|1D|8|@$D|1E|E|1F|F|G]]|9|@]|A|$]]|$1|S|3|T|5|J|7|1G|8|@]|9|@]|A|$K|L]]|$1|U|3|V|5|6|7|1H|8|@]|9|@$D|1I|E|1J|1|1K]]|A|$]]|$1|W|3|-4|5|6|7|1L|8|@]|9|@]|A|$]]]|X|$Y|$5|Z|10|11|A|$12|13]]]]

After a while of trial and error, I found a solution which fits my needs in the most situations. Here is the Code:

Manifest configuration:

<pre><code>&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;manifest xmlns:android="http://schemas.android.com/apk/res/android"
 package="com.pepperonas.myapplication"&gt;

 &lt;application
 android:name=".App"
 android:allowBackup="true"
 android:icon="@mipmap/ic_launcher"
 android:label="@string/app_name"
 android:supportsRtl="true"
 android:theme="@style/AppTheme"&gt;
 &lt;activity
 android:name=".MainActivity"
 android:configChanges="orientation|keyboardHidden|screenSize"&gt;
 &lt;intent-filter&gt;
 &lt;action android:name="android.intent.action.MAIN"/&gt;

 &lt;category android:name="android.intent.category.LAUNCHER"/&gt;
 &lt;/intent-filter&gt;
 &lt;/activity&gt;
 &lt;/application&gt;

&lt;/manifest&gt;
</code></pre>

MainActivity:

<pre><code>import android.content.res.Configuration;
import android.os.Bundle;
import android.support.v4.app.Fragment;
import android.support.v4.app.FragmentManager;
import android.support.v4.app.FragmentTransaction;
import android.support.v7.app.AppCompatActivity;
import android.util.Log;
import android.view.View;
import android.widget.Button;

public class MainActivity extends AppCompatActivity implements View.OnClickListener {

 private static final String TAG = "MainActivity";

 private Fragment mFragment;

 private int mSelected = -1;


 @Override
 public void onCreate(Bundle savedInstanceState) {
 super.onCreate(savedInstanceState);
 Log.d(TAG, "onCreate " + "");

 // null check not realy needed - but just in case...
 if (savedInstanceState == null) {

 initUi();

 // get an instance of FragmentTransaction from your Activity
 FragmentManager fragmentManager = getSupportFragmentManager();
 FragmentTransaction fragmentTransaction = fragmentManager.beginTransaction();

 /*IMPORTANT: Do the INITIAL(!) transaction only once!
 * If we call this everytime the layout changes orientation,
 * we will end with a messy, half-working UI.
 * */
 mFragment = FragmentOne.newInstance(mSelected = 0);
 fragmentTransaction.add(R.id.frame, mFragment);
 fragmentTransaction.commit();
 }
 }


 @Override
 public void onConfigurationChanged(Configuration newConfig) {
 super.onConfigurationChanged(newConfig);
 Log.d(TAG, "onConfigurationChanged " +
 (newConfig.orientation
 == Configuration.ORIENTATION_LANDSCAPE
 ? "landscape" : "portrait"));

 initUi();

 Log.i(TAG, "onConfigurationChanged - last selected: " + mSelected);
 makeFragmentTransaction(mSelected);
 }


 /**
 * Called from {@link #onCreate} and {@link #onConfigurationChanged}
 */
 private void initUi() {
 setContentView(R.layout.activity_main);
 Log.d(TAG, "onCreate instanceState == null / reinitializing..." + "");
 Button btnFragmentOne = (Button) findViewById(R.id.btn_fragment_one);
 Button btnFragmentTwo = (Button) findViewById(R.id.btn_fragment_two);
 btnFragmentOne.setOnClickListener(this);
 btnFragmentTwo.setOnClickListener(this);
 }


 /**
 * Not invoked (just for testing)...
 */
 @Override
 protected void onSaveInstanceState(Bundle outState) {
 super.onSaveInstanceState(outState);
 Log.d(TAG, "onSaveInstanceState " + "YOU WON'T SEE ME!!!");
 }


 /**
 * Not invoked (just for testing)...
 */
 @Override
 protected void onRestoreInstanceState(Bundle savedInstanceState) {
 super.onRestoreInstanceState(savedInstanceState);
 Log.d(TAG, "onSaveInstanceState " + "YOU WON'T SEE ME, AS WELL!!!");
 }


 @Override
 protected void onResume() {
 super.onResume();
 Log.d(TAG, "onResume " + "");
 }


 @Override
 protected void onPause() {
 super.onPause();
 Log.d(TAG, "onPause " + "");
 }


 @Override
 protected void onDestroy() {
 super.onDestroy();
 Log.d(TAG, "onDestroy " + "");
 }


 @Override
 public void onClick(View v) {

 switch (v.getId()) {
 case R.id.btn_fragment_one:
 Log.d(TAG, "onClick btn_fragment_one " + "");
 makeFragmentTransaction(0);
 break;

 case R.id.btn_fragment_two:
 Log.d(TAG, "onClick btn_fragment_two " + "");
 makeFragmentTransaction(1);
 break;

 default:
 Log.d(TAG, "onClick null - wtf?!" + "");
 }
 }


 /**
 * We replace the current Fragment with the selected one.
 * Note: It's called from {@link #onConfigurationChanged} as well.
 */
 private void makeFragmentTransaction(int selection) {

 switch (selection) {
 case 0:
 mFragment = FragmentOne.newInstance(mSelected = 0);
 break;
 case 1:
 mFragment = FragmentTwo.newInstance(mSelected = 1);
 break;
 }

 // Create new transaction
 FragmentTransaction transaction = getSupportFragmentManager().beginTransaction();

 // Replace whatever is in the fragment_container view with this fragment,
 // and add the transaction to the back stack
 transaction.replace(R.id.frame, mFragment);

 /*This would add the Fragment to the backstack...
 * But right now we comment it out.*/
 // transaction.addToBackStack(null);

 // Commit the transaction
 transaction.commit();
 }

}
</code></pre>

And sample Fragment:

<pre><code>import android.os.Bundle;
import android.support.v4.app.Fragment;
import android.util.Log;
import android.view.LayoutInflater;
import android.view.View;
import android.view.ViewGroup;

/**
 * @author Martin Pfeffer (pepperonas)
 */
public class FragmentOne extends Fragment {

 private static final String TAG = "FragmentOne";


 public static Fragment newInstance(int i) {
 Fragment fragment = new FragmentOne();
 Bundle args = new Bundle();
 args.putInt("the_id", i);
 fragment.setArguments(args);
 return fragment;
 }


 @Override
 public View onCreateView(LayoutInflater inflater, ViewGroup container, Bundle savedInstanceState) {
 Log.d(TAG, "onCreateView " + "");
 return inflater.inflate(R.layout.fragment_one, container, false);
 }

}
</code></pre>

Can be found on <a href="https://github.com/pepperonas/AndroidTest" rel="nofollow">github</a>.

blocks|key|464537|text|它非常简单，只需执行以下步骤：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|464538|<activity
++++android:name=".Test"
++++android:configChanges="orientation%7CscreenSize"
++++android:screenOrientation="landscape"+>
</activity>|code-block|syntax|javascript|464539|这对我来说很管用：|464540|注：定位取决于您的请求|offset|length|style|BOLD|464541|entityMap^0|0|0|0|0|2|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|T|8|@$K|U|L|V|M|N]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

It is very simple just do the following steps:

<pre><code>&lt;activity
 android:name=".Test"
 android:configChanges="orientation|screenSize"
 android:screenOrientation="landscape" &gt;
&lt;/activity&gt;
</code></pre>

This works for me :

Note: orientation depends on your requitement

blocks|key|765630|text|有几种方法可以做到这一点：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|765631|保存活动状态|offset|length|style|BOLD|765632|您可以在onSaveInstanceState中保存活动状态。|CODE|765633|@Override
public+void+onSaveInstanceState(Bundle+outState)+{
++++/*Save+your+data+to+be+restored+here
++++Example:+outState.putLong("time_state",+time);+,+time+is+a+long+variable*/
++++super.onSaveInstanceState(outState);
}|code-block|syntax|javascript|765634|然后使用bundle恢复状态。|765635|@Override
protected+void+onCreate(Bundle+savedInstanceState)+{
++++super.onCreate(savedInstanceState);

++++if(savedInstanceState!=+null){
+++++++/*When+rotation+occurs
++++++++Example+:+time+=+savedInstanceState.getLong("time_state",+0);+*/
++++}+else+{
++++++//When+onCreate+is+called+for+the+first+time
++++}
}|765636|自行处理方向变更|765637|另一种选择是自己处理方向变化。但这被认为不是一个好做法。|765638|将此添加到清单文件中。|765639|android:configChanges="keyboardHidden%7Corientation"|765640|对于Android3.2及更高版本：|765641|android:configChanges="keyboardHidden%7Corientation%7CscreenSize"

@Override
public+void+onConfigurationChanged(Configuration+config)+{
++++super.onConfigurationChanged(config);
++++
if+(newConfig.orientation+==+Configuration.ORIENTATION_PORTRAIT)+{
++++++++//Handle+rotation+from+landscape+to+portrait+mode+here
++++}+else+if+(newConfig.orientation+==+Configuration.ORIENTATION_LANDSCAPE){
++++++++//Handle+rotation+from+portrait+to+landscape+mode+here
++++}
}|765642|限制旋转|765643|您也可以限制您的活动肖像或景观模式，以避免旋转。|765644|将其添加到清单文件中的活动标记中：|765645|++++++++android:screenOrientation="portrait"|765646|或在您的活动中以编程方式实现此功能：|765647|@Override
++++protected+void+onCreate(Bundle+savedInstanceState)+{
++++++++super.onCreate(savedInstanceState);
++++++++setRequestedOrientation(ActivityInfo.SCREEN_ORIENTATION_PORTRAIT);
}|765648|entityMap^0|0|0|6|0|4|J|0|0|4|6|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1K|8|@$D|1L|E|1M|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|1N|8|@$D|1O|E|1P|F|J]]|9|@]|A|$]]|$1|K|3|L|5|M|7|1Q|8|@]|9|@]|A|$N|O]]|$1|P|3|Q|5|6|7|1R|8|@$D|1S|E|1T|F|J]]|9|@]|A|$]]|$1|R|3|S|5|M|7|1U|8|@]|9|@]|A|$N|O]]|$1|T|3|U|5|6|7|1V|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|1W|8|@]|9|@]|A|$]]|$1|X|3|Y|5|6|7|1X|8|@]|9|@]|A|$]]|$1|Z|3|10|5|M|7|1Y|8|@]|9|@]|A|$N|O]]|$1|11|3|12|5|6|7|1Z|8|@]|9|@]|A|$]]|$1|13|3|14|5|M|7|20|8|@]|9|@]|A|$N|O]]|$1|15|3|16|5|6|7|21|8|@]|9|@]|A|$]]|$1|17|3|18|5|6|7|22|8|@]|9|@]|A|$]]|$1|19|3|1A|5|6|7|23|8|@]|9|@]|A|$]]|$1|1B|3|1C|5|M|7|24|8|@]|9|@]|A|$N|O]]|$1|1D|3|1E|5|6|7|25|8|@]|9|@]|A|$]]|$1|1F|3|1G|5|M|7|26|8|@]|9|@]|A|$N|O]]|$1|1H|3|-4|5|6|7|27|8|@]|9|@]|A|$]]]|1I|$]]

There are several ways to do this:
<h2>Save Activity State</h2>
You can save the activity state in <code>onSaveInstanceState</code>.
<pre><code>@Override
public void onSaveInstanceState(Bundle outState) {
 /*Save your data to be restored here
 Example: outState.putLong(&quot;time_state&quot;, time); , time is a long variable*/
 super.onSaveInstanceState(outState);
}
</code></pre>
and then use the <code>bundle</code> to restore the state.
<pre><code>@Override
protected void onCreate(Bundle savedInstanceState) {
 super.onCreate(savedInstanceState);

 if(savedInstanceState!= null){
 /*When rotation occurs
 Example : time = savedInstanceState.getLong(&quot;time_state&quot;, 0); */
 } else {
 //When onCreate is called for the first time
 }
}
</code></pre>
<h2>Handle orientation changes by yourself</h2>
Another alternative is to handle the orientation changes by yourself. But this is not considered a good practice.
Add this to your manifest file.
<pre><code>android:configChanges=&quot;keyboardHidden|orientation&quot;
</code></pre>
for Android 3.2 and later:
<pre><code>android:configChanges=&quot;keyboardHidden|orientation|screenSize&quot;

@Override
public void onConfigurationChanged(Configuration config) {
 super.onConfigurationChanged(config);
 
if (newConfig.orientation == Configuration.ORIENTATION_PORTRAIT) {
 //Handle rotation from landscape to portrait mode here
 } else if (newConfig.orientation == Configuration.ORIENTATION_LANDSCAPE){
 //Handle rotation from portrait to landscape mode here
 }
}
</code></pre>
<h2>Restrict rotation</h2>
You can also confine your activity to portrait or landscape mode to avoid rotation.
Add this to the activity tag in your manifest file:
<pre><code> android:screenOrientation=&quot;portrait&quot;
</code></pre>
Or implement this programmatically in your activity:
<pre><code>@Override
 protected void onCreate(Bundle savedInstanceState) {
 super.onCreate(savedInstanceState);
 setRequestedOrientation(ActivityInfo.SCREEN_ORIENTATION_PORTRAIT);
}
</code></pre>

blocks|key|1998793|text|您需要使用onSavedInstanceState方法将所有值存储到其参数is具有，这是一个包。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1998794|@Override
++++public+void+onSaveInstanceState(Bundle+outState,+PersistableBundle+outPersistentState)+{
++++++++super.onSaveInstanceState(outState,+outPersistentState);
++++++++outPersistentState.putBoolean("key",value);
++++}|code-block|syntax|javascript|1998795|并使用|1998796|@Override
++++protected+void+onRestoreInstanceState(Bundle+savedInstanceState)+{
++++++++super.onRestoreInstanceState(savedInstanceState);
++++++++savedInstanceState.getBoolean("key");
++++}+|1998797|要检索和设置要查看对象的值，它将处理屏幕旋转。|1998798|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

you need to use the onSavedInstanceState method to store all the values to its parameter is has which is a bundle
<pre><code>@Override
 public void onSaveInstanceState(Bundle outState, PersistableBundle outPersistentState) {
 super.onSaveInstanceState(outState, outPersistentState);
 outPersistentState.putBoolean(&quot;key&quot;,value);
 }
</code></pre>
and use
<pre><code>@Override
 protected void onRestoreInstanceState(Bundle savedInstanceState) {
 super.onRestoreInstanceState(savedInstanceState);
 savedInstanceState.getBoolean(&quot;key&quot;);
 } 
</code></pre>
to retrieve and set the value to view objects
it will handle the screen rotations

blocks|key|464664|text|每当屏幕旋转时，打开的活动就会结束，onCreate()再次被调用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|464665|1.您可以做一件事，在屏幕旋转时保存活动状态，这样，当活动的onCreate()再次被调用时，您可以恢复所有旧的东西。参考这链接|offset|length|464666|2.如果要防止重新启动活动，只需在manifest.xml文件中放置以下行即可。|464667|<activity+android:name=".Youractivity"
++++android:configChanges="orientation%7CscreenSize"/>|code-block|syntax|javascript|464668|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/41804128/3578677.^0|0|1P|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@$D|W|E|X|1|Y]]|A|$]]|$1|F|3|G|5|6|7|Z|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|10|8|@]|9|@]|A|$K|L]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

Every time when the screen is rotated, opened activity is finished and onCreate() is called again.
1 . You can do one thing save the state of activity when the screen is rotated so that, You can recover all old stuff when the activity's onCreate() is called again.
Refer <a href="https://stackoverflow.com/a/41804128/3578677.">this</a> link
2 . If you want to prevent restarting of the activity just place the following lines in your manifest.xml file.
<pre><code>&lt;activity android:name=&quot;.Youractivity&quot;
 android:configChanges=&quot;orientation|screenSize&quot;/&gt;
</code></pre>

blocks|key|464688|text|在manifest的活动部分中，添加：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|464689|android:configChanges="keyboardHidden%7Corientation"|code-block|syntax|javascript|464690|entityMap^0|1|8|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

In the activity section of the <code>manifest</code>, add:

<pre><code>android:configChanges="keyboardHidden|orientation"
</code></pre>

blocks|key|1998889|text|在清单中添加这一行:+android:configChanges="orientation%7CscreenSize"|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|1998890|entityMap^0|0|A|B|1A|0^^$0|@$1|2|3|4|5|6|7|I|8|@$9|J|A|K|B|C]|$9|L|A|M|B|D]]|E|@]|F|$]]|$1|G|3|-4|5|6|7|N|8|@]|E|@]|F|$]]]|H|$]]

Add this line in manifest : <code>android:configChanges="orientation|screenSize"</code>

blocks|key|766603|text|人们说你应该用|type|unstyled|depth|inlineStyleRanges|entityRanges|data|766604|android:configChanges="keyboardHidden%7Corientation"|code-block|syntax|javascript|766605|但是，在Android中处理轮转的最好和最专业的方法是使用Loader类。它不是一个著名的类(我不知道为什么)，但它比AsyncTask好得多。要获得更多信息，您可以阅读在Udacity的Android课程中找到的Android教程。|766606|当然，作为另一种方式，您可以用onSaveInstanceState存储值或视图，并使用onRestoreInstanceState读取它们。这真的取决于你。|766607|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

People are saying that you should use 

<pre><code>android:configChanges="keyboardHidden|orientation"
</code></pre>

But the best and most professional way to handle rotation in Android is to use the Loader class. It's not a famous class(I don't know why), but it is way better than the AsyncTask. For more information, you can read the Android tutorials found in Udacity's Android courses. 

Of course, as another way, you could store the values or the views with onSaveInstanceState and read them with onRestoreInstanceState. It's up to you really.

blocks|key|765723|text|您可以在活动中使用ViewModel对象。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|765724|ViewModel对象在配置更改期间自动保留，以便它们所持有的数据可立即用于下一个活动或片段实例。阅读更多：https://developer.android.com/topic/libraries/architecture/viewmodel|offset|length|765725|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.android.com/topic/libraries/architecture/viewmodel^0|0|1I|1W|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

You may use the ViewModel object in your activity.
ViewModel objects are automatically retained during configuration changes so that the data they hold is immediately available to the next activity or fragment instance.
Read more:
<a href="https://developer.android.com/topic/libraries/architecture/viewmodel" rel="nofollow noreferrer">https://developer.android.com/topic/libraries/architecture/viewmodel</a>

blocks|key|464841|text|谷歌推出的android架构中最好的组件之一，将满足所有的ViewModel需求。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|464842|它旨在以生命周期的方式存储和管理与UI相关的数据，并且允许数据在屏幕旋转时存活下来。|464843|class+MyViewModel+:+ViewModel()+{|code-block|syntax|javascript|464844|请参阅此：https://developer.android.com/topic/libraries/architecture/viewmodel|offset|length|464845|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.android.com/topic/libraries/architecture/viewmodel^0|0|0|0|5|1W|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|X|8|@]|9|@$K|Y|L|Z|1|10]]|A|$]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

One of the best components of android architecture introduced by google will fulfill all the requirements that are ViewModel.
That is designed to store and manage UI-related data in a lifecycle way plus that will allow data to survive as the screen rotates
<pre><code>class MyViewModel : ViewModel() {
</code></pre>
Please refer to this: <a href="https://developer.android.com/topic/libraries/architecture/viewmodel" rel="nofollow noreferrer">https://developer.android.com/topic/libraries/architecture/viewmodel</a>

blocks|key|1999042|text|将此代码添加到您的manifest.xml中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1999043|这是你的活动。|1999044|<activity
....
..
android:configChanges="orientation%7CscreenSize"/>|code-block|syntax|javascript|1999045|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

add this code to your manifest.xml.
this is your activity.
<pre><code>&lt;activity
....
..
android:configChanges=&quot;orientation|screenSize&quot;/&gt;
</code></pre>

blocks|key|464884|text|在该活动中，将config+changes+设置为，类似于下面。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|464885|+android:configChanges="orientation%7CscreenSize%7CkeyboardHidden"|code-block|syntax|javascript|464886|entityMap^0|7|E|M|7|7|E|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]|$9|Q|A|R|B|C]|$9|S|A|T|B|D]]|E|@]|F|$]]|$1|G|3|H|5|I|7|U|8|@]|E|@]|F|$J|K]]|$1|L|3|-4|5|6|7|V|8|@]|E|@]|F|$]]]|M|$]]

in that activity set <code>config changes</code> like below
<pre><code> android:configChanges=&quot;orientation|screenSize|keyboardHidden&quot;
</code></pre>

In my Android application, when I rotate the device (slide out the keyboard) then my <code>Activity</code> is restarted (<code>onCreate</code> is called). Now, this is probably how it's supposed to be, but I do a lot of initial setting up in the <code>onCreate</code> method, so I need either:

<ol>
<li>Put all the initial setting up in another function so it's not all lost on device rotation or</li>
<li>Make it so <code>onCreate</code> is not called again and the layout just adjusts or</li>
<li>Limit the app to just portrait so that <code>onCreate</code> is not called.</li>
</ol>

Activity restart on rotation Android

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

在我的Android应用程序中，当我旋转设备(从键盘上滑出)时，我的Activity被重新启动(onCreate被调用)。现在，可能是这样的，但是我在onCreate方法中做了很多初始设置，所以我需要：将所有初始设置放在另一个函数中，这样就不会在设备旋转或使其不再调用onCreate，并且布局只是调整或限制应用程序仅仅...

问循环启动活动，Android
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问循环启动活动，AndroidEN