Updated Android readme for merge

Removed the instruction about checking out swig branch, the
code will be on master.

Removed the onboarding instructions instead it points people to
the root level README.

Changed the header underline style I had the header style
reverse of what it should be for markdown.

Change-Id: I761185b502db6704201b1f1de0fbdd1988024e23
Signed-off-by: George Nash <george.nash@intel.com>

port/android/README.md

 IoTivity-Lite Android port
--------------------------------------------------
+=================================================
 
 Getting Started
-=================================================
+-------------------------------------------------
 To use this code you will need the following:
   - git version control system
   - IoTivity-lite
@@ -24,7 +24,6 @@ Checkout IoTivity-lite git project run the following command to get a anonymous
 iotivity-lite.  Checkout the SWIG branch.
 
     git clone https://gerrit.iotivity.org/gerrit/iotivity-lite
-    git checkout -t origin/swig
 
 ### Android SDK tools
 Download the [Android SDK command line tools](https://developer.android.com/studio#downloads)
@@ -73,7 +72,7 @@ Developers wishing to use Android Studio can find details here:
 [Android Studio](https://developer.android.com/studio)
 
 Building IoTivity-Lite libraries
-=================================================
+-------------------------------------------------
 To build for Android cd to
 
     cd <iotivity-lite>/android/port
@@ -100,7 +99,7 @@ If developing your own project you may need to manually copy the libraries from
 by your project.
 
 Building and Running Samples
-=================================================
+-------------------------------------------------
 All samples have the default out of the box behavior of IoTivity-Lite which means they are are not
 onboarded or provisioned.  The default security will prevent the samples from communicating with
 one another till onboarding and provisioning has been completed.  See the following section
@@ -116,7 +115,6 @@ example:
 
     export ANDROID_HOME=~/Android/sdk
 
-
 To resolve any proxy issues reference [gradle user guide for proxy](https://docs.gradle.org/current/userguide/build_environment.html#sec:accessing_the_web_via_a_proxy)
 
 The server sample is in `android_simple_server/SimpleServer`.  To build and install the sample
@@ -147,97 +145,16 @@ To install
     cd app/build/outputs/apk
     adb install app-armeabi-debug.apk
 
-Onboarding and Provisioning
-=================================================
-### Runing the onboarding tool
-
-At this time there are three versions of the onboarding tool.  The command line C version, the
-command line Java version, and the GUI Android version. Both command line versions are identical.
-It does not matter which version of the onboarding tool is used.
-
-The C version of the onboarding tool can be found in `<iotivity-lite>/port/linux` see Linux build
-instructions.
-
-A Java version of the onboarding-tool can be found in `<iotivity-lite>/swig/apps/java_onboarding_tool`
-
-Assuming you have already followed the `Building for Linux` or `Building for Windows` build
-instructions the following commands can be used to build and run the Java version of the onboarding
-tool.
-
-Linux:
-
-    build-onboarding-tool-lite.sh
-    run-onboarding-tool-lite.sh
-
-Windows
-
-    sh build-onboarding-tool-lite.sh
-    run-onboarding-tool-lite.cmd
-
 The Android version of the onboarding tool can be found in
 `<iotivity-lite>/swig/apps/oc/android_on_boarding_tool`
 
 It is built and installed using the same instructions as other Android samples documented above.
 
-### Simple Step-by-Step guide for onboarding and provisioning
-
-This guide assumes you are starting one discoverable device at a time. Multiple devices can be
-discovered and onboarded at the same time however it becomes the responsibility of the user to
-figure out which UUID belongs to which device.
-
-Once you have successfully onboarded the samples the first time using the following step-by-step
-options feel free to RESET the devices and play around with different provisioning options.
-
-The below steps use the command line version of the onboarding tool. The steps for the Android
-onboarding tool is very similar but is not described here.
-
-### (Step 1) Onboard and Provision the Server
-
-There are multiple methods to onboard and provision server and client samples.  Below is given one
-of the many possible ways the this could be done.
-
- - start the server sample
- - start onboarding tool it will print a menu with many option
- - Type `1` **Enter** to _Discover un-owned devices_
- - Type `8` **Enter** to _Take ownership of device_
-   - Type `0` **Enter**. If you have multiple unowned devices you will have to select the correct
-     device from the list.
- - Type `4` **Enter** to _Discover owned devices_ the device you just took ownership of should be
-   listed.
- - Type `13` **Enter** to _Provision ACE2_. There are many ways to properly provision the device.
-   This will give instruction for using wildcard provisioning.
-   - Type `0` **Enter**. If you have multiple unowned devices you will have to select the correct
-     device from the list.
-   - Type `1` **Enter** for an _auth-crypt_ ACE
-   - Type `1` **Enter** in response to `Enter number of resources in this ACE:`
-   - Type `0` **Enter** in response to `Have resource href? [0-No, 1-Yes]:`
-   - Type `1` **Enter** in response to `Set wildcard resource? [0-No, 1-Yes]:`
-   - Type `2` **Enter** to select the `[2]: All discoverable resources` option
-   - Type `0` **Enter** in response to `Enter number of resource types [0-None]:`
-   - Type `0` **Enter** in response to `Enter number of interfaces [0-None]`
-   - Type `0` **Enter** for CREATE, `1` **Enter** for RETRIEVE, `1` **Enter** for UPDATE, `0`
-     **Enter** for DELETE, and `1` **Enter** for NOTIFY.
-   - `Successfully issued request to provision ACE` should be printed on the screen upon success
-
-### (Step 2) Onboard the client
- - start the client sample
- - Type `1` **Enter** to _Discover un-owned devices_
- - Type `8` **Enter** to _Take ownership of device_
-   - Type `0` **Enter**. If you have multiple unowned devices you will have to select the correct
-     device from the list.
-  - Type `2` **Enter** to _Discover owned devices_ the server and client should be listed
-
-### (Step 3) Pair Server and Client
-  - Type `12` **Enter** to _Provision pair-wise credentials_
-  - Type `0` **Enter** `1` **Enter** to pair the client and server. If you have multiple owned
-    devices you will have to select the correct devices from the list.
-
-### (Step 4) Restart and Test
-The samples should be onboarded and provisioned. Restart the server and then the client they should
-discover each other and run without difficulty.
+See the Simple Step-by-Step guide for onboarding and provisioning section found in the root level
+README for step-by-step instructions to onboard and test the samples.
 
 Building Custom Android Applications
-=================================================
+-------------------------------------------------
 These libraries and examples were built with Android API 23.  When creating a new Android project you
 can choose the API level.  In building these examples, the native code libraries were copied to specific
 directories in the project.  The project structure is:
@@ -278,7 +195,7 @@ This structure is reflected in the app `build.gradle` file:
             }
         }
     }
-    
+
     dependencies {
         compile fileTree(dir: 'libs', include: ['*.jar'])
         .
@@ -291,25 +208,25 @@ To allow these example applications to work, permissions had to be granted in th
 
 ```
     <manifest ...>
-    
+
         <uses-permission android:name="android.permission.INTERNET"/>
         <uses-permission android:name="android.permission.ACCESS_WIFI_STATE"/>
         <uses-permission android:name="android.permission.CHANGE_WIFI_STATE"/>
         <uses-permission android:name="android.permission.CHANGE_WIFI_MULTICAST_STATE"/>
         <uses-permission android:name="android.permission.ACCESS_NETWORK_STATE"/>
         <uses-permission android:name="android.permission.CHANGE_NETWORK_STATE"/>
-        
+
         <application
             .
             .
             .
         </application>
-    
+
     </manifest>
 ```
 
 Send Feedback
-=================================================
+-------------------------------------------------
 Questions
 [IoTivity-Lite Developer Mailing List](https://iotivity-dev@lists.iotivity.org)