I just installed the latest kitchen build on a 6700 and notice there's a performance program in the settings section, that allows for overclocking the cpu. it has a couple warnings about damages and errors etc, however I'm curious what the experiences are using this. is it safe to run all the time or what? I tried it out a couple times and the phone seems twice as fast. Any info appreciated.
I use Pocket Hack Master v4.33 and I run at 624 all day and have been for a long lone time and never had any adverse effects.
I have used XCPUScaler and I never had a problem, for Xscale processors, from what I have researched, all the program does is change the frequency of the CPU controller, Ram controller, and LCD controller. I have also read that the more power that the Xscale processor is given, the higher the speed/frequency. Well enough tech talk, the only difference I have ever seen is that battery drain is a bit more when the cpu is overclocked, never has frozen on me running at 624Mhz. Good luck.
Related
The question is often, how to overclock and there is a bunch of thread on that, but what about "downclocking" ?
I was thinking of that to extend my battery life when using low CPU consumption programs. Is there a stable program that can be recommended (my processor is a Samsung SC32442 400MHz Processor) ?
Thank for your support !
I would also be interested in something like this. Also a program that could suspend different parts of the phone would be nice. I would really like a program that could shutdown the display when playing mp3s on the pda.
hi guys.
i'll want know a good program for overclock my trinity.
it's possiblehave 500mhz rock solid?
thanks
http://forum.xda-developers.com/showthread.php?t=324781&highlight=overclock
Some people report Pocket Hack Master worked for them.
Able to actually change the CPU speed, and noticed some obvious changes in their device behaviour.
It's worth a try
well i was experiencing very slow speeds and it seemed too sluggish for a 400mhz cpu. well i install xcpuscalar(3.03) and it was showing my cpu was set at 200mhz. this is a fresh flash of htc official wm5 rom so i found that odd. well i set it to 500mhz and ive been running it stable and smooth no problems. much faster, very obvious, will have to test more to see effect on battery but it does have settings to scale the cpu according to load. ymmv
cecrops said:
well i was experiencing very slow speeds and it seemed too sluggish for a 400mhz cpu. well i install xcpuscalar(3.03) and it was showing my cpu was set at 200mhz. this is a fresh flash of htc official wm5 rom so i found that odd. well i set it to 500mhz and ive been running it stable and smooth no problems. much faster, very obvious, will have to test more to see effect on battery but it does have settings to scale the cpu according to load. ymmv
Click to expand...
Click to collapse
That might be a new release of xcpuscalar that does support the samsung cpu effectively.
Some people has tested that soft one year ago, but it appeared to be, even once set to 500 mhz only placebo effect. When check with other softs, the cpu speed remained the same.
Nevertheless, it's very odd that on a fresh bought device, you have only a 200mhz speed, half the normal one...
The Trinity run very slow sometimes, but this is a matter of optimisation of the ROM you are using, not necessarilly a problem with the cpu speed itself.
Another good and simple way to check your cpu speed is TCPMP. In any case, it's always better to double-check with another soft, rather than believe everything your overclocking soft says.
riri22 said:
That might be a new release of xcpuscalar that does support the samsung cpu effectively.
Some people has tested that soft one year ago, but it appeared to be, even once set to 500 mhz only placebo effect. When check with other softs, the cpu speed remained the same.
Nevertheless, it's very odd that on a fresh bought device, you have only a 200mhz speed, half the normal one...
The Trinity run very slow sometimes, but this is a matter of optimisation of the ROM you are using, not necessarilly a problem with the cpu speed itself.
Another good and simple way to check your cpu speed is TCPMP. In any case, it's always better to double-check with another soft, rather than believe everything your overclocking soft says.
Click to expand...
Click to collapse
after more usage i uninstalled xcpu. when you first run the program it is set to default 200mhz which is why i thought thats what i was really at. TCPMP says im at 390-400 no matter what. better not to have too many programs running and loading at boot. also i tried pocket hack master but that didnt work either. ill stick to sktools and trinityhack, those registry tweaks are what i think i really needed.
I read a lot about undervolting on here and i think i have an idea about what it does but i may be way off, and im sure each device is different. in pimp my cpu there are multiple options, and while this sounds newbish i think this should be explained to folks in some more detail.
this is what im assuming.
undervolting allows for less power consumption.
UV on higher OC levels controls power spikes to the CPU?
what is a safe level to UV and at what frequencies specific to the G2x
i am reading up on this, to get a better idea. http://www.android.net/forum/android-rooting/58117-droid-x-guide-undervolting-guide.html
Here's my understanding of the whole undervolting thing..
In order to maintain stable operation across devices with varying production quality (not all chips are created equal), manufactures use voltage levels higher than necessary for most devices. They cater to the least common denominator. But most phones will still operate reliably at a lower voltage. By undervolting you can extend your battery life and ward off chip killing heat. This all becomes even more important when overclocking. When you overclock your device you increase the power usages (those extra megahertz aren't without cost). This increases both the drain on your battery and the heat produced by your CPU. Undervolting helps to offset both issues.
As for the proper undervolting levels...that will vary with the tolerance of each individual device. But I'm sure someone can provide some general guidelines...sorry I haven't undervolted the g2x yet and don't want to steer you wrong.
Hope this helped...
Good info. I dropped mine .25 on each higher level. So ill see how it goes
G2x with CM7 and faux kernel
what confuses me on this topic is the "it's different for each device" phrase that I keep reading. Is this in reference to the rom/kernel that is being used or is it specific to apps installed/how the phone is used.. or is it a combo of both?
It's confusing me because its seems that OC/UV is hardware specific and each phone has the same hardware. So I don't quite get this "it's different for each device" thing..
schmit said:
It's confusing me because its seems that OC/UV is hardware specific and each phone has the same hardware.
Click to expand...
Click to collapse
Each phone doesn't have the same hardware....for example, G2X has an nvidia tegra 2 and the nexus s has a hummingbird.
i think you mean this.
cybereclipse said:
Each phone doesn't have the same hardware....for example, G2X has an nvidia tegra 2 and the nexus s has a hummingbird.
Click to expand...
Click to collapse
yes all g2x's have a tegra 2 chip.
But production does not always produce the same tolerances for all the chips.
ussually(with the quality control apparently given to the g2x who knows) but ussually all chips are tested and every chip that is in a g2x will perform reliably at 1ghz as it is specified and sold at.
some of these will run reliably at 1500 or better while some will not go over 1100 without starting to get unreliable.
example is the droid 1 was sold at 550 mhz. they did an update that upped it to 600mhz so they knew all chips were tested to be ok at that threshold. Mine would run at 1200 reliably no overheating(except running flash) no reboots.
with 2 different kernels. there was another kernel that they messed with the voltages so that i would get constant reboots even at 700mhz.
some droids would not run over 700 without experiencing problems.
So yes the tegra 2 chips is the same but the abilities of it can be different. they are guarenteed to run at the speed they are sold at but most will function at a much higher speed without problems while some will not.
oh just thought of a great example. the AMD tri-core processors.
those are quadcores where 1 of the cores did not pass the tests but the other 3 did so instead of scrapping the entire chip they turned off the bad processor and sold it as a tricore. there are motherboards out there that allow this core to be turned back on and many have done this and it works just fine. its just that core didnt pass whatever minimum they set on it even though it was perfectally functional they determined that if it got to this temp or didnt run at this speed(over what it was sold at) it didnt pass.
So while this kernel at this voltage may run fine on your phone it may caused reboots or lock ups on others.
hope this makes some sense.
eagle1967 said:
yes all g2x's have a tegra 2 chip.
But production does not always produce the same tolerances for all the chips.
ussually(with the quality control apparently given to the g2x who knows) but ussually all chips are tested and every chip that is in a g2x will perform reliably at 1ghz as it is specified and sold at.
some of these will run reliably at 1500 or better while some will not go over 1100 without starting to get unreliable.
example is the droid 1 was sold at 550 mhz. they did an update that upped it to 600mhz so they knew all chips were tested to be ok at that threshold. Mine would run at 1200 reliably no overheating(except running flash) no reboots.
with 2 different kernels. there was another kernel that they messed with the voltages so that i would get constant reboots even at 700mhz.
some droids would not run over 700 without experiencing problems.
So yes the tegra 2 chips is the same but the abilities of it can be different. they are guarenteed to run at the speed they are sold at but most will function at a much higher speed without problems while some will not.
oh just thought of a great example. the AMD tri-core processors.
those are quadcores where 1 of the cores did not pass the tests but the other 3 did so instead of scrapping the entire chip they turned off the bad processor and sold it as a tricore. there are motherboards out there that allow this core to be turned back on and many have done this and it works just fine. its just that core didnt pass whatever minimum they set on it even though it was perfectally functional they determined that if it got to this temp or didnt run at this speed(over what it was sold at) it didnt pass.
So while this kernel at this voltage may run fine on your phone it may caused reboots or lock ups on others.
hope this makes some sense.
Click to expand...
Click to collapse
Nice...that was much better than my explanation.
cybereclipse said:
Each phone doesn't have the same hardware....for example, G2X has an nvidia tegra 2 and the nexus s has a hummingbird.
Click to expand...
Click to collapse
lol. dude, I'm in the g2x forum.. not the "whatever phone ya wanna talk about" forum. I was referring to the g2x's having the same hardware, lol.
Thanks to the other guy for the awesome explanation
Hello,
My Nexus S reboots when I overclock it to 1,4 Ghz or higher. I read some posts of people who run their phone without problem with this speed.
Is there a reason that mine reboots? It happens with every ROM/kernel I use.
Thanks in advance
Linus_BE,
I've seen this as well.
Mine seem to happen only when I try to open Firefox or Opera Mobile.
I assumed that like most desktop CPUs, the processors in mobile devices go through the same type of testing process, and are rated at a specific clock speed because that is the one they are stable at.
Overclocking works because in most cases a CPU is actually capable of running at higher clock speeds, but due to manufacturing defects and/or microscopic differences in the silicon an individual CPU from a batch may not be happy at a faster clock speed.
Now, why mine only seems to exhibit this behavior at higher clock speeds when running Firefox or Opera Mobile, I can't explain.
I don't believe it to be something related to the CPU, since I can run the stress test in SetCPU and not have the device reboot.
Jacob
I'm running CM10, and it's running fine overclocked to 1600 MHz, yet the phone is factory clocked, (with a factory ROM), to 1200 MHz. Why? My phone seems to run perfectly fine using SmartAss2 management, but Samsung apparently purposely underclocks phones for some unknown reason. Obviously stability isn't a concern, or it would crash at 1600 MHz. Yet it is stable, so why is the default clock speed so slow? Considering the phone is perfectly stable at 1600 MHz, would it be possible to O/C my phone to 2 GHz, or would I risk frying my phone if I somehow managed to OC it by that much?
k-semler said:
I'm running CM10, and it's running fine overclocked to 1600 MHz, yet the phone is factory clocked, (with a factory ROM), to 1200 MHz. Why? My phone seems to run perfectly fine using SmartAss2 management, but Samsung apparently purposely underclocks phones for some unknown reason. Obviously stability isn't a concern, or it would crash at 1600 MHz. Yet it is stable, so why is the default clock speed so slow? Considering the phone is perfectly stable at 1600 MHz, would it be possible to O/C my phone to 2 GHz, or would I risk frying my phone if I somehow managed to OC it by that much?
Click to expand...
Click to collapse
uhh well.... yea and no. there are a few things you need to understand about microprocessors. no two are alike. they are built on a scale of a few nanometers and any difference causes a significant difference. to keep production numbers up there is a line they have to draw between performance potential and stability. more chips will be stable at lower clocks so they pick an speed they can get a high production number out of. sometimes a whole line of chips is produced with exactly the same core. chips that pass the highest get boxed as the highest performing and priced. chips that dont pass will either have specific features turned off, cores turned off or be underclocked and sold as lower models. in addition to that the top performing models are actually over priced, and often many more pass the tests than they need so perfectly good processors are intentionally disabled to fill the market for lower speed processors, so yes the cpu may be "underclocked" in a sense. but i don't know if that really applies to the infuse because i don't know if there are any chips in the same family that have a higher rated clock speed, if there are they aren't used in phones.
in example, on my pc i have a 3 core processor, it's actually a 4 core and i can even turn the 4th core on in bios, but a certain percentage of that particular model of chip will be unstable with the 4th core active.
another thing to understand is how the clock speed is set. there is a buss and a table of multipliers and dividers. so as one part of the chip oscillates at one frequency the multipliers and dividers say how may times per oscillation the other components go. the cpu speed changes by changing these multiplier values. the problem is that there are only so many multipliers the cpu is designed to use. this is a hardware limitation and can't be overcome so at some point the only way to get more clock speed is to change the buss speed which affects the entire system and will cause instability in most cases. occasionally you can get around this if you change the multiplier values for other componants as well but it's probably not a good idea to mess with it. the hummingbird chip only has multipliers to go to 1600mhz regardless of stability unless you mess with the buss, one developer got the galaxy s to 1700 with buss overclocking but some things didn't really work at that speed and it took a lot of changes to other system clocks. snapdragon chips can go to higher clocks and process numbers better but the hummingbird is better for graphics and multimedia which is more important on a modern phone imho.
so yeah 1600 is it, as far as practicality goes anyway. there are a few infuses that can only go to 1400-1500 as well and galaxy s phones which have the same clock limitations but are only rates for 1000mhz rarely go to 1600, but a few do, my captivate was absolutely peaked out at 1300, believe me i tried to get it higher, i tried a lot of things with voltages to try to get it stable, but even 1300 took some doing. it took a long time before developers even produced a kernel for the sgs that used clocks over 1200 because many of the early builds of the sgs series were much like mine and were not stable at high speeds.
Beautiful. :thumbup:
Sent from my SGH-I997 using xda app-developers app