Outdated, do not use.

the stock kernel is 800, if you want to overclock higher install one of the v2 kernels from petes website then reinstall the autoclock.

 

Yeah, I know it was 600. I ran his overclock script and now in terminal it says it's at 800 on the stock kernel. My phone is way snappier now, 600 was just a bit too low I guess. If I need any higher I'll use one of his v2 kernels. Thanks!

 

The stock kernel is set at 600 by default, but reaches 800 max. And I agree, 800 makes a big difference and that's how I set it up originally.

 

Why is there a big lag in the reloading of the homescreen? Everytime i exit an app, it takes 5 secs to reload my home screen. I noiticed this everysince i used pete's V2 kernels. Now i have changed back to V1 kernels and there is no lag at all. Is there a way to adjust V2 kernels?

 

Where is this overclock script?

 

It's on his website: here

Here, I'll make it easy for you: AutoOverClock

Flash this through recovery, just like you would a rom. That's all, you're done.

 

It's because your phone is low on memory and kicking the launcher out of memory so resources can be used in other apps. Not sure of the difference between V1 and V2 kernels but you could try locking your launcher into memory. Sometimes it helps, but sometimes it can also hurt the performance of the device. Just depends since no two droids perform the same.

 

I've been running 5/2 since Sunday and here are some issues I've noticed:

After phone calls, 3g icon comes back right away, but no matter how long I wait, it won't establish a "google server" connection, i.e. turn green (I've waited as long as 4 hours). To get it back, I have to go to Airplane mode, then back for the phone to connect to google. Even though it says I have 3g, during those times I don't have google connectivity, I can't do 3g things, like surf the web ("web page not available").
As a comparison, 4/23 didn't seem to have this problem for me.

Also, I don't know if it's a GPA thing or an app thing, but compared to the 4/23 build, Cachemate and Advance Task Killer work very slowly.

Just my observations.
Keep up the good work, Pete. I really appreciate all you are doing!

 

How can i lock the launcher into memory? Is anyone else having the same issue when switching to v2 kernels?

 

WTF? Why the hell are you using ATK? Get rid of that immediately. You absolutely do not need it on gingerbread (or froyo for that matter). It's only wasting resources.

 

From Terminal:
su
echo ro.HOME_APP_ADJ=2 >> /data/local.prop

I use 2, but you can try 1 or even 0 to see what works best. The number I'm referring to is known as the Out of Memory (OOM) value. The lower the number, the lower chance the launcher will get kicked out of memory. 2 works best for my device. Launcher stays in memory almost all of the time, plus it doesn't screw with anything else. I tried 0 and 1 for a while but google maps kept getting killed. Test it out, see what works best for you. I'd start with 2. Once this file is created, and you feel you need to change it, just go into the file using root explorer and manually change the value, then reboot.

 

thanks for the help so far. is there better instructions. Im sorry, im just not familar with the info you just gave me.