Originally Posted by DooMLoRD
its really strange...
the actual kernel (zImage) is the same as stock kernel.sin kernel
i triple checked the ramdisks and they are all consistent...
really dont know where the issue has come up...
This so called "RAM bug" thing is almost consistently reproduced doing the following (at least for me). Accidently noted while trying make cooltool to display the frequency of the second cpu core.
[ROM: Stock 4.3 (.201), On AdvStk kernel v2, On-demand governor, deadline I/O, CPU 1.728Ghz~384Mhz]
-In cooltool, adding the following to one of custom label slots..
-Enabling that to display in cooltool..
(but the output is some "error" I think.. no idea what cooltool is trying to do..)
-waiting few seconds.. can see ram going down steadily.. Opening Settings>Apps>Running.. ram v. low.. but, note the difference between cooltool and this android value! No idea why..?
-Phone becomes laggy.. and finally crashed resulting in a reboot (didn't happen always). Last_kmsg
-Another occasion.. quite consistently can reproduce this.
This same thing can be reproduced in Stock .201 kernel, but didn't reboot. It gets stuck, have to reset
. But the difference is, in AdvStk_v2 this ram bug thing comes unprovoked and randomly. This spontaneous occurrence doesn't happen in stock kernel. Only noted (for the first time) when doing like above..
** Could it be that something initiated by the ramdisk is randomly meddling with similar cpu setting, triggering the ram issue..?? (Because, the kernel image is same in both cases). You know well what's under the hood
Can anyone else try like this whether same thing happens.. or only me?