[Galaxy Y GT-S5360 Themes and Apps] kurotsugi:
first of all, I didn't intended to discourage OP or anyone to share his finding on this forum. I also didn't said that OP is lie or trying to deceive you. let's think positive. he might misinformed about this stuff from internet. please don't hate me for doing this :P

the point is...as stated by my old friend hitme, this stuff won't work

this mod is actually working, but...not as described by OP. this mod is actually intended to change the adj value of home app in lowmemorykiller system in android system (...the explanation is a lil bit long-let skip it). what OP said about kill the app bla bla bla isn't quite true. this mod simply only make the launcher never killed. thus make our device seems faster.

# Define the oom_adj values for the classes of processes that can be
# killed by the kernel. These are used in ActivityManagerService.
setprop ro.FOREGROUND_APP_ADJ 0
setprop ro.VISIBLE_APP_ADJ 1
setprop ro.PERCEPTIBLE_APP_ADJ 2
setprop ro.HEAVY_WEIGHT_APP_ADJ 3
setprop ro.SECONDARY_SERVER_ADJ 4
setprop ro.BACKUP_APP_ADJ 5
setprop ro.HOME_APP_ADJ 6 --> default value
setprop ro.HIDDEN_APP_MIN_ADJ 7
setprop ro.EMPTY_APP_ADJ 15

# Define the memory thresholds at which the above process classes will
# be killed. These numbers are in pages (4k).
setprop ro.FOREGROUND_APP_MEM 2048
setprop ro.VISIBLE_APP_MEM 3072
setprop ro.PERCEPTIBLE_APP_MEM 4096
setprop ro.HEAVY_WEIGHT_APP_MEM 4096
setprop ro.SECONDARY_SERVER_MEM 6144
setprop ro.BACKUP_APP_MEM 6144
setprop ro.HOME_APP_MEM 6144
setprop ro.HIDDEN_APP_MEM 7168
setprop ro.EMPTY_APP_MEM 8192

that one is a part of our init.rc file in our kernel ramdisk. as you can see, these value are stored in our kernel. if you're a kernel dev you can play with these value. to increase multitasking stuff yo can play with the value of memory threshold and the adj value. for a comparison, you can check the one used by me

setprop ro.FOREGROUND_APP_ADJ 0
setprop ro.VISIBLE_APP_ADJ 4
setprop ro.PERCEPTIBLE_APP_ADJ 2
setprop ro.HEAVY_WEIGHT_APP_ADJ 5
setprop ro.SECONDARY_SERVER_ADJ 6
setprop ro.BACKUP_APP_ADJ 7
setprop ro.HOME_APP_ADJ 1
setprop ro.HIDDEN_APP_MIN_ADJ 8
setprop ro.EMPTY_APP_ADJ 15
setprop ro.FOREGROUND_APP_MEM 1536
setprop ro.VISIBLE_APP_MEM 3072
setprop ro.PERCEPTIBLE_APP_MEM 1024
setprop ro.HEAVY_WEIGHT_APP_MEM 10240
setprop ro.SECONDARY_SERVER_MEM 10240
setprop ro.BACKUP_APP_MEM 12800
setprop ro.HOME_APP_MEM 1024
setprop ro.HIDDEN_APP_MEM 12800
setprop ro.EMPTY_APP_MEM 19200

if you want to play deeper, you can also check into this part

# Write value must be consistent with the above properties.
# Note that the driver only supports 6 slots, so we have combined some of
# the classes into the same memory level; the associated processes of higher
# classes will still be killed first.
write /sys/module/lowmemorykiller/parameters/adj 0,1,2,4,7,15 --> change this value

write /proc/sys/vm/overcommit_memory 1
write /proc/sys/vm/min_free_order_shift 4
#write /sys/module/lowmemorykiller/parameters/minfree 1536,2048,4096,5120,5632,6144
#write /sys/module/lowmemorykiller/parameters/minfree 1536,2048,4096,5120,6144,8960
write /sys/module/lowmemorykiller/parameters/minfree 1536,2048,6144,8192,12288,15360 --> change this value

