Just ignore ActivityManager.getMemoryInfo(). It is trying to infer the status of memory on the device, but as the java doc says due to the nature of modern kernels things like the available memory is somewhat meaningless. The low memory flag is just set if the activity manager is inferring that memory is getting low because it is seeing certain processes go away, but this is no a guarantee.
On Thu, Jul 28, 2011 at 2:49 AM, sandeep kumar <[email protected]>wrote: > In android "lowmemorykiller.c" file has been added for more advantageous > memory management. > ActivityManager.MemoryInfo uses ActivityManager.getMemoryInfo. > The call into the system service ends up in > ActivityManagerService.getMemoryInfo, > where it checks if available memory is less than some threshold. > And thus determines whether it is in low memory condition or not. > > Can I get some help in understanding the point as in where the flag (which > is set on lowmemory) > is monitored and how a callback is linked to the lowmem_shrink function in > lower layers (i.e., kernel/drivers) > > > -- > With regards, > Sandeep Kumar Anantapalli, > > -- > unsubscribe: [email protected] > website: http://groups.google.com/group/android-porting > -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
