PDA

View Full Version : Seven Ways to Free Up BlackBerry Memory: Got More to Add?


AZA43
04-22-2008, 07:37 AM
If you're like me and you download lots of third-party apps to your BlackBerry, you've probably experienced memory-lag issues or even device crashes. I'm constantly trying to find ways to optimize my BlackBerry memory.

This article offers up seven tips to help free your BlackBerry's internal memory. Some are intuitive, like deleting excess apps, others less so, like wiping your event log.

Check it out. (http://www.cio.com/article/338863)

Do you know of any other tips to free memory? Drop 'em in the thread below if so.

AZA 8-)

bigme
04-22-2008, 07:41 AM
If you're like me and you download lots of third-party apps to your BlackBerry, you've probably experienced memory-lag issues or even device crashes. I'm constantly trying to find ways to optimize my BlackBerry memory.

This article offers up seven tips to help free your BlackBerry's internal memory (If you're like me and you download lots of third-party apps to your BlackBerry, you've probably experienced memory-lag issues or even device crashes. I'm constantly trying to find ways to optimize my BlackBerry memory.). Some are intuitive, like deleting excess apps, others less so, like wiping your event log.

Check it out. (If you're like me and you download lots of third-party apps to your BlackBerry, you've probably experienced memory-lag issues or even device crashes. I'm constantly trying to find ways to optimize my BlackBerry memory.)

Do you know of any other tips to free memory? Drop 'em in the thread below if so.

AZA 8-)

You link appears not to be working.

Clear the event log on your BB to free up some memory.

fusky
04-22-2008, 07:42 AM
http://www.blackberryforums.com/general-blackberry-discussion/112029-optimize-your-bb-how-setup-max-free-memory.html

hdawg
04-22-2008, 07:43 AM
no link ... and JC's post is better (y)

AZA43
04-22-2008, 08:39 AM
You link appears not to be working.

Clear the event log on your BB to free up some memory.

Link is fixed. Sorry about that, folks.