Hey guys! It was a blast to read your thread while I was trying to connect android 4.0 phone with Nonin Oximeter last months.
The connection works fine and I can see green indicator together with "Connected" section on the screen. Then it was time to implement a manager and that is when I got some problems. So I am able to receive (as a raw data) 54 bytes which look as following: "e2000032800000000001002a5079002680..." As I figured out from IEEE 11073-10404 specifications this first byte array is sending an associate request, on which my manager has to reply using one of the options: (a) accept (b) unknown configuration (c) accept with unknown configuration I will describe next steps I decided to take, but first I just wanna make sure that i am on the right way. Let me know if I got it all wrong. Any tips are appreciated. regards, Gregory On Feb 9, 4:04 pm, jfernandez <jorge.fernandez.gonza...@gmail.com> wrote: > Hi Chenchen and Ming, > > Sorry for the delay. I think you are right Chenchen, I obtain the same > behaviour, so, I guess the problem is in the Android source code... > Well, we will wait for a new Android release solving this issue. > > Regards. > > On 9 feb, 15:58, Ming <ming030...@gmail.com> wrote: > > > > > > > > > Exactly same problem with you. > > I am using UA-767-PBT-C > > After connected to the device, I can see the Connection State is > > "Connected" and "Reading data..." and a green icon. > > However, I can never see data. > > In log ,I keep receiving dalvikm - GC_CONCURRENT freed 494K ..., and > > sometime even reboot! > > Do u solve the problem? Thank You. > > > On Feb 2, 7:05 pm, jfernandez <jorge.fernandez.gonza...@gmail.com> > > wrote: > > > > Hi all, > > > > I have observed a strange and undesirable behaviour that I'm going to > > > describe. When anHDPchannel 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 > > > > 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 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