Develop Bugs

[Q] queation about SetCpu

ok, i searched for the problem i had but couldnt find anything relevant. i hope someone can direct me to it, if there is any already, or give me an answer,
i downloaded Setcpu and ive seen most of people using "conservative" scaling for better battery life, but i dont see that option in the app. i just see ondemand, userspace and performance.
any idea if im doing something wrong?
and also i would appreciate if someone can tell me the settings for longer battery life? wanted to try it but didnt understand that much.
thanks.
btw im using virus rom rc3 with stock kernel.

The governors are kernel specific- if the kernel doesn't support it, it won't show up as an option. In your case, conservative scaling is not supported by the kernel you are using.

_MetalHead_ said:
The governors are kernel specific- if the kernel doesn't support it, it won't show up as an option. In your case, conservative scaling is not supported by the kernel you are using.
Click to expand...
Click to collapse
oh ok. now i got it. thanks for the info.

Both Netarchy and Kings kernels have "conservative" governors on them. One of the top ways to conserve battery is to make a profile setting for Screen Off where you set the min and max freq to the lowest possible setting. For me though I can go to 128 Mhz, I get too much lag on wake-up and therefore set to 384. Your phone may do better.
Someone also made a thread that describes the advanced settings. Tweaking those can also improve battery life as well.
Sent from my PC36100 using XDA App

sombdy said:
Both Netarchy and Kings kernels have "conservative" governors on them. One of the top ways to conserve battery is to make a profile setting for Screen Off where you set the min and max freq to the lowest possible setting. For me though I can go to 128 Mhz, I get too much lag on wake-up and therefore set to 384. Your phone may do better.
Someone also made a thread that describes the advanced settings. Tweaking those can also improve battery life as well.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
appreciate it.. thanks ..

