Wow, this speaks volumes about their QA process, especially for Android. This bug is known since October '12, how hard can it be for a company with 50k employees to fix a bug like this?
As long as one uses statistical machine learning, edge cases like this are unavoidable.