yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 General] acidmoder:
Have almost the same setup as you with the exception I could not UV -50 on all steps..... Just wondering now that we can play around with the A7 frequency, how can we run tests and be sure A7 is being used? Is there a way to shutdown the A15s?
[Galaxy S 4 General] acidmoder:
Just noticed a weird behavior. Have a video converter app called Vid Trim Pro. When I am transcoding video files the max frequency is stuck to whatever frequency I set for the max A7 core frequency on Streaks. It gets 98% cpu usage, but no higher frequency is reached...

Same is happening on Internet browsers such as Boat and Chrome. I believe alpha 5 is stickier to A7 cores!
[Galaxy S 4 General] beatsmaster0510:
Here's my current setting:

internal_read_ahead_kb=256

sd_read_ahead_kb=1024

internal_iosched=row

internal_iosched=row

digital_abs_headphone_left=-4

digital_abs_headphone_right=-4

CONFIG_BOOTED=true

CONTROLSWITCH_CPU=on

scaling_max_freq=1600000

scaling_min_freq=300000

CA7_max_freq=650000

CPU_VOLT_2000=1187500

CPU_VOLT_1900=1187500

CPU_VOLT_1800=1187500

CPU_VOLT_1700=1137500

CPU_VOLT_1600=1100000

CPU_VOLT_1500=1075000

CPU_VOLT_1400=1037500

CPU_VOLT_1300=1000000

CPU_VOLT_1200=962500

CPU_VOLT_1100=937500

CPU_VOLT_1000=900000

CPU_VOLT_900=862500

CPU_VOLT_800=850000

CPU_VOLT_750=1262500

CPU_VOLT_700=1262500

CPU_VOLT_650=1237500

CPU_VOLT_600=1187500

CPU_VOLT_550=1125000

CPU_VOLT_500=1062500

CPU_VOLT_450=1000000

CPU_VOLT_400=950000

CPU_VOLT_350=900000

CPU_VOLT_300=900000

CPU_VOLT_250=900000

CPU_VOLT_200=900000

CPU_VOLT_150=900000

CPU_VOLT_100=900000

CONTROLSWITCH_GPU=on

sgx_dvfs_max_lock=600

GPU_VOLT_700=1100000

GPU_VOLT_640=1087500

GPU_VOLT_600=1112500

GPU_VOLT_532=1062500

GPU_VOLT_480=1000000

GPU_VOLT_350=887500

GPU_VOLT_266=850000

GPU_VOLT_177=850000

hook_intercept=on

sequence_intercept=on

brightness_reduction=128

brightness_takeover_point=64

brightness_input_delta=5

s_edge_enhancement=on

de_positive_e=2

de_positive_f=2

de_positive_b=2

cs_weight=4

cs_red=0

cs_green=0

cs_blue=0

cs_yellow=0

cs_cyan=0

cs_magenta=0

scr_white_red=0

scr_white_green=0

scr_white_blue=0

switch_hp_mono=off

digital_speaker_volume=0

digital_earpiece_volume=1

switch_sp_privacy=on

switch_eq_speaker=on

switch_eq_headphone=on

eq_hp_gain_1=5

eq_hp_gain_2=4

eq_hp_gain_3=1

eq_hp_gain_4=2

eq_hp_gain_5=3

sd_iosched=noop

You may copy and paste it as text and save it on data/.perseus folder as a .profile file and apply it using StweaksProfile app. Currently on Omega 9.0 + Perseus alpha5 + Crossbreeder. Phone running good and smooth. Deep sleep is ok and no lag on daily use.
[Galaxy S 4 General] acidmoder:
Thanks a lot for sharing! Not copying because I like to try and see what happens So, I am using it as a guide. :)

After some tweaking it is all smooth. Cpu ranging from 200 to 1800 MHz and snappy as hell! I probably have screwed up with little core frequencies!

Cheers!
[Galaxy S 4 General] irishrally:
I was wondering where you went.
[Galaxy S 4 General] croach246:
I too would like to know if there is a way to shut down the A15s. I think that would yield great battery improvements.. (alpha 6?) Plus 1200MHz should be more than enough for everyday usage (obviously if you want to do something that you really need some umpf change the profile)
[Galaxy S 4 General] acidmoder:
You are reading my mind!

Not really sure why this has not been implemented so far. It may not be as straightforward as I imagine. I would say 600 Mhz would do the job for most of my general phone use (yeah, I don't play games :angel:). Don't like to see CPU reaching 1.8 Ghz when scrolling my twitter widget on the home screen. Of course you can always use CPU underclocking and profiling, but it would be nice to simply shutdown those A15s.
[Galaxy S 4 General] ivanchin99:
One way to do that is to set the maximum frequency at 600mhz. Then it wont activate the A15 cores
[Galaxy S 4 General] skivnit:
At 750 if you can then you get the best of both worlds as it hardly goes above 1500 MHz unless you are gaming. At least that's what I did and I'm getting better battery life
[Galaxy S 4 General] acidmoder:
Yup, that is what I do for now when I want a slightly better battery life. But how about running at 1500 Mhz on A7 cores only? I have overclocked my A7 to run at 1500 Mhz, but can't guarantee the the A15s won't come into action when I set the CPU Max = 1500 Mhz.
[Galaxy S 4 General] ivanchin99:
Assuming no over clocking. A7 runs on 100-600mhz. Above 600 (800mhz) you activate the A15 cores. Note that you'll have to times 2 to get the actual clock.

Hence, 600mhz is actually running at 1200mhz.

If you want only the A7 to come alive at 1500mhz, you will have to set the max frequency at 750mhz. Stweaks doesn't allow 50mhz increment, try system tuner.

Or you can try a more conservative overclock with 700mhz.
[Galaxy S 4 General] acidmoder:
Thanks I am aware of this! I am running smooth with no issues setting A7 to 750 Mhz/1275 mV on STweaks and using SetCPU to play with max/min frequencies :cool:

However, there is something a little cloudy for me still. If I limit max freq to 1500 Mhz how can I learn which core (A7/A15) is really in use when I see my current clock at 1500 Mhz?
[Galaxy S 4 General] mw86:
If ANY monitor tool shows over 750mhz your using A15. 1500mhz is only A15 as if your running 1500mhz A7 the monitor app shows 750mhz. So if you ever see 800-2000mhz that is A15 cpu. Cool Tool is easy enough to use to monitor this. 100/150/200/250/300/350/400/450/500/550/600/650/700/750 show in cool tool is 200/300/400/500/600/700/800/900/1000/1100/1200/1300/1400/1500mhz A7

800/900/1000/1100/1200/1300/1400/1500/1600/1700/1800/1900/2000 in cool tool is exactly same mhz shown and is all A15 mhz.
[Galaxy S 4 General] acidmoder:
Great, thank you very much for bringing some light to this subject! At least for me! :)I have been using Cool Tool indeed.:good:
[Galaxy S 4 General] croach246:
Indeed, thanks.

On the contrary, I'm currently limiting cpu max to 1300mHz, and UV - 50. However I've had to increase the minimum cpu states (150,200,250,300) back to their stock voltages..

Reason being I would find the phone would randomly shut down after maybe an hour of the screen off... Like I said this was random, happened 3 times one day, and I'd have to hold the power button for 10s before the phone would turn back on.

Anyone else experienced these issues?

(omega v8, Perseus 3.4)
[Galaxy S 4 General] mw86:
Yes experienced this myself but not issue it's undervolt. I have one of the weaker or average cpus and mine requires mostly stock. Surely i could be dropping a few mv here and there but I want a super fast stable phone that doesn't reboot, fc to home screen in apps, freeze or even subtle problems as network issues which are very possible to happen when data is transferred as to have low latency speed the cpu needs to be highly responsive and whwn undervolted all else could be stable and network issues happen randomly. I've tried a lot and it brings me back to my main point I had started undervolt on this cpu. To get mhz stable. Some need overvolt and some have different stock voltages based ln detected chip quality. Those lower volt tables may need a raise on some mhz for overclocks to work. Mine is already on high volts stock defaults for mine. So i tested and found for example stock my 1.7 is stable in anything i throw at it even repeated tests where i push it up in heat. Chainfire so far has been great in this as its one long test and heavy cpu loads. Ive got 1.8 stable and for me testing endurance under high heat and extended loads i needed undervolt for it. Others may need opposite especially those with lower stocl volt tables. All my voltages are fully stock except 1800mhz. Mine shown 1250 stock and mine started to be stable at 1175 and im using 1200mv so it can take high heat under load and not suddenly crash.

Reference my 1800-2000mhz stock is 1250mv. A friend's starts lower on those and all of the frequency. Some cpus like these need a proper minimum voltage, though some take like 800mv on a7 the default like mine is 950mv min for 100-700 a7 and my friends 100-800 is 950mv. Consider it a padding of voltage needed. Technically todays loads on low mhz of these cores is very heavy work on them vs the higher mhz hence their need the a7's to have such high mv for the same mhz compared on an a15.

Currently a common way to get a reboot random easily is trying the a7 at 1500mhz on some handsets like mine and from what I gather from Andrei's own provided info his aswell?!? Mine has no random reboot on 1400mhz a7 cores. I came to conclusion mine can't use 1500mhz when i tried various volts and stock shown volts in chanfire two three runs in row max and it would crash or reboot. Benchmark showed it but I had the random reboot not running the bench just idle and unlock screen sometimes so I can consider that mhz unstable for my cpu and move on.
[Galaxy S 4 General] croach246:
Hmm. Lots of info there. I'm wondering how you manage to get the a7 cores up to 1400 and 1500mhz.. Highest mine go is 1200MHz...?

I noticed the shutting off of the phone after extended inactivity was greatest when I forced the cpu to 150mhz when screen off, less at 200MHz, and almost non existent with stock voltages from 150-300mhz (while the rest were - 50mv) and not forcing a cpu state when screen off. I assume the phone would hit a state where there was simply not enough processing power and shut itself off/crash.
[Galaxy S 4 General] mw86:
I don't recommend a screen off profile but if there is one I would think you should set your max a7 mhz there such as 600/650/700/750. Or perhaps 800 for minimum A15 as your max screen off. Stays cool but can finish a workload faster when it is necessary. I don't use a screen off profile on mine as the governor and the unique design of the Octa runs the mhz in most cases needed for a workload.

Your inquiry I'd say it was not lack of processing power but voltage to keep that mhz stable. You seem to see the correlation between low mhz being forced to work through perhaps heavy workloads than are suited for the cores its running on and the low mhz on a screen off profile. If you drop those volts tpo low those mhz simply cannot stay stable completing the work the cpu has been assigned even on screen off our phones can wake up and have a process run and stop quick.

The idea is where a lot of people apply a number pulled out of a hat dropped off all mhz to start testing doesn't lead necessarily to a stable undervolted cpu.

You can test loads on a mhz by using user space gov and set min max to same mhz, same way I tested 750mhz. Ypu cant cap the mhz that drives the cluster migration to anything but 700 or 800 mhz max so this seemed effective in setting specific mhz to idle and test on Chain fire. Also another good method especially testing high A15 mhz is set the max mhz to the mhz your trying to test stability on. Say i wanted 800 a15 stable on a undervolt. I'd set my max to 800mhz and test in a bunch of heavy benchmarks and daily usage. Screen power on for example puts quite a heavy cpu load on and very sudden. If such stuff makes phone unstable the volts should be returned to more stock values.

