Hi Fernandez, I have the same problem. I think it is because the bluetooth does not close properly. In my case, I didn't touch the default state machine and it does not turn off the blue color bluetooth logo after the measurement is finished. And Connection State is still CONNECTED. Which is very weird. Have you encountering the same problem?
Thanks and regards, Chenchen On Feb 2, 3:05 am, jfernandez <jorge.fernandez.gonza...@gmail.com> wrote: > Hi all, > > I have observed a strange and undesirable behaviour that I'm going to > describe. When an HDP channel is stablished, the Android system starts > a long proccess of freeing memory (I have lots of Logcat messages like > "dalvikm - GC_CONCURRENT freed 494K ..."), even in some occasions, the > system crashes and the smartphone is rebooted. I don't know if this is > a problem of my ROM/smartphone (I'm using Android 4.0.3 ICS). Does > anybody has the same problem? > > Thanks and regards! > > On 15 dic 2011, 18:30, jfernandez <jorge.fernandez.gonza...@gmail.com> > wrote: > > > > > > > > > Hi all, > > > I'm executing the BluetoothHDPDemo [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 isunableto 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 > > the Bluetooth Health 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 android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
