nRF Connect for Mobile is faster updating the FW than my app

[mobilekosmos]

Version

"androidx.bluetooth:bluetooth:1.0.0-alpha02"
"no.nordicsemi.android:dfu:2.9.0"

Ask the question

I noticed that your nRF Connect for Mobile Android app is updating the FW in about 1min, while my app using the Jetpack Bluetooth Alpha Lib is taking aroung 1:50m, with the latest DFU lib.
I was using an older version of the DFU version where it was taking 2:55, after updating, it went down to 1:50 but it's still a big difference from your app, and I'm not seeing anything I can configure while establishing a connection to the device via the Google lib. Any ideas?

Relevant log output

No response

[philips77]

Please, compare the settings in nRF DFU app in Setttings to the settings you set in DfuServiceInitiator. For example, are PRNs enabeld, what is the data object delay, etc.
Your code for setting up the initiator would help.

[mobilekosmos]

private fun startFirmwareUpdate(
        cachedFileName: String,
        readableName: String,
        dfuDeviceMACAddress: String,
        serialNumber: String,
    ) {
        Timber.tag("Firmware_DFU").d("Update starts for ${dfuDeviceMACAddress}")
        val starter =
            DfuServiceInitiator(dfuDeviceMACAddress)
                .setDeviceName(serialNumber)
                .setForceDfu(true)
                .setForeground(false)
                .setPrepareDataObjectDelay(400L)
                .setNumberOfRetries(5)

        // Init packet is required by Bootloader/DFU from SDK 7.0+ if HEX or BIN file is given above.
        // In case of a ZIP file, the init packet (a DAT file) must be included inside the ZIP file.
        val cachedFile = File(applicationContext.cacheDir, cachedFileName)
        starter.setZip(Uri.fromFile(cachedFile))

        starter.setPacketsReceiptNotificationsEnabled(true)
        DfuServiceInitiator.createDfuNotificationChannel(applicationContext)

        starter.start(applicationContext, dfuServiceClass)
    }

I tried different values with setPrepareDataObjectDelay() without changes at all.

[philips77]

Hi again,
Which SDK is your firmware based on?

Some comments to your code:

1. This has effect only for nRF5 SDK v4.3 - 7, where there's no DFU Version characteristic. Otherwise, it can be removed.

   .setForceDfu(true)

2. This is a setting for Secure DFU only. For Legacy DFU it is unused.

   .setPrepareDataObjectDelay(400L)

Are you using this DFU library, or "Jetpack Bluetooth Alpha Lib" (I believe you're talking about this)?

Are you comparing your own implementation based on this lib vs this library?

[mobilekosmos]

Currently I'm using these:
"androidx.bluetooth:bluetooth:1.0.0-alpha02"
"no.nordicsemi.android:dfu:2.9.0"

I'm comparing my implementation with doing the same action with nRF Connect for Mobile

[mobilekosmos]

Hi again, Which SDK is your firmware based on?

Some comments to your code:

1. This has effect only for nRF5 SDK v4.3 - 7, where there's no DFU Version characteristic. Otherwise, it can be removed.
   .setForceDfu(true)
2. This is a setting for Secure DFU only. For Legacy DFU it is unused.
   .setPrepareDataObjectDelay(400L)

Are you using this DFU library, or "Jetpack Bluetooth Alpha Lib" (I believe you're talking about this)?

Are you comparing your own implementation based on this lib vs this library?

Regarding this I just got the info that the Firmware is based on SDK v14.2.0, we had legacy Code from years ago, so it was just copy pasted, thus you are right that I can remove forceDFU, but the other one should bring something.

[philips77]

With .setPrepareDataObjectDelay(0L) the DFU should speed up. Also, try disabling PRNs using .setPacketReceiptNotificationsEnabeld(false).