Last 7 days

• Dec 07, 2009

  issue 17 (remoteBluetoothDevice.pair() does not work) reported by dskaputa   -   What steps will reproduce the problem? 1.remoteBluetoothDevice.pair() 2. 3. What is the expected output? What do you see instead? the public void pinRequested() or one of the other event listeners should get triggered but nothing happens. What version of the product are you using? On what operating system? G1, android 1.6, the latest code base .3 Please provide any additional information below. I am not trying to connect to a headset.. I'm connecting to a roving networks bluetooth chip. The scan works fine and the bluetooth chip shows up but the pair does not work. I am wondering if the other bluetooth device class needs to be different.

  What steps will reproduce the problem? 1.remoteBluetoothDevice.pair() 2. 3. What is the expected output? What do you see instead? the public void pinRequested() or one of the other event listeners should get triggered but nothing happens. What version of the product are you using? On what operating system? G1, android 1.6, the latest code base .3 Please provide any additional information below. I am not trying to connect to a headset.. I'm connecting to a roving networks bluetooth chip. The scan works fine and the bluetooth chip shows up but the pair does not work. I am wondering if the other bluetooth device class needs to be different.

Last 30 days

• Nov 24, 2009

  issue 16 (Does not work on HTC Tattoo) reported by mich...@jixel.com   -   I can't seem to get thos to work on my HTC Tattoo 1.6, 1.67.405.6 I have an application that works fine on my Magic. I perform the pairing outwith the application using the standard BT system tools. Once this is paired i run the app which find the device then open a port to it. On the Magic this works on the Tattoo I get; ERROR/bluetooth_RfcommSocket.cpp(1751): connect error: No route to host (113) The device is paired as I check this before I connect and isPaired returns true. I have attached the log. Any iead why this works on magic and not tattoo would be a great help.

  I can't seem to get thos to work on my HTC Tattoo 1.6, 1.67.405.6 I have an application that works fine on my Magic. I perform the pairing outwith the application using the standard BT system tools. Once this is paired i run the app which find the device then open a port to it. On the Magic this works on the Tattoo I get; ERROR/bluetooth_RfcommSocket.cpp(1751): connect error: No route to host (113) The device is paired as I check this before I connect and isPaired returns true. I have attached the log. Any iead why this works on magic and not tattoo would be a great help.
• Nov 17, 2009

  r47 ([No log message]) committed by emanuele...@gmail.com   -   [No log message]

  [No log message]
• Nov 17, 2009

  r46 ([No log message]) committed by emanuele...@gmail.com   -   [No log message]

  [No log message]
• Nov 17, 2009

  r45 ([No log message]) committed by emanuele...@gmail.com   -   [No log message]

  [No log message]
• Nov 17, 2009

  r44 ([No log message]) committed by emanuele...@gmail.com   -   [No log message]

  [No log message]
• Nov 17, 2009

  r43 ([No log message]) committed by emanuele...@gmail.com   -   [No log message]

  [No log message]
• Nov 17, 2009

  r42 ([No log message]) committed by emanuele...@gmail.com   -   [No log message]

  [No log message]
• Nov 17, 2009

  r41 ( ) committed by emanuele...@gmail.com   -  
• Nov 17, 2009

  r40 ([No log message]) committed by emanuele...@gmail.com   -   [No log message]

  [No log message]
• Nov 17, 2009

  r39 ([No log message]) committed by emanuele...@gmail.com   -   [No log message]

  [No log message]
• Nov 17, 2009

  r38 ([No log message]) committed by emanuele...@gmail.com   -   [No log message]

  [No log message]
• Nov 17, 2009

  r37 ( ) committed by emanuele...@gmail.com   -  
• Nov 17, 2009

  r36 ([No log message]) committed by emanuele...@gmail.com   -   [No log message]

  [No log message]
• Nov 17, 2009

  r35 ([No log message]) committed by emanuele...@gmail.com   -   [No log message]

  [No log message]
• Nov 17, 2009

  issue 14 (pair() does not return) commented on by zytiam   -   not supported pair(String) API. Only support pair() API.

  not supported pair(String) API. Only support pair() API.
• Nov 16, 2009

  r34 ( ) committed by emanuele...@gmail.com   -  
• Nov 16, 2009

  r33 (SCAN, RSSI and and autoenabling of the thing) committed by emanuele...@gmail.com   -   SCAN, RSSI and and autoenabling of the thing

  SCAN, RSSI and and autoenabling of the thing
• Nov 15, 2009

  issue 15 (Multiple Links) reported by tomer.berdugo   -   Hello not exactly an issue but more of a general question.. is it technically possible to open more than one bluetooth link ? i know that your bluetooth class is implemented as a singleton, but i wanted to know what would happen if lets say you tried to create more than one instance. thanks

  Hello not exactly an issue but more of a general question.. is it technically possible to open more than one bluetooth link ? i know that your bluetooth class is implemented as a singleton, but i wanted to know what would happen if lets say you tried to create more than one instance. thanks
• Nov 10, 2009

  r32 ([No log message]) committed by emanuele...@gmail.com   -   [No log message]

  [No log message]
• Nov 10, 2009

  r31 ([No log message]) committed by emanuele...@gmail.com   -   [No log message]

  [No log message]
• Nov 10, 2009

  r30 ([No log message]) committed by emanuele...@gmail.com   -   [No log message]

  [No log message]
• Nov 10, 2009

  r29 ([No log message]) committed by emanuele...@gmail.com   -   [No log message]

  [No log message]

Earlier this year

• Nov 10, 2009

  r28 ([No log message]) committed by emanuele...@gmail.com   -   [No log message]

  [No log message]
