So I've compiled a custom kernel, and added a few more clock speeds.
However, I can now only go from 883mHz --> 1152mHz. The clock speeds in between are in "ascorpion . . .", but they don't show up in SetCPU.
Also, there is often an occasional lag when waking up my phone. It comes and goes, but ranges from 0-2 seconds lag.
Any help?
Related
I know there are quite a few threads on setCPU BUT this is my first time using and i was wondering for my rom, kernel, and phone usage what you guys think is best to save battery but still be snappy when the screen is on.
My phone setup:
2.2 Android
2.15.00.09.01 Baseband
King CFS 10 kernel
Evervolv v0.2.1 rom
pri 1.77_003
PRL 60670
I have the phone on wifi about 90% of the time because some of my reading says it saves battery. I use my phone for browsing facebook and a few forums, send a few hundred texts a day, talk on the phone maybe 10 times a week ( im a college student), regularly on email. NOW with that said how would YOU set up the set cpu for battery life but no lag while operating.
You need to update your PRL ...
twigums said:
I know there are quite a few threads on setCPU BUT this is my first time using and i was wondering for my rom, kernel, and phone usage what you guys think is best to save battery but still be snappy when the screen is on.
My phone setup:
2.2 Android
2.15.00.09.01 Baseband
King CFS 10 kernel
Evervolv v0.2.1 rom
pri 1.77_003
PRL 60670
I have the phone on wifi about 90% of the time because some of my reading says it saves battery. I use my phone for browsing facebook and a few forums, send a few hundred texts a day, talk on the phone maybe 10 times a week ( im a college student), regularly on email. NOW with that said how would YOU set up the set cpu for battery life but no lag while operating.
Click to expand...
Click to collapse
I always leave my main profile at 245 mhz min and 998 mhz max (ondemand mode). Then, of course, you'll want a screen off profile, and as far as that goes, I've heard that 128 and 245 draw the same voltage, so I have mine set to 128 min, 245 max (powersave mode). Other than that I just have some low battery profiles and a temp one. I don't really get any lag with this setup, but I've heard some people do. If that's the case, and I'm only talking about lag when first turning on, just up the 245 to 384 or something and I'd make it ondemand.
do i need to check set on boot under the scaling option
twigums said:
do i need to check set on boot under the scaling option
Click to expand...
Click to collapse
No. I would leave it unchecked. This has been known to cause some issues.
grouse130 said:
No. I would leave it unchecked. This has been known to cause some issues.
Click to expand...
Click to collapse
what kind of issues are you talking about? i've only heard and practice leaving it off when experimenting with overclocking (since it can put you in a boot loop). once you find a stable overclock speed, you can check it to start on boot so that you don't have to open setcpu every time you reboot if you decide to run it at that speed.
on-demand is a little less laggy (barely noticeable to me) but may consume more juice than conservative.
most kernels will step down to 245 when the screen is off so creating a profile to do that is redundant. you can verify this with the app android system info under the system tab > cpu.
having said that, i don't use setcpu unless i'm benchmarking and want to overclock.
kings #6 bfs kernel is awesome for battery life (default is conservative governor). it's what i use. give it a go when you've gotten a good feel on how kings #10 cfs is working out for you.
Here's what I would hit up..
set it to conservative. Conservative starts your phone at your minimum clock speed and works its way up, as opposed to on demand which starts at the highest and works its way down.
then for advanced i have sampling rate at 50000
Up threshold at 95% <- that's saying that when the workload hits 98%, crank up the processing speed
Down threshold at 70% <- when the load hits 70% turn it down
That stuff right there is agressive as hell, and when I say agressive, i mean...you probably won't ever hit your max frequency unless you are seriously doing some heavy lifting. The settings there are what I use to save up battery, you can get through a day easy with everything on (GPS, Wifi, sync, 3g, the works) and with your current usage, since its similar to mine (except that i also run beejive, skype and twitter at refresh rate of 5min).
grouse130 said:
No. I would leave it unchecked. This has been known to cause some issues.
Click to expand...
Click to collapse
Yeah I think you've probably just seen that on some custom kernel pages. They only say not to do that because if you're testing battery life with say...HAVS, it could interfere w/o you realizing it. Set on boot just means you don't have to turn setCPU on everytime you reboot your phone.
just go set a profile on minimal mhz and on powersave mode if kerenal allows if not just use ondemand
My problem with the "Set on Boot" option is if you accidentally fat finger the slider past your stable clock with it checked, you're looking at boot loops and possibly having to restore from a backup to sort it out. SetCPU really needs the "Set on Boot" option grayed out and a "Lock Settings" option that must be checked before "Set on Boot" becomes accessible (unchecking "Lock Settings" would also uncheck "Set on Boot").
Another option would be a user defined field for max stable clock in the advanced settings that would limit the slider on the main tab. Either one should eliminate accidental boot loops.
ok so im running the STOCK GB but im rooted and have been running gingertiny 9/29 ran into rebooting issues.. phone constently reboots after 20 mins of use. usually when this happened before like on stock kernels the battery temp would rise up to 104 but i kept eyes on the temp and it never goes over 78.4 F
not overclocking cpu im actually running at about 625 mhz but issue still occurs
SO with that being said i need help finding either a better kernal or trying to find solutions with this one.
i went back to complete stock and rooted to see if i still have this issue
any help will do thanks!
These questions belong in the Q/A section. This has zero relevance to development.
Now:
1) pull the battery then place it back into your phone.
2) Charge it awhile to make sure you haven't dropped a considerable charge during the bootloops.
3) Turn your phone on and move your clock speed towards 998400 (stock clock speed) via setcpu or however you underclocked.
This bootloop is likely due to you being underclocked so low. If you want, flash Tiny's latest kernel from 9/29/2011 to bring yourself up to date.
Was your min clock speed underclocked below the stock 245000? I had random reboot issues when I underclocked my min to 128000.
Having your max_freq set at 628 or whatever it was shouldn't cause reboot issues. You're phone should be rock-solid stable at a speed like that. I'd suggest taking a look at your voltages.
I've never run that kernel so I'm not familiar with what the voltage table looks like, but it might very well be that your voltage is too low. If your max_freq were higher, the transition through that clock freq would probably be too brief to cause an issue. I don't know if that kernel has sysfs enabled, but if it does, upping the voltage at that step .25 volts should cure it.
Min speed was at 628 even switching back to stock kernel still having issues I'm not sure what can be the issue I only last few mins playing any games or watching anything all speeds are stock
Sent from my ADR6300 using XDA App
Sounds like it's time to start wiping stuff.
Does anybody know what the ondemand governor uses as it's default screen off settings. By that I mean if I have profiles disabled in setcpu and just allow the ondemand governor to determine frequencies and I leave the max min freq's at default values, then what happens when the screen is turned off?
I know the cpu will eventually go into deepsleep but there are inconsistencies.
If I dont use setcpu and just allow the default kernel settings (im on doomlords btw) to determine the frequencies, then when I turn the screen on after leaving the phone for a while, the cpu speeds up very quickly and the system becomes responsive before I can ever notice.
If I use setcpu however, with a screen off profile set to ondemand, max 245, min 120, then it still takes achieves deepsleep as often as not using setcpu but there is a noticeable lag and stutter for about 5-10 seconds as I turn the screen on to use it again.
Does anyone have any idea;
A) Why this happens?
B) What is the default screen off behaviour for the ondemand governor on doomlords kernel.
you may need a program like system monitor to record your % of cpu activity, im on stock rom and i have it at 100 - 300 mhz max when screen off, i used the program while im asleep to see if there was issues but there was none or lag when the screen turned on
there isnt any inconsistency with mine,but then again i removed alot of the programs i dont use to have very few programs running in the background,playing music with this setting doesn't cause issues
i havent read alot into his kernal yet,guess you wait till someone that has more knowlege in his rom.
[v03 onwards] added new CPU governors:
InteractiveX
Savaged-Zen
SmartAssV2
Hi,
I was wondering if there was any effort to port the following governors to the Defy for CM7?
SmoothAss,
LagFree,
SmartassV2
I ask because I am using Smartass now and while it is great for the battery life(especially when you undervolt), it isn't as responsive when it needs to wake up on a call (screen stays black for 2-3 rings), and phone call processing can be kind of choppy when using HSPA (3G connection). Also sometimes the Mp3 playback skips when background data process goes off, or tower coverage changes.
---
I have seen SmartassV2 on Motorola DEXT and it rocks. 2 Days use worth of average phone use without charging.
Thanks in advance all.
tsurerb now
Any word on feasibility? Is this the wrong place to post this? I seem to have solved some of the problem by putting the first cpu setting at 400mhz. But it is apparent that the cpu never ramps to the second setting of 600mhz. I hear the newer governors solve these issues.
hi, dunno about supporting smartassv2, but you can set smt_sleep_max_freq to your clk2 speed, so in sleep smartass dont limit your defy to 300mhz. You dont be "saving" the batery charge like the smt_sleep_max_freq = clk1 but i think it will be better than having 400mhz in clk1
I am currently doing some o/c on the Perseus-alpha27.4-i317-CWM. I noticed that when I force the cpu speed on STweaks with a minimum and maximum at 1800mhz, and run a stability test (on Stability Test) it would run for a while on 1800mhz. But then after a few minutes it would start to switch back and forth between 1800mhz and 1000mhz.
It doesn't just do this for 1800mhz. It does it for lower speeds as well. So if I force the speed to go at 1700mhz, it would be switch off between 1700mhz and some number below 1000mhz (I forgot what the exact number was).
Can anyone shed some light on why it is doing this even though I forced the cpu speed on STweaks at a set speed?