Database Users

Making my Evo any faster?

So I've been messing around with different roms and kernels for the past few weeks and finally settled on CM6 6.1.1, and the snap 7.6 bfs kernel, for stability and speed. I turned on the turbo mode with snap, OC'd to 1152mhz (freezes at 1192), killed all apps, and ran quadrant.
[Picture of a 2330 benchmark screencap was supposed to go here, but I don't have eight post haha]
I know thats pretty good, my scores average from 2100-2350, but I'm looking to make it even quicker. What can I do?
Thanks!

Move to gingerbread.
Sent from my PC36100 using Tapatalk

sultan.of.swing said:
Move to gingerbread.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Which ROM and which kernel?
weehooherod said:
Don't use Snap 7.6 on CM6.1.1, just use the stock kernel. The new kernel built in with CM6.1.1 is much better, Snap 7.6 is pretty old.
Click to expand...
Click to collapse
I had 6.1.2 flashed, but snap wouldn't work on it and I was only benching around 1400 with the stock kernel.. Even with an OC

xsaqzw said:
Which ROM and which kernel?
I had 6.1.2 flashed, but snap wouldn't work on it and I was only benching around 1400 with the stock kernel.. Even with an OC
Click to expand...
Click to collapse
Benchmark scores don't matter. I don't even check them anymore. Wether I get a 1400 or 2200 its still gonna dial a number at the same speed. Im not playing call of duty on my phone or anything. I want efficiency.

A benchmark does not actually show how fast your phone is....
Cyanogen himself stated this.

quadrant scores =/= to your phone being 'fast'.
But if you care about synthetic benchmarks then you could trick your file system into giving you quadrant scores in the 3000+ range.
by the way thanks for posting this in the relevant subsection of the evo forum dedicated to development this will absolutely further the development of android.

Yeah man, don't worry about benches. If you want to brag about how high it is just PhotoShop it. It's all about smoothness and real world performance/battery life for me. Just find what setup works best on your phone
Edit: and this goes in the q and a section

Lol okay then guys, so which gingerbread ROM and which kernel for the best efficiency and speed?

david279 said:
Benchmark scores don't matter. I don't even check them anymore. Wether I get a 1400 or 2200 its still gonna dial a number at the same speed. Im not playing call of duty on my phone or anything. I want efficiency.
Click to expand...
Click to collapse
I couldn't agree more, how instant can a phone get? Theres a point where speed wont be relevant anymore and its pretty damn close to it already. In my eyes efficiency is the future, doing more with less is something im looking forward to.
Sent from my Warm TwoPointTwo RLS5 Beta'd out Evo

lexusmike said:
Yeah man, don't worry about benches. If you want to brag about how high it is just PhotoShop it. It's all about smoothness and real world performance/battery life for me. Just find what setup works best on your phone
Edit: and this goes in the q and a section
Click to expand...
Click to collapse
**** man I'm sorry I'm new to this forum.
Mods: Please move to the correct section.

Thread moved to General.

Also keep in mind that the EVO's Snapdragon CPU was never a problem, it's still competitive even with the newer CPUs (with the exception of the upcoming A9's both single and especially dual core). Most of the "hacks" that raise the Quandrant score over 2000 are just that, hacks. They manipulate the other tests (non-CPU specific ones) to raise the score and make you think that you've just achieved some kind of new level of performance when in fact you'll see pretty much no difference.
Over clocking will help a little but like I said the problem isn't the CPU; a lot of the lag you may see on the EVO is because of the GPU. Nobody has figured out out how to overclock the GPU so over clocking the CPU will make no difference with the GPU. There have been some improvements in the drivers and if you're running CM or MIUI, you already have them. Gingerbread slightly improves some of the core graphics in Android so you'll see a boost over pre-Gingerbread Android but I think what we should all be waiting on is for the new Adreno 200 GPU drivers that Google will release when the OTA 2.3 update for the N1 drops. It wont magically make our EVO's into Nexus S' or anything but I wouldn't be surprised to see a noticeable boost in performance.

Oddly enough, I'd rather have the transition animations that come with some of the custom ROMs, even if they take longer. They provide a much more "fluid" experience. I don't like the jarring, speed-driven, animation-free transitions that come with stock ROMs, because they lack polish. As soon as I saw videos of those animations, I was in love. LOL. Seriously though, lag and lack of animations (which consequently actually help hide lag and load times) are the two things I see holding back the polish of Android. Just as an example (not trying start a flame war here, people), look at the animation when going from portrait to landscape in iOS. Then look at Android's lack thereof. THAT is what Android needs-to actually FEEL faster, not necessarily BE faster. So try something like that if you want the phone to feel more fluid instead of just achieving raw benchmark speed. Again, just my opinion (kind of sad that I feel the need to put that disclaimer in every post lately).

Award Tour said:
Also keep in mind that the EVO's Snapdragon CPU was never a problem, it's still competitive even with the newer CPUs (with the exception of the upcoming A9's both single and especially dual core). Most of the "hacks" that raise the Quandrant score over 2000 are just that, hacks. They manipulate the other tests (non-CPU specific ones) to raise the score and make you think that you've just achieved some kind of new level of performance when in fact you'll see pretty much no difference.
Over clocking will help a little but like I said the problem isn't the CPU; a lot of the lag you may see on the EVO is because of the GPU. Nobody has figured out out how to overclock the GPU so over clocking the CPU will make no difference with the GPU. There have been some improvements in the drivers and if you're running CM or MIUI, you already have them. Gingerbread slightly improves some of the core graphics in Android so you'll see a boost over pre-Gingerbread Android but I think what we should all be waiting on is for the new Adreno 200 GPU drivers that Google will release when the OTA 2.3 update for the N1 drops. It wont magically make our EVO's into Nexus S' or anything but I wouldn't be surprised to see a noticeable boost in performance.
Click to expand...
Click to collapse
that is interesting.. thanks for the info.
I hope it does open some more performance and maybe a way to overclock the GPU

Im not playing call of duty on my phone or anything. I want efficiency.[/QUOTE said:
Lmao
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse

[REQUEST] Tegra GPU OC....

Hey everyone...I tell ya, I sure am enjoying all these awesome custom roms and kernels. Great job to all the developers here, putting in the blood, sweat, and tears for the advancement of the community, thank you so much. One feature that I saw in a Xoom build was the GPU overclocked, and while I'm sure it won't interest everyone, and there is probably only little gain to be had from it, I would love to have the option to oc the CPU and the GPU for the highest performance possible...please. Well I think that covers it unless someone else shares my desire to see this feature. Thanks for all your work and consideration XDA and have a great day.

if ur CPU OC than GPU too

Apparently not so on the Motorola Xoom as there are two versions of Tiamat 1.4.4... with and without GPU OC. Tiamat 1.4.4 Full Throttle

cq842000 said:
Apparently not so on the Motorola Xoom as there are two versions of Tiamat 1.4.4... with and without GPU OC. Tiamat 1.4.4 Full Throttle
Click to expand...
Click to collapse
oc-ing the gpu doesnt get you anything... gpu is default 200mhz 2d with 300mhz in 3d and it can be uped to 250mhz 2d and 400mhz 3d but it cant be software controlled and it will eat more power...
and no oc-ing the cpu doesn't oc the gpu, its a separate part of the tegra2 processor

Hey Thor, thanks for joining the conversation. Based on what youve seen so far, how well are the tegra GPU cores being utilized? Suffice to say I've pulled off insane desktop GPU overclocks that showed almost nill gain with drivers that werent mature in which the GPU cores werent being loaded past 50% . I realize that the tegra is a horse of a different color, but isnt it still affected by the specific driver optimizations, hence the THD enhancements? Just out of curiosity as I very much trust your experience. I am still interested in trying it with definitive comparisons to follow...well about as definitive as synthetic benchmarks can be anyway.
I just saw that you have a new beta... Yay. I cant wait to give it a whirl.

I have been over locked for a little while. Max I have done is 1506 but it tends to be slightly unstable. I run 1400 now and haven't had any issues. biggest difference I notice is home screen transitions load fast and don't lag and programs load much quicker. there doesnt seem to be any games that will push the CPU hard so I don't notice much of a difference there.
.

specd_out said:
I have been over locked for a little while. Max I have done is 1506 but it tends to be slightly unstable. I run 1400 now and haven't had any issues. biggest difference I notice is home screen transitions load fast and don't lag and programs load much quicker. there doesnt seem to be any games that will push the CPU hard so I don't notice much of a difference there.
.
Click to expand...
Click to collapse
I've had 1600mhz going strong with no instability, benchmark after benchmark, the only issue I've had is the device shutting down when left alone for too long, but I consider that a useful standard function. Otherwise 1600 performance has been rock solid. I decided to take it upon myself to take this girl apart' clean the CPU off, remove the thermal pad, and apply some as5....though the chip didnt really run very hot to begin with. Now until I have the option to go for 1800mhz, I'd like to see where the max threshold is for cpu/gpu oc.

I have mine overclocked also at 1600.. Runs very stable at this speed and benchmarks not too bad:
http://imageshack.us/photo/my-images/20/device20110712225412.png/
I have had higher speeds, but very unstable...

thor2002ro said:
oc-ing the gpu doesnt get you anything... gpu is default 200mhz 2d with 300mhz in 3d and it can be uped to 250mhz 2d and 400mhz 3d but it cant be software controlled and it will eat more power...
and no oc-ing the cpu doesn't oc the gpu, its a separate part of the tegra2 processor
Click to expand...
Click to collapse
Can only the 3D Clocks be altered without touching 2D? If yes can you make such a version of the ........... that "nobody" knows anything about?

Trinnity66 said:
I have mine overclocked also at 1600.. Runs very stable at this speed and benchmarks not too bad:
http://imageshack.us/photo/my-images/20/device20110712225412.png/
I have had higher speeds, but very unstable...
Click to expand...
Click to collapse
Very nice quadrant score man, I used to score alot higher until I updated to stock 3.1+ updates. It seems like the higher my OS version number gets, the lower my synthetic performance gets overall.

cq842000 said:
I've had 1600mhz going strong with no instability, benchmark after benchmark, the only issue I've had is the device shutting down when left alone for too long, but I consider that a useful standard function. Otherwise 1600 performance has been rock solid. I decided to take it upon myself to take this girl apart' clean the CPU off, remove the thermal pad, and apply some as5....though the chip didnt really run very hot to begin with. Now until I have the option to go for 1800mhz, I'd like to see where the max threshold is for cpu/gpu oc.
Click to expand...
Click to collapse
that's what mine did. it would reboot while sleeping. sometimes it would be 3 or 4 times in an hour.

Trinnity66 said:
I have mine overclocked also at 1600.. Runs very stable at this speed and benchmarks not too bad:
I have had higher speeds, but very unstable...
Click to expand...
Click to collapse
Wow!
Umm, what rom do you guys run for this? I'm on rooted and CWMd stock 3.1 rom. Can't find a OC kernel for it. Only one I can find is for ASUS based roms. I prefer to keep stock rom if it's possible.
ME: Asus A500 Iconia USA wifi only. HC 3.1

nexgenasian said:
Wow!
Umm, what rom do you guys run for this? I'm on rooted and CWMd stock 3.1 rom. Can't find a OC kernel for it. Only one I can find is for ASUS based roms. I prefer to keep stock rom if it's possible.
ME: Asus A500 Iconia USA wifi only. HC 3.1
Click to expand...
Click to collapse
You should try richardtrip's kernel. His kernel is keep updating Very good performance and stability.

thats the kernel i am using o/c 1400 works very well. you can find it in the development thread.

ardatdat said:
You should try richardtrip's kernel. His kernel is keep updating Very good performance and stability.
Click to expand...
Click to collapse
Thanks! Works great. Do you feel the HoneyVillian rom runs faster with the v2.4 Kernel or about the same as stock Acer 3.1 HC rom with v2.4 Kernel?
So far I can keep stable at 1.5 after 2 hours of use. It's also slept for 30 mins and seems ok at that too.
Also what kind of Scaling do you guys use? Ondeman, Interactive? On my phone I use ondemand.

Overclocking My Desire Z=Risky??

So in CM7 there is an option to overclock the Desire Z.
Now my question is if I can do this without having to worry about damaging my phone?
For example, the desire Z has a 800MHZ processor, so will it damage my phone to overclock it to 1000MHZ? Or maybe 1200 MHZ?

whitis said:
So in CM7 there is an option to overclock the Desire Z.
Now my question is if I can do this without having to worry about damaging my phone?
For example, the desire Z has a 800MHZ processor, so will it damage my phone to overclock it to 1000MHZ? Or maybe 1200 MHZ?
Click to expand...
Click to collapse
well it depends if your kernel allows overclocking to that speeds. if it dosent its very risky but if it does support it then its not that risky. for me i have e kernel that goes to 1.7 ghz so i safely clocked it to 1.5 ghz

Sorry, I'm really a noob, but what kernel do I have with CM7?
And where can I get other kernels?

whitis said:
Sorry, I'm really a noob, but what kernel do I have with CM7?
And where can I get other kernels?
Click to expand...
Click to collapse
sorry but i dont sure CM7, im using virtuous unity rom so i wouldnt know. but im sure your using the stock kernel that comes with cm7. just ask someone who has cm7. also there are a wide variety of kernels that you can use. just search them up on google or the xda developer forums

The CM 7 Kernal will allow you to overclock up to 1.5ghz (which for the DZ/G2 seems to be the consensus of a 'safe' overclock)
One thing to remember is that not all processors are created equal. Meaning that although we all have the same processor in our phone, some processors are able to handle overclocking better than others. It also depends on what you use your phone for and how much you need the overclock for what you are doing. I ran my device at 1.2 ghz for a while and now run it at 1ghz as it feels plenty fast to me. When playing some graphic intensive games, a higher overclock may help performance as well.
If you overclock and your phone starts to act up, then dial it down a bit. 1.5ghz is fast as hell but will alter voltage and affect battery life as well. Just play around with and see where you like your CPU speed to be at. But you shouldn't have to worry about damaging the processor by overclocking. If its more than it can handle, you will know quickly and can tone it down.

So just for example if I'm going to use Virtious(I quit because it's lagging on the Desire Z) and install this kernel and overclock my desire z up to 1,500 mhz, virtious should run way smoother, right?

evilcuber said:
well it depends if your kernel allows overclocking to that speeds. if it dosent its very risky but if it does support it then its not that risky. for me i have e kernel that goes to 1.7 ghz so i safely clocked it to 1.5 ghz
Click to expand...
Click to collapse
if your kernel doesn't support overclocking, you can't overclock no matter what... there is nothing "unsafe" about overclocking without an overclocking kernel because it cannot be done.
OP: cyanogen has its own overclocking kernel (with capability up to 1516mhz) built-in. as far as safety, it depends on your device, but the most common worst-case scenario is random restarting issues or waking issues.
on CM7, with a launcher other than the bundled ADW launcher which is choppy and slow no matter how high you're clocked, you should be able to have a smooth experience at stock speeds. I am clocked at between 1017 and 1209mhz at any given point as I have been since January and I haven't ever experienced wake or random reboot issues. YMMV but I think the general consensus for the Vision is that a mild overclock is very safe.

HELP!
I overclocked my DZ, but didn't really notice any difference, since CM7 is pretty smooth without overclocking, but know suddenly my device begins to lag very very bad. I put the CPU limit back to 245MHZ to 806MHZ but it keeps lagging:-(

whitis said:
HELP!
I overclocked my DZ, but didn't really notice any difference, since CM7 is pretty smooth without overclocking, but know suddenly my device begins to lag very very bad. I put the CPU limit back to 245MHZ to 806MHZ but it keeps lagging:-(
Click to expand...
Click to collapse
which governor are you using? which launcher? have you rebooted?

HTC Titans CPU versus HTC Desire HD CPU (MSM8255)

Hello everyone!
I've been looking on the web for some time now about the new HTC Titans CPU,
clocked at 1.5GHz, named as Scorpion MSM8255 (same as ours (DHDs CPU)).
What do you guys think about it? Since our MSM8255 can "officialy" only hit 1GHz,
but now HTCs new MSM8255 can get it to 1.5GHz?!
I've searched the wiki also and i cannot find any differences.
Oh wait, is it that T at the end maybe? Just found it now.
HTC Titan: MSM8255T
Okay, so anyone know more about this? Feel free to comment

It's the same chipset. HTC did the same on the Flyer. They just OCed the cpu to 1.5 GHz since the cpu can handle it without problems.
Sent from my Desire HD using Tapatalk

How easy is it to actually oc the dhd cpu and is it really wise?
Sent from my HTC Desire HD using xda premium

A fellow Bristolian! Hi!
How easy? Very. 1.3GHz is achievable on the DHD with stock volts (1.1V). Wise? Yeah, anything up to around 1.2V is sensible, and safe is far beyond that.
To be honest, nobody will need to go past 1.3GHz, virtually all ROMs run smoothly at that clock.

Haha hey nice surprise lol
Oh sounds good. Pretty new to this only just rooted and flashed custom ROM the other day. Wasn't sure if I should OC or not tho. Guessing it's going to reduce an already poor battery life haha
Sent from my HTC Desire HD using xda premium

affinity121 said:
How easy is it to actually oc the dhd cpu and is it really wise?
Sent from my HTC Desire HD using xda premium
Click to expand...
Click to collapse
I've had mine at 2GHz. I clocked it down to 1,3GHz after 10 minutes since it got REALLY hot. But it managed to run just fine at that speed.

affinity121 said:
Haha hey nice surprise lol
Oh sounds good. Pretty new to this only just rooted and flashed custom ROM the other day. Wasn't sure if I should OC or not tho. Guessing it's going to reduce an already poor battery life haha
Sent from my HTC Desire HD using xda premium
Click to expand...
Click to collapse
Well, all of the kernels undervolt as well. Almost all of them run the processor at 1.2GHz at stock voltage. So overclocking shouldn't shorten battery life. Also, remember that many of the ROMs have andrev or virtuous OC daemons installed, so they will be underclocked to minimum speed most of the time. So either way, battery life and performance will be improved.
As for overclocking to 2GHz, while it is possible, I'd very strongly suggest you don't do so.
But it does prove that firstly, the MSM8255 is very overclockable, unlike the larger processed chip in the Desire (which I think will really go as far as 1.2GHz only, correct me if I'm wrong...). The Flyer's processor is exactly the same, just selected (a process called binning) because it is "capable" of running at that speed at the required, and desired voltages with the required stability that the manufacturer (Qualcomm) wants.

lambomanx1 said:
Well, all of the kernels undervolt as well. Almost all of them run the processor at 1.2GHz at stock voltage. So overclocking shouldn't shorten battery life. Also, remember that many of the ROMs have andrev or virtuous OC daemons installed, so they will be underclocked to minimum speed most of the time. So either way, battery life and performance will be improved.
As for overclocking to 2GHz, while it is possible, I'd very strongly suggest you don't do so.
Click to expand...
Click to collapse
Thanks for the reply. I'm currently using rcmix runnymede ROM and its not oc'd. Would a OC of 1.3 be wise on stock voltages?
Sent from my HTC Desire HD using xda premium

1.3 might be pushing it. Mine needs 1.125V to be stable. I'd suggest that you probably do the same just in case, or even better 1.150.
The safest thing to do is take a look at the NCTeam kernel voltages, and use those (use IncrediControl from the Market to change voltages). They should work for virtually everybody. 1.3GHz is the speed I needed on Sense ROMs to be very smooth, you might find it is less though.

The desire hd doesnt actually overheat much @ 1.3ghz (I use that + Performance governor when playing some games), so the CPU can probably be overclocked quite alot without any problems
Other phones overheat quite a bit @ stock speeds...

Mine is set to 1,6GHz and it can handle 3d gaming for hours with the case only getting a bit warm. I wrote in a different thread that WP7 is getting an update and it will be able to run on DHD hardware. Maybe some devs will be interested in porting it to DHD then. It would be nice to dual boot Android and WP7. I can almost see all iPhone users faces.
Sent from my Desire HD using XDA App

314 said:
The desire hd doesnt actually overheat much @ 1.3ghz (I use that + Performance governor when playing some games), so the CPU can probably be overclocked quite alot without any problems
Other phones overheat quite a bit @ stock speeds...
Click to expand...
Click to collapse
Just to make sure I was clear, I meant that 1.3GHz could be pushing it on stock voltage, not that it could be pushing the limits of the chipset for speed. I think everyone got that, and knows that, but was just making sure.
As for heat, my phone didn't even heat up at 1.3GHz. You can push very far with no problems.

haerigrek said:
Mine is set to 1,6GHz and it can handle 3d gaming for hours with the case only getting a bit warm. I wrote in a different thread that WP7 is getting an update and it will be able to run on DHD hardware. Maybe some devs will be interested in porting it to DHD then. It would be nice to dual boot Android and WP7. I can almost see all iPhone users faces.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Don't forget that we need a wp7 bootloader. The android one can't handle wp7. Furthermore we probably have to repartition our internal memory (or sdcard if you want to run it from there) since wp7 uses other partitions than android (not sure about that, but i guess we have to.)
Sent out of my Free-Candy-Van. Your kids are safe in there. Trust me.

Why do YOU Overclock (or refuse to) on the Atrix?

After the release of Clemsyn's 1.6 GHz Kernel for CM7 based ROMs last night, I immediately switched to it just to see.
But before that I was running Faux123 1.3 GHz.
I'm keeping the Clemsyn kernel for now, simply because I can. My phone can run it with little difficulty thus far and I have a profile to lower the max freq when the CPU gets to a certain temperature. I think I went with about 65 Celsisus.
Before I switched back to CM7 (or rather Neutrino) I was using Wet Dream. I OCed to 1.45 then in attempt to compensate for only half decent webtop performance.
But now I really only do it because I can. Whenever possible, my phone is on the lapdock since I like to HDMI mirror. Battery is not a concern since the lapdock charges the phone and I pretty much always keep the lapdock charger on hand in my bag.
I just thought it would be an interesting subject for the community to discuss as I'm sure it's something that a number of us haven't even thought of and I bet a good number of us fall into the because I can or bragging rights category.
Specific instances of problems OCing helped with in x app or y app might make someone else want to OC whereas someone who doesn't OC might persuade a user like myself to drop it for amazing battery ETC.
Sent from my MB860 using Tapatalk

Why I DO OC.
Right now I have my Atrix OC'ed at 1.45. I'm currently running Alien ROM Build #4.
The CPU has never gotten past ~55º C.
I also have 2 profiles set
1 for Screen off - 800 MHz max.
1 for Battery< 10% -216 MHz max.
This paired with Alien ROM and LP has left me with a buttery smooth experience.
Is the 1.6 OC kernel worth giving a shot? Or does it make the CPU run excessively hot?
EDIT: I didn't really address battery life. I don't notice a huge decrease in battery life, I'm a pretty heavy user- SMS, Web, Video streaming, Facebook, Twitter. Over all OC'ing is definitely worth it to me.

I like to keep mine overclocked because it seems snapier. I use faux 1.45 and its great. Ive noticed clem's likes to make my phone very hot when running video or games and has actually shut my phone down due to heat. If I run clems I like to drop the overclock with setcpu to around 1.3 so it doesnt shut down but seems to get way hotter than faux's. Anything over 1.5 is just going to cause damage to peoples phones and IMO it should not be used so lightly.

I'm OC'd to 1.45ghz I do it for performance and those random times I need to benchmark I want to try 1.5-6 but I can't seem to get them to boot with the ICS mod2 cm7 so till cm9 or neutrino ill just float about with what I have
Sent from my Atrix-4G, stock 2.3.4 (rooted)

No need for 1.6 IMO.
1.3 is plenty for the Atrix. Even Faux 1.0 is fine. Its a phone, not a PC.
Sent from my HTC Inspire 4G using XDA App

I dunno...my webtop configuration may want to take exception to that statement

troycarpenter said:
I dunno...my webtop configuration may want to take exception to that statement
Click to expand...
Click to collapse
+ 1
Sent from my Atrix 4G using Tapatalk

i honestly haven't been able to really tell a difference between 1.0 and 1.3GHz in most of my applications. it definitely doesn't help with system slowdown due to live wallpapers, which is a disappointment.

troycarpenter said:
I dunno...my webtop configuration may want to take exception to that statement
Click to expand...
Click to collapse
Haha, I was in that boat before I switched to HDMI mirroring coupled with VNC or Splashtop (when applicable) from experience, I can tell why Webtop users want OC. You can turn your phone into such a useful computer, and then it falls flat on its face because the inner-workings aren't streamlined. The extra power DOES help in that situation.
But in my actual experience, I haven't seen many realworld benefits past 1.2.
Especially since 1.6 kept eventually shutting down on me after about an hour (assuming there is the same issue as in Clemsyn 1.5, setting your max to a lower frequency than 1.6 won't stick so my temperature profile wouldn't actually work)
My "because I can" mindset is going to leave me stuck on 1.45 though most likely. I keep it maxed at 1.2(or is it 1.1? I'm not using the kernel right now) and then have a profile to ramp it up to 1.45 when it's on the charger (aka my lapdock)
I don't think it is quite the same for Blur based ROMs, but on CM7 1.0 seems perfectly adequate for the Atrix. Even at it's stock speed, it is snappy.
Sent from my MB860 using Tapatalk

I dont overclock. I used to be at 1.3ghz, but I didnt see a big enough difference to keep it. At least on CM7, the Atrix is plenty fast on stock speed.

I overclock, but I wait for thoroughly tested kernels before doing so. Right now I'm with faux's v023r @ 1.3 Ghz. I'll try Clemsyn's after its second or third "redesign" or bugfix.

I stick to optimal battery life kernels rather than performance (faux 123 0.2.3 being the one I'm currently on and most likely will be for the foreseeable future)
Also I can't imagine performance possibly getting any quicker or running programs any faster than they already are on the atrix.

Honestly, I never understood why people oc their phone, especially the Atrix. I mean the phone is already fast being that it is 1Ghz dual core. Plus from what I have seen, the Atrix overheats like crazy with the stock frequency so why would you want to increase that even more, so it explodes? I use my phone to mostly play 3D games and I have never encountered any lag or low fps whenever I play games.

Atrix_Owner said:
Honestly, I never understood why people oc their phone, especially the Atrix. I mean the phone is already fast being that it is 1Ghz dual core. Plus from what I have seen, the Atrix overheats like crazy with the stock frequency so why would you want to increase that even more, so it explodes? I use my phone to mostly play 3D games and I have never encountered any lag or low fps whenever I play games.
Click to expand...
Click to collapse
Quote for truth
The Atrix is plenty fast already. I can understand if you OC a HTC Magic, or a Hero; but there's no real need to do so on the Atrix.

Idk I see a difference on any launcher when I flip through pages and through apps. 1.3 or 1.45. But I def notice the difference in snappyness.
Sent from my MB860 using xda premium

95% of the time I overclock I do it for getting awesome benchmark scores that I can admire. 5% of the time I do it when playing 3D games like Fruit Ninja, It seems a lot smoother to me. But I hardly ever do it because it sucks the battery down so fast, so usually I'm at 1ghz. Also it's just kind of cool to see the the potential the phone has when overclocking.

i used faux's kernel to overclock to 1.3 for a few months but i didnt really see any difference except when i run quadrant or how my phone got hotter than stock when under load. another thing that annoyed me with faux's kernel was constantly losing widgets on reboot. i use two batteries so i reboot pretty often.

I used faux 23r 1.4GHz with setCPU profiles.
Profiles clamped speed to 1ghz at cpu temp of 50degc and 800mhz at 60degc.
Most noticeable difference was in k9 mail, indexing and searching were slightly improved.
I ran it so I would get a short boost if the cpu was cold.
Matthew
Sent from my MB860 using XDA App

Hey
On my old and feeble Hero I had to OC, if I wanted it to run fine, however I never felt the need to OC my Atrix. it has so much juice in it without OC, making it useless to squeeze the battery for the extra 0.2-0.5 GHz. Moreover, since we have no real ICS, our CPU runs freely and waste energy for nothing, so OC it will just make it run ever faster for nothing (In Hebrew there is a saying- running full throttle on neutral ).
I used to run Faux123 1.0Ghz kernel just to UV the device, but since I flashed weekly 6 I use the stock kernel, and it runs great, no overheating, and extremely stable (What cannot be said on UV kernels...)

The only time i oc is when using webtop, that extra speed makes a difference. The rest of the its running at 1ghz and seems plenty
Sent from my MB860 using xda premium