Samsung Copy and Paste Bug
shkspr.mobi
shkspr.mobi
But please, does this bug really warrant "never trust Samsung", and "...Samsung's atrocious attitude to its customers..." and all that? I think someone needs to take a deep breath and try to calm down a little.
Here's the thing. There's a lot that goes into fixing even "simple" bugs for an existing product that is in production. Ideally, there is a lot of testing, and a lot of review for each and every fix.
In the case of mobile phones, there's even more hurdles, because the carrier has to approve the update too. They do their own testing, and it can take a while to get it pushed out. The carrier may be all up in your grill about other issues that you don't see (like something on the network side) that they prioritize over a clipboard bug that only affects users of alternate keyboards.
I don't know why a fix for this particular issue hasn't been pushed out yet. But there may be a good reason for that. Or a bad reason.
I'm not terribly impressed with some Samsung product divisions myself. My Bluray player does indeed play discs, but beyond that it is quite slow and crash-tastic. And my SK4G's original firmware was rather buggy. And my Nexus 10's video playback is a little glitchy.
Hmmm... maybe it is Samsung after all. At any rate, I don't know if there's a need to rant and rave about that though.
I still don't get what manufacturers are thinking here. I know they want to differentiate their devices and have unique features but I've yet to see an Android shell that wasn't buggy, slow, and usually ugly.
Not only does their software suck, but it keep users from updating their phones. I suffered through this with the horrible worthless Motorola Photon 4G (don't buy Moto phones kids, they are garbage), a dual core piece of overpowered bugware they wouldn't bring to Android 4 because they were too lazy to rewrite their nearly worthless third party tools like Moto Blur.
Companies like Samsung and Motorola clearly cannot handle software development and should leave it to the pros instead of cluttering and messing up an attractive, usable interface.
What I was not prepared for is Samsung is full of it when it comes to release dates for their software updates. Apple was bad in other ways, but the ability to get direct updates from the manufacturer is something I expect now because of the few years of iPhone I had.
To those who think it's simple enough to flash another rom on and get what I want -- my phone is not a toy, and my time is more valuable than constantly spending it in this way. I need the data in my phone, available and running at all times.
The fact that I'm first at Samsung's mercy, and then the carrier to get an official update while Google quietly pushes it's updates directly to it's devices has lead me to get a Nexus 4. I love my Galaxy note, but it's handicapped by not having the latest. Jellybean 4.2.1+ is for the first time an equivalent experience to iOS, and the Android 4.0.4 still has issues.
I hope that Samsung understands I appreciate and support their audacity in leading the charge into phablets, or flexible displays, but it really comes down to usability in software and it needs to be just as usable. I avoided the first two iPhones for this same reason.
Sadly, my Treo 650 still is more productive than these novelty purusing devices that provide more distractions than value. I am excited for the time our software skills move beyond creating novelty.
I hope Ubuntu's offerings become interesting enough moving forward.
The bottom line is this, I've had one Android phone that was the best phone I've ever owned (better than the iPhone 3G even), which was the Nexus One. I sold my N1 to a friend and it's STILL IN SERVICE and works perfectly.
I've had two Androids that were two of the worst three phones I've ever used and those were the Samsung Moment and the Motorola Photon. I'm seeing a pattern here.
Another possibly related problem is that spamming the setPrimaryClip function will cause a reboot. I haven't been able to cause the permanent lockup using this method, but running a program that runs an infinite loop seems to reboot the phone with 100% success.
You can see for yourself:
Or if you don't trust random APK's off the internet (this one has no permissions, though), just write your own test app - it takes 5 minutes:
http://developer.android.com/reference/android/content/Clipb...
Once again, this doesn't happen in stock Android or on any other manufacturer's device.
Car analogy: Headline: "Honda Civics prone to stalling".
You> Headline is wrong because if the Civic's engine is replaced with a Porsche engine, the problem does not occur.
The phones as sold to end users are subject to the bug.
- an exception
- a 1.5 year old model
- a discontinued product
- a model that Samsung did not ever advertise themselves
- the only high-end Samsung phone not running their software
The Galaxy Nexus is a Google phone manufactured by Samsung. It is not a Samsung phone like the SIII or Note II.
I am rooted though.
Also, I've had considerably less crashes on the S3 than on my previous N1.
If you don't use the Samsung Keyboard, items are still copied onto their clipboard - but you're unable to access them.
Which suggests that the issue should be affecting me, but it's not. Nor did I see it for the few days after getting the phone when I was using their keyboard.
I'm not suggesting that he's not experiencing the issue, but it's obviously not as universal as he suggests.
This is where I would usually say, "Silly me, I misread the article. Sorry, that's what I get for commenting in the wee hours."
So I re-read the article, and I can't see where it says that at all. The only mention of "keyboard" is in this section:
> As part of Samsung's desire to "improve" Android, they've created a "Clipboard History" function.
> It's pretty nifty. It shows you the last 20 items you copied - be they text or images. The only downside is that it only works if you're using the default Samsung Keyboard. (For iOS users - keyboards on Android are apps. You can swap them out if you want a better or different keyboard).
> If you don't use the Samsung Keyboard, items are still copied onto their clipboard - but you're unable to access them.
> Once you have copied around 20 items, the phone throws this error:...
When I read that, it seemed to be saying that the problem happens when you don't use the Samsung keyboard. That was the only way I could make sense of this: "The only downside is that it only works if you're using the default Samsung Keyboard... If you don't use the Samsung Keyboard, items are still copied onto their clipboard - but you're unable to access them. Once you have copied around 20 items, the phone throws this error:"
I still may have missed something, of course, but it's pretty unclear what the author means. Does the problem happen only with the Samsung keyboard? Only with other keyboards? Or what?
And now that I think about it, how would the input method selection affect the operation of the Copy action? Does Copy go through the input method at all? I get exactly the same select-text-and-Copy interaction regardless of what input method I've selected. Even if I select the Null Keyboard or Null Input Method, I still get exactly the same interaction for select and copy. This makes me suspect that the input method isn't involved in this interaction, although I don't know the Android architecture well enough to be sure.
Even so, I've been accused of being a paid schill for Apple, Dell, Google, RIM, Nokia, Samsung, Sony and - on one memorable occasion - Panasonic!
I really wish I was in the pocket of all these companies - I'd be minted :-)
This happened when there are quite amount of elements in the page (text, images, tables, divs). So instead of directly copying from the e-banking site, I now choose 'Search <s/n> in Google' option after blocking the text, and then Google, with much simpler output will render the S/N once again where I can copy it safely. Not sure if this is the problem with Android, or Samsung. I have a moderate amount of installed apps and running background services, my phone is S3.
Fast forward a couple of years and even Google Chrome in Android has bugs in a textbox when you remove characters with backspace (it swaps characters, move the cursor).
You have no idea. Issues that cross my mind:
- plain vs rich vs embedded: which one to paste, and at that time, if applicable, how to degrade one into the other? ask the original app, which knows the semantic? store multiple versions? store once, as-is, and hope the target app knows how to handle it, leading to inconsistencies?
- persistence across app life cycle: copy, close app, paste into other app. For years Linux, X or something simply could not do that and your paste would fail.
- UI concerns: it's easy to take the current, refined by the years way to handle clipboard for granted. remember how at some point some implementations required you to click a button on a damn toolbar. Notice how competing alternatives exist, such as X autofill with selection buffer pasted with middle click, xterm's left click to move left + right click to move right, OSX's growth of selection to the closest selection edge, or the infamous quick mode CMD.EXE way that gets copied with enter.
- security concerns: apps could be running with different levels of privilege, and you certainly don't want less privileged ones to have uncontrolled access to the clipboard buffer data, whose data may come from a more privileged source.
> plain vs rich vs embedded
When you copy you have multiple formats that you can apply. The target can accepts many of them.
> persistence across app life cycle
shared memory