This is the strangest thing
When I wrote the other day I could not get to that clipboard storage area at all, I tried multiple times even rebooting and nothing.
Now today, right now, I tried and I can get to the clipboard and have my clear button there.
This is weird (this is on my note 2), so that means eventually I think I will get this issue on my note 2, guess its time to root everything some how, Safely or something.
I think they're the same bug, realized different ways, depending upon the application. For example: It came to my attention while I was in Chrome, which it was crashing. Figuring it was Chrome at fault, I tried Dolphin. It crashed that, too. So I tried the default Android browser app. It did not crash that, but neither would it paste.
What that variance in behaviour says about the browsers is not comforting, either. If I were to guess: I'd guess that, of the three browsers, only the default browser app is handling the exception generated by the broken Samsung clipboard at all "elegantly," and it's not bothering to warn the user there's been an exception.
Jim
What about the fact that Shotgun solved his issue by clearing his clipboard from the stock keyboard? My GS3 will not show me any clipboard contents to clear, and the Clipboard Cleaner app I downloaded says my clipboard is empty.
Going on day 47 of this problem for me. Astounded that they haven't fixed it yet. Worst tech experience I've ever had. Shame because before this I was very happy with my switch from iPhone.
I'm not prepared to go that far quite yet, but I'm close. (What I suspect will happen is that, before either my window-of-opportunity to return the thing closes or Samsung fixes it, I'll grow tired of the whole issue, return the tablet and move on. We'll see.)
For the sake of your blood pressure, do not try to call Samsung customer "support" to raise this issue with them. The reaction I got from the other end when I tried to explain the nature of the problem was such that, just a couple minutes into the effort, I said "This is futile. Never mind." and terminated the call.
I tried to use their web site form, too. That is also broken. It lets you select WiFi-only Galaxy Tabs, but then gives you no choice for the model number it insists you must choose.
I'm sensing a pattern, here... It does not speak well of Samsung. As such: Even if I keep this tablet, I'll think twice before ever again considering a Samsung mobile device. I certainly won't be recommending them anytime soon.
Jim
The Following User Says Thank You to SEMIJim For This Useful Post:
I'm not prepared to go that far quite yet, but I'm close. (What I suspect will happen is that, before either my window-of-opportunity to return the thing closes or Samsung fixes it, I'll grow tired of the whole issue, return the tablet and move on. We'll see.)
For the sake of your blood pressure, do not try to call Samsung customer "support" to raise this issue with them. The reaction I got from the other end when I tried to explain the nature of the problem was such that, just a couple minutes into the effort, I said "This is futile. Never mind." and terminated the call.
I tried to use their web site form, too. That is also broken. It lets you select WiFi-only Galaxy Tabs, but then gives you no choice for the model number it insists you must choose.
I'm sensing a pattern, here... It does not speak well of Samsung. As such: Even if I keep this tablet, I'll think twice before ever again considering a Samsung mobile device. I certainly won't be recommending them anytime soon.
Jim
I've been dealing with them through Samsung Support's Facebook page. I at least get some attempts at help there and they understand that there is an issue and say they have reported it but that it's "being worked on." Nothing beyond that.
I know the little things in life bother people, some bother me, I did not like having this problem with my siii, but it happened and I had 3 choices..
1.. clear cache and reset
2.. root
3.. live with it and wait for samsung to fix it
I chose #1, It was a kind of a pain but really not that bad, and I have lots of stuff to configure LOTS.
It really was not the end of the world.
Now I had iPhones 2 (4 and 4s) for the year I owned them, the more I used them, for the life of me, could not figure out WHY NO WORD WRAP when you pinch to zoom, especially on a 3.5" screen, I mean WT?....
Now imagine trying to scroll left and right on just about everything web,email related, every day and night you use it, Boy way I glad to dich them, and to this day I can not understand why people line up for them. Cause that is one MAJOR SUCK feature of them. Lets not even get started on the yellow tinted, washed out screens some iPhone's came with and apple telling people thats normal, my 1st 4s came like that and I got it swapped at best buy where I purchased it, and the guy was looking at me sideways.... but did swap it and the 2nd iPhone 4s was perfect, no washed out yellow screen, and apple DOES NOT CARE EITHER...
Now NOTHING is perfect, and it may suck to get the copy and past bug, but in MY OPINION (nothing else), it really is not that big of a deal, noway near as the 2 I mentioned above.
Now I have a note 2 and my wife has my siii, she loves it, and does not want the iPhone back. I love these samsung's and hope they keep em coming, and I may some day replace the iPad with a samsung tablet also.
Thats why we all have choices, imagine everyone driving the same car...
I do hope samsung gets this fixed, but the features they offer outweigh the small bugs, annoying for sure but (in my opinion only) minor.
I was able to find the clipboard icon, but it doesn't respond...
Before my issue returned, I was able to see the past clippings when I pressed on the clipboard icon and able to clear them.
Shotgun84, u r either plain lucky or your problem was a different category...
I can't find any clipboard icon. To which specific bottom row button are you guys talking about?
I know the little things in life bother people, some bother me, I did not like having this problem with my siii, but it happened and I had 3 choices..
When you pay $300 or $400 for something, and it's broken, that's not a "little thing," in my view. Then again: I guess I'm "old school": To me, $300 or $400 is still a lot of money.
Quote:
Originally Posted by dfran1
I chose #1, It was a kind of a pain but really not that bad, and I have lots of stuff to configure LOTS.
And you know what: I wouldn't have a problem doing that if Samsung had the faintest clue as to what was causing the problem (besides their obviously broken clipboard code) so I'd have some hope I wouldn't have to turn around and do it again in another few days.
Quote:
Originally Posted by dfran1
I do hope samsung gets this fixed, but the features they offer outweigh the small bugs, annoying for sure but (in my opinion only) minor.
To you. To others of us that misfeature puts a serious crimp in the way we use our mobile devices. It's a show-stopper for me. Not because I wish to make a big deal of it, but because, for the way I use things such as this, it is a big deal for me.
Quote:
Originally Posted by dfran1
you must use the samsung keyboard and press and hold the mic Icon or 2nd in from the left bottom of the keyboard
Which is likewise broken design. If they felt they needed a manual clipboard manipulation interface, they should have made it available from Settings.
Which brings me to one of the most brain-dead aspects of this misfeature: Why is the clipboard being stashed in persistent storage in the first place? There is not another system I've ever used where the clipboard persists through logins, much less through reboots. If they hadn't put the clipboard in persistent storage the bug could be easily-mitigated by a cold start, rather than the extreme measures that are required.
In summary: It's a broken design, poorly thought-out, and poorly executed. To add insult to injury: It wouldn't even have happened if they'd just left the clipboard alone in the first place.
Quote:
Originally Posted by ANdroidno17
What about firmware upgrade? Does it fix the problem?
I've seen at least one report, maybe more, where upgrades to JellyBean did not fix the problem.
Quote:
Originally Posted by ANdroidno17
Does Samsung new about this?
They know about it. I've seen reports that it was reported to them as early as sometime in August. Near as I can tell: They still have no clue as to why it's happening.
I know the little things in life bother people, some bother me, I did not like having this problem with my siii, but it happened and I had 3 choices..
1.. clear cache and reset
2.. root
3.. live with it and wait for samsung to fix it
I chose #1, It was a kind of a pain but really not that bad, and I have lots of stuff to configure LOTS.
It really was not the end of the world.
Now I had iPhones 2 (4 and 4s) for the year I owned them, the more I used them, for the life of me, could not figure out WHY NO WORD WRAP when you pinch to zoom, especially on a 3.5" screen, I mean WT?....
Now imagine trying to scroll left and right on just about everything web,email related, every day and night you use it, Boy way I glad to dich them, and to this day I can not understand why people line up for them. Cause that is one MAJOR SUCK feature of them. Lets not even get started on the yellow tinted, washed out screens some iPhone's came with and apple telling people thats normal, my 1st 4s came like that and I got it swapped at best buy where I purchased it, and the guy was looking at me sideways.... but did swap it and the 2nd iPhone 4s was perfect, no washed out yellow screen, and apple DOES NOT CARE EITHER...
Now NOTHING is perfect, and it may suck to get the copy and past bug, but in MY OPINION (nothing else), it really is not that big of a deal, noway near as the 2 I mentioned above.
Now I have a note 2 and my wife has my siii, she loves it, and does not want the iPhone back. I love these samsung's and hope they keep em coming, and I may some day replace the iPad with a samsung tablet also.
Thats why we all have choices, imagine everyone driving the same car...
I do hope samsung gets this fixed, but the features they offer outweigh the small bugs, annoying for sure but (in my opinion only) minor.
My GS3 doesn't word wrap...am I doing something wrong?
Also, factory reset is just a temporary fix.
Lastly, this isn't a missing feature like word wrap, or something the phone doesn't do that we wish it would. It's a vital function of the phone for some of us - 75% of what I do with my phone requires the use of cut and paste.
The Following User Says Thank You to hiddenmickey For This Useful Post:
My GS3 doesn't word wrap...am I doing something wrong?
Also, factory reset is just a temporary fix.
Lastly, this isn't a missing feature like word wrap, or something the phone doesn't do that we wish it would. It's a vital function of the phone for some of us - 75% of what I do with my phone requires the use of cut and paste.
Quote:
SEMIJim
I'm not here to argue with anyone, i'm just stating my opinion, and that is all. PLEASE.
I am very sorry to offend anyone on this matter!
On the word wrap feature, compared to the iphone, the siii screen size is accommodating as the iphone 3.5" is not, and when I had my other android phones in that screen size bracket, they would wrap. Sorry for the misunderstanding.
I'm not here to argue with anyone, i'm just stating my opinion, and that is all. PLEASE.
I am very sorry to offend anyone on this matter!
And a couple of us stated our opinions. That's how "discussion" works Nobody's offended.
Quote:
Originally Posted by dfran1
I really do hope Samsung fixes this SOON.
I'm sure they will... eventually. I don't know as I'd bet on "soon." From what I've been reading, Samsung has a rather fine disregard for "customer service." In fact, not to put too fine a point on it, they appear to have an abysmally poor reputation in that regard.
So, following the links at Samsung's web site, I ended-up submitting a support issue.
I had written, in part:
Quote:
First of all: My tablet is actually a GT-P5113TSYXAR. Your web form would not let me select that, so I chose something it would let me select.
The problem: Samsung's development team has broken the Android clipboard support. When the bug hits, copy-and-paste stops working. Trying to use it crashes applications. The only way for the user to "fix" the problem is to either do a factory reset or root their device. Note: This problem applies to ALL Samsung devices with current versions of Ice Cream Sandwich or Jelly Bean, including mobile handsets.
I also supplied links to this thread and others.
Samsung's reply:
Quote:
Thank you for your inquiry. We understand that the cut, copy and paste feature does not work as it crashes and as you mentioned that this applies to all devices that has an Ice Cream Sandwich or Jellybean Android versions. We apologize for the inconvenience that this may have caused you.
So they know.
Continuing...
Quote:
You have contacted Samsung Telecommunications of America and that is the reason why the model name of your device is not listed on the drop down option.
Mind you: It was their web site that took me there, after I'd entered the proper model number earlier on.
Quote:
The issue is one that is best helped through calling our Customer Support Center for Electronics...
With pointers to what menu options to chose, and the order. I dunno. When I tried that before, the resulting conversation made me feel like I'd rather commit Seppuku with a rusty spork
Of particular note: Not a single word as to when they expect to push a fix out for this problem, or even that they're working on it.
Jim
The Following User Says Thank You to SEMIJim For This Useful Post:
Thank you for your inquiry. We understand that the cut, copy and paste feature does not work as it crashes and as you mentioned that this applies to all devices that has an Ice Cream Sandwich or Jellybean Android versions. We apologize for the inconvenience that this may have caused you.
I don't think they meant that they actually "understand" that it doesn't work, as in acknowledge the problem. I think that was a generic form letter type response to an issue that that department is not involved with, or doesn't want to involve itself with. As in "We understand that [insert customer's complaint here]".
I don't think they meant that they actually "understand" that it doesn't work, as in acknowledge the problem. I think that was a generic form letter type response to an issue that that department is not involved with, or doesn't want to involve itself with. As in "We understand that [insert customer's complaint here]".
I suppose that's possible.
I followed the recommendation in the email, choosing the 2nd option. Must have got a completely different group of CS people, because this time, instead of getting somebody allegedly with a Christian name, but speaking distinctly accented English, I got somebody with an unusual name, speaking flawless American English.
I explained the nature of the problem, and how wide-spread it was. She opened a ticket for me and, if I understood her correctly, escalated it right off.
Btw: This problem is apparently far more serious than "just" cut, copy and paste. Just saw Comment nbr. 80 at code.google.com and did what that poster suggested: Entered "android.sec.clipboard.clipboardexmanager" into a Google search. Turns up reams of hits. Hard to say how many of them actually related to the TouchWiz custom clipboard code, but it would appear that at least some of them do.
I would urge everybody who's experienced or experiencing this problem to use either the web form or, if a WiFi only version tablet, call, to report this problem. The CS rep. to whom I spoke just minutes ago agreed that complaint volume will affect Samsung's prioritization.
I seem to have a new variation of this. I'm running 4.1.1 on AT&T in the US. Since Sunday, there have been three instances where I've gone to copy something and after I hit copy, the phone reboots. It doesn't happen all the time. I've tried the clipboard clearing tip above, we'll see if that helps. Otherwise, I'll try a reset. Definitely going to let Samsung know about this.
I seem to have a new variation of this. I'm running 4.1.1 on AT&T in the US. Since Sunday, there have been three instances where I've gone to copy something and after I hit copy, the phone reboots. It doesn't happen all the time. I've tried the clipboard clearing tip above, we'll see if that helps. Otherwise, I'll try a reset.
Thank you for your inquiry. We understand that the copy and paste feature in your Samsung Galaxy S III model SCH-I535 from Verizon is not working. We apologize for the inconvenience that this may have caused you.
We suggest clearing the data of the Samsung Keyboard application to fix this concern. On the Home Screen, tap on Menu - Settings - Application Manager - All - Samsung Keyboard - Clear Data.
If this process didn't work, we advise performing a hard key reset to set the phone to it's factory setting to resolve this issue. Please check the link below for this process.
Needless to say, clearing the keyboard data did not work and I don't want to factory reset. So, no help.
So you tell them, firmly but politely, that their "solution" is not acceptable and you require the issue be escalated. That's what I did just an hour-and-a-half ago.
I made it clear that I would continue escalating the problem until it got to Kwon Oh-hyun, if necessary.
Quote:
Originally Posted by RyanLupin
Samsung's official fix for their incompetence is to factory reset? What??
Here's their response to my telling them FR is not sufficient. The model # was entered. I'm about ready to root.
Quote:
Thank you for contacting Samsung Telecomunications America. We understand that you are experiencing issue with the Samsung Keyboard.
We sincerely apologize for the inconvenience.
We did not receive enough information regarding the product for which you have requested assistance. Please contact us with additional information regarding the model number about which you are inquiring, so that we may assist you better.
Let us know hte exact issue you are experiencing the issue with the Samsung Key board
Do you have more questions regarding your Samsung Mobile Phone? For 24 hour information and assistance, we offer our new FAQ/ARS System - Automated Response System at Samsung.
Here's their response to my telling them FR is not sufficient. The model # was entered. I'm about ready to root.
They should have given you a ticket number when you first opened the issue. That ticket number is critical. It establishes "history." From then on: All you need is the ticket number.
They should have given you a ticket number when you first opened the issue. That ticket number is critical. It establishes "history." From then on: All you need is the ticket number.
Jim
Never had a ticket number. Just what I posted earlier, and a message saying not to reply to message because it's for outbound only and a link for "If you have additional inquiries related to your original email" which is what I used - and automatically filled in all the information which they acted like they didn't have the 2nd time. Whatever - don't have time for their incompetence.
After having submitting my ticket on the 10th, and receiving neither the promised emailed confirmation nor a callback w/in 48 hours: I called back to have the ticket escalated. That was done and I was again promised a callback w/in 48 hours.
On Friday, after not having received the promised callback, I called Samsung to have the ticket escalated again. They claimed they tried to call me on my home phone and, when they got no answer, closed the ticket. Thing is: I'd given them my wireless phone number and there was no message on the home line's answering machine. Nontheless, they opened a new ticket for me and immediately escalated it to a product support supervisor. I'm again supposed to receive a callback w/in 48 business hours.
Meanwhile, a developer has posted to Samsung's development forum that he's found that, not only does Samsung's broken software crash devices, but it may have introduced a security vulnerability:
Quote:
... some of your developer's math isn't correct. The clipboard shows a maximum of 20 entries, but /data/clipboard often contains 22 or 23 entries! So even if I think there is nothing confidential left in my 20 clipboard entries, there might be an entry 21 or 22 on the file system, where there is confidential data, e.g. passwords, that I have copied to the clipboard and I am not aware of this. This is a security flaw!
This is neither a pre- nor post-update problem. This is a problem with Samsung's custom clipboard code. There is an XDA thread more germane to the problem: http://forum.xda-developers.com/showthread.php?t=1766706 and perhaps others.
I had this problem on ICS on my Rogers Galaxy S3. Whenever I copied from any application the app would crash. I just upgraded to Jelly Bean the other weekend and did a factory reset after the upgrade. At first the copy paste was fine. However, now it works in some applications sometimes but most times when I copy something it doesn't just crash the application, but the whole phone reboots! So in my opinion it's even worse now. The factory reset was an all day process since Androids backup options are still terrible. I spent all day backing everything up, restoring it, recreating widgets, reinstalling applications, reconfiguring applications, homescreens, settings, etc. I don't want to do that every week to keep working around this issue. This is crazy that Samsung haven't fixed it yet.
The Following User Says Thank You to jaydee77ca For This Useful Post:
This is neither a pre- nor post-update problem. This is a problem with Samsung's custom clipboard code. There is an XDA thread more germane to the problem: http://forum.xda-developers.com/showthread.php?t=1766706 and perhaps others.
Jim
I understand that it's a spurious event, just like many others, e.g. notification bar scroll lag, battery drains, clock timing issues, etc.
I was simply adding to the dialogue here.
Regarding to the other XDA thread that you shared, unless I'm totally blind () the posts there are all pre-JB. The URL I provided covers just about every issue/problem that has come up since the update. I guess that's why it's now 32 pages long!
Regarding to the other XDA thread that you shared, unless I'm totally blind () the posts there are all pre-JB.
That's that thread. Here and elsewhere you'll find plenty of JB users that have experienced problems related to Samsung's clipboard code--just above, for example.
I just updated to JB, and now when I attempt to copy text the phone reboots (with ICS the app just crashed).
EDIT: PROBLEM SOLVED
After my phone rebooted, I decided to go into S Memo and try it there. First, though, I switched to the Samsung keyboard (I use SwiftKey) and attempted to clear the clipboard using the method described by another user earlier in this thread (hold down 2nd key from the left on the bottom, then select the clipboard - then clear all). The clipboard was, in fact, full with 20 items - despite Clipboard Cleaner saying my clipboard was empty when I attempted to use it. Before JB update, attempting to clear the clipboard in this manner using the Samsung keyboard did not work - selecting the clipboard icon did nothing. Now, after JB update, I was able to see the clipboard items and clear them. Following this, I am now able to cut and copy text in various applications (including Chrome) without a problem.
Last edited by hiddenmickey; December 17th, 2012 at 10:59 AM.
The Following User Says Thank You to hiddenmickey For This Useful Post:
I just updated to JB, and now when I attempt to copy text the phone reboots (with ICS the app just crashed).
EDIT: PROBLEM SOLVED
After my phone rebooted, I decided to go into S Memo and try it there. First, though, I switched to the Samsung keyboard (I use SwiftKey) and attempted to clear the clipboard using the method described by another user earlier in this thread (hold down 2nd key from the left on the bottom, then select the clipboard - then clear all). The clipboard was, in fact, full with 20 items - despite Clipboard Cleaner saying my clipboard was empty when I attempted to use it. Before JB update, attempting to clear the clipboard in this manner using the Samsung keyboard did not work - selecting the clipboard icon did nothing. Now, after JB update, I was able to see the clipboard items and clear them. Following this, I am now able to cut and copy text in various applications (including Chrome) without a problem.
I think there are 2 "strains" of this problem.
First strain is when the copy paste issue happen, the user can find the clipboard and clear the clips without rooting.
Second strain is when the copy paste issue happen, the user can find the clipboard, but the clipboard is inaccessible. Phone needs to be rooted to clear the clipboard clips.
First strain is when the copy paste issue happen, the user can find the clipboard and clear the clips without rooting.
Second strain is when the copy paste issue happen, the user can find the clipboard, but the clipboard is inaccessible. Phone needs to be rooted to clear the clipboard clips.
But if you read my explanation, you see that I was in the first camp before updating to JB - could not access the clipboard. After updating, I could access my clipboard and clear it.
Bottom line - those of you who are not able to access and clear the clipboard, have you updated to JB? It worked for me.
I think that's a good idea!
Samsung has far too many crapware and doesn't work very well with Google...
The Nexus S is the worse Nexus phone, in my opinion...
Bottom line - those of you who are not able to access and clear the clipboard, have you updated to JB? It worked for me.
Line under the bottom line: Apparently you've missed the posts from those who have upgraded to JB, and, not only has the problem remained, but, for some, it's become even worse?
Line under the bottom line: Apparently you've missed the posts from those who have upgraded to JB, and, not only has the problem remained, but, for some, it's become even worse?
Jim
Have they tried clearing the clipboard after upgrading? I had to clear the clipboard after upgrading - otherwise the problem was worse, as you say (rebooting instead of just crashing apps). 6 pages of posts, I'm not going back and looking at every one. Just giving my experience, certainly it will help SOME people.
The Following User Says Thank You to hiddenmickey For This Useful Post:
Device(s): Samsung Galaxy III (SCH 1535), Asus Transformer
Carrier: Verizon
Thanks: 2
Thanked 0 Times in 0 Posts
works for me now, too!
THANK YOU very much- with the update to JB 4.1.1 over the weekend, I tried this method & I can now copy & paste again AND no crashes- so happy!! I hope it stays this way!
-------------------------
Quote:
Originally Posted by hiddenmickey
I just updated to JB, and now when I attempt to copy text the phone reboots (with ICS the app just crashed).
EDIT: PROBLEM SOLVED
After my phone rebooted, I decided to go into S Memo and try it there. First, though, I switched to the Samsung keyboard (I use SwiftKey) and attempted to clear the clipboard using the method described by another user earlier in this thread (hold down 2nd key from the left on the bottom, then select the clipboard - then clear all). The clipboard was, in fact, full with 20 items - despite Clipboard Cleaner saying my clipboard was empty when I attempted to use it. Before JB update, attempting to clear the clipboard in this manner using the Samsung keyboard did not work - selecting the clipboard icon did nothing. Now, after JB update, I was able to see the clipboard items and clear them. Following this, I am now able to cut and copy text in various applications (including Chrome) without a problem.
Have they tried clearing the clipboard after upgrading?
Some of the people that have observed the problem, even after the JB upgrade, are developers. Others have reported it working after the JB upgrade, only to fail again later on. So if it's working for you now: I'm happy for you and I truly hope it continues working for you, but don't be surprised if the problem comes back again later--as it has for others.
Posted to the "clipboard crash" thread on Samsung's developer forum:
Quote:
Good news and bad news.
To start with the bad news: the clipboard issue is not the biggest issue at the moment.
Developers discovered a very dangerous root exploit (For example on S3).
From the developer of a patch to defang the root exploit:
Quote:
You should be very afraid of this exploit - any app can use it to gain root without asking and without any permissions on a vulnerable device. Let's hope for some fixes ASAP !
I'm on the unlucky side: JB, Samsung keyboard, touch and hold second button down, tap clipboard... nothing happens, zero: no itens shown on clipboard, no option to clean it...
Thank you for signing up to receive updates for the 374
An email has been dispatched to confirm your signup. Please click the link in the email.
Buy the Samsung Galaxy S III
Sign up for instant notification when the Samsung Galaxy S III goes on sale!
The Samsung Galaxy S3 is the company's flagship device of 2012. As one of the most anticipated devices of the year, this device is the first to come with a Exynos 4 Quad processor. It also has Android 4.0, a 4.8-inch 720p Super AMOLED ... Read More