[Galaxy S I9000 Android Development] flolep:
Ok.

I promised a full report.

Here it is.

For my tests, I was not in a good situation to have the best conclusion possible but please note that I have enough arguments to say I arrived to a real conclusion nonetheless.

I was on supersonic jvr (very hard to install but good first rom).

New sqlite by acid, Ext4 no journal and barrier = 0 (I know, it's risky but in that case, smoothness is really great... But it doesn't help for my conclusion of this report, you will understand after why I say that)

1200 mHz, 1292 mv, ondemand governor, but min and max to 1200 (again, it maximizes performance but it's very stable at 1292 mv, but doesn't help for my conclusion)

vr scheduler (the best for me)

Talon 0.5.1.1 1200 mhz bigmem neutral colors (I really don't like voodoo colors and never succeeded to have variables that put my screen to the level attained by neutral colors). I think bigmem is the feature that really didn't help me to conclude something...

I had configuration proposed by pikachu: hidden apps 52, ZRAM 160 and swappiness 50.

Plus his two retouched zach's scripts in init.d, maximizing vm settings to trigger even more the memory leaks because of the possibility to clear it (see the next sentence)

And finally last but not least, the command he proposed to "drop caches" (sync then echo 3 > /proc/sys/vm/drop_caches), running every 2 hours thanks to the scheduler of script manager.

I must say that with this configuration, we are near paradise utilisation... Very smooth in every situation, call, games, video, surf, flash, applications, multi tasking, 3d. Near every application is instantaneously launched and multi tasking is for more than 5 applications in the same time without one being killed by aggressive min free settings (that is the only feature that I don't wanted to push because I know your opinion about that and my report wouldn't have had so much impact if I had too aggressive min free settings), very good battery too because no aggressive min free settings again. And even with only 40 mb free only, sometimes, it was still smooth, and I really must say, here, that I was really surprised about it... But I think that the sqlite, no journal and barrier = 0 features helped here a bit to have smooth things even with not too much free memory (but that is my only opinion, I think you will have another on that one :p)

But I have some things to say after some days of tests and one full day with the full configuration exposed in this post.

First, I think that 160 mb for zram was a little too much in my case, with my installed applications, because doing free command, I see that only 80 mb is used in swap memory... And when I see the advice of existz, I think I understand that even with this heavenly configuration, there were sometimes some lags and couldn't understand why (big free memory, overclock, no journal... Etc... It was making no sense to have some lags, even if they were minor). Maybe I will try 100 mb next time... Could improve performances without removing any useful memory.

Second, a bug (or maybe functionality for you, I don't know...) was annoying: after a call, my phone goes alone into lock mode... Every time I had a call, I had to push unlock button to use my phone again lol (something that is not happening with other kernels on xda, I tested it). So maybe it's a known bug and there is a well known solution but I couldn't find it, but I will be happy to know how resolve this bug :p

Then I wanted to talk about the point that really made me want to do a report. The famous talon memory leak :p

I think that, even with this good configuration and the big free memory, we can still see it between the morning of a day and the evening of this same day (without rebooting), even with the commands of pikachu / existz...

To test it, I launched my phone with the heavenly configuration in the morning, wait for it to be smooth as it must be, system applications launched and cached, scripts running, free memory coming a little after boot.

Then, when all is launched and no more task is "moving", I kill all the tasks in memory with taskiller, giving me a whopping 147 mb free memory (no need to say that the phone is smooth here :p), and take a screenshot (1st picture). Even launching some applications, playing with contacts, market, etc, after this and a little kill of applications, I have around 140 mb free in memory and nothing seems to diminish this total thanks to the bigmem feature, the zram and the hidden apps 52.

But after one day of use, and every two hours launching the drop cache command, sometimes the phone gets a bit laggy, some applications don't launch as quickly, launching angry birds seasons for example, begins to be a very long task :-)

So in that cases, I launch again the sync and drop cache command, but even if I go from 80 mb to 90 or 100 thanks to the drop (and using taskiller to be sure everytime that there is no big application in memory, and to note, the use of taskiller is only for the tests, my goal is to never use it, I hope you understand), impossible to go back to the 140 mb of the beginning...

At the end of the day, impossible to have more than 100 mb free memory (second picture).

That is 40 mb memory lost, we don't know where, in the limbs :p

So I let you imagine after some hours / days more, without bigmem to have 720p recording back, less ZRAM to improve performance, less than 52 for hidden app, to gain more battery... The leak leads me to where I was with talon kernel some weeks ago, without knowing all these configurations and tweaks, just flashing talon kernel and that's all, having 30 or 40 mb only free all the time and a phone unusable after some hours of use... Lol. Noob I was, for sure :-)

But the purpose was only to prove that the memory leaks are still there, and my little finger tells me that existz knows that and was letting us test and see by ourselves. Because if he didn't know that, he wouldn't be working on another "little thing that will help with memory" and memory leak wouldn't be on the todo list of talon crew when they will have sgs and finally he would have validated that the commands of pikachu indeed were solving the memory leaks.

Long life to talon crew, developers in here (I am one in my life too, web dev and Microsoft, sorry for that :p and I am more than interested in Linux and android dev too), to users like pikachu or others that always try to push the limits and to xda forum :p

Sent from my GT-I9000

P. S will now try supersonic jvs and talon 0.5.1.2 (thank you very much existz and crew) but with neutral colors (thanks tatsuya), no bigmem this time, and zram 100 :-) but don't know if I will report lol... Too long... For me, and maybe for you :p sorry about that :p