Since the KitKat update pushed to my SGS3, I have had a number of big issues with my phone, which the benefits of KitKat cannot outweigh in order to make me happy about this update. In addition t...
See more...
Since the KitKat update pushed to my SGS3, I have had a number of big issues with my phone, which the benefits of KitKat cannot outweigh in order to make me happy about this update. In addition to the battery life and performance problems which many of you have also reported encountering, I've had major issues with the Swype keyboard. Here are the issues I've encountered with Swype Huge spikes in lag on input recognition: I can Swype a word and the tracer line can take several seconds to appear, which sometimes causes it to not recognize that I ended my Swype, requiring me to tap the end of the tracer line as accurately as I can to try and salvage the word I was Swyping, but more often than not, I end up having to delete the word and try again "Dropped" words: Sometimes, when I successfully Swype a word (tracer line appears, I was very accurate in my Swyping, etc), it fails to input the word and will just give me a space. No selection of "did you mean?" words above the keyboard, no "sorry try again" message above the keyboard, nothing, just a space Lack of input recognition when receiving text messages: this might be a phone performance issue and not Swype's fault (actually, all my issues might be and probably are caused by the massive performance drop caused by this boondoggle of an OS update) but when I receive text messages while I'm writing something, Swype will lock up and stop recognizing my inputs for a few seconds while the phone handles the arrival of the new text message Load Lag: when selecting a text field to start inputting text, whether it be in Chrome, the default text messaging, Facebook, or Gmail, it can be several seconds for the Swype keyboard to appear (the longest I've seen is 20 seconds). I've encountered this in a number of scenarios, including times when the text field I was using was in the only running app following a close of all other apps and a dumping of the RAM cache to free up memory capacity, so it does not seem to be isolated to times of high CPU and/or RAM load. Anyone else experiencing one or more of these problems with Swype? If so, have you been able to solve them without sacrificing Swype? I fell in love with this keyboard back in the days of my Moto Droid X, so I don't want to give it up unless I absolutely have to. Thanks!