Samsung Galaxy S II Gets Overclocked to 1.5GHz And Scores 4000+ in Quadrant

Those crazy mamajamas over at XDA have managed to take a device that was already difficult to beat and made it out right untouchable.  Member coolbho3000, has managed to overclock his Samsung Galaxy S II to 1.5 GHz, shooting Quadrant benchmark scores through the roof.

I have successfully overclocked the new Samsung Galaxy S II to 1.504GHz. This speed is enough to allow it to achieve really high benchmark scores like over 4000 points in Quadrant! 1.5GHz is a 25% overclock and makes this fast phone even faster and snappier in day to day usage.

Below, we’ve pasted the details for your convenience as he guides you through how to do it for yourself and also provides video as evidence for his achievement. Definitely give it a look over if you’ve been entertaining the idea of pushing your Galaxy S II to the max to see what it’s made of.   And definitely let us know what you think in the comments below.  Feel free to email the developer as well with your findings or if you have any questions during the process.  Just to reiterate a caveat of his to emphasize the severity and potential pit fall that lies ahead, “The usual disclaimers apply here. Only do this if you know what you’re doing”

1. You’ll need the latest version of odin3 and the USB drivers for Windows. jutley’s post on debranding the phone has links to both:….php?t=1064894
2. Grab the kernel. It is a tar file for odin with the overclocked kernel and a initramfs with proper modules for the kernel:
3. Reboot the phone into download mode using ADB:
adb reboot download
4. Flash the kernel using odin3 by placing the tar file in the PDA section and pressing “Start.”
5. The phone will reboot automatically.
6. Use SuperOneClick to root your phone if you haven’t already. ADB should have root access with this kernel so it’ll just work.
7. Grab SetCPU and try 1.504GHz.

Source code (with relevant commit for the overclock. I also enabled the interactive governor in the config):

I haven’t gone crazy on the voltages – 1.504GHz is stable at 1375mV on my device. Depending on your device, there may be even more headroom. I’ve gotten speeds of up to 2GHz to boot with instability (my unstable 1.8GHz Linpack run is currently in the Linpack top 10), but at very high voltages and temperatures. Leave it up to other developers to give you higher/more dangerous frequencies and voltages. If you stress the CPU a ton the phone will become hot to touch (though it does to a certain extent even at stock frequencies – there is not much thermal insulation between the processor and your hands in such a thin phone).

Current features in this kernel: Added 1.504GHz overclocking step (default frequency is still 1.2GHz for safety – use SetCPU to safely raise the frequency) and relevant modifications, 800MHz sleep death fix, interactive governor, = 0.

The usual disclaimers apply here. Only do this if you know what you’re doing. Though the long term stability/reliability of similar overclocks on other Android based ARM devices is known, this software is provided with no warranty, and I can’t be held responsible if you fry your device.

Just to reiterate in case you missed it in the above paragraph “The usual disclaimers apply here. Only do this if you know what you’re doing”

Since Linpack and Quadrant aren’t (sufficiently?) multi-threaded, you won’t see that much improvement over single core Cortex A8 devices at the same clock. But these are dual core phones!

Developers: keep in mind that the Galaxy S II source currently “fixes” voltages on this revision of the Exynos to be 25mV less than what is in the table. Upon boot, the driver will actually print the real voltages at each level (look for ASV voltage_table in the kernel log) if you don’t know which chipset revision a particular phone has. The overclock itself is controlled in the s5pv310_apll_pms_table.


[via xda]

About the Author: Joe Sirianni

Joe was born in New Jersey and spent most of his childhood moving around from state to state. He eventually made his way to Pennsylvania where he met his Portuguese beauty and made her his wife. He now has three great kids and full access to all of the Portuguese food he can eat. Joe's love for mobile technology began when he bought his first Palm Pilot, a Palm M130 and left it on top of his car, driving off, causing it to smash into a thousand pieces. Forced to buy a new device, he quickly discovered that specs were changing so rapidly he was buying a new device every six months just to keep up. Since then, he has constantly felt the need to have the latest and greatest. When the "smartphone" revolution began and integrating cell phones and PDA's was the norm, he quickly jumped to Windows Mobile for several years until the first Android device was launched, the T-Mobile G1. Joe began appreciating all of the free utilities Google provided and sold his soul (his precious data) to Google long before they got into the mobile OS business. So, there was no hesitation at all for him to jump on board and ride the Android train as an early adopter. And boy has it been a blast. Joe now works in the Engineering & Operations dept for a major mobile carrier where he remotely troubleshoots cell sites and loves being an Editor for TalkAndroid.

  • Attila Takács

    Than what?you can do the same with LG O2X..

  • Spike

    Wow, my over-clocked ZTE Blade manages 1060 Quadrant on Gingerbread! And that’s pretty snappy and lag free!