F4ktion kernel settings discussion - Galaxy S 4 Mini General

This thread is for posting and discussing ones kernel settings.

TIP 1#
To prevent random reboots, turn the the default undervolting off in options and tick set on boot (sorry can't provide screenshot right now)

Dont know if its the best way to configure it but heres mine.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

AndreAkaNick said:
Dont know if its the best way to configure it but heres mine.
Click to expand...
Click to collapse
What ROM/Theme u are using ?

pedromms86 said:
What ROM/Theme u are using ?
Click to expand...
Click to collapse
CM11, MIUI6 Theme and Xposed Flat Style Module for the status bar.

Aronuser said:
TIP 1#
To prevent random reboots, turn the the default undervolting off in options and tick set on boot (sorry can't provide screenshot right now)
Click to expand...
Click to collapse
This does nothing. The Random Reboot problem is a problem with the kernel itself.
If anyone have problems with F4k kernel just use stock cyanogenmod kernel.

iFlasher said:
This does nothing. The Random Reboot problem is a problem with the kernel itself.
If anyone have problems with F4k kernel just use stock cyanogenmod kernel.
Click to expand...
Click to collapse
well i remember that i had random reboots and i disabled that, so it stopped. i thought maybe the chips data became buggy because of low voltage

I'm using smartmax with fiops , 182-1458 mhz very battery friendly. Any other good settings ?

Ursurobertt said:
I'm using smartmax with fiops , 182-1458 mhz very battery friendly. Any other good settings ?
Click to expand...
Click to collapse
i use fiops too cause it's improved for flash drives and i've freq from 162-810 mhz it's still smooth enough for messaging and browsing and maximum battery saving i think. i also have multi core power saving at "on" cause i think it's useful

AndreAkaNick said:
Dont know if its the best way to configure it but heres mine.
Click to expand...
Click to collapse
Wht app is this
Sent from my unknown using XDA Free mobile app
---------- Post added at 10:55 AM ---------- Previous post was at 10:52 AM ----------
Aronuser said:
i use fiops too cause it's improved for flash drives and i've freq from 162-810 mhz it's still smooth enough for messaging and browsing and maximum battery saving i think. i also have multi core power saving at "on" cause i think it's useful
Click to expand...
Click to collapse
If you're like me who likes to game n also save battery life,
Max: 1Ghz
Min: 162mhz
Governor: Smartmax
I/O: FIOPS
I too switched Multicore power saving. Ran Asphalt 8 in Very low graphics (since i find special effects to be annoying) and it works smooth. Very minor stutter.
Sent from my unknown using XDA Free mobile app

TiTAN-O-One said:
Wht app is this
Sent from my unknown using XDA Free mobile app
---------- Post added at 10:55 AM ---------- Previous post was at 10:52 AM ----------
If you're like me who likes to game n also save battery life,
Max: 1Ghz
Min: 162mhz
Governor: Smartmax
I/O: FIOPS
I too switched Multicore power saving. Ran Asphalt 8 in Very low graphics (since i find special effects to be annoying) and it works smooth. Very minor stutter.
Sent from my unknown using XDA Free mobile app
Click to expand...
Click to collapse
Faux123 Kernel Enhancement Pro ?

I typically set min CPU freq to 162 and max to 1458 with Wheatley Governor.
I/O:Fiops
Disable MPDecision, and enable msm-hotplug
Hyst value 4/threshold-722.
Entropy read_1024 write_2048

Related

Desire HD and SetCPU

Is there anyway to make setcpu works with my desire hd?
Visionary is working perfectly but I think perflock is blocking the speeds control. If I try to stop it with the menu command it gives me an error message.
Please If you find any solution post it... I'd like to save some Battery limiting the cpu frequencies
Sent from my Desire HD using XDA App
UPDATE yesterday. Working great. Battery life 30% more!
Sent from my Desire HD using XDA App
Endr1 said:
UPDATE yesterday. Working great. Battery life 30% more!
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
???????
Is it temporary, as you used Visionary?
Love_Velvet said:
Is it temporary, as you used Visionary?
Click to expand...
Click to collapse
Since the update setcpu works perfectly with visionary. We DHD users can now disable perflock and control cpu frequency. Life is good.
If you set visionary to root your DHD on boot then you don't have any issues with things being "temporary". Well technically they are but you won't notice.
Have all installed on mine but i cant find a way to go above stock speed, is there a way to do this ?
Endr1 said:
Battery life 30% more!
Click to expand...
Click to collapse
What cpu frequency's are you setting in place to gain 30% more battery life?
Hi.
To use setcpu on the desire hd you should first root it with Visionary (set it to run on boot). Then you can dowload the app and launch it. When it has the root permission you should press the menu button on the main screen and use PERFLOCK disable. (set it ti run on boot too).
When perflock is disable setcpu take control of the clock speed.
My settings are:
When screen is off, speed is set to 245min-245max. this will grant you lot of spare juice from battery, only con is the 3 or 4 second lag when you turn the screen on. It needs some moments to put speed back to 1024. Not big deal if you get use to it.
Then when battery is under 50% I set it to 245min-768max. this will reduce the power need of the beast of a little 10%, means like 1,5h more standby time.
When power is under 20% I reduce the speed again to 245min-368max. In this config the phone react like my oldtime beloved hero...
I do not use the htc battery saving.
Hope it helps!
boarne71 said:
Have all installed on mine but i cant find a way to go above stock speed, is there a way to do this ?
Click to expand...
Click to collapse
You can not Overclock the stock Kernel.
Thank you for the post Endr1, quite interesting.
I can use SetCPU, I can manage profiles, but I cannot OC the device beyond the 1024 MHz
I have tried several CPU frequencies with SetCPU (very nice and simple tool, love it!) and noticed that overclocking the Desire HD to 1459MHz seems to be ideal. With higher OC speeds I do not get better performance (if I may believe Quandrant standard benchmarking tool).
I have LordMod kernel + CoreDroid v9.2 running.
Here you can see benchmark before OC
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And here after
Benchmarks have been run a few times to check if correct, and each time the score was around this so I consider it trusthworthy.
hello, what "governors" do you choose?

G2 benchmark... numbers sucked!

Just flashed enoms g2 rom and I cleared up what I can, tried making it efficient.I ran some benchmark tests on quadrant standard and was kinda disappointed in the numbers. My bests score was low 1100 after that it was 850,900, 835... very basic stuff any suggestions???
Sent from my T-Mobile G2 using XDA App
If you ran the benchmark on battery power, try plugging the phone in. Sometimes the CPU will underclock itself to save power. If that doesn't work, download SetCPU (google it) and make sure that the max speed is set above 800 MHz.
On the stock G2 ROM I was getting 1600-1800... maybe it's the ROM your using
omarsalmin said:
On the stock G2 ROM I was getting 1600-1800... maybe it's the ROM your using
Click to expand...
Click to collapse
Yeah this is the typical range for a stock G2.
Those scores in the OP are so low, its almost like hes underclocking or something. Or possibly a running application using a ton of resources?
i got 2064. but i was running virtuous.
im running enom's rom and i had it underclocked at 768 and i was still able to get 1609
Stargazer418 said:
If you ran the benchmark on battery power, try plugging the phone in. Sometimes the CPU will underclock itself to save power. If that doesn't work, download SetCPU (google it) and make sure that the max speed is set above 800 MHz.
Click to expand...
Click to collapse
Umm... No... The CPU doesn't underclock to save power...
gravis86 said:
Umm... No... The CPU doesn't underclock to save power...
Click to expand...
Click to collapse
Perhaps the kernel has an undervolting profile built in and it's triggered by a < battery percentage?
Sent from my HTC Vision using XDA App
What should I have my phone clocked at with enoms rom?? I dnt have much running at all I dnt understand why its so slow, I was gunna flash the latest kernal and try that... clock settings please anyone
Edit: jus tweaked my clock on spareparts. I switched cpu governor from ondemand to performance and the clock setting. I put underclock at the lowest and overclock at the max highest... benchmark test put up a 2200... I feel as if this will drain battery like crazy only time will tell... what do u think, should I drop the overclock? Is it safe at that high number???
Sent from my T-Mobile G2 using XDA App
If I run with Flippy's kernel, CM 6.1.1 Stable and OC my phone to 1.8 GHz, I can get a Quadrant score of 3037 (screenshot below). With it OC'd to 1.4 GHz (my normal OC setting) I can get around 2500.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If I'm averging 2500 I'm fine wit that my current settings are Enoms Rom
Using enoms cpu controls
Cpu governor: performance
Max frequency: 1,516,800
Min frequency 245,760
I dropped 3 percent in battery writing this message.... my main concern is battery and overworking the cpu.... I'm thinking about downloading set cpu and clocking the performance settings then set it for power save after a certain drop point........ does this sound logical?
Sent from my T-Mobile G2 using XDA App
When you set your cpu to performance it means your cpu will stay at max all the time and it never goes down which is why you are getting bad battery life.
There is no need for that.
Yes you can do that with setcpu
Sent from my HTC Vision using XDA App
Maybe you tested your Samsung Galaxy s by mistake?..lol..just joking.
I score around 2500 on quadrant:
OC'd to 1.4 (normally run 1.2)
SetCpu On Demand
CyanogenMod 6.1
fablife said:
Maybe you tested your Samsung Galaxy s by mistake?..lol..just joking.
Click to expand...
Click to collapse
Hey! Not funny! My vibrant gets 2035 in the quadrant! But I'm going to get myself a g2 because I miss the hardware keyboard
Got me 2813 with Virtous 0.9 <---- (sense rom btw) and eVil's latest Glacier based kernel @ 1.5ghz... life is good
Sent from my HTC Vision using XDA App

[Q] OC/UV Beater2v1.7 makes my phone unstable with default values, help!

Ok I need to narrow down if I'm doing something wrong, or if my phone is actually faulty.
I have the latest Virtuous Affinity Rom, and installed OC/UV Beater, and I cannot seem to find a stable setting, and after using the VDD/OC reset .zip's that are supposed to reset everything to normal, I still have the issues.
I'm new to the whole OC the phone thing, can someone tell me if my voltages are far off what they should be for my phone.
ALSO could anyone supply me with their virgin (or stable working) files from their MT4G found in the sys/devices/system/cpu/cpu0/cpufreq/ folder so I can double check mine?
It seems below the 537600mhz is where I'm unstable. I stress tested 3 freq at a time and went down the list, that's where I would get the issues.
My OC settings in OC/UV Beater are:
Wake Gov: ondemand
Wake Min: 122000
Wake Max: 1459200
Sleep Gov: conservative
Sleep Min: 122000
Sleep Max: 460800
VDD:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can think of 2 things.
1) Your wake min is WAY too low. That alone could be the issue.
2) Try bumping the voltage on higher frequencies up a notch.
Asking us if your voltages are ok is asking us a question we can't answer. Always start with default voltages. If that gives you stability VERY slowly adjust your voltage down a notch at a time, allowing time and testing between each setting. Never set on boot until you're SURE it's stable.
Sent from my HTC Glacier using xda app-developers app
estallings15 said:
I can think of 2 things.
1) Your wake min is WAY too low. That alone could be the issue.
2) Try bumping the voltage on higher frequencies up a notch.
Asking us if your voltages are ok is asking us a question we can't answer. Always start with default voltages. If that gives you stability VERY slowly adjust your voltage down a notch at a time, allowing time and testing between each setting. Never set on boot until you're SURE it's stable.
Sent from my HTC Glacier using xda app-developers app
Click to expand...
Click to collapse
Thanks for that. I understand what you are saying as I have been overclocking my PC for years, however, what I don't understand is why does OC/UV Beater2 seem to not be stable at all stock clocks and voltages when I stress test.
I have now gotten 1.5Ghz through 537600mhz stable, however, I cannot get 460mhz through 122mhz stable at stock volts, but it is stable with the voltage boost I have added. I'm curious to see if maybe my default voltage settings have gotten corrupted or misconfigured, that's why I am looking for someone to fill me in on the stock VDD and Freq for my cpu.
Also looking for advice as to what I have set there is normal voltage for the frequencies there?
Just looked at mine on cm 7.2. Your voltages look a little low across rhe board. Clear the data on oc/uv beater and reflash your kernel.
Sent from my HTC Glacier using xda app-developers app
Awesome, when you get a chance could you give me some screen shots of your voltages or tell me how much more yours are boosted?
Well, I'm on a different ROM now, but maybe this will help you. The voltages on this kernel are pretty low.
Sent from my HTC Glacier using xda app-developers app

