Dear All, I've tried to post in this thread earlier, but not sure if it worked so I decided to duplicate my message.
So, thanks for a lot of useful information, it was a blast to read this thread while connecting android 4.0 phone with Nonin Oximeter sensor. Everything seems to work fine, sensor is connected to a phone through application and a green indicator is on. But when it comes to interpreting the data, I might need some tips. I receive a raw data (54 bytes) from sensor which represents an associate request. Then my manager should reply on this request choosing from the following options: (a) accept (b) unknown configuration (c) accepted with extended configuration I send a respond (b) and get 140 bytes with as I guess sensor's configuration. I can also send a attribute request and the sensor response with 188 bytes including the name of the company and type of sensor. I am a bit lost in all these bytes, requests, responses. Does anyone have any tips or approach for interpreting sensor data? regards, Gregory Den torsdagen den 15:e december 2011 kl. 18:30:08 UTC+1 skrev jfernandez: > > Hi all, > > I'm executing the Bluetooth HDP Demo [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 > connection HDP. > > 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 [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
