Sorry ... you are incorrect. While turning off the smart stabilization "fixed" the issue, it was not the root cause. I turned the smart stabilization back on, and the issue returned, but, upon clearing the RAM cache, the issue was gone. This is a classic problem in technology circles, wherein an issue can seemingly be resolved via one solution, when, in fact, the root cause was not addressed. Actually, if you contemplated more deeply, then you would have to ask, which is more likely: (1) Samsung delivered a device with a defect that makes it problematic to use a key feature, or (2) it is an operational issue that could have benefited from better documentation. In this case it was definitely the latter.