View Single Post
Old November 19th, 2012, 02:56 PM   #187 (permalink)
Jerethi
Junior Member
 
Join Date: Nov 2010
Posts: 68
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 8 Times in 3 Posts
Default

Quote:
Originally Posted by RyanLupin View Post
What third party keyboards have you tried?

I believe it was a keyboard modeled after the new keyboard in 4.2.

In any event, regardless of what apps may trigger this issue (Chrome or otherwise) the underlying issue seems to be that there is a root file or directory that should be write-protected but which clearly is not, and the solution is to get Samsung to recognize it and do something! Unfortunately, that's easier said that done, apparently.
Jerethi is offline  
Reply With Quote
The Following User Says Thank You to Jerethi For This Useful Post:
blue02 (November 19th, 2012)