Anyone done any oc'ing yet? I'll even take a mild oc. Instructions needed!
Related
I'm running Overcome Hermes 2.0.1 on an AT&T GSM Galaxy Tab, and I'm using SetCPU for both overclocking and voltage control. Seems like everyone has a Galaxy Tab that can be overclocked to 1.4Ghz except me. I want to join the party.
When I overclock to 1.4Ghz, for the most part everything runs fine, but when the CPU really gets stressed I get crashes. This has forced me to disable the 1.4Ghz step. This is despite the fact that my CPU performs like a champ otherwise, and I've managed to undervolt all the steps except for 1.2Ghz by quite a bit.
Is there a way for me to give the 1.4Ghz step a slight voltage bump to improve stability? SetCPU doesn't seem to offer an overvolt option, is there a way to edit a file and manually change the voltage? Where are these voltages for the overclock steps being read from in the first place?
manekineko said:
I'm running Overcome Hermes 2.0.1 on an AT&T GSM Galaxy Tab, and I'm using SetCPU for both overclocking and voltage control. Seems like everyone has a Galaxy Tab that can be overclocked to 1.4Ghz except me. I want to join the party.
When I overclock to 1.4Ghz, for the most part everything runs fine, but when the CPU really gets stressed I get crashes. This has forced me to disable the 1.4Ghz step. This is despite the fact that my CPU performs like a champ otherwise, and I've managed to undervolt all the steps except for 1.2Ghz by quite a bit.
Is there a way for me to give the 1.4Ghz step a slight voltage bump to improve stability? SetCPU doesn't seem to offer an overvolt option, is there a way to edit a file and manually change the voltage? Where are these voltages for the overclock steps being read from in the first place?
Click to expand...
Click to collapse
If you do a quick search, there's a voltage control app floating around these forums.. voltage_control_gt.apk i think..
Donate version of voltage control supports over volting. Bear in mind increasing boltage doesnt necessarily mean more stabilty at certain clock speed.
But it does mean a higher chance of ruining your motherboard.
This is a question-come-guidance request to the senior/experienced members.
> Is it possible for OB to simply just root and then Overclock?
> If not, then why?
--
I mean, in some devices, after usual rooting, we can use applications like SetCPU or similar to set the CPU frequency and voltage. But while browsing some websites, i came to know that it is not possible in case of OB due to some chipset issue or something like that. Is it true? Or there's any other reason? .... I will really appreciate if someone with knowledge can give a little technical info about this.
first of all ,you need init.d script support
you can flash quasar kernel to solve it , and then ,write some code into init.d
done
one of my friend said that he underclocked his cpu with this: https://market.android.com/details?id=com.antutu.CpuMasterFree&hl=en
he is using rooted stock rom. without quasar kernel.
is it possible?
just like you said,he's underclock,not overlock
we all can set lower frequence via setcpu or other applications,but can not overlock
Thanks for the replies. I am quite pleased to know we can at least underclock P970 easily.
I mean, i needed to guide one of my friend who is no much knowing of custom ROMs, and i culdn't risk to advise him for NOVA. But, this underclocking is still easy and sufficient, since all he was worried about was to have a long battery life. And i just hope, even without the useful tweaks of NOVA v8, a simple underclocking can improve sufficient battery life. .
( if any other "not-so-much-geek-and-easy-to-understand/employ" ways you can suggest me to extend battery life, i shall appreciate. )
Hi everyone. So I've been wondering about what the "hotplug" and "mot_hotplug" scaling governors that are present on the Droid 3 are, and I finally decided to post something about them. Does anyone know the difference between the two? What about how they scale the CPU clock compared to how the ondemand governor does it? Has anyone benchmarked battery life or something and found out if switching to hotplug or ondemand from mot_hotplug is a good idea in terms of battery life?
Thanks.
-Zane
According to the research i did, messing with setcpu causes problems, and underclocking/overclocking is not advisable right now
Droid 1 Rooted (ChevyNo1 0.9MV Kernel, LGB2.6)
Droid 3 Rooted (Stock Kernel, Custom lite De-bloat)
you can overclock to 1.2, but the kernal doesnt recognize the change. It does yield better benchmark results though. dont change to any governor. leave at moto_hotplug. checkout the xt860 overclock thread under the dev section. it works for the xt862 verizon d3 too. without the unlocked bootloader, thats about as good as we're gonna get.
here:
http://forum.xda-developers.com/showthread.php?t=1341514
I have a Samsung S phone.
I am running Cyanogen Mod-7.1.0-NS and Trinity Kernel 1.44Ghz OC version: [email protected]untu #4
The phone freezes at least once a day and the only way to get it back to life is to take out the battery.
Can someone tell me what is causing it and whether I should get a different kernel or ROM on this phone?
Is there a better Kernel to go with this ROM?
Please help!
you know what , i think it is due to the kernel cause as you said it is 1.44 Ghz while the default is 1000 only !!!!!!!!
Should I change the settings back to 1000 then?
OMG yes... why are you even using it overclocked? It's just slowly destroying your phone and drains your battery.
I also think that the freeze is due to excessive overclocking... I would suggest the default 1000 but if you really wanna overclock.. take it to max 1200 .. and if you really wanna overclock to 1400 then do some undervolting too
the oc will only gives you better shoes in bench mark your phone can run very smoothly with oc also.
-----Sent using RemICS-i9000-----
You really shouldn't be overclocking if you haven't done your research and understood what you are doing and its consequences.there is loads of information out there, search. Ask yourself this....will I be upset if I fry my phone?
Sent from the gutter, gazing at the stars
I think you should move to another rom and overclock to maximum 1200 if you desperatly want to overclock, but to be onest...it doesn't help you at all
Anyone else found this?
I was on CM7.2 with Glitch 13.1 and was able to OC safely to 1.7Ghz STABLE!!! And further more I NEVER had to touch the voltages.
But now I'm on CM9.1 with Devil3 1.4.1 I cannot OC past go 1.2Ghz with LiveOC at 110% giving me a determined CPU clock of 1.3 and a bit Ghz, if you push LiveOC to 111% at 1.2Ghz it reboots and you have to clear NSTool Settings from recovery.
Is it just me or is LiveOC a much poorer idea then the methods for overclocking used by Gingerbread...? Should I try Glitch v14 Beta 6? Even though it looks as though the Glitch kernel project has been abandoned :'(
This is just leaving me with a very s**t taste in my mouth as I was looking forward to Ice Cream Sandwich... anyone else having this issue?
You have to increase the voltages. When you set 120%liveOC, 1000Mhz are now 1200Mhz and you should set the same voltage for it as you get automatically on 1200Mhz normal OC. And you should mind that liveOC doesn't only OC the CPU, so it makes your device faster than normal OC, but it's more unstable. The maximum liveOC you can get are 130%, most users can't put in more than 120%.
Thank you dark_knight35, I will have yet another look at the LiveOC guides kicking about (Glitch's one for example) and see if I can make more sense of it.
But what you say about the voltages on a step after LiveOC is truer than true... can't believe I didn't see it! But I was getting proper annoyed :/
Do you (or anyone) know if there is a kernel out there for ICS that doesn't use LiveOC? And instead just OC's the CPU and or GPU like Glitch 13.1 did for CM7?
Again, thank you