firedroidI hope I’m not blowing up his spot but XDA’s morphic and simms22 have produced a 1.5GHz Nexus S kernel, an otherwise very fast 1GHz phone which is just fine at the stock speed but damnit we gotta paste excessively large screenshots of our Quadrant tests in the threads. If 1.5GHz sounds too white hot to you, unless you’re running CM, check out their better tested official (?) 1.4GHz kernel. Yes these kernels scale and you’re better off not using SetCPU. Either way you’ll get some benchmarks to write home about.

It’s compatible with CyanogenMOD 7  though I strongly (see what I did there with the boldface?) recommend Team Whiskey’s Bionix NS1 rom which packs a pretty sturdy 1.4GHz kernel they made which I’ve been using for a week or two quite happily, though you are free to flash this 1.5GHz kernel on top of it which I’ve been using for a good twenty minutes without a single reboot.

For the benchmarking fanatics this will bring you north of 4000 on Quadrant and you’ll hold your own on Smartbench and whatever the hell you kids are using these days. Well done gents.

Doug Simmons


  1. If you could / would what, overclock? I know we need some good pools (people keep putting new ones up after I do) but, .. well let’s see.. Poll #62: For those of you who OC, have you ever incurred any hardware damage from overclocking?

    Three votes.

    So what we learn from that is that overclocking fall flat along with articles like this but I’m trying to cultivate our Android audience and maintain a draw on people who get this far under the hood with their phone, whatever the platform, so I toss it on. Also someone got an 800MHz phone up to 1.9GHz, so 50% .. eh.

    To make a weak attempt to try to kickstart an on topic discussion, you don’t hear a lot of noise from people who fried their phones from cranking up the RPMs too much. You hear plenty of warnings, at your own risk blah blah, but I haven’t come across people who’ve managed to brick their phone. I think it happens extremely rarely.

    And the phone doesn’t just shoot up to 1500MHz and stay there – when there is less demand for processor juice then the clockspeed ramps up along with, depending on the kernel, the voltage. In certain cases whatever that needs to be done being done 50% faster, battery-wise at the peak may be stronger but the peak is thinner. And when it drops not only down to lower speeds, the xda guys seem to figure out optimal voltage combinations in order to keep the phone working fully while not wasting any more battery than necessary, including, at least with the Nexus One, dropping down to half the MHz as it would otherwise when you shut the screen off.

    I can think of better polls.

  2. Not questions or challenging any of your overclocking experience. Question was:
    If you could overclock your phone (meaning any phone) would you pursue it? Or, are you satisfied with the way things are? But as you already stated, there is probably little interest in the subject. So never mind.

  3. If there was a widget on the home screen if phones out of the box that said on either side more / less CPU juice, I imagine over half would mess with it and of that half three quarters would slide it to the righ but among those two halves well over half would slide it all the way to one side or another.

    But overclocking is a bizarre concept to grasp, that you can somehow manipulate how much math some chip inside your phone does over time. Few have even a vague understanding of what a kernel is.

    Back to polling, you’re right that I’m right. Unzooming to poll people about something less technical would be a bit better (would you prefer /not/ to jailbreak / root / whatever) but the good polls need some more pinache, like this: Would you have more or less respect for Google AdSense if they allowed us to post some light “artistic” nudity?

    Now there’s a good poll.

Comments are closed.