What is 'nebulous' about it? By free memory, he most likely means the
amount of memory not yet allocated to any process, available (to user,
not system processes) on the heap.
Now true, the whole purpose of a garbage collector is that it can
change that value on the fly by freeing up memory as it
On Wed, Aug 11, 2010 at 6:44 PM, Indicator Veritatis mej1...@yahoo.com wrote:
What is 'nebulous' about it? By free memory, he most likely means the
amount of memory not yet allocated to any process, available (to user,
not system processes) on the heap.
Android caches processes that are not
The question isn't so simple, eh?
The total ram available to the device appears to be a fairly
objective hardware question. For the Motorola/Verizon Droid it's
256MB.
But the OP seems to be looking for some other answer. Perhaps restate
it a different way?
--
You received this message because
I can get the amount free from MemoryInfo - but I want to know the
percentage free - so, for example, if running on the Droid I want to
know that there is 256MB installed, so that if MemoryInfo reports
128MB free, it's 50%, while on an EVO with 512MB, 128MB free is 25%.
If you take a look at the
I meant in windows xp device manager
On Aug 11, 2010 9:51 PM, Jonathan j.trachtenb...@gmail.com wrote:
I can get the amount free from MemoryInfo - but I want to know the
percentage free - so, for example, if running on the Droid I want to
know that there is 256MB installed, so that if MemoryInfo
Hi,
No, you should be able to access /proc/meminfo even from userland just
fine. It would be the best way to do it. Yesterday I was browsing the
source for Android's Running Services app and this is what it does
(gets meminfo and adds free + cached together to get free mem,
total mem it does
6 matches
Mail list logo
