Database Users

What is the Max Overclock?

Hey guys whats the max overclock that the Aria can be set to? I had CM6 on mine and had the overclock widget from the market and the max that the sliders went to was 600... But I have Liberty FR008 on it now and i still have the overclock widget but the max that the sliders goes to now is 864... I tried overclocking to 864 but it froze and something went wrong so i had to flash a backup i made. My overclock options right now are 245, 400, 480, 600, 768, 787, 806, 825, 844, & 864... Has anyone tried to over clock the Aria past 600? and did you have any problems with it? Thanks for any help.
-Cpl. T. King

I dont think the cm6 kernal allows for over clocking. I have the latest liberated rom and overclocked to 806 which is the recomended max setting by the dev.
Sent from my HTC Liberty using XDA App

Use the search button. The safe zone is 806.
Sent from my HTC Liberty using XDA App

andrew.cambridge said:
I dont think the cm6 kernal allows for over clocking. I have the latest liberated rom and overclocked to 806 which is the recomended max setting by the dev.
Sent from my HTC Liberty using XDA App
Click to expand...
Click to collapse
The CM 6.1 kernel most certainly does support over-clocking. The CM 6.1 kernel was used as the basis for the Liberated FR008 kernel.

Maybe I was thinking about 6.0. Whatever one I had, I could only over clock to 600.
Sent from my HTC Liberty using XDA App

6.0 didn't allow overclocking, 6.1.1 does though. I overclock my Aria to 806mHz and underclock it to the lowest setting when the phone's screen is off so I don't tire out the processor. 806mHz is really good, it puts the phone at the level of the G2 or the Shift 4G...and because I usually run Edge w/3G when downloading, WiFi if available, my battery is really good. Probably about 14 hours of normal (good) usage.
I wouldn't overclock it higher, you risk burning the processor out.

I'm OCd to 825 on-demand and the phone runs very nicely. 245 when screen off

825 is not recommended I don't think. 806 seems to be the sweet spot.

brswattt said:
825 is not recommended I don't think. 806 seems to be the sweet spot.
Click to expand...
Click to collapse
Says who? It's dependent on the quality of the processor. Some can do it, some can't.

kaschenberg said:
Says who? It's dependent on the quality of the processor. Some can do it, some can't.
Click to expand...
Click to collapse
Attn1 said he doesn't recommend overclocking over 806, because you might fry the cpu
Sent from my HTC Liberty using XDA App

I forgot attn1 was a engineer for HTC. 806mHz is the sweet spot, I've been running it for weeks OD with Screen off at 206 and it doesn't overheat & good battery life.

tribestros said:
I forgot attn1 was a engineer for HTC. 806mHz is the sweet spot, I've been running it for weeks OD with Screen off at 206 and it doesn't overheat & good battery life.
Click to expand...
Click to collapse
Suit yourself. Just saying 806 is the sweet spot for most people around here. I've gotten force closes and reboots at 825. We don't need your attitude

Then it seems like your particular phone can't handle 825. I suggest people try it on both. every phone is different. Just don't be stupid about it. When using the phone as a gps, under clock it. under clock when screen off. and over clock on demand and I'm fine on 825. never seen any issue.

"Suit yourself." I think that was the point of his post. His phone and usage of it OCd at 825 is good for him. He was just stating an answer to the OP. No reason to go around telling him he's wrong..
Anyways, not trying to start a OC war... because that would be ridiculous (-ly funny I might add).
As for myself, when I did OC my processor, 825 didn't effect my phone's performance, but it did make it extremely hot after a bit of use. So it's up to your phone and how you want to handle your phone. I don't really need the OC anymore though; I just stick with 600 (;

Sorry for the nooby question, but whats this even do? Besides making it faster I assume?

vicmora5 said:
Sorry for the nooby question, but whats this even do? Besides making it faster I assume?
Click to expand...
Click to collapse
That's basically all it's for. d:
You get more processing power.

brswattt said:
That's basically all it's for. d:
You get more processing power.
Click to expand...
Click to collapse
Thanks. Is it really necessary? What are the downsides of doing this. Sorry I'm just trying to learn /:
Sent from my Liberty using XDA App

vicmora5 said:
Thanks. Is it really necessary? What are the downsides of doing this. Sorry I'm just trying to learn /:
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
Downsides are less battery life (may be a lot or not) and not going as fast as it would be if you were OCd. It may also heat up more.

vicmora5 said:
Thanks. Is it really necessary? What are the downsides of doing this. Sorry I'm just trying to learn /:
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
Overclocking is not necessary at all. We just recently became able to overclock. If you are satisfied with the speed/fluidity of your phone, then there is no need to overclock. The downsides would be less battery life (cpu running faster), and if you push your phone too hard (overclock stupidly), you run the risk of burning out your cpu. your phone should not be getting hot.

vicmora5 said:
Thanks. Is it really necessary? What are the downsides of doing this. Sorry I'm just trying to learn /:
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
It's not necessary. It's pretty damn cool to make the little Aria have a processor as fast as the one in the G2 though.

[Q] Freezing once passing 1.51ghz

I've tried both CM7 and Evervolv roms and they both freeze once I go past 1.51ghz. Anyone know a reason for this?
Using cwm3 or 2.5:
When I flash a rom I wipe cache, delvik, data and battery.
Then i install zip from sdcard > choose zip from sdcard. I do this for roms, kernals, and gapps. I first flash rom then gapps then kernal.
Ive also tried setting permissions with cwm.
I am currently using CM7 with the gb kernal, and SetCPU. Funny thing is that setcpu sometimes has the bar thing set to 1.51 but then the max says 800mhz. I have to move the bar around for it to set correctly.

Some phones aren't going to be able to clock that high, no matter what what you do. The Hero CDMA was like this as well. Some couldn't go over 691 mhz.
Try and remember that this phone is marketed at 800 mhz, so making it all the way to 1.8 could be considered a pipe dream by some. Although I've personally seen a G2 make it all the way to 2.1 ghz.
Sent from my PG06100
Edit: As far as setcpu goes, I myself have had that same issue with the Shift and the Heroc. I am personally using the nofrills app. Best I've seen. You can find it in the Hero CDMA forum, first post of the aospCmod thread by user aosp.

What governor are you using under setcpu(assuming you are using setcpu)? Try using "on demand" if you haven't already tried that.
powered by the tears of a million orphaned alpacas...

smoothtaste said:
Some phones aren't going to be able to clock that high, no matter what what you do. The Hero CDMA was like this as well. Some couldn't go over 691 mhz.
Try and remember that this phone is marketed at 800 mhz, so making it all the way to 1.8 could be considered a pipe dream by some. Although I've personally seen a G2 make it all the way to 2.1 ghz.
Sent from my PG06100
Edit: As far as setcpu goes, I myself have had that same issue with the Shift and the Heroc. I am personally using the nofrills app. Best I've seen. You can find it in the Hero CDMA forum, first post of the aospCmod thread by user aosp.
Click to expand...
Click to collapse
That would make since! Dam...i got screwed haha.
oboroninja said:
What governor are you using under setcpu(assuming you are using setcpu)? Try using "on demand" if you haven't already tried that.
powered by the tears of a million orphaned alpacas...
Click to expand...
Click to collapse
ill try ondemand. Usually if I go that high its for benchmark purposes.

depsidynamic said:
That would make since! Dam...i got screwed haha.
Click to expand...
Click to collapse
You didn't get screwed. Your phone works as advertised at 800Mhz. You're nearly doubling your speed at 1.5Ghz....

depsidynamic said:
That would make since! Dam...i got screwed haha.
ill try ondemand. Usually if I go that high its for benchmark purposes.
Click to expand...
Click to collapse
I also agree that you didn't get screwed at all. I posted that app in the Themes and Apps section, FYI!
Sent from my PG06100

I was joking guys!

CM7 Kernel Recommendations?

Hello all!
Just upgraded my wife from the MyTouch 3G Slide to the G2 as she has to have a keyboard and we were on our 5th replacement Slide. So, as she is not the geek that I am, she will not be constantly flashing new ROMs and such. However, I am going to at least install the latest CM and I am looking for kernel suggestions. I already have root, s-off, new hboot, and all that, I'm just waiting for CM7 to finish downloading.
I started using Android with the G1 and constantly updating Radios, as well as ROMs and I currently use a Samsung Vibrant running a TeamWhiskey ROM. It's stable as anything, I like the theme, and CM7 still has some broken stuff on the Vibrant. I'm glad to see that Eugene recently picked up a G2 as he made some bad ass kernels and ROMs for the Vibrant.
So, let's here those kernel recommendations and why you recommend them.
Thanks!

Well am currently using mexdroidmod and their kernel is pretty awesome because its fast and stable. My best advice is to test the diffrent kernel and read through the tread, see what people say about it. All the kernels I have tried are all awesome so you should try them
Sent from my HTC Vision using XDA Premium App

pershoot's kernel. great batt life and OCing

Umaro's kernel has been rock solid for me and has tons of features as well. You can OC all the way to 1.9 Ghz if you so please and it has smartass.

well considering your wife isn't much of a techie.. i say you should go with pershoots kernel because he's always releasing updates and i've never had a problem with any of them. the battery life is excellent if you use the right radio (.17 and .30 have been good to me), but you need to experiment with this though. the phone runs beautifully, just make sure you use superwipe+ to format/wipe so you don't end up with gps issues like many people have had, good luck!

I've run umaro, eugene, pershoot, flippy, pyro, etc etc... aaand I've decided that the provided kernel is pretty much good to go. yeah, there are some little trinkety things with a few of the above kernels that the standard CM7 kernel doesn't support... but honestly, they're worthless to a user who just wants to turn the phone on and have it work.
set her up with the stock kernel @ 245-1017 (I haven't found a reason yet to ditch the ondemand governor, it seems to work best with CM7) and a vanilla gingerbread launcher and she'll be blown away.. that's my $.02

Like said above, CM kernel is great. I've tried most or even all available kernels for CM and finaly decided to stick with original one. It's stable and supports OC (up to 1.5GHz) "out of box", so really, I see no single reason to use the other ones.
Sent from my HTC Vision using XDA App

AllWin said:
Like said above, CM kernel is great. I've tried most or even all available kernels for CM and finaly decided to stick with original one. It's stable and supports OC (up to 1.5GHz) "out of box", so really, I see no single reason to use the other ones.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
I'm also thinking about changing the kernal, but only for smartass. Does smartass offer that much of an increase on battery life or anything else? Also, when you OC, do you use SetCPU or just CyanogenMod Settings?

slapshot30 said:
I'm also thinking about changing the kernal, but only for smartass. Does smartass offer that much of an increase on battery life or anything else? Also, when you OC, do you use SetCPU or just CyanogenMod Settings?
Click to expand...
Click to collapse
not at all pooping on any of the guys who swear by smartass/other governors, but the change in battery life is almost unnoticable for me.. the change in performance however can be pretty apparent.
here's my problem with "battery saving" governors:
in order to save battery, these governors are supposed to be more intelligent about which frequencies they select once a task is called... well, that's all well and dandy, but the problem is that the majority of battery-hogging apps (ie streaming music/video, gaming, browsing for a long time, being on the phone, etc) are still going to be battery hogs with or without a fancy governor. the governor isn't capable of making an app that needs a lot of processing power run well at a lower frequency, it can only try to be more selective about which frequencies it uses in order to attempt to save battery life.
additionally, most people use their phones like this: phone is idle (ie screen off), and a call arrives. call ends, phone is back to idle. texting a few people, back to idle. playing a game for 15 minutes, back to idle.
is it really logical to assume that these short bursts of activity are going to benefit at all from a fancy shmancy governor? I doubt it.
I still swear by ondemand or interactive (both work well for me) thru built-in settings if possible (ie cyanogen performance settings). second choice would be setcpu with no profiles (unless you're overclocking heavily, then you should at least have a temp warning profile). at this point, screen-off profiles don't do a damn bit of good, because pretty much every kernel we have for the vision is going to scale down during inactivity.

SetCPU no longer underclocking at low usage?

I have moved from CM7 to Hombase 5.4, and found that setcpu no longer seems to do anything. on CM7 it worked as i had hoped, underclocking the phone when i was doing low intensity stuff like texting, and pushing it up to full power for videos etc. now it does nothing but tell me core temps, which are always high as its always running at 1Ghz.
Can anyone explain how to get it back to underclocking?
Many Thanks

Try a different kernel.
Sent from my CM860

ishamm said:
I have moved from CM7 to Hombase 5.4, and found that setcpu no longer seems to do anything. on CM7 it worked as i had hoped, underclocking the phone when i was doing low intensity stuff like texting, and pushing it up to full power for videos etc. now it does nothing but tell me core temps, which are always high as its always running at 1Ghz.
Can anyone explain how to get it back to underclocking?
Many Thanks
Click to expand...
Click to collapse
This is a known issue with the OC faux kernel. I was running into the same problem with his enhanced stock kernel after using webtop. After reflashing the enhanced stock 0.2.0 it would still get stuck at max 1Ghz after using webtop, but a reboot would get the underclocking working again.
I only tried the webtop hack to see if I could get it working. I haven't gone back into it at all so I don't know if this is something that will reoccur. Although I will say that with my day to day use I have not run into any clocking issues since.

Thanks, is there a page somewhere which details which kernels do what and which would work with my rom?
Sent from my MB860 using xda premium

ishamm said:
Thanks, is there a page somewhere which details which kernels do what and which would work with my rom?
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
This is the page for faux's kernels. As far as details, start reading and searching through that thread as well as the threads for any ROMS you are using. 99% of the time people will either have the same problem (and possible fix), the other 1% of the time they will identify a bug (i.e. maxed out CPU).
Keep in mind faux does have different kernels for Froyo, GB, and CM7.

For some reason even if I move the slider from 1300my to 1000, when I touch the screen with at least 3 fingers for a few seconds it pegs out at 1300. I read our cpu's are daisy chained so to speak
so the 2nd core kicks in when needed. I tried cpu tuner and it gives the option to powersave and only use one core or if you choose performance it will allow Both cores. Just might be setcpu isn't designed fully for our dual core setup.

thanks for the link to kernels, but i cant find one for HomBase, or a Kernel only download on the homebase thread. i have the Version2, which has some blur, but only the 1.0Ghz clock kernel. where could i get the 1.3GHz download by itself, to see if that might help, as its the one CM7 had iirc
Thanks

ishamm said:
thanks for the link to kernels, but i cant find one for HomBase, or a Kernel only download on the homebase thread. i have the Version2, which has some blur, but only the 1.0Ghz clock kernel. where could i get the 1.3GHz download by itself, to see if that might help, as its the one CM7 had iirc
Thanks
Click to expand...
Click to collapse
Get the 1.3 from the faux thread that I linked to. They're in the very first post...
CM7 is the only ROM that has its own custom faux kernel. For all other ROMS just match the kernel to the build the ROM is based off of (Froyo or GB). If you're using V.2 of Homebase then use the GB one.
Update: Also, there are other kernels out there. I was only using faux's as an example since you were using CM7 and Homebase.

thanks, ive now got the 1.3Ghz kernel installed successfuly, but it still seems like setcpu will not underclock. i dont know if its normal, but the "Scaling" option is greyed out, and i cant get access to the Advanced tab. is there something im doing wrong in setcpu itself?
thanks again

ishamm said:
thanks, ive now got the 1.3Ghz kernel installed successfuly, but it still seems like setcpu will not underclock. i dont know if its normal, but the "Scaling" option is greyed out, and i cant get access to the Advanced tab. is there something im doing wrong in setcpu itself?
thanks again
Click to expand...
Click to collapse
Lack of underclocking is a known issue with the latest OC kernel. I'm unclear whether it's actually a bug with the kernel or with setCPU not supporting dual core devices. But yeah, there's a problem with it right now. I'm on the stock enhanced, and other than the webtop issue I mentioned above, it works fine.
Scaling/advanced are not available, this is something that is determined by the kernel you are using not the app.

ok so if i understand you right i would be best off using the stock enhanced kernel (for now), as it will underclock fine?

ishamm said:
ok so if i understand you right i would be best off using the stock enhanced kernel (for now), as it will underclock fine?
Click to expand...
Click to collapse
It's working perfectly for me, except after webtop use (which I don't normally use).

I'm still having the same issues regardless of weather I choose power save or performance it will not underclock, and those are the only governors I get the option of :s
Sent from my MB860 using xda premium

Trinity Kernel...1400mhz max?

I recently flashed the newest Trinity Kernel on my Nexus 7. I still have the stock ROM. I tried to tweak the CPU settings with ROM Toolbox and the most I can overclock is 1400mhz. Why can't I overclock to 1600? Is it because of the stock ROM? I'm looking into Glazed Jelly Bean as a custom ROM but I'm not sure I want or need to use a custom ROM at this point.
Any suggestions?

Because he dropped the Max. You probably flashed A111 correct? That's a TSVZ meaning it is slightly over clocked and undervolted kernel meant for battery not for performance.
Sent from my Nexus 7 using Xparent White Tapatalk 2

U2Bono269 said:
I recently flashed the newest Trinity Kernel on my Nexus 7. I still have the stock ROM. I tried to tweak the CPU settings with ROM Toolbox and the most I can overclock is 1400mhz. Why can't I overclock to 1600? Is it because of the stock ROM? I'm looking into Glazed Jelly Bean as a custom ROM but I'm not sure I want or need to use a custom ROM at this point.
Any suggestions?
Click to expand...
Click to collapse
try a96, its one of my faves. it has a max of 1700mhz http://goo.gl/mLUCZ

Mildly on topic question ... do you notice any imporvments with overclocking? My first experience with overclocking as on my Hero, and then Galaxy S1, but this N7 just feels so fast i cant see overclocking making it any smoother? lol
thanks

myke66 said:
Mildly on topic question ... do you notice any imporvments with overclocking? My first experience with overclocking as on my Hero, and then Galaxy S1, but this N7 just feels so fast i cant see overclocking making it any smoother? lol
thanks
Click to expand...
Click to collapse
yes. its noticeable, but not like on the older devices.

simms22 said:
yes. its noticeable, but not like on the older devices.
Click to expand...
Click to collapse
Nice, ill have to look into rooting sometime soon.

Ok, I got the a96 and I've flashed it...
Is there a detailed changelog for each version? The a111 said it was a 1600mhz kernel so I don't understand why it was dropped down to 1400. That's where my confusion was.
I did notice some increase in speed at 1400. I was having some stuttering issues with Dead Trigger and Minecraft PE, and they were less with the 1400. I've got it running at 1600 now but I don't know what it will do to the battery or how well it will perform. I'll find out later. I've run through the battery pretty quickly today, but I was tinkering with it A LOT so it's not accurate.
What kind of tweaks could I do using Rom Toolbox that would help me maximize my battery while overclocking to 1.6?

Dont over clock.. i dont even see a need to. I use the ondemand gov which stutters a little but using interactive clears that up. Also using the CFQ IO as it is the stock IO used. Its stock so its gotta be good . Also you should turn F-Sync off that helps quite a bit. Also you could toggle auto hotplug and make it only run two cores while gaming and then turn it back on when finished so that way it will hotplug cores as it sees necessary. You could also up the voltages a little bit, some CPU's dont like the lower voltage and that will cause stuttering and glitching just up them by 25mV and see if it clears if not try another 25mV.

I will try those things, but I really want to play with overclocking and learn what happens. This is my first Android device so I'm experimenting and playing around.
But I have one more question...I've overclocked to 1.5...I found 1.6 to be the same as 1.5. But it seems that after an hour or so, it resets to 1.3. in ROMToolbox. Why is this?

Don't use rom toolbox. Use the Trinity app. It sticks just fine for me. Besides you support the dev to make better kernels.
Sent From My Toro+ via White Tapatalk

simms22 said:
try a96, its one of my faves. it has a max of 1700mhz http://goo.gl/mLUCZ
Click to expand...
Click to collapse
i **** my pants a little when it says "system succesfully corrupted, please freak out now"

MRsf27 said:
i **** my pants a little when it says "system succesfully corrupted, please freak out now"
Click to expand...
Click to collapse
Lol its a joke... its the updater-script you can make it say anything... :laugh:

MRsf27 said:
i **** my pants a little when it says "system succesfully corrupted, please freak out now"
Click to expand...
Click to collapse
ha!
youre not the first

Overclocking past 1.4 Ghz doesn't result in any major usability improvements. I've gone up to 1.7 Ghz and the only thing it does is make my tablet really warm and unstable. All you really need for improving system performance is I/O tweaks to speed up app and page loading, and a little bit of GPU overclocking to help with the transitional effects.

and, to be honest, depending which trinity kernel im using, im using either 1100 or 1150mhz mostly. on a111 im using 1100mhz and on a96 i used 1150mhz. with those speeds everything is still fast but a bit better on battery

Overclocking
If you want a little more information about the the overclocking if you havent already you might want to check out http://forum.xda-developers.com/showthread.php?t=1788759 its the official thread of the trinity kernel for grouper.