HI Jorge, thanks that solves the problem, now i can see the data from the Nonin.
Regards Vijay On Mon, Jan 23, 2012 at 3:13 AM, jfernandez < [email protected]> wrote: > Hi vijay, > > I'm seeing that you obtain the following error: > > onHealthDeviceConnectionResult: D-Bus > error: org.bluez.Error.HealthError (No matching MDEP found) > > I guess your Nonin device is a pulse oximeter. Are you sure you are > registering in the HDP code an application interesting in pulse > oximeter data type (0x1004)? > > Regards. > > On 20 ene, 23:39, vijay <[email protected]> wrote: > > could you please share the changes need to get it working. > > connection seems to working but i don't see data coming to device > > running Android 4.0.3 > > > > On Jan 20, 10:00 am, Raul Ruiz <[email protected]> wrote: > > > > > > > > > > > > > > > > > Hi all, > > > > > I have Nonin working withHDP, if someone need help tell me. > > > > > On 14 ene, 13:07, 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 newHDPconnection 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 > -- 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
