Seeing so many reporting the same issue provides the kind of relief that actually having your car screw up AT the mechanic does. This is not a good situation. Samsung screwed this up royally.
It's clear they did not test at the resolution/refresh long enough (or at all). When speaking with someone from their Twitter support team, we talked about more than just this issue. When she told me that the "product specialist hadn't heard of this before" and that I was "the first person to report this" I got a little upset.
There's a reason that people are having a hard time reporting this. Samsung's knee-jerk reaction is to send out a tech. They have no efficient and easy-to-access mechanism for communicating findings like we have here. I asked her how exactly people were supposed to report this in a way that wasn't automatically deemed a hardware issue and she had no good answer. She agreed that it is a problem.
While the firmware might be defective, the bigger problem is Samsung's internal structure for dealing with consumers. Their Tier 1 people know absolutely nothing about the technology. They merely read off the screen. Between them and Exec Customer Relations, the decisions trees should have a "report to product specialist" node. This would allow educated users to more easily communicate with people who speak the language.
Are we mad about buggy firmware released into the wild? Sure. It's the lack of response, belligerent attitude and overall laziness of people on the ground level that are what infuriate educated users, though.
The horrible truth is that consumers are part of the QA process. Instead of partnering with us, they've made us adversaries. It's a problem, and it needs to be fixed.