Samsung has been heavily criticized for its delay in fixing a bug that causes clipboard crash in many Samsung devices, including the Galaxy S3, Galaxy S2 and the Samsung Galaxy Note 10.1 tablet. The clipboard crash is sometimes bricking the devices that are running Android 3.0 or later. However, the issue is now reportedly fixed with the Android 4.1.2 Jelly Bean update, Phones Review reports.

A good number of users have complained that a crippling copy and paste bug causes the clipboard to continually crash and does not allow use of the copy and paste function or any of the features associated with the Clipboard.

The issue has been explained in detail in a long and growing thread on the Samsung Developers Forum dated back to October 2012 that said, "Samsung devices running TouchWiz and Android 3.0 or higher have a fatal clipboard bug that can cause it to become permanently unusable until a factory reset. It seems to occur randomly. Whenever a user tries to copy something, this error occurs in the system ClipboardManager class."

"And the application that the user is using crashes. The only fix for this is to perform a factory reset or to clear the contents of /data/clipboard as a rooted user. Since this directory does not exist in stock Android, the fault is clearly with the Samsung software," the post continues.

The issue was later reflected in a tweet by the counternotions that said, "Don't copy & paste too much on Samsung phones, they'll become permanently unusable until a factory reset."

Although a Samsung developer, in reply to the complaint, said the problem will be resolved soon, the issue remained unsolved even five months after it was brought to the notice of the company. Samsung has been highly criticized for the length of time it has taken to fix the issue and the sentiment of frustration has been well expressed in the forum that runs to more than 100 posts now.

"I experienced this problem on my Galaxy S3, and had to do a factory reset to get the clipboard to work again. This is extremely annoying. We urgently need an over-the-wire update to fix this bug. If it happens again, I'm finished with Samsung," a user by the name Banjamin said in a post.

Hundreds of Samsung Galaxy users are reporting the issue from different parts of the world. "I have the same problem on my Galaxy S3 in Hungary," another user post said. While the report claims the Android 4.1.2 Jelly Bean update has cleared the issue, the trouble is far from over, as not all Samsung Galaxy hardware has received this software update yet.