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.
In reply to JXS:
"That's unfortunate that not all OEMs have implemented the AOSP change from 6.0.1."
I have also heard that there are still problem with LG devices (G5,G4,G3). Could you ask manufacturers to implement this fix? S7 together with most popular LG devices means that there are millions devices out there that do not work with CC2541 devices that require security.
In reply to Lou Prado:
Please see the TI BLE Wiki www.ti.com/ble-wiki and sticky forum threads for additional examples & answers to most common questions!
Thank you for marking the thread as answered if your question was answered :)
Our customers used Nexus 6P (Android 7.0) to test our BLE device and also got pair problem.Our BLE device is BLE 1.4.1 stack and CC2541 chip.Here is log file. Nexus6P_2D00_NG.zip
We are going to get one Android 7.0 phone to test it, will feedback the result later.I found your post about improving SNV read operations on October 2016. Is this code to solve Android N compatibility issue? (or the pairing issue is from SNV handle?)Please give us some suggestion.
In reply to Moby Chiu:
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. 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 respect to these materials. 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.