# Set init its forked children's oom_adj.
write /proc/1/oom_adj -16

# Tweak background writeout
write /proc/sys/vm/dirty_expire_centisecs 200
write /proc/sys/vm/dirty_background_ratio 5

if you're not a kernel dev, you can made a simple tweak to play with this stuff too. just note that the first part (the one using setprop command) is only could be changed via build.prop modification or via terminal/script command with root permission. the second part can simply modified by any init.d script. it's a lil bit long but you can check into this part

# kernel kick
echo "4096" > /proc/sys/kernel/shmmni;
echo "4096" > /proc/sys/kernel/msgmni;
echo "64000" > /proc/sys/kernel/msgmax;
echo "20000000" > /proc/sys/kernel/sched_latency_ns;
echo "2500000" > /proc/sys/kernel/sched_wakeup_granularity_ns;
echo "1000000" > /proc/sys/kernel/sched_min_granularity_ns;
echo "500 512000 64 2048" > /proc/sys/kernel/sem;
echo "268435456" > /proc/sys/kernel/shmmax;
echo "2097152" > /proc/sys/kernel/shmall;
echo "30" > /proc/sys/kernel/panic;
echo "0" > /proc/sys/kernel/panic_on_oops;
echo "5000" > /proc/sys/kernel/threads-max;
echo "10" > /proc/sys/fs/lease-break-time;
echo "65536" > /proc/sys/fs/file-max;
echo "60" > /proc/sys/kernel/panic;
echo "0" > /proc/sys/kernel/panic_on_oops;
echo "1" > /proc/sys/kernel/sched_compat_yield;
echo "256000" > /proc/sys/kernel/sched_shares_ratelimit;
echo "0" > /proc/sys/kernel/ctrl-alt-del;
echo "kernel kick-----------[OK]" | tee -a $LOG_FILE;

# OOM
echo "0" > /proc/sys/vm/laptop_mode;
echo "40" > /proc/sys/vm/swappiness;
echo "3000" > /proc/sys/vm/dirty_writeback_centisecs;
echo "500" > /proc/sys/vm/dirty_expire_centisecs;
echo "15" > /proc/sys/vm/dirty_ratio;
echo "100 100" > /proc/sys/vm/lowmem_reserve_ratio;
echo "1" > /proc/sys/vm/highmem_is_dirtyable;
echo "4" > /proc/sys/vm/min_free_order_shift;
echo "0" > /proc/sys/vm/oom_kill_allocating_task;
echo "0" > /proc/sys/vm/panic_on_oom;
echo "70" > /proc/sys/vm/overcommit_ratio;
echo "3" > /proc/sys/vm/page-cluster;
echo "3" > /proc/sys/vm/drop_caches;
echo "15360" > /proc/sys/vm/min_free_kbytes;
echo "50" > /proc/sys/vm/vfs_cache_pressure;
echo "70" > /proc/sys/vm/dirty_background_ratio;
echo "0" > /proc/sys/vm/block_dump;

#minfree
echo "0" > /sys/module/lowmemorykiller/parameters/debug_level;
echo "64" > /sys/module/lowmemorykiller/parameters/cost;
echo "0,1,3,5,7,15" > /sys/module/lowmemorykiller/parameters/adj;
echo "1536,2048,4096,20480,20480,15360" > /sys/module/lowmemorykiller/parameters/minfree;

you can play with the value of echo command. don't worry about the values. playing with these stuff is usually save. have a nice tweaking, lads :P

PS:

1. instead of modifying build.prop directly, you can use script. this is just an example.

#!/system/bin/sh
setprop persist.sys.purgeable_assets 1
setprop dalvik.vm.execution-mode int:jit
setprop dalvik.vm.dexopt-flags m=y
setprop dalvik.vm.heapsize 64m
setprop ro.kernel.android.checkjni 0
setprop ro.telephony.call_ring.delay=0

you can add this one on init.d script.

2. type 'getprop' in your terminal to see your system prop value.