Support Known Issues - ComThings/PandwaRF GitHub Wiki

BLE connection issues

If you experiment some BLE connection issues, please check the wiki page: BLE connection issues tips

Unexpected disconnect

After selecting the PandwaRF in the Scan screen, if it shows a Connected and shortly after a Disconnected message, please try to clear your phone Bluetooth device cache.

To clear the Bluetooth Device cache

Google Search "Android remove a Bluetooth pairing"

Google Search: "android clear bluetooth device cache"

OnePlus

Unexpected BLE disconnect

Samsung Galaxy Sx

Unexpected BLE disconnect

Huawei P9 lite

Fail to update Nordic BLE FW

PandwaRF app cannot find any device when pressing the "Scan" button

After upgrading to Android version 6.0 Bluetooth Low Energy (BLE) scanning will only work if Location services are enabled on the device. Please check that you have enabled your phone GPS.

Sending data bigger than size 250 may cause the PandwaRF to hang or disconnect

We are currently working to fix this. Until then we recommand capturing and transmitting payload smaller than 250 bytes. [Update 17/07/2017] Issue fixed, please wait until Nordic BLE FW 0.9.8 update is OTA-deployed.

TX data in 2-FSK mode doesn't work

but 2-FSK RX works. We are currently working to fix this.

Spectrum Analyzer doesn't support sliding/zooming/pinching

We know the Specan has some issues. Please do not change the settings on the fly. Always stop the Specan before changing a setting.

Spectrum Analyzer refresh rate is very slow

Reduce the Packet Interval. Warning: reducing packet interval too low may overflow the BLE link. If you still experience low data rate, then it is probably because your phone policy doesn't allow BLE connection with small Connection Interval value. This implies low throughput. Please have a look at Measuring the throughput of the BLE link between your Android phone and PandwaRF

HiSilicon Kirin chipsets

There is very poor BLE throughput with the Kirin 655 chipset (Huawei Honor 6X). Probably many phones using the Kirin family chipset have same BLE performance issue, so we encourage you to use another brand.

Nordic FW update issue

CC1111 FW update issue

GATT_ERROR(133)

GATT error 133 is quite generic and can happen when bonding information is not valid. In this case, try :