7 posts / 0 new
Last post
Fri, 2015-02-06 18:49
#1
shiva
Offline
Last seen:5 years 4 weeks ago
加入:2015-01-19 12:23
reporter_fh monitor

Hi,

I have loaded reporter_fh code into Expert dev kit and trying to monitor using BLE device monitor android app(general app).
so, i could able to see device(DA14580) and connect, but SERVICEs and CHARs are not able to see in app.

How to check this?

Thanks
Shiva

Fri, 2015-02-06 19:13
shiva
Offline
Last seen:5 years 4 weeks ago
加入:2015-01-19 12:23
should have our own

should have our own application(apps) to see proprietary profiles and Services.

Kindly waiting for some valuable comments.

Thanks
Shiva

Sat, 2015-02-07 06:20
JE_Dialog
Offline
Last seen:6 days 4 hours ago
工作人员
加入:2013-12-05 14:02
Hello Shiva, i would try

Hello Shiva, i would try BlueLoupe app which is in my view one of the better general purpose scanning apps out there.

BR JE_Dialog.

Sat, 2015-02-07 09:13
(Reply to #3)
shiva
Offline
Last seen:5 years 4 weeks ago
加入:2015-01-19 12:23
Hi,

Hi,

Thanks for the reply!!!

i have already using this app but result is same, this would show only Generic profile(1800) not Battery profile, Proximity profile and SPOTA profile.

this is unable to detect because of proprietary profiles??

thanks
Shiva

Mon, 2015-02-09 10:51
shiva
Offline
Last seen:5 years 4 weeks ago
加入:2015-01-19 12:23
Pls help me to get this up

Pls help me to get this up and running!!!
why its not showing other profiles?
is there any bug in reporter_fh?? bcoz we dint change anything in SDK 3.0.6 code

Thanks
Shiva

Tue, 2015-02-10 16:32
(Reply to #5)
MHv_Dialog
Offline
Last seen:1 month 5 days ago
工作人员
加入:2013-12-06 15:10
Hi,

Hi,

I think you are seeing an effect of Android storing discovery information. At some point, you probably loaded the template_fh application an used the Android device to discover the services. Android does not make a service discovery for devices that are already known to Android. Instead, it just assumes that nothing has changed.

The fix is simple:

On Android 4.3 to 4.4.4 devices simply disable Bluetooth and then re-enable it

On Android 5.0 (Lollipop), you need to go to the Bluetooth settings menu, select the DA1458x device and press "Forget".

An other way to solve it would be to change the BD Address in the nvds.c file. This will trick your Android device into thinking that there is a new device in town ;o)

Fri, 2015-02-13 15:21
shiva
Offline
Last seen:5 years 4 weeks ago
加入:2015-01-19 12:23
its working!!!

its working!!!
Thanks you very much.

Shiva