[Announcement/Update] SetCPU Profiles w/ Manhattan Kernel - Vibrant Android Development

First of all, for anyone who has not yet tried the new Manhattan Project 1.6ghz kernel by Team Whiskey, i suggest you do so (http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=821514). It is currently in alpha but so far has gotten outstanding feedback. Ive personally been running it and I'm not looking back.
Up until now its been well known that SetCPU profiles not only dont work on our phone, but also causes crashes and severe instability. However, SINCE I FLASHED THIS NEW KERNEL (and running Bionix Fusion 1.1), I have successfully profiled my phone. Here is what I've been running all day with absolutely no issues, and my phone running like LIGHTNING:
Main: 1600-200 Conserv.
Screen Off: 200-200 Conserv.
Temp > 50: 800-200 Conserv.
I posted these results in the kernel forum, but I also wanted to post them here for everyone to see because i know that the lack of SetCPU profiles has been a major complaint around here. If anyone would like to try this out and verify that it works for them also with this kernel, please post here, so everyone can finally enjoy the beauty of overclocking AND underclocking.
Once again, I'm running Manhattan Project Kernel and Bionix Fusion 1.1

Outstanding!

Appreciate the profiles. Should be a great help. I personally lowered my Temp to 40c but thats just my opinion

Excited to get the running will tell results soon!

So had my phone sitting for a bit, it became unresponsive and i think it had something to do with the sleep profile. I went ahead and changed it to 400/200 conserv for testing.

Awesome. But is the set on boot option still not working?
Oh and just an educated guess bit I would figure no Voodoo on this kernel. So disabling just in case before I update

YatimaMeiji said:
Awesome. But is the set on boot option still not working?
Click to expand...
Click to collapse
i dont even bother, its not really needed....even if its unchecked yoru settings are preserbed upon reboot
----------------
UPDATE #2: after 5 hours of no problems my phone finally started crashing, so i have may have spoken prematurely. But I'm stubborn, so Im still gonna try every damn combination possible until my phone tells me to go f*ck myself haha

I will post my feedback as well...
OP, are you running any lag fixes?

drizze99 said:
I will post my feedback as well...
OP, are you running any lag fixes?
Click to expand...
Click to collapse
OCLF Ext2 v2.2
--------
I'm also trying "Overclock Widget" to see if i get better results
As much as I love Overclocking to 1600ghz, my it is beautiful....id also feel much more comfortable being able to underclock when its sleeping.........this is probably a wild goose chase, but i dont care, im bored at work

With screen off 200/200, phone does not wake up, changed to 400/200, still no wake up. Both set to conservative. Disabling profiles for now.
EDIT: Found the problem, if you enable Performance scaling on the main tab, and switch it back to conservative, it really doesn't switch. This is what was causing my Vibrant to not wake up! I had to set it to on-demand, leave setCPU and switch it to conservative, before it would stick. Re-testing 200/200 screen off.

TopShelf10 said:
OCLF Ext2 v2.2
--------
I'm also trying "Overclock Widget" to see if i get better results
As much as I love Overclocking to 1600ghz, my it is beautiful....id also feel much more comfortable being able to underclock when its sleeping.........this is probably a wild goose chase, but i dont care, im bored at work
Click to expand...
Click to collapse
you realize that the phone does this automatically, right?
turn on set cpu with nothing going on in the background and just let the phone sit. it will drop down to 200mhz and stay there.
the profile setting for temp is a good idea, but screen off is just going to cause lag issues. if the screen is off and the phone isnt doing a sync or something else, you can bet its probably chilling out at 200mhz

jnp1974 said:
With screen off 200/200, phone does not wake up, changed to 400/200, still no wake up. Both set to conservative. Disabling profiles for now.
EDIT: Found the problem, if you enable Performance scaling on the main tab, and switch it back to conservative, it really doesn't switch. This is what was causing my Vibrant to not wake up! I had to set it to on-demand, leave setCPU and switch it to conservative, before it would stick. Re-testing 200/200 screen off.
Click to expand...
Click to collapse
probably not going to help, but i certainly hope it does!!!

