• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Overclocking with CPU Tuner

So, those who are using CPU setting apps to "OC" to 600, you're not doing anything.

I'm using the Overclock Widget. It has the option to run the CPU at a lower speed while the screen is off. I have mine set to go down to 128 while the screen is off. This is assuming that doing so will help save battery. Is it actually doing anything or am I wasting my time with it?

Thanks again!
 
I'm using the Overclock Widget. It has the option to run the CPU at a lower speed while the screen is off. I have mine set to go down to 128 while the screen is off. This is assuming that doing so will help save battery. Is it actually doing anything or am I wasting my time with it?

Thanks again!

Yeah, that's actually useful because you're telling the system to use less CPU. What's your average battery life with those settings?
 
So, those who are using CPU setting apps to "OC" to 600, you're not doing anything.

So running a CPU setting apps such aas CPUBoost or SetCPU is actually pointless?

Just wondering because I am rooted but do not run a CPU setting app. Should I get one?
 
So running a CPU setting apps such aas CPUBoost or SetCPU is actually pointless?

Just wondering because I am rooted but do not run a CPU setting app. Should I get one?

Well, not necessarily. Like the guy above, he uses it to save battery life. But if you're trying to overclock, you can't with Icarus.
 
Yeah, that's actually useful because you're telling the system to use less CPU. What's your average battery life with those settings?

Running Icarus, and with those underclock settings, I can go longer than 12hrs with normal use of the phone before the battery indicator dips down into the orange color. I don't leave Wi-Fi and GPS on constantly. I only turn those on when I need to use them.

I have it on the charger now. When it reaches 100%, ill see how long I can go without actually charging it, then report back.
 
i pulled 16hrs yesterday using web, phandroid and playing with my home screens on crazy home.

screen full dim, maxed cpu at 480 min 122880, wifi only when near access and no synch gps.

battery at 7% when i charged it.


edit:
yes, i know it's way underclocked but i had no issues i didn't foresee. icarus is faster to the point of a 480 underclock being just fine for me, little lag here ands there but that's what i expect from a $100 phone.
 
Ok, overclocked set at 600, underclocked down to 128 when the screen is off.

At 7am this morning, I took the phone off of the charger at 100% battery. Now, 15hrs later (10pm), I am down to 20% battery.

Today, I used the phone quite a bit throughout the day.
I used GPS and Wi-Fi off and on as well.
Longest streak of continuous usage with the screen on was about an hour.
Sent and recieved about 30 sms, 5 mms, and had a few friends meet me up with me in various places on the island (bar hopping) by using an app called GPS Share.
I used the camera for about 15 pictures before ultimately deciding that it really does suck compared to the other gear I carry with me.
Watched three 5min videos on Youtube.
Oh, and I used Tune-In radio for about 2hrs with the screen off.

I have absolutely no complaints about battery issues with this phone.

I'll be going to bed soon, and won't be putting it on the charger. Since the phone won't see much use through the night, it shouldn't use that much battery being an alarm clock. I wake up at 7am, and will see how long it will last until it gets down to near dead. Will follow this up tomorrow afternoon with a complete total running time.
 
The normal speed for the MSM_7x25 is 528 Mhz. However, Huawei has ALREADY overclocked the Ascend up to 600. An OC kernel is required to overclock. Another dev, Linuxgeek, has patched and compiled a new OC kernel that takes it a couple steps higher to 691 Mhz, which is what I used in my discontinued CM6 port. So, those who are using CPU setting apps to "OC" to 600, you're not doing anything.

The thing that really kills the Ascend is the lack of GPU. Other similar devices that have the same processing speeds are at an advantage because they have an onboard GPU.


do you by any chance have a link to this kernal?? i would like to take the ascend to 691 if possible,
 
do you by any chance have a link to this kernal?? i would like to take the ascend to 691 if possible,

Did you ever get any access to this Modified Kernal? If so let me know please. I wouldn't mind trying to give it a little nitrous boost!..LOL...

Seriously though, if you ran across this let me know...
Thanks.....Jeff
 
Hi guys...know this thread is a little older but its kinda related to what I'm looking for so I thought i'd post here. I am the developer of CPUBoost. I've been working with someone with an ascend who is having some issues with the app not saving the speeds when exiting the app. I'm wondering if this is a common problem with this phone. I don't have access to an ascend . Do you guys have custom kernels for overclocking or is the stock kernel not locked? Its hard to troubleshoot all the different hardware when you don't have access to them but I want to improve the app as best I can. If anyone is familiar with the ascend kernels and how the clock speed is handled and could lend some insight I'd appreciate it.

Joser116 I quoted you cause I was wondering what you were running on the Evo when you tried the app?

Thanks for any replies...(I actually got my start into android and rom deving here on Android Forums so I know it's a great place to get feedback)

It is my complete understanding that the Kernal just does not have the capabiliity for overclocking, and that 600hz is the best we can do. I guess the best for performance would be to assure that it stays at 600 all the time, unless it's dormant. But as far as the Kernal, my previous post was the first I've heard of a dev. coming up with something that can be overclocked, and I would love to see it.
So as far as NOW is concerned, I don't think there is anyway to truly "Overclock" this phone.


Oh well, if you have any luck, let me know...that would be great....Jeff
 
I suppose that means its likely the oc kernal was actually done. I will ask Linuxgeek later (He is another genius, He is nice too :)). I am kinda curious. Though I mostly underclock this phone. 38 hours without dying is my max so far. I too, Am using the overclock widget for its ability to have a different frequency when the screen is off. ^^.

He said he did make the kernal. It worked with stock/rooted. Though when it was overclocked at around 694, The camera stopped functioning. That's why it wasn't released. Also, It was not used with Icarus (Didn't try it, Probably won't?). Isaac is running something of his own, I believe. So perhaps it's easier to OC better on whatever he is using. ^^.
 
Set my Nitrous Widget to 710 but I think I will wait until a few others try it first. :D


No difference from a 600 force run with nitrous.
Tested by shutting everything off and removing all icons from launcher. Ran kelidoscope lwp.
Set max/min to 600. Nitrous to 710.
No change in performance when widget activated besides the usual lag while it activated.
 
When I hit the Nitrous Widget (710), it seemed to stop the lag I was getting with GO SMS messaging.
 
When I hit the Nitrous Widget (710), it seemed to stop the lag I was getting with GO SMS messaging.
To be honest with you, Depending on when you last used your messaging app and how long you had it open, It can change the amount of lag you have loading/opening it. I've seen my phone sometimes open up the message app really fast, Other times it took a few seconds. That could be taken into account as well.
 
i use the kaleidoscope live wall paper because you can really see a difference when changing cpu speeds. it's a pretty graphically intensive wallpaper too.
 
Back
Top Bottom