Proximity application is not working in android smart phone

[balaji]

Hi, How can i test the proximity application with the use of nexus4 smart phone and nrf51822 evaluation board? We already tested the ios proximity application which are all working fine. When we try to test the android application we are facing lot of problem's. For ios we have three application's to test 1.nRF Toolbox, 2. nRF Utility, 3. nRF proximity, but for android 4.3 we have only one application nRF Toolbox, that is also not working. It gives error like, error on connection state change and error on discovering sevices. Is there any other proximity application we can get with the source code?

Regards, Balaji.

[balaji]

Hi Hung Bui, Here, i attached the log file from the nRF master control panel, this app is not at all connecting with the device. And also i attached the log file taken with the use of eclipse IDE for nRF Toolbox application.

Log 2013-12-17 12_05.txt

Eclipse_nRFToolbox.txt

[Paul Yip]

Hi,

I get the following from the website you provided:

[i]Note:

• Supported on Android version 4.3 or later.
• Tested on Nexus 4, Nexus 7, Samsung S4 with Android 4.3 and on Nexus 4, Nexus 5, Nexus 7 with Android 4.4.
• Compatible with nRF51822 devices that have S110 v5.2.1 and the bootloader from nRF51 SDK v4.4.1+
• nRF51822 Development kits can be ordered from www.nordicsemi.com/.../Buy-Online .
• The nRF51 SDK and S110 SoftDevice are available online from http://www.nordicsemi.com for developers who have purchased an nRF51822 product.
• The source code of nRF Toolbox is available on http://www.nordicsemi.com and can be downloaded if you have purchased nRF 8001, nRF 51822 development kit or evaluation kit. Known problems:
• Nexus 4 and Nexus 7 with Android 4.3 does not allow to unbound devices.
• Reconnection to bondable devices may not work on several tested phones.
• Nexus 4, 5 and 7 with Android 4.4 fails when reconnecting when Gatt Server is running.
• Reset of Bluetooth adapter may be required if other error appear.[/i]

It looks like there are many connection problem on nexus devices. Does it mean Samsung S4 with Android 4.3 is the most stable device for nordic 51822 or 8100 chips for the proximity function at the moment? Thanks.

[Hung Bui]

@Balaji: It seems that the Nexus 4 had trouble when discovering the services. Have you tried disable wifi when connecting ? A reset on the phone is also worth to try. Could you let me know your Baseband version, Kernel version and Buildnumber in the "About Device" list ? Please send your firmware on the EV kit as well.

@Paul: We had issues with Nexus 4 and Nexus 7 before, especially when bonding is performed. However, after the update recently to Android 4.4.2, we found that the problem of re-connect after bonding was disappeared and also was able to un-pair. We was able to test only with our Nexus device samples that we have in house here, this may not true with other Nexus devices that may have different ROM built.

The Samsung devices that run Android 4.3 seems to be most stable and bug free at this moment. However, there are some new features added in Android 4.4 these devices missing, such as HID over GATT.

[balaji]

@Hung Bui: After disabling wifi, the application works fine for the first time. Disconnecting and reconnecting the device gives the error as same as i mentioned above. Reset and unpair requires both the side to connect again. I attached the screen shot of my nexus device information, and the firmware on my evaluation kit please check it and give your suggestion.

ble_app_proximity.hex

[Hung Bui]

@Balaji: We have exactly the same ROM built, but haven't got the same issue, especially when testing with Master Control Panel. Currently there is an issue with nRFToolbox and proximity profile is that, the nrfToolbox implemented server on the phone, and it still cause error when reconnecting.

Could you try other example ? such as the Heart rate measurement example?

Also I tried to program your hex file on the development kit but it didn't advertise anything, maybe there is some dependency ? Which softdevice you used ?