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.
Is there any one tried to get CC254x (even CC26xx) working with the latest Android 6.x Marshmallow? We heard there are issues from multiple sources. We are still looking for any Android 6 device to confirm. Will get back here and let everyone know once we have a device to test it.
Ed (TI): ** Update Dec 9, 2015: See Dec 9 post confirming Android 6.0.1 (Nexus 5) update is now compatible with BLE 1.4.0 and earlier BLE-Stack releases. Peripherals that are Pairing with Android devices that do not yet incorporate this change will need BLE 1.4.1 to remain compatible with smart devices that implement LE Secure Connections (BT4.2) Pairing.
Ed (TI): ** Update October 2016: Reports of compatibility issues with Android N and BLE-Stack 1.4.2/1.4.2 are not related to Pairing. An update to improve the performance of the SNV read operations can be made by replacing the findItem() function in osal_snv.c with the version in the the attached findItem.txt.
Ed (TI): ** Update May 2018: TI has fielded inquires about peripheral devices not detected after upgrading to Android 8. Previously, these devices were detected with the same handset running Android 7 (or earlier). The issue has been traced to improperly formatted data within the peripheral's ADV or scan response (SCAN_RSP) PDU. Specifically, if the length byte in the ADV or scan response does not match the actual payload of the proceeding AD data type (e.g., Manufacture Specific Data), Android 8 will not present the peripheral device to the application. Please ensure that your advertData and scanRspData arrays properly set the "// length of this data" for the given AD data type.
Ed (TI): ** Update Apr 2019:TI has released BLE-Stack 1.5.0 for CC254x which is qualified to Bluetooth 5.0. This release addresses the "findItem" SNV limitation described above. Please see the release notes and porting guide which are included with the 1.5.0 SDK for details on upgrading and using this release.
Please click the "This Resolved My Issue" button on this post if it answers your question
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to JXS:
We did test it on a Nexus 7 (Android 6.0, Build MRA58K). SDK 1.4.0 does not work and SDK 1.4.1 works fine.
In reply to Samson Chen1:
In reply to Karim Houni:
In reply to Moby Chiu:
TI does not have visibility as to when a respective phone OEM (i.e., LG for Nexus 5) will issue an OTA or ROM update incorporating the patch listed above.
If you have not shipped your product, I strongly recommend you upgrade your firmware to BLE 1.4.1 which does not have the Android6 LE Pairing compatibility issue.
Thanks for your answer.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.