Related
I know this is probably a noob question and has been asked before (i've tried searching but to no avail). How does Smartass V2 go about setting cpu speeds? What is it comparable to?
Thanks in advance.
-Vin
Sent from my HTC Sensation Z710e using xda premium
Vineares said:
I know this is probably a noob question and has been asked before (i've tried searching but to no avail). How does Smartass V2 go about setting cpu speeds? What is it comparable to?
Thanks in advance.
-Vin
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
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 600/245 kernel, it will sleep at 245. No need for sleep profiles any more!
Thats the definition of SmarAss Gov, some kernels support smartass other dont, where smarass is not supported your choice is ONDemand its kind of the same with less tweaks
Hi, sorry for an even noobier question, but I just started with all this rooting and custom ROM stuff. How do I go about setting the kernel to use the SmartAss V2 algorithm?
I just flashed this kernel [Kernel]CM7/AOSP[2.6.35.14](v0.1.2)OC~1.78GHz/BFQ/SLQB[Sep-11]. The dev states I cant use setcpu, but then goes on to mention the use of SmartAss V2 among others. I tried to access the Performance tab in cyanogensettings->performance->cpu settings, but it FC. Tried looking around the forums, but can't find anything. Tried posting in that thread, but apparently i'm too much of a noob.
Edit: Kinda went digging through the root explorer, does /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor = ondemand mean that its using SmartAss?
This kernel uses AOSP camera driver so it's most likely compatible only with Redux 2.0 (tested) and Oxygen (not tested)
Before you do anything- make a backup
It's my lame attempt (I'm a modder, not a dev) to get more battery life without loosing stability of original kernel.
Kernel is based on current thalamus 2.6.35.14 sources
What is changed (mod8):
-Vdd levels sysfs interface is back, this time seems to be stable
-default voltages for CPU clocks <700 MHz are lowered a bit- keep this in mind when playing with UV
-headphone volume boosted a little- needs to be tested
-more optimized compilation- kernel should use CPU in more efficient way (and kernel is 500 bytes smaller )
-big thanks to paul8944 for testing
What is changed (mod7):
-removed sysfs Vdd levels interface- it seems that it was responsible for instability and FC's in mod6
-USB transfer speed is higher (was ~800kB/s, now ~2MB/s for write operations)
What is changed (mod6):
-added sysfs Vdd levels interface- VDD_MIN is set to 800 mV, VDD_MAX to 1300 mV, step is 25 mV (this works fine with IncrediControl)
-available governors: ondemand, powersave, conservative, performance and smartassV2
-conservative governor is tweaked a little (should be a little less conservative)
-USB transfer speed tweak- needs testing
-other fixes
What is changed (mod5)
-lowered minimum cpu clock to 128 MHz
-more clock speeds are available up to 1113 MHz
-added smartass and smartassV2 governors
-tinyRCU replaced with preemtive tinyRCU
-enabled call recording (not tested)
-many other fixes and improvements mainly form ch33kybutt's and elevendroids' sources
Note about smartass governor- after longer period of inactivity you have to press Power button for about 2 seconds to wake up the phone
Installation:
-make a nandroid backup (just in case)
-put zip on SD card and flash in recovery, I suggest also wiping dalvik-cache (just in case)
Download:
thalamus 2.6.35.14 mod8
md5: E526C99D4326F5B11D02DB60FEFA169F
Previous versions:
thalamus 2.6.35.14 mod7 (description above), md5: 7AB623BCC5E28D9BC8A012EDD9E9BBC7
Mod6 is not available due to instability
thalamus 2.6.35.14 mod5 (description above), md5: 7DC3E94E56FD00C49FEB5C713033DE33
thalamus 2.6.35.14 mod4 (128 MHz min cpu clock, default governors set, non-preemptive TinyRCU) md5: E7DD4637D8838A6E1A64E763C8A4D549
Kernel sources available on Github
I'll give it a try, seems good. I have one question and one suggestion:
the question is: what are the reasons to enable / disable the intermediate frequencies? I don't know if it can save battery, become more stable or what. But the original kernel with only 6 frequencies available works very fine for me
and the suggestion is to add the syscf interface for being able to change the voltages. It could save some battery life if our Desire stands it (mine does even at 800 mV )
i flashed mod5 over mod4, with the result of non working wifi, then switched back to mod4 -> turned wifi off (read your post in the redux2-thread, but i didn't use tb), flashed again, no wifi. now on mod4.
blackhawk_LA said:
what are the reasons to enable / disable the intermediate frequencies? I don't know if it can save battery, become more stable or what. But the original kernel with only 6 frequencies available works very fine for me
Click to expand...
Click to collapse
I was not satisfied with default cpu clock table
-128 MHz uses ~20 mA of current less than 245- it's about 10% saving for iddle not locked phone
-for me 691 MHz max clock is really enough for my needs, it was not available in stock version
-more speeds make governors able to better match cpu speed (and save some juice)
-there are some performance fans so why not enable also 1113?
soronk said:
i flashed mod5 over mod4, with the result of non working wifi, then switched back to mod4 -> turned wifi off (read your post in the redux2-thread, but i didn't use tb), flashed again, no wifi. now on mod4.
Click to expand...
Click to collapse
Looking what caused this, I'm not sure if it's wlan driver or preemtive tinyRCU (not present in mod4)
Download temporarily removed
EDIT:
It was wlan driver.
Corrected, reuploaded package
gen_scheisskopf said:
EDIT:
It was wlan driver.
Corrected, reuploaded package
Click to expand...
Click to collapse
testing now mod5 smartassv2
Sent from my HTC Desire using xda premium
soronk said:
testing now mod5 smartassv2
Sent from my HTC Desire using xda premium
Click to expand...
Click to collapse
Me too.....
Sent from my HTC Desire using XDA App
Apologies for this noob question as im a Desire HD user and spend all my time in there. But i installed MIUI rom on my brothers Desire yesterday. Will this kernel work with MIUI, which is an AOSP rom?
Tones1971 said:
Apologies for this noob question as im a Desire HD user and spend all my time in there. But i installed MIUI rom on my brothers Desire yesterday. Will this kernel work with MIUI, which is an AOSP rom?
Click to expand...
Click to collapse
I never touched MIUI kernel so I can't tell.
MIUI framework is quite heavily modified, I can't tell if drivers included in Thalamus kernel will work with it or not
gen_scheisskopf said:
I never touched MIUI kernel so I can't tell.
MIUI framework is quite heavily modified, I can't tell if drivers included in Thalamus kernel will work with it or not
Click to expand...
Click to collapse
Yes it work! But without camera. MIUI needs the 720p camera drivers.
Does this kernel include the conservative governor? I think you mentioned somewhere you removed it.
I find the conservative governor perfect for a screen off profile, that governor would be a reason to try it.
h_misc said:
Does this kernel include the conservative governor? I think you mentioned somewhere you removed it.
I find the conservative governor perfect for a screen off profile, that governor would be a reason to try it.
Click to expand...
Click to collapse
Yes, conservative was removed. IMO smartass replaces it's functionality but it is not as laggy when raising cpu clock.
Sent from my HTC Desire using Tapatalk
gen_scheisskopf said:
Yes, conservative was removed. IMO smartass replaces it's functionality but it is not as laggy when raising cpu clock.
Click to expand...
Click to collapse
Too bad, with screen off laggy behaviour when raising the CPU-clock is exactly what I want.
With the conservative governor reaction to the power button is instant, smartass was really irritating me when pushing the power button the days I tried it.
I used setcpu with a screen off profile with conservative and ondemand with screen on (on gingervillain) which was just perfect.
I think that the best settings for a screen off profile is to use the same governor as with screen on (it takes a few seconds to change the governor so it can be a bit laggy)
I use ondemand 245/245 with screen off and ondemand 768/245 with screen on.
And of course, if min and max are the same value, it doesn't matter what governor you are using.
blackhawk_LA said:
I think that the best settings for a screen off profile is to use the same governor as with screen on (it takes a few seconds to change the governor so it can be a bit laggy)
I use ondemand 245/245 with screen off and ondemand 768/245 with screen on.
And of course, if min and max are the same value, it doesn't matter what governor you are using.
Click to expand...
Click to collapse
I use the FTP server with screen off, a script that functions as webserver to name two examples. So I need it to be possible for the CPU to be at more than minimal speed.
Then conservative should be a good option, but still thinking that there must be no much difference if you use ondemand.
I also don't like smartass
blackhawk_LA said:
Then conservative should be a good option, but still thinking that there must be no much difference if you use ondemand.
I also don't like smartass
Click to expand...
Click to collapse
You're probably right, but isn't tweaking for 1% battery saving part of the fun?
So which governors do you think should be in kernel? I don't want to include all available
Sent from my HTC Desire using Tapatalk
gen_scheisskopf said:
So which governors do you think should be in kernel? I don't want to include all available
Click to expand...
Click to collapse
The ones I like to use are ondemand and conservative.
You should include what you like off course
h_misc said:
You're probably right, but isn't tweaking for 1% battery saving part of the fun?
Click to expand...
Click to collapse
I couldn't agree more
I think that the most used governors are conservative, ondemand, interactive and smartass (don't know about the new governos: smartass2 and others)
But for me, having ondemand it's enough
blackhawk_LA said:
But for me, having ondemand it's enough
Click to expand...
Click to collapse
Do you want a dedicated build?
So as for now governors will be ondemand, performance, conservative, powersave (even more conservative than conservative ) and smartass- more likely v2.
I plan to release mod6 when I'll implement SVS
Good evening all,
I am currently running vb with the latest above kernel and xda-edition of setcpu...
My question, has anyone found voltages that are stable?
I have always/only used tegrak, when adjusting the voltages I am able to adjust "internal" as well as "core" voltages, as you may know setcpu only allows the adjustment of one voltage. So, I set all levels to the "internal" voltages that worked for me on tegrak(scaling set to smartass), everything was working fine until I rebooted the phone... At that point the phone would boot then freeze after the third media scan, I had to flash back to the b1 kernel to get back up and running.
Any advise would be greatly appreciated.
Thank you in advance!
Sent from my SGH-T959V using xda premium
You're trying to undervolt? Anton's b5 in undervolted. I'd stick with his recommended values.
How do you actually implement these voltages? I've only used Tegrak so this is new
Sent from my SGH-T959V using xda premium
QUIETLYloud , I dont't have paid Tegrak so I cannot make a thorough test.
I tried using very old Ultimate version available someplace on the web, and it does in fact seem to mess the phone up. I didn't need to reflash, but had to uninstall Tegrak, reboot, clear caches, and rescan SD for errors. Google says that there were issues with Tegrak module and custom kernels, but they were supposedly fixed around version 1.4.
I tied the new free version 1.6.7 from Market. It doesn't let me do much (like setting on boot), but at least it seems to work correctly with frequencies.
The setup with OC kernel is a little different. Before, if you wanted to OC, you would go and enable CPU Max Frequency, which would replace 1 GHz. Do not go there! The kernel already has all overclocking frequencies available. Instead set the Scaling to the highest frequency you want to use (let's say 1.2 Ghz, which is CPU Level 2). Then go to Optimization and set desired voltages for the frequencies you chose. No need to change anything for frequencies above you max scaling, the CPU will not go there anyway. Maybe it's a good idea to completely clear Tegrak data and start setting it up form scratch.
Let me know if you succeed.
Btw common Google knowledge doesn't seem to recommend lowering internal voltages. You will not gain much, there is just not a lot of current draw there. It's the core that draws a lot of current.
EDIT: Hmm... Tegrak seems to have a problem with smartassV2 governor. If the scaling in Tegrak is set to use anything but all frequencies, including 1.4 Ghz, the governor will never lower the frequency from the highest selected. The kernel itself (with SetCPU or without) doesn't have this problem, it's only when proprietary Tegrak module is loaded.
AntonX...
I decided to scrap tegrak for the time being and use what you recommended with setcpu and left voltages alone until I have a better understanding, since doing so haven't had any problems
Sent from my SGH-T959V using xda premium
Btw I said before I set the default voltages kind of safe, even if they are slightly undervolted. I'm running the kernel UV-ed a little more with SetCPU for second day without any issues. Here are my numbers right now:
1.4 - 1350
1.3 - 1300
1.2 - 1275
1.0 - 1250
800 - 1175
400 - 1025
200 - 925
100 - 900
Hi guys
I apologize for some noobness coming this way, but I don't understand. Kernel beta5 is oc/uv - what does it mean if I don't use setcpu/tegrak?
Will kernel behave other than prior versions?
And if I decide to do use setcpu? What good does it make if uv makes no change (according to Antonx) and oc will only drain the battery even more, I mean, phone is pretty much fast, so why bother oc it?
Thanks!
Sent from my SGH-T959V
My wife and I both have the htc one x. We bought it online and had the old hboot. Right now we have the same set up as viper xl with beast mode kernel oc to 1.8... Her phone seems to reboot itself at least five times a day while I usually never encounter a reboot. So im wondering if u guys think it's hardware problem or what might cause it. She has deleted the latest apps that she downloaded and the problem still persist... Thank for the help
Sent from my Nexus 7 using xda app-developers app
are you undervolted? try bringing your voltages up if so. also try bringing the overclock down a bit. just because your phone can run at 1.8 stable doesnt mean hers can, every CPU is different (unfortunately) . give that a try and report back. :good:
edit: a few users have reported running zip-align and fix permissions in TWRP/venom tweaks can fix reboot issues. id try messing with the voltages/OC first though
Try running the chip at default values (1.5GHz) and if problems persist try using the stock kernel. Every CPU/SoC is different and therefore can handle different values/clocks. Those would be my first troubleshooting tips because they're easy to change! Lemme know how those go before you try anything more difficult. Also please list your i/o scheduler and governor as well as voltage if possible. Good luck!
I didn't under volt her phone manually but possibly the rom under volt it. I'm going to dial back the over clock a little bit and try to dial back the voltage. I will also try to fix permissions and fix the zip. But what governor would buy recommend? Thank for your help.
Sent from my Nexus 7 using xda app-developers app
cables2590 said:
I didn't under volt her phone manually but possibly the rom under volt it. I'm going to dial back the over clock a little bit and try to dial back the voltage. I will also try to fix permissions and fix the zip. But what governor would buy recommend? Thank for your help.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
intellidemand and SIO scheduler seems to be pretty popular around here. its what i use, perfect battery life / performance. but again, every phone is different so try a few out. are you just using venom tweaks to OC? check voltages under the CPU tab in tweaks.
I have mine on conservative and sio with values at 192-1350MHz for conserving my battery. However because you are checking for stability I would go with ondemand or intellidemand. Dial back the OC and go with default voltage, if you dial back the voltage that can make it unstable as well.
Yes I'm just using viper tweaks for the over clock. I'm wondering if I should use an app instead. I did revert the over clock back to 1.5 so we will see if that helps... The io schedule that we use is sio. The ones avaliable are noop, deadline, cfq, sio, and vr. I had her governor at intellidemand but changed it to lion heart cuz I thought maybe it would out less stress on the cpu... I also did fix permissions and sip aligned so ill keep u guys posted if this worked. Again thanks u guys for the help.
Sent from my Nexus 7 using xda app-developers app
cables2590 said:
Yes I'm just using viper tweaks for the over clock. I'm wondering if I should use an app instead. I did revert the over clock back to 1.5 so we will see if that helps... The io schedule that we use is sio. The ones avaliable are noop, deadline, cfq, sio, and vr. I had her governor at intellidemand but changed it to lion heart cuz I thought maybe it would out less stress on the cpu... I also did fix permissions and sip aligned so ill keep u guys posted if this worked. Again thanks u guys for the help.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Your welcome! hit thanks if we helped you out. SIO is a good one to stick with. Also, I haven't found much difference between built-in and apps as long as your settings stick and run at boot. The apps will have more features but should do the same thing. :good:
jo3holl4nd said:
Your welcome! hit thanks if we helped you out. SIO is a good one to stick with. Also, I haven't found much difference between built-in and apps as long as your settings stick and run at boot. The apps will have more features but should do the same thing. :good:
Click to expand...
Click to collapse
agreed. i would say stick to venom tweaks (as joe said, if it sticks. it should though) . other apps like set cpu and kernel tuner seem to have trouble getting our min frequencies to stick. the one thing kernel tuner is good for is it gives you the ability to change both governors. as of right now your second core governor is probably set to badass with no way of changing other than kernel tuner. if you flash the zip in the post below itll make it so the governor setting you select in venom tweaks applies to BOTH governors. hopefully that makes sense? just figured id let you know, could possibly help with stability/performance. :good:
Genetic517 said:
agreed. i would say stick to venom tweaks (as joe said, if it sticks. it should though) . other apps like set cpu and kernel tuner seem to have trouble getting our min frequencies to stick. the one thing kernel tuner is good for is it gives you the ability to change both governors. as of right now your second core governor is probably set to badass with no way of changing other than kernel tuner. if you flash the zip in the post below itll make it so the governor setting you select in venom tweaks applies to BOTH governors. hopefully that makes sense? just figured id let you know, could possibly help with stability/performance. :good:
Click to expand...
Click to collapse
Yeah I would like to flash the zip to see if that helps... So far I've done all what u have said and no reboots
Sent from my Nexus 7 using xda app-developers app
wow man i completely failed to post the link :laugh: . sorry about that, here you go.
http://forum.xda-developers.com/showpost.php?p=34214493&postcount=4201
edit: make sure to hit thanks on turges post in the viper thread, he deserves all the credit =p
I can't seem to get my Min/Max CPU frequencies to stay locked in regardless of Governor or IO Scheduler I use. I can't figure out why ig s doing this. I've never had a problem before. I am running everything stock right now except cot Root and Custom recovery obviously. But other then that. The phone is stock rom/kernel.
Can someone help me figure this out. It keeps setting my min frequency at over 1Ghz, which I obviously want it to be able to drop down more then that so I can save battery life.
Any ideas?
Silicon Knight said:
I can't seem to get my Min/Max CPU frequencies to stay locked in regardless of Governor or IO Scheduler I use. I can't figure out why ig s doing this. I've never had a problem before. I am running everything stock right now except cot Root and Custom recovery obviously. But other then that. The phone is stock rom/kernel.
Can someone help me figure this out. It keeps setting my min frequency at over 1Ghz, which I obviously want it to be able to drop down more then that so I can save battery life.
Any ideas?
Click to expand...
Click to collapse
do you have busybox installed? im sure that your cpu control app needs it. grab the busybox app by stericson, install it, open it, then install busybox. check if your cpu speed sticks. if it still doesnt, could just be mpdecision. then it would have to be disabled.
Yea I have busybox installed. Its always one of the first things I do. This isn't my first time modding a phone lol I've been modding phones since back when the Droid 2 Global first came out. Even started developing my first App and Custom ROM recently.
I use Jrummy's Busybox Pro app tho.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Mpdecision. I've seen that in FKU, I can't remember off the top of my head what that controls. I thought it had to do with thermal settings for the CPU
Sent from my Nexus 5 using XDA Premium 4 mobile app
It is mpdecision. Its supposed to make the launcher smoother.
Some kernels allow "stop mpdecision" from terminal.. or in chaos kernel, dev got mpdecision to pretty much boosting min frequency
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
I thought I had seen Mpdecision controls in the FKU app, but I musta been thinking of something else cause I can't seem to find it now. I just flashed Franco Kernel r32, and Now it seems to be keeping my Min/Max Freq locked to where I set them. So the issue seems to be fixed on its own.
I have the governor set to interactive and IO set to Row. Still learning about what IO scheduling does so I just keep that to whatever the kernel has it at by default.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Here's a screenshot
Yes faux used to have mpdecision controlsw. I haven't used it or a while though
This isn't really a solution more just avoiding the problem on your current kernel, but if you want to do this I recommend Chaos kernel :http://forum.xda-developers.com/showthread.php?t=2551441 Comes with the NXT app that allows a lot of tweaks to the CPU, GPU, memory, and so on.
mistahseller said:
This isn't really a solution more just avoiding the problem on your current kernel, but if you want to do this I recommend Chaos kernel :http://forum.xda-developers.com/showthread.php?t=2551441 Comes with the NXT app that allows a lot of tweaks to the CPU, GPU, memory, and so on.
Click to expand...
Click to collapse
Thanks for the link, so far I got it working alright ever since I flash the latest Franco kernel. Got max set to 1958Mhz & Min @ 422Mhz with the voltage dropped by 25 from stock which at 1958Mhz, the voltage is 945mv. So yes everything is staying to where I set it now. If I have any issues again tho I will try the idea in the link.
Thanks to everyone else for the replies as well
Sent from my Nexus 5 using XDA Premium 4 mobile app