Here is my stweaks pic of those mhz for you. Other's phone may have lower volt tables stock no doubt. If yours has lower volts yours may need volts mine shows to stabilize 1400mhz A7. I have not found an undervolt using my stock max on a7 to stabilize 1500mhz, but start testing on stock volts always before adding undervolt. Also start testing lower mhz before the higher, ie for a7 max try 1300/1400/1500 in that order ie cool tool shows 650/700/750.

Im using stock for all mhz except 1800mhz and my min a7 is 200mhz(100 cool tool) to 1400mhz (700) and 800- 1800 on the a15.

Im using 1200mv on 1800mhz.
[Galaxy S 4 General] croach246:
A word of advice before flashing!

Just flashed alpha5 coming from 3.4 on omega v8 rom, phone would reboot after 10s or so after booting, then would get stuck in a boot loop. Tried refreshing etc. Ended up flashing the rom again then flashing alpha5 (working now).

I believe the voltages I had set on android tuner to apply when booting may have been causing this. So reset voltages to stock, disabled apply on boot then reflected rom.

---------- Post added at 03:41 AM ---------- Previous post was at 03:36 AM ----------

@mw86

Cool. Just reluctantly flashed alpha 5 since omega v8 and 3.4 was running so smooth, but I see alpha5 has some settings I wanted to mess with that 3.4 didn't. Will start messing around and provide any valuable feedback I come across as well
[Galaxy S 4 General] mw86:
Personally I would always upgrade to Andrei's latest on github whenever possible. Goodluck on the tinkering. I only use Stweaks and scripts but to test using userspace gov i used rom toolbox cpu section just to change governor and the mhz min and max there. I still left my normal setup in stweaks set on boot and i didn't set on boot in rom toolbox so nothing was permanent at boot. Android tuner is a good app but using Andrei's Stweaks controls tend to work 100% for any new implemented features like gpu over clock and a7 max mhz over clock.

Yes there is a good chance the way you had set Android Tuner for volts may have caused issues with how the kernel is set up now for a7 clocks. Likely you can go back to setting like before as it should load the new tables according to the new mhz available but I still would use Stweaks for everything it allows setting.
[Galaxy S 4 General] jlevy73:
Which Chainfire app are you using for the stress test? I'm not aware he had one, I know setcpu does. Thanks in advance.
[Galaxy S 4 General] mw86:
https://play.google.com/store/apps/details?id=eu.chainfire.cfbench

Its not a stability test it's his benchmark but it ran once or even twice or more in a row creates a lot of heat and stress for low or high frequency.
[Galaxy S 4 General] jlevy73:
Yes I do the same thing. The problem is that this kernel benches low for me, so it's hard to tell if that's just throttling kicking in or instability. I guess if it was too unstable it would crash.
[Galaxy S 4 General] mw86:
Java scores bad on my setups ive tested on that bench but native score is cpu intensive too and likely its throttling. If your seeing drops from your max mhz to 1.4 or lower under load its kicking in.
[Galaxy S 4 General] gp545:
I'll be really thankful, if someone help me out to set values in "Screen" tab. :fingers-crossed: Tried to set various values, messed up every time! :bang-head:
[Galaxy S 4 General] croach246:
^^

True. I know little about the screen settings.. Altho I don't see any major gains to be had from tinkering... Anyone care to call me a crazy and explain??
[Galaxy S 4 General] noideaforusername:
Check enable master sequence and you good to go :)
[Galaxy S 4 General] beatsmaster0510:
Benchmark after alpha 6.1 tweaking

Sent from my GT-I9500
[Galaxy S 4 General] gp545:
Have master sequence enabled and rest of them all are on default state though.

Wanted to know what's the best settings.. Thanks by the way..
[Galaxy S 4 General] mashaal95:
Configuration? :)

Can you tell us your exact configuration, or the way you have tweaked it please? :)
[Galaxy S 4 General] hotheabilly:
Impressed with alpha 6.1 although this benchmark sometimes not accurate

1700Mhz A15 and 1500Mhz A7 running together with 640Mhz PowerVR SGX.
[Galaxy S 4 General] mw86:
Could you graciously post the volt table you have for A7 the top half with the overclock mhz. Mine only has 1312mv as highest available. I wish i was able to apply up to 1325/1350 on the A7 max on mine. I am unsure if it is a preset base on detected cpu binning or if it is the A7 max volt would could ever set.
[Galaxy S 4 General] AndreiLux:
It's a safety limit and I won't allow people to go over it.
[Galaxy S 4 General] hotheabilly:
Yes, overvolting too much can cook your chip well :banghead:

[MENTION=4745870]mw86[/MENTION] here is my default.profile

internal_read_ahead_kb=512

sd_read_ahead_kb=1024

internal_iosched=row

internal_iosched=row

digital_abs_headphone_left=-4

digital_abs_headphone_right=-4

CONFIG_BOOTED=true

CONTROLSWITCH_CPU=on

scaling_max_freq=1700000

scaling_min_freq=300000

CPU_VOLT_2000=1187500

CPU_VOLT_1900=1131250

CPU_VOLT_1800=1112500

CPU_VOLT_1700=1087500

CPU_VOLT_1600=1068750

CPU_VOLT_1500=1050000

CPU_VOLT_1400=1025000

CPU_VOLT_1300=1012500

CPU_VOLT_1200=981250

CPU_VOLT_1100=962500

CPU_VOLT_1000=937500

CPU_VOLT_900=912500

CPU_VOLT_800=881250

CPU_VOLT_600=1143750

CPU_VOLT_550=1106250

CPU_VOLT_500=1062500

CPU_VOLT_450=1006250

CPU_VOLT_400=975000

CPU_VOLT_350=937500

CPU_VOLT_300=912500

CPU_VOLT_250=900000

CPU_VOLT_200=900000

CPU_VOLT_150=900000

CPU_VOLT_100=900000

CONTROLSWITCH_GPU=on

sgx_dvfs_max_lock=640

GPU_VOLT_700=1100000

GPU_VOLT_640=1068750

GPU_VOLT_600=1031250

GPU_VOLT_532=1012500

GPU_VOLT_480=975000

GPU_VOLT_350=918750

GPU_VOLT_266=893750

GPU_VOLT_177=893750

hook_intercept=on

sequence_intercept=off

brightness_reduction=128

brightness_takeover_point=64

brightness_input_delta=5

s_edge_enhancement=off

de_positive_e=2

de_positive_f=2

de_positive_b=2

cs_weight=4

cs_red=0

cs_green=0

cs_blue=0

cs_yellow=0

cs_cyan=0

cs_magenta=0

scr_white_red=0

scr_white_green=0

scr_white_blue=0

switch_hp_mono=off

digital_speaker_volume=0

digital_earpiece_volume=1

switch_sp_privacy=off

switch_eq_speaker=on

switch_eq_headphone=on

eq_hp_gain_1=5

eq_hp_gain_2=4

eq_hp_gain_3=1

eq_hp_gain_4=2

eq_hp_gain_5=3

sd_iosched=row

vnswap_size=0

max_pool_percent=20

swappiness=60

CA7_max_freq=750000

CPU_VOLT_2000=1187500

CPU_VOLT_1900=1131250

CPU_VOLT_1800=1112500

CPU_VOLT_1700=1087500

CPU_VOLT_1600=1068750

CPU_VOLT_1500=1050000

CPU_VOLT_1400=1025000

CPU_VOLT_1300=1012500

CPU_VOLT_1200=981250

CPU_VOLT_1100=962500

CPU_VOLT_1000=937500

CPU_VOLT_900=912500

CPU_VOLT_800=881250

CPU_VOLT_750=1275000

CPU_VOLT_700=1262500

CPU_VOLT_650=1225000

CPU_VOLT_600=1143750

CPU_VOLT_550=1106250

CPU_VOLT_500=1062500

