Xperia Go Bluetooth SPP (serial) pin loop problem with JB

[meta96]

Funny, the Bluetooth SPP (serial) pin loop bug is still not fix in the new JB update. Congratulations Sony developers! 6 month begging for nothing. Great support, great skills. Bravo. That means no fun with sony xperia, arduino and common BT devices like: https://www.google.at/search?q=HC-06+bluetooth&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:de:official&cl...

[Rickard]

Sorry to hear that you're still having problems. We did forward this as feedback but checking supported services on the phone from a computer it seems SPP is still not listed as a supported profile.

I searched a bit and it seems to be possible to create a SPP using an app but that will give this problem in certain Android versions but looking at Stackoverflow there seems to be some workarounds you can do in the app that's creating the port.

[someDeveloper]

This is a known bug that hit some manufacturers in 4.0, unfortunately Sony didn't fix it for 4.1.

The workaround is to use the createInsecureRfcommSocketToServiceRecord and just give up on the correct createRfcommSocketToServiceRecord call.

[meta96]

Dear someDeveloper, thanx for your answer. I will try, if the devs of my sports tracker app change their code for the use of heart-rate belts ( xperia go > outdoor > sport ). I was wondering because, some people (me too) pointed to this "well known bug" (also to the google developer page) and the proper firmware fix for month ... but if SPP is not listed, then it is not listed, i get it.

[someDeveloper]

SPP will not be listed as supported by the phone because it does not have any application to work as a Serial Port Profile interface (SPP) when pairing the phone with a computer.

SPP has been part of BlueTooth for a long time and all Android phones should support it, a lot of peripherals use SPP for data transfer to the phone.

Unfortunately Google has hired the worst developers ever to handle SPP and Bluetooth and you will find Bluetooth bugs In almost all versions of android, to which each manufacturer then ads a couple of extra bugs, you know just for the fun of it.

Depending on Android version, manufacturer and phone model you will run into various bugs such as:

Reconnect fails.

Adapter getting stuck turning off.

Adapter getting stuck turning on.

Adapter refuses to turn on.

Pin request loop on secure connections.

Phone reboots after to many connect attempts.

Adapter refuses to connect to anything.

Random disconnects.

[meta96]

Thanks alot, but .

The change of the call methode fixed the pinloop Problem, but now i see some

"Phone reboots after to many some attempts"

Sony, pleaze fix your BT stack ...

[someDeveloper]

Are you seing this on the Xperia GO?

I know this is a bug on pre 3.0 devices, but I have not yet found it on 4.0 devices, usually the BT stack just dies, requiring a reboot to get it back online.

And yes there is a workaround to fix the to many connect attempts bug on devices with an android version below 3.0. I had to use the same workaround on the GO to prevent random and undocumented lockups in 4.1.2.

Do you have a link to where this talk is going on?

[glsarto]

I have random disconnects from my car, could it be related to this issue?

I can only restart the phone to be able to use BT again, however, in 3-15min it will disconnect again.

I don't like having to fumble with the phone while driving...

[someDeveloper]

No, you will not be able to connect when you hit this bug, you will just experience an andless loop of pairing PIN code boxes.

[meta96]

@someDeveloper ... sorry, can't help you on this topic. I ve just asked the devolper of a special app, to test your suggestion. And it works fine, but i had these two reboots. A reboot in my case is more dramatically, so ... but maybe it was something else ... but thanks for the glimmer of hope ...

... btw, new firmware .100 is out, maybe sony has adressed this month old BT bug, would be silly if not ...