Develop Bugs

set cpu 2.0

Alright, so set cpu has been updated and it says it has a beta setting for the evo. I was reading through the comments and one of them says that setcpu is only for controlling the cpu speed from standard 1ghz and lowering. If i wanted to overclock to 1.2(I think that's the highest i've seen around) I would have to get a custom rom. So.. i have baked snack v7... is that what they are considering a custom rom? or do i have to have a supported overlcock custom rom. then i use set cpu to control the cpu speed.
?
hah thank you.

derik123derik123 said:
Alright, so set cpu has been updated and it says it has a beta setting for the evo. I was reading through the comments and one of them says that setcpu is only for controlling the cpu speed from standard 1ghz and lowering. If i wanted to overclock to 1.2(I think that's the highest i've seen around) I would have to get a custom rom. So.. i have baked snack v7... is that what they are considering a custom rom? or do i have to have a supported overlcock custom rom. then i use set cpu to control the cpu speed.
?
hah thank you.
Click to expand...
Click to collapse
You can only overclock the CPU by using a custom kernel, and at this point in time you lose camera
http://forum.xda-developers.com/showthread.php?t=686240

[Q] Kernels ain't working for me

Hello there,
I've been flashing kernels since I was in LeeDroid Froyo and got no problems. However since I switched to GB based roms such as RCMix3D and TB Fusion, my phone always freezes when I try setting Kernel-Lee-V3.1.1-2.6.35.13-CALLREC or MDJs v19 to maximum overclock so I have no choice to but to stay on stock kernel. I have no ext3/ext4 partition on my SD card in case you ask.
Current ROM: TB Fusion 1.1.2
Radio: 12.54.60.25U_26.09.04.11_M2
Any idea what should I do to solve this issue?

golokipok said:
Hello there,
I've been flashing kernels since I was in LeeDroid Froyo and got no problems. However since I switched to GB based roms such as RCMix3D and TB Fusion, my phone always freezes when I try setting Kernel-Lee-V3.1.1-2.6.35.13-CALLREC or MDJs v19 to maximum overclock
Click to expand...
Click to collapse
uoooo this is sooo dangerous for your handset... u can "smoke" it...
Any idea what should I do to solve this issue?
Click to expand...
Click to collapse
yes, your handset freezes because the overclock that u do its too high... underclock it at 1200-1400mhz & try...
and configure SET CPU features... like the standby status, etc....but do it with common sense....
think about that DHD proccessor goes by default at 1gz, really when we overclock the processor we are putting in danger the security of our device

SERGI.3210 said:
uoooo this is sooo dangerous for your handset... u can "smoke" it...
yes, your handset freezes because the overclock that u do its too high... underclock it at 1200-1400mhz & try...
and configure SET CPU features... like the standby status, etc....but do it with common sense....
think about that DHD proccessor goes by default at 1gz, really when we overclock the processor we are putting in danger the security of our device
Click to expand...
Click to collapse
Haha! I know that overclocking is quite dangerous. Back on the froyo days, my phone is quite stable around 1.8ghz so I'm just wondering why is this happening (maybe my phone's processor is starting to fry up? ). Is there any effect if I'm using smartass profile on those kernels I've mentioned?

golokipok said:
Haha! I know that overclocking is quite dangerous. Back on the froyo days, my phone is quite stable around 1.8ghz so I'm just wondering why is this happening (maybe my phone's processor is starting to fry up? ).
i hope that the processor works or not works (don´t crashes a little bit...)
but the reason of your freezes maybe (almost sure) because froyo & gingerbread don´t works at the same form, and gingerbread need more resources & stability for to work correct... don´t forget that the kernel manages the hardware...
if u force it......... u know what can happen...
golokipok said:
there any effect if I'm using smartass profile on those kernels I've mentioned?
Click to expand...
Click to collapse
it´s possible, take this explanation, read and judge by yourself what´s the better cpu governor...
smartass (Best explanation i've found paraphrases to: based on interactive, but better.)
----
ondemand
Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see "up threshold" in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed. - SetCPU website
conservative
Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery. - SetCPU website
performance
Available in most kernels. It will keep the CPU running at the "max" set value at all times. This is a bit more efficient than simply setting "max" and "min" to the same value and using ondemand because the system will not waste resources scanning for the CPU load. This governor is recommended for stable benchmarking. - SetCPU website
powersave
Available in some kernels. It will keep the CPU running at the "min" set value at all times. - SetCPU website
userspace
A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor. - SetCPU website
Interactive
The 'interactive' governor has a different approach. Instead of sampling the cpu
at a specified rate, the governor will scale the cpu frequency up when coming
out of idle. When the cpu comes out of idle, a timer is configured to fire
within 1-2 ticks. If the cpu is 100% busy from exiting idle to when the timer
fires then we assume the cpu is underpowered and ramp to MAX speed.
If the cpu was not 100% busy, then the governor evaluates the cpu load over the
last 'min_sample_rate' (default 50000 uS) to determine the cpu speed to ramp down
Click to expand...
Click to collapse

Thanks for the info
SERGI.3210 said:
because froyo & gingerbread don´t works at the same form, and gingerbread need more resources & stability for to work correct... don´t forget that the kernel manages the hardware...
if u force it......... u know what can happen...
Click to expand...
Click to collapse
You have mentioned about those "resources", is there any special measure that I need to do or what? I'm using the smartass profile on those kernels but still *sigh*
Anyway, I've observed on your sig that yours is overclocked @ 1.8ghz even though you're running GB, me envy

golokipok said:
have mentioned about those "resources", is there any special measure that I need to do or what? I'm using the smartass profile on those kernels but still *sigh*
Click to expand...
Click to collapse
you only should do a good over/underclock & set the correct cpu governor for your daily use....
well, you know ho is @MDeeJaay? the developer of MDJ kernels and roms...
he explained smartass with this words:
SMARTASS GOVERNOR - is based on the concept of the interactive governor.
I have always agreed that in theory the way interactive works - by taking over the idle loop - is very attractive. I have never managed to tweak it so it would behave decently in real life. Smartass is a complete rewrite of the code plus more. I think its a success. Performance is on par with the "old" minmax and I think smartass is a bit more responsive. Battery life is hard to quantify precisely but it does spend much more time at the lower frequencies.
Smartass will also cap the max frequency when sleeping to 245Mhz (or if your min frequency is higher than 245 - why?! - it will cap it to your min frequency). Lets take for example the 998/245 kernel, it will sleep at 245.
golokipok said:
, I've observed on your sig that yours is overclocked @ 1.8ghz even though you're running GB, me envy
Click to expand...
Click to collapse
no, no buddy... i only show the max speed nothing more... i set my cpu concretly like this;
CPU GOVERNOR:interactive
MAX SPEED:1113 MHZ
MIN SPEED:245 MHZ
PROFILE: screen off; 245 MHZ max.
245 MHZ min.
in adition i´m going to modify my syg LOL

haha..thanks again. I'm gonna try playing with the frequencies to see which will suit me
i hope someone can make a stable 1.8ghz kernel without the freeze

IT´S POSSIBLE but i don´t want to try it LOL
i love a lot my DHD

Still problems with Desire and blackscreen

Hi folks!
I´ve installed the latest LeeDroid with full wipe and got the problem, that the display often don´t wake up from standby. The touchscreen works, but it won´t wake up.
Then i tried to install the latest radio version and flashed/wiped again. Still the same problem.
So i tried to flash CyanogenMod7 with GAPPS, but the same error is still available. Never had that problem with original rom.
What should i try next?

What radio do you have/flashed.
Maybe try a different kernel.

Now i´ve installed radio: 5.17.05.23
Before i had installed 5.17.05.08. I got the problems with both radio versions.
Version of kernel is 2.6.37.6-cyanogenmod-g37556d9 [email protected] #1
Where can i download suitable kernel versions?

AOSP Kernels - in the developement section.
http://forum.xda-developers.com/showpost.php?p=12350779&postcount=3
Are you using any program to control CPU? You can try SetCPU and use a screen-off profile.

I didn´t use this tools before, but now i´ve installed Set CPU for root users.
I´m now in the menu and see the the profile screen-off, but i don´t know what i should configure there?! What does that tool with screen-off do?
Update:
Made a profile with screen off with 245 max/min. Enabled it!
Anything else to do?
Which kernel you would prefer for my desire gsm?

Okay, first of all - set the main frequencies.
Depends on ROM, I have 384-998 Ondemand.
Then go to profiles, click enable.
Click add profile, then select:
Profile: Screen OFF
Max: 245
Min: 128
Scaling: Ondemand (but you can play around with that)
Priority: 100
Maybe, you must adjust higher frequencies, but play around with it a little.

Profile: Screen OFF
Max: 245
Min: 245 (minimum is 245, i can´t configure it to 128)
The display bug is still available!

Set max to 368. Seems as if your desire can't handle 245/245.
Swyped from Oxygen with Transparent XDA App

Update!
Now i wiped and installed CyanogenMod7 RC1 again with Gapps. I didn´t install any other Apps, so i can be shure, that no app cause this display problem.
I can´t reproduce the problem again. I need more time for testing, but at this time it seems that there is a problem with any installed app.
Set CPU is disabled!
Update:
Problem is here again!
Now i´m testing the suggestion of Mr. MatDrOiD!

Which governor do you use?
Swyped from Oxygen with Transparent XDA App

i use "Set CPU".
It feels like, the chance my Display wake up from standby is now bit higher and better, but the problem still exists.

Heavymaxx said:
i use "Set CPU".
It feels like, the chance my Display wake up from standby is now bit higher and better, but the problem still exists.
Click to expand...
Click to collapse
No, i mean the governor, not the software. The governors are the controllers for the regulation of the cpu frequencies (how fast it increases and decreases). Most available governors are "ondemand", "performance", "powersave", "interactive" and "smartass". So what governor do you use?
According to your experiences, setcpu is probably the crux of matter.

I can't be 100% I had the same issue as you, but when I used to use CM7 or Redux I did have problems with black screens and unresponsive touchscreen (in that order respectively). Didn't happen on Sense at all.
But now I've been on Oxygen for close to two weeks and I haven't had any of those symptoms since. I think all the hacks they include in CM7 and other custom ROMS is to blame. Perhaps give Oxygen a try to rule it out, as it's an almost pure AOSP ROM. Don't run Setcpu either on it.

MatDrOiD said:
No, i mean the governor, not the software. The governors are the controllers for the regulation of the cpu frequencies (how fast it increases and decreases). Most available governors are "ondemand", "performance", "powersave", "interactive" and "smartass". So what governor do you use?
According to your experiences, setcpu is probably the crux of matter.
Click to expand...
Click to collapse
Ah ok! I use "ondemand".
I would not use SetCPU if i would have no problems. I´m testing around, BECAUSE i have problems.
@Salty: Thanks for the fish! I got the same problem on LeeDroid too. IDC what Rom i use. It should be up to date and should support App2SD+, i need more internal memory, that´s all.

Amoled Display got changed - everything works fine!
Just wanted to finish this thread with a solution!
Thanx!
**CLOSED**

[q] htc wildfire s overclock

I have htc wildfire s ...i hav rooted ...i want to overclock it 806 mhz.....pls tell me the procedure to overclock..
I am using htc wildfire rom ..pls help

First you need a kernel that supports overclocking.
If you using a stock Rom then look for the kernel that matches your Android version eg. 2.3.3 or 2.3.5 you will find them in the development section posted by Jikantaru
If you install a custom Rom then it will most likely have an overclockable kernel baked in.
To change clock settings I recommend 'no frills CPU' search it in the market or you could use set CPU.
Once you install one of the above apps then change the min and max sliders to the desired frequency.

if we over clock it much does it effect the speed or hardware of the phone?

Your phone may hang.
There is SetCPU for XDA members:
http://forum.xda-developers.com/showthread.php?t=505419

RRRb50 said:
if we over clock it much does it effect the speed or hardware of the phone?
Click to expand...
Click to collapse
You will definitely get better performance and it shouldn't cause you any problems.
Use no frills CPU I find its better than set CPU, when restarting your phone set CPU doesn't keep your overclock settings even though its set on boot.
As for the govonor settings I would choose smartass2 and noop for the scheduler.
I would keep the minimum frequency on 245MHz it can go lower but it could cause some issues (lag and slow unlocking and waking)
Note: not all cpu's are capable of running at the same speed, I'm lucky mine can run at 806MHz but some people have issues.
If you notice any problems like freezing etc, then drop the speed to a lower frequency until you find the sweet spot for your CPU.

I had mine at 806 MHz with no problems
Sent from my NookColor using xda premium

so it wont cause hardware problems only lagging and other stuff

RRRb50 said:
so it wont cause hardware problems only lagging and other stuff
Click to expand...
Click to collapse
Should be fine mate.
But remember if in the very unlikely event something does go wrong I wont be held responsible.

youll have to need an overclock kernel for that. (and a rom which supports one)
go for dust kernel or cake kernel! These two are well known for high end kernels!

Overclocking Instability

Hey I just bought a 32 GB Gnex and got it yesterday but it seems to be unstable at anything above the stock max frequency of 1230 MHz. I've tried Paranoid Android and last night's CM10 nightly and they would both freeze and immediately reboot upon setting it to 1305 MHz. I then flashed the Zen kernel on top of CM10 and I like that it can go up to 1.8 GHz but whenever I set anything beyond 1.23 GHz it starts to lag for about 1-3 seconds. When I knock it back down to 1.23 GHz everything is fine again.
This is the first OMAP device I have since I had the OG Droid back in 09, I loved how they were extremely overclockable and I'm going to be pretty sad if mine has to stay at stock speeds. I've tried using JRummy's ROM Toolbox Pro and the built in Performance settings to try and set the frequencies but it doesn't seem to make a difference on which one I use. I've been using the OnDemand and Interactive(x) Governors.
Is this a known problem or am I alone on this?

some CPUs have a higher tolerance than others for overclocking. looks like you got one of the super low tolerance ones.

I hope that's not the case :-/

brando56894 said:
Hey I just bought a 32 GB Gnex and got it yesterday but it seems to be unstable at anything above the stock max frequency of 1230 MHz. I've tried Paranoid Android and last night's CM10 nightly and they would both freeze and immediately reboot upon setting it to 1305 MHz. I then flashed the Zen kernel on top of CM10 and I like that it can go up to 1.8 GHz but whenever I set anything beyond 1.23 GHz it starts to lag for about 1-3 seconds. When I knock it back down to 1.23 GHz everything is fine again.
This is the first OMAP device I have since I had the OG Droid back in 09, I loved how they were extremely overclockable and I'm going to be pretty sad if mine has to stay at stock speeds. I've tried using JRummy's ROM Toolbox Pro and the built in Performance settings to try and set the frequencies but it doesn't seem to make a difference on which one I use. I've been using the OnDemand and Interactive(x) Governors.
Is this a known problem or am I alone on this?
Click to expand...
Click to collapse
you need to disable smart reflex mpu if you want to overclock. smart reflex doesnt know overclocking, so it sets your voltages to low for an overclocked cpu. thus, instant instability.
to disable smart reflex manually, use a terminal emulator. type su(press enter) then type these 3 lines and press enter after each..
*
echo "0" > /sys/kernel/debug/smartreflex/sr_mpu/autocomp
0 to disable, 1 to enable.
btw, some cpu control apps give you options to disable/enable smart reflex.

What three lines? I only see one...
I echo'd a value of "0" to the file but it was still unstable at 1.8 GHz, haven't tried lower frequencies yet, I don't have to reboot after setting the value, correct?
edit: still unstable at 1.42 GHz, also what apps would those be that allow this? Antutu CPU Master Pro only has an option to disable PerfLock.

the way to overclock is to keep moving in small increments upward and burn testing them to check for stability. Don't go straight for a 50% overclock. move up and find your threashold, and when you do start tweaking to see if you can slowly creep beyond that

brando56894 said:
What three lines? I only see one...
I echo'd a value of "0" to the file but it was still unstable at 1.8 GHz, haven't tried lower frequencies yet, I don't have to reboot after setting the value, correct?
Click to expand...
Click to collapse
The 3 lines would be:
Code:
echo "0" > /sys/kernel/debug/smartreflex/sr_mpu/autocomp
echo "0" > /sys/kernel/debug/smartreflex/sr_core/autocomp
echo "0" > /sys/kernel/debug/smartreflex/sr_iva/autocomp
Frankly, though, don't expect 1.8GHz to be stable.

Your particular device's components might not hold it together with that oc.
Sent from my i9250

Darunion said:
the way to overclock is to keep moving in small increments upward and burn testing them to check for stability. Don't go straight for a 50% overclock. move up and find your threashold, and when you do start tweaking to see if you can slowly creep beyond that
Click to expand...
Click to collapse
Yea I know (I used to OC the CPU on my PC), I just wanted to go for something big to see if it could handle it.
Edit: seems to be stable at 1.4 GHz, I'm going to keep increasing it to see what the limit is. I'm assuming i'd have to turn off smartreflex on each boot so I should probably put it in a script in /etc/init.d correct?

brando56894 said:
What three lines? I only see one...
I echo'd a value of "0" to the file but it was still unstable at 1.8 GHz, haven't tried lower frequencies yet, I don't have to reboot after setting the value, correct?
edit: still unstable at 1.42 GHz, also what apps would those be that allow this? Antutu CPU Master Pro only has an option to disable PerfLock.
Click to expand...
Click to collapse
the trinity kernel toolbox lets you disable/enable smart reflex. plus, extremely few gnex will oc to 1.8ghz. and on top of that, to oc even to 1.4 or 1.5ghz, youll need to adjust your voltages to get yourself stable. every device likes different voltages.

I had it stable at 1.4, 1.5, 1.6, 1.7 and told my GF that I could OC it now (because I told her before that I didn't think I could) ...and then it froze rock solid lol

brando56894 said:
I had it stable at 1.4, 1.5, 1.6, 1.7 and told my GF that I could OC it now (because I told her before that I didn't think I could) ...and then it froze rock solid lol
Click to expand...
Click to collapse
i can oc my gnex(using trinity kernel) to 1.803ghz.. but to use stable for every day, 1.689ghz is a good speed for my device. a majority of devices wont even oc that high and stable. stable being the key word.

brando56894 said:
I had it stable at 1.4, 1.5, 1.6, 1.7 and told my GF that I could OC it now (because I told her before that I didn't think I could) ...and then it froze rock solid lol
Click to expand...
Click to collapse
I'd find it surprising that you got 4 different overclock levels stable in 30 minutes. There's a difference between "it boots", "it boots and runs some apps", and "stable".

brando56894 said:
I had it stable at 1.4, 1.5, 1.6, 1.7 and told my GF that I could OC it now (because I told her before that I didn't think I could) ...and then it froze rock solid lol
Click to expand...
Click to collapse
Is she impressed by your turbo-nerd status?! :silly:

Haha she was an iSheep but I made her get an SGS3 and I turned her into an Android geek, now she flashes ROMs on her own lol
Cilraaz said:
I'd find it surprising that you got 4 different overclock levels stable in 30 minutes. There's a difference between "it boots", "it boots and runs some apps", and "stable".
Click to expand...
Click to collapse
Yea it wasn't stable in the true sense of the word, I meant it just didn't freeze every minute or so.
Sent from my Galaxy Nexus using Tapatalk 2

I'm running the 11/4 build of Paranoid Android with v3.0.51-ZenSeries v4 Tuna and I having problems setting CPU frequencies via Trinity Kernel Toolbox. The frequency will stick until I switch to another app, then when I come back to the app it will be at the stock max frequency. I am also unable to use the built in frequency tuner when using TKT.
I've tried stress testing it with stability test and even when the frequencies will stick in TKT (ex. 1.4 GHz) Stability Test will report that its at 1.1 GHz. WTF is going on here? I have all three of the smart reflex values disabled.

brando56894 said:
I'm running the 11/4 build of Paranoid Android with v3.0.51-ZenSeries v4 Tuna and I having problems setting CPU frequencies via Trinity Kernel Toolbox. The frequency will stick until I switch to another app, then when I come back to the app it will be at the stock max frequency. I am also unable to use the built in frequency tuner when using TKT.
I've tried stress testing it with stability test and even when the frequencies will stick in TKT (ex. 1.4 GHz) Stability Test will report that its at 1.1 GHz. WTF is going on here? I have all three of the smart reflex values disabled.
Click to expand...
Click to collapse
dont use PA cpu settings. do you have any other cpu control apps installed? make sure theres nothing enabled in PA cpu settings, nothing. then reboot. wait 2-3 after bootup then open tkt and try using it. is the problem still there?

It seems to be sticking now for the moment, but I haven't had anything in PA CPU settings before I rebooted anyway. I do not have any other CPU OC apps installed either. Stability test is reporting the correct frequency also. Thanks.

brando56894 said:
It seems to be sticking now for the moment, but I haven't had anything in PA CPU settings before I rebooted anyway. I do not have any other CPU OC apps installed either. Stability test is reporting the correct frequency also. Thanks.
Click to expand...
Click to collapse
sweet.
if you were checking before 3 minutes after bootup, then that was the issue. whatever it was, lets hope it doesnt come back.

I was setting the values after the phone had been up for hours, idk what the problem was :-\q