• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 51 subscribers
  • Views 1793 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.

CC2540: Android Security Patch Level Jul 01 2017(release on August 8, 2017) causes 100% failed connections with cc254x. Pairing works fine. The findItem.c speed improvement does not fix the issue. Latest BLE Stack V1.4.2 does not fix the issue.

Lou Prado
Prodigy 180 points
Part Number: CC2540

Greetings.  This post is not to be confused with previous posts regarding Android M and Android N pairing problems.

After updating to the latest Android Security Patch Level, July 01, 2017 every single connection fails (error code 133 in Android). Pairing succeeds without issue and GAPBOND_BOND_COUNT shows that the device has paired and the Android OS shows as paired. 

The cc2540 is running V1.4.2 of the BLE Stack and has the optimized version of findItem.c/GAPBondMgr_ResolveAddr. I also tried earlier versions of the BLE stack and all failed. 

As of Aug  14, 2017 this is a problem on two Verizon phones: the Samsung Galaxy S5 and the Samsung Note 4.  But we suspect this may become a problem on all Android phones as the security patch becomes more widely available.

I will follow up with a packet sniffer capture using the simpleBLEPerhiperal.c code, but if anyone else is having this issue, please confirm. 

Thanks in advance.

Lou Prado

Bluemate.com

  • 0
    TI__Guru** 105180 points
    Hi Lou,

    I don't have any of the handsets that you list above but I will see if this update is on any of our test phones. Please do attach the sniffer when you are able to capture a trace.

    Best wishes
  • 0
    TI__Expert 5390 points
    Hey Lou,

    To provide an update, I tested your setup described in your original post and was unable to see the error described above. I've been able to connect to the CC2540 (with simple peripheral), enable notifications and see the notification come in by a button press.
    This was tested with the following 3 phones:
    Samsung Galaxy S7 with Android Security Patch- July 1, 2017
    Google Pixel with Android Security Patch- August 5, 2017
    ZTE Axon 7 with Android Security Patch- March 1, 2017

    Please share your sniffer capture when available.

    -Sy Su
  • 0 in reply to Sy Su
    Prodigy 180 points

    Thank you for your quick response and for performing all those tests.  

    I was able to also confirm this bug does NOT occur on a Nexus 6P running Android OS 7.1.2 and Security Patch - July 5, 2017. This may just be a Verizon S5/Note 4 issue (and perhaps the Pixel XL), but I am monitoring it closely.

    My application is based on the SimpleBLEPeripheral code but I use 128-bit UUIDs. I have 2 custom services and 11 characteristics total. I will continue to strip all of my Application code  and report my results soon.

    In the meantime here are two sniffer captures. One is for a Galaxy S5 from AT&T that can connect and RW and the other is from an S5 Verizon that fails to connect.

    I'll also follow-up with the Android/Google team since I realize this issue is not caused by TI. 

    Any feedback is greatly appreciated.s5_ATnT_connection_success.psds5_verizon_connection_failed.psd

    Lou Prado

  • 0 in reply to Lou Prado
    TI__Guru** 105180 points

    Hi Lou,

    I took a quick look at your sniffer captures. For the good case, it looks, well, normal. I see the expected GATT 'banter' from the Client for Char discovery. In the NG capture, there is no GATT/ATT activity from the Client (i.e, master) and the connection is eventually voluntarily terminated by the slave (your application). What is odd is the sniffer shows the slave sending the initial Version Indication instead of the master but I think this is a sniffer anomaly. Taking a few more NG captures would probably confirm this. So, the real question that you'll need to answer is why is the master not doing anything during the connection other than sending empty packets. Did you try clearing the BT Share cache from the phone?

    Best wishes

  • 0 in reply to JXS
    Prodigy 180 points
    Hi Jeff. I think there is no solution to this. I start with SimpleBLEPeripheral and strip out nearly all the application code. Then I attempt to simply connect. The Samsung Galaxy S5 from AT & T has no problem but the Samsung Galaxy S5 from Verizon always fails. I have factory reset the Verizon S5 and also tested multiple TI 2540 ICs.

    This Verizon bug appears to have affected many BLE devices. Here's a link to the Verizon page:
    community.verizonwireless.com/.../936180

    We can only hope that the August or September Security Patch from Verizon fixes this issue.

    I will mark this issue as resolved since there is no more I can ask from TI. Thanks again for your outstanding support.

    Lou Prado
  • 0 in reply to Lou Prado
    TI__Guru** 105180 points
    Hi Lou,

    Thanks for updating. I had a read of the Vzw community post, and yes, it looks like they may have broken BLE with that update. Hopefully they can resolve it quickly.

    Best wishes