[Galaxy Ace II Android Development] xo.en:
Thanks for answers, guys!

...situation cleared up after recharge: -96ma idle(when screen's on, almost min brightness), deep sleep works, zero issues so far.

Interesting - i had no blackscreen for a day(50hz), nor "sound-loss"(no viper here, though, now).

2d is totally great(canabalt, browsers, scrolling, etc),

3d performance is OK, i have no idea why antutu showed BS yesterday(tbh antutu is ok, if we are NOT looking at overall score, only parts of it, independently, it can help with tweaking to some extend(i/o, gpu libs, 2d)),

3d games are working ok(my main test game is Beach Buggy Blitz - VERY useful for testing overall rom/kernel/tweaks fiddling, with this kernel game has best fluidity i ever seen on A2 - DEFINITELY great i/o subsys has its effect here).

GPS works GREAT.

Oh, new version :)

-91ma with min backlight now..drop from 100% to 96% now, quite fast.

Btw, i forgot - only, but weird issue: flashlight widget...stopped working(clicking does not turning on a LED), but apk itself works fine.

May it be related to bln_off that i am using(on vodka's kernel there was no such problem)?

Hhheh, i had same thing with vodka's kernel(default one from slimkat 9.0). Battery indicator was SO lazy that i had c.a. 16% loss after over 1.5 days. Hard to say what would i see later, i was impressed. I think, that Chronokernel just shows exact state(it's just honest), so it may be seen as drain, lets say.

btw - do NOT use swapiness more than 30, bigger values can bog machine down!

small advice:

#!/system/bin/sh
#chmod -R 755 /system/etc/init.d
chown root:root /proc/sys/vm;

echo "30" > /proc/sys/vm/swappiness;
busybox chmod ugo+rw /proc/sys/vm/vfs_cache_pressure;
echo "50" > /proc/sys/vm/vfs_cache_pressure;
echo "2000" > /proc/sys/vm/dirty_expire_centisecs;
echo "1500" > /proc/sys/vm/dirty_writeback_centisecs;
busybox chmod ugo+rw /proc/sys/vm/dirty_ratio;
echo "90" > /proc/sys/vm/dirty_ratio;
busybox chmod ugo+rw /proc/sys/vm/dirty_background_ratio;
echo "75" > /proc/sys/vm/dirty_background_ratio;
echo "512" > /sys/devices/virtual/bdi/default/read_ahead_kb;
echo "10" > /proc/sys/fs/lease-break-time;
echo "4" > /proc/sys/vm/page-cluster;
echo "5360" > /proc/sys/vm/min_free_kbytes;
echo "8" > /proc/sys/vm/min_free_order_shift;
echo "0" > /proc/sys/vm/oom_kill_allocating_task;
echo "1" > /proc/sys/vm/overcommit_memory
busybox sysctl -w kernel.random.write_wakeup_threshold=256;
busybox sysctl -w kernel.random.read_wakeup_threshold=1376;

and

#!/system/bin/sh
chmod 0644 /sys/module/lowmemorykiller/parameters/adj
echo "0,3,6,10,12,15" > /sys/module/lowmemorykiller/parameters/adj;

chmod 0644 /sys/module/lowmemorykiller/parameters/minfree
echo "1024,2048,2560,4096,6144,8192" > /sys/module/lowmemorykiller/parameters/minfree;

chmod 0644 /sys/module/lowmemorykiller/parameters/debug_level
echo "0" > /sys/module/lowmemorykiller/parameters/debug_level;

works miracles in my case, especially second one, imho it would be hard to use different values, i was trying different setups for YEARS(with this machine), so it is not just random throw. Bigger LMK REALLY makes things worse here. It usually has tremendous influence over fluidity of gui, and whole sys(well, at least it had such on other kernels and older roms:) )..