Q: IOS 8 copy paste problem + slowdown

Use the link below to send feedback.

http://www.apple.com/feedback/

Thanks a lot! I sent my feedback, even thought I do not expect a quick answer/solution considering the number of people in this post experiencing the same problem

This is the only way I know of other than writing directly to their CEO too!

http://www.apple.com/feedback

You're welcome. I don't know how quick the solution will be but I do know Apple can't fix a problem unless they know about it and Feedback is the only way to let them know.

Exactly my thought!! That's why I wanted to report it even if a hundred somewhat people are experiencing the same problem. I also imagine that if everyone having this problem sends them a feedback e-mail, they might find a solution quicker, just saying

I wish everybody did too. Hopefully the solution comes sooner then later.

I think what is going on for me in the Safari pasting issue is that the URL is shown as highlighted, but it isn't actually, so a cut or a copy doesn't return any characters so the previous cut/copy text remains. I unselected the URL then did a Select All then Copy, and it worked properly. Now if iOS8 would stop putting 'a' in front of random(?) words I type, I would be happier. And can't, and don't are properly spelled in spite of what Apple's spell-checking thinks.

Please also someone try this:

http://bugreport.apple.com/

I'm not sure if it works for the general public though, or for developers only (I'm a developer), but I'd like to know if it *does* work for you!

The link took me right to the bug report so it works for the general public.. Thank you.

I upgraded to iOS 8 on my iPhone 4S without considering reports of severe memory issues people have made online.  So, firstly, be aware upgrading your iOS is irreversible.  Secondly, I found that Reducing Motion, recommended by an in-store Genius, (Settings > General > Accessibility > Reduce Motion > On), makes a huge improvement in max running tasks and Safari open tabs.  It also helps clip board responsiveness, boot time, glitches, and memory-intensive apps (such as HD Video).  Thirdly, I recommend the highly-praised, well-designed Battery Doctor app which will let you clean your memory from the Control Center drawer or a one-tap home screen shortcut.  It also doesn't hurt to close tasks and reboot occasionally.  Fourth, Fifth, and Sixthly: Consider NOT upgrading to iOS 8 on devices with less than 1GB of RAM if it's not too late !!!!!!!

Shopie~ wrote:

 

Exactly my thought!! That's why I wanted to report it even if a hundred somewhat people are experiencing the same problem. I also imagine that if everyone having this problem sends them a feedback e-mail, they might find a solution quicker, just saying

I would think that 100 people opening up trouble tickets with Apple Support would get quicker action.

Apple Support

http://www.apple.com/support/

Apple Retail Store - Genius Bar

http://www.apple.com/retail/geniusbar/

Star Traveler:  your suggestions have been tried by many along with reporting bug and issues.  It's common sense that when multiple end users with different device types/models are experiencing like problems there is wasted effort to attempt to do process of elimination steps to determine if there is a particular app issue.  The common denominator is IOS 8.0 and rests with Apple to fix.  Apple has resources, knowledge, and tools to quickly resolve the issue. At minimum, offering the option for impacted customers to rollback to 7.0 would be a step in the right direction until Apple has a permanent fix.

There is absolutely no consistency in how the copy paste issue will surface.  It's "consistently" random.  I can copy paste the same thing in an email or iMessage multiple times one right after the other to create a string of the same paste.  Then, out of nowhere a paste ends up being something from two days prior versus the ten I just pasted. The Apple Subject Matter Experts need to resolve.

<Edited by Host>

woodyrich wrote:

 

At minimum, offering the option for impacted customers to rollback to 7.0 would be a step in the right direction until Apple has a permanent fix.

 

 

No matter how how many times you or others want to tell Apple to roll back to a previous system, it isn't going to happen because it has NEVER HAPPENED in the history of iPhones, iPods, and iPads and/or the history of iOS. You're telling Apple to do something that would open up another whole round of TROUBLE TICKETS. That's not what Apple considers to be "solving something" ... LOL ...

AND THEN ... apart from the rollback, which is never going to happen, the situation of various people having various problems -- that does not ALL translate back to an "Apple problem" requiring an Apple fix. Many of the problems, as I have seen here already, can easily be solved by taking appropriate troubleshooting methods and doing one of several solutions given here.

If you end up just telling people to simply "wait for Apple" ... you'll end up having a bunch of people waiting for something that may NEVER HAPPEN for them, because the "fix" was not Apple's thing, but was something that needed fixing ONLY on their iPad!

Pepole definitely need to go through the troubleshooting and Apple Support.

I have sent an email back to the supervisor tech person at Apple who has been handling my case.  I directed her yet again to go look at all the complaints here on this forum and to please try to get this info to Apple's engineers.  Other than that at this point, I have no further answers.  I have done everything suggested by Apple and by those here offering 'fixes'  I don't think there is a fix at this point and we are at Apple's mercy and have to wait on them to address it.  Only thing I know to suggest is to call Apple and have them open a case file on your problems.  I know they will direct you to try all the things they had me try numerous times.  Maybe if they get enough open cases on file, they will address it.

GASusiQ wrote:

 

Only thing I know to suggest is to call Apple and have them open a case file on your problems.  I know they will direct you to try all the things they had me try numerous times.  Maybe if they get enough open cases on file, they will address it.

Opening a case file on a problem that one has not been able to solve is exactly what one should do, as Apple does track those and acts on those case files. THAT is exactly the place where Apple will be looking for things to "work on".

AND ... in order to shortcut the process with Apple, be sure to be talking to Apple Support AT THIS POINT ... with a factory default setup and be sure to tell them that ... and that none of your data is on there. The following is what I posted elsewhere ...

Follow this procedure for a Troubleshooting Methodology ... basically reset to factory default condition -BUT- be sure to do the following methodically and also to follow the part with Apple Support!

First you want to make sure you have several backups of your data and done with a couple of "different" sources. Be sure to understand what data is backed up and what is NOT on iCloud Backup and iTunes Backup. Use a variety of methods for backup ... you might check into Dropbox, in addition to your Apple options.

Then turn off your desktop anti-virus software when using iTunes for this reset to factory default. After you do that reset, then leave your iPad in its factory default state and see how it operates then. If you encounter any problems in that factory default state, then take it to Apple Support, and let them know that you have just reset it to that state with iTunes and have not put any of your data back on and it is operating in this fashion (whatever the problem is) in that pristine state. Make sure you keep that trouble ticket number, because if it has to be escalated through Apple Support, you're going to find all communications tied in with that number. If the lower level help isn't able to help you, then escalate it to a higher level to examine the problem. Keep at it with that trouble ticket number until Apple Support arrives at a solution to that problem. Be methodical and keep at it.

On the other hand, if everything is okay with the factory default condition, then restore your backup. Some people have discovered that the problem resides in the apps or something in the restored backup. If that's the case, then it's going to be trying and difficult to find out which developer's app is causing you the problem. And ... it's true ... that a developer not following Apple's instructions and guidelines for his app can CAUSE YOU TROUBLE. This kind of thing does happen from developers, especially when a new system upgrade comes out, because some developers ignore what Apple tells them about changes coming, and what they do BREAKS SOMETHING.

This is a troubleshooting methodology that you are going through. See it through to the end.

Choosing an iOS Backup Method (Should I Use iTunes or iCloud to back up ...)

https://support.apple.com/kb/HT5262

Back up and Restore your iOS Device with iCloud or iTunes

http://support.apple.com/kb/ht1766

iTunes: About iOS Backups

http://support.apple.com/kb/ht4946

Create and Delete iPhone, iPad and iPod Touch Backups in iTunes

http://support.apple.com/kb/ht4946

iOS: Troubleshooting Encrypted Backups

http://support.apple.com/kb/TS5162

Use iTunes to Restore your iOS Device to Factory Settings

http://support.apple.com/kb/ht1414