ansaurus

Question

Problem with bluetooth on android 2.1 (samsung spica i5700) where pairing works but connection does not work

Answer 1

A:

I got the same problem using an OBD-II Bluetooth connector... I can pair, but can not connect. It seems that is a stack problem. I'm using XXJD1 firmware on the I5700.

Shadowbr 2010-04-26 21:28:41

Answer 2

+3 A:

I got this information from the gps-sport forum. Not sure what to do with it though...

See also http://www.gps-sport.net/forums/thread/1532-0/Keine-Sprachausgabe-auf-HTC-Desire

Cross posting this entry from the software category. The thread over there deals with the Zephyr HxM as a secondary issue - meaning it mightn't be easy to find...

24.04.2010 16:47:05 UTC geändert am 24.04.2010 17:03:03 UTC

A fix to the bluetooth connection problem

Hi

If this problem still is not resolved, the code below describes how to make the connection work with Android 2.1 (Tested on HTC Desire). Just replace "00:07:80:89:EE:EB" with the MAC of your HXM to make it connect. After the connection is successful, a regular method with input = socket.getInputStream() can be used.

BluetoothDevice hxm = BluetoothAdapter.getDefaultAdapter().getRemoteDevice("00:07:80:89:EE:EB");
Method m = hxm.getClass().getMethod("createRfcommSocket", new Class[]{int.class});
socket = (BluetoothSocket)m.invoke(hxm, Integer.valueOf(1));
socket.connect();

Hope the fix will be out very soon =)

Best regards Espen S. Nygaard

Ciaran 2010-04-27 14:39:45

