I was the mod who deleted your answer.
The link-only answer stuff has already been covered pretty well by others, but there's also another problem not mentioned here. What you've also been doing here is astro-turfing old posts with this same answer.
Five of your answers were created within an hour of each other and posted on old questions that already have accepted or highly upvoted answers. Your answers were more or less identical and linking to your github project.
All of this is suggesting that you hunted down specific question just so that you could post a link to your project. This is not something we welcome in our community and it is viewed as excessive self-promotion.
You need to go and spend time contributing answers on our site that aren't fixating on this one problem that you've solved. Go and help solve other problems, there's certainly no shortage of Android questions to keep you busy.
If this type of question arises again, and you think your project will help, then feel free to mention it, but please abide by the general guidelines that answers should be able to stand on their own which is hugely important to our site. Also, if you're posting the same solution each time then there's a fairly good chance that the questions are all duplicates, so flag them instead.
This answer, which we didn't delete still doesn't give much of a clue on how to solve the OP's problem should your GitHub repo go AWOL. You have a whopping 30K characters available to write up a nice detailed canonical answer on how you solved this particular problem. So why not spend time doing this with code snippets and some nice annotations?
Then go and find a more recent question where your answer addresses this problem and post your nicely detailed solution there. If your answer is well written then you should get an accept. After that, if you see the same problem you can either flag as a dupe or (when you have enough rep) add a comment pointing at your nice super-answer.