Manifest File

SQLiteDemo/app/src/main/AndroidManifest.xml 
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
    package="com.example.wenchen.sqlitedemo"
    android:versionCode="1"
    android:versionName="1.0">
  <uses-sdk android:minSdkVersion="10" />
  <application android:icon="@mipmap/ic_launcher"
               android:label="@string/app_name">
    <activity android:name=".TestDatabase"
              android:label="@string/app_name"
              android:configChanges="orientation">
      <intent-filter>
        <action   android:name="android.intent.action.MAIN" />
        <category android:name="android.intent.category.LAUNCHER" />
      </intent-filter>
    </activity>
  </application>
</manifest>
package="com.example.wenchen.sqlitedemo"
The package of this application is com.example.wenchen.sqlitedemo.

<activity android:name=".TestDatabase"
This application has only one activity/interface points to the class: 
   com.example.wenchen.sqlitedemo.TestDatabase
android:configChanges="orientation">
It lists configuration changes that the activity will handle itself. When a configuration change occurs at runtime, the activity is shut down and restarted by default, but declaring a configuration with this attribute will prevent the activity from being restarted. Instead, the activity remains running and its onConfigurationChanged method is called.

android:configChanges="orientation">
The screen orientation has changed—the user has rotated the device. If your application targets API level 13 or higher, then you should also declare the screenSize configuration, because it also changes when a device switches between portrait and landscape orientations.



      Why beat around the bush (equivocate)    
      with words like implies and possible?