I tried this with my i5700 and this little experiment ended with the following error in the LogCat: "wrp_sock_create: socket create failed (Permission denied)". (My application requested both BLUETOOTH and BLUETOOTH_ADMIN permissions, so that shouldn't be a problem.)

Kalmi 2010-07-13 19:52:10

I should also mention that I'm unable to create a working Bluetooth SPP connection on this phone. I have tried quite a few ways...

Kalmi 2010-07-13 19:53:43

Probably the same issue: http://groups.google.com/group/android-developers/browse_thread/thread/a705aa4b8f865cc1

Kalmi 2010-07-13 19:54:22

Answer 3

A:

Just for recordkeeping, here are the logcat traces from the small python application which I wrote to produce the problem, as well as from the Run.GPS app:

pastebin.org/191806 - trace from my python app
pastebin.org/191824 - source of my python app
pastebin.org/191830 - trace from my Run.GPS

Ciaran 2010-04-29 11:16:21

Answer 4

A:

Just saw this in the logcat

V/BluetoothEventRedirector(21741): Received android.bleutooth.device.action.UUID

I assume that android.*bleu*tooth (i.e. misspelled android.bluetooth) is a string which is outputted as a message and thus has no effect on the code. At least, I would hope so...

Ciaran 2010-04-30 14:35:30

Answer 5

A:

This thread over at Google Groups (android-developers) is also interesting: ' Is Google working on the Bluetooth bug? Any estimated date of completion? '

------ VERSION INFO ------ currenttime=Sat May 1 21:31:48 CEST 2010 kernel.version=Linux version 2.6.29 (root@SE-S611) (gcc version 4.3.1 (for S3C64XX Samsung Electronics AP Development Team) ) #2 Sat Mar 13 02:28:48 KST 2010

kernel.cmdline=# begin build properties

autogenerated by buildinfo.sh

ro.build.id=ECLAIR ro.build.display.id=ECLAIR.XXJCB ro.build.version.incremental=XXJCB ro.build.version.sdk=7 ro.build.version.codename=REL ro.build.version.release=2.1-update1 ro.build.date=2010. 03. 13. (토) 02:07:55 KST ro.build.date.utc=1268413675 ro.build.type=user ro.build.user=root ro.build.host=SE-S611 ro.build.tags=ota-rel-keys,release-keys ro.product.model=GT-I5700 ro.product.brand=Samsung ro.product.name=GT-I5700 ro.product.device=GT-I5700 ro.product.board=GT-I5700 ro.product.cpu.abi=armeabi ro.product.manufacturer=Samsung ro.product.locale.language=en ro.product.locale.region=GB ro.wifi.channels= ro.board.platform=s3c6410

ro.build.product is obsolete; use ro.product.device

ro.build.product=GT-I5700

Do not try to parse ro.build.description or .fingerprint

ro.build.description=GT-I5700-user 2.1-update1 ECLAIR XXJCB ota-rel- keys,release-keys ro.build.fingerprint=Samsung/GT-I5700/GT-I5700/GT-I5700:2.1-update1/ ECLAIR/XXJCB:user/ota-rel-keys,release-keys

Samsung Specific Properties

ro.build.PDA=I570EXXJCB ro.build.Phone=I570EXXJCB ro.build.HW=REV 0.1 ro.build.RFCallDate=2009.02.25 ro.build.hidden_ver=I570EXXJCB ro.build.changelist=193516 ro.build.FUSDLMode=Change ro.build.SupportFUS=TRUE ro.build.CGMM=GT-I5700 ro.build.GMM=GT-I5700

end build properties

#

system.prop for spica

Ciaran 2010-05-02 08:58:17

Answer 6

A:

This logcat trace is also quite interesting. This was done using the python script available on pastebin.com (see previous post). The difference is that this time I manually unpaired the bluetooth device (HxM) in the Spica bluetooth settings first. When I ran the Python script, it first asked me to allow bluetooth access. Then, I got the message that I needed to pair the device. Once I paired the device (entered '1234' in the pop-up dialog), this logcat trace came about....

I/DTUN_CLNT( 7704):     Client calling DTUN_METHOD_DM_PIN_REPLY (id 9)
I/        ( 7691): DTUN_ReceiveCtrlMsg: [DTUN] Received message [BTLIF_DTUN_METHOD_CALL] 4354
I/        ( 7691): handle_method_call: handle_method_call :: received DTUN_METHOD_DM_PIN_REPLY (id 9), len 23
W/InputManagerService( 1905): Starting input on non-focused client com.android.internal.view.IInputMethodClient$Stub$Proxy@43f16da0 (uid=1000 pid=7742)
W/IInputConnectionWrapper( 7742): showStatusIcon on inactive InputConnection
I/BTL-IFS ( 7691): send_ctrl_msg: [BTL_IFS CTRL] send BTLIF_DTUN_SIGNAL_EVT (CTRL) 29 pbytes (hdl 10)
I/DTUN_CLNT( 7704): dtun-rx signal [DTUN_SIG_DM_AUTH_COMP] (id 46) len 31
I/DTUN_HCID( 7704):     ***  sig_auth_comp status: 0 ***
I/DTUN_HCID( 7704): 
I/SECURITY( 7704): link_key_notify (sba=43:25:34:74:04:A3, dba=00:07:80:88:F5:AD, type=0)
D/ADAPTER ( 7704): adapter_get_device(00:07:80:88:F5:AD)
E/DBUS-HCI( 7704): ...get_auth_requirements unimplemented
D/ADAPTER ( 7704): adapter_get_device(00:07:80:88:F5:AD)
I/DBUS-HCI( 7704): hcid_dbus_conn_complete: adding device = 0xfbb0 handle = 256
I/ADAPTER ( 7704): adapter_add_connection: adding device = 0xfbb0 handle = 256
I/BluetoothEventLoop.cpp( 1905): event_filter: Received signal org.bluez.Device:PropertyChanged from /org/bluez/7704/hci0/dev_00_07_80_88_F5_AD
D/BluetoothEventLoop( 1905): Device property changed:00:07:80:88:F5:ADproperty:Connected
I/BluetoothService( 1905): ACL connected, mAclLinkCount = 1
D/BluetoothA2dpService( 1905): Received intent Intent { act=android.bluetooth.device.action.ACL_CONNECTED (has extras) }
D/BluetoothA2dpService( 1905): [KJH] device - 00:07:80:88:F5:AD, SinkPriority - 0, isSinkDevice - false, aclCount - 1
I/DBUS-HCI( 7704): hcid_dbus_bonding_process_complete: status=00
D/ADAPTER ( 7704): adapter_get_device(00:07:80:88:F5:AD)
D/DEVICE  ( 7704): setting timer for reverse service discovery
I/BluetoothEventLoop.cpp( 1905): event_filter: Received signal org.bluez.Device:PropertyChanged from /org/bluez/7704/hci0/dev_00_07_80_88_F5_AD
D/BluetoothEventLoop( 1905): Device property changed:00:07:80:88:F5:ADproperty:Paired
D/BluetoothService( 1905): ***** 00:07:80:88:F5:AD bond state 11 -> 12 (0)
D/BT HSHFP( 1961): Received intent Intent { act=android.bluetooth.device.action.BOND_STATE_CHANGED (has extras) }
V/BluetoothEventRedirector( 7742): Received android.bluetooth.device.action.BOND_STATE_CHANGED
D/BluetoothA2dpService( 1905): Received intent Intent { act=android.bluetooth.device.action.BOND_STATE_CHANGED (has extras) }
D/BluetoothA2dpService( 1905): *******************************************************
I/BluetoothA2dpService( 1905): Class of Bonded Device : 0x1f00
I/DBUS-HCI( 7704): hcid_dbus_bonding_process_complete: status=00
D/ADAPTER ( 7704): adapter_get_device(00:07:80:88:F5:AD)
I/DBUS-HCI( 7704): hcid_dbus_bonding_process_complete: no pending auth request
D/BluetoothA2dpService( 1905): Major Class of Bonded Device : ???
D/BluetoothA2dpService( 1905): Minor Class of Bonded Device : ???
W/BTLD    ( 7691): ccb timer ticks: 0
D/BluetoothA2dpService( 1905): *******************************************************
W/BTLD    ( 7691): info:x0
I/BTL-IFS ( 7691): send_ctrl_msg: [BTL_IFS CTRL] send BTLIF_DTUN_SIGNAL_EVT (CTRL) 10 pbytes (hdl 10)
I/DTUN_CLNT( 7704): dtun-rx signal [DTUN_SIG_DM_LINK_UP] (id 49) len 12
D/DTUN_HCID( 7704):             dtun_dm_sig_link_up()
I/DTUN_HCID( 7704): dtun_dm_sig_link_up: dummy_handle = 257
D/ADAPTER ( 7704): adapter_get_device(00:07:80:88:F5:AD)
I/DBUS-HCI( 7704): hcid_dbus_conn_complete: adding device = 0xfbb0 handle = 257
E/ADAPTER ( 7704): Unable to add connection 257
D/dalvikvm( 7720): GC freed 63 objects / 17040 bytes in 352ms
D/BT HSHFP( 1961): Loaded priority 00:07:80:88:F5:AD = 0
I/dalvikvm-heap( 7720): Grow heap (frag case) to 5.849MB for 1060016-byte allocation
D/dalvikvm( 7720): GC freed 3 objects / 1060104 bytes in 81ms
D/DTUN_HCID( 7704):             dtun_client_get_remote_services()
I/DTUN_HCID( 7704): dtun_client_get_remote_services: Get remote services on 
I/DTUN_CLNT( 7704):     Client calling DTUN_METHOD_DM_GET_REMOTE_SERVICES (id 5)
I/        ( 7691): DTUN_ReceiveCtrlMsg: [DTUN] Received message [BTLIF_DTUN_METHOD_CALL] 4354
I/        ( 7691): handle_method_call: handle_method_call :: received DTUN_METHOD_DM_GET_REMOTE_SERVICES (id 5), len 6
I/BTL-IFS ( 7691): send_ctrl_msg: [BTL_IFS CTRL] send BTLIF_DTUN_SIGNAL_EVT (CTRL) 14 pbytes (hdl 10)
I/DTUN_CLNT( 7704): dtun-rx signal [DTUN_SIG_DM_RMT_SERVICES] (id 43) len 16
I/DTUN_HCID( 7704): dtun_dm_sig_rmt_services: success=0, service=00250000
E/DTUN_HCID( 7704): No device pointer found for peer! Ignore Error = true. Ignoring error...
I//system/bin/btld( 7690):              btapp_dm_GetRemoteServices()
W/BTLD    ( 7691): process_service_search_attr_rsp
I/BTL-IFS ( 7691): send_ctrl_msg: [BTL_IFS CTRL] send BTLIF_DTUN_SIGNAL_EVT (CTRL) 13 pbytes (hdl 10)
I/DTUN_CLNT( 7704): dtun-rx signal [DTUN_SIG_DM_RMT_SERVICE_CHANNEL] (id 42) len 15
I/DTUN_HCID( 7704): dtun_dm_sig_rmt_service_channel: success=0, service=00000000
E/DTUN_HCID( 7704): discovery unsuccessful!
I/BTL-IFS ( 7691): send_ctrl_msg: [BTL_IFS CTRL] send BTLIF_DTUN_SIGNAL_EVT (CTRL) 11 pbytes (hdl 10)
I/DTUN_CLNT( 7704): dtun-rx signal [DTUN_SIG_DM_LINK_DOWN] (id 47) len 13
I/DTUN_HCID( 7704):     *** sig_link_down :: device = [0xfbb0] handle = [256] addr = [00:07:80:88:F5:AD] reason = [16] ***
I/DTUN_HCID( 7704): 
I/BluetoothEventLoop.cpp( 1905): event_filter: Received signal org.bluez.Device:PropertyChanged from /org/bluez/7704/hci0/dev_00_07_80_88_F5_AD
D/BluetoothEventLoop( 1905): Device property changed:00:07:80:88:F5:ADproperty:Disconnected
I/BluetoothService( 1905): ACL disconnected, mAclLinkCount = 0
D/BluetoothA2dpService( 1905): Received intent Intent { act=android.bluetooth.device.action.ACL_DISCONNECTED (has extras) }
D/BT HSHFP( 1961): Received intent Intent { act=android.bluetooth.device.action.ACL_DISCONNECTED (has extras) }
I/BT HSHFP( 1961): ACL disconnected

Ciaran 2010-05-03 16:05:46

Answer 7

A:

I found this exact problem happens when one of the devices has the Bluetooth turned off.

Jaime Botero 2010-05-04 17:01:48

In my case, bluetooth is definitely turned on, on both devices. I am sure of this because I can also connect the heartrate monitor (Zephyr HxM) to my computer and read the data sent over serial.I always disconnect the device on my computer before trying over the Android phone, in case of interference etc.

Ciaran 2010-05-05 10:48:34

Answer 8

A:

Hello, Any news on this ? I tried the workaround proposed by Espen S. Nygaard but it still fails on a Samsung Spica.

Below an excerpt of the LogCat of where I think it fails.

05-13 18:16:40.359: DEBUG/BluetoothSocket.cpp(4375): initSocketFromFdNative
05-13 18:16:40.394: DEBUG/BluetoothSocket(4375): connect
05-13 18:16:40.394: DEBUG/BluetoothSocket.cpp(4375): connectNative
05-13 18:16:40.394: DEBUG/BluetoothSocket.cpp(4375): ...connect(33, RFCOMM) = -1 (errno 22)
05-13 18:16:40.414: WARN/System.err(4375): java.io.IOException: Invalid argument
05-13 18:16:40.449: WARN/System.err(4375):     at android.bluetooth.BluetoothSocket.connectNative(Native Method)
05-13 18:16:40.449: WARN/System.err(4375):     at android.bluetooth.BluetoothSocket.connect(BluetoothSocket.java:187)
05-13 18:16:40.449: WARN/System.err(4375):     at com.payd.android.Payd.onActivityResult(Payd.java:203)
05-13 18:16:40.449: WARN/System.err(4375):     at android.app.Activity.dispatchActivityResult(Activity.java:3828)
enter code here

Edwin 2010-05-13 16:33:19

Answer 9

A:

https://android.git.kernel.org/?p=platform/system/wlan/broadcom.git;a=commit;h=e10efcc0c020caa486fa9d8cd05c986fd86f7c44

may solve this. The commit log is: "Add firmware for BCM4325"

If there was no firmware in the kernel to support this before, then it obviously would cause problems.

I guess I'll have to see if I can build android from source and install it on my phone :-(

Ciaran 2010-05-17 10:05:35

False alarm. That commit relates to the wlan part of the chip. But the Broadcom contact has forwarded details of the bug in the bluetooth driver to the bluetooth team at Broadcom

Ciaran 2010-05-17 21:44:33

Answer 10

A:

Ok, solved it.

The solution is to update the firmware on the phone. I now have: PDA: I570EXXJE1 PHONE: i570EXXJD1 CSC: I570EOXEJE1

and bluetooth spp worked 'out of the box'.

Look at http://samsung-firmwares.com for both the latest firmware as well as programs to flash the phone (odin) and details/tutorials.

Ciaran 2010-05-20 07:18:52

ansaurus

tags:

views:

answers: