Bluetooth: Fix to avoid crash during message listing due to disconnect

A case, where message listing is going on and user does explicitly
disconnect. As mInterrupted is not set, so clientThread waits forever
after completing existing MAS request. Hence setting mInterrupted while
disconnecting MAS session to solve this crash.

Change-Id: Icdbaf70e917e139bcd2e63544b315fde346f6c2f
CRs-fixed: 914961
diff --git a/src/android/bluetooth/client/map/BluetoothMasObexClientSession.java b/src/android/bluetooth/client/map/BluetoothMasObexClientSession.java
index 025bd7a..37f758c 100644
--- a/src/android/bluetooth/client/map/BluetoothMasObexClientSession.java
+++ b/src/android/bluetooth/client/map/BluetoothMasObexClientSession.java
@@ -154,6 +154,12 @@
 
             return true;
         }
+
+        private void shutdown() {
+            Log.w(TAG, "shutdown ");
+            mInterrupted = true;
+            interrupt();
+        }
     }
 
     public BluetoothMasObexClientSession(ObexTransport transport, Handler handler) {
@@ -171,7 +177,7 @@
 
     public void stop() {
         if (mClientThread != null) {
-            mClientThread.interrupt();
+            mClientThread.shutdown();
 
             (new Thread() {
                 @Override