Okay.. This is starting to piss me off pretty bad, to the point where I'm considering having my phone sent to a service center.
Am I the only one experiencing (quite often - like .. at least 10-20 times a day depending on usage), when typing a text message - somehow it's like the "touch overlay" that activates the keys on the onscreen keyboard is offset about 1 cm to the right and 0.5cm down??
Meaning that if I press on the screen where it says "B" it will highlight and press "G" instead .. and "G" will fetch me an "E" .. and so on (and yes this means I'm not able to press either space or "P" because that would require my finger to be pressing a point 1cm outside of the iPhone screen
)
Somehow though when I try pressing "backspace" (delete - which is also as far right as possible) .. it works just fine?? .. but trying other keys again afterwards, its still broken.
I've tried doing all kinds of random stuff to realign the keyboard - even going to homescreen and back into text, won't fix it. However waiting a minute or so without doing anything fixes the issue??
Running on the latest firmware that isn't developer-beta - willing to try anything to have this issue fixed
Am I the only one experiencing (quite often - like .. at least 10-20 times a day depending on usage), when typing a text message - somehow it's like the "touch overlay" that activates the keys on the onscreen keyboard is offset about 1 cm to the right and 0.5cm down??
Meaning that if I press on the screen where it says "B" it will highlight and press "G" instead .. and "G" will fetch me an "E" .. and so on (and yes this means I'm not able to press either space or "P" because that would require my finger to be pressing a point 1cm outside of the iPhone screen
Somehow though when I try pressing "backspace" (delete - which is also as far right as possible) .. it works just fine?? .. but trying other keys again afterwards, its still broken.
I've tried doing all kinds of random stuff to realign the keyboard - even going to homescreen and back into text, won't fix it. However waiting a minute or so without doing anything fixes the issue??
Running on the latest firmware that isn't developer-beta - willing to try anything to have this issue fixed