View Single Post
Old 12-03-2011, 03:58 PM   #5
mpeg2
Connoisseur
mpeg2 ought to be getting tired of karma fortunes by now.mpeg2 ought to be getting tired of karma fortunes by now.mpeg2 ought to be getting tired of karma fortunes by now.mpeg2 ought to be getting tired of karma fortunes by now.mpeg2 ought to be getting tired of karma fortunes by now.mpeg2 ought to be getting tired of karma fortunes by now.mpeg2 ought to be getting tired of karma fortunes by now.mpeg2 ought to be getting tired of karma fortunes by now.mpeg2 ought to be getting tired of karma fortunes by now.mpeg2 ought to be getting tired of karma fortunes by now.mpeg2 ought to be getting tired of karma fortunes by now.
 
Posts: 66
Karma: 2687880
Join Date: Aug 2010
Device: Kindle
This whole discussion seems to be quite confused to me.

There are two types of memory in these devices (just like in computers): Volatile memory (RAM) and Persistent memory (Storage - Flash or Hard Disk). Everyone here seems to be discussing persistent memory (Flash on the Fire).

Remember, when you start an application, it is loaded from Flash to RAM for execution. The Fire manages RAM (or more accurately, Android does this). Androids memory management is quite good - often leaving apps loaded in RAM even when they're not running to aid in quicker startups. I think the Fire has a pretty generous allocation of RAM compared to many phones - 1GB compared to 256MB (on my Droid 1).

I think that the problems being reported & error messages relate to running out of RAM. Playing around with the Flash memory won't do much for this.

Of course, I could be wrong also...

Rich
mpeg2 is offline   Reply With Quote