I don't think that's nasty. You're the foreground app, serving the user's immediate interests.
But I don't think it would work unless the background app in question is misbehaving. Ordinary background apps should only be running in response to events or timers -- and they'd have to do MORE work when those ran, if they're not already loaded in memory. I see other potential ways for it to backfire on you, too. But I see no harm in experimenting. I'm always annoyed when background apps interfere with what I'm doing in Windows. Back in the 1980's, I made the Symbolics scheduler give foreground thread a *serious* scheduler boost, especially if mouse response was involved. It was one of a number of changes that gave a major improvement to the responsiveness of the system. So my experience says users will generally be happy about almost any measures you undertake that focus the machine's resources on what they're doing Right Now. On Mar 14, 2:26 am, Yahel <kaye...@gmail.com> wrote:> > I've been thinking for a while about doing something that feels nasty > but could be an answer : > Allocate as much memory(12M ? 24M ?) as you can during the loading of > the game. This would force Android to look for memory somewhere else > and therefore kill as many non useful process as possible. > That sounds evil doesn't it ? But I'm not sure if it would work > anyway, I didn't try yet :) -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