TopShelf10 said:
probably not going to help, but i certainly hope it does!!!
Click to expand...
Click to collapse
Thanks for the hope, it worked. YEAH! It now wakes when it should, and profiles appear to be working just fine.
EDIT: I was testing different benchmarks with scaling on conservative, on-demand and performance to see if they altered my benchmark results. The difference was minimal, but I forgot to change scaling back to conservative and it wouldn't wake. When I pulled the battery, rebooted and checked SetCPU, it said conservative, but was stuck on performance. Changed to on-demand, left SetCPU, back in and changed to Conservative. It worked.

jnp1974 said:
Thanks for the hope, it worked. YEAH! It now wakes when it should, and profiles appear to be working just fine.
Click to expand...
Click to collapse
dont be fooled, it can often work for a while before it shows its ugly side, be patient

I've never had any problems with profiles? The only thing that needs to be kept in mind is that if you check "set on boot" you'll get errors. Anything but "conservative" for scaling will give you errors.
edit: for screen off don't be so stingy trying to set it to 200/200, if you need more battery life then get a bigger battery or spare batteries or Juice Defender , I usually set it to 200/800 and I have no issues.

TopShelf10 said:
dont be fooled, it can often work for a while before it shows its ugly side, be patient
Click to expand...
Click to collapse
I was fooled, ditching profiles altogether, boo

Can conferm that both profiles and set on boot work.
Sent from my Vibrant.

Mouahmong said:
I've never had any problems with profiles? The only thing that needs to be kept in mind is that if you check "set on boot" you'll get errors. Anything but "conservative" for scaling will give you errors.
Click to expand...
Click to collapse
i never check set on boot....what are your profile settings and what ROM/kernel are you running?

OK, I don't have mine OCLF yet but so far so good.
I have run Sleep profiles of 200/200 and 400/200 and the phone wakes up every time. I have gotten a txt message as well during my test and the screen lit up just like Bionix should! Will continue to kep messing with it....

turbosix said:
you realize that the phone does this automatically, right?
turn on set cpu with nothing going on in the background and just let the phone sit. it will drop down to 200mhz and stay there.
the profile setting for temp is a good idea, but screen off is just going to cause lag issues. if the screen is off and the phone isnt doing a sync or something else, you can bet its probably chilling out at 200mhz
Click to expand...
Click to collapse
if it does so automatically then why is there an option to adjust "screen off" values?
Setcpu automatically scales between the high/low you set. SO if you let the main value stay at 1600-100..when the screen is off it will scale at a lower value of course cus you're not using the phone..but it wont stay at 200, because it has a Max of 1600! So depending on background processes it could scale back up to 4 or even 600 while screen is off
MY suggestions:
Download superpower battery saver from market, tweak to turn data on/off with screen and force ondemand cpu scaling
Download Autokiller--donate to get extra functions-- and set the value to Extreme or Ultimate when screen is off and Moderate or Optimal when it is on
I did that without setcpu profiles and it took 4 1/2 hrs to go from 81 % to 70
Im running Fusion 1.1 w/ Manhattan Project

Related

overclock widget

