Originally Posted by BrianXP7
...I might revert the kernel to overclock by default because it seems to be more buggy. I played around with the Dalvik Just In Time recompiler and there seems to be less issues at initial boot.,,
The "deadline" scheduler is also important to avoid overheatings because it lets calculate properly the percentage of CPU needed for the bandwidth requirement of each process and it reduces latency of any given single input/output so it increases read/write performance. From my point of view, it is completely necessary for our kovsky, even more when we use upper dalvik heaps. If you can't set it on boot by default, the last version of SetCPU controls it pretty good working with deadline scheduler.
---------- Post added at 10:35 AM ---------- Previous post was at 10:17 AM ----------
Originally Posted by ady_95
... I know I shouldn't ask this here, but have any of you experienced that HW problem that when you slightly hit the phone, it shuts down just like you take out the battery? (ANSWER THIS JUST ON PM)
I only experiment HW key problems after using the phone for usb tethering if I set the screen on "stay awake" while charging and I unplug the phone and I press power off button to lock the screen. Therefore, I think it is caused by the suspend problem explained post before by CoolrunnerII.