Saneless
Well-known member
I'm going with it being a software problem. I am pretty sure I didn't have this issue until the latest update to 2.17.651.5. The good thing about that is that it's fixable...eventually.
It's doing it for me in other ROMs, but I never had this issue till I updated the firmware and radio (as well as the 2.17 update).
It may be software but I doubt they'll address it. I may have to trade in my phone..