CPU_VOLT_450=1006250

CPU_VOLT_400=975000

CPU_VOLT_350=937500

CPU_VOLT_300=912500

CPU_VOLT_250=900000

CPU_VOLT_200=900000

CPU_VOLT_150=900000

CPU_VOLT_100=900000

led_lowpower_current=50

led_highpower_current=80

led_fade=on

led_fade_in_time=300

led_fade_out_time=750

led_blink_retention=350

led_blink_delay=500

led_noti_r=254

led_noti_g=254

led_noti_b=50

1700Mhz A15 and 1500Mhz A7 running together with 640Mhz PowerVR SGX.
[Galaxy S 4 General] djigane:
I don't know if I have the best in both worlds (performance + battery), but here's my antutu score :

Envoyé depuis mon GT-I9500 avec Tapatalk

---------- Post added at 12:34 AM ---------- Previous post was at 12:29 AM ----------

And here's my stweaks settings:

internal_read_ahead_kb=256

sd_read_ahead_kb=1024

internal_iosched=row

internal_iosched=row

digital_abs_headphone_left=0

digital_abs_headphone_right=0

CONFIG_BOOTED=true

CONTROLSWITCH_CPU=on

scaling_max_freq=1600000

scaling_min_freq=300000

CPU_VOLT_2000=1187500

CPU_VOLT_1900=1187500

CPU_VOLT_1800=1187500

CPU_VOLT_1700=1137500

CPU_VOLT_1600=1100000

CPU_VOLT_1500=1075000

CPU_VOLT_1400=1037500

CPU_VOLT_1300=1000000

CPU_VOLT_1200=962500

CPU_VOLT_1100=937500

CPU_VOLT_1000=900000

CPU_VOLT_900=862500

CPU_VOLT_800=850000

CPU_VOLT_600=1187500

CPU_VOLT_550=1125000

CPU_VOLT_500=1062500

CPU_VOLT_450=1000000

CPU_VOLT_400=950000

CPU_VOLT_350=900000

CPU_VOLT_300=900000

CPU_VOLT_250=900000

CPU_VOLT_200=900000

CPU_VOLT_150=900000

CPU_VOLT_100=900000

CONTROLSWITCH_GPU=on

sgx_dvfs_max_lock=600

GPU_VOLT_700=1100000

GPU_VOLT_640=1087500

GPU_VOLT_600=1112500

GPU_VOLT_532=1062500

GPU_VOLT_480=1000000

GPU_VOLT_350=887500

GPU_VOLT_266=850000

GPU_VOLT_177=850000

hook_intercept=on

sequence_intercept=on

brightness_reduction=110

brightness_takeover_point=50

brightness_input_delta=40

s_edge_enhancement=on

de_positive_e=0

de_positive_f=0

de_positive_b=0

cs_weight=0

cs_red=0

cs_green=0

cs_blue=0

cs_yellow=0

cs_cyan=0

cs_magenta=0

scr_white_red=0

scr_white_green=0

scr_white_blue=0

switch_hp_mono=off

digital_speaker_volume=0

digital_earpiece_volume=0

switch_sp_privacy=off

switch_eq_speaker=on

switch_eq_headphone=on

eq_hp_gain_1=4

eq_hp_gain_2=3

eq_hp_gain_3=1

eq_hp_gain_4=2

eq_hp_gain_5=3

sd_iosched=noop

vnswap_size=0

max_pool_percent=20

swappiness=60

CA7_max_freq=650000

CPU_VOLT_2000=1187500

CPU_VOLT_1900=1187500

CPU_VOLT_1800=1187500

CPU_VOLT_1700=1137500

CPU_VOLT_1600=1100000

CPU_VOLT_1500=1075000

CPU_VOLT_1400=1037500

CPU_VOLT_1300=1000000

CPU_VOLT_1200=962500

CPU_VOLT_1100=937500

CPU_VOLT_1000=900000

CPU_VOLT_900=862500

CPU_VOLT_800=850000

CPU_VOLT_750=1262500

CPU_VOLT_700=1262500

CPU_VOLT_650=1237500

CPU_VOLT_600=1187500

CPU_VOLT_550=1125000

CPU_VOLT_500=1062500

CPU_VOLT_450=1000000

CPU_VOLT_400=950000

CPU_VOLT_350=900000

CPU_VOLT_300=900000

CPU_VOLT_250=900000

CPU_VOLT_200=900000

CPU_VOLT_150=900000

CPU_VOLT_100=900000

led_lowpower_current=5

led_highpower_current=40

led_fade=on

led_fade_in_time=300

led_fade_out_time=1300

led_blink_retention=350

led_blink_delay=3250

led_noti_r=0

led_noti_g=0

led_noti_b=254

Envoyé depuis mon GT-I9500 avec Tapatalk
[Galaxy S 4 General] jianlinooi:
anyone can do glbenchmark for 640mhz gpu?
[Galaxy S 4 General] zetlaw:
i think something is wrong with Alpha 6.1

i locked the clock to 250 mhz to test stability. my phone is still stable at 700000mv at 500mhz A7 cpu.

i think the stweaks doesnt execute the changes in voltage. its weird.
[Galaxy S 4 General] nealkoy:
You can try alpha 6.2
[Galaxy S 4 General] zetlaw:
oops i ment 6.2 sorry.

---------- Post added at 11:25 AM ---------- Previous post was at 11:21 AM ----------

I Think i found the problem.

What the value

Controlswitch_cpu=off

Means ?

Nope that didnt solve it.
[Galaxy S 4 General] mw86:
Trick is simple. Cpu volt doesn't switch once your staying on a mhz bud. Simply reenable scaling to an idle frequency and then apply volts and lock mhz once on the mhz you are testing after. The new volts apply the next time cpu hits the frequency you changed but can't apply till it visitited another mhz and returns to that mhz you changed it on. I found the same thing testing 1500mhz a7. Thanks Andrei for your statement on the voltage. I think I have got a stable setup thanks to a combo of both the voltage tables posted before. They were very helpful. I used the higher of the two voltage for each overclock step above 1200mhz A7. Thanks Andrei and users above that helped me with the voltage.

I still went back to max on 1500 after some reboots but it stopped. Thanks.
[Galaxy S 4 General] tabenf:
What should I wipe before flashing this kernel!
[Galaxy S 4 General] TheMrcool212:
No need to wipe anything, as it is a kernel.

Sent from my Galaxy S4 i9500
[Galaxy S 4 General] HassanM:
Hi friends....

I'm on Perseus 6.2 w/ Omega ROM 10 / Crossbreeder...

I'm using Ondemand-Sec as my Governer.... I selected it in SetCpu

Just wanted to tweak this Governer in SetCpu... Actually I wanna change certain values for performance such as:

- Up Threshold

- Sample Rate

- Sampling Down Factor

- Down Differential

- Frequency Step

Up Threshold from 90 to 80

Sample Rate from 100000 to 80000

Sampling Down Factor from 1 to 2

Somehow I don't see Down Differential & Frequency Step .... Moreover when I change the Up Threshold value to 80, it reverts back to default (90)...

Can anyone plz advise/ suggest???

Thanks
[Galaxy S 4 General] stanley08:
There's a way to apply this by pasting it somewhere instead of manually setting them in Stweaks. Yes? What i really want now is best battery life.
[Galaxy S 4 General] iede:
Dear AndreiLux,

Thanks for your great kernel. I've been using your kernel since SGS3 era :fingers-crossed:

love your screen calibration thing. But in SGS4 when I'm playing a video, our screen suddenly change to greenish tint (isn't it?).

This happens to before XXUMEA when the keyboard pops up.

Do you think this is kernel related or ROM related? I'm wondering if this greenish tint can be solved :)

Once again thanks for your great kernel! :good: