fix: issues

Author: RohitKushvaha01

src/plugins/terminal/src/android/Executor.java

@@ -268,7 +268,6 @@ public boolean execute(String action, JSONArray args, CallbackContext callbackCo
 
                 int port;
                 try (ServerSocket socket = new ServerSocket(0)) {
-                    socket.setReuseAddress(true);
                     port = socket.getLocalPort();
                 }
 

src/plugins/terminal/src/android/ProcessServer.java

@@ -101,12 +101,18 @@ public void onMessage(WebSocket conn, String message) {
 
     @Override
     public void onClose(WebSocket conn, int code, String reason, boolean remote) {
-        // Single point of cleanup for every connection lifecycle ending —
-        // whether closed cleanly, after an error, or by the process exiting.
         try {
             ConnState state = conn.getAttachment();
             if (state != null) state.process.destroy();
-            stop();
         } catch (Exception ignored) {}
+
+        // stop() calls w.join() on every worker thread. If called directly from
+        // onClose (which runs on a WebSocketWorker thread), it deadlocks waiting
+        // for itself to finish. A separate thread sidesteps that entirely.
+        new Thread(() -> {
+            try {
+                stop();
+            } catch (Exception ignored) {}
+        }).start();
     }
 }