You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The advantage of using the 'DfuBaseService' inherited service is that you can safely upload DFU.
However, if you upload several DFUs at the same time, you have to add several of the relevant 'DfuBase Service' and declare it in 'Android Manifest'.
Solution
How about controlling DFU uploads to be processed within one class?
The text was updated successfully, but these errors were encountered:
sieunju
changed the title
[Core] Can I delete 'DfuBaseService'?
Can I delete 'DfuBaseService'?
Dec 17, 2024
Yes, true. This is a very old library, modern approach would be very different, with split for transport and logic, tests, etc. IntentService besides that is deprecated and it's the user that should decide how and where to run it, e.g. in WorkManager.
Anyway, you may cut the relevant part from the DfuBaseService and implement it as a method.
No, it's lower layer. Handles GATT and GAP operations (connection, GATT, advertising) and allows peripheral emulation for test, kinds like CoreBluetooth Mock for iOS, but better. And it may be KMM at some point also.
The new DFU would be built on top of it as version 3 of DFU library.
Target
Library
Describe the feature
Why?
However, if you upload several DFUs at the same time, you have to add several of the relevant 'DfuBase Service' and declare it in 'Android Manifest'.
Solution
The text was updated successfully, but these errors were encountered: