[Solved] Preventing abuse of Reset License
It was noticed growing number of cases where customers reset Manufacture Date and Cycles Counter on the old and used batteries without replacing the cells.
It is definitely not the purpose Reset License was developed for.
Most of the customers catched on this activity even not hesitating to publish snapshots with 'renewed' parameters, another says it was done 'by mistake' or due to 'poor English' and misunderstanding of button design.
So to prevent erroneous reset of these parameters its suggested to fill Manufacture Date, Cycles Counter and FCC with a values copied from SBS report. So if someone press the button by mistake nothing will change.
Presently these values are corresponding to new battery and non-fair customers who even not have a plans to rebuild the battery could easy tempt to press a button and reset the data.
When proposed feature to be implemented, noone will say 'cycles were reset by mistake' as this will require entering new values wittingly which will prove abuse activity.
Indeed, there are people who are abusing this function and changing the wear parameters. But there are also people who are changing these values without abuse intention, for example thinking the battery will work again if the cycle count is set back to 1. I still see articles on the internet saying that laptop batteries stop working overnight because the counter reached a certain limit.
Another implementation option would be to warn through a message like: "Resetting cycle count and date without replacing the cells could be considered fraud and you are responsible for this. We don't encourage it and we could stop offering support."
Also, if the same customer repeats the "fault" and doesn't take our recommendation into consideration we could limit the support for him. Let's say the first and second time could be errors, mistakes, tries, etc, but not to continue.
I used it when replacing the new battery cell, but it didn't work. I had to use ev2300 to fix. When does it work? Please guide me, thanks.
It works for most of the chips. If you have a problem please open a separate topic in the Reset category.
P.S. FCC editor on "z" chip families (bq20zxxx, bq30zxxx, bq40zxxx) does not work because of the chip concept not because of NLBA1 software.
Abuse continues without any hesitation, any chances to implement proposed feature ?
A counter measurement is implemented since version 4.2.0: https://www.laptopu.ro/community/nlba-pc-software-version-history/nlba-pc-software-revisions/