Clone set to long button press in latest firmware doesnt seem to clone anymore

[quentynt]

hi in latest firmware pulled today setting long button press to clone doesnt seem to clone mifare classics UID's any more

going back a few versions and it seems to work as expected

[nieldk]

I will have a look. PR #24 is where I added long-press functionality. Hopefully this weekend :)

Had a look, not my PR that broke, but there are only so many changes since that. So, still looking for what broke long press.

[qqice]

hi I also encountered this issue. Actually, it's nothing to do with long button press function, but clone function itself.
I noticed that since "CLONE_MFU" function was add, the "clone" function, along with "CLONE_MFU" function, fails to function properly.
So I flashed the build 152dc71 to get it back to functioning.

[nieldk]

The problem is that Latest pull request extends the FW above allowed size. Resulting in config getting wiped.
Added pull request #46 (comment) to reduce the size of the Firmware, using LTO.
My tests seems to fix this issue.

[zviratko]

I have the same issue on latest firmwares, are you sure it is fixed?

[quentynt]

check in the Makefile - when i looked the function to copy cards on button press was commented out

…

On Wed, 22 Sept 2021 at 12:25, Jan Schermer ***@***.***> wrote: I have the same issue on latest firmwares, are you sure it is fixed? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#43 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARB6ZPUAJHKEIF33FOQCSHDUDG4MLANCNFSM4RTCQ4WA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[zviratko]

Hmm, doesn't look like it's commented out. Where did you see it?

[xeonxu]

Seems this c5b0798 commit cause the issue.

[d4g]

Has this ever been fixed?