Originally Posted by freakinvibe
That happened for me as well on the OS version that the device came with (184.108.40.206). After I have upgraded to 220.127.116.11 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.