• Nov 09, 2009

  r27 ([No log message]) committed by emanuele...@gmail.com   -   [No log message]

  [No log message]
• Nov 09, 2009

  r26 ([No log message]) committed by emanuele...@gmail.com   -   [No log message]

  [No log message]
• Nov 09, 2009

  r25 (fix) committed by emanuele...@gmail.com   -   fix

  fix
• Nov 09, 2009

  r24 (fix) committed by emanuele...@gmail.com   -   fix

  fix
• Nov 09, 2009

  r23 ([No log message]) committed by emanuele...@gmail.com   -   [No log message]

  [No log message]
• Nov 09, 2009

  r22 (trying a porting) committed by emanuele...@gmail.com   -   trying a porting

  trying a porting
• Nov 06, 2009

  BluetoothAPIHowto (This page will contain code snippets to show how to use the ...) Wiki page commented on by sunyal   -   Had a question, is it possible to act as client? I am researching being able to connect to the PS3 as the BD Remote.

  Had a question, is it possible to act as client? I am researching being able to connect to the PS3 as the BD Remote.
• Nov 06, 2009

  issue 12 (sending string from one phone to another) commented on by bonifaz.kaufmann   -   I get the same error on Samsung Moment / Behold. When trying to connect. It runs Android 1.5

  I get the same error on Samsung Moment / Behold. When trying to connect. It runs Android 1.5
• Nov 02, 2009

  issue 14 (pair() does not return) commented on by mich...@jixel.com   -   Actaully, it does not hang, I get an exception ... 11-02 18:20:40.601: INFO/BluetoothEventLoop.cpp(72): DiscoveryCompleted signal received 11-02 18:20:40.621: INFO/TTSActivity(14384): BT Scan done 11-02 18:20:40.621: INFO/TTSActivity(14384): BT get dev 11-02 18:20:40.621: INFO/TTSActivity(14384): BT dev name: KDC300[000158] 11-02 18:20:40.651: INFO/TTSActivity(14384): BT pair ... 11-02 18:20:40.751: ERROR/TTSActivity(14384): BT Exception: java.lang.UnsupportedOperationException 11-02 18:20:40.751: ERROR/TTSActivity(14384): java.lang.UnsupportedOperationException 11-02 18:20:40.751: ERROR/TTSActivity(14384): at it.gerdavax.android.bluetooth.LocalBluetoothDevice$RemoteBluetoothDeviceImpl.pair(LocalBluetoothDevice.java:312) 11-02 18:20:40.751: ERROR/TTSActivity(14384): at com.himoa.tts.TTSActivity.scanCompleted(TTSActivity.java:122) 11-02 18:20:40.751: ERROR/TTSActivity(14384): at it.gerdavax.android.bluetooth.LocalBluetoothDevice$BluetoothBroadcastReceiver.processDiscoveryCompleted(LocalBluetoothDevice.java:790) 11-02 18:20:40.751: ERROR/TTSActivity(14384): at it.gerdavax.android.bluetooth.LocalBluetoothDevice$BluetoothBroadcastReceiver.onReceive(LocalBluetoothDevice.java:689) 11-02 18:20:40.751: ERROR/TTSActivity(14384): at android.app.ActivityThread$PackageInfo$ReceiverDispatcher$Args.run(ActivityThread.java:705) 11-02 18:20:40.751: ERROR/TTSActivity(14384): at android.os.Handler.handleCallback(Handler.java:587) 11-02 18:20:40.751: ERROR/TTSActivity(14384): at android.os.Handler.dispatchMessage(Handler.java:92) 11-02 18:20:40.751: ERROR/TTSActivity(14384): at android.os.Looper.loop(Looper.java:123) 11-02 18:20:40.751: ERROR/TTSActivity(14384): at android.app.ActivityThread.main(ActivityThread.java:4203) 11-02 18:20:40.751: ERROR/TTSActivity(14384): at java.lang.reflect.Method.invokeNative(Native Method) 11-02 18:20:40.751: ERROR/TTSActivity(14384): at java.lang.reflect.Method.invoke(Method.java:521) 11-02 18:20:40.751: ERROR/TTSActivity(14384): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:791) 11-02 18:20:40.751: ERROR/TTSActivity(14384): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:549) 11-02 18:20:40.751: ERROR/TTSActivity(14384): at dalvik.system.NativeStart.main(Native Method) Can you offer any advise?

  Actaully, it does not hang, I get an exception ... 11-02 18:20:40.601: INFO/BluetoothEventLoop.cpp(72): DiscoveryCompleted signal received 11-02 18:20:40.621: INFO/TTSActivity(14384): BT Scan done 11-02 18:20:40.621: INFO/TTSActivity(14384): BT get dev 11-02 18:20:40.621: INFO/TTSActivity(14384): BT dev name: KDC300[000158] 11-02 18:20:40.651: INFO/TTSActivity(14384): BT pair ... 11-02 18:20:40.751: ERROR/TTSActivity(14384): BT Exception: java.lang.UnsupportedOperationException 11-02 18:20:40.751: ERROR/TTSActivity(14384): java.lang.UnsupportedOperationException 11-02 18:20:40.751: ERROR/TTSActivity(14384): at it.gerdavax.android.bluetooth.LocalBluetoothDevice$RemoteBluetoothDeviceImpl.pair(LocalBluetoothDevice.java:312) 11-02 18:20:40.751: ERROR/TTSActivity(14384): at com.himoa.tts.TTSActivity.scanCompleted(TTSActivity.java:122) 11-02 18:20:40.751: ERROR/TTSActivity(14384): at it.gerdavax.android.bluetooth.LocalBluetoothDevice$BluetoothBroadcastReceiver.processDiscoveryCompleted(LocalBluetoothDevice.java:790) 11-02 18:20:40.751: ERROR/TTSActivity(14384): at it.gerdavax.android.bluetooth.LocalBluetoothDevice$BluetoothBroadcastReceiver.onReceive(LocalBluetoothDevice.java:689) 11-02 18:20:40.751: ERROR/TTSActivity(14384): at android.app.ActivityThread$PackageInfo$ReceiverDispatcher$Args.run(ActivityThread.java:705) 11-02 18:20:40.751: ERROR/TTSActivity(14384): at android.os.Handler.handleCallback(Handler.java:587) 11-02 18:20:40.751: ERROR/TTSActivity(14384): at android.os.Handler.dispatchMessage(Handler.java:92) 11-02 18:20:40.751: ERROR/TTSActivity(14384): at android.os.Looper.loop(Looper.java:123) 11-02 18:20:40.751: ERROR/TTSActivity(14384): at android.app.ActivityThread.main(ActivityThread.java:4203) 11-02 18:20:40.751: ERROR/TTSActivity(14384): at java.lang.reflect.Method.invokeNative(Native Method) 11-02 18:20:40.751: ERROR/TTSActivity(14384): at java.lang.reflect.Method.invoke(Method.java:521) 11-02 18:20:40.751: ERROR/TTSActivity(14384): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:791) 11-02 18:20:40.751: ERROR/TTSActivity(14384): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:549) 11-02 18:20:40.751: ERROR/TTSActivity(14384): at dalvik.system.NativeStart.main(Native Method) Can you offer any advise?
• Nov 02, 2009

  issue 14 (pair() does not return) reported by mich...@jixel.com   -   I'm using this api to connect to a KDC barcode scanner. Everything seems pretty straight forward to use, however it seems to hang when I call pair(). 1. I create my local device - ok 2. Initial a scan - ok 3. The listener reports seeing the KDC 4. When scan is complete, I pick the KDC from the devices 5. Check if it's paired already, return no. 6. call pair("0000"), this is the correct key for the KDC My code is; Log.i("BT", "Pairing ..."); kdc.pair("0000"); Log.i("BT", "Paired"); // *** THIS IS NEVER REACHED *** Any ideas? I have been able to connect to a KDC using JSR-82 on a Nokia if that helps. What version of the product are you using? On what operating system? Please provide any additional information below. I am using an HTC magic with a 1.6 version of android.

  I'm using this api to connect to a KDC barcode scanner. Everything seems pretty straight forward to use, however it seems to hang when I call pair(). 1. I create my local device - ok 2. Initial a scan - ok 3. The listener reports seeing the KDC 4. When scan is complete, I pick the KDC from the devices 5. Check if it's paired already, return no. 6. call pair("0000"), this is the correct key for the KDC My code is; Log.i("BT", "Pairing ..."); kdc.pair("0000"); Log.i("BT", "Paired"); // *** THIS IS NEVER REACHED *** Any ideas? I have been able to connect to a KDC using JSR-82 on a Nokia if that helps. What version of the product are you using? On what operating system? Please provide any additional information below. I am using an HTC magic with a 1.6 version of android.
• Oct 30, 2009

  issue 6 (Problem with device discovery sample on HTC Hero) commented on by victor.noel.irit   -   Ok, I think that's great :) Thank you for your work!

  Ok, I think that's great :) Thank you for your work!
• Oct 30, 2009

  issue 6 (Problem with device discovery sample on HTC Hero) Status changed by gerdavax   -   Hi all. As officially announced by HTC on their Twitter page: http://twitter.com/htc/status/5243593307 "Hero will be getting an Eclair update" Therefore (and given that I have not an HTC Hero to work with), there is no need to invest for porting the Bluetooth API on this handset that is going to get official Bluetooth support. On the other hand, I'll continue to work to support those handsets (probably HTC Dream and Magic) for which no update plan has been announced. I consider this issue as not applicable to the project.

  Status: WontFix

  Hi all. As officially announced by HTC on their Twitter page: http://twitter.com/htc/status/5243593307 "Hero will be getting an Eclair update" Therefore (and given that I have not an HTC Hero to work with), there is no need to invest for porting the Bluetooth API on this handset that is going to get official Bluetooth support. On the other hand, I'll continue to work to support those handsets (probably HTC Dream and Magic) for which no update plan has been announced. I consider this issue as not applicable to the project.

  Status: WontFix
• Oct 28, 2009

  issue 6 (Problem with device discovery sample on HTC Hero) commented on by konstantin.pribluda   -   Here is logcat from HTC Hero: ----------------------------- 10-28 10:02:48.072: ERROR/AG(115): CIEV: 6,4 10-28 10:02:48.072: INFO/bluetooth_common.cpp(115): com.ti.btips, /com/ti/btips, com.ti.btips.ag, SetIndicatorValue 10-28 10:02:51.062: ERROR/AG(115): CIEV: 6,3 10-28 10:02:51.062: INFO/bluetooth_common.cpp(115): com.ti.btips, /com/ti/btips, com.ti.btips.ag, SetIndicatorValue 10-28 10:02:53.282: VERBOSE/BluetoothDeviceService.cpp(63): startDiscoveryNative 10-28 10:02:53.282: INFO/bluetooth_common.cpp(63): com.ti.btips, /com/ti/btips, com.ti.btips.bmg, SearchByCod 10-28 10:02:53.322: WARN/InputManagerService(63): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@439fe958 10-28 10:02:53.617: VERBOSE/BluetoothEventLoop.cpp(63): COD = 4063492 10-28 10:02:53.632: VERBOSE/BluetoothEventRedirector(346): Received android.bluetooth.intent.action.REMOTE_DEVICE_FOUND 10-28 10:02:53.632: WARN/System.err(22875): action:android.bluetooth.intent.action.REMOTE_DEVICE_FOUND 10-28 10:02:53.642: INFO/System.out(22875): Device found with address 00:0A:3A:88:AE:F3, class 4063492 and rssi -1 10-28 10:02:53.672: VERBOSE/BluetoothEventRedirector(346): Received android.bluetooth.intent.action.REMOTE_NAME_UPDATED 10-28 10:02:54.152: VERBOSE/BluetoothEventLoop.cpp(63): COD = 268 10-28 10:02:54.162: VERBOSE/BluetoothEventRedirector(346): Received android.bluetooth.intent.action.REMOTE_DEVICE_FOUND 10-28 10:02:54.162: WARN/System.err(22875): action:android.bluetooth.intent.action.REMOTE_DEVICE_FOUND 10-28 10:02:54.162: INFO/System.out(22875): Device found with address 00:25:56:D4:BD:76, class 268 and rssi -1 10-28 10:02:54.172: VERBOSE/BluetoothEventRedirector(346): Received android.bluetooth.intent.action.REMOTE_NAME_UPDATED 10-28 10:02:56.392: VERBOSE/BluetoothEventLoop.cpp(63): COD = 5243404 10-28 10:02:56.392: VERBOSE/BluetoothEventRedirector(346): Received android.bluetooth.intent.action.REMOTE_DEVICE_FOUND 10-28 10:02:56.402: WARN/System.err(22875): action:android.bluetooth.intent.action.REMOTE_DEVICE_FOUND 10-28 10:02:56.402: INFO/System.out(22875): Device found with address 00:19:79:D1:6B:26, class 5243404 and rssi -1 10-28 10:02:56.402: VERBOSE/BluetoothEventRedirector(346): Received android.bluetooth.intent.action.REMOTE_NAME_UPDATED 10-28 10:02:57.062: ERROR/AG(115): CIEV: 6,4 10-28 10:02:57.062: INFO/bluetooth_common.cpp(115): com.ti.btips, /com/ti/btips, com.ti.btips.ag, SetIndicatorValue 10-28 10:03:03.592: VERBOSE/BluetoothEventLoop.cpp(63): DiscoveryCompleted signal received 10-28 10:03:03.592: VERBOSE/BluetoothEventRedirector(346): Received android.bluetooth.intent.action.DISCOVERY_COMPLETED 10-28 10:03:03.592: WARN/System.err(22875): action:android.bluetooth.intent.action.DISCOVERY_COMPLETED 10-28 10:03:03.592: VERBOSE/BluetoothDeviceService.cpp(63): getRemoteNameNative 10-28 10:03:03.602: INFO/bluetooth_common.cpp(63): com.ti.btips, /com/ti/btips, com.ti.btips.bmg, GetRemoteDeviceName 10-28 10:03:03.612: WARN/System.err(22875): result:null 10-28 10:03:03.612: INFO/System.out(22875): Device: empty 10-28 10:03:03.612: INFO/System.out(22875): - This is a computer 10-28 10:03:03.612: VERBOSE/BluetoothDeviceService.cpp(63): getRemoteNameNative 10-28 10:03:03.612: INFO/bluetooth_common.cpp(63): com.ti.btips, /com/ti/btips, com.ti.btips.bmg, GetRemoteDeviceName 10-28 10:03:03.632: WARN/System.err(22875): result:null 10-28 10:03:03.632: INFO/System.out(22875): Device: empty 10-28 10:03:03.632: INFO/System.out(22875): - This is a computer 10-28 10:03:03.632: VERBOSE/BluetoothDeviceService.cpp(63): getRemoteNameNative 10-28 10:03:03.632: INFO/bluetooth_common.cpp(63): com.ti.btips, /com/ti/btips, com.ti.btips.bmg, GetRemoteDeviceName 10-28 10:03:03.642: WARN/System.err(22875): result:null 10-28 10:03:03.642: INFO/System.out(22875): Device: empty 10-28 10:03:03.652: INFO/System.out(22875): - This is a phone 10-28 10:03:05.442: VERBOSE/BluetoothEventRedirector(346): Received android.bluetooth.intent.action.REMOTE_NAME_UPDATED 10-28 10:03:05.864: VERBOSE/BluetoothEventRedirector(346): Received android.bluetooth.intent.action.REMOTE_NAME_UPDATED 10-28 10:03:06.472: VERBOSE/BluetoothEventRedirector(346): Received android.bluetooth.intent.action.REMOTE_NAME_UPDATED 10-28 10:06:36.092: ERROR/AG(115): CIEV: 6,5 10-28 10:06:36.092: INFO/bluetooth_common.cpp(115): com.ti.btips, /com/ti/btips, com.ti.btips.ag, SetIndicatorValue 10-28 10:06:42.082: ERROR/AG(115): CIEV: 6,4 10-28 10:06:42.082: INFO/bluetooth_common.cpp(115): com.ti.btips, /com/ti/btips, com.ti.btips.ag, SetIndicatorValue 10-28 10:06:54.092: ERROR/AG(115): CIEV: 6,5 10-28 10:06:54.092: INFO/bluetooth_common.cpp(115): com.ti.btips, /com/ti/btips, com.ti.btips.ag, SetIndicatorValue 10-28 10:06:54.442: DEBUG/dalvikvm(63): GC freed 28433 objects / 1497592 bytes in 319ms 10-28 10:06:57.082: ERROR/AG(115): CIEV: 6,4 10-28 10:06:57.082: INFO/bluetooth_common.cpp(115): com.ti.btips, /com/ti/btips, com.ti.btips.ag, SetIndicatorValue 10-28 10:07:28.752: ERROR/AG(115): CIEV: 6,5 10-28 10:07:28.752: INFO/bluetooth_common.cpp(115): com.ti.btips, /com/ti/btips, com.ti.btips.ag, SetIndicatorValue 10-28 10:07:49.732: ERROR/AG(115): CIEV: 6,4 10-28 10:07:49.732: INFO/bluetooth_common.cpp(115): com.ti.btips, /com/ti/btips, com.ti.btips.ag, SetIndicatorValue -------------------------- ( I guarded that NPE and added some additional output to show actions arriving to BluetoothBroadcastReceiver )

  Here is logcat from HTC Hero: ----------------------------- 10-28 10:02:48.072: ERROR/AG(115): CIEV: 6,4 10-28 10:02:48.072: INFO/bluetooth_common.cpp(115): com.ti.btips, /com/ti/btips, com.ti.btips.ag, SetIndicatorValue 10-28 10:02:51.062: ERROR/AG(115): CIEV: 6,3 10-28 10:02:51.062: INFO/bluetooth_common.cpp(115): com.ti.btips, /com/ti/btips, com.ti.btips.ag, SetIndicatorValue 10-28 10:02:53.282: VERBOSE/BluetoothDeviceService.cpp(63): startDiscoveryNative 10-28 10:02:53.282: INFO/bluetooth_common.cpp(63): com.ti.btips, /com/ti/btips, com.ti.btips.bmg, SearchByCod 10-28 10:02:53.322: WARN/InputManagerService(63): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@439fe958 10-28 10:02:53.617: VERBOSE/BluetoothEventLoop.cpp(63): COD = 4063492 10-28 10:02:53.632: VERBOSE/BluetoothEventRedirector(346): Received android.bluetooth.intent.action.REMOTE_DEVICE_FOUND 10-28 10:02:53.632: WARN/System.err(22875): action:android.bluetooth.intent.action.REMOTE_DEVICE_FOUND 10-28 10:02:53.642: INFO/System.out(22875): Device found with address 00:0A:3A:88:AE:F3, class 4063492 and rssi -1 10-28 10:02:53.672: VERBOSE/BluetoothEventRedirector(346): Received android.bluetooth.intent.action.REMOTE_NAME_UPDATED 10-28 10:02:54.152: VERBOSE/BluetoothEventLoop.cpp(63): COD = 268 10-28 10:02:54.162: VERBOSE/BluetoothEventRedirector(346): Received android.bluetooth.intent.action.REMOTE_DEVICE_FOUND 10-28 10:02:54.162: WARN/System.err(22875): action:android.bluetooth.intent.action.REMOTE_DEVICE_FOUND 10-28 10:02:54.162: INFO/System.out(22875): Device found with address 00:25:56:D4:BD:76, class 268 and rssi -1 10-28 10:02:54.172: VERBOSE/BluetoothEventRedirector(346): Received android.bluetooth.intent.action.REMOTE_NAME_UPDATED 10-28 10:02:56.392: VERBOSE/BluetoothEventLoop.cpp(63): COD = 5243404 10-28 10:02:56.392: VERBOSE/BluetoothEventRedirector(346): Received android.bluetooth.intent.action.REMOTE_DEVICE_FOUND 10-28 10:02:56.402: WARN/System.err(22875): action:android.bluetooth.intent.action.REMOTE_DEVICE_FOUND 10-28 10:02:56.402: INFO/System.out(22875): Device found with address 00:19:79:D1:6B:26, class 5243404 and rssi -1 10-28 10:02:56.402: VERBOSE/BluetoothEventRedirector(346): Received android.bluetooth.intent.action.REMOTE_NAME_UPDATED 10-28 10:02:57.062: ERROR/AG(115): CIEV: 6,4 10-28 10:02:57.062: INFO/bluetooth_common.cpp(115): com.ti.btips, /com/ti/btips, com.ti.btips.ag, SetIndicatorValue 10-28 10:03:03.592: VERBOSE/BluetoothEventLoop.cpp(63): DiscoveryCompleted signal received 10-28 10:03:03.592: VERBOSE/BluetoothEventRedirector(346): Received android.bluetooth.intent.action.DISCOVERY_COMPLETED 10-28 10:03:03.592: WARN/System.err(22875): action:android.bluetooth.intent.action.DISCOVERY_COMPLETED 10-28 10:03:03.592: VERBOSE/BluetoothDeviceService.cpp(63): getRemoteNameNative 10-28 10:03:03.602: INFO/bluetooth_common.cpp(63): com.ti.btips, /com/ti/btips, com.ti.btips.bmg, GetRemoteDeviceName 10-28 10:03:03.612: WARN/System.err(22875): result:null 10-28 10:03:03.612: INFO/System.out(22875): Device: empty 10-28 10:03:03.612: INFO/System.out(22875): - This is a computer 10-28 10:03:03.612: VERBOSE/BluetoothDeviceService.cpp(63): getRemoteNameNative 10-28 10:03:03.612: INFO/bluetooth_common.cpp(63): com.ti.btips, /com/ti/btips, com.ti.btips.bmg, GetRemoteDeviceName 10-28 10:03:03.632: WARN/System.err(22875): result:null 10-28 10:03:03.632: INFO/System.out(22875): Device: empty 10-28 10:03:03.632: INFO/System.out(22875): - This is a computer 10-28 10:03:03.632: VERBOSE/BluetoothDeviceService.cpp(63): getRemoteNameNative 10-28 10:03:03.632: INFO/bluetooth_common.cpp(63): com.ti.btips, /com/ti/btips, com.ti.btips.bmg, GetRemoteDeviceName 10-28 10:03:03.642: WARN/System.err(22875): result:null 10-28 10:03:03.642: INFO/System.out(22875): Device: empty 10-28 10:03:03.652: INFO/System.out(22875): - This is a phone 10-28 10:03:05.442: VERBOSE/BluetoothEventRedirector(346): Received android.bluetooth.intent.action.REMOTE_NAME_UPDATED 10-28 10:03:05.864: VERBOSE/BluetoothEventRedirector(346): Received android.bluetooth.intent.action.REMOTE_NAME_UPDATED 10-28 10:03:06.472: VERBOSE/BluetoothEventRedirector(346): Received android.bluetooth.intent.action.REMOTE_NAME_UPDATED 10-28 10:06:36.092: ERROR/AG(115): CIEV: 6,5 10-28 10:06:36.092: INFO/bluetooth_common.cpp(115): com.ti.btips, /com/ti/btips, com.ti.btips.ag, SetIndicatorValue 10-28 10:06:42.082: ERROR/AG(115): CIEV: 6,4 10-28 10:06:42.082: INFO/bluetooth_common.cpp(115): com.ti.btips, /com/ti/btips, com.ti.btips.ag, SetIndicatorValue 10-28 10:06:54.092: ERROR/AG(115): CIEV: 6,5 10-28 10:06:54.092: INFO/bluetooth_common.cpp(115): com.ti.btips, /com/ti/btips, com.ti.btips.ag, SetIndicatorValue 10-28 10:06:54.442: DEBUG/dalvikvm(63): GC freed 28433 objects / 1497592 bytes in 319ms 10-28 10:06:57.082: ERROR/AG(115): CIEV: 6,4 10-28 10:06:57.082: INFO/bluetooth_common.cpp(115): com.ti.btips, /com/ti/btips, com.ti.btips.ag, SetIndicatorValue 10-28 10:07:28.752: ERROR/AG(115): CIEV: 6,5 10-28 10:07:28.752: INFO/bluetooth_common.cpp(115): com.ti.btips, /com/ti/btips, com.ti.btips.ag, SetIndicatorValue 10-28 10:07:49.732: ERROR/AG(115): CIEV: 6,4 10-28 10:07:49.732: INFO/bluetooth_common.cpp(115): com.ti.btips, /com/ti/btips, com.ti.btips.ag, SetIndicatorValue -------------------------- ( I guarded that NPE and added some additional output to show actions arriving to BluetoothBroadcastReceiver )
