Related
So now that I have Froyo, how do I overclock it?
I'm rooted with stock build (FRF50).
There have been a few tutorials out there but I'm not sure what is applicable now and whether they will still work.
If they do still work, can someone pls recommend a good one that will work for sure with Froyo?
Thanks lots in advance!
Hi there,
I've been running FroYo overclocked for a few days now and am absolutely loving it.
I'm running the leaked build that Paul uploaded, and running the pre-rooted kernel from Cyanogen. Other than that, I manage the CPU's speed with SetCPU, running at a max of 1113MHz.
The kernel can be found at http://forum.xda-developers.com/showthread.php?t=686627
codesplice said:
Hi there,
I've been running FroYo overclocked for a few days now and am absolutely loving it.
I'm running the leaked build that Paul uploaded, and running the pre-rooted kernel from Cyanogen. Other than that, I manage the CPU's speed with SetCPU, running at a max of 1113MHz.
The kernel can be found at http://forum.xda-developers.com/showthread.php?t=686627
Click to expand...
Click to collapse
what he said...
Umm...
OT
...Android kernels don't get "rooted". Root on these phones simply means having the "su" app with suid set, and superuser.apk around to manage thos permissions. If you can put those two files in place with a stock kernel, and properly set the permissions, you have root.
endOT
That said, there appear to be two "packaged" solutions to OC your FroYo:
Cyanogen's update.zip (not only does it put in an overclockable kernel, it also roots your phone).
Pershoot's newly-posted kernel (this is what I'm running...)
Of course, if you are brave, you can always "roll your own". People are clearly doing this, as there are FroYo Nexus One's out there showing 1.2ghz speeds.
big_adventure said:
Umm...
OT
...Android kernels don't get "rooted". Root on these phones simply means having the "su" app with suid set, and superuser.apk around to manage thos permissions. If you can put those two files in place with a stock kernel, and properly set the permissions, you have root.
Click to expand...
Click to collapse
You also need ro.secure=0 in the default.prop file (of the ramdisk portion of boot.img). So you could say the kernel gets 'rooted' this way (correct me if I'm wrong).
(On the Motorola Milestone this is not possible even though you can add "su" and "Superuser.apk", although on the Droid you can)
has anyone really gotten a real world speed increase with the OC'ed cpu? Yes it can technically run faster, but do our phones ever really max out the cpu when we are using them? Personally I feel that the ram adds more to the speed of the phone than the cpu. But that just an opinion. I'll have to see about doing some testing to see what the active cpu levels are under use.
followinginsanity said:
has anyone really gotten a real world speed increase with the OC'ed cpu? Yes it can technically run faster, but do our phones ever really max out the cpu when we are using them? Personally I feel that the ram adds more to the speed of the phone than the cpu. But that just an opinion. I'll have to see about doing some testing to see what the active cpu levels are under use.
Click to expand...
Click to collapse
You can see improvements with benchmarks, but as far as noticing a difference... no, not really. There's always the placebo effect of "wow, this is so much faster with a ~10% overclock", but I don't think it's really a difference that you can pick up on. There are a lot of other things that could account for a 10-15% performance difference at any given time.
Granted, I could tell more of a difference on 2.1 than I can on 2.2 Froyo's JIT capability improves the efficiency to the point that you really can't tell a difference at all. Under 2.1, I at least felt like the menus were just a little snappier. Everything is snappy under Froyo though.
Clear as mud, lol?
side by side with a stock clocked n1 was the only way i could see a differance.
but its not a drastic differance, like a stock droid vs 800 mhz droid
I'm sure one of the first additions to a rooted EVO is the wifi tether option...
What are some cool unique things the community has done to your very on EVO. Changed the carrier string from Sprint to your initials...?
dlbevo said:
I'm sure one of the first additions to a rooted EVO is the wifi tether option...
What are some cool unique things the community has done to your very on EVO. Changed the carrier string from Sprint to your initials...?
Click to expand...
Click to collapse
Custom kernels, which allow you to overclock the Evo to 1.2 Ghz, new boot screens, new themes, and new ROM's with better performance, speed upgrades, and longer battery life.
i have heard quite a bit of buz about that overclock. im eager to see what are the long time effects of that on the CPU. Can it handle several months of being overclocked...not to mention the increased heat-output?
dlbevo said:
i have heard quite a bit of buz about that overclock. im eager to see what are the long time effects of that on the CPU. Can it handle several months of being overclocked...not to mention the increased heat-output?
Click to expand...
Click to collapse
I don't understand the point, other than for bragging rights. 200MHz isn't really enough to make a noticeable difference, once you're in the GHz range!
For me, I rooted for freedom and control over my device. Things like removing all the bloatware to free up space for real applications! Oh, and the Decepticon boot animation!
20% faster is substantial. More importantly to me, you can underclock your device at idol, and overclock when the processor is maxed out. Try watching a move at full resolution and tell me you don't need more speed. I hope that gets better with Froyo.
I added a reset button widget that only works with root.
-Roger
Has anyone else noticed that when using NAND Desire HD/Z sense builds that their phone seems to run more smoothly after the 1st day or two running at stock speeds than it does when running overclocked?
I was getting a bit of lag here and there, and as expected after having streamed music literally all night via wifi the phone was a real dog first thing in the morning until the memory cleared out.
I noticed after a couple of days my phone would spontaneously reboot - I was overclocking to 1.5ghz using MDJ's 10.3OC kernel, so I figured that it was the overclock causing the reboot - sure enough the phone runs smooth as glass now that I've throttled it back to 1ghz (interactive governor).
Is it just my imagination?
It is hard to say really, as you will have different apps, widgets and syncs set up to me, plus we are running different builds, thus a direct comparison is very hard.
All that matters is what works for YOU.
FYI I don't find any meaningful benefit by overclocking. So I don't bother. I haven't really noticed a speed difference either way. If however it made a positive difference, I would.
Just for the record, benchmarking and Quadrant scores are nothing more than a waste of time and are only useful for arguments starting with the words "Mine is better than yours because...".
Curiousity always gets me to run Quadrant, but having seen varied phones with roller-coaster scores, I know the scores are not really any kind of valid gauge for real world performance.
I'm going to run my phone at stock speeds for the rest of the week and see how it does. I've got a feeling it will be running a lot smoother.
Ok I aint joking but seriously what is the point of overclocking a Desire z/G2. Unless I am running on a slow phone I don't see the point. Stock speed never lags and i haven't seen any difference between 1.5 ghz vs 800mhz.
The only time when 1.5ghz clock speed is useful is when i running quadrant and rubbing its scores infront of my friends face.
There is any areas where you can actually see the performance difference?
bluntly, if you dont see the point of it then you don't need it.
For others, sometimes you run alot of stuff in the background and still want to be able to have your main app perform at its best level.
There is also the minute tweaking of speed and snappiness of the interface. The idea of instant reaction when you open your message app, or your email, or anything.
bruceko86 said:
Ok I aint joking but seriously what is the point of overclocking a Desire z/G2. Unless I am running on a slow phone I don't see the point. Stock speed never lags and i haven't seen any difference between 1.5 ghz vs 800mhz.
The only time when 1.5ghz clock speed is useful is when i running quadrant and rubbing its scores infront of my friends face.
There is any areas where you can actually see the performance difference?
Click to expand...
Click to collapse
Heavy multitasking
Sent from my HTC Vision using Tapatalk
flash video seems pretty laggy to me at 800...
http://lmgtfy.com/?q=overclocking
Sent from a Western Union telegram.
blackknightavalon said:
http://lmgtfy.com/?q=overclocking
Sent from a Western Union telegram.
Click to expand...
Click to collapse
Best link ever! I hope i can remember it long enough to use it sometime.
Sent from my HTC Vision using XDA Premium App
blackknightavalon said:
http://lmgtfy.com/?q=overclocking
Sent from a Western Union telegram.
Click to expand...
Click to collapse
Ya i know what overclocking is but I haven't found one instances where I needed it to run an app. G2 is already damn fast and it runs android with no lag but I really see no point until more demanding ver. of android come out.
I just wanted to see who overclocks their G2 everyday and for what purpose.
bruceko86 said:
Ya i know what overclocking is but I haven't found one instances where I needed it to run an app. G2 is already damn fast and it runs android with no lag but I really see no point until more demanding ver. of android come out.
I just wanted to see who overclocks their G2 everyday and for what purpose.
Click to expand...
Click to collapse
Fair question IMHO.
I don't see the difference when overclocking, or rather I don't feel it. Software does make a difference, but not the extra 200-500Mhz. I do feel however the battery drain
It always makes me laugh when somebody asks a legitimate question and you get silly responses like the above 2. It's as if these people feel threatened and have to justify that they are more knowledgeable than the op. The facts of the matter are most of the tweaks, mods and alterations are wholly unnecessary in the real world.
If you don't feel like it makes it better then you don't have to use it. I use it because I feel it makes everything just a little snappier and more instant. If you don't notice a difference that's fine. It's probably trivial for me to notice the little hang ups but I can't help it.
Sent from my HTC Vision using XDA App
For me there's several reasons. For the most part, the reason for oc is because you can. But there are practical reasons as well. For example, with the stock ROM running at 800MHz, you're stuck with that. With an oc kernel and using SetCPU or built in clock settings in CM, you can adjust it as needed. Gonna play a game? Bump it up to 1GHz or so. Done with said game? Take it back down to 800MHz. But it's not all about oc. Sometimes there's a need to underclock. Getting low on battery and don't have a charger near by and need to squeeze another hour or two out of it? Maybe take it down to 768MHz or 600MHz (if you're running Pershoot's kernel).
Dungeon Defender:
800 mHz : not fun, laggy
1.5 gHz : fun, graphic are more smooth
Reasons for using over clocking:
Because I can
Because sometimes I do notice the difference in performance of the UI and some applications (wait for Sense 3.0 etc...)
Because I also use it to underclock.
Like everything else, a lot of it is perception. My wife cannot see any difference between our normal cable channels and the HD ones. I can (or am I just trying to convince myself that I can?). Oh well.
Finally some practical and helpful responses, showing an understanding of the need for information from some people.
here's my experience when it comes to overclocking. keep in mind that, like with your computer, it does vary from user to user... so I'm making these statements from MY experience, not making blanket statements regarding all of our devices:
- if you run multiple homescreens with multiple widgets and ui "smoothness," not just aesthetically, but performance-wise as well, is of concern, mild overclocking becomes necessary.
- if you have several apps running at any given time (in background or foreground) and ui smoothness, same definition as above, is of concern, mild overclocking becomes necessary.
- if you run any iteration of a sense rom in any configuration and ui smoothness is of concern, mild overclocking becomes necessary.
- if you run PSX/N64 emulators and you don't want audio distortion or general lagginess, more aggressive (in my case, 1209 is a safe speed for maximizing performance without having a drastic effect on battery life) overclocking becomes necessary.
on AOSP builds, especially gingerbread-based, I don't think there is a necessity for more processing power than what we get from the factory if you're running a relatively slim setup and aren't using something like a PSX/N64 emulator regularly.
I run mine at 1ghz, but I did use 1.2ghz before. I do notice a slight performance difference. Overall tho I don't notice it much. I notice it more when I'm doing multiple things.
Nonsense!
OneGoodKnock said:
Finally some practical and helpful responses, showing an understanding of the need for information from some people.
Click to expand...
Click to collapse
For all that you're talking, you have yet to provide anything of value to this conversation while you're sitting up there berating those other 2 posters.
Think about it.
Sent from my Desire Z via XDA App
I run 1.1 because it is noticably faster. Everything opens faster and works smoother. My wife has a stock G2 and when I grab it to look something up on the web or to use maps when we're out, I instantly notice how mucher slower hers is.
Works for me so I use it.
I notice a definite performance boost on mine, but it also depends on which kernel/ROM you use. I was running meXroid for a few days and found that it got extremely laggy even overclocked with Flippy's kernel built in (1.9Ghz), plus my battery was dying faster than a Chuck Norris joke. PyroMod has always been reliable for me and I flashed back to 2.0 earlier and it's just as reliable and power-saving as ever.
mputtr said:
For all that you're talking, you have yet to provide anything of value to this conversation while you're sitting up there berating those other 2 posters.
Think about it.
Sent from my Desire Z via XDA App
Click to expand...
Click to collapse
Thanks for that.
Hello,
two days ago i changed the size of my Vm-heap to 32mb. I was curious after i read in some posts that this could affect the performance of resource-intensiv apps. As i am using navigon-navigation a lot i had to give it a try...
After ive changed it and rebootet the device, navigon works MUCH better then before, track calculation is much faster and the app is much more responsive and running fluent. The difference is highly noticeable. For other apps like my browser i experiecend the same.
I read that the downside of it is that it is possible that apps could be moved out of memory because some other apps now use more ram and so the jumping between apps could be more time intensive. But i have noticed no slow down at all.
(Wildfire is not a fast phone, but i think 384 mb ram is really good for that kind of phone, some other phones like galaxy ace have only 287 RAM with better cpu)
My experience is that a lot of apps running much better know, and for me its a absolute performance enhancement, I would even go so far that i would say it was the best performance-enhacement after overclocking the device. So if you are running resource-intensive apps (like navigation browsing) you should definitely give it a try.
Whats your experience with that ? Ever changed the vm heap size? Noticed differences??
Cheers.
im rocking 32 since i s-off my phone with alpharevx beta,and yes its better for intensive apps (imo) but the one thing i cant understand is way my phone i lagging when i get a call??some times the ringtone is playing and the screen is black,any tips thx
darkstep said:
im rocking 32 since i s-off my phone with alpharevx beta,and yes its better for intensive apps (imo) but the one thing i cant understand is way my phone i lagging when i get a call??some times the ringtone is playing and the screen is black,any tips thx
Click to expand...
Click to collapse
im running my phone with the ondemand governor with cpu-min:528 and cpu-max:691 and i have no lag when someone is calling.
Nhs666 said:
im running my phone with the ondemand governor with cpu-min:528 and cpu-max:691 and i have no lag when someone is calling.
Click to expand...
Click to collapse
It is indeed said that such lag is due to the 'extreme' underclocking of the processor.
I'm on CM7 RC1, use SMARTASS with 245 as a minimum, and haven't noticed any lag yet..
Sent from my HTC Wildfire using XDA App
ErwinP said:
It is indeed said that such lag is due to the 'extreme' underclocking of the processor.
I'm on CM7 RC1, use SMARTASS with 245 as a minimum, and haven't noticed any lag yet..
Click to expand...
Click to collapse
I didn't want to implicate that the ringing lag is about the low freq., but i noticed that with such low freq's the phone is not so responsive when pulling suddenly the notificationbar, get it out of standby and such things. Never noticed something like that??
I was testing about it too. i settled with 32mb heap size, which i've found to be the best practice. Anything lower would make apps like navigon or opera lag, anything higher, would give me force closes on apps for some reason.
I also tried to experiment with compcache, with the following settings "disabled, 18%, 26%" and i think 26% makes my wildfire a bit snappier, although it might be just a placebo effect, because there's no difference in quadrant/linpack benchmarks.
why placebo effect....the question is how good can a benchmark represent the practial application in daily usage. Anybody?
I tried vm heap bigger than 32mb too. But while running navigon it seems to me not much as a big improvement so i switched back.
The compcage thing will be the next thing im testing.
Nhs666 said:
why placebo effect....the question is how good can a benchmark represent the practial application in daily usage. Anybody?
I tried vm heap bigger than 32mb too. But while running navigon it seems to me not much as a big improvement so i switched back.
The compcage thing will be the next thing im testing.
Click to expand...
Click to collapse
I have to agree with you Whatever makes my phone "feeling" snappier and faster is good enough in my eyes!
You should really check Juwes Ram optimization thread in the Android development section for some serious performance gain. I flashed it yesterday in CM 7.1 Nightly 144 and the responsiveness boost is quite noticeable.
i agree the synthetic benchmarks are not that important its the daily use performance that mater to me
I have disabled compcache and enabled swap and my phone is snappier than 18%compcache may be Coz of compressing and decompression techniques that slow the process in compcache and scores 3.9 to 4.1 on linpack score with 576 MHz speed...
Sent from my HTC Wildfire
vijaykirann said:
I have disabled compcache and enabled swap and my phone is snappier than 18%compcache may be Coz of compressing and decompression techniques that slow the process in compcache and scores 3.9 to 4.1 on linpack score with 576 MHz speed...
Sent from my HTC Wildfire
Click to expand...
Click to collapse
Hmm i have a swap partition already made just in case and i might try it, but in theory a swap partition (even worse if it's a file) is much slower than the compressed cache due to the SD Speed limitations, unless we are discussing about class 10 cards.
anyone ?