name: Bug report
about: Create a report to help us improve
If you got it from Google Play, please note that version is unofficial and not supported here; it's also often quite outdated. Please switch to one of the above versions if you can.
Since 0.40.1 or maybe 0.40.0 installing watchface files fails even with files that previously worked with the same firmware. Mi Band 4 uses its default watchface after trying. I can still install watchfaces using other software.
If possible, please attach logs! that might help identifying the problem.
Please specify model and firmware version if possible
New issues about already solved/documented topics could be closed without further comments. Same for too generic or incomplete reports.
Can you please tell us which watchface that is?
I can then try the same and fix the bug.
It's been https://amazfitwatchfaces.com/mi-band-4/view/4982
But I tried also my previous one that had installed well with an older Gadgetbridge version and it failed too.
Ok, thanks for the report, I think the change in 0.40.1 to use a bigger MTU broke it for you.
The Mi Band 4 asks for a bigger MTU (247 instead of 23), and I was under the impression that this is already a confirmation for a successful negotiation. But probably it is not.
For me I could flash firmware and res in record time with the change.
I will try to fix it for 0.41.1, if you are able to build yourself I could send you a patch to try possible fixes.
Hmm...now I remember I also could flash watchfaces immediately after the update with the MTU change. But I did NOT notice any remarkable speedup.
And I remember there's been another change to my configuration since then: my stock ROM for Galaxy S7 has received another security update... Maybe it's somehow related to this. But I can still use some other software to flash watchfaces successfully.
I can't compile Gadgetbridge myself unfortunately. Tried it a while ago using AIDE but this threw too many errors I could not figure out.
But I'll give feedback when 0.41.1 is on F-Droid.
Just tested the watchface and it worked here, damn.
Gadgetbridge should compile fine.
without android studio you can just type
(shamelessly assuming you are on Linux)
Thanks - not on Linux or at least not on the one you mean: AIDE is an Android app ;)
I'm going to uninstall Gadgetbridge 0.40.1 now and try out an older version to see if the issue is somehow related to the MTU change on my device.
Ok, it worked with 0.40.0. So I upgraded to 0.40.1 to make sure it does not work there. But it does flash watchfaces successfully with it as well!
I did not notice speed improvement over 0.40.0 however. Should I do any checks regarding that?
Bad news - after a reboot of the smartphone and setting all options in Gadgetbridge like app blacklist and automatic reconnection flashing watchfaces fails again.
Did the same procedure again but settings already in 0.40.0. With this it first worked then the watchface update after a reboot failed. Please note that Mi Band Gadgetbridge loses connection to the Mi Band 4 when failing although the smartphone is very close to it.
I then turned off automatic reconnection and flashing a watchface with 0.40.0 worked again. Updated to 0.40.1 then. First failed even after turning off automatic reconnection. But after a while ago from the smartphone it suddenly worked with 0.40.1.
Could there be an interference of the firmware update code with the reconnecting code?
No due date set.
This issue currently doesn't have any dependencies.
Deleting a branch is permanent. It CANNOT be undone. Continue?