• Oct 27, 2009

  issue 6 (Problem with device discovery sample on HTC Hero) commented on by victor.noel.irit   -   Obviously, it will take some time to have Android 2.0 on already released device and maybe they will not support JSR-82 like Bluecove do it.

  Obviously, it will take some time to have Android 2.0 on already released device and maybe they will not support JSR-82 like Bluecove do it.
• Oct 27, 2009

  BluetoothAPIHowto (This page will contain code snippets to show how to use the ...) Wiki page commented on by mickamusset   -   Hi, I would like to know if at this state we can dialog we a PC ? And if it is possible do you have a sample code ? just a basic one. ( server and client side ) thanks a lot

  Hi, I would like to know if at this state we can dialog we a PC ? And if it is possible do you have a sample code ? just a basic one. ( server and client side ) thanks a lot
• Oct 27, 2009

  issue 6 (Problem with device discovery sample on HTC Hero) commented on by gerdavax   -   Maybe it is no longer required: http://android-developers.blogspot.com/2009/10/announcing-android-20-support-in-sdk.html

  Maybe it is no longer required: http://android-developers.blogspot.com/2009/10/announcing-android-20-support-in-sdk.html
• Oct 27, 2009

  issue 6 (Problem with device discovery sample on HTC Hero) commented on by victor.noel.irit   -   Hello, why not work in conjunction with the guys from Bluecove that are working on it, maybe they can help you for this matter. See: http://groups.google.com/group/bluecove-developers/browse_thread/thread/a05875b928c89dc2

  Hello, why not work in conjunction with the guys from Bluecove that are working on it, maybe they can help you for this matter. See: http://groups.google.com/group/bluecove-developers/browse_thread/thread/a05875b928c89dc2
