RE: Mobile phone compatibility issue

Elliot.Chao — Tue, 25 Feb 2014 09:40:31 GMT

I see,Thank you.

RE: Mobile phone compatibility issue

Aleksander Nowakowski — Mon, 24 Feb 2014 14:49:05 GMT

Hi Elliot, Since nRF Toolbox v1.3 there is no significant difference in DFU implementation between MCP and Toolbox. I don't know why uploading succeeds on MCP but on Toolbox it fails. Could you please attach the HEX file that you are using?

However there are some differences in general application framework. For example in order to start DFU process in MCP you have to connect to the device and discover services. Only then, when the DFU service will be find, the DFU button is shown. The initial connection may filter out some problems while DFU, f.e. you may receive an error during the initial connection, quickly go back, connect again and forget about it. In Toolbox you are not connecting to the device before starting DFU operation. The application assumes that if DFU service UUID was present in the advertisement packet, the device will support it. It may not always be true (Android caches the device information and does not discover services if already obtained). Nothing filter out Bluetooth problems. To be sure, that both implementations will behave the same, it is recommended to restart Bluetooth adapter just before opening app. You may also find out that after successful upload both apps call the hidden method refresh() in BluetoothDevice that clears the cache so next time when you connect to it it may show different services..

The 133 (0x85) error is something that should never happen. All we know that it is a Gatt Error. You may find more such errors here: android.googlesource.com/.../gatt_api.h. Sometimes it comes after error 129 (0x81) (internal gatt error). When BLE stack on Android gets more and more stable, those errors comes less often. If you have tried Nexus 4 with Android 4.3 when it was released, than it was a real nightmare. Samsung has better implementation of BLE stack. There are much less instability errors. It was working quite good even in Android 4.3. Nevertheless we have found some significant differences between different phone models.