Hi everybody ...
I have a question regarding using SetCpu to a full potential and keeps on freezing whenever I set the clock to 1704 Mhz on main section of application. For your information regarding my GN
- LA4 ROOTED WITH CWM recovery ([ROM] [03.02] Chrack´s XXLA4)
and please refer to the screen capture of my about phone so you can see the kernel version etc... and also including the screen capture of the setting of SetCpu as well so anyone knows what I am not doing right in settings of SetCpu...
Every single time I set the clock to the max which is 1704 Mhz, m my phone freezes and had to reboot again !!.
Please carefully look at the screen captures and advice me what to do with these setting in SetCpu...
Thank you very much in advance !!
If it freezes, that means you've gone too high. Keep lowering it until you stop experiencing freezing.
@Seeker14491 --- YEAH thanks for your information much appreciated !
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
Hi,
I am having an issue where the screen takes a solid 1-2 seconds to power on after the phone has been sleeping/idling. Sometimes it's not so bad but it's becoming quite annoying, and sometimes I think the screen turns off again before it can show the lockscreen and I have to pull out the battery to fix it!
Cm7.1 stable w/cm7 kernel. Was happening on stock too.
Does anyone know a way around this? Widgetlocker doesn't seem to fix it
Thanks.
i am having a similar issue on Topogigi's v1.9, no issue on his 1.4 version, very annoying!
noticed with Topogigi's ROM since v1.9:
This issue is even worse when a call comes in: The fon will vibrate about 4-5 seconds before the screen turns on to shows the caller. Until then you can not see whos calling.
On Horsepower rc1 kernel and topo 1.9 I can't say I have noticed this issue.
Used fon was already running on v2.0 with RC1 kernel.
Also did a clean flash of the rom again to eliminate possible issues of other apps running. But this has no effect on the problem. It still persists: When a call comes in, the fon vibrates up to 5 seconds before the screen turns on. Even then, you first see the unlock screen and about a second later the screen with the incomming call. Reproducability 10/10 times. Notice that vibration for incomming calls has to be set as "always on" in settings to reproduce problem!
Extremely annyoing because call can not be answered or dismissed while fon keeps ringing! Already missed calls because called hung up before screen unlocked.
Don't know if its a kernel or rom issue...
Advice
The best way for you not to have troubles is to pick a stable rom and flash it!
If you are on Topogigi ROM, This has already been explaine in the FAQ.
Topogigi said:
Ladies and gentlemen, guys and gals, experts and noobs, here you will find a F.A.Q. collection for our ROM. Hope it will help.
Q6.But I'm still experimenting lags with overclock daemon on wakeup: how can I tune it to fit my needs at best?
A6.One of the best features of overclock daemon is that you can tune it as you like. If you don't want to see lags on wakeup, just raise a little the max frequency for sleep profile. If you want to mock SGS2 owners with astonishing Quadrant scores, raise the frequency to the max for wake profile and your phone will turn into a raging bull. It's up to you. Your interest is raising? Let's see how to do it:
Fire up ES file explorer (you will find it in my rom beginning with v. 1.6 release), open settings and check "Use Root Mode" and "Mount Filesystem" (you need to do it only once). Then exit settings and hit the highest icon on the left: you will be in the root directory of your phone. Navigate to /etc/andrev_oc, you will find six files there:
-sleep_gov: indicates which governor to use during sleep mode ("performance" or "powersave")
-wake_gov: governor for awake state ("performance" or "powersave")
-sleep(or wake)_max: max frequency to allow during sleep or wake (see frequencies below)
-sleep(or wake)_min: min frequency to allow during sleep or wake (see frequencies below)
Here there are the frequency values available on current kernel (Neoblaze 28092011):
1408000
1216000
1100000
1015000
800000
503000
389000
216000
Make your changes to the files listed above and save them.
Since overclock daemon is already up and running and it monitors these files at every screen state change, it should be enough to hit the sleep button, wait some seconds, and hit it again to wake your phone. Your new settings will be applied immediately.
You may want to check the actual CPU frequencies by using OS Monitor or SystemPanel App (download the freely from the Market).
Click to expand...
Click to collapse
Look in my signature. Download the Andrev OC app.
Set asleep maximum frequency to 800 or 1016.
Problem solved.
There is also an app for the Topogig ROM http://forum.xda-developers.com/showthread.php?p=18273457#post18273457
---------- Post added at 08:22 PM ---------- Previous post was at 08:21 PM ----------
Hahaha, same timing
Problem solved here like described. Thank you guys!
p.s.: I really appreciate the work of topogigi and spica for roms and kernel. They run 1000x better than the stock roms so I would never follow an inappropriate advice to fall back on those. Must be the urge to reach the amount of 10 posts for some ppl to get access to the dev area...
Hello XDA-Members
I wanna ask around if someone of you is experiencing the same bug when trying to underclock the SGS on CM10-Nightlies...
The first time i experienced this bug was on 20120820 - I tried to set the max freq to 800 Mhz and saw instantly the bootanimation.
The second time was today with 20120826 - when i choose max freq 800 mhz in the system settings, the hole SGS freezes. only the backlight of hardware keys shows response.
The Nightlies in between i couldn't test.
Everything is stock. Checked the md5 of the downloaded zips. No apps installed. All okay. This bug is annoying Even if nearly nobody would underclock this phone because of the "butter" in CM10...
Cheers
i pushed the max clock rate to 1.1ghz,it's unstable and rebooted again n again
i knew i have to stop it,so i just set it into original rate,then i flash oem rom
the result is my phone just always keep in max clock [email protected] although the governor setting is ondemand
i can't phone for a long time,it will stop conversation suddenly,duration usually not more than a minute
then i flash cocore 8.8 again, i set max rate @400mhz,but still can't phone normally,it just stop stop stopstop
bad english:silly:
PLEASE HELP ME
hus159 said:
i pushed the max clock rate to 1.1ghz,it's unstable and rebooted again n again
i knew i have to stop it,so i just set it into original rate,then i flash oem rom
the result is my phone just always keep in max clock [email protected] although the governor setting is ondemand
i can't phone for a long time,it will stop conversation suddenly,duration usually not more than a minute
then i flash cocore 8.8 again, i set max rate @400mhz,but still can't phone normally,it just stop stop stopstop
bad english:silly:
PLEASE HELP ME
Click to expand...
Click to collapse
Do not use max 400MHz, it will make your phone so slow. Use default, overclock will cause reboot to you. Some phones work overclocked, some do not.
Hi folks,
I am using the latest (20140908) omni rom nightly build and I have the following issues:
I am getting called (ringtone) but the screen stays black for 5-10 seconds
Alarmclock: when it goes off, the screen stays black and i can't switch it off (very annoying)
Screen takes 2-3 seconds or more to light up after I press the power button
Any ideas on that?
Thanks!
adam recommends (well, used to, not sure if it's still the case) that you use a custom kernel, and he mentioned iodak's few times. remember to set max screen off frequency to 1ghz or so via trickstermod, so the device won't lag (default is 475 mhz which isn't quite enough) with wake-up when screen is off
Thanks, I'll try the frequency fix first (I have no modifications there whatsoever) and if it's not helping go with mourta kernel.
aktentasche said:
Thanks, I'll try the frequency fix first (I have no modifications there whatsoever) and if it's not helping go with mourta kernel.
Click to expand...
Click to collapse
you're only able to change screen off frequency on iodak-based kernels (mourta, iodak, cyodak, mahdi), not stock omni. good luck
I personally use Tasker to set performance governor for 5 seconds when a call comes.
That is also an interesting idea. I'll see how the phone performs with the next incoming call and if the problem still occurs I'll try it.
Until now I installed mourta 02/09 and I'm using abyssplugv2 governor. It does not have a max screen off frequency but the smoothness is much better already.
aktentasche said:
That is also an interesting idea. I'll see how the phone performs with the next incoming call and if the problem still occurs I'll try it.
Until now I installed mourta 02/09 and I'm using abyssplugv2 governor. It does not have a max screen off frequency but the smoothness is much better already.
Click to expand...
Click to collapse
I've the same problem on cyanogenmod with stock cm kernel. When i install another kernel such as iodak my 4x is faster and smoother. Try to install iodak and set the min cpu freq to 475mhz.