The right thing to do here is set the LMK thresholds so that cached apps (adj=9-12) get killed more aggressively.
On Saturday, June 23, 2012 at 9:03:19 PM UTC-7, HV wrote: > > understand that it's not normal, but this platform is running on low > memory & I'd like to free up the entire memory once the app closes. I see > that with "no background processes" there is huge improvement in free > memory. So, I'd like to make this the default configuration > > Thanks > HV > > On Saturday, June 23, 2012 12:09:32 AM UTC-7, Dianne Hackborn wrote: >> >> That setting is intended for development purposes only. Android is not >> designed to run like this for production. >> >> Why do you think you need to do this? >> >> On Thu, Jun 21, 2012 at 5:58 PM, HV <[email protected] <javascript:>> >> wrote: >> >>> Hi, >>> >>> I'm looking at changing this to "no background processes" and wondering >>> where I should tweak this in the code. I know that this can be done through >>> Settings->Developer Options->Background process limit, but I want my >>> release default to be zero. Could anyone please point me to the right file? >>> >>> Thanks >>> HV >>> >>> -- >>> unsubscribe: [email protected] <javascript:> >>> website: http://groups.google.com/group/android-porting >>> >> >> >> >> -- >> Dianne Hackborn >> Android framework engineer >> [email protected] <javascript:> >> >> 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 --- You received this message because you are subscribed to the Google Groups "android-porting" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
