I can't give you any definite date but I will get back to you on that issue. Please wait for an announcement from "Bitmain" username on that part.
If you have a solution, you may submit the Github Commit
Thank you for your patience.
Now that you are, can you explain why S2 users are still waiting after 2 months for the fix you promised within two weeks?
If you have a solution, you may submit the Github Commit
Thank you for your patience.
We are still here... we didn't go offline yet. You may see us come online, offline time to time. may stay online status but may have no one actually online.
Now that you are, can you explain why S2 users are still waiting after 2 months for the fix you promised within two weeks?
That's exactly the problem: user "Bitmain" is not answering any questions about the matter whatsoever, & it was that user who promised the fix 2 months ago. What does it take to get a straight answer from anyone there? Bitmain publicly promised the S2 users this would be done - but since then there has been nothing but silence, while in the meantime users are having their hash rate stolen because of it - are you going to compensate them? Of course not.
I'm sure that if your S2 farm suddenly had it's hash rate redirected in the same manner, you'd provide a fix as quick as a flash, do your customers not deserve the same treatment? After all, they paid you.