[Q] Cpu setting? - Samsung Galaxy Mini

What is the best performance for the parameter for cpu galaxy mini GT-S5570?

It's your choice. But my opinion :
1. Balanced
Governor : SMARTASSV2
Max Clock : 600 Mhz / 604 Mhz
Min Clock : 122 Mhz / 245 Mhz
2. Power Saver
Governor : Interactive
Max Clock : 480 Mhz
Min Clock : 122 Mhz
3. Performance
Governor : Performance
Max Clock : 7xx Mhz
Min Clock : 7xx Mhz
Remember, it's MY opinion ONLY.

F4uzan said:
It's your choice. But my opinion :
1. Balanced
Governor : SMARTASSV2
Max Clock : 600 Mhz / 604 Mhz
Min Clock : 122 Mhz / 245 Mhz
2. Power Saver
Governor : Interactive
Max Clock : 480 Mhz
Min Clock : 122 Mhz
3. Performance
Governor : Performance
Max Clock : 7xx Mhz
Min Clock : 7xx Mhz
Remember, it's MY opinion ONLY.
Click to expand...
Click to collapse
i use
3. Performance
Governor : Performance
Max Clock :804 Mhz
Min Clock :245 Mhz
it's good or bad???

pluticoman said:
i use
3. Performance
Governor : Performance
Max Clock :804 Mhz
Min Clock :245 Mhz
it's good or bed???
Click to expand...
Click to collapse
804 Mhz is too bad, it may harm your Mini too much.

SMARTASSV2
Max 245 Mhz
Min 122 Mhz

pryerlee said:
SMARTASSV2
Max 245 Mhz
Min 122 Mhz
Click to expand...
Click to collapse
0_0....
Too low for Mini.

Try this:
Governor: ondemand (when you're not using your phone it runs on lowest cpu frequency that is set)
Max CPU: 768 (this is the biggest frequency that doesn't harm your cpu and doesn't cause freezes)
Min CPU: 122
It's perfect because when you don't use your phone battery consumption is very low and when it's used you get maximum performance from mini.

Related

[SetCPU] Share your Recomended SetCPU Setting & Tricks for X1

For me & maybe others Newbie here,
it's Hard to find the Best or Optimal SetCPU setting for My X1 as I don't have Knowledge about Overclocking Stuff & still Learning about Android
INFO:
SetCPU Application Thread
SetCPU and Advanced Settings [Tutorial & Info]
Sample Setting [it's for HD2]
So Let's Gather Our Recomended, Best & Optimal Setting Here
Please Share The Information like this:
Code:
Android Build :
Kernel :
Overclock :
[B][B][COLOR="Blue"]SetCPU Setting[/COLOR][/B][/B]
Device Detection: Auto, Custom or other
[COLOR="Red"]*if you do Custom, Please Share with us[/COLOR]
[B]Main Screen:[/B]
Max:
Min:
Scalling (Governor):
[B]Profiles:[/B]
Enable or Disable
[B]Profile Name[/B]
Max:
Min:
Scalling:
Priority:
[COLOR="Red"]*Please Share All Your Profile if You Set More than One Profile[/COLOR]
[B]Advance:[/B]
Sampling Rate:
Up Threshold:
Down Threshhold:
Ignore Nice:
Freq:
And Tell Us The Effect of your Setting...
Here My Current Setting:
Android Build : [ROM][EXT2] TouchWiz CyanogenMod6.1
Kernel : ygge's Turbo Kernel
Overclock : 652mhz (startup.txt)
SetCPU Setting
Device Detection: Autodetect
Main Screen:
Max: 633.60
Min: 122.88
Scalling (Governor): Ondemand
Profiles:
Enable
Charging
Max: 633 (maximum)
Min : 122
Scalling: Performance
Priority: 100
Screen Off
Max: 122
Min : 122
Scalling: powersave
Priority: 99
Battery < 40%
Max: 320
Min : 122
Scalling: Conservative
Priority: 98
Advance:
I Use Default, it's detect
Sampling Rate: 200000
Up Threshold: 40
Ignore Nice: 0
powersave: 0
Effect:
So far it Gives me good battery Life
Let's Share Yours
I tried to squeeze more perf out of this tiny animal but I'm not aware of the right way. Directly changed the clocks in startup.txt. First time 680, way too optimistic and it didn't even boot. After that all clocks gave errors with googlesync and android os boot, even below stock and stock itself. I think I raped my install with it.
How is the right way?
Here My Current Setting:
Android Build : [Clockwork][ROM][EXT2] HoneyComb Froyo
Kernel : ygge's Turbo Kernel
Overclock : 652mhz (startup.txt)
SetCPU Setting
Device Detection: Autodetect
Main Screen:
Max: 633.60
Min: 122.88
Scalling (Governor): Ondemand
Profiles:
Enable
Charging
Max: 633 (maximum)
Min : 633
Scalling: Performance
Priority: 100
Screen Off
Max: 122
Min : 122
Scalling: powersave
Priority: 99
Battery < 50%
Max: 480
Min : 122
Scalling: Ondemand
Priority: 95
Advance:
I Use Default, it's detect
Sampling Rate: 250000
Up Threshold: 60
Ignore Nice: 0
powersave: 0
Ok battery life

Need help at OC/UV my device!

Hello friends,
i was about to oc/uv my i9000 with insane oc kernel
and the app "voltage control".
Unfortunately i dont know how to use the app
correktly. I want to lagfix my device with ext4 later
and therefor i use "noop" as for the scheduler.
At "limit clock to:" i choosed 1200Mhz.
Now i have some options in the list.
As far as i can see there is the possibility to
uv the mhz options.
What can i choose there?
Id use damians GTO kernel....great froyo kernel and easy to OC and UV through Clockwork mod....no app needed
You should take a look..
Thx for reply,
but i thought battery life is so good at speedmod.
How it is with damian kernel?
And which uv settings do you use with your i9000?
I used these settings:
1200 mhz - 50 mv
1000 mhz - 50 mv
800 mhz - 50 mv
400 mhz - 25mv
200 and 100 mhz - 25mv
but unfortunately phone hung up.
greetz

[Q] Semaphore 1.6 beta

Unfortunately I can not post to dev section, so hopefully stratos will see my post here:
I had stock JVR with semaphore 1.5 (not v) on ext4 and everything was excellent with this brilliant kernel apart from the well known phone fc.
OC/UV was ok: quadrant scores were approx 1900-2400 on conservative cpu gov and 2500-3000 on ondemand gov.
Now, I flashed the 1.6 beta and my system is noticeably slower on *conservative* cpu gov and quadrant scores dropped clearly below 1500. Ondemand cpu gov seems to work ok but as I was alwaus on conservative I can not be abs.sure
I don't know if it is important but using voltage control app to check cpu function I see that:
a) cpu freq is wildly/unpredictably fluctuating with 1.6beta while this was not happening in 1.5 under conservative cpu gov,
and
1b) reported default voltage is different: for example with sema1.5 1200mhz had default 1275, now in 1.6beta without oc module 1000mhz is 1275 but with oc module 1200mhz have 1300mv by default.
Stratos,
could it be that a) something is broken in the new conservative cpu gov? , b) have you changed the default cpu voltage between v1.5 and v1.6beta?
GrNick said:
Unfortunately I can not post to dev section, so hopefully stratos will see my post here:
I had stock JVR with semaphore 1.5 (not v) on ext4 and everything was excellent with this brilliant kernel apart from the well known phone fc.
OC/UV was ok: quadrant scores were approx 1900-2400 on conservative cpu gov and 2500-3000 on ondemand gov.
Now, I flashed the 1.6 beta and my system is noticeably slower on *conservative* cpu gov and quadrant scores dropped clearly below 1500. Ondemand cpu gov seems to work ok but as I was alwaus on conservative I can not be abs.sure
I don't know if it is important but using voltage control app to check cpu function I see that:
a) cpu freq is wildly/unpredictably fluctuating with 1.6beta while this was not happening in 1.5 under conservative cpu gov,
and
1b) reported default voltage is different: for example with sema1.5 1200mhz had default 1275, now in 1.6beta without oc module 1000mhz is 1275 but with oc module 1200mhz have 1300mv by default.
Stratos,
could it be that a) something is broken in the new conservative cpu gov? , b) have you changed the default cpu voltage between v1.5 and v1.6beta?
Click to expand...
Click to collapse
Unfortunately I can not confirm your results. I just load the conservative governor and tested with and without overclocking. No problems here.
During benchmarking due to high load the frequency it's difficult to drop below the max. So, governor should not make the difference.
The uv value was the same in 1.5.0 (1300mv) for 1.2Ghz but it was wrongly displayed as 1275.
Thanks for you feedback. I will let you know if someone else report problems about the conservative governor.
Hey stratos, thanks for the clarification about cpu voltage.
Re cpu gov, I just did a nandroid restore and confirmed that conservative cpu gov works much better in 1.5
Any ideas on how to explore it further? There is definetely something different here.
I mean, its not just quadrant scores, its memento database loading instantly vs seconds of delay under cons cpu gov in 1.5 vs 1.6beta.
I will reflash again l8r tonight.
Anyhow, this kernel rocks! And I love the tun/netfilter module design.
Sent from my GT-I9000 using Tapatalk

