Samsung Galaxy Tab 2 Fixing Clipboard Bug

By -

Problem:

I have recently come up with a problem with Samsung tablets that is causing quite a fuzz.
After a while using one of Samsung Android tablets, we start getting issues while opening applications or trying to write stuff using the keyboard. The problem seems to be related to an issue with the Samsung Clipboard API, while using the default keyboard.

Error: "Agente Feedback do Market parou" (Portuguese) or "Unfortunately, Market Feedback agent has stopped" (English)

Description: Unable to open some applications or write text using the keyboard

Specs:
Samsung Galaxy Tab 2
Model GT-P5110
Android 4.0.4
Kernel 3.0.8-846656-user

Stacktrace:
nulljava.lang.NullPointerException
at android.content.ClipboardManager.setPrimaryClip(ClipboardManager.java:146)
at android.content.ClipboardManager.setText(ClipboardManager.java:267)


Solution
There are various ways to fix this, but sadly none of them is an easy deal.

Solution #1 - recommended by Samsung
This option means restoring the tablet data to factory defaults. Needless to say you should back up everything before doing so, and removing SIM or SD cards if existent.

The actual process is:
- Go to the context menu on the lower right corner of the screen
- Click "Settings"
- On the settings screen, below "Personal", click "Back up and reset"
- Uncheck "Automatic restore" to prevent current issues persisting
- Click "Factory data reset"
- Click "Reset device" and follow the reset procedure


Solution #2 - root
In order to actually fix this issue we just need to do something as simple as removing the /data/clipboard folder, which will reset the clipboard and fix the problem immediately. However, access to this folder isn't available unless the device is rooted.
It's not an easy process and could easily brick the device if not done properly. Also, it will most likely void the garanty. Still, it is an option and the whole process is available on xda-developers.


Prevent Process
If you own such an Android tablet from Samsung, either you don't have this issue or have done one of the two solutions above, you should make sure that this doesn't happen again. Since Samsung has not yet come up with an update or easier solution for this issue, I recommend doing two things to remove the possibility of this error ocurring, or at lest lower the chances.

#1 - Remove the screen capture icon
The icon that comes by default and captures a screen shot can be quite annoying since you can easily click it unintentionally, and since it uses the clipboard, it can contribute to the bug.
To remove it:
- Click "Settings"
- Click "Display" under "Device"
- Click "Quick launch"
- Choose "None" instead of "Screen capture" or any other option available

#2 - Use a third party keyboard
Since the Samsung default keyboard seems to be one of the most probable culprits that is causing this error, not using it seems to be the strongest fix, and many users have not experienced this bug again after using another keyboard app.
- Download and install a keyboard app (e.g. Jelly Bean or Ice Cream Sandwhich)
- Go to "Settings"
- Click "Language and input" under "Personal"
- Check one or more keyboard apps (this will make them all available for usage)
- Now if you open any application that popups up the keyboard, you will still see the default Samsumg keyboard. However, you will see a small keyboard icon in the lower right corner, next to the clock. If you click it, you will be able to pick a different keyboard, which will then be used by default on all applications.

Comments

Post a Comment

Popular posts from this blog

Breaking down document locking in SharePoint

By -
Image
This is a topic I've been meaning to discuss in a while. We open, change and close documents almost every day, and sometimes we collaborate with other people at the same time on those documents. SharePoint brings all co-authoring features we need, straight out-of-the-box, but sometimes, there are problems. While things are starting to look better on the cloud side, the concept of document locking is still very much up-to-date and understanding how it works and what to do when things go wrong is crucial. In an article that has since disappeared the Microsoft Knowledge Base (but still available here ), Microsoft explains it best: When a document is opened by a client program, Windows SharePoint Services puts a write lock on the document on the server. The write lock times out after 10 minutes. Users cannot modify the document during the time when the document is locked. In a scenario where the program that opens the document unexpectedly quits or crashes and you try to open the do
Read more

Working around X-Frame-Options for iframes

By -
Image
The problem: One of the first things we noticed after migrating to SharePoint 2013 was that our iframes have stopped working, giving the error: "Refused to display 'http://contoso/pages/home.aspx' in a frame because it set 'X-Frame-Options' to 'SAMEORIGIN'." Quickly we could see that this is in fact a security mechanism to prevent click-jacking and others: "The X-Frame-Options HTTP response header can be used to indicate whether or not a browser should be allowed to render a page in a frame or iframe. Sites can use this to avoid Clickjacking attacks, by ensuring that their content is not embedded into other sites." Soon we realized that, starting SharePoint 2013, an HTTP Module is adding the header " X-Frame-Options " by default, with the value " SAMEORIGIN ". This is effectively preventing the rendering of pages outside the scope of the current web application. The (attempted) solution: So what to do?
Read more

Document ID not being generated

By -
Image
Problem In a scenario where we have many document Content Types, we may want to enable Document ID - aka "Permanent Links" - which is a feature in SharePoint that assigns a specific ID for each document. That ID never changes even if the document is renamed or moved to another location. In this scenario, the Document ID field was being generated for some libraries/content types, but not others, which is a surprisingly common problem. Background There are several stages we need to go through to enable use this mechanism. Stage 1 We enable the feature in the Site Collection Features. Stage 2 Under Site Collection Administration > Document ID Settings, we need to enable the assignment and pick a prefix. The IDs use the format: PREFIX-LISTID-LISTITEMID ( ref ) Where: PREFIX: the preconfigured prefix for the site collection, which can be any set of numbers and letters between 4-12 characters LISTID: the property docid_msft_hier_listid of the list
Read more