-
-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DFU Never Finishes #2
Comments
Thanks for reporting. I will try and see if it works later this week. |
Have you found out anything on this yet? |
No not yet, i do think this is an issue with the underlying nordic dfu android library. They are however actively improving this so i am waiting for a new version of it over at https://github.com/NordicSemiconductor/Android-DFU-Library |
Nordic has released an updated library and I was wondering if you have had the chance to work on this. |
I also found this post. Hope it helps. |
Thank you for working on this. I'll be looking forward for a package update on pub.dev. |
@tpevahouse25 I have released v3.3.0. I hope it solves your problem. |
Unfortunately, that update didn't fix my issue. |
I got the same problem on my pixel 6. Although I noticed that recently even the nRF Connect app no longer works and outputs identical behaviour... Edit: Tested the code on my old Oneplus 3T (Androdi 9) and I get the same problem, however the loading bar was progressing smoothly as opposed to jumping. I also tested various nrf Connect app versions on both of my phones and it seems that the last version that still worked for me on both phones was 4.24.3. New versions 4.25.X would behave slightly differently on each of my phones. Pixel 6 would have those same jumps, while OnePlus 3T would be progressing smoothly. But in the end, after reaching 100% neither of the phones would complete the OTA and would just get stuck. Given this, I am 100% sure that the problem is within the Nordic SDK, since their own app no longer works in identical way that I am observing on my app using their SDK... 🥲 |
I have released V5.0.0 and checked with my Pixel 4a 5G with Android 13. I had no problems with DFU. |
Sadly it's still not working for me. But I think it might have something to do with the bootloader that I am using, it's Adafruit bootloader, which I think is considered a legacy, since it's not a secure bootloader, thus maybe Nordic isn't serious about making the new SDK to work with it or simply they didn't test it...
|
@Montvydas I am using secure DFU which is working without problems. I think it would be better to open an issue on the android dfu github page https://github.com/NordicSemiconductor/Android-DFU-Library |
Yep, I am also 100% it's got nothing to do with the Flutter part :) |
Why ? fail to open file: No such file or directory |
I solved it, thanks |
@juliansteenbakker Would you be able to tell me: |
Version 2.0.2 https://github.com/juliansteenbakker/nordic_dfu/blob/master/android/build.gradle#L38 |
I/flutter (18078): PlatformException(File Error, File not found!, flutter_assets/assets/file.zip, null) I am getting this error can anybody help ? |
Did you add the file to your assets folder? And did you also add it in your pubspec.yaml? |
Your path is not correct. You need to change |
I have been talking to Nordic about the issue with updating legacy bootloaders on android. I was told to use the default mtu of 23. I noticed that when using the nordic_dfu package is switches the mtu to 247. Is there a way to manually request an mtu using this package. |
I have released v5.1.0 of this package which updates both the android side aswell as the iOS side to the latest versions of the DFU library. The MTU is not something that can be controlled right now, so that would be a good addition imo. |
I've updated this package to version 5.1.1. Please check if the issue still persist and otherwise feel free to comment. |
I am having an issue with the nordic dfu service finishing. I have been using the flutter_nordic_dfu package for a while now with great success but since Android 12 has been released I have had to move to nordic_dfu. The dfu starts and in my on progress listener, I am printing out the percent. It will print out from 1% to 100% but then does nothing. My progress indicator shows that it has large jumps from 0 to 30 to 50 to 80 then 100 then stays at 100. The time it takes from 0% to 100% is only about 10 seconds when normally it would take about a minute and 30 seconds. After a couple of minutes at 100% the app will crash.
I am testing on a Google Pixel 6 with Android 12 and a Samsung Tab A with Android 11 and getting the same results.
I can put this same code on an iPhone and it performs like it should and always has.
Can you give me an idea why this might be happening and how i could fix it.
Thank you.
The text was updated successfully, but these errors were encountered: