Cosas que no debes hacer con tu Android: Overclockear los 8 núcleos de un SGS4

Cosas que no debes hacer con tu Android: Overclockear los 8 núcleos de un SGS4

Otros

Cosas que no debes hacer con tu Android: Overclockear los 8 núcleos de un SGS4

7 julio, 2013 11:36

¿Queréis saber una divertida manera de cargaros vuestro SGS4 de 8 núcleos? Pues bien, esto es lo que ha hecho el hacker DSWR: retocar el kernel para que los 8 núcleos de su SGS4 -i9500 estén activos y overclockeados a la vez, permitiendo alcanzar una frecuencia de 2,8 GHz. Efectivamente, el resultado ha sido la placa base quemada.

El mismo DSWR explica el proceso (ojo, en inglés):

My main focus has been towards the twin processors though. As some of you maybe aware, the Exynos 5 octa-core chip is technically a 1.6GHz Cortex-A15 and a 1.2GHz Cortex-A7. This therefore means we technically haven’t got the output power of Snapdragon 600 variant at 1.9Ghz. I’ve been running octa-core and quad-core variants of this phone side by side. Although technically the snapdragon 600 should technically be more powerful and also more economic, I’ve finally managed to beat the 1.9GHz of the Snapdragon on an octa core version. Originally, I managed to overclock the octacores A15 to 2.0Ghz. After much research I then looked into what many have mentioned on the forums. «Is there a way to get both processors going at the same time» entially, have a true octa-core processor running. I found a few flaws in the system trying to do this. First problem was the requirement to get them to work along happily. These cores would NEED to run at the same frequencies. I found out that you could infact get them on the same frequencies with a simple bit of underclocking. Forcing the A15 to run at 1.2Ghz and telling both chips to run at a minimum of 500MHz at exactly 1000000-μv. Now that they would work in harmony together, I had to then get them both working together. I had simulate a way to make the phone think it was in power saving mode, so the A7 would power, and then have the A15 working as well. Using a custom kernel, this actually worked, for a while, Sadly, the device did cook itself after…half an hour running. I think the problem was down to the voltage going through the cores at such power, especially seeing as both the chips were running where as it’s typically just one. Before actually managing to cook the phone (It was completely knackered, overheated, will strip the phone down sometime showing pictures of the disaster) I did manage to clock it on geekbench at 2.8GHz. Hopefully I can do something about the phone, or even just buy another if required and release a couple of videos showing how this was all done. I believe it was the A7 that cooked as people have said to have managed 2.6GHz on just the A15 alone. Please note, If this was 2.8GHz between both cores, that’s only 1.4GHz per chip as geekbench does recognise «8 cores» but samsung before only ran 4 of them!!!

 

Así que ya sabéis queridos androides, no hagáis esto en casa.

Vía AndroidCentral