i get this once in a while also did you turn the phone off and let it restart ????
Yep.
I shut mine down every night.
RAM?
Where are you finding that stat?
Or are you talking about on board storage space instead of RAM?
The Commando comes with 512MB of dedicated RAM if I'm not mistaken.
It comes with 400MB of on board storage, 70MB+ of which has already been used by that damn bloatware.
If that's what you meant, I have 272MB free. Plenty-o-space.
Well...now I do.
I just went back into my Apps2SD app and found that there was
3.5MB of cache STILL being used by apps.
I knew something was funny because I know that I had 272MB free before.
Once I cleared that one, it somehow cleaned up 10MB of space (not just the 3.5MB it said) and put me back to where I needed to be.
The phone seems to be back to normal now.
That said, I don't understand how even 10MB of cached space
could cause the phone to F'UP as much as it was.
I'm sure most people would say, who care's it's back to normal now,
but I'd like to know just so I can prevent that type of thing from happening again.
It was really pissing me off.
-haha, I've had that sync thing happen too.
it makes ya feel like an ass when you figure out how simple the fix was, huh?
still...it shouldn't happen.
these devices are suppose to be "smart", right?
I've noticed my phone acting up this past week. Mainly when I unlock and my home screen appears, it takes 10 seconds sometimes before it responds to anything. I downloaded launcher pro but uninstalled it. I have juice defender and was thinking that was my problem but I've had it for a long time with no pevious problems. My main issue is my clock ,, I use the same one that came on the phone. when I go to my home screen this week, the clock will be stuck at 3 or 4 hours ago and does'nt straighten itself out. The clock on my lock screen will be right but not on my home screen. The only way to fix it is to restart the phone or drag it into the trash and create a new widget of it. sux
Yeah...I've had that clock freeze up on mine a few times too.
I always had to dump it in the trash and start a new one as well.
Never found the problem either.
It could very well be a conflict with Launcher Pro
because it never did that while just running the stock launcher.
We'll probably never know.
But even if it is a conflict with Launcher Pro,
I can't bitch too much about it being that it's free, ya know?
It's still plenty annoying nonetheless.