• Oct 27, 2009

  issue 6 (Problem with device discovery sample on HTC Hero) commented on by gerdavax   -   Hi all. Unfortunately I have not an HTC Hero nor I can purchase one in a short time. To do investigation on this device I definitively need to have it for one or two weeks, to understand at least if there is a workaround to let the library running on it or we have to consider this handset as not compatible. Stefano.

  Hi all. Unfortunately I have not an HTC Hero nor I can purchase one in a short time. To do investigation on this device I definitively need to have it for one or two weeks, to understand at least if there is a workaround to let the library running on it or we have to consider this handset as not compatible. Stefano.
• Oct 27, 2009

  issue 6 (Problem with device discovery sample on HTC Hero) commented on by konstantin.pribluda   -   Mea culpa - Problem is definitely there.

  Mea culpa - Problem is definitely there.
• Oct 27, 2009

  issue 6 (Problem with device discovery sample on HTC Hero) commented on by konstantin.pribluda   -   I just checked out today, and build them with 1.5 contained in 1.6 SDK

  I just checked out today, and build them with 1.5 contained in 1.6 SDK
• Oct 27, 2009

  issue 6 (Problem with device discovery sample on HTC Hero) commented on by victor.noel.irit   -   When you say that you tried samples, do you mean those on the svn or those on the market? If I recall correctly, I tried both and none worked (the name of the devices was always ERROR).

  When you say that you tried samples, do you mean those on the svn or those on the market? If I recall correctly, I tried both and none worked (the name of the devices was always ERROR).
• Oct 27, 2009

  issue 6 (Problem with device discovery sample on HTC Hero) commented on by jacek.ku...@gmail.com   -   That's good news. I'll have to upgrade to the latest ROM and check. Did you build the samples with SDK 1.6 or did you use the Market version?

  That's good news. I'll have to upgrade to the latest ROM and check. Did you build the samples with SDK 1.6 or did you use the Market version?
• Oct 27, 2009

  issue 6 (Problem with device discovery sample on HTC Hero) commented on by konstantin.pribluda   -   I tried samples today on HTC Hero ( 1.5, latest ROM build, unbranded ) and it worked. My environment: Idea 9 EAP, Ubuntu , SDK 1.6

  I tried samples today on HTC Hero ( 1.5, latest ROM build, unbranded ) and it worked. My environment: Idea 9 EAP, Ubuntu , SDK 1.6
• Oct 26, 2009

  issue 12 (sending string from one phone to another) commented on by christian.frank.schneider   -   I installed the original ROM now but it also wont work. Here's my adb logcat output: I/ActivityManager( 1052): Start proc priv.s2 for activity priv.s2/.rccar.RCCar: pid=1598 uid=10036 gids={3002, 3001} I/dalvikvm( 1598): Debugger thread not active, ignoring DDM send (t=0x41504e4d l=38) I/dalvikvm( 1598): Debugger thread not active, ignoring DDM send (t=0x41504e4d l=18) W/Resources( 1598): Converting to string: TypedValue{t=0x12/d=0x0 a=2 r=0x7f050001} D/LocalBluetoothDevice( 1598): _localDevice is null D/BluetoothBroadcastReceiver( 1598): Registering I/ActivityManager( 1052): Displayed activity priv.s2/.rccar.RCCar: 852 ms D/dalvikvm( 1134): GC freed 7838 objects / 441008 bytes in 156ms D/InetAddress( 1134): android.clients.google.com: 74.125.43.101 (family 2, proto 6) D/InetAddress( 1134): android.clients.google.com: 74.125.43.113 (family 2, proto 6) D/InetAddress( 1134): android.clients.google.com: 74.125.43.102 (family 2, proto 6) D/InetAddress( 1134): android.clients.google.com: 74.125.43.138 (family 2, proto 6) D/InetAddress( 1134): android.clients.google.com: 74.125.43.139 (family 2, proto 6) D/InetAddress( 1134): android.clients.google.com: 74.125.43.100 (family 2, proto 6) D/dalvikvm( 1099): GC freed 1696 objects / 80496 bytes in 252ms D/dalvikvm( 1134): GC freed 8490 objects / 560880 bytes in 121ms D/dalvikvm( 1134): GC freed 7340 objects / 524936 bytes in 109ms D/dalvikvm( 1134): GC freed 9106 objects / 515504 bytes in 111ms I/CheckinService( 1052): Checkin triggered: Intent { action=android.server.checkin.CHECKIN (has extras) }, market only = true I/ActivityManager( 1052): Stopping service: com.android.vending/.PackageMonitorReceiver$UpdateCheckinDatabaseService I/CheckinService( 1052): Sending checkin request (905 bytes)... D/InetAddress( 1052): android.clients.google.com: 74.125.39.113 (family 2, proto 6) D/InetAddress( 1052): android.clients.google.com: 74.125.39.102 (family 2, proto 6) D/InetAddress( 1052): android.clients.google.com: 74.125.39.101 (family 2, proto 6) D/InetAddress( 1052): android.clients.google.com: 74.125.39.138 (family 2, proto 6) D/InetAddress( 1052): android.clients.google.com: 74.125.39.139 (family 2, proto 6) D/InetAddress( 1052): android.clients.google.com: 74.125.39.100 (family 2, proto 6) D/dalvikvm( 1052): GC freed 12187 objects / 737960 bytes in 185ms D/dalvikvm( 1052): GC freed 15138 objects / 1077528 bytes in 187ms I/ActivityManager( 1052): Process com.google.android.apps.maps:FriendService (pid 1195) has died. D/dalvikvm( 1582): GC freed 2694 objects / 196416 bytes in 181ms I/CheckinService( 1052): From server: Intent { action=android.server.checkin.FOTA_CANCEL } V/CheckinService( 1052): Disabling timed checkins (interval: 0 secs) I/NotificationService( 1052): enqueueToast pkg=priv.s2 callback=android.app.ITransientNotification$Stub$Proxy@4333ca18 duration=1 I/NotificationService( 1052): enqueueToast pkg=priv.s2 callback=android.app.ITransientNotification$Stub$Proxy@43323de0 duration=1 E/BLZ_WRAPPER( 1598): btl_if_socket : blz wrapper not initialized I/ActivityManager( 1052): Process priv.s2 (pid 1598) has died. I/WindowManager( 1052): WIN DEATH: Window{434d1928 priv.s2/priv.s2.rccar.RCCar paused=false} D/Zygote ( 1014): Process 1598 exited cleanly (1) I/Launcher( 1099): onResume mRestoring = false W/InputManagerService( 1052): Got RemoteException sending setActive(false) notification to pid 1598 uid 10036 W/NotificationService( 1052): Object died trying to hide notification android.app.ITransientNotification$Stub$Proxy@4333ca18 in package priv.s2 W/ActivityManager( 1052): setProcessForeground called on unknown pid: 1598 W/NotificationService( 1052): Object died trying to show notification android.app.ITransientNotification$Stub$Proxy@43323de0 in package priv.s2 W/ActivityManager( 1052): setProcessForeground called on unknown pid: 1598 D/dalvikvm( 1094): GC freed 8969 objects / 525600 bytes in 211ms

  I installed the original ROM now but it also wont work. Here's my adb logcat output: I/ActivityManager( 1052): Start proc priv.s2 for activity priv.s2/.rccar.RCCar: pid=1598 uid=10036 gids={3002, 3001} I/dalvikvm( 1598): Debugger thread not active, ignoring DDM send (t=0x41504e4d l=38) I/dalvikvm( 1598): Debugger thread not active, ignoring DDM send (t=0x41504e4d l=18) W/Resources( 1598): Converting to string: TypedValue{t=0x12/d=0x0 a=2 r=0x7f050001} D/LocalBluetoothDevice( 1598): _localDevice is null D/BluetoothBroadcastReceiver( 1598): Registering I/ActivityManager( 1052): Displayed activity priv.s2/.rccar.RCCar: 852 ms D/dalvikvm( 1134): GC freed 7838 objects / 441008 bytes in 156ms D/InetAddress( 1134): android.clients.google.com: 74.125.43.101 (family 2, proto 6) D/InetAddress( 1134): android.clients.google.com: 74.125.43.113 (family 2, proto 6) D/InetAddress( 1134): android.clients.google.com: 74.125.43.102 (family 2, proto 6) D/InetAddress( 1134): android.clients.google.com: 74.125.43.138 (family 2, proto 6) D/InetAddress( 1134): android.clients.google.com: 74.125.43.139 (family 2, proto 6) D/InetAddress( 1134): android.clients.google.com: 74.125.43.100 (family 2, proto 6) D/dalvikvm( 1099): GC freed 1696 objects / 80496 bytes in 252ms D/dalvikvm( 1134): GC freed 8490 objects / 560880 bytes in 121ms D/dalvikvm( 1134): GC freed 7340 objects / 524936 bytes in 109ms D/dalvikvm( 1134): GC freed 9106 objects / 515504 bytes in 111ms I/CheckinService( 1052): Checkin triggered: Intent { action=android.server.checkin.CHECKIN (has extras) }, market only = true I/ActivityManager( 1052): Stopping service: com.android.vending/.PackageMonitorReceiver$UpdateCheckinDatabaseService I/CheckinService( 1052): Sending checkin request (905 bytes)... D/InetAddress( 1052): android.clients.google.com: 74.125.39.113 (family 2, proto 6) D/InetAddress( 1052): android.clients.google.com: 74.125.39.102 (family 2, proto 6) D/InetAddress( 1052): android.clients.google.com: 74.125.39.101 (family 2, proto 6) D/InetAddress( 1052): android.clients.google.com: 74.125.39.138 (family 2, proto 6) D/InetAddress( 1052): android.clients.google.com: 74.125.39.139 (family 2, proto 6) D/InetAddress( 1052): android.clients.google.com: 74.125.39.100 (family 2, proto 6) D/dalvikvm( 1052): GC freed 12187 objects / 737960 bytes in 185ms D/dalvikvm( 1052): GC freed 15138 objects / 1077528 bytes in 187ms I/ActivityManager( 1052): Process com.google.android.apps.maps:FriendService (pid 1195) has died. D/dalvikvm( 1582): GC freed 2694 objects / 196416 bytes in 181ms I/CheckinService( 1052): From server: Intent { action=android.server.checkin.FOTA_CANCEL } V/CheckinService( 1052): Disabling timed checkins (interval: 0 secs) I/NotificationService( 1052): enqueueToast pkg=priv.s2 callback=android.app.ITransientNotification$Stub$Proxy@4333ca18 duration=1 I/NotificationService( 1052): enqueueToast pkg=priv.s2 callback=android.app.ITransientNotification$Stub$Proxy@43323de0 duration=1 E/BLZ_WRAPPER( 1598): btl_if_socket : blz wrapper not initialized I/ActivityManager( 1052): Process priv.s2 (pid 1598) has died. I/WindowManager( 1052): WIN DEATH: Window{434d1928 priv.s2/priv.s2.rccar.RCCar paused=false} D/Zygote ( 1014): Process 1598 exited cleanly (1) I/Launcher( 1099): onResume mRestoring = false W/InputManagerService( 1052): Got RemoteException sending setActive(false) notification to pid 1598 uid 10036 W/NotificationService( 1052): Object died trying to hide notification android.app.ITransientNotification$Stub$Proxy@4333ca18 in package priv.s2 W/ActivityManager( 1052): setProcessForeground called on unknown pid: 1598 W/NotificationService( 1052): Object died trying to show notification android.app.ITransientNotification$Stub$Proxy@43323de0 in package priv.s2 W/ActivityManager( 1052): setProcessForeground called on unknown pid: 1598 D/dalvikvm( 1094): GC freed 8969 objects / 525600 bytes in 211ms
• Oct 26, 2009

  issue 12 (sending string from one phone to another) commented on by christian.frank.schneider   -   btw. hcitool dev and hciconfig -a gives no output. Maybe the reason is our custom rom (galaxo). I try to flash it back today.

  btw. hcitool dev and hciconfig -a gives no output. Maybe the reason is our custom rom (galaxo). I try to flash it back today.
• Oct 25, 2009

  issue 12 (sending string from one phone to another) commented on by christian.frank.schneider   -   I have the same error: "blz wrapper not initialized" Any idea how to fix?

  I have the same error: "blz wrapper not initialized" Any idea how to fix?