There are ~100 Knowledge Base Articles (KBAs) in the Bluetooth section of the forum on a diverse range of sub-topics. We know they are sometimes challenging to find, especially when you don't know what exists (and therefore you don't search for it).

To simplify this task we have created a Bluetooth Knowledge Base Article List which has all the KBAs divided into sub-topics. This list only contains KBAs which are meaningful today, so you won't find anything related with SDK 1.x, BGScript or anything else which has been deprecated. Most of those KBAs are still here but their title has been marked with a "[Deprecated]" prefix and a Note pointing for a more updated KBA where applicable. This is to avoid confusing our customers into reading material which is no longer applicable.

It would be great to hear if you find this list useful and any thoughts you might have on how to improve it.

Additionally please check out our Bluetooth training page -> https://www.silabs.com/support/training/bluetooth

Problem

Some mobile devices may have connection problems after updating BGX13 to 1.2.2045.0.

SIlicon Labs recently updated the firmware for BGX13 to version 1.2.2045.0.

https://docs.silabs.com/gecko-os/1/bgx/latest/release-notes

This version has some feature improvements, but these improvements required that we make some changes to the GATT attributes. Because of this, some phones may experience connection problems after the BGX13 firmware is updated.

Reason for Problem

Some mobile devices remember the GATT attributes of devices that have been paired or bonded in the past. When the GATT attributes are changed after the 1.2 update, the mobile device cached GATT information is misaligned between the two devices. This causes invalid handles to bluetooth services and characteristics. As a result attempts to connect to the device may no longer work, or some feature may not work such as sending or receiving data between a phone and the specific BGX for which this invalid bonding exists.

Invalid/misaligned bonding data must be cleared and then the bond should be re-established using the correct GATT attributes.

Solution

The problem may manifest in the following ways.

On iOS, you may see a message on the device details screen reading "SOME_OTHER_MODE".

On either Android or iOS, you may also see a password dialog appear at an inappropriate time or when no password has been set. You might also see that data is not being sent from the phone to the BGX or from the BGX to the phone.

To solve this problem, perform the following operations:

1. If you have access to the BGX command line interface such as through a Terminal emulator connected to the serial interface, enter the command 'clrb' to clear the bonding information from the BGX.
2. On your phone, open the Bluetooth Settings and locate the BGX device. Click a "i" icon, gear icon, or other details icon for the device in the Bluetooth settings and choose "Forget" or "Unpair". 
3. On your phone, turn Bluetooth off and then back on. This has been particularly noted as a necessary step on iOS 13. Alternatively, you could reboot the phone itself. However, rebooting is not a substitute for "forgetting" the device in the Bluetooth settings.
4. Kill the BGX Commander app as you would any app on your iOS or Android phone.
5. Restart BGX Commander and re-connect to the device. It should work correctly now. 

Also refer to https://docs.silabs.com/gecko-os/1/bgx/latest/firmware-update#problems-after-upgrade

1. Clarify to yourself what the specific issue is.

2. Apply basic troubleshooting:

• Check hardware connections with multimeter.
• Use logic analyzers/oscilloscopes.
• Use Simplicity Studio Debugger/Energy Profiler/Network Analyzer/BG Tool, use logging prints.

3. Consult the datasheets and reference manuals. Sources include:

• Simplicity Studio Launcher Documentation Tab
• Bluetooth Knowledge Base Article List
• Silicon Labs Technical Resource Search

4. Search to see if someone has asked the same question already.

5. Include the relevant parts of your development setup in the problem description. Examples include:

• SDK version
• Part number
• Radio board vs custom hardware
• Host OS
• Mobile phone model and OS version
• Compiler and compiler version

6. Include steps to reproduce the problem or specific conditions the problem occurs in.

7. Be patient and avoid making duplicates of your question.

For general community usage please refer to the Silicon Labs Community Guidelines.