Why i can't debug Nordic supply nRF UART App source code in my Google nexus 7 II ?

[Michael Lin]

I tried to debug Nordic provided Uart App code on the Google Nexus 7 II device.

But I found a problem, when I remove: LocalBroadcastManager.getInstance(this).registerReceiver(UARTStatusChangeReceiver, makeGattUpdateIntentFilter()); function, I can debug, but after connecting to the device, APP will crash.

If not removed, then at a start of the operation, it can not debug.

[Michael Lin]

Is there any new progress yet, there are many customers waiting.

And the iOS & Android APP can be supports Google Nexus Series & SAMSUNG S4 outside, you have tested the other brands?

Ex : HTC or SONY.....

[Hung Bui]

Hi Micheal Lin,

I am really sorry again for the late answer. The notification from your reply on 24th Jan was missing. So I didn't really followed the case. Good that you pull it up.

I am not really sure why you still have issue with the library. Could you follow what I have in the attached screenshot ?

If the issue still remain, please have a screen shot of the error you get, and also attach your project files (zip them in 1 file)

After the release of Android 4.3 many other vendors now support BLE, as far as I know HTC One and Sony Z1 (or Sony Z) support BLE, and can run our example apps after the update to Android 4.3 and above.

javabuiltpath.PNG

[Michael Lin]

Hi :

Thank your help! i will be test it, tomorrow.

The Samsung Galaxy Note 3 can be support Nordic's APP?

Because i am not have the Samsung Galaxy Note 3 can be tested, so, do you have some information about it?

[moriszen]

I too am having problems connecting the UART demo app to Note 3 . I get "Device does not support UART. Disconnecting" . The regular BT was so simple and easy . THe BLE is so difficult - I really wish they would make it simple like standard BT . Nordic - If you can help fix tis - would be highly appreciated.

[Hung Bui]

@Moriszen: I'm sorry for a late response. Do you have the device bonded to your phone before you program the UART firmware ? Android doesn't always do a service discovery right after connected (as in iOS). So sometimes when you modified the code, changed the ATT table, Android might still keep the old ATT table as in the old firmware, especially when you are bonded.

The solution is to remove bonding, turn off and on bluetooth, or you can change the address of the device manually using sd_ble_gap_address_set() so that android will treat the device as a new device.

Please let me know if the issue remains