Sluggish TWICS CM9

Hi everyone,
As I'm not allowed to post in development yet, let me show you my problem here.
I've installed TWICS CM9 without problems. Unfortunately, it feels very slow. LauncherPro's app drawer swiping is far from smoothness, Quadrant Benchmark gives ~1400 only.
Before that it was Darky 10.4.2 installed and it gived me ~2000 points.
Here are my cpu settings (from NSTools 1.16):
VR scheduler (also SIO tested)
Governor: lulzactive (also smartass v2 tested)
Min CPU Freq: 115 MHz
Max CPU Freq: 1380 MHz
Live OC: 115%
OC Target low: 800 MHz
OC Target high: 1400 MHz
Deep Idle ON (if that matters)
Rest stayed default.
What's wrong with that?

kernel adiutor settings for MI5

i have tried many kernel...from them...dragon xia and xceed works the best...
the thing is i am a moderate use guy...just anime episodes ...songs...web surfing and lots of calls...
i main aim is to get better battery life....performance doesnt matter to me much...as long as its stable...
from my experience xceed gives better battery life then dragon xia...but since i am new to these kind of stuff....
i would really love to have knowledge from you guys...
i would love to see if someone can provide me with the adiutor settings they have used...
currently i am on resurrection remix rom 5.8.4 (mi5 standard)
i really want a better battery life from my device
Like how much battery life you are getting? SOT as well as overall usage + SOT.. try my setup on dragonxia.. I don't use it now though..
*CPU 3 &4
Min - 307
Max - 1401
Gov - interactive
*CPU 1 & 2
Min - 307
Max - 1036
Gov - interactive
*Input boost freq core 1 - 556
*Input boost freq core 2 - disabled
*Input boost freq core 3 - 729
*Input boost freq core 4 - disabled
*Touch boost - disabled
*Set GPU at max
*Turn on backlight dimmer
*I/O sched - bfq
*Swap - 100
With daily usage on this, I can say that there's no performance decrease..it actually performs well and battery life is pretty awesome..
Tip: you can personally tweak the kernel depending on your usage..rule of thumb, CPU 3 & 4 (cores with lower clock speed) is the main driver over all..means CPU interaction triggers from here most of the time..and CPU 1 & 2 (higher clock speed) will work if you're doing extensive task like gaming..
viking_kong16 said:
Like how much battery life you are getting? SOT as well as overall usage + SOT.. try my setup on dragonxia.. I don't use it now though..
*CPU 3 &4
Min - 307
Max - 1401
Gov - interactive
*CPU 1 & 2
Min - 307
Max - 1036
Gov - interactive
*Input boost freq core 1 - 556
*Input boost freq core 2 - disabled
*Input boost freq core 3 - 729
*Input boost freq core 4 - disabled
*Touch boost - disabled
*Set GPU at max
*Turn on backlight dimmer
*I/O sched - bfq
*Swap - 100
With daily usage on this, I can say that there's no performance decrease..it actually performs well and battery life is pretty awesome..
Tip: you can personally tweak the kernel depending on your usage..rule of thumb, CPU 3 & 4 (cores with lower clock speed) is the main driver over all..means CPU interaction triggers from here most of the time..and CPU 1 & 2 (higher clock speed) will work if you're doing extensive task like gaming..
Click to expand...
Click to collapse
What does swappiness do actually?
Sent from my MI 5 using Tapatalk
cheaterfruity said:
What does swappiness do actually?
Click to expand...
Click to collapse
Speed up read and write speed of the zram which is enabled by default in our RAM.. which means snappy switching of apps..
viking_kong16 said:
Speed up read and write speed of the zram which is enabled by default in our RAM.. which means snappy switching of apps..
Click to expand...
Click to collapse
Consumes more battery?
Sent from my MI 5 using Tapatalk
cheaterfruity said:
Consumes more battery?
Click to expand...
Click to collapse
Nope.. our phone is using zram as swap..not internal storage.. zram is actually a compressed RAM that sits within RAM itself.. try to google it..

Categories

Resources