Databases
StackOverflow2013
Postsdbo
POConnecting Android device to multiple Bluetooth serial embedded peers
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POConnecting Android device to multiple Bluetooth serial embedded peers
    primarykey
    data
    text
    <p>I'm trying to find a solution for this setup:</p> <p>I have a single Android device, which I would like to connect to multiple serial embedded devices... </p> <p>And here is the thing, using the "Normal" way to retrieve the Bluetooth socket, doesn't work on all devices, and while it does, I can connect to multiple devices, and send and receive data to and from multiple devices. </p> <pre><code>public final synchronized void connect() throws ConnectionException { if (socket != null) throw new IllegalStateException("Error socket is not null!!"); connecting = true; lastException = null; lastPacket = null; lastHeartBeatReceivedAt = 0; log.setLength(0); try { socket = fetchBT_Socket_Normal(); connectToSocket(socket); listenForIncomingSPP_Packets(); connecting = false; return; } catch (Exception e) { socket = null; logError(e); } try { socket = fetchBT_Socket_Workaround(); connectToSocket(socket); listenForIncomingSPP_Packets(); connecting = false; return; } catch (Exception e) { socket = null; logError(e); } connecting = false; if (socket == null) throw new ConnectionException("Error creating RFcomm socket for" + this); } private BluetoothSocket fetchBT_Socket_Normal() throws Exception { /* The getType() is a hex 0xXXXX value agreed between peers --- this is the key (in my case) to multiple connections in the "Normal" way */ String uuid = getType() + "1101-0000-1000-8000-00805F9B34FB"; try { logDebug("Fetching BT RFcomm Socket standard for UUID: " + uuid + "..."); socket = btDevice.createRfcommSocketToServiceRecord(UUID.fromString(uuid)); return socket; } catch (Exception e) { logError(e); throw e; } } private BluetoothSocket fetchBT_Socket_Workaround() throws Exception { Method m; int connectionIndex = 1; try { logDebug("Fetching BT RFcomm Socket workaround index " + connectionIndex + "..."); m = btDevice.getClass().getMethod("createRfcommSocket", new Class[]{int.class}); socket = (BluetoothSocket) m.invoke(btDevice, connectionIndex); return socket; } catch (Exception e1) { logError(e1); throw e1; } } private void connectToSocket(BluetoothSocket socket) throws ConnectionException { try { socket.connect(); } catch (IOException e) { try { socket.close(); } catch (IOException e1) { logError("Error while closing socket", e1); } finally { socket = null; } throw new ConnectionException("Error connecting to socket with" + this, e); } } </code></pre> <p>And here is the thing, while on phones which the "Normal" way doesn't work, the "Workaround" way provides a solution for a single connection. I've <a href="https://stackoverflow.com/questions/4468658/android-bluetooth-api-connect-to-multiple-devices"><strong>searched</strong></a> <a href="https://stackoverflow.com/questions/6760102/connecting-to-a-already-paired-bluetooth-device"><strong>far</strong></a> <a href="http://groups.google.com/group/android-developers/browse_thread/thread/69d7810f6ef9bb7d?pli=1" rel="nofollow noreferrer"><strong>and</strong></a> <a href="http://code.google.com/p/android/issues/detail?id=5427" rel="nofollow noreferrer"><strong>wide</strong></a>, but came up with zip.</p> <p>The problem with the workaround is mentioned in the last link, both connection uses the same port, which in my case, causes a block, where both of the embedded devices can actually send data, that is not been processed on the Android, while both embedded devices can receive data sent from the Android.</p> <p>Did anyone handle this before?</p> <p>There is a bit more reference <a href="http://code.google.com/p/apps-for-android/source/browse/BTClickLinkCompete/src/net/clc/bt/ConnectionService.java" rel="nofollow noreferrer">here</a>, </p> <p><strong>UPDATE:</strong></p> <p>Following <a href="http://code.google.com/p/android/issues/detail?id=5427" rel="nofollow noreferrer">this</a> (that I posted earlier) I wanted to give the mPort a chance, and perhaps to see other port indices, and how other devices manage them, and I found out the the fields in the BluetoothSocket object are different while it is the same class FQN in both cases:</p> <p>Detils from an HTC Vivid 2.3.4, uses the "workaround" Technic:</p> <p>The Socket class type is: [<strong>android.bluetooth.BluetoothSocket</strong>]</p> <pre><code>mSocket BluetoothSocket (id=830008629928) EADDRINUSE 98 EBADFD 77 MAX_RFCOMM_CHANNEL 30 TAG "BluetoothSocket" (id=830002722432) TYPE_L2CAP 3 TYPE_RFCOMM 1 TYPE_SCO 2 mAddress "64:9C:8E:DC:56:9A" (id=830008516328) mAuth true mClosed false mClosing AtomicBoolean (id=830007851600) mDevice BluetoothDevice (id=830007854256) mEncrypt true mInputStream BluetoothInputStream (id=830008688856) mLock ReentrantReadWriteLock (id=830008629992) mOutputStream BluetoothOutputStream (id=830008430536) **mPort 1** mSdp null mSocketData 3923880 mType 1 </code></pre> <p>Detils from an LG-P925 2.2.2, uses the "normal" Technic:</p> <p>The Socket class type is: [<strong>android.bluetooth.BluetoothSocket</strong>]</p> <pre><code>mSocket BluetoothSocket (id=830105532880) EADDRINUSE 98 EBADFD 77 MAX_RFCOMM_CHANNEL 30 TAG "BluetoothSocket" (id=830002668088) TYPE_L2CAP 3 TYPE_RFCOMM 1 TYPE_SCO 2 mAccepted false mAddress "64:9C:8E:B9:3F:77" (id=830105544600) mAuth true mClosed false mConnected ConditionVariable (id=830105533144) mDevice BluetoothDevice (id=830105349488) mEncrypt true mInputStream BluetoothInputStream (id=830105532952) mLock ReentrantReadWriteLock (id=830105532984) mOutputStream BluetoothOutputStream (id=830105532968) mPortName "" (id=830002606256) mSocketData 0 mSppPort BluetoothSppPort (id=830105533160) mType 1 mUuid ParcelUuid (id=830105714176) </code></pre> <p>Anyone have some insight... </p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USTacB0sS
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    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. POConnecting Android device to multiple Bluetooth serial embedded peers
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POConnecting Android device to multiple Bluetooth serial embedded peers
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POConnecting Android device to multiple Bluetooth serial embedded peers
      1. USyugi
      1. VTFavorite
    1. COI've tried all sort of random port numbers, 1-5, which none worked.
      singulars
      1. POConnecting Android device to multiple Bluetooth serial embedded peers
      1. USTacB0sS
    2. COI've also mapped a couple of other issues I've encountered working on the Android Bluetooth feature here: http://www.blogger.com/blogger.g?blogID=1531299241496277633#allposts/postNum=0
      singulars
      1. POConnecting Android device to multiple Bluetooth serial embedded peers
      1. USTacB0sS
 

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