Extend the DFU library

RE: Extend the DFU library

AD1170 — Fri, 09 Jun 2017 07:06:37 GMT

Ok, thank you for the tip. It seems to be the better solution. I have taken a look to the content provider implementation. For now, it is a little bit to complex for me and i have not much time at the moment. But for a future release of the app, this is an option. Or do you have any sample code how this can be done (you mentioned libs the make the implentation easy). I'm not so firm with java. The app is written with Qt (Qml, C++). The DFU Lib is called via JNI.

RE: Extend the DFU library

Aleksander Nowakowski — Fri, 09 Jun 2017 06:32:24 GMT

As the lib also takes the URI, you may create a Content Provider (there are libs that make it very easy) which will provide bytes on URI, and pass this URI to the lib.

RE: Extend the DFU library

AD1170 — Thu, 08 Jun 2017 20:40:34 GMT

Hi Aleksander! Sure, it would be easier so store the file temporairly. But for security reasons this is not an option. I have added a function "setZip(byte[] zipBuffer), extended the "start()" - function and "onHandleIntend()" with a additional EXTRA... and take care if the zipBuffer is provided in the intent handler. Finally, i open the InputStream() in this way: is = new ArchiveInputStream(new ByteArrayInputStream(zipBuffer), mbrSize, fileType); So far it works. I know i must merge my functions to a new library version by myelf. Thanks!

RE: Extend the DFU library

Aleksander Nowakowski — Thu, 08 Jun 2017 09:31:33 GMT

Hi! Isn't it easier for you to just save the files in the temp folder (no permission required) and provide path to those files? You may do what you want, but you'd have to override the github.com/.../DfuBaseService.java method in your project and read the data on your own. Any later changes/bug fixes to the lib that we provide would have to be manually maintained by you and we highly discourage you to do so.