Hi Chenchen, I'm trying connecting UA-767PBT.-C to android manager that i did and it connect and disconnect all time. I don't know how do you do connection to get read thread and get the association request. If you get something tell me. With Nonin i establish connection and i get 0 bytes all time.
Its problem of L2CAP. BlueZ developers in 4.97 version fixed bug. On 4 ene, 23:35, Chenchen <chenchen.zh...@gmail.com> wrote: > Dear Raul, > > I'm playing around with UA-767PBT-C, and find that I could be able to > get the association request by printing log in read thread: > 01-04 13:46:49.652: I/BluetoothHDPService(7249): > e200 > 0032 > 80000000 > 0001002a > 5079 > 0026 > 80000000 > 8000 //?? not 0xA0 > 80000000 > 00000000 > 00800000 > 0008 > 00091ffffe8002be > 02bc > 0081 //?? 0x01, 0x00 > 0100 > > However, I don't know what is the right now to write association > response back. > > On Dec 16 2011, 6:54 am, Raul Ruiz <spekwh...@gmail.com> wrote: > > > > > > > > > Well we have same trouble. I have UA-767PBT-C device too and with HDP > > Demo doesnt connect. > > > Im doing a program that receive ACL_CONNECT from device and opens a > > channel. > > In the program, Health service is use by android BT and the link is > > connected but device is in CONNECTING_STATE and then drops down. > > Using a BT sniffer like HCIDUMP, i watch that android BT doest send > > CONNECT RSP to device and I think that this is the problem. > > > If you want some help tell me i will continue working in this. > > > PD: Me too check this in linux, and it works finelly.I think that dbus > > library is different. > > > On 16 dic, 12:29, jfernandez <jorge.fernandez.gonza...@gmail.com> > > wrote: > > > > On 16 dic, 11:31, Raul Ruiz <spekwh...@gmail.com> wrote: > > > > > Hi Jorge, > > > > Hi Raul, > > > > > What device are you using? I have a same problem using Nonin 9560BT > > > > pulseoximeter. It conects and disconnects and any data had received in > > > > the Android. > > > > I'm working with a board which is able to simulate several biomedical > > > devices. > > > > On the other hand, I have a real device (blood pressure monitor > > > UA-767PBT-C). In that case, the device opens the HDP channel > > > automatically with the smartphone which acts as sink. But the truth is > > > that I don't see anything in the LogCat related to this channel. > > > However, if I try opening the connection channel from the HDP Demo > > > Application, I obtain the same error. > > > > Anyway, I have checked all of this in a Linux laptop using the same > > > BlueZ stack that we have in Android and everything works fine. > > > > > Do you have any solution? > > > > Not yet. I'm expecting some feedback. > > > > > Thanks > > > > > On Dec 15, 6:30 pm, 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 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 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
