Cursor Jump

[bjs229]

Not sure if i mentioned this before. Sorry if it is a repeat.. I am having problems with my keyboard.  When editing text it is nearly impossible to set the two markers. I also have an extremely annoying issue that occurs when trying to edit. After editing a sentence and resetting the cursor to the end of the phrase, typing a letter brings me back to where I was before and starts erasing the text. The only thing that fixes it is if I turn the nexus off and on I can then resume . Better yet . Sometimes my kb will freeze and then start deleting text on its own. Like the back key is stuck. Anyone else encountering this? Maybe time for a reset, BTW , this was happening before I rooted the tablet.
This is a pre drop issue. Lol

Sent from my Nexus 7 using Tapatalk 4

[matt]

I'm having some phantom key presses. The last update was supposed to fix this, but it seems worse.
Like a ghost in the machine. Wooooo.

[bjs229]

Good way of putting it Matt. Phantom.. I need to brush up on my tech lingo.
Btw, It happens with both the stock and Swiftkey apps

Sent from my Nexus 7 using Tapatalk 4

[birdastrompgman]

What apps does this happen in?

Sent from my rooted Nexus 7 running Paranoid Android 3.96.

[matt]

Just fc'ed twice on chrome trying to post this, could have been a phantom back press. Was closing the keyboard randomly and other odd stuff. Turned off, cleaned screen, rebooted, crossed fingers, typing (uncrossed). Better, if it recurs I'll find an Ouija board app before attempting full exorcism. Bjs- careful cleaning around the crack, some cleaners may contain water, which could short the grid. A screen protector may be a good idea.

[bjs229]

Thanks for the heads up Matt. I will be careful when cleaning. I really can't stand screen protectors especially the thought of one after the fact of cracking the screen.

Sent from my Nexus 7 using Tapatalk 4

[bjs229]

What apps does this happen in?

Sent from my rooted Nexus 7 running Paranoid Android 3.96.

I have it occur when entering text in most apps. Gmail, Tapatalk, Chrome browser..

Sent from my Nexus 7 using Tapatalk 4

[matt]

More keyboard ghost here.

http://www.androidpolice.com/2013/08/30/bug-watch-2013-nexus-7s-touchscreen-issues-persist-even-worsened-on-some-units-after-jss15q-fixed-them/

My problems are gone. No, posted too soon. Causing pop up ads to appear. Click on double underlined words.

[bjs229]

I still have problems but haven't updated. I am going to have to go back to stock and go from there.

Sent from my Nexus 7 using Tapatalk 4

[matt]

http://forum.xda-developers.com/showthread.php?t=2428133

Going back to stock may not help. The last update also changed the firmware on the digitizer chip which won't change back with a stock rom . above is a link to a developer's fix. Several different digitizer firmwares to try. I'm going to wait for it to be tested a bit first. Or Google could attempt to fix it again with another ota update.

[bjs229]

Well I updated by turning off the keep alive in Supersu. I am at JSS15Q now. I lost root. We will see if any of the bugs went away. I notice there are numbers on the qwerty keyboard now.

Sent from my Nexus 7 using Tapatalk 4

[bjs229]

Still having cursor jump. Grrrrrrrr

Sent from my Nexus 7 using Tapatalk 4

[JayJ]

Weird, I haven't had this issue for the last couple of iterations of Android...

Haven't used my 2nd gen N7 all that much but was on G+ today and it never happened, will see the more I use it...

Sent using The Force

[bjs229]

Rerooted and flashed TWRP with WUGS. Pretty painless. The kit couldn't automatically download the modified boot image so I had to manually d/l and then add it to the toolkit.

Sent from my Nexus 7 using Tapatalk 4

[Crystal03JC]

Mine has phantom key presses too, I have reset it twice.  Right now it seems to be working fine, but last time I reset it..after a while it would start doing it again. Mainly it keeps putting uuuuuuuu and I can't touch the back button because it will bring up the tabs screen.  Frustrating at times..I usually just turn the screen off and back on for a temporary fix.

Hoping the 5.0 update fixes it