Related
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
im using serendipity 4.0.1, and rGB-v.4-Voodoo #10, im new to UV the phone, but i search in the post and found a template, i applied it and save it as boot setting, when i pressed the back button and open the app again, the values reseted, how do i maintain them?
The values reset because you didn't hit "Apply for now".
"Apply for now" applies the values until you reboot the phone and "Save as boot setting" saves your settings for everytime the phone boots up.
So, either put everything back in and hit "Apply for now" or restart the phone. I recommend erasing your bootup settings and hitting "Apply for now" so you don't end up in a boot loop if your settings are not stable.
how do i erase my bootup settings?
i dont know how to set up my voltage control app, it keep crashing on me
also consider the battery life for normal usage when oc ...
im not trying to over clock, i just want to save on battery but i cant seem to set up Voltage Control without crashing, i dont know what to do anymore, i cant set it up!!
hernan078 said:
im not trying to over clock, i just want to save on battery but i cant seem to set up Voltage Control without crashing, i dont know what to do anymore, i cant set it up!!
Click to expand...
Click to collapse
Try going to adb shell and removing it, and then reinstalling it. If that doesn't work you might just need to reflash Serendipity.
Auridran said:
Try going to adb shell and removing it, and then reinstalling it. If that doesn't work you might just need to reflash Serendipity.
Click to expand...
Click to collapse
i think the problem is not the app, is the values im using, i dont know what to do, i was pumped to using voltage control to save battery!
hernan078 said:
i think the problem is not the app, is the values im using, i dont know what to do, i was pumped to using voltage control to save battery!
Click to expand...
Click to collapse
Have you tried lower values? Does it do the same thing?
I lower the values and it works, for a while, when i press the lock button i wait 2 minute or less and the phone crashes and i have to do a battery pull out!
hernan078 said:
I lower the values and it works, for a while, when i press the lock button i wait 2 minute or less and the phone crashes and i have to do a battery pull out!
Click to expand...
Click to collapse
What values are you using? Not all the processors in the phones are created equal, and some don't like to be run very far out of spec.
I would recommend to start conservatively.
Note: If u r using OC based kernels, try not to reduce much voltage from any step over 1200. I think I read in some post there (probably glitterballs' kernel related one) that 1200 and 1280 both use same voltage levels. So its best to be conservative on that end.
Values I regarded as safe are 100, 100, 75, 50, 50, 50 (bottom to top), and the ones I am currently using are 125, 125, 100, 75, 75, 50 (bottom to top), and I have my speed capped at 1000 (since this is sufficient for my needs).
diablo009 said:
I would recommend to start conservatively.
Note: If u r using OC based kernels, try not to reduce much voltage from any step over 1200. I think I read in some post there (probably glitterballs' kernel related one) that 1200 and 1280 both use same voltage levels. So its best to be conservative on that end.
Values I regarded as safe are 100, 100, 75, 50, 50, 50 (bottom to top), and the ones I am currently using are 125, 125, 100, 75, 75, 50 (bottom to top), and I have my speed capped at 1000 (since this is sufficient for my needs).
Click to expand...
Click to collapse
Im using rGB-v.4-Voodoo #10 Kernel, and i put the values you posted, but it crashes on me, do i need to change my kernel or something like that?
hernan078 said:
Im using rGB-v.4-Voodoo #10 Kernel, and i put the values you posted, but it crashes on me, do i need to change my kernel or something like that?
Click to expand...
Click to collapse
Your phone may just not be quite capable of those undervoltages. It might not be capable of any undervolting at all. Remember, undervolting is running the processor out of spec. It's all luck of the draw if you get a processor that is from the top of the bin or a processor that is from the bottom of the bin.
Auridran said:
Your phone may just not be quite capable of those undervoltages. It might not be capable of any undervolting at all. Remember, undervolting is running the processor out of spec. It's all luck of the draw if you get a processor that is from the top of the bin or a processor that is from the bottom of the bin.
Click to expand...
Click to collapse
but it doesnt matter what kernel im running? if i use a kernal that dont support UV, i cant UV? The kernel im using, support undervolt?
hernan078 said:
but it doesnt matter what kernel im running? if i use a kernal that dont support UV, i cant UV? The kernel im using, support undervolt?
Click to expand...
Click to collapse
As far as I know, every kernel that supports overclocking for the Captivate supports undervolting. I know for a fact the kernel you're using does.
Auridran said:
As far as I know, every kernel that supports overclocking for the Captivate supports undervolting. I know for a fact the kernel you're using does.
Click to expand...
Click to collapse
And what you suggest is the problem? :S
hernan078 said:
And what you suggest is the problem? :S
Click to expand...
Click to collapse
Like I said, your CPU probably can't handle the level of undervolting you're trying to give it. Also, some peoples' phones can't even reach 1.28GHz (the stock clock of the kernel you're using) without undervolting at all, so your problem could easily lie there, unless you've limited the clock to 1GHz in Voltage Control.
hernan078 said:
Im using rGB-v.4-Voodoo #10 Kernel, and i put the values you posted, but it crashes on me, do i need to change my kernel or something like that?
Click to expand...
Click to collapse
Is it crashing for the values in green too? They were supposed to be very conservative, and the ones I regard as "safe".
And like "Auridran" quoted, try limiting speed to 1000.
Edit: I would recommend u starting with 25 for lower speeds, and try not reducing voltage at speeds over 800.
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.
Hiya!
I seem to have lost root privileges for some reason, or at least setCPU seems to think so (but I'm not sure if it's true). As a result, my Nook seems to be running at 1.1 ghz all the time, regardless of load, regardless of whether or not the screen is on, etc. I can't tell for sure, but that's what it looks like to me (in part due to the swift battery drain I experience even with the screen off and a screen-off profile [possibly] activated). Because setCPU can't get root privileges I can't change the profiles or change the governor (which is, for some reason, set to "conservative").
Has anyone experienced this? Any thoughts on what I can do to regain root?
thanks
Anyone? Any and all help would be appreciated :S
I don't believe you need to use SetCPU in HC. It throttles the CPU all by itself. When I go into Quadrant Standard, it indicates minimum(300), maximum(1100), and current(varies) speeds.
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.