[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

[KERNEL] UmaroKernel V1.06 - 2.6.35.13 - CM7-1.9Ghz-SMARTASS-OC-UV-VDD-SWAP-SLQB-BFS

THIS COMES WITH ABSOLUTELY NO WARRANTY.
I AM NOT RESPONSIBLE FOR WHAT THIS KERNEL MAY OR MAY NOT DO TO YOUR PHONE, ESPECIALLY WHEN YOU OC!
This is based on CM's 2.6.35.13 kernel.
Credits include Cyanogen, x99percent, scaryghoul, faux123, -snq, LordClockaN, and others that I couldn't find out who to credit for. If I used your code and you're not mentioned here, let me know!
GPL IN, GPL OUT: github
Version 1.0
- Added SmartAss Governor
- Added Scary Governor
- Added MinMax Governor
- Minor UV, as it depends on your own device. I suggest using the VDD sysfs interface to tweak them yourself.
- Added VDD sysfs interface (OV/UV on the fly) info/usage
- Added SLQB
- Added OC up to 1.9Ghz - SetCPU failsafe profiles are a MUST!
- Allocated more GPU memory
- Enabled swap
- Compcache is still disabled until I can get it working properly
Version 1.01
- Fixed 1.9Ghz OC
Version 1.02
- Fixed modules inside zip
Version 1.03
- Minor bugfixes
- Added TINY_PREEMPT_RCU (should help with multitasking)
Version 1.04
- Fix smartass (wouldn't go below 768mhz while awake)
- Minor bugfixes
- BFS
Version 1.05
- Added USB Mass Storage speed tweak
- Tweaked ext4 extensively
- LOTS of bugfixes
Version 1.06
- Added new governor "GreaseLightning" based on smartass
- Tweaked max readahead to 4096
- backported changes from 2.6.36.1 and 3.0rc6 (Imoseyon)
- Added Simple I/O Scheduler and set as default
- various PM fixes
- Merged HTC's vision-2.6.35-gb-MR release
- Tweaked charging code to "overcharge" for ~2 hours, should be safe and improve battery life
- Fixed netflix playback issues
GOVERNOR EXPLANATIONS:
'minmax' - this driver tries to minimize the frequency jumps by limiting
the the selected frequencies to either the min or the max frequency of
the policy. The frequency is selected according to the load.
Originally posted by erasmux -
smartass - 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 352Mhz (or if your min frequency is higher than 352 - why?! - it will cap it to your min frequency). Lets take for example the 528/176 kernel, it will sleep at 352/176. No need for sleep profiles any more!
Originally posted by scaryghoul -
Scary - A new governor I wrote based on conservative with some smartass features, it scales accordingly to conservatives laws. So it will start from the bottom, take a load sample, if it's above the upthreshold, ramp up only one speed at a time, and ramp down one at a time. It will automatically cap the off screen speeds to 245Mhz, and if your min freq is higher than 245mhz, it will reset the min to 120mhz while screen is off and restore it upon screen awakening, and still scale accordingly to conservatives laws. So it spends most of its time at lower frequencies. The goal of this is to get the best battery life with decent performance. It will give the same performance as conservative right now, it will get tweaked over time.
Click to expand...
Click to collapse
I hope to add some more user-friendly control to UV/OV, hopefully in the next version.
I tested this on my device, but as stated below, there's no guarantee it will work on yours.
This kernel should only really be used on CM7 nightly 78 and above. Not sure what'll happen if you use it on earlier nightlies, but it's definitely not supported.
Performance should be as good as or better than stock kernel.
Download:
MD5SUM: 71031df052b62d276657190cd4ec94d8
dropbox (will probably go over quota and stop working) - UmaroKernel-1.06.zip
MultiUpload: UmaroKernel-1.06.zip

This kernel excites me greatly. I will be flashing it right away. Thanks!
Sent from my HTC Vision using XDA Premium App

Great work bro! I'll def. give it a shot right now!

Thanks, gonna give this a try.

You sir just made my day. So we will need to use terminal to edit our UV values until you get that dealt with, correct? Will they persist through a reboot or not?

Now this is what I was waiting for
Thank you

KCRic said:
You sir just made my day. So we will need to use terminal to edit our UV values until you get that dealt with, correct? Will they persist through a reboot or not?
Click to expand...
Click to collapse
not to get off-topic, but your sig says youre using the pyro kernel with the CM nightlies. You do know that blah said the recent nightlies are no longer compatible with that kernel, due to the CM kernel being rebased on a different kernel than the base of the pyro kernel. However, I can attest that this kernel DOES work with both nightlies and pyromod

Thanks for the 1.9GHz Will test in conjunction with the latest CM7 nightly when I get home!

Thanks. Flashed and working great. On build 91
Sent from my HTC Vision using XDA App

I just flashed this and everything is working without any issues
However, I noticed that there is no 1.9GHz option in SetCPU...

theSpam said:
I just flashed this and everything is working without any issues
However, I noticed that there is no 1.9GHz option in SetCPU...
Click to expand...
Click to collapse
Sorry for the dumb question, but did you do the autodetect?
Sent from my HTC Vision using XDA Premium App

heybobitsme said:
Sorry for the dumb question, but did you do the autodetect?
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
I just did and the max frequency is still 1516MHz...

theSpam said:
I just did and the max frequency is still 1516MHz...
Click to expand...
Click to collapse
Ya I just noticed the same with the built in settings as well.
Sent from my HTC Vision using XDA Premium App

heybobitsme said:
Ya I just noticed the same with the built in settings as well.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
I'm having the same issue.

I know the og post said that this should mainly be used with CM7 nightlies, but I decided to give it a try with the MIUI ROM that I'm using. No dice. Wouldn't even load the bootscreen. I'm thinking I may flash over to the current CM7 nightly to give it a try though.
Sent from my HTC Vision using XDA Premium App

Im using the MIUI rom on my G2 and the smartass kernal... Freakin great if you ask me. I have about 30 to 35% battery and its about to be 1010 pm and i unplugged from charger at 730 am. Beat kernal so far.
Sent from my HTC Desire Z (actually its a G2) using XDA App

Updated OP with fixed kernel, OC up to 1.9Ghz is now supported.
Enjoy!

umaro said:
Updated OP with fixed kernel, OC up to 1.9Ghz is now supported.
Enjoy!
Click to expand...
Click to collapse
Nice! How much more memory was allocated to the GPU? Just curious...

Nice work any one test out WiFi and the kind of stuff?
Sent from my HTC Vision using XDA App

sino8r said:
Nice! How much more memory was allocated to the GPU? Just curious...
Click to expand...
Click to collapse
I think it's just under a meg, for a total of 4 megs of GPU ram instead of 3 megs.
I don't know what kind of performance gain comes from it.. I'll have to benchmark it and let you guys know.
The added memory doesn't look like it was being used by anything else, though.

SMARTASSv2 Governor question

I am trying to find a governor that will give me good performance (no lag) but also good battery life. I was told that SMARTASSv2 is the one to use for the best of both worlds. However, I notice that when I look in SETCPU, the frequency jumps all over the place and never settles down even when the phone isnt doing anything. Is there a fix for this? I am running LIONFISH 1.6 Kernel. If there isnt a fix, what is a recommended governor?
Thanks.....

dahauss said:
I am trying to find a governor that will give me good performance (no lag) but also good battery life. I was told that SMARTASSv2 is the one to use for the best of both worlds. However, I notice that when I look in SETCPU, the frequency jumps all over the place and never settles down even when the phone isnt doing anything. Is there a fix for this? I am running LIONFISH 1.6 Kernel. If there isnt a fix, what is a recommended governor?
Thanks.....
Click to expand...
Click to collapse
I always use ondemand,no matter how many governors there are,its always did me right as far as battery and speed go,very smooth.

Diablo67 said:
I always use ondemand,no matter how many governors there are,its always did me right as far as battery and speed go,very smooth.
Click to expand...
Click to collapse
here is what I have always read about ONDEMAND and why I really dont use it:
"OnDemand scales its clock speed in a work queue context. In other words, once the task that triggered the clock speed ramp is finished, OnDemand will attempt to move the clock speed back to minimum. If the user executes another task that triggers OnDemand's ramp, the clock speed will bounce from minimum to maximum. This can happen especially frequently if the user is multi-tasking. This, too, has negative implications for battery life. "
Im now testing intellidemand but there appears to be a lag when opening programs (mail, contacts, etc).

dahauss said:
here is what I have always read about ONDEMAND and why I really dont use it:
"OnDemand scales its clock speed in a work queue context. In other words, once the task that triggered the clock speed ramp is finished, OnDemand will attempt to move the clock speed back to minimum. If the user executes another task that triggers OnDemand's ramp, the clock speed will bounce from minimum to maximum. This can happen especially frequently if the user is multi-tasking. This, too, has negative implications for battery life. "
Im now testing intellidemand but there appears to be a lag when opening programs (mail, contacts, etc).
Click to expand...
Click to collapse
Try smartass instead of 2,see if that balances it out.

Diablo67 said:
Try smartass instead of 2,see if that balances it out.
Click to expand...
Click to collapse
Does same thing. Intellidemand is pretty snappy and I watch the setcpu screen and it raps down and up nicely.. the only issue is opening apps.. small lag but once you are in the program its quick

dahauss said:
Does same thing. Intellidemand is pretty snappy and I watch the setcpu screen and it raps down and up nicely.. the only issue is opening apps.. small lag but once you are in the program its quick
Click to expand...
Click to collapse
Maybe try a full reboot.Clear cache and delvik.

Diablo67 said:
Maybe try a full reboot.Clear cache and delvik.
Click to expand...
Click to collapse
tried that.. same issue... Does anyone run intellidemand and if so, how does it work with the evo in terms in performance and battery life.. so far so good here except for the small lag wen opening programs

not sure what ROM you are on..but the Mason kernel w/ wheatley gov is treating me nicely, I spend most of my time at either 245 or 960..it does ramp all the frequencies in between thought as well. Maybe try underclocking your device..I like to keep my freq. high because I want my EVO to perform! With that being said, with normal usage (lots of texts, few calls, moderate web browsing, some GPS use), I am seeing at least 40% left after 16 hrs.

I personally use ondemandx which is in lionfish 1.8 or underworld v0.5. I find that smartass, V2 specifically. Changes frequency way to often and causes random reboots because our CPU doesn't handle that many frequency changes that quickly. Interactivex or ondemandx seem to be the best for me. They are both good on battery and very snappy.
Sent from my PC36100 using xda premium

dieselford said:
I personally use ondemandx which is in lionfish 1.8 or underworld v0.5. I find that smartass, V2 specifically. Changes frequency way to often and causes random reboots because our CPU doesn't handle that many frequency changes that quickly. Interactivex or ondemandx seem to be the best for me. They are both good on battery and very snappy.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
I noticed this too with SMARTASS (both versions). I was trying INTELLIDEMAND yesterday, but with 5 hours on battery (anker 1700), and almost no use (mostly stand by) I was down to 78% battery. I am now back to interaxtiveX

KISS-Kernel

excuse me; have question about this kernel; i couldn't post in the original thread;
by setting the min clock speed to 768MHZ & the max to 1407MHZ, How much voltage does it spend? by setting the min to 245MHZ & max to 1024MHZ how much? i overclocked to 1407MHZ , i saw more smoothness and speed; but i felt that its consuming more power!
is overclocking harmful to CPU? ( always overclocking )
Rom: MY One V RC4.0 FX
PrimoU GSM
Kernel: Latest Kiss Kernel

Hi
Political correct answer:
Of course OC "can" harm your device - like all OC´ing
Realistic answer:
Most One V devices can handle OCing up to 1.5 without problems
but since this may be specific to chip manifacturing there is no
guarantee that it is. Therefore before using any OC you should
test it very carefully.
And also - Of course running the chip at higher frequencies needs
more power. Simply physics .)
In "normal" daily use the difference is not big because the cpu will
not run at high frequencies most of the time. If you do things
like "heavy" gaming this is of course forcing the cpu to run faster.
To reduce the "effect" a little bit there is a kernel feature called
Undervolting (UV) with that you can reduce the voltage for
specific frequencies. Like OC this is device specific. So some
devices can run stable with more reduced voltage then others
BTW: why to you set the min frequency to 768?
This will limit that the frequency cannot go lower then that if the
device is idle. Running at 245 needs of course less power then 768
max

Thanks for the nice info, well, i heard that some users said that the best frequency for " My One V" rom:
Minimum: 768MHZ
MAX: 1407
I'm using "Set CPU" to OC
So setting the min frequency to 245MHZ will save more power, right?
Sent from my HTC One V using xda app-developers app

Satohiroshi said:
So setting the min frequency to 245MHZ will save more power, right?
Click to expand...
Click to collapse
Yes - especially for the time before the device can go into
"deep sleep" when beeing idle.
The only "disadvantage" is that depending on the govener that you use
there might be a small lag before the frequency scales up
Actually it depends if you notice it at all
If you use govener ondemand it should be no problem
if you use e.g. smartassV2 you might consider thinking about
using some tunables that will reduce that behaviour.
max

Thanks, yeah, i meant for normal activities, like checking Facebook,mail, watching movies ... So ondemand mode would be better
Sent from my HTC One V using xda app-developers app

maxwen said:
Yes - especially for the time before the device can go into
"deep sleep" when beeing idle.
The only "disadvantage" is that depending on the govener that you use
there might be a small lag before the frequency scales up
Actually it depends if you notice it at all
If you use govener ondemand it should be no problem
if you use e.g. smartassV2 you might consider thinking about
using some tunables that will reduce that behaviour.
max
Click to expand...
Click to collapse
What is your recommend governor to integrate with your Titanium-KISS kernel and what is your favourite I/O Scheduler tweaks, for daily use & heavy gaming?
I'm using smartassV2 & i set my I/O Scheduler to deadline until now, because it's peoples favourite
Should i change it to ondemmand to gain a better performance?

Hi
Actually there is already a lot of information about your question
in the KISS kernel thread.
Especially about how to tweak smartassV2 based on "profiles"
max

maxwen said:
Hi
Actually there is already a lot of information about your question
in the KISS kernel thread.
Especially about how to tweak smartassV2 based on "profiles"
max
Click to expand...
Click to collapse
uh, okay...i'll re-read the info once again :good: