Database Develop

SetCpu

Hi, installed Setcpu but cant get the option to boost it faster than 528, is there a setting on it for getting it close to 600+?
Thanks

You'll have to be running a custom kernal to take advantage of over clocking. The stock kernal will be limited to stock speeds.
Hey... I think this thing makes phone calls too!

If SETCPU>menu>auto-detect does not list speeds greater than 528, then that is the highest that your ROM/Kernel supports. What ROM are you running?

Unfortunately Im on the stock 2.1

Deltatristar500 said:
Unfortunately Im on the stock 2.1
Click to expand...
Click to collapse
Root then and get a deca kernel on there!
-----
Sent from my CDMA Hero. I got some hot Froyo-on-Hero action here!

user7618 said:
Root then and get a deca kernel on there!
-----
Sent from my CDMA Hero. I got some hot Froyo-on-Hero action here!
Click to expand...
Click to collapse
so drop the kernel on my rooted stock 2.1 and then I can crack the speed on it?

Deltatristar500 said:
so drop the kernel on my rooted stock 2.1 and then I can crack the speed on it?
Click to expand...
Click to collapse
You'll have to save it in the root of your SD card, boot to recovery, wipe dalvik and flash it there. More info here

I don't know if deca's kernels work with sense or not. Beezy420 on AC has an oc kernel posted in his honey bun thread, I believe.
-----
Sent from my CDMA Hero. I got some hot Froyo-on-Hero action here!

when I go to revcovery mode, I get a black screen with a triangle and an exclamation
nvm, got into recovery

You need to flash a custom recovery. I'm assuming you didn't search or read the wiki.

Yes Deca's kernels work on 2.1 & 2.2 sense roms . Just to let u know
user7618 said:
I don't know if deca's kernels work with sense or not. Beezy420 on AC has an oc kernel posted in his honey bun thread, I believe.
-----
Sent from my CDMA Hero. I got some hot Froyo-on-Hero action here!
Click to expand...
Click to collapse
Sent from my DROIDX using XDA App

FdxRider said:
Yes Deca's kernels work on 2.1 & 2.2 sense roms . Just to let u know
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Good call. I wasn't sure.
-----
Sent from my CDMA Hero. I got some hot Froyo-on-Hero action here!

MrCoolHand said:
You'll have to save it in the root of your SD card, boot to recovery, wipe dalvik and flash it there. More info here
Click to expand...
Click to collapse
hmm, I only have a couple options on recovery
1 reboot
2 apply sdcard:updatezip
3 wipe data
4 wipe cache
thanks it

Deltatristar500 said:
hmm, I only have a couple options on recovery
1 reboot
2 apply sdcard:updatezip
3 wipe data
4 wipe cache
thanks it
Click to expand...
Click to collapse
Have you flashed a custom recovery image like clockwork or amon ra? That sounds like the stock one.

MrCoolHand said:
Have you flashed a custom recovery image like clockwork or amon ra? That sounds like the stock one.
Click to expand...
Click to collapse
thanks, no I have not...will look at getting one of those..Im really new at all this so bare with me.

From a new to this standpoint the easiest thing to do is search the market for "Rom Manager" download the free version and there should be an option to flash Clockwork to your phone. It will do all of the work for you.
Then reboot into recovery, and you will have the option to Flash/Apply Zip.
For a Sense rom the best kernal I have found is still Zen's no perf lock kernal, a quick search should pull it up. It eliminates the screen lag in Sense that typically occurs when the screen is off, answering calls, and typing. No other kernal has ever come close to it when I run sense roms.
It will let you overclock and undervolt with a wide range of speeds. I get great performance out of 345 low 729 high with on demand while the screen is on, then set a profile in set cpu for the screen off to be 245 to 480 (allows music/pandora to play without issue while conserving battery).
Just some helpful stuff for you.

indiscriminant said:
From a new to this standpoint the easiest thing to do is search the market for "Rom Manager" download the free version and there should be an option to flash Clockwork to your phone. It will do all of the work for you.
Then reboot into recovery, and you will have the option to Flash/Apply Zip.
For a Sense rom the best kernal I have found is still Zen's no perf lock kernal, a quick search should pull it up. It eliminates the screen lag in Sense that typically occurs when the screen is off, answering calls, and typing. No other kernal has ever come close to it when I run sense roms.
It will let you overclock and undervolt with a wide range of speeds. I get great performance out of 345 low 729 high with on demand while the screen is on, then set a profile in set cpu for the screen off to be 245 to 480 (allows music/pandora to play without issue while conserving battery).
Just some helpful stuff for you.
Click to expand...
Click to collapse
thanks for the reply

thanks, worked like a charm with the Zen kernel, and with set cpu set at 345 low 729 high, yet Restaurant story seem to still lag a but at 729, most be all the folks at me restaurant. Oh well.

How do I minimize the lag from turning on the screen and useing the device on the home screen. I turn it on, there looks like there is a bit of a pause for the CPU to relize the screen is turned on and to switch to the 345 low 729 high setting (on demand) instead of the lowest setting to 345 for (screen off). The dely is a bit annoying since I can move to the other screens left or right from the home screen. Its like the phone freezes for a few seconds

Deltatristar500 said:
How do I minimize the lag from turning on the screen and useing the device on the home screen. I turn it on, there looks like there is a bit of a pause for the CPU to relize the screen is turned on and to switch to the 345 low 729 high setting (on demand) instead of the lowest setting to 345 for (screen off). The dely is a bit annoying since I can move to the other screens left or right from the home screen. Its like the phone freezes for a few seconds
Click to expand...
Click to collapse
Go into your display settings and turn off Screen animations. (I have mine on some and it seems fine though)
Also, take the stock android clock/weather widget and remove it.
Then re-apply the widget again and when it gives you the option to keep its animation on turn it off as well, by default when the Rom is loaded it is on. For some reason that seems to always cause me lag when first getting the screen on. I think it is due to whenever it loads it checks the weather, the last time it showed, and then decides if it wants to do the animation or not. Unfortunately our Hero's just don't process that too fast.
Also as a new person go to this link, about half way down http://wecravegames.com/forums/gadg...sion/34-~~~official-android-thread~~~-67.html
It is a gaming forum I am also on and I answered a basic question on terms for rooting etc that may be of help to you.

[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.

[Q] [OMNIROM] Phone takes long to wake up / screen does not light up

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.

[Q] Small lags here and there

Hello guys, how are you?
I would like to ask if you also have the same "problem" with your nexus 6. First of all, I come from an OnePlus One which was very smooth . I used to run CM + Franco Kernel but even stock CM (11 or 12) run nicely on it.
Now I'm using a Nexus 6 with the stock rom and the latest version of franco kernel (r26) but, for example, when I swipe the multitasking windows, I can see clearly a lag especially with the last one. Scrolling up and down is also laggy sometimes. Are you experiencing the same? I am running without the encryption and I already tried to disable Fsync; the launcher is the Google one.
Do you have any other sugestions?
Regards,
Rafael

I had this issue on Franco kernel. I went back to stock and the lags went away and battery life almost doubled

I have small lags here and there (sometimes seconds long freezes) but that's mostly due to me messing with kernel settings, trying out custom kernels and nightly ROM builds.

where you able to find out what was causing the lag and how to fx it? im having the same issue.

angourakis said:
Hello guys, how are you?
I would like to ask if you also have the same "problem" with your nexus 6. First of all, I come from an OnePlus One which was very smooth . I used to run CM + Franco Kernel but even stock CM (11 or 12) run nicely on it.
Now I'm using a Nexus 6 with the stock rom and the latest version of franco kernel (r26) but, for example, when I swipe the multitasking windows, I can see clearly a lag especially with the last one. Scrolling up and down is also laggy sometimes. Are you experiencing the same? I am running without the encryption and I already tried to disable Fsync; the launcher is the Google one.
Do you have any other sugestions?
Regards,
Rafael
Click to expand...
Click to collapse
phyba said:
I had this issue on Franco kernel. I went back to stock and the lags went away and battery life almost doubled
Click to expand...
Click to collapse
brando56894 said:
I have small lags here and there (sometimes seconds long freezes) but that's mostly due to me messing with kernel settings, trying out custom kernels and nightly ROM builds.
Click to expand...
Click to collapse
aniel300 said:
where you able to find out what was causing the lag and how to fx it? im having the same issue.
Click to expand...
Click to collapse
@ ALL who have this problem:
i had it too, and i was thinking that i have been the only one..went crazy because i didnt find the reason for this.
Solution:
1) You need the paid version of FKU
2) Open FKU, go into "CPU Manager"
3) Go into Governor Control
4) click on "input_boost_duration"
5) Change the value to: 1000000
6) Turn the button on for set on boot (so this value will be saved and applys again after a reboot)
7) then reboot the device, and voila
explanation:
on the stock kernel there is following setting:
if you touch the display, the Cpu will stay at 1497 Mhz for 3 Seconds and thats the reason why stock is smooth!
Franco changed this value for saving battery. his standard value is 0.04 Seconds on 1497 MHz, then it goes down to 300 if the cpu dont has to handle something.
So for example: if you scroll in the settings, and the CPU frequency goes so quickly down (after the 0.04 secs) there will be stutters
and with the 7 steps i mentioned above, you change the boost duration to 1 second. This means the device will not lag, because the CPU stays for 1 sec on 1497 Mhz and the battery impact isnt that big!
Please try this out and respond to me if it helped

aniel300 said:
where you able to find out what was causing the lag and how to fx it? im having the same issue.
Click to expand...
Click to collapse
Turns out, most of my problems were caused by the "Deep Darkness" CM theme. Builds of BlissPop and BenzoROM would be fine for a little while and then start to screw up, getting pissed off I would boot into CleanROM which didn't have any themes applied (I use MultiROM) and everything would work as expected for hours, no lags at all! I decided to switch to another theme in BlissPop to test my theory and voila no more lag!

GregNexus said:
@ ALL who have this problem:
i had it too, and i was thinking that i have been the only one..went crazy because i didnt find the reason for this.
Solution:
1) You need the paid version of FKU
2) Open FKU, go into "CPU Manager"
3) Go into Governor Control
4) click on "input_boost_duration"
5) Change the value to: 1000000
6) Turn the button on for set on boot (so this value will be saved and applys again after a reboot)
7) then reboot the device, and voila
explanation:
on the stock kernel there is following setting:
if you touch the display, the Cpu will stay at 1497 Mhz for 3 Seconds and thats the reason why stock is smooth!
Franco changed this value for saving battery. his standard value is 0.04 Seconds on 1497 MHz, then it goes down to 300 if the cpu dont has to handle something.
So for example: if you scroll in the settings, and the CPU frequency goes so quickly down (after the 0.04 secs) there will be stutters
and with the 7 steps i mentioned above, you change the boost duration to 1 second. This means the device will not lag, because the CPU stays for 1 sec on 1497 Mhz and the battery impact isnt that big!
Please try this out and respond to me if it helped
Click to expand...
Click to collapse
BEEN SEARCHING FOR A SOLUTION TO THIS FOR DAYS NOW AND THIS WORKED! THANKS! :good: