> Hi all.
> I've found a HDP application on Google Play.
> https://play.google.com/store/apps/details?id=jp.littlesoftware.dnet.bts

> I think that It's the only HDP application with HDP API in the world.
> It can communicate with these devices.
> A&D UC-321PBT-C
> A&D UA-767PBT-C
> A&D UC-411PBT-C

> I don't have any of them.
> So I want someone who have these devices to check the steps below.

> 1.communicate with the device.
> 2.kill the app proccess or turn off Bluetooth in Android config.
> 3.try to recommunicate.

> If you can recommunicate in step3, the application would unregister
> AppConfig correctly.
> And we can say that, there are some way to unregister AppConfig correctly
> and make HDP application what works fine.

> Thanks.

> On Tuesday, July 17, 2012 8:07:58 PM UTC+9, wambin wrote:

>> For my 6 monthes reseach, I understand that below.
>> No one can build Android HDP application with this HDP API.
>> (Some people built HDP app to use Bluez with JNI. search in youtube.)
>> I cann't find any Android HDP app in markets.
>> (it has taken 6 monthes over since HDP API to be published!)
>> So many people have troubles about HDP demo.
>> Android API developers don't take any action about it.
>> (4.1.1 jellybean has same problems
>> http://code.google.com/p/android/issues/detail?id=26704&can=1&q=hdp&c...
>> )

>> The only way to report the problem to Android API developers is Google
>> group Android.
>> (http://code.google.com/p/android/issues/list)
>> developer.android.com dosen't publish mail address but provide this
>> forum.
>> I want to add star to the HDP issues(
>> http://code.google.com/p/android/issues/detail?id=26704&q=hdp&colspec...)
>> API developers to see, if no one has solution.

>> Regards.

>> On Tuesday, July 17, 2012 4:49:41 PM UTC+9, jfernandez wrote:

>>> Hi wambin,

>>> Then, you have found the same troubles that all of us.

>>> Regards.

>>> On Tue, Jul 17, 2012 at 7:59 AM, wambin <ambiti...@gmail.com> wrote:
>>> > Hi, thanks to reply.
>>> > The problem is that ApplicationConfiguration remain, in spite of
>>> calling
>>> > unregisterAppConfiguration().
>>> > I confirmed the demo can communicate with a health device at first
>>> time, but
>>> > second time or later it cann't.
>>> > Sometimes Android reboots when I unregister the application config and
>>> > REregister.
>>> > The demo can communicate only once whenever rebooting.

>>> > My health devices
>>> > blood pressure: HEM-7081-IT
>>> > weighing machine: HBF-206IT
>>> > pedometer: HJ-720IT

>>> > I can communicate currectly with all of these devices and get health
>>> > data.(only once whenever rebooting)

>>> > On Thursday, July 12, 2012 6:06:55 PM UTC+9, jfernandez wrote:

>>> >> Hi wambin:

>>> >> Could you tell more about the exact problem that you are
>>> experiencing?
>>> >> And, what's the medical device that you are using?

>>> >> Regards.

>>> >> On Tue, Jul 10, 2012 at 12:16 PM, wambin <ambiti...@gmail.com>
>>> wrote:
>>> >> > Hi jfernandez and all.

>>> >> > I've had the same problem for half a year.
>>> >> > My device is Galaxy Nexus SC-04D ver4.0.4.
>>> >> > I've not solved this problem yet, in spite of half a year
>>> researches.
>>> >> > I gradually be sure that this is a bug of unregisterAppConfig().
>>> >> > Here is a report about this problem.
>>> >> > Google android group

>>> http://code.google.com/p/android/issues/detail?id=26704&can=1&q=hdp&c...

>>> >> > I think this is a only way to report the bug to Android API
>>> developers,
>>> >> > because developer.android.com provides this forum as a Support.
>>> >> > So, I want you to add a star or comment to this issue, if you have
>>> the
>>> >> > same
>>> >> > problem.
>>> >> > And wish to be debug.

>>> >> > On Thursday, February 2, 2012 8:05:51 PM UTC+9, jfernandez 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-d...@googlegroups.com
>>> >> > To unsubscribe from this group, send email to
>>> >> > android-developers+unsubscribe@googlegroups.com
>>> >> > 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 android-d...@googlegroups.com
>>> > To unsubscribe from this group, send email to
>>> > android-developers+unsubscribe@googlegroups.com
>>> > For more options, visit this group at
>>> > http://groups.google.com/group/android-developers?hl=en