views:

100

answers:

2

I've been having an issue with data integrity using an RFCOMM socket over Bluetooth in Android. I don't have any issues connecting, but the data I receive is garbled and not the same as the data that is sent. The data is sent by an RS232 device over a Bluetooth adapter, which the phone connects to. There isn't a problem with the adapter as the data is properly received if I connect with a laptop.

My Bluetooth connection is handled based off of the BluetoothChat sample application found at the Android developer site (http://developer.android.com/resources/samples/BluetoothChat/index.html), with no changes. The data being sent is plain text and control characters (which are stripped out before display to the user). The specific problem I have is that some of the text is missing, some of it is repeated, etc. The funny thing is if I connect to a computer with a terminal app and type in there, the data is transmitted fine. Additionally, if I connect to the device using the GetBlue app (http://www.tec-it.com/en/software/data-acquisition/getblue/android-smartphone/Default.aspx) the data is received fine.

So I guess the issue is what does GetBlue possibly do different to handle it's Bluetooth data transfer, or is there another way receive Bluetooth data over an RFCOMM socket on Android?

+1  A: 

Hello!

TEC-IT (http://www.tec-it.com) is the developer of GetBlue. GetBlue is divided into two parts: a) the frontent (user interface) and b) a service which communicates using Bluetooth, TCP/IP or other supported interfaces.

Part b) will be made available for use by 3rd party. This eliminates development efforts and provides a stable / device - independent communication interface. If interested please let us know ([email protected]).

TEC-IT
+1  A: 

The fix for the solution was to create the string in the connected thread, directly after calling read() on the InputStream, and then passing the string back to the main thread for display. For whatever reason, passing the byte array between threads led to significant repetition and data loss.

Modified run() code:

        public void run() {
        byte[] buffer = new byte[256];  // buffer store for the stream
        int bytes; // bytes returned from read()

        // Keep listening to the InputStream until an exception occurs
        while (true) {
            try {
                // Read from the InputStream
                bytes = mmInStream.read(buffer);
                String readMessage = new String(buffer, 0, bytes);
                // Send the obtained bytes to the UI Activity
                mHandler.obtainMessage(MESSAGE_READ, bytes, -1, readMessage)
                        .sendToTarget();
            } catch (IOException e) {
                break;
            }
        }
    }

And the handler reception:

        case MESSAGE_READ:
            // Read in string from message, display to mainText for user
            String readMessage = (String) msg.obj;
            if (msg.arg1 > 0) {
                mainText.append(readMessage);
            }
MortalToaster