• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 52 subscribers
  • Views 1820 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

SIMPLELINK-CC2640R2-SDK: Few android versions doesnt work with CC2640R2F BLE chip

Suganya A M
Intellectual 480 points
Part Number: SIMPLELINK-CC2640R2-SDK
Other Parts Discussed in Thread: CC2640R2F,

Hi all

We have F1 sample based on CC2640R2F BLE chip and we created custom service to notify our data and that was working with our custom BVS Android app and also 3rd party apps.

With F2 sample hardware based on same chip, only we added SPI based communication + sensor controller feature, our custom BVS Android app or any 3rd part app doesnt work with few mobiles

When tested with python script using BLE blugiga dongle, our embedded code works without issues

We face different issues with different mobiles.. Few are listed below

Nexus 5 Android 6.0.1 - Working perfectly

Asus Android 6.0.1 - Not even getting connected

HTC Nexus 9 Android 7.1.1  - Getting connected but frequently app gets auto disconnected and connected

Xiaomi Redmi Note Android 7.1.1 - Getting connected after 30secs only

We captured mobile side and embedded side logs.

In mobile logs, it looks like due to connection timeout, app gets auto disconnected.

Attached the logs.

We are trying to narrow down the issue if its with embedded or android app side. Urgent reply would be helpful for us.

- Suganya

  • 0
    Intellectual 480 points

    we dont send any disconnect packet request from embedded side

  • 0 in reply to Suganya A M
    TI__Guru** 105180 points
    Hi Suganya,

    Have you tried disabling the Data Length Update feature based on the procedure in the BLE Stack SW User's Guide in the SIMPLELINK-CC2640R2-SDK? Some of these Androids have trouble with handing this feature, even if they don't support it.

    Beyond that, posting actual sniffer capture files for the specific failures would be helpful for us to provide more specific guidance.

    Best wishes
  • 0 in reply to JXS
    Intellectual 480 points
    Disabling DLE feature has solved issue in Nexus 6 running Android 7.1.1
    But Nexus tablet running 7.1.1 was facing still auto disconnection/connection issues when connected to app.
    When we changed conn. interval to lesser minimum value, this was also solved.
    First we started with minimum value of 6 (7.5ms) and increased to 600 (750ms), where our application is found to be running in all mobiles apps
    Thanks for the support
  • 0 in reply to JXS
    Intellectual 480 points

    We disabled DLE feature and reduced connection interval also.
    Though this solved our issue, but in long run, we are still facing disconnection issue with few mobiles.

    Inconsistently, issue is seen with Nexus tablet running Android version 7.1.1 and Redmi note running Android version 7.0 as of now
    We are sending notifications to mobile and randomly after some "n"th packet, mobile app is getting disconnected and connected automatically
    When we checked the wireshark capture, we found that after the last notification packet being sent to mobile, master is sending connection event but slave is not responding for it and after 20s of supervision timeout, app is getting disconnected automatically

    We tried to reduce connection interval to 7.5ms in peripheral side but still the issue was seen
    Here connection interval is getting updated to 48.75ms after conn. update parameter req.

    Why the slave didn't respond after sometime is unknown?
    What are the possible scenarios that slave wouldn't respond to master connection event?

    Note - Using BLE BLUGIGA dongle, python script to get notification is working in long run always

    Attaching wireshark capture of disconnected issue

    Regards,
    Suganya

  • 0 in reply to Suganya A M
    Intellectual 480 points

    Please rename .ppt to .pcapng and open using wireshark

    nexus_tablet_disconnected - Copy.ppt