Is your feature request related to a problem? Please describe.
Yes. Despite the recent write stability improvements and retry mechanisms introduced in PR #834 and PR #847 by @wu-zuan, I still occasionally encounter incomplete card writing issues.
Describe the solution you'd like
I would like to request implementing a card writing mechanism similar to Mifare Classic Tool (MCT). In my experience, MCT's writing process is highly stable and almost never fails. Porting or adapting its core writing logic/strategy into ChameleonUltraGUI could fundamentally resolve the current instability.
Describe alternatives you've considered
My current alternative is to use ChameleonUltraGUI for most tasks, but switch to the MCT app specifically for writing cards to ensure success. While the existing 10x retry and delay mechanisms in the GUI help, they serve more as a workaround rather than a definitive fix.
Additional context
References:
While the added delays and retries are appreciated, MCT seems to handle the RF write cycle differently, resulting in a near 100% success rate without heavily relying on retry loops. Investigating and adopting MCT's approach could greatly improve the user experience.
Is your feature request related to a problem? Please describe.
Yes. Despite the recent write stability improvements and retry mechanisms introduced in PR #834 and PR #847 by @wu-zuan, I still occasionally encounter incomplete card writing issues.
Describe the solution you'd like
I would like to request implementing a card writing mechanism similar to Mifare Classic Tool (MCT). In my experience, MCT's writing process is highly stable and almost never fails. Porting or adapting its core writing logic/strategy into ChameleonUltraGUI could fundamentally resolve the current instability.
Describe alternatives you've considered
My current alternative is to use ChameleonUltraGUI for most tasks, but switch to the MCT app specifically for writing cards to ensure success. While the existing 10x retry and delay mechanisms in the GUI help, they serve more as a workaround rather than a definitive fix.
Additional context
References:
While the added delays and retries are appreciated, MCT seems to handle the RF write cycle differently, resulting in a near 100% success rate without heavily relying on retry loops. Investigating and adopting MCT's approach could greatly improve the user experience.