Until recently, I, too, had this problem. When I took my smart in for its 2.0 upgrade, they also applied a patch for the problem. For me, the problem has been resolved (I say it that way, since another fellow smart owner in my area has not been as lucky, and may actually need a hardware fix)