Hi , I still see the issue with my Nonin device even on Android 4.0.3. here is what is see in my log,
using demo sample i am able to connect to the device but i am not getting any data from the device Any help? I//system/bin/bluetoothd( 1198): bluetoothd[1199]: external/bluetooth/ bluez/plugins/hciops.c:conn_complete() status 0x00 I//system/bin/bluetoothd( 1198): bluetoothd[1199]: external/bluetooth/ bluez/src/adapter.c:adapter_get_device() 00:1C:05:00:49:4A D/BluetoothEventLoop( 1089): Device property changed: 00:1C: 05:00:49:4A property: Connected value: true I//system/bin/bluetoothd( 1198): bluetoothd[1199]: external/bluetooth/ bluez/plugins/hciops.c:remote_features_information() hci0 status 0 I//system/bin/bluetoothd( 1198): bluetoothd[1199]: external/bluetooth/ bluez/plugins/hciops.c:remote_name_information() hci0 status 0 E/BluetoothEventLoop.cpp( 1089): onHealthDeviceConnectionResult: D-Bus error: org.bluez.Error.HealthError (No matching MDEP found) D/BluetoothEventLoop( 1089): onHealthDeviceConnectionResult 1 6001 I//system/bin/bluetoothd( 1198): bluetoothd[1199]: external/bluetooth/ bluez/plugins/hciops.c:disconn_complete() handle 1 status 0x00 I//system/bin/bluetoothd( 1198): bluetoothd[1199]: external/bluetooth/ bluez/src/event.c:btd_event_disconn_complete() I//system/bin/bluetoothd( 1198): bluetoothd[1199]: external/bluetooth/ bluez/src/adapter.c:adapter_remove_connection() D/BluetoothEventLoop( 1089): Device property changed: 00:1C: 05:00:49:4A property: Connected value: false W/ThrottleService( 1089): unable to find stats for iface rmnet0 I/power ( 1089): *** set_screen_state 0 D/SurfaceFlinger( 125): About to give-up screen, flinger = 0x1420918 W/ProcessStats( 1089): Skipping unknown process pid 1620 W/NetworkManagementSocketTagger( 1089): setKernelCountSet(10048, 0) failed with errno -2 D/dalvikvm( 1089): GC_CONCURRENT freed 629K, 14% free 8879K/10247K, paused 5ms+4ms On Jan 14, 6:07 am, jfernandez <[email protected]> wrote: > Hi Fernando, > > I have introduced a change in the implementation of the > BluetoothHealthCallback mHealthCallback. Exactly, in its method > onHealthChannelStateChange(...). I detected that the state machine > during the stablishment of a new HDP connection is: Disconnected- > Connecting-Connected. However, you can see that the example is > checking the case Disconnected-Connected, but not the case Connecting- > Connected. I added this new case Connecting-Connected, and now it > works and I'm able to read/write data from/to UA-767PBT-C and a board > that emulates several biomedical devices. > > I hope it help you. > > Regards. > > On 14 ene, 12:35, Fernando Almeida <[email protected]> wrote: > > > > > > > > > Hi jfernandez... i upgrade my android version to 4.03 and still can't > > connect... > > > Could you please show me the changes that you made? > > > Thank you > > > On 13 Jan, 10:57, jfernandez <[email protected]> > > wrote: > > > > Hi again, > > > > Well, after upgrading my Android 4.0 to 4.03, and adding some changes > > > to the BluetoothHDPsample, I'm able to connect to the biomedical > > > device, as well as I'm able to read/write data from/to theHDP > > > channel. So, it seems the problem has been fixed in this new Android > > > version. > > > > Regards. > > > > On 15 dic 2011, 18:30, jfernandez <[email protected]> > > > wrote: > > > > > Hi all, > > > > > I'm executing theBluetoothHDPDemo [1] (offered from Android 4.0 > > > > Ice Cream Sandwich) in my Android smartphone. When I have registered > > > > the application in order to receive data, and I have paired the > > > > biomedical device with the smartphone, I try to open the channel > > > > connection and I can see that the device starts sending data to the > > > > smartphone. However, the smartphone is unable to open the channel > > > > connectionHDP. > > > > > At the end of this message you can see the output obtained in the > > > > LogCat. > > > > > Has anybody achieved to run successfully this sample about the use of > > > > theBluetoothHealth Profile API? Any ideas? > > > > > Thanks. Regards. > > > > > [1]http://developer.android.com/resources/samples/BluetoothHDP/index.html > > > > > This is the log that I obtain: > > > > > 12-15 16:40:54.048: I/BluetoothHDPService(1105): connectChannel() > > > > 12-15 16:40:54.068: D/BluetoothService(147): CONNECTION_STATE_CHANGE: > > > > 00:80:25:14:A1:BC: 0 -> 1 > > > > 12-15 16:40:55.169: D/ConnectivityService(147): > > > > handleInetConditionHoldEnd: net=1, condition=0, published condition=0 > > > > 12-15 16:40:59.393: D/BluetoothEventLoop(147): Device property > > > > changed: 00:80:25:14:A1:BC property: Connected value: true > > > > 12-15 16:41:00.024: D/BluetoothEventLoop(147): Health Device : > > > > devicePath: /org/bluez/278/hci0/dev_00_80_25_14_A1_BC:channelPath:/org/ > > > >bluez/278/hci0/dev_00_80_25_14_A1_BC/chan3115:existstrue > > > > 12-15 16:41:00.034: E/BluetoothService.cpp(147): > > > > getChannelApplicationNative > > > > 12-15 16:41:00.044: E/bluetooth_common.cpp(147): > > > > dbus_func_args_timeout_valist: D-Bus error in Acquire: > > > > org.bluez.Error.HealthError (Cannot reconnect: MDL is not closed) > > > > 12-15 16:41:00.044: E/BluetoothHealthProfileHandler(147): Error > > > > obtaining fd for channel:/org/bluez/278/hci0/dev_00_80_25_14_A1_BC/ > > > > chan3115 > > > > 12-15 16:41:00.074: E/BluetoothService.cpp(147): destroyChannelNative > > > > 12-15 16:41:00.074: E/BluetoothEventLoop.cpp(147): > > > > onHealthDeviceConnectionResult: D-Bus error: > > > > org.bluez.Error.HealthError (Mdl is not created) > > > > 12-15 16:41:00.074: D/BluetoothEventLoop(147): > > > > onHealthDeviceConnectionResult 2 6001 > > > > 12-15 16:41:00.214: D/BluetoothEventLoop(147): > > > > onHealthDeviceConnectionResult 2 6000 > > > > 12-15 16:41:00.214: D/BluetoothEventLoop(147): Health Device : Name of > > > > Property is: MainChannel Value:/org/bluez/278/hci0/ > > > > dev_00_80_25_14_A1_BC/chan3115 -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
