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.
Related
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
I saw that they have SetCPU working with the Hummingbird in the Nexus S; I was wondering if this means there is a possibility that SetCPU overclock support may be coming for the Captivate as well?
it must be supported by kernel...
It already works?? But most of us use voltage control and you have to flash the right kernel
Sent from my SGH-I897 using XDA App
All the OC-supporting kernels I saw said not to use SetCPU...
Thread moved to Q&A.
Only person that would know that answer for sure would be supercurio as he's doing the kernel for both the i9000 and the Captivate.
I'd suggest going to his i9000 thread or checking his twitter to find out.
set cpu works but is not recomended with i9000 kernels though i dont know why. on the threads for unhelpfuls kernels there was talk about it messing up the interneal clock causing the time on texts to be off but that happened to me with the stock kernel and no use of set cpu when using set cpu the problem was no better or worse, therewas also non specific talk of it not playing nice with our phones.
i havent tried it on an i9000 kernel because there is no use for it. the voltage control app is capable of setting the max clock speed. set cpu could still be used for profiles i guess but i never saw the need for a profile, if you are running such a fine line that stability is effected by heat and charging status you might want a little less overclock. over/under clocking has very little effect on battery life do to cpu scaling. under clocking just makes it take longer to get tasks done keeping the cpu from sleeping, really not as big an effect on battery life as you'd expect. so that leaves you with the governor settings which our kernels dont support very well, you can try different kernels with different governor settings built in. perhaps the aosp kernels do better. i dont know becasue there are too many problems with cyanogen mod and the gingerbread port right now.
As mentioned it has worked for some time. But we've been recommended not to use it. I'd love to know why just out of curiousity.
Hello, i recently rooted my phone with the bootloader still locker. The main reason for me to do this was to remove the scrolling lag i noticed.
So after the rooting i installed pimp my z1 and changed the governors of my cpu to performance. After that i started testing again and the lag was gone! No more jitter and stutter anymore. I tried the other governors but they all increased the lag, with powersave being the worst.
The default setting is ondemand, which works quite well, but gives a little lag on apps like phonebook and gmail. Although i guess it's better for the battery etc. But seeing this, i started wondering why the default settings aren't working well, while the hardware really is good! Is that sony failing at improving the performance of the roms or making it work smooth with kitkat? Or what is the cause for this situation? Also because i'm a bit scared that using performance all the time will reduce the battery or even wear the hardware down faster.
Is not Sony fault, you are messing around with Custom settings and Apps. BTW, Pimp my Z1 should be coordinate with Custom Kernel like the Doom one, but you still on Locked Bootloader then you are working on Stock one which do not have the option to be tweeked. In this case half of the Setting in Pimp my Z1 will not work or will not work properly, so do not complain. Try just to find the best settings with what you got.
eclyptos said:
Is not Sony fault, you are messing around with Custom settings and Apps. BTW, Pimp my Z1 should be coordinate with Custom Kernel like the Doom one, but you still on Locked Bootloader then you are working on Stock one which do not have the option to be tweeked. In this case half of the Setting in Pimp my Z1 will not work or will not work properly, so do not complain. Try just to find the best settings with what you got.
Click to expand...
Click to collapse
Yeah, that's why i posted this topic. If i use pimp my z1 (or i guess any other kernel tuner/oc app) and change governor to performance, all lag is gone. While using unrooted stock rom with standard governors gives quite some lag and stutters when scrolling through standard apps like phone and gmail. I'm just trying to find the cause of that. Also because i can't believe that this hardware has problems simple actions like this scrolling.
I also read that on other devices like the xperia z people have problems with lag in the ui like this. So maybe it's also because of android 4.4 or something.
saintgein said:
Hello, i recently rooted my phone with the bootloader still locker. The main reason for me to do this was to remove the scrolling lag i noticed.
So after the rooting i installed pimp my z1 and changed the governors of my cpu to performance. After that i started testing again and the lag was gone! No more jitter and stutter anymore. I tried the other governors but they all increased the lag, with powersave being the worst.
The default setting is ondemand, which works quite well, but gives a little lag on apps like phonebook and gmail. Although i guess it's better for the battery etc. But seeing this, i started wondering why the default settings aren't working well, while the hardware really is good! Is that sony failing at improving the performance of the roms or making it work smooth with kitkat? Or what is the cause for this situation? Also because i'm a bit scared that using performance all the time will reduce the battery or even wear the hardware down faster.
Click to expand...
Click to collapse
The "performance" governor is the least intelligent governor there is. It has no clocking logic. All it does is "keep CPU at maximum speed at all times". I'm sure you can see why this is a bad idea on a device that can (and does) overheat when the CPU is at high clocks, and where the power consumption should be restricted to make the battery last more. You shouldn't use performance as your day to day governor.
But it is smoother, of course. Since there is no logic, it runs at full speed all the time, while other governors only drive your CPU to 2.3GHz when it's absolutely necessary. 1GHz is more than enough for the UI (and this is in fact how "project butter" is implemented on Snapdragon phones: when there is a finger on the screen, the minimum clock goes up to something around 1GHz). The fact that you can detect lags mean that Sony didn't go nuclear and just make the CPU run too fast.
saintgein said:
Hello, i recently rooted my phone with the bootloader still locker. The main reason for me to do this was to remove the scrolling lag i noticed.
So after the rooting i installed pimp my z1 and changed the governors of my cpu to performance. After that i started testing again and the lag was gone! No more jitter and stutter anymore. I tried the other governors but they all increased the lag, with powersave being the worst.
The default setting is ondemand, which works quite well, but gives a little lag on apps like phonebook and gmail. Although i guess it's better for the battery etc. But seeing this, i started wondering why the default settings aren't working well, while the hardware really is good! Is that sony failing at improving the performance of the roms or making it work smooth with kitkat? Or what is the cause for this situation? Also because i'm a bit scared that using performance all the time will reduce the battery or even wear the hardware down faster.
Click to expand...
Click to collapse
The best governor for me is SmartassV2 set to 1 core and the rest on either ondemand or interactive. Use Doomlords kernel along with Pimp My Z1 app for per core governors. I'm not sure of you can do that for UB. If you cant, then just change Rom for me ihackers is the smooth on stock governor, which i think is onDemand - im currently using CM11 just moved from iHackers 4.1 2 days ago
yup owns Z1 and stuff. Also if I've helped you don't forget to hit THANKS - actions speak louder that words.
Steve_max said:
The "performance" governor is the least intelligent governor there is. It has no clocking logic. All it does is "keep CPU at maximum speed at all times". I'm sure you can see why this is a bad idea on a device that can (and does) overheat when the CPU is at high clocks, and where the power consumption should be restricted to make the battery last more. You shouldn't use performance as your day to day governor.
But it is smoother, of course. Since there is no logic, it runs at full speed all the time, while other governors only drive your CPU to 2.3GHz when it's absolutely necessary. 1GHz is more than enough for the UI (and this is in fact how "project butter" is implemented on Snapdragon phones: when there is a finger on the screen, the minimum clock goes up to something around 1GHz). The fact that you can detect lags mean that Sony didn't go nuclear and just make the CPU run too fast.
Click to expand...
Click to collapse
So getting the minimum clock to about 1ghz using interactive governor should be enough?
RealiableCandy4 said:
The best governor for me is SmartassV2 set to 1 core and the rest on either ondemand or interactive. Use Doomlords kernel along with Pimp My Z1 app for per core governors. I'm not sure of you can do that for UB. If you cant, then just change Rom for me ihackers is the smooth on stock governor, which i think is onDemand - im currently using CM11 just moved from iHackers 4.1 2 days ago
yup owns Z1 and stuff. Also if I've helped you don't forget to hit THANKS - actions speak louder that words.
Click to expand...
Click to collapse
I'm on a locked bootloader like i said in the op.
saintgein said:
Hello
So after the rooting i installed pimp my z1 and changed the governors of my cpu to performance. ....Also because i'm a bit scared that using performance all the time will reduce the battery or even wear the hardware down faster.
Click to expand...
Click to collapse
Wow, if you use performance all the time then your CPU is at max all the time. No matter what you are doing, no matter if your screen is off or if you have just put to one side...
It will kill your battery and burn out hardware very quick.
gregbradley said:
Wow, if you use performance all the time then your CPU is at max all the time. No matter what you are doing, no matter if your screen is off or if you have just put to one side...
It will kill your battery and burn out hardware very quick.
Click to expand...
Click to collapse
I got that, that's why i'm looking for better ways to do that. It just doesn't feel right that i have to do stuff like that to get a smooth working ui. Maybe i'm a perfectionist, but this s800 hardware should be able to do the call log/phonebook and gmail without stuttering right?
I'm using interactive governor atm with minimum clock 600. I notice that helps a bit already.
So I'm having from the beginning extreme problems with stuttering and lag and couldn't really pinpoint it. Benchmarks went great and apps run good but not the animations and scrolling. Perticular on the homescreen, really really bad.
I installed Kernel auditor and looked at the stats and was quite baffled that mpdecision trottled down to one core. Thats not usual. Under Hotplug it was surpisingly disabled and switching it on did nothing, it just reverted back itself. I fiddled around when suddenly two cores stay on the whole time, like i experienced in the past from this hotplug. This was after running Antutu. I was like, naaah, this can't be it.
Looking in Kernel auditor the switch was suddenly on. I'm like wtf is going on here. What is causing this? Am i the only one that notices the stutter on a phone that got shipped thousands of times and praised in many reviews?? This can't be it. So i switched it on and off and then it goes. Only one core...
Switched it off then rebooted and guess what? 2 cores.
Please explain what is causing this cause i don't know what is going on
Added a little touchboost and now its pretty on par with the smoothness on my old Galaxy S5, but to be it would need a GPU touch boost too.
EDIT:
It's like i would enable this special function in stamina to lower the performance, exactly like that. I would be interested in other people having the same problems as i have!
EDIT2:
Maybe GPU acceleration is not in full effect? Using devloper settings i cant let me show what is rendered with the gpu. It just doesn't flash up.
Noone?
I've been having this problem too, on CM12. Sometimes I could go a couple days after a fresh flash with butter smooth animations, then it would revert to stuttery animation
zander21510 said:
I've been having this problem too, on CM12. Sometimes I could go a couple days after a fresh flash with butter smooth animations, then it would revert to stuttery animation
Click to expand...
Click to collapse
Interesting... but they're using different kernels. I first thought they tweaked the hotplug to be more aggressive, or something in the phone itself triggers that to get more battery life for sacrificing user experience... i dont know but for now its smooth even when i tame the interactive governer.
My S5 didn't had any of these problems. CM12 was extremely smooth but they have good custom kernel. I still think that somehow gpu rendering is borked...
boilavera1980 said:
Interesting... but they're using different kernels. I first thought they tweaked the hotplug to be more aggressive, or something in the phone itself triggers that to get more battery life for sacrificing user experience... i dont know but for now its smooth even when i tame the interactive governer.
My S5 didn't had any of these problems. CM12 was extremely smooth but they have good custom kernel. I still think that somehow gpu rendering is borked...
Click to expand...
Click to collapse
So what i did now to test is that i enabled the "old" hotplugging where it goes down to one core, even enabled core parking, but gave it a near 2ghz touch boost for 500ms now.
I'm really curious if someone tested this : http://forum.xda-developers.com/xperia-z/development/mod-gpu-rendering-tweak-t2286709
I can't do it right now because i need my phone at his moment, but could test it tonight and see what happens.
boilavera1980 said:
So what i did now to test is that i enabled the "old" hotplugging where it goes down to one core, even enabled core parking, but gave it a near 2ghz touch boost for 500ms now.
I'm really curious if someone tested this : http://forum.xda-developers.com/xperia-z/development/mod-gpu-rendering-tweak-t2286709
I can't do it right now because i need my phone at his moment, but could test it tonight and see what happens.
Click to expand...
Click to collapse
Okay so i stumbled upon this thread http://forum.xda-developers.com/showthread.php?t=2769899 and tweaked the interactive gouvers in this way. Stay pretty good idle and is very smooth like i wanted it. Don't know about battery life but i cant stand a stuttery mess.
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.