worked great for a while then kept force closeing anyone haveing problems??
It seems to be working fine for me. One thing is that when I set the clock to 128 or something, the status displayed on the widget still shows 527. The performance is significantly slowed so I assume it's doing it's job.
Overall I think it's a nice little widget. Great for maxing out performance, and maxing battery life by limiting performance.
Phone:
Black G1
JF 1.51
Yup...me too
I will make the change but it sometimes does not refresh the gui. It will also not work if you reboot. (if i remember correctly) also tons of force closes. I am on 6.01 and have tried JF1.5 and am curently on HERO but have not had success with the widgets on the build yet so I dont have a confirmation.
Could someone post the previous version of this app please? The updated version on the market shows "problem loading gadget" on the Hero rom when you add it to the screen..previous versions worked without any problems. Thanks in advance.
edit: nm..fixed it..just had to run the odex optimization script and all is good again
just use SETCPU from market...its more stable thank open overclock......at least it doesnt unclock back to 384mhz
what is a good configeration for over clock..i dotn want to mess up my phone??
I was thinking the same and should I have it on always max. Or what?
I've got mine set to 128Mhz min and 527Mhz max, it has drastically increased my battery life. Batter life barely drops 1% overnight.
Anyone have the Version before the 1.7 update. The new update doesnt seem to work on hero w/ Rosie.
You can grab the 1.6 apk from the Dev's Google Site (check the Files section).
1.7 doesn't work with Ion for me either
zgmf-x322a said:
just use SETCPU from market...its more stable thank open overclock......at least it doesnt unclock back to 384mhz
Click to expand...
Click to collapse
Did setcpu support choosing a different freq. when the screen is off? Setting that to 128 - 245 has helped my battery greatly. One question for anyone using OC apps, does your phones at any time run at a lower freq than what's specified as the maximum? I just set my phone to (with the screen on) to 128 - 384 because if I put it all the way to 527 it won't come down (unless I turn the screen off).
masr1979 said:
Did setcpu support choosing a different freq. when the screen is off? Setting that to 128 - 245 has helped my battery greatly. One question for anyone using OC apps, does your phones at any time run at a lower freq than what's specified as the maximum? I just set my phone to (with the screen on) to 128 - 384 because if I put it all the way to 527 it won't come down (unless I turn the screen off).
Click to expand...
Click to collapse
1.2.0 does not currently.
I swear, the next version will (I swear!). I'll also add some basic battery profiles (if battery is less than 50%, set the speed to something) and a profile for charging. Of course, it'll always be free here (link in my sig).
does your phones at any time run at a lower freq than what's specified as the maximum? I just set my phone to (with the screen on) to 128 - 384 because if I put it all the way to 527 it won't come down (unless I turn the screen off).
Click to expand...
Click to collapse
Yes. You can usually catch it by doing cat proc/cpuinfo in ADB. It depends on what the phone is doing at that moment.
That's strange it doesn't work well with hero. Since I'm using haykuros adp1.5hr3 it workd beautifully, but the regular overclocker app doesn't even budge and I uninstalled that..idk tho, probably a build issue as far as I'm guessing.
IronCross1788 said:
That's strange it doesn't work well with hero. Since I'm using haykuros adp1.5hr3 it workd beautifully, but the regular overclocker app doesn't even budge and I uninstalled that..idk tho, probably a build issue as far as I'm guessing.
Click to expand...
Click to collapse
The creator of the original Overclock app hasn't updated his application for even Cupcake build support yet. I thought he removed it from the market.
masr1979 said:
Did setcpu support choosing a different freq. when the screen is off? Setting that to 128 - 245 has helped my battery greatly. One question for anyone using OC apps, does your phones at any time run at a lower freq than what's specified as the maximum? I just set my phone to (with the screen on) to 128 - 384 because if I put it all the way to 527 it won't come down (unless I turn the screen off).
Click to expand...
Click to collapse
Yeah NeoBlade (thanks!) gave me the tip on that one yesterday. Seems to be helping a ton.
Min384Max527
Screen off Min128Max245
I can't find Overclock Widget in Market, was it removed?
I have the Overclock Widget and my question is, is it bad for my phone that while my screen is on i have it a min 527 max 527 then while screen off min 128 max 245... I've noticed that phone charges last longer but the useage of going back and forth determental to the phone? Thanks
coolbho3000 said:
1.2.0 does not currently.
I swear, the next version will (I swear!). I'll also add some basic battery profiles (if battery is less than 50%, set the speed to something) and a profile for charging. Of course, it'll always be free here (link in my sig).
Yes. You can usually catch it by doing cat proc/cpuinfo in ADB. It depends on what the phone is doing at that moment.
Click to expand...
Click to collapse
Thanks, that would be of great help. Specially the battery profile settings. If you could also put a monitor, be it a widget or something on the notification bar it would be beyond awesome, or maybe a just notification of when the speed is changed and to what it was changed to.
Does anyobdy know if this SETCPU works on Hero ?
And must the app be on after i set the clock or can i close the app after ?
*bump* need to know

