Originally Posted by freakinvibe
That happened for me as well on the OS version that the device came with (188.8.131.52). After I have upgraded to 184.108.40.206 this problem has gone.
I thought this issue was corrected in beta OS updates but then came back in .246...? Mine is anyways, I am using 246 and still have the problem.