Databases
StackOverflow2013
Postsdbo
POAndroid Bluetooth IOException bad file number
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAndroid Bluetooth IOException bad file number
    primarykey
    data
    text
    <p>I have a receive thread listening with the BluetoothServerSocket accept() call. This thread will be killed and restarted by another thread pretty frequently. When it gets the kill signal, it closes the BluetoothServerSocket therefore causing an IOException in accept(), and gets out of the infinite-loop. But occasionally, during these starts and restarts the listenUsingRfcommWithServiceRecord() call will catch a "bad file number" IOException and exit the loop prematurely. I think I may not be shutting down the BT component correctly in kill(?) but haven't figure out anything yet... Could someone give me some pointers?</p> <pre><code>private class ReceiveThread extends Thread { private final static String TAG = "ReceiveThread"; private BluetoothServerSocket mmBtServer; private BluetoothSocket mmBtSocket; public ReceiveThread() { setName(TAG); } public void run() { if(D) Log.d(TAG,"RceiveThread running"); while(true) { try { SetState(SERVICE_STATE.LISTENING); mmBtServer = mBtAdapter.listenUsingRfcommWithServiceRecord(mAppName, mUUID); if(D) Log.d(TAG,"ReceiveThd accepting connection"); mmBtSocket = mmBtServer.accept(); // Close server once socket establishes mmBtServer.close(); if(D) Log.d(TAG, "Connection Established"); SetState(SERVICE_STATE.CONNECTED_BUSY); /** Handle Processing **/ // Close socket mmBtSocket.close(); } catch (IOException e) { SetState(SERVICE_STATE.NOT_CONNECTED); Log.d(TAG,"IOException in ReceiveThread", e); break; } SetState(SERVICE_STATE.CONNECTED_IDLE); } } public void kill() { try { if(mmBtSocket!=null) mmBtSocket.close(); if(mmBtServer!=null) mmBtServer.close(); } catch (IOException e) { Log.d(TAG,"Failure killing ReceiveThread", e); } SetState(SERVICE_STATE.NOT_CONNECTED); } } </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USbroody
    1. USbroody
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POAndroid Bluetooth IOException bad file number
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POAndroid Bluetooth IOException bad file number
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POAndroid Bluetooth IOException bad file number
      1. USTom
      1. VTFavorite
    1. COThe same problem on Samsung Galaxy S. Can't reproduce on other devices. What does it mean?
      singulars
      1. POAndroid Bluetooth IOException bad file number
      1. USSaasha
    2. COGlad you can reproduce. Prolly just means samsung didnt do a very good job integrating bt.
      singulars
      1. POAndroid Bluetooth IOException bad file number
      1. USbroody
    3. COI've seen the same symptom on Galaxy Tab GT-P1000 (the original) with 2.3.3. My app does a bluetoothsocket connect which makes a connection to a remote device, but the connect call never returns and eventually I have to kill the process. On my next run I get the problem you observed. So, the root of the problem is in the connect (for me).
      singulars
      1. POAndroid Bluetooth IOException bad file number
      1. USTom
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload