1. 首頁
  2. 問答
  3. 在Android 2.1（三星spica i5700）藍牙問題，配對工程，但連接不工作

在Android 2.1（三星spica i5700）藍牙問題，配對工程，但連接不工作

2010-04-18 39 views
4

我有一個三星Spica i5700，我已經更新到Android 2.1。我正在使用名爲Run.GPS的應用程序（http://www.rungps.net）。此應用程序記錄GPS位置，路線，速度，方位等數據。如果用戶擁有Zephyr HxM藍牙心率監視器（「HxM」），也可以記錄心率。在Android 2.1（三星spica i5700）藍牙問題，配對工程，但連接不工作

我可以通過標準藍牙實用程序將HxM與手機配對。系統會提示我輸入PIN，並將設備顯示爲「配對但未連接」。

在Run.GPS應用程序本身，我點擊「連接心率監視器」。大約30秒後超時並且錯誤消息是'無法連接到心率監視器。請嘗試其他設置'。

我用朋友的HTC的Windows Mobile作爲控制裝置，看看是否HXM那裏工作。它的確如此。 Run.GPS應用程序會自動設置波特率（最初爲9600 IIRC，但連接也可以使用更高的波特率），並且可以在各種COM端口以及.Net COM端口之間進行選擇。

我做了我的角宿一的Android一些測試，試圖找出爲什麼藍牙連接不起作用。下面是我通過在Run.GPS應用程序中單擊「連接到心率監視器」時通過adb連接的一些日誌文件。

我會對任何提示感興趣（包括如果我在這裏發佈錯誤的論壇;-)） - 是否有可能在Android等實驗波特率等我仍然不知道是否問題出在Run.GPS應用程序（我已經發布在開發論壇上）或者使用Android 2.1。我查看了另一個應用程序 - Endomondo - 這也是一個運動跟蹤應用程序，它只支持HxM的心率監視器。在那裏，看起來發生了完全相同的錯誤 - 我點擊了「Connect Zephyr HxM」。幾秒鐘後，我看到「正在連接...」狀態，但後來超時到「未連接」狀態。因此，我傾向於尋找Android解決這個問題。

這裏的亞行logcat的輸出，同時試圖連接

./adb logcat | grep Run.GPS 
    D/WYNEX> (11551): Excute :: Run.GPS Trainer UV, (null) 
    E/Run.GPS (11997): Cannot connect to BT device 
    E/Run.GPS (11997): java.io.IOException: Service discovery failed 
    E/Run.GPS (11997): at android.bluetooth.BluetoothSocket$SdpHelper.doSdp(BluetoothSocket.java:374) 
    E/Run.GPS (11997): at android.bluetooth.BluetoothSocket.connect(BluetoothSocket.java:184) 
    E/Run.GPS (11997): at ju.a(Unknown Source) 
    E/Run.GPS (11997): at qk.j(Unknown Source) 
    E/Run.GPS (11997): at fs.c(Unknown Source) 
    E/Run.GPS (11997): at le.a(Unknown Source) 
    E/Run.GPS (11997): at s.b(Unknown Source) 
    E/Run.GPS (11997): at pb.a(Unknown Source) 
    E/Run.GPS (11997): at as.a(Unknown Source) 
    E/Run.GPS (11997): at am.b(Unknown Source) 
    E/Run.GPS (11997): at gf.onTouchEvent(Unknown Source) 
    E/Run.GPS (11997): at android.view.View.dispatchTouchEvent(View.java:3709) 
    E/Run.GPS (11997): at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:884) 
    E/Run.GPS (11997): at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:884) 
    E/Run.GPS (11997): at com.android.internal.policy.impl.PhoneWindow$DecorView.superDispatchTouchEvent(PhoneWindow.java:1665) 
    E/Run.GPS (11997): at com.android.internal.policy.impl.PhoneWindow.superDispatchTouchEvent(PhoneWindow.java:1107) 
    E/Run.GPS (11997): at android.app.Activity.dispatchTouchEvent(Activity.java:2061) 
    E/Run.GPS (11997): at com.android.internal.policy.impl.PhoneWindow$DecorView.dispatchTouchEvent(PhoneWindow.java:1649) 
    E/Run.GPS (11997): at android.view.ViewRoot.handleMessage(ViewRoot.java:1694) 
    E/Run.GPS (11997): at android.os.Handler.dispatchMessage(Handler.java:99) 
    E/Run.GPS (11997): at android.os.Looper.loop(Looper.java:123) 
    E/Run.GPS (11997): at android.app.ActivityThread.main(ActivityThread.java:4363) 
    E/Run.GPS (11997): at java.lang.reflect.Method.invokeNative(Native Method) 
    E/Run.GPS (11997): at java.lang.reflect.Method.invoke(Method.java:521) 
    E/Run.GPS (11997): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860) 
    E/Run.GPS (11997): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618) 
    E/Run.GPS (11997): at dalvik.system.NativeStart.main(Native Method) 
    E/Run.GPS (11997): Cannot connect to BT device 
    E/Run.GPS (11997): java.io.IOException: Service discovery failed

這裏的dmesg的輸出，同時試圖連接心率監視器

<4>[74726.239833] select 11691 (.serviceModeApp), adj 15, size 3205, to kill 
<4>[74726.240741] select 11739 (com.wssnps), adj 15, size 3207, to kill 
<4>[74726.246870] select 11750 (id.partnersetup), adj 15, size 3219, to kill 
<4>[74726.253390] select 11857 (p.bluetoothicon), adj 15, size 3299, to kill 
<4>[74726.259879] select 13131 (ndroid.settings), adj 15, size 4586, to kill 
<4>[74726.266372] send sigkill to 13131 (ndroid.settings), adj 15, size 4586 
<7>[74733.945097] [BT] GPIO_BT_WAKE = 1 
<7>[74733.945121] [BT] wake_lock(bt_wake_lock) 
<7>[74733.951799] [BT] GPIO_BT_HOST_WAKE = 1 
<7>[74733.951822] [BT] wake_lock timeout = 5 sec 
<7>[74735.890196] [BT] GPIO_BT_HOST_WAKE = 0 
<7>[74736.150987] [BT] GPIO_BT_HOST_WAKE = 1 
<7>[74736.151009] [BT] wake_lock timeout = 5 sec 
<7>[74737.490185] [BT] GPIO_BT_HOST_WAKE = 0 
<7>[74740.073913] [BT] GPIO_BT_HOST_WAKE = 1 
<7>[74740.073948] [BT] wake_lock timeout = 5 sec 
<7>[74741.315336] [BT] GPIO_BT_HOST_WAKE = 0 
<7>[74743.249747] [BT] GPIO_BT_HOST_WAKE = 1 
<7>[74743.249768] [BT] wake_lock timeout = 5 sec 
<7>[74744.865099] [BT] GPIO_BT_HOST_WAKE = 0 
<7>[74745.154487] [BT] GPIO_BT_HOST_WAKE = 1 
<7>[74745.154509] [BT] wake_lock timeout = 5 sec 
<7>[74748.852534] [BT] GPIO_BT_HOST_WAKE = 0 
<7>[74749.156256] [BT] GPIO_BT_HOST_WAKE = 1 
<7>[74749.156278] [BT] wake_lock timeout = 5 sec 
<7>[74750.490018] [BT] GPIO_BT_HOST_WAKE = 0 
<4>[74754.230424] select 11691 (.serviceModeApp), adj 15, size 3191, to kill 
<4>[74754.231326] select 11739 (com.wssnps), adj 15, size 3193, to kill 
<4>[74754.237473] select 11750 (id.partnersetup), adj 15, size 3205, to kill 
<4>[74754.243950] select 11857 (p.bluetoothicon), adj 15, size 3283, to kill 
<4>[74754.250452] select 13140 (com.svox.pico), adj 15, size 3465, to kill 
<4>[74754.256787] send sigkill to 13140 (com.svox.pico), adj 15, size 3465

這裏的logcat的輸出時我在Endomondo點擊'connect zephyr'

I/PUSH Event(19147): MotionEvent : QueuedEvent{43d7d480 MotionEvent{440b5680 action=1 x=228.28438 y=212.55624 pressure=0.0 size=0.0}} 
D/BluetoothZephyrService(23605): connect to: 00:07:80:88:F5:AD 
D/BluetoothSocket(23605): BluetoothSocket created fd: -1uuid00001101-0000-1000-8000-00805f9b34fbport -1      
D/BluetoothSocket.cpp(23605): initSocketNative  
I/BLZ20_WRAPPER(23605): blz20_wrp_socket: fam 31, type 1, prot BTPROTO_RFCOMM              
D/BLZ20_WRAPPER(23605): blz20_init: initializing...  
D/BTL_IFC_WRP(23605): wsactive_init: init active list                   
I/BTL_IFC (23605): main_client_thread: Client main thread starting                
D/BLZ20_WRAPPER(23605): blz20_init: success  
I/BTL_IFC (23605): BTL_IFC_RegisterSubSystem: Register subsystem [(null)]               
I/BTL_IFC (23605): btl_ifc_ctrl_connect: Connect control channel for subsystem [(null)]           
D/BTL_IFC_WRP(23605): wrp_sock_create: CTRL 
D/BTL_IFC_WRP(23605): wrp_alloc_new_sock: wrp_alloc_new_sock sub 1            
D/BTL_IFC_WRP(23605): wrp_sock_create: 28 
D/BTL_IFC_WRP(23605): wrp_sock_connect: wrp_sock_connect 127.0.0.1:9000 (28)          
I/BTL-IFS (21889): main_server_thread: [CTRL] Client connected (14)            
I/BTL_IFC_WRP(23605): wrp_sock_connect: Connected. (28)               
I/BTL_IFC (23605): send_ctrl_msg: [BTL_IFC CTRL] send BTLIF_REGISTER_SUBSYS_REQ ((null)) 0 pbytes (hdl 28)  
I/BTL-IFS (21889): attach_client: multiclient index 1                  
I/BTL-IFS (21889): attach_client: ######## Attached client subsystem (14) ########             
I/BTL-IFS (21889): btl_if_notify_local_event: Notify local event BTLIF_SUBSYSTEM_ATTACHED 
D/  (21889): btlif_bts_api_ctrl_cb: btlif_bts_api_ctrl_cb : id BTLIF_SUBSYSTEM_ATTACHED (4112) on hdl 14     
I/  (21889): btlif_rfc_ctrl_chan_attached: client attached ctrl handle 14            
D/BTL-IFS (21889): send_registration_rsp: send_registration_rsp [0]                
I/BTL-IFS (21889): send_ctrl_msg: [BTL_IFS CTRL] send BTLIF_REGISTER_SUBSYS_RSP (CTRL) 2 pbytes (hdl 14)       
D/BTL_IFC (23605): BTL_IFC_RegisterSubSystem: add new ctrl fd to active set              
D/BTL_IFC_WRP(23605): wrp_wsock_create: (null)  
D/BTL_IFC_WRP(23605): wrp_alloc_new_sock: wrp_alloc_new_sock sub 15                
D/BTL_IFC_WRP(23605): wrp_wsock_create: 32  
D/BLZ20_WRAPPER(23605): btsk_alloc_add: success  
I/BLZ20_WRAPPER(23605): blz20_wrp_socket: return 32                    
D/BLZ20_WRAPPER(23605): blz20_wrp_setsockopt: fd (-1:32), bta -1, rc 0, wflags 0x0             
I/BLZ20_WRAPPER(23605): blz20_wrp_setsockopt: configure rfcomm lm mode 0x26, (master:0, auth 1, enc 1)      
I/BLZ20_WRAPPER(23605): blz20_wrp_setsockopt: success 
D/BLZ20_WRAPPER(23605): blz20_wrp_setsockopt: fd (-1:32), bta -1, rc 0, wflags 0x0            
I/BLZ20_WRAPPER(23605): blz20_wrp_setsockopt: configure rfcomm sndbuf len 71680 bytes            
I/BLZ20_WRAPPER(23605): blz20_wrp_setsockopt: success 
D/BluetoothSocket.cpp(23605): ...fd 32 created (RFCOMM, lm = 26)                
D/BluetoothSocket.cpp(23605): initSocketFromFdNative    
D/BluetoothZephyrService(23605): setState() 0 -> 2                    
I/BluetoothZephyrService(23605): BEGIN mConnectThread  
E/BluetoothService.cpp(19147): stopDiscoveryNative: D-Bus error in StopDiscovery: org.bluez.Error.Failed (Invalid discovery session) 
D/BluetoothSocket(23605): connect     
D/BluetoothSocket(23605): doSdp     
I/BluetoothService.cpp(19147): ... Object Path = /org/bluez/21902/hci0/dev_00_07_80_88_F5_AD  
I/BluetoothService.cpp(19147): ... Pattern = 00001101-0000-1000-8000-00805f9b34fb, strlen = 36         
I/BluetoothZephyr(23605): MESSAGE_STATE_CHANGE: 2                    
D/DEVICE (21902):  *************DiscoverServices********       
I/DTUN_HCID(21902): dtun_client_get_remote_svc_channel: starting discovery on (uuid16=0x0011)            
I/DTUN_HCID(21902): bdaddr=00:07:80:88:F5:AD      
I/DTUN_CLNT(21902):  Client calling DTUN_METHOD_DM_GET_REMOTE_SERVICE_CHANNEL (id 4)          
I/  (21889): DTUN_ReceiveCtrlMsg: [DTUN] Received message [BTLIF_DTUN_METHOD_CALL] 4354         
I/  (21889): handle_method_call: handle_method_call :: received DTUN_METHOD_DM_GET_REMOTE_SERVICE_CHANNEL (id 4), len 134 
E/BTLD (21889): ****************search UUID = 1101***********   
I//system/bin/btld(21888):    btapp_dm_GetRemoteServiceChannel()        
W/BTLD (21889): SDP - Rcvd conn cnf with error: 0x4 CID 0x42                
I/BTL-IFS (21889): send_ctrl_msg: [BTL_IFS CTRL] send BTLIF_DTUN_SIGNAL_EVT (CTRL) 13 pbytes (hdl 10)       
I/DTUN_CLNT(21902): dtun-rx signal [DTUN_SIG_DM_RMT_SERVICE_CHANNEL] (id 42) len 15           
I/DTUN_HCID(21902): dtun_dm_sig_rmt_service_channel: success=1, service=00000000               
E/DTUN_HCID(21902): discovery unsuccessful!    
V/BluetoothEventRedirector(21741): Received android.bleutooth.device.action.UUID 
E/CachedBluetoothDevice(21741): onUuidChanged: Time since last connect9266997                
D/BluetoothService(19147): Cleaning up failed UUID channel lookup: 00:07:80:88:F5:AD 00001101-0000-1000-8000-00805f9b34fb          
D/BluetoothSocket(23605): onRfcommChannelFound -1                    
D/BluetoothZephyrService(23605): setState() 2 -> 1                    
D/BluetoothSocket(23605): close     
D/BluetoothSocket(23605): cancel    
D/BluetoothSocket.cpp(23605): abortNative   
D/BluetoothSocket.cpp(23605): ...asocket_abort(32) complete                  
D/BluetoothSocket.cpp(23605): destroyNative   
D/BluetoothSocket.cpp(23605): ...asocket_destroy(32) complete                  
D/BluetoothZephyrService(23605): start   
D/BluetoothSocket(23605): close    
D/BluetoothSocket(23605): BluetoothSocket created fd: -1uuidnullport 1             
D/BluetoothSocket.cpp(23605): initSocketNative   
I/BLZ20_WRAPPER(23605): blz20_wrp_socket: fam 31, type 1, prot BTPROTO_RFCOMM               
D/BTL_IFC_WRP(23605): wrp_wsock_create: (null) 
D/BTL_IFC_WRP(23605): wrp_alloc_new_sock: wrp_alloc_new_sock sub 15                
D/BTL_IFC_WRP(23605): wrp_wsock_create: 32 
D/BLZ20_WRAPPER(23605): btsk_alloc_add: success  
D/BLZ20_WRAPPER(23605): btsk_dump_list: fd (-1:32), bta -1, rc 0, wflags 0x0             
I/BLZ20_WRAPPER(23605): blz20_wrp_socket: return 32                    
E/BLZ20_WRAPPER(23605): ##### ERROR : btsk_check_duplicates: WARNING : duplicate entries found for key 4, val 32#####   
D/BLZ20_WRAPPER(23605): btsk_check_duplicates: fd (-1:32), bta -1, rc 0, wflags 0x0           
D/BLZ20_WRAPPER(23605): btsk_check_duplicates: fd (-1:32), bta -1, rc 0, wflags 0x0           
E/BLZ20_WRAPPER(23605): ##### ERROR : btsk_check_duplicates: ### ASSERT : frameworks/base/core/jni/../../../../vendor/brcm/adaptation/btl-if/client/blz20_wrapper.c line 534 duplicates found (2) ########  
D/BLZ20_WRAPPER(23605): blz20_wrp_setsockopt: fd (-1:32), bta -1, rc 0, wflags 0x0           
I/BLZ20_WRAPPER(23605): blz20_wrp_setsockopt: configure rfcomm lm mode 0x26, (master:0, auth 1, enc 1)      
I/BLZ20_WRAPPER(23605): blz20_wrp_setsockopt: success 
E/BLZ20_WRAPPER(23605): ##### ERROR : btsk_check_duplicates: WARNING : duplicate entries found for key 4, val 32#####   
D/BLZ20_WRAPPER(23605): btsk_check_duplicates: fd (-1:32), bta -1, rc 0, wflags 0x0           
D/BLZ20_WRAPPER(23605): btsk_check_duplicates: fd (-1:32), bta -1, rc 0, wflags 0x0           
E/BLZ20_WRAPPER(23605): ##### ERROR : btsk_check_duplicates: ### ASSERT : frameworks/base/core/jni/../../../../vendor/brcm/adaptation/btl-if/client/blz20_wrapper.c line 534 duplicates found (2) ########  
D/BLZ20_WRAPPER(23605): blz20_wrp_setsockopt: fd (-1:32), bta -1, rc 0, wflags 0x0           
I/BLZ20_WRAPPER(23605): blz20_wrp_setsockopt: configure rfcomm sndbuf len 71680 bytes           
I/BLZ20_WRAPPER(23605): blz20_wrp_setsockopt: success 
D/BluetoothSocket.cpp(23605): ...fd 32 created (RFCOMM, lm = 26)               
D/BluetoothSocket.cpp(23605): initSocketFromFdNative   
D/BluetoothSocket(23605): bindListen      
D/BluetoothSocket.cpp(23605): bindListenNative     
I/BLZ20_WRAPPER(23605): blz20_wrp_bind: s 32 
E/BLZ20_WRAPPER(23605): ##### ERROR : btsk_check_duplicates: WARNING : duplicate entries found for key 4, val 32#####   
D/BLZ20_WRAPPER(23605): btsk_check_duplicates: fd (-1:32), bta -1, rc 0, wflags 0x0           
D/BLZ20_WRAPPER(23605): btsk_check_duplicates: fd (-1:32), bta -1, rc 0, wflags 0x0           
E/BLZ20_WRAPPER(23605): ##### ERROR : btsk_check_duplicates: ### ASSERT : frameworks/base/core/jni/../../../../vendor/brcm/adaptation/btl-if/client/blz20_wrapper.c line 534 duplicates found (2) ########  
D/BLZ20_WRAPPER(23605): blz20_wrp_bind: bind socket fd (-1:32), bta -1, rc 0, wflags 0x0          
D/BLZ20_WRAPPER(23605): __bind_prot_rfcomm: rc_chan 1                  
D/BTL_IFC_WRP(23605): wrp_sock_bind: wrp_sock_bind on port 9050                
I/BLZ20_WRAPPER(23605): blz20_wrp_listen: s 32, backlog 1                  
E/BLZ20_WRAPPER(23605): ##### ERROR : btsk_check_duplicates: WARNING : duplicate entries found for key 4, val 32#####    
D/BLZ20_WRAPPER(23605): btsk_check_duplicates: fd (-1:32), bta -1, rc 1, wflags 0x0           
D/BLZ20_WRAPPER(23605): btsk_check_duplicates: fd (-1:32), bta -1, rc 0, wflags 0x0           
E/BLZ20_WRAPPER(23605): ##### ERROR : btsk_check_duplicates: ### ASSERT : frameworks/base/core/jni/../../../../vendor/brcm/adaptation/btl-if/client/blz20_wrapper.c line 534 duplicates found (2) ########  
D/BLZ20_WRAPPER(23605): blz20_wrp_listen: fd (-1:32), bta -1, rc 1, wflags 0x0            
D/BLZ20_WRAPPER(23605): btlif_send_msg_wait_response: send BTLIF_BTS_RFC_LISTEN_REQ, wait for |BTLIF_BTS_RFC_LISTEN_RSP|       
D/BTL_IFC (23605): BTL_IFC_CtrlSend: BTL_IFC_CtrlSend  
I/BTL_IFC (23605): send_ctrl_msg: [BTL_IFC CTRL] send BTLIF_BTS_RFC_LISTEN_REQ ((null)) 20 pbytes (hdl 28)      
D/  (21889): btlif_bts_api_ctrl_cb: btlif_bts_api_ctrl_cb : id BTLIF_BTS_RFC_LISTEN_REQ (4433) on hdl 14     
I/  (21889): btlif_rfc_listen_req: Allocated dynamic server channel 4             
D/  (21889): bts_chan_alloc_add: bts_chan_alloc_add : success (tot 1)             
D/  (21889): bts_chan_dump_all: ### channel list ###                  
D/  (21889): bts_chan_dump_all: type 3, dhdl -1, bta_hdl -1, scn -1, phdl 65535, lstpnd 0, -1:-1 (L:D) 
I/  (21889): btlif_rfc_listen_req: start rfcomm server on scn 4, role 1, sec_mask 0x30 
D/  (21889): jw_if_rfcomm_srv_cback: event=BTA_JV_RFCOMM_START_EVT 
I/  (21889): jw_if_rfcomm_srv_cback: [BTA_JV_RFCOMM_START_EVT] start status: 0, handle:0, security id: 47 
I/  (21889): jv_rfc_srv_listen_started: jv_rfc_srv_listen_started 
I/BTL-IFS (21889): send_ctrl_msg: [BTL_IFS CTRL] send BTLIF_BTS_RFC_LISTEN_RSP() 17 pbytes (hdl 14) 
I/BTL_IFC (23605): btl_ifc_ctrl_rx: [BTL_IFC CTRL] recv BTLIF_BTS_RFC_LISTEN_RSP ((null)) 19 pbytes (hdl 28) 
I/BLZ20_WRAPPER(23605): btlif_ctrl_callback: btlif_ctrl_callback : msg id BTLIF_BTS_RFC_LISTEN_RSP 
E/BLZ20_WRAPPER(23605): ##### ERROR : btsk_check_duplicates: WARNING : duplicate entries found for key 4, val 32##### 
D/BLZ20_WRAPPER(23605): btsk_check_duplicates: fd (-1:32), bta -1, rc 1, wflags 0x2 
D/BLZ20_WRAPPER(23605): btsk_check_duplicates: fd (-1:32), bta -1, rc 0, wflags 0x0 
E/BLZ20_WRAPPER(23605): ##### ERROR : btsk_check_duplicates: ### ASSERT : frameworks/base/core/jni/../../../../vendor/brcm/adaptation/btl-if/client/blz20_wrapper.c line 534 duplicates found (2) ######## 
I/BLZ20_WRAPPER(23605): btlif_process_listen_rsp: listen response for bta hdl 0 
D/BLZ20_WRAPPER(23605): btlif_signal_event: fd (-1:32), bta 0, rc 1, wflags 0x2 
D/BLZ20_WRAPPER(23605): btlif_signal_event: event BTLIF_BTS_RFC_LISTEN_RSP matched 
D/BLZ20_WRAPPER(23605): btlif_send_msg_wait_response: unblocked fd (-1:32), bta 0, rc 1, wflags 0x0 
I/BLZ20_WRAPPER(23605): __listen_prot_rfcomm: success, scn 4 
D/BTL_IFC_WRP(23605): wrp_sock_listen_bl: wrp_sock_listen_bl : fd 32 127.0.0.1:9050 backlog 1 
I/BLZ20_WRAPPER(23605): __listen_prot_rfcomm: success 
D/BluetoothSocket.cpp(23605): ...bindListenNative(32) success 
I/DTUN_CLNT(21902):  Client calling DTUN_METHOD_DM_ADD_SDP_REC (id 17) 
I/  (21889): DTUN_ReceiveCtrlMsg: [DTUN] Received message [BTLIF_DTUN_METHOD_CALL] 4354 
I/  (21889): handle_method_call: handle_method_call :: received DTUN_METHOD_DM_ADD_SDP_REC (id 17), len 270 
I/  (21889): btapp_bts_convert_rc_chan_to_scn: found scn 4 
I/BTL-IFS (21889): send_ctrl_msg: [BTL_IFS CTRL] send BTLIF_DTUN_SIGNAL_EVT (CTRL) 12 pbytes (hdl 10) 
I/DTUN_CLNT(21902): dtun-rx signal [DTUN_SIG_DM_SDP_REC_HANDLE] (id 50) len 14 
I/DTUN_HCID(21902): dtun_dm_sig_sdp_rec_handle: handle = 0x10006 
D/BluetoothService(19147): new handle 0 
I/BluetoothZephyr(23605): MESSAGE_STATE_CHANGE: 1 
I/BluetoothZephyr(23605): Unable to connect device 
D/BluetoothZephyrService(23605): setState() 1 -> 1 
D/BluetoothZephyrService(23605): BEGIN mAcceptThreadThread[Thread-9,5,main] 
D/BluetoothSocket(23605): accept 
D/BluetoothSocket.cpp(23605): acceptNative 
I/BluetoothZephyr(23605): MESSAGE_STATE_CHANGE: 1 
D/WynexActivity(19215): <><><>ACTION ::android.intent.action.TIME_TICK 
D/LocationMasfClient(19147): getNetworkLocation(): Location not found in cache, making network request 
D/ProtoRequestListener(19147): requestFailed() 
I/power (19147): *** set_screen_state 0

來源

2010-04-18 Ciaran

+0

剛剛在logcat V/BluetoothEventRedirector（21741）中看到了這個：收到android.bleutooth.device.action.UUID我假設android。** bleu ** tooth（即拼錯的android.bluetooth）是一個輸出的字符串作爲消息，因此對代碼沒有影響。至少，我希望如此... – Ciaran 2010-04-30 14:35:30

回答

2

好了，解決了這個問題。

的解決方案是更新的固件。手機我現在有： PDA：I570EXXJE1 電話：i570EXXJD1 CSC：I570EOXEJE1

和藍牙屬工作 '開箱即用'

看http://samsung-firmwares.com爲最新的固件以及閃光手機（奧丁）和細節/教程的程序。

來源

2010-05-20 07:18:52 Ciaran

+0

我發現了一個應用程序來通過藍牙傳輸文件，並且我在各種手機上進行了測試，並且其工作正常......我想知道如果固件存在問題，那麼這些人如何解決他們的應用程序中的錯誤。檢查它... http：//www.mobyware.net/samsung-gt-s5360-galaxy-y-device-2173/bluetooth-file-transfer-obex-ftp-for-android-get-free-11596.html – Sandeep 2012-04-27 11:42:11

3

我從gps-sport論壇得到了這些信息。不知道如何處理它雖然...

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

交叉張貼從軟件類別此項。在那裏的線程處理Zephyr HxM作爲次要問題 - 這意味着它可能不容易找到...

24.04.2010 16:47:05 UTCgeändertam 24.04。2010 17時03分03秒UTC

一個修復藍牙連接問題

嗨

如果這個問題仍然沒有解決，下面的代碼描述瞭如何使Android 2.1的連接工作（測試在HTC Desire上）。只需將您的HXM的MAC替換爲「00：07：80：89：EE：EB」即可進行連接。連接成功後，可以使用input = socket.getInputStream（）的常規方法。

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();

希望修復會出很快=）

問候 埃斯S.尼加德

來源

2010-04-27 14:39:45 Ciaran

+1

我試着用我的i5700，這個小實驗在LogCat中以下面的錯誤結束：「wrp_sock_create：套接字創建失敗（Permission denied）」。 （我的應用程序請求BLUETOOTH和BLUETOOTH_ADMIN權限，所以這應該不成問題。） – 2010-07-13 19:52:10

+0

我還應該提到，我無法在此手機上創建可用的藍牙SPP連接。我嘗試了很多方法... – 2010-07-13 19:53:43

+0

也許是同一個問題：http://groups.google.com/group/android-developers/browse_thread/thread/a705aa4b8f865cc1 – 2010-07-13 19:54:22

0

這個線程了在谷歌羣組（Android的開發者）也很有意思： ' 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 2.6.29版本（root @ SE-S611） （gcc版本4.3.1 （用於S3C64XX三星電子AP開發團隊））＃2星期六年03月13 2點28分48秒KST 2010

kernel.cmdline =＃首先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，釋放鍵 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 =三星 ro.product.locale.language = EN ro.product.locale.region = GB ro.wifi.channels = ro.board.platform = s3c6410

ro.build.product已過時;使用ro.product.device

ro.build.product = GT-I5700

不要試圖解析ro.build.description或.fingerprint

ro.build.description = GT-I5700-用戶2.1-update1 ECLAIR XXJCB ota-rel- 密鑰，釋放密鑰 ro.build.fingerprint = Samsung/GT-I5700/GT-I5700/GT-I5700：2.1-update1/ ECLAIR/XXJCB：user/ota- rel-keys，釋放鍵

Samsung特性

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 =更改 ro.build.SupportFUS = TRUE ロ.build.CGMM = GT-I5700 ro.build.GMM = GT-I5700

端建立屬性

＃

system.prop用於人字

來源

2010-05-02 08:58:17 Ciaran

0

我發現這個確切的問題發生在其中一個設備關閉藍牙時。

來源

2010-05-04 17:01:48

+0

在我的情況下，藍牙絕對是打開的，兩個設備。我確信這是因爲我也可以將心率監視器（Zephyr HxM）連接到我的電腦，並讀取通過串行發送的數據。 我總是斷開我的電腦上的設備，然後嘗試通過Android手機，以防干擾等。 – Ciaran 2010-05-05 10:48:34

0

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

可以解決這個問題。提交日誌爲： 「爲BCM4325添加固件」

如果之前沒有內核中的固件支持此操作，那麼顯然會導致問題。

我想我得看看我是否可以從源代碼構建Android和我的手機上安裝:-(

來源

2010-05-17 10:05:35 Ciaran

+0

虛假警報。該提交涉及芯片的wlan部分。但Broadcom聯繫已將藍牙驅動程序中的錯誤的詳細信息轉發給Broadcom的藍牙團隊 – Ciaran 2010-05-17 21:44:33

相關問題

 相關問題