Gary - thanks for the tip. I will try it out later this week (I'll let
you know how it goes).

Indicator Veritatis - I think most consumer products support pairing
but it is not necessary if you are using Bluetooth as a cable
replacement for RS232. You should be able to establish a connection
without pairing, depending on what you are developing you can then add
security by having password access (encrypted or not) to the device.
This is mainly used in industrial applications.

On Jun 26, 1:17 am, gjs <[email protected]> wrote:
> Hi,
>
> Answering the following in the forum -
>
> -----------------------------------------------------------------------------------------
>
> from    Si
> to      gjs
> date    Sun, Jun 26, 2011 at 5:47 AM
> subject Re:BluetoothSerialPortQuestion
>
> Hi,
>
> Thanks for the reply.
>
> Would you be able to email me an example project?
>
> I am fairly new to Androd development and I am still learning (through
> example code). I have done some basic Java programming but most of my
> software is written in National Instruments LabVIEW (industrial
> machine automation).
>
> Thanks
>
> Simon
>
> -----------------------------------------------------------------------------------------
>
> Hi Simon,
>
> For thebluetoothdevice I am using I simply modified theBlueTooth
> Chat example -
>
> http://developer.android.com/resources/samples/BluetoothChat/index.html
>
> The only change I made was to use 00001101-0000-1000-8000-00805F9B34FB
> (as mentioned) instead of -
>
> private static final UUID MY_UUID_INSECURE =
>         UUID.fromString("8ce255c0-200a-11e0-ac64-0800200c9a66");
>
> - in class BluetoothChatService.
>
> Then start the app & select the INSECURE option with Android menu
> button & connect to the device (after selecting it from device list) ,
> I can then send & receive message from & to the device.
>
> Thebluetoothdevice I am using does not need / cannot accept a
> passkey, it has no user interface and uses the UUID mentioned.
>
> Regards
>
> On Jun 25, 10:37 am, gjs <[email protected]> wrote:
>
> > Hi,
>
> > Yes I have this working correctly in similar scenario you describe
> > with InsecureRfcomm, try creating & connecting an outgoing socket
> > connection to the device and make sure you are using the correct UUID
> > string for the device. eg
>
> > 'Hint: If you are connecting to aBluetoothserialboard then try
> > using the well-known SPP UUID 00001101-0000-1000-8000-00805F9B34FB.
> > However if you are connecting to an Android peer then please generate
> > your own unique UUID.'
>
> >http://developer.android.com/reference/android/bluetooth/BluetoothDev...
>
> > Yes you need 2.3.3 or greater.
>
> > Regards
>
> > On Jun 24, 9:23 pm, Si <[email protected]> wrote:
>
> > > I have done some further trawling around the internet and as far as I
> > > can tell until recently the standard API only supported pairing (with
> > > a passkey).
>
> > > It would appear though that this functionality has been included in
> > > 2.3.3 (http://developer.android.com/sdk/android-2.3.3.html)
>
> > > "Android 2.3.3 adds platform and API support forBluetoothnonsecure
> > > socket connections. This lets applications communicate with simple
> > > devices that may not offer a UI for authentication."
>
> > > Has anybody got any examples that connect to "non-secure" devices that
> > > do not exchange a passkey?

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to