Strange. I had this problem once or twice while using 2.0, but it hasn't happened since 2.0.1. Doing a factory reset fixed it. I didn't reset specifically for that issue (I had an issue with another app) but it took care of it.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.