Overclocking Aria

[Ryan Roland]

Is anyone using CPU set or set CPU to overclock your phone? if so what speeds and how are the results. Or what program do you use if you have something else. You have to be rooted if I'm not mistaken to download or use these programs

Sent from my CM6.1 Aria using Tapatalk

 

[ls377]

I use Overclock Widget from the market. It's more reliable than SetCPU to me. I set mine to 806 most of the time, but it really depends on how your specific phone handles it.

 

[Ryan Roland]

So I see the different speeds. What will happenn if I go too high? will it just freeze my phone it will it break it permanently? I've downloaded it and see it going back and forth but I've never done any overclocking on any computers or phones so I'm very noobish with this

Thanks for your help

Sent from my CM6.1 Aria using Tapatalk

 

[ls377]

So I see the different speeds. What will happenn if I go too high? will it just freeze my phone it will it break it permanently? I've downloaded it and see it going back and forth but I've never done any overclocking on any computers or phones so I'm very noobish with this

Thanks for your help

Sent from my CM6.1 Aria using Tapatalk

At the speeds that we have the ability to right now, you won't fry your phone. The biggest risk is shortening the life of your phone, or making it freeze up. Just keep an eye on the battery temp (since we don't have a CPU monitor), and if your phone freezes up, bump it down. Anything up to 806 shouldn't give you any problems, but don't go to high if you don't feel comfortable with it.

 

[Droidiculous]

I recently OC'd my Aria. I have had it run at 900mhz. It froze up when I was fooling around with turning different switches on ( wifi, bluetooth, GPS, Data, etc). Other than that the phone is quick! I benchmarked it using Quadrant Standard App. According to the results the OC'd Aria was tied with a HTC Evo w/ Froyo. My score was 1189!

I used OverclockWidget


Phone is running CM 6.0.2.1 Liberty
Kernel 2.6.29.6- cyanogen mod jp@eddie #1

 

[ls377]

I recently OC'd my Aria. I have had it run at 900mhz. It froze up when I was fooling around with turning different switches on ( wifi, bluetooth, GPS, Data, etc). Other than that the phone is quick! I benchmarked it using Quadrant Standard App. According to the results the OC'd Aria was tied with a HTC Evo w/ Froyo. My score was 1189!

I used OverclockWidget


Phone is running CM 6.0.2.1 Liberty
Kernel 2.6.29.6- cyanogen mod jp@eddie #1

900? Ouch, didn't think there was a way to do that yet.

 

[maevro#CB]

806 is the recommended max.

What are you each using to overclock?

I have been keeping it at 700 and 245.

 

[Droidiculous]

Okay so I take back my statement about 900mhz. That was before I downloaded temp+CPU v2 app. The app tells you your literal clock speed. The Aria's max speed is 864mhz.

Maervo , I originally used Overclock widget from the market. However I broke down and bought SetCPU for 1.99. It sets it so my Aria normally runs at 245mhz and only on demand will it go to 864mhz.

For overclocking to work you have to have a kernel that supports it. I believe the latest version Cyanogen for Aria has this support.

I am currently running version CyanogenMod-6.1.0-Liberty

Kernel version 2.6.32.17-cyanogenmod aria@giovanni #69

The phone is very stable and most of all is very quick.

 

[wantabe]

"Is anyone using CPU set or set CPU to overclock your phone? if so what speeds and how are the results."

First of all, after lurking (too long) and absorbing as much as possible before I moved up from windows mobile, I want to thank everyone on this forum. I'm going to try and contribute something back and share what little I've learned. After trying to do the AT&T Froyo update and not succeeding I decided to root my phone, flash a new rom and see what I could get by overclocking it. Basically got the phone for free so not a huge deal if I screwed up. If you do overclock, before you decide to go over 806Mhz you really need to do a nandroid backup. It is very important to not skip that step. There is a good chance it will freeze up or get stuck in a loop trying to boot if you go to far for your phone. I'm talking from personal experience! My phone will run at any step above 806Mhz except 864Mhz. At 864 endless loop trying to boot. Without a backup I would have been stuck. Had to pull the battery, replace, hold volume down and hit the power button. That boots you into the rom manager and you can do a restore. Only planned to do a benchmark at 864Mhz and the phone decided otherwise. On a daily basis I have my phone set at 768Mhz using SetCpu. Results will vary from phone to phone for numerous reasons. I'm running Liberated 2.2.2 Froyo and you will see a performance increase "just" by updating to Froyo if you haven't done so already. I didn't benchmark my phone on 2.1 but from what I've seen an average benchmark will be around 400 using Quadrant. These are my benchmarks, no profiles set in SetCpu and default settings in the advanced tab using ondemand. Minimum frequency for all runs set at 245Mhz. The numbers are an average from 4 runs at each step.
Quadrant Standard Benchmarks:
600Mhz - 770
768Mhz - 928
787Mhz - 924
806Mhz - 991
The numbers will vary depending on what's running in the background, apps installed, email updating, so forth. I've seen quite a bit over 1000 for 806Mhz but that's the average for this test.
Will list profiles I use shortly.

 

[wantabe]

Part 2;

For those that might be interested, there is a very comprehensive and very long thread about overclocking and primarily the use of SetCpu over at droidforums (OverClocking 101 - Droid Forum - Verizon Droid & the Motorola Droid Forum). The OP is obviously very knowledgeable and has spent a ton of time testing. Check out the first page and you'll see what I'm talking about.

From what I've read and seen with my phone, using SetCpu has the potential of saving a little battery time, reducing heat and still let you use the overclocking ability as much and when YOU choose to use it. It's all a matter of setting the parameters in the different profiles to change how much overclocking is done when certain conditions are met. One profile is for the screen off. If I am for example overclocked to 806Mhz, I don't see the need for the cpu to ramp up to that speed when I'm not using it. The screen off profile gives us the ability to set the minimum and maximum Mhz for that profile. My phone is set to 245Mhz min - 480Mhz max when the screen is off. Even though you can use the ondemand scaling it's surprising how much the cpu will ramp up just sitting there. You can see this in the info tab of setcpu, it shows the current cpu frequency, load average and time in state. Time in state shows how much time spent in each step of the kernel. The kernel in the rom I'm using has 10 steps; 245Mhz, 400Mhz, 480Mhz, 600, 768, 787, 806, 825, 844, 864. These are the different steps I can use when setting the min-max on the main page and in the different profiles. From what I've been able to find out the minimum frequency of the kernel in the stock AT&T Froyo update for the Aria is 480Mhz. Being able to underclock when the screen is off would (I think) save the battery to some degree. As long as everything updates and there are no issues waking up. I am by the way experimenting with bumping up the min setting (screen off) from 245Mhz to 400Mhz and/or raising the max to 600Mhz to lower the load average when the screen is off . As recommended by the OP at droidforums, need to shoot for less than 2 in the load average with the screen off (screen off for 6 hrs or longer). Not that I'm having any issues with 245-480. Just like my Dodge Hemi, can't leave well enough alone, got to bleed every last bit of performance and mileage out of it.
Wrap up to follow.

 

[wantabe]

My current configuration for SetCpu ON HTC Aria.

Main Tab
Max: 768 Min: 245
Scaling: ondemand

Profiles Tab
Screen Off 480 max 245 min
Priority: 100 ondemand

Temp>48.6 C 480 max 245 min
Priority: 95 ondemand

Temp>44.7 C 600 max 245 min
Priority: 90 ondemand

Charging 600 max 245 min
Priority: 85 ondemand

Battery<31% 600 max 245 min
Priority: 75 ondemand

Advanced Tab
Sampling Rate: 50000
Up Threshold: 95
Ignore Nice Load: 0
Powersave Bias: 0

1. 
   
   ​

 

[wantabe]

A few pointers using SetCpu.
1. It's recommended to use the same scaling on the main page and in the profiles. Ondemand, conservative, performance, whatever. If you mix them up it messes with the settings in the advanced tab.
2. The battery profile works in steps of 10. If you want 30% use 31, for 40% use 41, so forth.

 

[wantabe]

Updated configuration for SetCpu ON HTC Aria.

Main Tab
Max: 787 Min: 400
Scaling: ondemand

Profiles Tab
Screen Off 600 max 245 min
Priority: 100 ondemand

Temp>46.0 C 600 max 245 min
Priority: 95 ondemand

Charging 600 max 400 min
Priority: 85 ondemand

Battery<31% 600 max 400 min
Priority: 75 ondemand

Advanced Tab
Sampling Rate: 32000
Up Threshold: 80
Ignore Nice Load: 0
Powersave Bias: 0

Played around with the screen off profile a little trying to get the load average below 2 and never was able to get there. Going to a faster sampling rate seemed to help as much as trying to bump up the min-max in the screen off profile. No issues updating or waking up when the screen is off and the battery life has been great, sooo not going to worry about it! Averaging 10-22 hrs of battery life with moderate to very heavy use. Usually have over 30% when I plug it in at night (10-11pm).
On my phone maybe 99% of the time no lag, very responsive and fast. Bumping up the min Mhz on the main page along with a faster sampling rate eliminated the rare occurrence of any lag.
I tell you what, the next phone I get has some big shoes to fill when it comes to matching the performance of this little beast.
MODIFIED 3/23/2011
Bumped up the max Mhz to 787 from 768. Bumped up the min Mhz for the charging and battery profiles to 400 from 245 for both. I can feel the difference when dropping from the main profile and bumping up the min Mhz helps. Definitely spoiled!!! Changed the up threshold from 95 to 80. Don't see much of a change in battery life, if I do I'll bump the max back down to 768. That's the great thing about SetCpu, the ability to find out what works best for YOU.

 

[wantabe]

Final configuration for SetCpu ON HTC Aria.

Main Tab
Max: 768 Min: 245
Scaling: ondemand

Profiles Tab
Screen Off 600 max 245 min
Priority: 100 ondemand

Temp>46.0 C 600 max 245 min
Priority: 95 ondemand

Charging 600 max 245 min
Priority: 85 ondemand

Battery<31% 600 max 400 min
Priority: 75 ondemand

Advanced Tab
Sampling Rate: 32000
Up Threshold: 50
Ignore Nice Load: 0
Powersave Bias: 5

After trying different configurations I've come to the conclusion that the above settings are a good compromise between performance and battery life. With average use I can easily go 2 full days on the battery. At home I do switch over to Edge and use wifi if I need to go online. At home I get 5 bars on Edge, 1-3 bars on 3G depending on if I move, blink an eye or whatever. With the screen off the phone uses less than 1 percent of the battery per hour. Probably the biggest change would be the Powersave Bias which prevents the cpu from jumping to the max freq for any little thing but if the user does something it will still ramp up to the full max cpu freq. For example when the screen is on anything going on in the background will generally make the cpu go to 600Mhz but if I do something it will go up to 768Mhz. Same thing with the screen off, it will generally ramp up to 480Mhz and much less often go up to 600Mhz. Everything updates as it should, still very fast, rarely any lag. I also lowered the max freq because on my phone 787Mhz and 768Mhz both benchmark very close to the same numbers. This is an incredible little phone! Recently played with my nephews' T-Mo G2x and that beast has more lag than my phone.