Develop Bugs

Proper/Ideal settings of SetCPU on I9100?

Hi,
I purchased SetCPU last night from Android market but I am unable to select the correct settings for it. I tried with 'Powersave' preset as I was going to sleep, but after 5 mins when I checked my phone it was off! and I had to turn it on. Every time I select Powersave mode it is forcing the phone to go off. Then I selected 'Ondemand' preset and went to bed at 0245 hrs. Today when I woke up at 1200 hrs ( ) the battery was at 48%, while yesterday night when I selected ondemand preset it was at 53%, it's a gap of 10 hours, in the mean time the Phone was in Flight mode and everything was set to OFF. So that's a 5% battery decrease overnight. But before that, when I was at all Default settings without SetCPU installed the battery was decreasing at a rate of 2-3% overnight under same settings. So I wonder after installing SetCPU the battery back up isn't extended but actually decreased. So I was thinking it may be a problem with my settings. Can you guys please tell me that what settings should I use to get the maximum juice out of my battery and that without compromising the clock rate of the CPU? Isn't there an Automatic settings that the CPU will run at Full speed when needed and check it's speed when in Idle? I thought 'Ondemand' preset would serve that purpose but I was wrong I guess!
Thanks in advance.
Here is a screen from SetCPU,
Regards.

I've got the same problem,any help would be appreciated.

Max 500 Min 200 and work from that adjust as needed .
jje

JJEgan said:
Max 500 Min 200 and work from that adjust as needed .
jje
Click to expand...
Click to collapse
Oh! And by setting the upper limit to 500 MHz we won't ever be able to use the CPU at 1200 MHz, great. I should've stick with my S8500 then, eh? What do you say?

ithehappy said:
Oh! And by setting the upper limit to 500 MHz we won't ever be able to use the CPU at 1200 MHz, great. I should've stick with my S8500 then, eh? What do you say?
Click to expand...
Click to collapse
aren't you eager to criticize. there are something called profiles. does your phone require to use 1.2 ghz in sleep , low battery conditions or overheating conditions? galaxy s2 uses ondemand governor at 200 to 1200 by default. meaning when it needs power it will ramp up to 1200. it does this in steps higher than battery saving governors so you spend more time in 1.2 ghz
my advice
sorted by priority
screen off = 200 - 500
in battery < 30 use 200 to 800
overheating = 200 - 800
charging = full speed
regular use when no profiles apply = full speed

Reason for Processor Speed as 800 MHz

Hi Wavers,
From last few days, I have read many posts saying “This Firmware is not final as Processor speed is still set to 800 MHz by SAMSUNG”.
So, I contacted Samsung via “Bada Developers” and asked them why they have set Processor speed as 800 MHz (i.e. whether Latest Firmware are final or not).
I got reply for one of the Bada Developer saying “800MHz on IDLE! If you start a Application or Game it goes up to 1GHz... (The same is on a Wave 3)”
That means, they have set Processor speed as 800 MHz only for idle state (No Application running) and it will goes up to 1GHz if you start Application or Game. And same is implemented for Wave 3.
So, I think SAMSUNG is right at least at this Time and Reason looks pretty logical.
Note: - I haven’t verified whether this is correct or not, as I haven’t flashed my wave 2 with latest firmware. Mods can verify this and let us know whether I and Samsung are right or not ;-)
Regards,
WaveGuru

hmmmmmmmmm
not totally true
i tried to check processor speed while game is running in the background and the highest number i got was 850 MHz only !!
Maybe Samsung missed something and limited speed to 850 only ?!
Best Regards

Tell that developer that he is dumbass. In idle mode ARM Clock goes to lowest possible frequency ~100MHz. But yeah, in many kernels I've been looking into it seems that they got upper limit of 800MHz.

Guys... i'm installing Zombie Infection via KIES right now and it shows 1000MHz. I didn't change anything in service menu. I have newest LA1 firmware. For me it usually shows 800MHz but it is enough to move upper beam and booom - it shows 950MHz right away. So i think the developer doesn't lie.

can you post which firmware version?

800MHz sounds reasonable on idle. Some droids (used to own an o2x, now I'm on a Wave 1) with go as low as 500 - 650 to up the powersaving. However, this causes the device to lag a bit when you wake it up. But that's very little inconvenience compared to the juice you're saving.
100MHz could be too slow when running background services such as radio, wifi, etc... I have no statistics though

kolo2x said:
100MHz could be too slow when running background services such as radio, wifi, etc... I have no statistics though
Click to expand...
Click to collapse
100Mhz is still damn 100 millions of cycles per second, that is about 20 millions of elementar operations per second. For me it's enough to run radio, wifi, bluetooth, jump and sing. Especially if all of these are handled not by CPU but external chipsets.
If you look at WinComm logs at debuglevel high you will see everytime phone turns off screen clock goes 100~200MHz. When you wake it up - that depends, sometimes goes 400, when you move screen animation can go up to 800.

Rebellos said:
100Mhz is still damn 100 millions of cycles per second, that is about 20 millions of elementar operations per second. For me it's enough to run radio, wifi, bluetooth, jump and sing. Especially if all of these are handled not by CPU but external chipsets.
If you look at WinComm logs at debuglevel high you will see everytime phone turns off screen clock goes 100~200MHz. When you wake it up - that depends, sometimes goes 400, when you move screen animation can go up to 800.
Click to expand...
Click to collapse
I've never used WinComm but it seems like a good tool. When you turn a phone off, you go in some "deep sleep" mode (yep it's not really off), which only runs the most basic of services. Services that poll your buttons or monitor certain interrupts that may cause your device to wake up such as some special alarms. Radio, wifi, and bluetooth are not among them. Embedded devices are required to drop their CPU frequencies drastically so you don't run out of battery.
Screen-off is another state that may just require disabling screen controllers, software renders, and the like. Some droids even turn off wifi on screen-off. I believe this is the idle state we're talking about.
From your observation, it seems the Wave's kernel is good at adjusting frequencies where needed. This could explain the good battery life this device has.
---------- Post added at 06:18 PM ---------- Previous post was at 06:14 PM ----------
Rebellos said:
100Mhz is still damn 100 millions of cycles per second, that is about 20 millions of elementar operations per second. For me it's enough to run radio, wifi, bluetooth, jump and sing. Especially if all of these are handled not by CPU but external chipsets.
If you look at WinComm logs at debuglevel high you will see everytime phone turns off screen clock goes 100~200MHz. When you wake it up - that depends, sometimes goes 400, when you move screen animation can go up to 800.
Click to expand...
Click to collapse
My bad. I believe I've read your reply incorrectly. If WinComm says we're at 100~200 MHz on screen-off then maybe this is all it needs to keep radio, wifi, etc.
Good stuff!

More Govenors for CM7

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

Blu Kuban - Kuban Kernal 3.0.15 battery life

Ive got blu Kuban 1.0.4.3 ROM on my phone with the attatched Kuban Kernal 3.0.15 and am having battery issues. I just recently deleted my facebook widget thinking maybe thats doing it, but it will last about 4 hours before it dies. Im downloading bad ass battery monitor to see if I can further look into whats sucking the battery power.

GO to developer option and click do not keep activities
maybe there something runing on the background you have to look at under battery or in appliication

OK I did that ill see if it changes anything. As of 72% battery left, battery monitor shows 69.8% app usage, and 51.8% is the Kernel. All of the apps listed don't use much under app usage its the kernel that is killing it. Does this mean I need a new Kernel? This cant be normal right? Can I use just any Kernel? Thanks

51% kernel is high, yes. See if other people have the same percentage with that kernel. If not, then maybe try a different kernel. agat's or sleshepic's kernels are also good and built from source. Btw, I wouldn't advise doing the Developer Options setting change to close all activities. That setting isn't meant for ordinary use and severely limits your multitasking abilities. "Closing apps" also has a minimal effect because of the way Linux deals with RAM. It turns out that opening and closing apps takes away more battery than keeping one running in the background.
If your battery isn't good, diagnose why with the following apps:
Betterbatterystats - Download this app and check your "Partial Wakelocks". Basically this checks what apps are waking your phone up when it's sleeping.
CPU Spy - This allows you to easily see how much time your phone has spent in each state. You get really bad battery life if your phone idles on 200 Mhz instead of Deep Sleeping. Your phone should be on Deep Sleep when the screen is off, or else your idle battery drain will be fast.
Other ways to save battery life:
Tweaking system settings
Get SetCPU/Tegrak/Voltage Control/Any other CPU Settings app and undervolt each of your processor states to -50 mV. By stock your phone's states come "overvolted" and you can conserve battery without loosing performance if you slightly tweak them. Don't go too low or your phone may get unstable and crash.
Use those same apps to underclock or set profiles to underclock under certain circumstances
Use those same apps to change your governor. Read up on different governors and how they scale your processor when needed. Here is a link that explains different governors - http://forum.xda-developers.com/showthread.php?t=1369817 . Usually "conservative" and "SmartassV2" and "Lulzactive" are pretty good with battery life. It all depends on how much performance you are willing to give up for low battery life.
Use those same apps to change your I/O scheduler. The scheduler, in simple terms, basically describes in what order apps will run, which will be prioritized, etc. The "SIO" scheduler is probably the best balanced one. "Deadline" I believe saves more battery life but maybe slow you down a little.
Apply tweaks that do it for you
In the general section of our forums, a developer named PhAkEer has posted some tweaks. His "dietpill" battery ones are really good for keeping your phone fast but saving battery life. If you have these tweaks though, they automatically choose a governor and I/O scheduler so manually changing them will only interfere if you decide to do this.
Change simple unneeded settings
Another reminder is that simple things can save you a lot of battery life. Turn off haptic feedback. Take off pulse light notifications (there are reports that these wake up your phone from Deep Sleep and put the processor back into the 200 Mhz state... thus taking away battery life). Turn off 3G when not needed (3G and 4G are huge drainers). Set WiFi to turn off when your screen is off. There is a ton of other stuff you can do.
Well I hope this long post helps you in your quest to find better battery life. Good luck

Tried putting the new agatas kernel on my phone and nothing has changed. CPU Usage shows 200MHz is 79% of sleep while deep sleep is only9. How to I go about dealing with this?

Check your wakelocks with Betterbatterystats. Otherwise just play around with some settings. For me it's usually WiFi that keeps my phone in 200 Mhz. I set WiFi to turn off when the screen is off. Maybe you have an app running that actively requires your phone's processor or something.

partial wavelocks is MAIL SERVICE - at 6.5% 5m 54s count 1953, AudioOut_! is 4.9% count 7 5m 54s, Juice defender 1.6% count 447 2m. So is it my email then? What is Kernel wavelocks?

any help here??
Did the new kuban update which switch kernels back, battery life has improved but is only 4 hours still. Deep sleep has gone up which is probaly why i saw an increase, but betterbatterystats shows no data connection and no signal to be high usually around 30-90 percent. It seems like Kernel percent has gone down tho around 30-40 usually...

I saw a post saying these are stock voltage -- is it correct?
200 MHz = 950 mV
500 MHz = 975 mV
800 MHz = 1075 mV
1000 MHz = 1175 mV
1200 MHz = 1275 mV
1400 MHz = 1275 mV
1504 MHz = 1350 mV
1600 MHz = 1425 mV
1704 MHz = 1475 mV

bhollehday said:
any help here??
Did the new kuban update which switch kernels back, battery life has improved but is only 4 hours still. Deep sleep has gone up which is probaly why i saw an increase, but betterbatterystats shows no data connection and no signal to be high usually around 30-90 percent. It seems like Kernel percent has gone down tho around 30-40 usually...
Click to expand...
Click to collapse
What is your awake time versus you screen on time. If you are having signal problems test out other modems which are in the updater. Make sure you update prl and profile afterwards in about phone. Not having signal/service will kill your battery no matter what because it then tries to search for it constantly. Last week I was somewhere that had no service in my hotel room. For 18 hours in my lab it only drained 10% with about 2 hours of usage, then I went to sleep for 6 hours and it was down another 40%. I turned it on airplane mode to save battery. Hopefully trying a different modem might help. If not I have some suggestions for that too.

Delay in receiving a call

So when my phone screen is off, and I receive a call, the ringtone plays for about 3-4 seconds and then half way through the ringing, the screen turns on. I'm running ktoonsez kernel version 6/10
Do I need to increase a setting or something?

Have your off screen MHz too low I bet.

stevessvt said:
Have your off screen MHz too low I bet.
Click to expand...
Click to collapse
This is the first thing I thoguht of too.
Try setting it to 384 and see if it improves.

Skipjacks said:
This is the first thing I thoguht of too.
Try setting it to 384 and see if it improves.
Click to expand...
Click to collapse
stevessvt said:
Have your off screen MHz too low I bet.
Click to expand...
Click to collapse
My settings are :
MIN/MAX : 189 Mhz and 1890 Mhz
Screen Off Profile Mhz: 486 Mhz
Disable Screen Off Mhz Call: Enabled
Screen Off Profile Sched: noop
Screen Off GPU Max Mhz: 200
Which one's do i increase? and 384 isn't an option for me, it's either 378 or 189 (those are the lowest)

Change your min/max to 384(378?)/1890 and your screen off to 5XX, dont remember what that number is...

kevinrubio1 said:
My settings are :
MIN/MAX : 189 Mhz and 1890 Mhz
Screen Off Profile Mhz: 486 Mhz
Disable Screen Off Mhz Call: Enabled
Screen Off Profile Sched: noop
Screen Off GPU Max Mhz: 200
Which one's do i increase? and 384 isn't an option for me, it's either 378 or 189 (those are the lowest)
Click to expand...
Click to collapse
I meant 378.
But looking at your settings, first change the 486 max screen off to "No Change". Having that limiter on there could easily be what's causing your problem because the phoen is suddenly trying to perform 3 tasks at once. It's trying to notify you of the incoming call, turn the screen on, and change its' max processor speed to 1890. The change in processor speed is coming from the Kernel app, which has the lowest priority over the other 2 processes. So it's trying to turn the screen on and notify you of the incoming call while it's stuck at 486 Mhz. Only after it handles those tasks is the speed limit raised.
If you didn't have that speed limit then the phone would work at 1890 Mhz to turn the screen on and notify you of the call, and it would take about a half a second to complete.
I promise you it doesn't make much of a difference in battery if the screen off CPU speed is limited. If something runs with the screen off at 486 it just takes longer than it does at 1890. So the CPU is still going to run.

stevessvt said:
Change your min/max to 384(378?)/1890 and your screen off to 5XX, dont remember what that number is...
Click to expand...
Click to collapse
Okay I increased it to 378 Mhz and my screen off to 594 Mhz! I'll leave my phone to the side for a couple of minutes and see if it has the delay or not!

Skipjacks said:
I meant 378.
But looking at your settings, first change the 486 max screen off to "No Change". Having that limiter on there could easily be what's causing your problem because the phoen is suddenly trying to perform 3 tasks at once. It's trying to notify you of the incoming call, turn the screen on, and change its' max processor speed to 1890. The change in processor speed is coming from the Kernel app, which has the lowest priority over the other 2 processes. So it's trying to turn the screen on and notify you of the incoming call while it's stuck at 486 Mhz. Only after it handles those tasks is the speed limit raised.
If you didn't have that speed limit then the phone would work at 1890 Mhz to turn the screen on and notify you of the call, and it would take about a half a second to complete.
I promise you it doesn't make much of a difference in battery if the screen off CPU speed is limited. If something runs with the screen off at 486 it just takes longer than it does at 1890. So the CPU is still going to run.
Click to expand...
Click to collapse
Thanks, that makes perfect sense! I just set it to " Selected Scaling Max" because I couldn't find "No change" , is that the same?

kevinrubio1 said:
Thanks, that makes perfect sense! I just set it to " Selected Scaling Max" because I couldn't find "No change" , is that the same?
Click to expand...
Click to collapse
Yes. Same thing.

Skipjacks said:
Yes. Same thing.
Click to expand...
Click to collapse
It worked! Thanks skip
Sent from my SGH-M919 using xda app-developers app

Skipjacks said:
I meant 378.
But looking at your settings, first change the 486 max screen off to "No Change". Having that limiter on there could easily be what's causing your problem because the phoen is suddenly trying to perform 3 tasks at once. It's trying to notify you of the incoming call, turn the screen on, and change its' max processor speed to 1890. The change in processor speed is coming from the Kernel app, which has the lowest priority over the other 2 processes. So it's trying to turn the screen on and notify you of the incoming call while it's stuck at 486 Mhz. Only after it handles those tasks is the speed limit raised.
If you didn't have that speed limit then the phone would work at 1890 Mhz to turn the screen on and notify you of the call, and it would take about a half a second to complete.
I promise you it doesn't make much of a difference in battery if the screen off CPU speed is limited. If something runs with the screen off at 486 it just takes longer than it does at 1890. So the CPU is still going to run.
Click to expand...
Click to collapse
Great info! But partly incorrect.
Ktweaker is not like your other CPU tweaking apps. The app is not doing the screen on change. The kernel itself is doing that. If you look at the last_kmsg you will see the lines outputting the change. It also contains no screen on receiver which is needed for listening for screen events. Ktoonsez has kernel powers, they are better than APIs But yes, the max screen off CPU will cause lag when receiving a phone call for the reasons you state. It needs power to do its processes but is limited to the max CPU setting until the screen awakes.
But also increasing the min CPU levels helps too. I also think depending on which governor is used, that only one CPU is allowed to go on when the screen is off. Which is a great battery saver.

elesbb said:
Great info! But partly incorrect.
Ktweaker is not like your other CPU tweaking apps. The app is not doing the screen on change. The kernel itself is doing that. If you look at the last_kmsg you will see the lines outputting the change. It also contains no screen on receiver which is needed for listening for screen events. Ktoonsez has kernel powers, they are better than APIs But yes, the max screen off CPU will cause lag when receiving a phone call for the reasons you state. It needs power to do its processes but is limited to the max CPU setting until the screen awakes.
But also increasing the min CPU levels helps too. I also think depending on which governor is used, that only one CPU is allowed to go on when the screen is off. Which is a great battery saver.
Click to expand...
Click to collapse
wait so if I set the screen off mhz to 702, I would be fine and I would be saving battery?

kevinrubio1 said:
wait so if I set the screen off mhz to 702, I would be fine and I would be saving battery?
Click to expand...
Click to collapse
Yes you would save battery. And that should be high enough to let the processes carry out.
Sent from my SGH-M919 using Tapatalk 2

where is the screen setting menu??
i have the same problem how do i find the setting?