search

andengineering / A-D-HDP-Android-Demo

Sample App for connect Android device to A&D Continua Device
www.andonline.com
28 stars 18 forks source link

Unable to get any data from UA-767PBT #3

Open thejae opened 10 years ago

thejae commented 10 years ago

Hello guys,

Firstly I'd like to say thanks to @nunoar for troubleshooting and sending us his APK (https://github.com/andengineering/A-D-HDP-Android-Demo/issues/1). But the end result is still the same as the one we compiled.

Below is the console log from the moment we launched the app until the UA-767PBT has completed a cycle of blood pressure test and until its screen switched off.

04-30 03:46:09.650: I/ActivityManager(189): START {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.example.bluetooth.health/.BluetoothHDPActivity} from pid 585
04-30 03:46:09.791: D/OpenGLRenderer(585): Flushing caches (mode 1)
04-30 03:46:09.806: D/dalvikvm(189): GC_CONCURRENT freed 1706K, 55% free 6318K/13895K, paused 2ms+7ms
04-30 03:46:09.885: D/dalvikvm(32332): GC_FOR_ALLOC freed 807K, 56% free 3643K/8131K, paused 18ms
04-30 03:46:09.892: I/dalvikvm-heap(32332): Grow heap (frag case) to 15.664MB for 4250360-byte allocation
04-30 03:46:09.924: D/dalvikvm(32332): GC_CONCURRENT freed 9K, 37% free 7784K/12295K, paused 2ms+2ms
04-30 03:46:09.931: D/OpenGLRenderer(585): Flushing caches (mode 0)
04-30 03:46:10.049: D/dalvikvm(32332): GC_FOR_ALLOC freed 4151K, 62% free 4673K/12295K, paused 14ms
04-30 03:46:10.056: I/dalvikvm-heap(32332): Grow heap (frag case) to 16.669MB for 4250360-byte allocation
04-30 03:46:10.080: D/dalvikvm(32332): GC_CONCURRENT freed <1K, 29% free 8823K/12295K, paused 1ms+2ms
04-30 03:46:10.220: I/Process(189): Sending signal. PID: 32332 SIG: 3
04-30 03:46:10.220: I/dalvikvm(32332): threadid=3: reacting to signal 3
04-30 03:46:10.228: I/dalvikvm(32332): Wrote stack traces to '/data/anr/traces.txt'
04-30 03:46:10.236: D/BluetoothHDPService(32332): BluetoothHDPService is running.
04-30 03:46:10.299: D/libEGL(32332): loaded /vendor/lib/egl/libEGL_POWERVR_SGX540_120.so
04-30 03:46:10.306: D/libEGL(32332): loaded /vendor/lib/egl/libGLESv1_CM_POWERVR_SGX540_120.so
04-30 03:46:10.306: D/libEGL(32332): loaded /vendor/lib/egl/libGLESv2_POWERVR_SGX540_120.so
04-30 03:46:10.439: D/OpenGLRenderer(32332): Enabling debug mode 0
04-30 03:46:10.463: W/InputManagerService(189): Starting input on non-focused client com.android.internal.view.IInputMethodClient$Stub$Proxy@40dd96c0 (uid=10038 pid=585)
04-30 03:46:10.603: D/BluetoothHDPService(32332): Activity client registered
04-30 03:46:10.603: I/ActivityManager(189): Displayed com.example.bluetooth.health/.BluetoothHDPActivity: +882ms
04-30 03:46:12.806: D/BluetoothEventLoop(189): Property Changed: UUIDs : 9
04-30 03:46:12.806: D/BluetoothAdapterStateMachine(189): BluetoothOn process message: 51
04-30 03:46:12.806: D/BluetoothEventLoop(189): Property Changed: UUIDs : 10
04-30 03:46:12.806: D/BluetoothAdapterStateMachine(189): BluetoothOn process message: 51
04-30 03:46:15.635: W/ActivityManager(189): Activity destroy timeout for ActivityRecord{40dfb610 com.android.settings/.Settings}
04-30 03:46:54.822: D/BluetoothEventLoop(189): Device property changed: 00:A0:96:33:15:70 property: Connected value: true
04-30 03:46:57.236: D/BluetoothEventLoop(189): Device property changed: 00:A0:96:33:15:70 property: Connected value: false
04-30 03:47:24.658: D/BluetoothEventLoop(189): Device property changed: 00:A0:96:33:15:70 property: Connected value: true
04-30 03:47:25.064: D/BluetoothEventLoop(189): Device property changed: 00:A0:96:33:15:70 property: Connected value: false

We have tested under the following conditions

nunoar commented 10 years ago

You're welcome, @thejae.

It looks like the bluetooth connection isn't being started at all.

