• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 51 subscribers
  • Views 1558 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.

BLE stack 1.3 doesn't work with Android 5.0, but BLE stack 1.4 works?

Leo Bellotindos
Intellectual 710 points

Other Parts Discussed in Thread: CC2541

Hi,

We have a device (based on CC2541) that was developed 2 years ago using the BLE stack 1.3 which worked well with phones running Android 4.3 and Android 4.4.  However, we are now having problems connecting to phones running Android 5.0.   The problem is that the phone immediately disconnects after the connection.

Our device is able to connect properly to a Samsung Galaxy S5 that is running Android 4.4, but the device disconnects immediately after connection when used together with a Samsung Galaxy S5 running Android 5.0.

After encountering the problem, we decided to start debugging.  But since the BLE stack 1.4 is already available, we decided to use the new BLE stack.  After compiling the original source code together with the new stack, the device is now able to connect to the phone running Android 5.0.  

Does anyone know of a problem in the BLE stack 1.3 that causes the connection problems in Android 5.0?  What were changed in BLE stack 1.4 that somehow fixes the issues with connecting to Android 5.0?

After some more testing, it seems the problem we have with connecting our device to Android 5.0 is only occurring when using Samsung phones and the Nexus 5.  The problem does not exist when using other Android 5.0 phones.  Is there anything we can do in the phone side to fix the connection problems?

Any help is much appreciated.

Thanks,
Leo

  • 0
    Expert 1730 points
    Hi Leo,

    I guess the old BLE Stack were not able to resolve the private BLE address (PRA - Private Resolvable Address).
    Refer to the below link:
    e2e.ti.com/.../1428335

    Probably Samsung S5 uses Private Address. So the older BLE stack might not be able to resolve the private BLE address of Samsung S5 device. Now since you are using the newer stack, it might be able to resolve the private BLE address and you are fine.

    Thanks,
    Sunny
  • 0 in reply to Sunny Bhayani
    Intellectual 710 points
    Hi Sunny,

    Thank you for the reply. I don't think it is related to the PRA because our device doesn't use any pairing or bonding.

    Leo
  • 0 in reply to Leo Bellotindos
    TI__Mastermind 34660 points
    Hello Leo. I'm not really sure what this could be and we'd probably need a sniffer capture to debug more. Do you know if the Android devices are attempting to pair?
  • 0 in reply to Tim C
    Intellectual 710 points
    Hi Tim,

    The app running on the Android phone is just performing an ordinary connect without pairing.

    We were just hoping that by knowing the changes in the stack we would be able to determine if there is something that we could do on the app from the phone side to resolve the connection problem. Definitely, we will be releasing a new build for the device firmware using the BLE stack 1.4.

    Just an added info, the problem doesn't seem to occur when using the Samsung Galaxy S4 running Android 5.0.1. The Galaxy S4 is using a much newer Android Lollipop update and was released more recently compared to the Galaxy S5 lollipop update.

    Thanks,
    Leo