Related
Does anyone know of some good apps (preferably free) that I can use to overclock a rooted droid charge, with the latest altered beast ROM and kernel?
There aren't any overclock kernels at this point. Its being worked on. Just be patient.
Fe_Man said:
Does anyone know of some good apps (preferably free) that I can use to overclock a rooted droid charge, with the latest altered beast ROM and kernel?
Click to expand...
Click to collapse
You can try tegrak from the market if you really want oc.
In all honesty, just wait for a kernel to come out that will actually oc. I'd love a kernel that uses voltage control and will wait for that...
Ahh, thanks. This is my first android device so I have no idea what to expect and when
If I can ever get my config straightened out, I was going to look into doing an OC kernel that uses Voltage Control, similar to nemesis2all's kernels for the Fascinate. Still trying to get a working config though.
My opinion though is that OCing the hummingbird processor is useless, and does little for performance on a day-to-day basis and only serves to give you big numbers in benchmarks while reducing battery life.
I mostly used the 1120 step skipping 1000 and scoring serious uv was awesome
I am using Tsugi 2.3.4 with the Oyasumi 0.1 UV kernal I want to overclock to 1500 but what settings should I undervolt it to that is stable thanks in advance for the info.
DirtyPISTOLA said:
I am using Tsugi 2.3.4 with the Oyasumi 0.1 UV kernal I want to overclock to 1500 but what settings should I undervolt it to that is stable thanks in advance for the info.
Click to expand...
Click to collapse
We can't tell you not all phones are the same, uv a little (10 or 25) run it for a day or two see how it acts, if its steady, uv a little more, when it starts acting up thats your limit go back to previous settings.
NVIDIA NEVER AGAIN!
fcisco13 said:
We can't tell you not all phones are the same, uv a little (10 or 25) run it for a day or two see how it acts, if its steady, uv a little more, when it starts acting up thats your limit go back to previous settings.
NVIDIA NEVER AGAIN!
Click to expand...
Click to collapse
Alright thanks will try
Sent from my LG-P999 using Tapatalk
I've seen some general advice not to UV for anything over 1ghz speeds as well, but it may not hurt to try if you want and adjust as needed for stability.
I'm running on a -75mv at 1.5Ghz faux kernel 0.4.7..
Perfectly stable, benchmarked AnTuTu, Quadrant, and all those other good stuff.
I have not tried -100mv yet, I doubt it will be stable.
Every phone is different, but I run mine at -20 up to 1 G, and -10 for the rest.
Mine I cant undervolt shoot I have to keep my minimum frequency at 500 to be stable, course I can also run at 1.5 all day (I keep it at 1.2).
Well I guess I can't say I cant UV since I use pimp my cpu and it only gives you options in 25 increments, maybe I would be stable at like -10. But coming from my galaxy s 4g where I could UV over -150 and still be stable, that just doesnt even sound worth doing.
Edit: I just thought about it and maybe the reason I cant UV (more) is because I'm using fauxs pre UV/OC kernel, so I dont even know what stock voltage is. But comparing to my sgs4g at stock voltage I am running considerably lower voltages on the g2x.
The faux thread says it's pre uv at -50 across the board.
Beekersguy said:
The faux thread says it's pre uv at -50 across the board.
Click to expand...
Click to collapse
I been running it so long and flashed so many friends phones I can't even remember details anymore!
Sent from my LG-P999 using xda premium
Hey guys i am new here and got a small question,
In the last 3 days i switched to several roms and kernels, dunno how much i tested but i got stuck with the Bricked kernel so far, i am using a HTC Sensation classic with the Pyramid3D Rom and Bricked 1.5 Kernel atm, switched from Bulletproofed to InsertCoin and from InsertCoin to ARHD with their respective kernels, but every ROM i installed gave me lags, in the Launcher and in Games, mostly Emulators.
So now im on Bricked kernel and can play almost every emulator or 3D Games w/o any Performance hit, my cpu speed is regulated by Daemon Controller @ 1536Mhz
and with the other @ 1521 Mhz,
How does it come that every rom gave me lags on Emulators except Bricked?
Oh and one other thing is that on most kernles my phone would not wake up on camera standby, but bricked kernel does.
What is the exact reason for all this? Im yet a noob in this case, i come from the iOs scene now im an android user, maybe somone can enlighten me
Your kernel controls the speed at which the CPU runs. So the CPU in the sensation may be capable of running safely at 1.8 Ghz, the manufacturer kernel sets the CPU to around 1.2 Ghz I believe, so a kernel without underclock/overclock capabilities will automatically run your cpu at the manufacturer setting. Some kernels (not all) give you the ability to change your CPU speed using a tool such as SetCPU where you control the speed at which your CPU runs.
Does this mean that Daemon Controller does not OC my CPU but only unlock the capability to do so at higher rates?
DarkenDE said:
Does this mean that Daemon Controller does not OC my CPU but only unlock the capability to do so at higher rates?
Click to expand...
Click to collapse
No, im pretty sure the Daemon Controller is like setCPU. It could have been set to overclock after install BUT you should also have the ability to manually change the CPU speed. Im not sure, I haven't used Daemon, but I think it is done through terminal emulator.
As some of you might know, the HTC Desire S overclocks very well.
I've done alot of research, and I've found no difference between the MSM8255 chipset our Desire S runs on, and the higher clocked MSM8255T (which runs at 1.4-1.5GHz).
I've created this topic to gather some information on what method you use to over/underclock (built-in, custom, app etc), how high you've clocked your device, what governor you're using, and what temperature you're at.
Right now my Desire S runs at 1.4GHz, incredibly stable, ive stress tested for hours (so far) without any errors, maxing at bout 36,5c temp.
My current method is SetCPU, using 245-1401 interactive scaling.
Please post your findings / preferences / device settings.
I never overclocked my Desire S. Ok sometimes he can be slow, but I don't like overclocking a CPU of a smartphone... Maybe it's because I'm scared to blow him up or something, dunno. I just leave it like it was, in my eyes, the best thing you can do
I'm using OC/UV Beater2 which came in Endymion ROM. My DS is overclocked to 1,2 Ghz and it is very stable, never freezes
But I have a question, what is default undervolt settings? Because I think when I set for example -25 undervolt settings, that will come default setting after a while..
So I dont know what is default voltage... So if someone could tell what is though 122Mhz voltage, I would be happy!
1ghz ondemand. Sometimes 245/768mhz and in games 1.2ghz
Raaert said:
As some of you might know, the HTC Desire S overclocks very well.
I've done alot of research, and I've found no difference between the MSM8255 chipset our Desire S runs on, and the higher clocked MSM8255T (which runs at 1.4-1.5GHz).
I've created this topic to gather some information on what method you use to over/underclock (built-in, custom, app etc), how high you've clocked your device, what governor you're using, and what temperature you're at.
Right now my Desire S runs at 1.4GHz, incredibly stable, ive stress tested for hours (so far) without any errors, maxing at bout 36,5c temp.
My current method is SetCPU, using 245-1401 interactive scaling.
Please post your findings / preferences / device settings.
Click to expand...
Click to collapse
Yeah, I've done some research too, and cannot find any differences about the 8255T vs 8255.
Ours are highly capable of going to 1.8Ghz stable.
What are the key differences?
-------------------------------
Sent from my HTC Desire S
How severely does overclocking affect battery life
Sent from my Desire S using xda premium
245-1200MHz, interactive governor, using CM7 built in performance control. Phone is very stable, never had any problems because of OC. The highest temp i saw was +34C.
Sent from my HTC Desire S using xda premium
Same CPU 'issue' with the Arc and Arc S ->
http://forum.xda-developers.com/showthread.php?t=1396071
That pretty much sums it up, why the Desire S (some - mine?) overclocks so well..
Same thing they do with desktop CPUs.
Like my old C2D E6600 2.4GHz OCs to 3.4GHz without adding volts and running only on air cooling, 48c after 10-12hrs of stress testing with SLI nvidia cards in the case.
All in all, the MSM8255 and MSM8255T could easily be the exact same chipset/CPU, just at different speeds, some tested more extensively than others.
Has anyone tried running speeds above 1.5GHz+ successfully? 1.5GHz should also be doable, as the HTC Flyer has the MSM8255T and runs at 1.5GHz.
Raaert said:
Same CPU 'issue' with the Arc and Arc S ->
http://forum.xda-developers.com/showthread.php?t=1396071
That pretty much sums it up, why the Desire S (some - mine?) overclocks so well..
Same thing they do with desktop CPUs.
Like my old C2D E6600 2.4GHz OCs to 3.4GHz without adding volts and running only on air cooling, 48c after 10-12hrs of stress testing with SLI nvidia cards in the case.
All in all, the MSM8255 and MSM8255T could easily be the exact same chipset/CPU, just at different speeds, some tested more extensively than others.
Has anyone tried running speeds above 1.5GHz+ successfully? 1.5GHz should also be doable, as the HTC Flyer has the MSM8255T and runs at 1.5GHz.
Click to expand...
Click to collapse
Ah!
Many thanks for that mate!
Been looking and couldn't find much info too!
Yeah, i guess the T stands for being tested more.
My Desire OC's very well. I can go to 1.8Ghz stable for very long.
(I don't usually OC though.)
I tried 2.0ghz too for about 10 minutes with no issues. but I quickly went back to 1ghz incase I had any issues.
-------------------------------
Sent from my HTC Desire S
My CPU clock is as in my siggy. I don't undervolt though.
I have overclocked my phone to 1.5GHz almost all time and I do not see any problem, it's very fast and snappy. I use Sense roms, CM7 and ICS without freezes or something like that. Battery life is nice for me, 1 or 2 days of use.
I've got mine oc at 1.2ghz and uv .75 on everything using ocuv and has been stable for weeks now with good battery life.
CM7.1 Stable
TIAMAT Kernel
SmartAssv2: 184mhz - 1017mhz
Screen Off: SmartAssv2 184mhz - 384mhz
-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-
Sent from my HTC Desire S
Do you use setcpu? Can i use it also on latest stock cm7. 1 for desire s? Or is tiamat necessary? I'm mainly interested in undervolting -> better battery life.
peters. said:
Do you use setcpu? Can i use it also on latest stock cm7. 1 for desire s? Or is tiamat necessary? I'm mainly interested in undervolting -> better battery life.
Click to expand...
Click to collapse
Hi there,
Yes I use setcpu. Tiamat kernel is Undervolted by default which is good.
I'm my experience, I'm getting much better battery life with Tiamat kernel.
Are you on the nightly build or the stable version? I heard a few issues with tiamat on nightly builds, but not too sure!
Also a small note; undervolting doesn't help massively with battery life... the battery gain is minimal. On sense based ROMs, I UV by about 125V and it doesn't make a HUGE difference.
I think tiamat has really good battery llife as it has been exclusively optimised for our 8255 CPU by the brialliant Devs
Hope this has been some help to you!
-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-
Sent from my HTC Desire S
I never overclock higher than 1.5 GHz, I dont want to melt my phone.
Sent from my HTC Desire S using XDA App
I'm on latest nighly, which doesn't work with tiamat 1.1.5 (no sound). Nightly fixed some bugs which were crucial for me, so no way going back to stable.
Reason i'm asking: on lowveld's hyperions i got 8-9mA consumption while idle, on CM i'm always at 10-15. The min freq on both is 245mHz, which was suggested as lowest stable so the next difference i thought could be the undervolting... From battery stats i see that phone was not awake...
peters. said:
I'm on latest nighly, which doesn't work with tiamat 1.1.5 (no sound). Nightly fixed some bugs which were crucial for me, so no way going back to stable.
Reason i'm asking: on lowveld's hyperions i got 8-9mA consumption while idle, on CM i'm always at 10-15. The min freq on both is 245mHz, which was suggested as lowest stable so the next difference i thought could be the undervolting... From battery stats i see that phone was not awake...
Click to expand...
Click to collapse
What bug fixes did the nightlies bring? Please share!
Hmmm... I guess you could just wait for CM 7.2, I think its coming very soon with the bug fixes, so I guess you could go back to stable from there, and use Tiamat.
My lowest CPU clockspeed is 184Mhz on CM (122Mhz on Endymion)
Its very stable for me. No freezes, etc
I use smartass2, so it will throttle up the speed in sleep if 184mhz is too low. When it has many tasks to load etc.
Not to sure how to Manually UV with CM, (as OC beater doesn't work - FC on me)
But on Endymion, OC beater app does the job.
-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-
Sent from my HTC Desire S
Mainly bugs with voip calls. After htc released kernel sources, Nexx included them into the cm and the voip audio hack was not needed any more... Hopefully cm9 will be out sooner than 7.2
peters. said:
Mainly bugs with voip calls. After htc released kernel sources, Nexx included them into the cm and the voip audio hack was not needed any more... Hopefully cm9 will be out sooner than 7.2
Click to expand...
Click to collapse
Yeah, hopefully!
Side note: on sense, i could OC easily to 1.5ghz, possbily more! And it was very stable.
But now with CM7, i OCed to 1.5ghz and it froze... I tried several times too ..
So does software depend on how much the CPU can clock?
Sent from my iPod touch using Tapatalk
Good evening all,
I am currently running vb with the latest above kernel and xda-edition of setcpu...
My question, has anyone found voltages that are stable?
I have always/only used tegrak, when adjusting the voltages I am able to adjust "internal" as well as "core" voltages, as you may know setcpu only allows the adjustment of one voltage. So, I set all levels to the "internal" voltages that worked for me on tegrak(scaling set to smartass), everything was working fine until I rebooted the phone... At that point the phone would boot then freeze after the third media scan, I had to flash back to the b1 kernel to get back up and running.
Any advise would be greatly appreciated.
Thank you in advance!
Sent from my SGH-T959V using xda premium
You're trying to undervolt? Anton's b5 in undervolted. I'd stick with his recommended values.
How do you actually implement these voltages? I've only used Tegrak so this is new
Sent from my SGH-T959V using xda premium
QUIETLYloud , I dont't have paid Tegrak so I cannot make a thorough test.
I tried using very old Ultimate version available someplace on the web, and it does in fact seem to mess the phone up. I didn't need to reflash, but had to uninstall Tegrak, reboot, clear caches, and rescan SD for errors. Google says that there were issues with Tegrak module and custom kernels, but they were supposedly fixed around version 1.4.
I tied the new free version 1.6.7 from Market. It doesn't let me do much (like setting on boot), but at least it seems to work correctly with frequencies.
The setup with OC kernel is a little different. Before, if you wanted to OC, you would go and enable CPU Max Frequency, which would replace 1 GHz. Do not go there! The kernel already has all overclocking frequencies available. Instead set the Scaling to the highest frequency you want to use (let's say 1.2 Ghz, which is CPU Level 2). Then go to Optimization and set desired voltages for the frequencies you chose. No need to change anything for frequencies above you max scaling, the CPU will not go there anyway. Maybe it's a good idea to completely clear Tegrak data and start setting it up form scratch.
Let me know if you succeed.
Btw common Google knowledge doesn't seem to recommend lowering internal voltages. You will not gain much, there is just not a lot of current draw there. It's the core that draws a lot of current.
EDIT: Hmm... Tegrak seems to have a problem with smartassV2 governor. If the scaling in Tegrak is set to use anything but all frequencies, including 1.4 Ghz, the governor will never lower the frequency from the highest selected. The kernel itself (with SetCPU or without) doesn't have this problem, it's only when proprietary Tegrak module is loaded.
AntonX...
I decided to scrap tegrak for the time being and use what you recommended with setcpu and left voltages alone until I have a better understanding, since doing so haven't had any problems
Sent from my SGH-T959V using xda premium
Btw I said before I set the default voltages kind of safe, even if they are slightly undervolted. I'm running the kernel UV-ed a little more with SetCPU for second day without any issues. Here are my numbers right now:
1.4 - 1350
1.3 - 1300
1.2 - 1275
1.0 - 1250
800 - 1175
400 - 1025
200 - 925
100 - 900
Hi guys
I apologize for some noobness coming this way, but I don't understand. Kernel beta5 is oc/uv - what does it mean if I don't use setcpu/tegrak?
Will kernel behave other than prior versions?
And if I decide to do use setcpu? What good does it make if uv makes no change (according to Antonx) and oc will only drain the battery even more, I mean, phone is pretty much fast, so why bother oc it?
Thanks!
Sent from my SGH-T959V