I suggest you should try repairing the device with one of the tablets (CM shouldn't be a problem as I believe it uses the the standard BlueZ stack), and checking the logs again - the device will try to connect to the last Android device it was paired with.

I was expecting to find something like:

04-30 11:10:42.040: D/BluetoothHealthActivity(2565): STATUS_CREATE_CHANNEl enabled

at some point, after

04-30 03:46:10.603: D/BluetoothHDPService(32332): Activity client registered
slodge commented 10 years ago

Hi

I'm seeing a similar set of problems.

I'm testing on:

The UA-767PBT-C is paired, Android says it connects, but then it disconnects again within 500ms.

I've tried unpairing, repairing, buying a new device and beyond - but no luck so far. i can't get existing apps like myfitnesscompanion to work with it either.

This thread might also be linked - https://code.google.com/p/android/issues/detail?id=41419

Is there any more debug info I can try to collect? Anything else I can try?

Thanks

Stuart

pixelyunicorn commented 10 years ago

I'm seeing the same issues as @slodge - testing on UA-767PBT-Ci using a Samsung Galaxy Tab 2 running Android 4.1.2. Apps like myfitnesscompanion won't work either.

davidepedranz commented 10 years ago

Hi,

I'm not sure this can help, anyway this is my experience. I had some issues at the beginning and somehow I was unable to get the data from the device. I reinstalled the application and repeated the pairing procedure and now it's working on:

I'm using UA-767PBT-Ci (not UA-767PBT-C) and it works.

asinisalo commented 10 years ago

The reason is HDP profile in Google's BT stack. It is broken.

br, ari

From: Davide Pedranz [mailto:notifications@github.com] Sent: 9. lokakuuta 2014 16:26 To: andengineering/A-D-HDP-Android-Demo Subject: Re: [A-D-HDP-Android-Demo] Unable to get any data from UA-767PBT (#3)

Hi,

I'm not sure this can help, anyway this is my experience. I had some issues at the beginning and somehow I was unable to get the data from the device. I reinstalled the application and repeated the pairing procedure and now it's working on:

I'm using UA-767PBT-Ci (not UA-767PBT-C) and it works.

— Reply to this email directly or view it on GitHub https://github.com/andengineering/A-D-HDP-Android-Demo/issues/3#issuecomment-58508308 . https://github.com/notifications/beacon/3920706__eyJzY29wZSI6Ik5ld3NpZXM6QmVhY29uIiwiZXhwaXJlcyI6MTcyODQ4MDM3OSwiZGF0YSI6eyJpZCI6MzExMDY0OTJ9fQ==--905220fdd937b0256391831cbe8a86317f0584a6.gif

thejae commented 9 years ago

Thanks @asinisalo for the valuable insight. It's a shame A&D engineers couldn't be bothered to update us with this information. My e-mail to @iamchenchen wasn't answered.

Even if the latest UA-767PBT-Ci works with the posted codes in this github, am not too sure how I feel about A&D in general.

Also thanks @nunoar for keeping an eye on user issues here.

iamchenchen commented 9 years ago

@thejae sorry that I've no longer working in A&D. If you have additional questions please send me a private message on Github, I'll direct you to the right person.

thejae commented 9 years ago

@iamchenchen thanks but I believe there's no need at this moment.

We were offered a contract to supply HK gov hospitals with cloud based solution. Needless to say we've already failed the bidding process.

Our regional supplier has tried to communicate the problem through their purchasing channels (thanks btw) but they received no meaningful reply. No hard feelings towards you. Our dev team is glad this git repo exist in the first place. We'r just disappointed the sales people at A&D failed to take us seriously.

Funny thing is, the winning vendor bought their BP from taobao.com for like $20...

vidyajejurkar commented 8 years ago

Hi i am not able to pair UA-767PBT-Ci with my phone.this app is not wotking for me.can anyone tell me why it is happened??

asinisalo commented 8 years ago

Hi,

This meter is Bluetooth 2.1 device, and uses Continua protocol to communicate. It can use profiles SSP and HDP. But the choise and support for profile must be in your app in the phone.

Continua equals to ISO_IEEE 11073 family that is FDA recognized.

That said, this combination may be hard to find in any phone nowadays. iOS has this BT in older models, but Google damaged Android BT-stack couple years ago and they do not work. Anyway that BT-version is history, newer versions rely on BTLE (NT 4.0) + the app must talk Continua -- but because of pairing, your problem is BT, to start.

br. Ari

From: vidyajejurkar [mailto:notifications@github.com] Sent: 15. kesäkuuta 2016 14:26 To: andengineering/A-D-HDP-Android-Demo Cc: asinisalo; Mention Subject: Re: [andengineering/A-D-HDP-Android-Demo] Unable to get any data from UA-767PBT (#3)

Hi i am not able to pair UA-767PBT-Ci with my phone.this app is not wotking for me.can anyone tell me why it is happened?? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/andengineering/A-D-HDP-Android-Demo/issues/3#issuecomment-226160120 , or mute the thread https://github.com/notifications/unsubscribe/ADvTQsuZ_O3c6EMYqgwgye6ZChFE39vNks5qL-FJgaJpZM4B2qW8 . https://github.com/notifications/beacon/ADvTQtvKreDOYz5B7Sfevo5L4krtsmyXks5qL-FJgaJpZM4B2qW8.gif

vidyajejurkar commented 8 years ago

code is working by manually pairing bt autopairing is not possible ? auto pairing happens sometimes only ,all permissions related bluetooth like bluetooth and bluetooth admin registered already.is there any way to make stable pairing??