[Samsung Galaxy SL i9003] loSconosciuto:
I decided to change the naming convention of my kernel releases to make my life easier. No more numbered releases, from now on it will be done as for my CM10 builds. The release date will be the name.

Kernel changes:

I found an error, or at least I think it is, that makes not good chip calibrations good. Maybe it was intentional, a way to disable a part of a pretty standard code (I found it in several Samsung devices) without modifying it too much. Anyway, I had the impression that things became better after the change, so I "fixed" it.

This change should decrease the chances of having an unresponsive touchscreen when the screen is turned on, but there are still miscalibration. That's why I added the possibility to disable them completely. The option is in DeviceParts, it replaces the option to disable the driver filter, whose effect is barely noticeable.

EDIT

Moisture causes issues mostly because it increases the touched area. Our touchscreen ignores all the touch input whenever the touched area is "too big" because it considers it an accidental touch made with your palm. The size of this area can be customized, but I think this feature is useful mostly on big screens. If you want to disable this feature, run from terminal emulator:

su
cd /sys/touchscreen/
echo 0 > set_grip
cat set_write

and magically you'll be able to use the touchscreen with your palms.

More info can be found in this old thread.

I also made a CM10 build with this kernel. With this new build ringtones will always loop (I set 2 seconds of pause), no need to edit ogg tags. If you don't want to flash the entire build add:

ro.telephony.call_ring.multiple=false
ro.telephony.call_ring.delay=2000

to your build.prop.

See the patches for more info, they are in the usual place, same for the flashable stuff. Find the link on your own:

kernel-cm-10-20130606-galaxysl-signed.zip

cm-10-20130606-UNOFFICIAL-galaxysl.zip

[MENTION=4588282]sgatechwork[/MENTION]

Active Power Managemenet: I've already posted this link where you can find the explanation of what APM is and what does. I can't say which is the best latency. With a low latency, the GPU tries to save power more frequently, but this causes a performance hit.

50ms seemed reasonable, not too big, not to small (in our original kernel sources the latency was 2ms).

BT calls: So most likely it wasn't that app.

Issues with launcher: Oh, wow, three screenshots, not so many informations at the same time. -.-

Remove the init script you posted a couple of times here (preventing the creation of logcats is bad, especially with alpha-stage ROMs. The problem of that script related to your problem is probably the custom mifree values) and remove/disable that app. This is my solution, if you don't like it, find another solution on your own. And as I've already said, there are no ways to lock apps in memory editing the build.prop file.

[MENTION=2606021]cukierkas[/MENTION]

BT headset: Nah, I don't want anything. Also, there are high changes I'm not able to fix it, so it would be just a waste of money. I don't want this responsibility.

X-GamerZ: I have no idea if you have to wipe etc. Anyway, flashing kernels shouldn't cause such problems. As ALoGeNo said, poorly written updater-script can cause issues.