[Q] What are the default CPU frequencies and governor?

What is the default CPU min/max frequencies and the governor being used? (on stock kernel)
My guess is that the max is 1512 and min is 384. But I'm really not sure what governor is used by default.
Anyone know?
Ondemand
Sent from my Nexus 4 using XDA Premium HD app
Defaults are as follows:
MIN: 1026MHz
MAX: 1512MHz
CPU govenor: ONDEMAND
xandr00 said:
Defaults are as follows:
MIN: 1026MHz
MAX: 1512MHz
CPU govenor: ONDEMAND
Click to expand...
Click to collapse
The default minimum is 1026??? Are you sure? Why would it be set to keep running so high? I heard that it doesn't fall from 1026 to 384 easily until 5-6 seconds have passed...but if 1026 is the minimum..then, smh
Is the default I/O CFQ?
Max - 1512
Min - 384 (CPU Apps don't show it correctly)
Govenor - Ondemand
I/O - Noop
Harry GT-S5830 said:
Max - 1512
Min - 384 (CPU Apps don't show it correctly)
Govenor - Ondemand
I/O - Noop
Click to expand...
Click to collapse
The fact that CPU apps don't show the minimum frequency properly, and the fact that it hangs on 1026 for a few seconds before dropping to 384...do you think that indicates a problem?
I don't know if the minimum is actually 1026 or not but I know for a fact that when you TOUCH the screen, it does ramp up to 1026. So that can be a explanation why battery life isn't as good in reviews.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
zephiK said:
I don't know if the minimum is actually 1026 or not but I know for a fact that when you TOUCH the screen, it does ramp up to 1026. So that can be a explanation why battery life isn't as good in reviews.
Click to expand...
Click to collapse
I remember with my i9300, as soon as you touched the screen, it would ramp up to 800mhz. It has to do with project butter. It does keep everything running smooth, at the cost of battery life.
K Rich said:
I remember with my i9300, as soon as you touched the screen, it would ramp up to 800mhz. It has to do with project butter. It does keep everything running smooth, at the cost of battery life.
Click to expand...
Click to collapse
never heard such of a thing on the galaxy nexus (might of been present but no one ever mentioned it so im not sure how GN reacts to that). first time ive heard of it.
battery life has been nothing but exceptional for me on N4 and GN. didnt notice a difference between 4.1 and 4.0.x for battery life. it stayed the same or slightly gotten better.
i recommend using franco kernel though
zephiK said:
never heard such of a thing on the galaxy nexus (might of been present but no one ever mentioned it so im not sure how GN reacts to that). first time ive heard of it.
battery life has been nothing but exceptional for me on N4 and GN. didnt notice a difference between 4.1 and 4.0.x for battery life. it stayed the same or slightly gotten better.
i recommend using franco kernel though
Click to expand...
Click to collapse
I agree completely, battery life has been great. Just letting others know what might be the cause for "bad" battery life from past experiences

Overclock problem

I am running on carbon rom with moltley kernel. I set the max cpu clock at 1674mhz using antutu cpu mastaer. I use cpu spy the watch the cpu frequence, it do can go up to 1674. Then I run my phone with antutu benchmark. the result shows that my cpu frequency is 1512mhz only. and then, I check the cpu spy and cpu master again, the max cpu frequency has underclock to 1512mhz. But why it happens? I have set it to 1674 before, why It will automatically lower down after I run antutu? thx
csunny95 said:
I am running on carbon rom with moltley kernel. I set the max cpu clock at 1674mhz using antutu cpu mastaer. I use cpu spy the watch the cpu frequence, it do can go up to 1674. Then I run my phone with antutu benchmark. the result shows that my cpu frequency is 1512mhz only. and then, I check the cpu spy and cpu master again, the max cpu frequency has underclock to 1512mhz. But why it happens? I have set it to 1674 before, why It will automatically lower down after I run antutu? thx
Click to expand...
Click to collapse
set it to 1674 max cpu and 1674 minimum cpu, then run antutu and check cpu spy again.
simms22 said:
set it to 1674 max cpu and 1674 minimum cpu, then run antutu and check cpu spy again.
Click to expand...
Click to collapse
When I set it to 1674 max cpu and 1674 minimum cpu, the frequency cannot lock at 1674, and keep changing the frequency
Check this, even I didn't over clock and didn't touch anything, it down clock to 1296mhz instead of 1512mhz as default
is it the rom problem or kernel problem?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 4 using xda app-developers app
csunny95 said:
Check this, even I didn't over clock and didn't touch anything, it down clock to 1296mhz instead of 1512mhz as default
is it the rom problem or kernel problem?
View attachment 1771369
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
you probably neex to update your busybox. download the free busybox app by stericson from the play store, install it. open it, let it do its thing, press smart install. after, try antutu again, with your cpu speed.
simms22 said:
you probably neex to update your busybox. download the free busybox app by stericson from the play store, install it. open it, let it do its thing, press smart install. after, try antutu again, with your cpu speed.
Click to expand...
Click to collapse
I have done by cooling the device, I have it is due to throttles, but how can I ignore it?
csunny95 said:
I have done by cooling the device, I have it is due to throttles, but how can I ignore it?
Click to expand...
Click to collapse
ahhh.. yea, heat throttle will do that. you can turn off heat throttle(or use a kernel that raised the heat throttle temp, like trinity). to turn off heat throttle via terminal emulator..
su(press enter)
echo N > /sys/module/msm_thermal/parameters/enabled(press enter)
to turn it back on, replace the N with a Y.
But the thermal throttle has already set to N before I setting it.
Sent from my Nexus 4 using xda app-developers app
csunny95 said:
But the thermal throttle has already set to N before I setting it.View attachment 1772558
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
The value revert back, after a reboot, why?

Categories

Resources