[Q] Why does my hero keep restarting? (Gingerbread 2.3.2 aosp)

It always restarts automatically, when i make a call, the call just freezes and when i turn the phone on from standby to see what happen, well you guessed it, it restarts! its pretty annoying i went through 2 batteries today in 8 hours, because of the restarts. please help!
If your using the stock kernel I think its overclocked to 768 not sure though. Try one of dec's 691 kernel the #589 is my recommendation. Hope it helps good luck.
Root-Hack-Mod-Always™
jlopez512 said:
It always restarts automatically, when i make a call, the call just freezes and when i turn the phone on from standby to see what happen, well you guessed it, it restarts! its pretty annoying i went through 2 batteries today in 8 hours, because of the restarts. please help!
Click to expand...
Click to collapse
There could be a lot of things happening. The most common is that your running a clock speed higher than that which your phone can handle. Not all heros are created equal, mine for instance starts rebooting at anything higher than 691. Try a different kernel or if using setcpu or over clocking widget to lower your upper end clock speed. Your phone freezing when coming out of standby can mean your lower clock speed is too low. ASOPGB has JIT enabled by default as well. Go into the settings and turn it off, then reboot. You will just have to play until you find out what works for you. Good luck!
runngwlf said:
There could be a lot of things happening. The most common is that your running a clock speed higher than that which your phone can handle. Not all heros are created equal, mine for instance starts rebooting at anything higher than 691. Try a different kernel or if using setcpu or over clocking widget to lower your upper end clock speed. Your phone freezing when coming out of standby can mean your lower clock speed is too low. ASOPGB has JIT enabled by default as well. Go into the settings and turn it off, then reboot. You will just have to play until you find out what works for you. Good luck!
Click to expand...
Click to collapse
Set cpu or similar will not fix the issue, laie was right a capped 691 kernel is needed and probably a capped recovery as well. Btw jit is no longer default in gb, and jit would not cause reboots anyway.
sent from my hero, which no longer sucks ass
il Duce said:
Set cpu or similar will not fix the issue, laie was right a capped 691 kernel is needed and probably a capped recovery as well. Btw jit is no longer default in gb, and jit would not cause reboots anyway.
sent from my hero, which no longer sucks ass
Click to expand...
Click to collapse
Ahh thanks for the info, I had not gotten through all the new posts on the other ASOP GB threads. Good to know though. I have no tried out the rom, I plan to this weekend and my phone does NOT like kernels that clock above 691.

[Kernel] Dragon TEST... SetCPU profiles support...

http://www.tabbal.net/files/Dragon-Kernel-Voodoo-OC-v3.3-T1.zip
Dragon 3.2 w/ a fix that seems to work for setCPU screen off profiles setting the CPU to low values. Please note: The max freq in setCPU for that profile is what will be used, no scaling. I set it to 200Mhz and it's working fine every time I fire it back up.
The original patch is from here: https://review.source.android.com//#change,20804
Created by coolbho3k for the Nexus S, I backported it to Froyo. If we get good test reports from others, I'll push the changes to github tomorrow so other devs can use it.
When testing, please either use known good OC/UV settings, or don't OC/UV at all. Phantom OC/UV crashes won't help us know if this is working well for others. I've tested it with and without, turning my phone on/off like a madman... working fine so far.
Hmmm... early reports aren't looking good. Perhaps something isn't quite right. lol... Be warned if you try it, read all the comments. Might have to declare this one a fail. Too bad the NS cpu-freq driver is so different.. maybe I'll try pulling the whole thing over..
Downloading now report back tomorrow! This sounds promising.
Sent from my SGH-T959 using XDA App
Will test as soon as i get mine back to stock! Its just what I felt like doing today.
I did have a question..
Do we need to adjust it to say.. performance,on demand powersave? or will it just default?
just flashed it on my phone its been running warm hot even then after about 10 15mins of running it reboots
coolkid893 said:
just flashed it on my phone its been running warm hot even then after about 10 15mins of running it reboots
Click to expand...
Click to collapse
wow that can't be good. Sounds like the phone is overheating..
PaiPiePia said:
wow that can't be good. Sounds like the phone is overheating..
Click to expand...
Click to collapse
ya i know an its not even o/c its set to only max at 800mhz lol i think im gonna reflash to 3.2 to be safe but its a step in the right direction good try
Ok Im gunna have to try and install setcpu first.. otherwise my phone loads and restarts a few minutes into being on the desktop.
Testing now, Just UV'ed my clocks, and now setting profiles.
Observation so far:
SetCPU, and Uvolting seems to lock up my phone, and cause a reboot, and phone is pretty warm/hot.
Confirmed I can not run this either.
Couldn't use it. Phone would shut off as soon as scanning started. Kept happening everytime I tried to start phone :¬( going back to 3.2 has been stable at 1.4 ghz.
Sent from my SGH-T959 using XDA App
junxracr said:
Couldn't use it. Phone would shut off as soon as scanning started. Kept happening everytime I tried to start phone :¬( going back to 3.2 has been stable at 1.4 ghz.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Im having better luck using profiles with 3.2 than with this one. I've been using set cpu since 3.2 came out with no problems @1.4 and on powersave when screen is off. I have made no changes to the UV settings.
yikes ! i smell quadrant score in few min lemme install it
Has anyone got a "kernel panic" on this before? I'm not sure what I could have done wrong.. had to Odin back to stock. Forgot to back up before I flashed, shame on me. lol.
kernel panic wipes your data ? everytime kernel panicked on me i just restarted =D
bartek25 said:
kernel panic wipes your data ? everytime kernel panicked on me i just restarted =D
Click to expand...
Click to collapse
Nah, it didn't wipe my data. I had to Odin back to stock because I couldn't go into Clockwork Mod Recovery Mode. It would go into Kernel Panic and it reset all my launcher settings....
Was running hot for me also. Back to stock and then to bionix .
I think that when you get things fine tuned you will have a great Kernal.

[MOD][KERNEL] Lazy - yet another CPUfreq governor

My last effort of improving the ondemand governor by implementing a dynamic sampling rate did not work out as I hoped. Thus I did switch back to ondemand and, with a sampling_rate of 40000 and an up_threshold of 80, XviD playback with MobyPlayer was fine and also FLAC playback with MortPlayer was ok. However, as Morfic and others have noted the GUI feels a bit sluggish with these settings and suggested to try a sampling_rate of 15000. I tried this before, however with a lower rate, playback with MobyPlayer has serious problems with cracks and stuttering sound. Exactly this was the motivation to try and implement this dynamic sampling rate in the first place.
So the question is, why does a lower sampling rate lead to these problems? Since a smaller sampling rate means a greater flexibility and responsiveness, missing the point in time when the frequency should be increase cannot be the cause. Also the polling function which determines the frequency change is relatively light-weight, thus the extra CPU load for calling this function more often should also not be the problem. The only reason I could think of was that maybe switching the CPU frequency at these fast rates might be the root of the problem.
Thus I took the ondemand governor and implemented an additional parameter 'min_timeinstate' defining a minimum time the CPU will stay in a certain frequency state before it will be allowed to switch frequencies again. This way one can have a fine grained polling by setting the sampling_rate to a low value without running into problems with these fast frequency changes.
I did some extensive testing with a sampling_rate of 10000, min_timeinstate of 40000 and up_threshold of 90 and FLAC, mp3 and video playback all seem to work flawlessly. So it seems the root of the problem was indeed that the CPU does not handle fast frequency changes well.
I tested several apps and games and so far I have not found anything that this governor cannot handle. Thus I dare to say that it seems to be the superior choice over ondemand.
Test it, torture it, try to break it - I am looking forward to your feedback.
Changes to the source: http://www.pastie.org/2586936
BUGFIX:
Fixed compilation error with 'lazy' chosen as default CPUfreq governor.
Bug fix: http://www.pastie.org/2587040
BUGFIX #2:
Added sysfs parameter 'screenoff_maxfreq' which when enabled will cause lazy to always select the maximum frequency while the screen is off.
Bugfix: http://www.pastie.org/2775900
No further patches will be published here. I have set up a git repo for all my tweaks. Each mod has its own branch to keep the tweaks cleanly separated and one can simply pull the latest patches from the corresponding branch.
https://github.com/Ezekeel/GLaDOS-nexus-s/tree/lazy
now this sounds interesting
Did you try building with lazy as default?
EDIT: builds fine as option, but not default. Too eager to try it to go fix code.
Oh, you are right. That does not work. I will fix it.
Bug fix: http://www.pastie.org/2587040
do we have to wait for this to be implemented in netarchy etc to use it .. ?
theallian said:
do we have to wait for this to be implemented in netarchy etc to use it .. ?
Click to expand...
Click to collapse
Yes, unless you can compile a kernel yourself you will have to wait. I do believe that there's a testing Trinity TEUV kernel by Morfic in his thread with the new governor as an option if you want it now.
theallian said:
do we have to wait for this to be implemented in netarchy etc to use it .. ?
Click to expand...
Click to collapse
Check trinity thread, there are 2 kernels with it and cooler colors, closer to voodoo punchy (if not exactly punchy)
Sent from my Nexus S using Tapatalk
awesome work ezekeel!
its running great here with the teuv kernel and the lazy governor. no complaints as of yet.
youll have to wait for it to be compiled into netarchy, or compile it yourself. you can try it already compiled into the trinity teuv kernel found here http://forum.xda-developers.com/showpost.php?p=17839805&postcount=4304
Yep it's working awesome so far. Using morfic's teuv with lazy gov.
Code:
diff --git a/include/linux/cpufreq.h b/include/linux/cpufreq.h
index 2c00088..b03d1e1 100644
--- a/include/linux/cpufreq.h
+++ b/include/linux/cpufreq.h
@@ -357,6 +357,9 @@ extern struct cpufreq_governor cpufreq_gov_performance;
#endif
#ifdef CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE
#define CPUFREQ_DEFAULT_GOVERNOR (&cpufreq_gov_performance)
+#elif defined(CONFIG_CPU_FREQ_DEFAULT_GOV_LAZY)
+extern struct cpufreq_governor cpufreq_gov_lazy;
+#define CPUFREQ_DEFAULT_GOVERNOR (&cpufreq_gov_lazy)
#elif defined(CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE)
extern struct cpufreq_governor cpufreq_gov_powersave;
#define CPUFREQ_DEFAULT_GOVERNOR (&cpufreq_gov_powersave)
seems to do the trick
Hi Ezekeel, an observation in the trinity thread mentioned that some games lagged really badly, i think it could be with too slow changes, due to your time delay feature. I'm not sure if it's feasible, but maybe a solution to this could be a dynamic time delay, longer for the lower frequencies (suited for music while screen off) and shorter for the higher frequency (for these intensive games).
Now I'm not a kernel guy, although I do wish to learn at some stage in the near future. This is just the product of some quick thinking, I have no idea if it is a workable theory or if it would just cause overhead and create more lag. Please let me know what you think though!
Sent from my Nexus S
Been running the TEUV kernel with the lazy governor on since last night and here are a few of my observations:
1) Amazing battery performance. During heavy use with pretty much everything on and the screen at maximum brightness, I lost a mere 6% over a 30 minute period. Turn the screen down and back to normal use? 1% over 2 hours. Not to mention the fact that for the first time in a very long time my phone charged to 99% and when pulled off the charger stayed there for a good amount of time.
2) Upon booting, things stutter a bit. Most likely due to the fact that a lot of things are trying to start fighting for resources and since its a UV kernel, there isn't as much power to go around. Its not horrible like using my MT3G was but its noticeable. Also, there is, again just after boot, about a .25 or .5 second delay between pressing icons and the subsequent action happening.
3) After that initial slowness, it runs extremely smoothly. Like buttah, as mike myers would say.
All in all, I'm quite fond of this governor. I've tried UV kernels before on my phone and it tends to dislike them. Like random reboots and random bootloop, dislike them. Perhaps its the rom, perhaps its morfic's coding, or perhaps its just the governor. Whatever it is the collaboration is absolutely phenomenal. Kudos.
Jonathon Grigg said:
Hi Ezekeel, an observation in the trinity thread mentioned that some games lagged really badly, i think it could be with too slow changes, due to your time delay feature. I'm not sure if it's feasible, but maybe a solution to this could be a dynamic time delay, longer for the lower frequencies (suited for music while screen off) and shorter for the higher frequency (for these intensive games).
Now I'm not a kernel guy, although I do wish to learn at some stage in the near future. This is just the product of some quick thinking, I have no idea if it is a workable theory or if it would just cause overhead and create more lag. Please let me know what you think though!
Sent from my Nexus S
Click to expand...
Click to collapse
I just downloaded and tried the two games which were mentioned in the Trinity thread, Fruit Ninja and Air Attack, and I am experiencing no problems at all with the reference kernel from my sig set to 100/800. So until more people report such problems I am inclined to believe that these are not directly related to the governor.
kenvan19 said:
2) Upon booting, things stutter a bit. Most likely due to the fact that a lot of things are trying to start fighting for resources and since its a UV kernel, there isn't as much power to go around. Its not horrible like using my MT3G was but its noticeable. Also, there is, again just after boot, about a .25 or .5 second delay between pressing icons and the subsequent action happening.
Click to expand...
Click to collapse
I think that is normal. The GUI starts up before all programs and settings are properly loaded. For example if I open the app drawer directly after boot, only the stock apps are visible and after some seconds all my apps appear one after another. It takes about 10s after the GUI has started until everything is setup.
Ezekeel said:
I just downloaded and tried the two games which were mentioned in the Trinity thread, Fruit Ninja and Air Attack, and I am experiencing no problems at all with the reference kernel from my sig set to 100/800. So until more people report such problems I am inclined to believe that these are not directly related to the governor.
I think that is normal. The GUI starts up before all programs and settings are properly loaded. For example if I open the app drawer directly after boot, only the stock apps are visible and after some seconds all my apps appear one after another. It takes about 10s after the GUI has started until everything is setup.
Click to expand...
Click to collapse
I personally think your new governor is working great. Only time will tell if its better on the battery. I really hope so. I'm hoping for at least another hour of use. is it possible?
Sent from my Nexus S using xda premium
dsellers2 said:
I personally think your new governor is working great. Only time will tell if its better on the battery. I really hope so. I'm hoping for at least another hour of use. is it possible?
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
I expect the battery runtime to be similar to ondemand. On the other hand, I have made the experience that modifying governors is a delicate business and seemingly small changes can have an unexpectedly large impact. So as you said, only time will tell.
If the sampling rate is 10000 and the min_timeinstate is 15000, will the governor not consider load changes until min time is over, but at the normal sampling intervals? Which would mean an essential 20000 in this state?
I was looking through the patch on pastie right now, but opera closed twice, so I figured I ask you instead.
Sent from my A501 using Tapatalk
morfic said:
If the sampling rate is 10000 and the min_timeinstate is 15000, will the governor not consider load changes until min time is over, but at the normal sampling intervals? Which would mean an essential 20000 in this state?
I was looking through the patch on pastie right now, but opera closed twice, so I figured I ask you instead.
Sent from my A501 using Tapatalk
Click to expand...
Click to collapse
When the frequency is changed the next sampling will be performed min_timeinstate µs later, after that sampling with the normal rate is resumed. So in your example, the first sampling after a frequency change will be performed after 15000 µs, after that every 10000 µs.
Hi EZkeel your governor implemented the latest TEUV kernel has helped improved my battery life by close to 20!, was getting around 10hrs of battery with heavy use. About 3+hrs of screen time, display set to auto. Was able to run for 13hrs today.
One day of testing so far but I haven't seen my phone charge to 99% or last over 13hrs until I put the latest TEUV kernel with lazy in. Will continue testing throughout the week. No compatibility issues with the apps so far. Was running on demand governor previously and with the previous version of TEUV
Thanks for your work on the governor development.
robin_77 said:
Hi EZkeel your governor implemented the latest TEUV kernel has helped improved my battery life by close to 20!, was getting around 10hrs of battery with heavy use. About 3+hrs of screen time, display set to auto. Was able to run for 13hrs today.
One day of testing so far but I haven't seen my phone charge to 99% or last over 13hrs until I put the latest TEUV kernel with lazy in. Will continue testing throughout the week. No compatibility issues with the apps so far. Was running on demand governor previously and with the previous version of TEUV
Thanks for your work on the governor development.
Click to expand...
Click to collapse
Looking at your screen shots vs what mine is and my 2nd most is gallery. Very confused as to why this is
Sent from my Nexus S 4G using xda premium
you may have a corrupt media file , so everytime your device syncs it gets stuck. clear your files.
turn off device, remove battery for 2mins.; try again
possibly flag the directories you don't want scanned with .nomedia file (there's an app to do this)
anyways excellent job Ezekeel, 2nd day and lets see what happens with battery life.

Nexus 6 drops to 1ghz gaming

Hey guys so I got this problem I'm wondering if anyone else has gotten it because it is a little frustrating.
OK so my nexus 6 when I game it drops to 1ghz all 4 cores. I have chroma and elementalx. I've tried turning off thermal in kernel auditor and I have used core CPU control and system monitor and it goes fine for fee few seconds then drops down to 1ghz .
Its really annoying I really wish someone could help me. Thanks I'd advance.
Power2daplayer said:
Hey guys so I got this problem I'm wondering if anyone else has gotten it because it is a little frustrating.
OK so my nexus 6 when I game it drops to 1ghz all 4 cores. I have chroma and elementalx. I've tried turning off thermal in kernel auditor and I have used core CPU control and system monitor and it goes fine for fee few seconds then drops down to 1ghz .
Its really annoying I really wish someone could help me. Thanks I'd advance.
Click to expand...
Click to collapse
change how your CPU is set up(by changing your governor/scheduler), and disable mpdecision. its very simple to get your CPU to work as you want it to, just learn what the different governors and their option do.
simms22 said:
change how your CPU is set up(by changing your governor/scheduler), and disable mpdecision. its very simple to get your CPU to work as you want it to, just learn what the different governors and their option do.
Click to expand...
Click to collapse
I have it on elemental governor, I heard you need busybox for it to stick but i dont know.
Sometimes I try to change the max frequency but it just won't change, the frequency's go all over the place haha.
Do you know which kernel is best for gaming on the nexus 6 ?
Power2daplayer said:
I have it on elemental governor, I heard you need busybox for it to stick but i dont know.
Sometimes I try to change the max frequency but it just won't change, the frequency's go all over the place haha.
Do you know which kernel is best for gaming on the nexus 6 ?
Click to expand...
Click to collapse
elemental is fine, probably do need busybox. but it sounds as you need to disable mpdecision.
BCL driver.
Check it out HERE.
You can even follow the instructions there to disable it.
Or you can install singularity kernel and the singularity kernel app with it. Singularity kernel has a option to disable it, along with a TON of other features.
The frequency drops because the CPU ***TEMPERATURE*** gets too high. Don't mess with it unless you like instability and "random" reboots.
doitright said:
The frequency drops because the CPU ***TEMPERATURE*** gets too high. Don't mess with it unless you like instability and "random" reboots.
Click to expand...
Click to collapse
funny, i disable thermal throttle every single time i boot up, since nov 2014, i my n6 doesnt get instability, and doent reboot.
simms22 said:
funny, i disable thermal throttle every single time i boot up, since nov 2014, i my n6 doesnt get instability, and doent reboot.
Click to expand...
Click to collapse
We've already gone over this and confirmed that your observations are incomplete.

Categories

Resources