[Android Software/Hacking General [Developers Only]] pikachu01:
That's what I've been saying. Whatever edits you made to ProcessList won't get realized as the only thing passed to the apps are thresholds and lowMemory. The ADJs are not exposed to the app. You have to remember that.

Yes. True. It seems you've understood that. Now, making the change to ProcessList doesn't seem to matter. Why do you keep bringing up changing ProcessList and not modifying the two important aspects of ADJ calculation which is the memoryTrimming and LRU oomAdjToImportance?

I'm not saying it as an accident or anything. I'm just saying that HIDDEN_MIN_APP_ADJ can be changed later as it doesn't have a final keyword.

And you're just repeating what I've said. Why you did that. I have no clue. I already realized that HIDDEN_APP_MIN_ADJ is not constant and doesn't have a final keyword. Reiterating it and putting it like you're the first one to say that is just plain confusing.

I actually said ProcessList edits (except for HIDDEN_APP_MIN_ADJ) doesn't get passed to ActivityManagerServices. Please quote a post of mine that says otherwise.

That I don't know as I didn't check Supercharger's method to edit. I'm only pointing out that your "fix" of changing all the points where HOME_APP_ADJ to 1 will cause problems towards memoryTrimming and LRU and you admitted it yourself. :S

No one will whether what you said is true or not. For one thing, whatever you're doing in the services.jar, it breaks the Android LMK and you've admitted it yourself by trying to solve it.

I'm not talking about the launcher. I'm talking about other apps.

If I made no sense, would you have listened to me and attempt to fix the issue I pointed out? Get a grip man. You're losing it.

Here's my quote:

What I mean here is, LRU/memoryTrimmings won't work even if you've enable "Keep Home App in Memory". I don't know which part you don't understand about this.

You talking about yourself?

I have already proven that you'll get a half-baked LMK. It's basically the same as only tweaking the Linux LMK. Remember that guy Juwe11 who created an app to apply LMK to Linux LMK? Lots of people also said that it works. And yes, it will work to a certain extent. The only problem is that Linux LMK isn't smart enough to determine which app should be killed first for the same OOM_ADJ. Apps also lose the ability to determine lowMemory situations.

So the issue of memoryTrimmings/LRU isn't that many? It's basically something that ruins a big part of the functionality of the Android LMK.

Wow, just wow. It doesn't matter if it's a home app or server app. Looks like you lost the plot.

if (app.nonStoppingAdj >= ProcessList.HOME_APP_ADJ
&& app.nonStoppingAdj != ProcessList.SERVICE_B_ADJ
&& !app.killedBackground) {
numTrimming++;
}

This code should be evaluating SERVICE_B/HIDDEN_APP and above. By putting it to 1 you're basically evaluating every app there is except system/foreground apps.

It's not hypothesis. The code is there for you to see. You just have to be less egoistical and see it for what it is.

Let me paste your quotes in another thread so that people see how many backtracks you've done

LOL. I know how having a half-baked LMK feels like. You can easily reproduce it by changing only the Linux LMK to a higher value than the Android LMK. Basically the same thing.

Oops, I mean SERVICE_B_ADJ.

And, I can see VISIBLE group contains things like SwiftKey, SMS Push. I prefer killing Swiftkey first before my Music player stops. As Swiftkey can be reloaded later, but I certainly don't like my music abruptly stopped. :/ There are certain cases where browser becomes VISIBLE group. Stuff like POP-UP Play comes to mind.

Hmm ..

I'm not even talking about the launcher exclusively. I'm talking about other apps also having the same LRU as the launcher. That basically lumps all the other apps together with the launcher.

It seems you and I have a different definition of what "Supercharged" is. My definition of "Supercharged" as in the launcher can't be killed before whatever in the foreground is killed and that the Android LMK isn't crippled i.e. LRU calculation and memoryTrimming occur for the right apps.