Keyboard not responding on Samsung Tab S2

Saturnv

Member
Aug 4, 2018
17
0
0
I'm having problems when using Chrome browser on my Tab S2. When you first open it and say type something in Google search box all is well. Close that, switch to say eBay and try to type in the search box and although you can type on the keyboard, nothing appears in the box. Ditto any other Web form. Open a new tab and you can repeat the exercise, ie it works on the first site but not the next one. Tried flushing chrome cache, data, using a different keyboard, (using SwiftKey primarily), flushing keyboard, reinstalled the keyboard but no joy. Chrome has updated at least once since this error started so is up to date.
 
Fixed! I eventually managed to solve this by disabling chrome, powering down, and then re-enabling chrome. Synced back to my phone to restore bookmarks and all sorted.
 
Errr. No it's not. Worked OK until I updated chrome to the latest version and then back to square one. Any ideas anyone?
 
No ideas, but I've been having the same issue with my Galaxy Tab s2 and the Chrome browser. Usually shutting down the tab and opening a new one helps.
 
Ah. Beginning to think I was alone with this problem. Yes, opening a new tab corrects it but only for one go. Gets very annoying! Started using Firefox as that works OK.
 
You are not alone. I am having the same problem with my Tab S2 . To type on a site's search or to a Forum reply I have to type it out on an app and then cut and paste it to the box on the site. It will just allow me to paste rather than type. It happened a couple of months ago and stopped. Now it is doing it again. I was thinking that it was a SwiftKey problem but it does the same with the Samsung keyboard.
To do this response I had to do the cut and paste trick.
 
Yep it sure is. Just brought a new S4 and got the same issue with this too! Going slightly mad and crazy now.
 
Tried factory reset on the S4 and loaded only my synched bookmarks, nothing else, no apps etc. Still the same problem. So has to be a Chrome issue.
 
Solved. Downloaded Chrome Beta and using that it appears that the problem no longer exists, so clear that it is a chrome issue. Be interesting to see what happens when we get the beta version as a full release.
 

Forum statistics

Threads
955,571
Messages
6,965,284
Members
3,163,337
Latest member
AnonymousMRFR