JF

Thanks for your feedback @Arsen6331 :+1: Adding a characteristic, or extending the BLE FS API is indeed a good idea to allow checking data validity with a CRC. Regarding (de)compression,...

> Also, the archive (without compression) could possibly be placed into the already existing DFU zip with a new entry for it in the manifest. That will mean there is...

We might not need to alter the manifest, and just add the resource file and maybe a metadata json file to the dfu archive.

I did a bit of progress : files (fonts and pictures) are now converted and packed into a single .zip file using a CMake `custom_target`. This target - Converts the...

I have also been thinking about this. Here's what we could do: - the developer of an app that use external resource name the resource file `something_v1.bin` for example. -...

Mhm that's a use-case I haven't anticipated... But I have the feeling that this should be handled on the companion app side. It could manage a list of "locked" files...

That won't be easy.. even if companion app developers agree on a single mechanism, you'll have to sync them across all your devices... Unless this "do not overwrite this file"...

Good idea! However, I might work on this on a second step, as I would like to implement a working version of the support for "external resources" soon. This feature...

I've just added an example package and the expected results (via ITD) in the [original comment](https://github.com/InfiniTimeOrg/InfiniTime/issues/1285#issuecomment-1221605579).

Here is the corresponding PR : https://github.com/InfiniTimeOrg/InfiniTime/pull/1299