latest Droid X issues...2.2 related?
There are many 2.2 issue threads for the Droid X out there I am sure. It might be more appropriate to put this in a "master" thread, but I haven't seen anyone discussing the same issues I am having yet. So if the thread needs to be moved, that's fine. Or maybe more appropriately the title of the thread could be changed...but overall I feel at this point these are my latest issues and seem like they are 2.2 related as they happened right after I updated.
First off, I am using a Droid X non-rooted, 2.2 update that came on official update day.
Three times this has happened so far. Twice with the battery drain I am about to explain, only once (right now as I am typing this) with just the clock issue.
All times had the clock issue.
I took my phone to work and although it already experiences battery drain due to the constant searching of a better signal (I have it set to turn data off after 15 minutes of non-use to combat that so that is under control and I would not attribute that to being the problem), it was at 100% at 7:45 and by 10:40 the battery was at 15% and the clock froze. I didn't use it at all and this had happened. Then I tried to make a call, use the phone, it completely locked up and after maybe 10 minutes I was able to get it to respond enough that I could try to turn it off and back on. I turned it back on and data seemed to be completely turned off, couldn't get it back on and the clock was stuck again, now at the time I turned it back on. The clock was originally stuck at 10:20 the first time. Now at 11:07 it was stuck after, like I said, trying to get it to respond after locking up. So then I just turned it off again, turned it back on at maybe 3:45pm and it started to work again no problem. The battery was still low, but thats because I didn't charge it, didn't have a charger at work.
It didn't happen again until maybe 5 days later. Same situation.
Then right now, no battery drain, but the clock is stuck at 12:00pm. It's 1:29 now. I was able to do stuff and pull stuff up and everything seems to be running ok, but then when the screen timed out, I can't get anything up, it timed out and I can't pull the screen back up, not by pressing lock button, nothing. Then about 5 minutes after I tried pressing some buttons, it pulled up, but clock still stuck at 12:00pm. It timed out again as I am typing this, and again...unable to pull anything up. I was able to get it turned off and am turning it back on right now. I'm assuming that will clear the issue up, but obviously temporarily. I'm guessing this might be a 2.2 related issue since it never happened until the update, and the first time was 3 days after the update. I got the update on the first Friday it was out, and then all weekend had it plugged in so I didn't notice the battery drain issue if it happened since it was plugged in. So the first time I had it away from home was that next Monday, as I described at work.
Ok, it turned back on and the clock is working right, so again, a temp fix it looks like. Anyone else experiencing this? Any ideas? Hopefully it isn't the sign of a bigger problem.
Thanks in advance.