BT-Rfcomm fixed with offcial 2.2?

[Guest Maj0r]

Hello,

does anyone know if communication over bluetooth rfcomm-socket will work with the official Dell-ROM 2.2 (Streak acting as Client)?

I tried with original Dell 1.6, 2.1 and with all Stephen Hyde ROMs, I think the bluetooth stack is buggy.

Pairing works but connecting via socket always ends with "conncetion refused".

I am trying to connect to a bluetooth printer, but connecting to a bluetooth dongle fails the same way.

Motorola Milestone works fine with the printer as well as with the bluetooth dongle...

Best regards,

Torsten

[Guest adzman808]

sorry but i haven't got a clue...

on steve's build my bt headset works for voice & music 100% with play/pause skip +/- vol +/- & on call vol +/- & answer hang up on a range of about 10meters

do you have good bt function with voice & music but not printing? in which case maybe it's a generic bt stack issue or if your music & voice isn't as good as above then perhaps its an issue with your device

sorry i cant be more helpful

[Guest Maj0r]

I have no problems with "standard"-bluetooth comunications, my headset and car-audio work very well.

The problem is serial-rfcomm over bluetooth, initiated with my own code.

I have to connect to a server-socket and send controls-codes via outputstream, but initiating socket#connect fails with "connection refused".

I think Dell did not put much effort into their bluetooth-stack, they only implemented the mostly used bluetooth-functions very well.

[Guest moneytoo]

Bluetooth apps I coded work well on Streak with Android 2.1 (both master/slave connections). I'm planning to test it on 2.2.

If someone has buggy BT drivers it's Samsung.

[Guest Maj0r]

As I said, no problems with standard bluetooth functionality, did you use serial rfcomm?

This is the code which does not work on Streak but on Motorola Milestone:

UUID	uuid = UUID.fromString("00001101-0000-1000-8000-00805F9B34FB"); // special uuid for serial rfcomm

BluetoothDevice device = ... // my printer or bt-dongle

BluetoothSocket	mmSocket = device.createRfcommSocketToServiceRecord(uuid);

mmSocket.connect(); // --> "connection refused"

Edited November 21, 2010 by Maj0r

[Guest moneytoo]

Sometimes the SDP search may fail. Make sure the device are paired (or unpair them and wait for pairing dialog). You should also try it more times.

If it doesn't work, you can always connect directly to selected RFCOMM channel (http://code.google.com/p/android/issues/detail?id=5427).

[Guest Maj0r]

Pairing works.

I tried it (as you mentioned) via the settings-dialog as well as with the popup pairing dialog.

I know the reflection-way, too, but it does not work either :-(.

Everything already tested, a thousands tries, but did not work one single time.

Did exactly this really work on your Streak-device?

[Guest moneytoo]

I didn't use SPP UUID (0x1101) but different - HFP and others.

Have you tried checking the sdp records directly from Streak (using sdptool)?

[Guest Maj0r]

Yes, rfcomm is shown, but I still have no clue how to connect with the Streak...

The code works on Motorola Milestone every time I try (I do not even have to try twice).

Therefore I am of the opinion that it must be a client issue of the Streak's bluetooth stack :-(.

[Guest moneytoo]

Most often "connection refused" error is because of invalid link keys (on one of these devices).