Related
I'm on the latest CM7 build and would like to know the pros and cons of using each kernel. Hopefully someone can enlighten me.
I'm on Pershoot's right now, btw.
personally i like the pershoot kernels, they give u more frequencies to choose from... now this isnt really a big deal when u picking the overclock frequency (844Mhz vs 864Mhz vs 883Mhz isnt a big difference really), but given that the kernel can vary the frequencies in real-time means that the kernel has more options to chose from, also given a good algorithm that picks the frequencies it should result in better performance and less battery use (theoretically since the power required for 806MHz is less than 883Mhz).
Also pershoot kernels are UV, which should mean that the CPU is using less power to run at any given frequency (compared to running at that exact frequency with a non UV kernel).
Having said so, CM kernel gives u more options regarding the governors, under the original CM kernel i always picked the Conservative governor which gave me amazing battery life... this option is not available under the pershoot kernel and i believe pershoot recommends using the OnDemand option (not a 100% on this one though).
so in my opinion, and if am correct it's mostly a preference thing. I use the pershoot kernels.
let me know if am missing anything
awsrasool said:
personally i like the pershoot kernels, they give u more frequencies to choose from... now this isnt really a big deal when u picking the overclock frequency (844Mhz vs 864Mhz vs 883Mhz isnt a big difference really), but given that the kernel can vary the frequencies in real-time means that the kernel has more options to chose from, also given a good algorithm that picks the frequencies it should result in better performance and less battery use (theoretically since the power required for 806MHz is less than 883Mhz).
Also pershoot kernels are UV, which should mean that the CPU is using less power to run at any given frequency (compared to running at that exact frequency with a non UV kernel).
Having said so, CM kernel gives u more options regarding the governors, under the original CM kernel i always picked the Conservative governor which gave me amazing battery life... this option is not available under the pershoot kernel and i believe pershoot recommends using the OnDemand option (not a 100% on this one though).
so in my opinion, and if am correct it's mostly a preference thing. I use the pershoot kernels.
let me know if am missing anything
Click to expand...
Click to collapse
Thank you so much! Just the answer I was looking for! Very informative and straight-forward, thanks.
Looks like I'll be sticking to Pershoot's.
awsrasool said:
Having said so, CM kernel gives u more options regarding the governors, under the original CM kernel i always picked the Conservative governor which gave me amazing battery life... this option is not available under the pershoot kernel and i believe pershoot recommends using the OnDemand option (not a 100% on this one though).
Click to expand...
Click to collapse
You're correct. Pershoot uses the ondemand governor because he says it's more stable at the higher cpu clock cycles. Few issues with FC's, lockups, and reboots. Though I do love the interactive governor (still want the smartass gov) he is correct from what I've personally experienced. That may be due to small variances in the kernels though despite coming from the same source but who knows.
Pershoot also has a .zip for every kernel that's full of some /lib files to add extra functions to your device, most users probably won't find a use for them though.
KCRic said:
Pershoot also has a .zip for every kernel that's full of some /lib files to add extra functions to your device, most users probably won't find a use for them though.
Click to expand...
Click to collapse
Can you please explain these extra functions and how to apply them please?
Wouldn't mind having some new functions
Sent from my HTC Vision using XDA App
I've found I get better battery life with Pershoot's kernel compared to the stock CM kernel using the same clocks speeds and governor (245 Mhz-1017 Mhz, Ondemand). No statistics to throw up though.
Goal of this little project is to dispel myths and hearsay and trying to assess the elusive performance of custom kernels for our beloved SGS I9000.
So far this has proven quite challenging as there is no single good benchmark on Android (yet):
a lot of people have been misled by ridiculous Quadrant scores: ridiculous because, with some small tweaks which do not affect real performance in any way, shape or form, it is possible to boost the Quadrant score by factor 3x.
You're free to believe that your SGS I9000 which scores 3000+ on Quadrant is faster than a SGS II, but then please leave this thread and move on.
some kernels may seem smooth with some games, and get high scores on some synthetic benchmark, yet the UI appears "laggy" and stutters a lot in comparison to other kernels which score lower on the same benchmark
some popular benchmarks give results with unacceptably low reproducibility, i.e. if you run them multiple times without changing a thing on your system, you get scores varying by 50% of more, in a completely random fashion
most popular benchmarks do not measure or take into account multitasking and CPU contention with other applications, yet on a typical usage one has background tasks such as the media scanner or synchronization which kick in often and unpredictably
So this will be mostly a work in progress, i'm testing several benchmarks and several kernels in multiple combinations, trying to analyze which benchmarks offer certain criteria which make them useful, namely:
Reproducibility of results: running the same tests multiple times, should result in a very small variance of the final score
Performance separation: benchmarks which are too "synthetic" and show only a dependency on clock speed are not useful to discriminate "fast" kernels from "slow" kernels
Performance representation: we all know when a kernel "looks" or "feels" fast or smooth. If a benchmarks shows you that a "laggy" kernel scores higher than a fast and responsive one, it's likely that the benchmark is not well designed
I'll work more on this thread explaining my (current) choice of tests and what they're good for.
But for now i'll just post a link to the summary table, and give a brief recommendation concerning popular ICS kernels; recommendation which i'll explain in the coming days.
Base ROM:
Slim ICS 2.8
(because is fast, smooth and has the least background stuff of all ICS ROMs which i tested)
Test Conditions:
Whenever possible, i tried to overclock the kernels to 1.2GHz which most / all phones should have no trouble achieving.
In case of Semaphore i had to use the bus / live overclock but it wasn't fully stable at 1.2GHz on my phone so i ran most of the tests at 1.14GHz.
Tested Kernels:
Stock Teamhacksung V17
Devil 1.1.6b BFS
Devil 1.1.6b CFS
Icy Glitch V14 b
Semaphore ICS 0.9.5b
Recommendation:
Devil 1.1.6b CFS, Icy Glitch V14b (with SmartassV2 and FIOPS), and Midnight ICS (with a tweaked Conservative) are trading blows for the fastest kernel.
At the time of testing, Midnight is slightly worse in terms of overclocking though, apparently due to different voltages, also it doesn't allow overclocking beyond 1.2GHz.
But what's interesting is that it achieves great performance while using a tweaked conservative governor.
Devil 1.1.6b BFS is good but obviously inferior to its CFS brother.
Semaphore has the lowest cache and memory latency in the multithreaded test, it also has impressive sd card read speed and in general appears super responsive, but it's a bit worse in 3D gaming and especially it lacks "true" overclocking, "live overclocking" changes the bus clock and is way more unstable, in fact on my phone i couldn't run it stable at 1.2GHz.
All kernels are significantly faster than the stock teamhacksung's kernel, so you have no excuses not to upgrade to one of the popular custom kernels!
ICS 4.0.4
Started testing Android ICS 4.0.4 kernels on Slim ICS 3.2.
All tested kernels are "huge mem" versions with 380+MB of available RAM, without breaking video playback or 720p recording.
Summary:
the stock kernel from Teamhacksung is now a very respectable performer, unless you plan to overclock probably you don't need to install one of the other kernels
Semaphore, Midnight and Devil are all very fast and smooth
Results table:
https://docs.google.com/spreadsheet/ccc?key=0AuBUEB4dGFSSdHIyN2VIeWU4QnhLOFpJejFPWDh5S1E
Res 1
One request for the kernel developers:
could you please post me what are your preferred / recommended settings in terms of Governor and I/O Scheduler?
Only one configuration per kernel please, as running these tests is rather time consuming.
Test Settings
So for anybody who wants to follow the same methodology as I used to test kernels, please pay attention that in some tests i didn't use stock settings, to try to improve the reproducibility of the results.
Before all test, i put the phone in flight mode, and disable all synch services.
Antutu: DB I/O and SD Write and Read have poor reproducibility. So i run these tests separately 5 times, and take the best scores.
RealPi: the number of iterations is increased by factor 10x i.e.: 100000 digits
MPAC: lots of customization here. Also be careful as it's not very stable and some settings will make it crash.
All tests: 8 threads (or 8 producer / consumer pairs)
CPU: 10000000 iterations, use case: integer (i'm considering to add logical too)
Memory: stock apart for nr of threads. Repeat the test 5 times and get best numbers
Cache: 40 iterations
Res 3
With this should be enough.
Judging from those results, CFS Devil looks really promising.
Semaphore live oc stability issues happen only on Slim ICS indeed. On ICSSGS I have perfect stability at 1.2 ghz. And performance is just great, paired with very good battery life.
GT-i9000 / ICSSGS 4.2 / Semaphore 0.9.0
A quick question: did you lock the max freq to eliminate the "governor" variable?
Because each kernel could have governor's tweaks that the other don't.
Based on what you posted here, the differences between Glitch and Devil is practically none.
I tested both and didn't feel any tangible difference, in the end, it comes down to the unique features of each kernel.
Overclocking bus vs adding an extra step aren't even slightly comparable. Maybe do tests not overclocked?
Also there is a new glitch build with 100% working bln.
Sent from my GT-I9000 using xda premium
+1 for tests without overclock. Majority of us, users do not overclock. Maybe a seperate test for overclocking could be nice , but comparisons should be done with stock speeds imho.
Thanks for the time and effort. We needed this.
Overclocking bus Vs adding an extra step isn't an apple to apple comparison, I agree.
However my goal was to use each kernel in the best possible way, and if some kernels have the possibility to use higher multipliers / extra frequency steps, that is an advantage for the user, compared to the kernels who only offer live overclock.
Don't get me wrong, i love Semaphore and i've been using it for a long time.
And i have no doubt that some users can get it stable with live overclock to 1.2GHz.
But that is the ceiling, while with other kernels even my phone can reach stable overclocks of 1.5GHz, and that is something to consider.
I chose as the basis for my tests an overclock of 1.2GHz because it's something which practically everybody can use, without massive battery drain, overheat or shortening the life of the device.
I'll try to add measurements at stock speeds for those who don't like to overclock.
cba1986 said:
A quick question: did you lock the max freq to eliminate the "governor" variable?
Because each kernel could have governor's tweaks that the other don't.
Click to expand...
Click to collapse
I didn't want to take the governor variable out.
Because, as you said, each kernel could use (and often does) governor tweaks which make the kernel "special" or different from the others, and that has to be taken into account in evaluating them.
Because nobody will use the phone locked at the maximum frequency.
So for me the governor and its tweaks is part of the user experience of a certain kernel, and a distinctive factor.
At the end, all kernels are coming from almost the same sources, so it's the little things which make the difference.
phzi said:
Also there is a new glitch build with 100% working bln.
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
That's great!
This test i run is not the "be all end all", it was just a recommendation at the time of writing.
Pipperox said:
Overclocking bus Vs adding an extra step isn't an apple to apple comparison, I agree.
However my goal was to use each kernel in the best possible way, and if some kernels have the possibility to use higher multipliers / extra frequency steps, that is an advantage for the user, compared to the kernels who only offer live overclock.
Click to expand...
Click to collapse
Agreed but, then again, benchmarks should be done at original CPU clock IMHO.
Otherwise, results are distorted.
HiKsFiles said:
Agreed but, then again, benchmarks should be done at original CPU clock IMHO.
Otherwise, results are distorted.
Click to expand...
Click to collapse
agreed. Especially since stock team hacksung seems to be clocked at 1GHz
what's the point of the comparison? Really?
As expected, there is no noticeable difference between all 1.2 GHz kernels.
It's not as if there was a real difference between them anyway.
zorxd said:
agreed. Especially since stock team hacksung seems to be clocked at 1GHz
what's the point of the comparison? Really?
As expected, there is no noticeable difference between all 1.2 GHz kernels.
It's not as if there was a real difference between them anyway.
Click to expand...
Click to collapse
That's not quite true.
If you look closer, you'll see that Devil CFS has quite a distinct advantage over all others in 3D tests.
The point of the comparison between stock hacksung @1.0GHz and the others, who can overclock, is to show what kind of benefit you get from switching to kernels which are overclock friendly.
Especially considering that you can't assume that a 20% clock speed increase will bring a 20% performance speedup across the board.
At last, i'd say that you may have "expected" that the kernels tested at 1.2 GHz don't have such a difference in performance.
But expectations have to be verified.
I tried to answer the questions:
On Devil's kernel, is BFS really better than CFS?
The "popular belief" is that BFS is faster than CFS.
According to my tests, CFS results faster instead.
Another question may be, what kernel gives you the best gaming performance.
If you pay attention to the An3D Bench XL, you'll see that Semaphore 0.9.5b, even overclocked a 1.2GHz, is significantly slower than Devil.
If i recall correctly Semaphore Author claimed that some kernel developers overclock GPU, and he didn't. Idk anything about it, but i recall something about it.
Is it possible to overclock only GPU, without overclocking CPU??
zipgenius said:
so you should benchmark them without setting anything. Average users don't overclock and don't change governor or scheduler: they flash the new kernel and stop.
Click to expand...
Click to collapse
I completely agree on benchmarking every kernel at the same frequency (stock 1Ghz max) but I think there are two different options for further benchmarking:
1) Benchmark kernels configured as similar as possible regarding CPU governor, IO scheduler, readahead -> comparable results for all kernels.
2) Benchmark kernels with default settings (only makes sense if all compared kernels are optimized for similar purpose like performance, does not make sense if a kernel does *not* focus on max. performance and uses e.g. Conservative CPU governor as default setting.
@Pipperox: Would it be possible to check my Mindnight-ICS dev version with your benchmark suite? I'd be really interested in the results as you use the same setup for all kernels (1.2Ghz would not be a problem, does not use LiveOC but old school 1/1.128/1.2Ghz OC).
Interesting thread... I never used devil's CFS version, always BFS. Will try CFS out now.
@Mialwe Where can we get your ics kernel?
mialwe said:
I completely agree on benchmarking every kernel at the same frequency (stock 1Ghz max) but I think there are two different options for further benchmarking:
1) Benchmark kernels configured as similar as possible regarding CPU governor, IO scheduler, readahead -> comparable results for all kernels.
2) Benchmark kernels with default settings (only makes sense if all compared kernels are optimized for similar purpose like performance, does not make sense if a kernel does *not* focus on max. performance and uses e.g. Conservative CPU governor as default setting.
@Pipperox: Would it be possible to check my Mindnight-ICS dev version with your benchmark suite? I'd be really interested in the results as you use the same setup for all kernels (1.2Ghz would not be a problem, does not use LiveOC but old school 1/1.128/1.2Ghz OC).
Click to expand...
Click to collapse
Sorry guys, i understand your logic but i do not fully agree with it.
I'm not comparing overclocked kernels with heavy tweaking of voltages and special settings with which they only work.
I did the "poor man"'s overclock, setting to 1.2GHz using NSTools, a setting where 95% of phones should have no problem working.
I think that if some kernels offer you this possibility while others do not, it is fair to use this "advantage" that they have over the other kernels.
Because a lot of users will have the possibility to do the same as i do, without esoteric knowledge and with just a couple of clicks in the menus.
That being said, "due to popular demand" i will also try to retest those kernels at 1.0GHz as soon as i get a bit of time.
BUT in my recommendations, i will also consider the overclocking capabilities.
@mialwe: sure, i'll give a run to your kernel as well!
mialwe said:
@Pipperox: Would it be possible to check my Mindnight-ICS dev version with your benchmark suite? I'd be really interested in the results as you use the same setup for all kernels (1.2Ghz would not be a problem, does not use LiveOC but old school 1/1.128/1.2Ghz OC).
Click to expand...
Click to collapse
Dude, sorry but i don't seem to find your ICS kernel anywhere.. can you provide a link?
I am running CM10 M2 on my Samsung Galaxy S3 I747
Now my question is which kernel do i use because i would like to OC my phone but it has to have some speed and keeps some battery life.
I don't want to have a lot of speed with hardly to no battery life, i need a little speed plus good battery life if possible.
So if anyone has any suggestions please post
Leandre20 said:
I am running CM10 M2 on my Samsung Galaxy S3 I747
Now my question is which kernel do i use because i would like to OC my phone but it has to have some speed and keeps some battery life.
I don't want to have a lot of speed with hardly to no battery life, i need a little speed plus good battery life if possible.
So if anyone has any suggestions please post
Click to expand...
Click to collapse
You can try all that work with CM10. It's a preference thing. I'm using ktoonsez. You can OC and UC.
Sent from my SAMSUNG-SGH-I747 using xda premium
Im not saying there aren't any others as i have only used ktoonez's kernel, http://forum.xda-developers.com/showthread.php?t=1756776 simply because there is, IMHO, no need to. He has versions for each of the available android versions for the i747...obviously you would want to use the AOSP JB based kernel under CM10. Packaged along with the kernel is ktweaker which is an app that gives you control over the clock speeds, under volting, governors, schedulers, plus a bunch of other options. If you overclock your processor you are going to drain the battery faster, you can compensate for this by under volting the frequencies however pushing the CPU too hard can shorten the life expectancy and under volting too far will cause severe system instability. Im not sure how much experience you have with OC/UV'ing but its basically trial and error until to find the right balance of speed and stability that is right for you.Just be sure to read and follow his instructions carefully and dont mess with anything in ktweaker you aren't 100% sure what it does, and as always make a backup in your recovery before messing with system files.....happy OC'ing.
dntesinfrno said:
Im not saying there aren't any others as i have only used ktoonez's kernel, http://forum.xda-developers.com/showthread.php?t=1756776 simply because there is, IMHO, no need to. He has versions for each of the available android versions for the i747...obviously you would want to use the AOSP JB based kernel under CM10. Packaged along with the kernel is ktweaker which is an app that gives you control over the clock speeds, under volting, governors, schedulers, plus a bunch of other options. If you overclock your processor you are going to drain the battery faster, you can compensate for this by under volting the frequencies however pushing the CPU too hard can shorten the life expectancy and under volting too far will cause severe system instability. Im not sure how much experience you have with OC/UV'ing but its basically trial and error until to find the right balance of speed and stability that is right for you.Just be sure to read and follow his instructions carefully and dont mess with anything in ktweaker you aren't 100% sure what it does, and as always make a backup in your recovery before messing with system files.....happy OC'ing.
Click to expand...
Click to collapse
I'm still learning since it's the first one I tried.
Sent from my SAMSUNG-SGH-I747 using xda premium
There is a thread dedicated to ktweaker settings on the i747 HERE that would be a good place to start and get an idea of what you are doing. There are also several topics that discuss the different governors and schedulers, what the differences are, advantages/disadvantages to each etc. You can also search google for a plethora of information regarding OC/UV'ing, although most of it will pertain to desktop processors and video cards. While the voltages and frequencies will be significantly lower the same principles apply with mobile device chips.
Hi guys,
I've got a Galaxy S3 via Rogers, rooted, running the rom Triune II, I haven't messed around with custom Kernals (tbh haven't figured that out really), I recently installed SetCPU to overclock my S3 for running graphic intensive/slow loading games like Asphalt 7, etc.
So far for that purpose it's been amazing, the games literally open twice as fast. I've setup SetCPU for a variety of CPU changes, ie. higher speeds for graphic intensive games, lower speed for screen off while charging (ie. overnight) and it seems to be working great.
My questions are:
Can "overclocking" damange my device? Ie. I know that obviously overclocking shreds through battery life, but is playing a game at the top speed available on SetCPU (1512 Mhz) bad over a prolonged period?
Also, am I not reaping the full benefits of over/underclocking having a custom kernal installed?
Also...nother totally n00b one, if the S3 is capable of reaching the "overclocked" max speed, why doesn't it in the stock ROM? I just don't quite get that....is it because the battery life would be terrible and people would blame Samsung for it?
Never had a issue overclocking. And I've overclocked every phone I've owned beside the iPhone.
As far as how much better it will make your phone it depends. Depends on the rom too. I've noticed better benchmark results yet not always better real world results.
I use it more for the ability to underclock, and overclock when necessary.
Sent from my SGH-I747 using xda app-developers app
a little off but do you know of a way to measure the temperature of the phone (when you overclock/or even normally) ?
My phone does heat up sometimes
For over/underclocking there must be support for it built in kernel ! So if stock kernel doesn't support it you cannot probably change frequencies without changing kernel on stock Rom !
Also read the kernel's documentation - stable frequencies will be listed there - jumping back and forth these frequencies won't cause any troubles apart from the obvious battery drainage depending on your settings
Sianspheric said:
Hi guys,
I've got a Galaxy S3 via Rogers, rooted, running the rom Triune II, I haven't messed around with custom Kernals (tbh haven't figured that out really), I recently installed SetCPU to overclock my S3 for running graphic intensive/slow loading games like Asphalt 7, etc.
So far for that purpose it's been amazing, the games literally open twice as fast. I've setup SetCPU for a variety of CPU changes, ie. higher speeds for graphic intensive games, lower speed for screen off while charging (ie. overnight) and it seems to be working great.
My questions are:
Can "overclocking" damange my device? Ie. I know that obviously overclocking shreds through battery life, but is playing a game at the top speed available on SetCPU (1512 Mhz) bad over a prolonged period?
Also, am I not reaping the full benefits of over/underclocking having a custom kernal installed?
Also...nother totally n00b one, if the S3 is capable of reaching the "overclocked" max speed, why doesn't it in the stock ROM? I just don't quite get that....is it because the battery life would be terrible and people would blame Samsung for it?
Click to expand...
Click to collapse
Yes overclocking can damage your cpu from overheating, some even believe it may reduce the lifespan of you cpu.
If you are running 1512 max you are running stock mhz, that isn't overclocked. You cannot run a stock Sammy kernel and overclock it unless it's been recompile..to be overclocked.
I recommend ktoonsez kernel it can be overclocked to 2106mhz and underclocked to 96mhz. As well as undervolting support which is pretty much essential for overclocking because an undervolt will make your phone produce less heat by lowering the voltage your phone requires when running.
To answer your second question, yes you are not reaping any benefits without a custom kernel, this is evident.
To answer the last. The stock kernel is maxed at 1512 because that is the best mhz for the STOCK Sammy kernel performance and battery wise. Also its possible that overheating happened when they set the max at higher mhz during their tests.
Some good general knowledge if you decide to overclock, would be learning how to and what undervolting does for your phone. You can read up on that here:
http://forum.xda-developers.com/showthread.php?p=33282284
Ktoonsez kernel thread: http://forum.xda-developers.com/showthread.php?p=28399829
Make sure you download the right one for your rom!
If after reading about undervolting and installing kernel and would like some safe undervolting and gov/scheduler settings let me know! You can also find many other settings here:
http://forum.xda-developers.com/showthread.php?p=31539830
AT&T SGS3 Marble White
Team AoCP The Collective ROM
KT747 10/31 OC'ed & UV'ed
Medical MJ Supporter
Sorry that kernal thread is a bit confusing.
Does that Kernal only exist for the stock carrier ROM and CM?
I'm using Triune II, if the kernal doesn't exist for that ROM then I take it I have to change ROM's?
Sianspheric said:
Sorry that kernal thread is a bit confusing.
Does that Kernal only exist for the stock carrier ROM and CM?
I'm using Triune II, if the kernal doesn't exist for that ROM then I take it I have to change ROM's?
Click to expand...
Click to collapse
No. Triune is a TW based ROM. Therefore, you need to download KToonsez TW kernel. Keep in mind there is a ICS TW kernel, and then there is a JB TW kernel.
There are other kernels out there. Faux123 has a good one. It is capable of OC to 1.8Ghz, I believe.
Sianspheric said:
Sorry that kernal thread is a bit confusing.
Does that Kernal only exist for the stock carrier ROM and CM?
I'm using Triune II, if the kernal doesn't exist for that ROM then I take it I have to change ROM's?
Click to expand...
Click to collapse
Download the one titled touchwiz and whatever version you are running be it ice cream sandwich touchwiz, or jellybean touchwiz.
AT&T SGS3 Marble White
Task & Ktoonsez AoKP ROM
Ktoonsez 11/13 Kernel OC'ed
Medical MJ Supporter
I have rooted my phone and I wanna overclock my gpu, but I don't know what app to use. I also wanna oc my CPU, if you know how, please tell me
As a phone doesn't have active cooling, this is generally unwise, as you'll rarely get significant performance gain while dealing with increased heat, which can be damaging. Custom kernels generally allow fine grained CPU and sometimes GPU control, but it's typically the opposite of overclocking - developers try to use the lowest voltages possible on the smallest cores while still maintaining decent performance, to reduce power consumption and extend battery life.
V0latyle said:
As a phone doesn't have active cooling, this is generally unwise, as you'll rarely get significant performance gain while dealing with increased heat, which can be damaging. Custom kernels generally allow fine grained CPU and sometimes GPU control, but it's typically the opposite of overclocking - developers try to use the lowest voltages possible on the smallest cores while still maintaining decent performance, to reduce power consumption and extend battery life.
Click to expand...
Click to collapse
Yes, but I just want to maximize performance, I have two phones, and I want to overclock this one, so it's faster. I will take care of cooling. I don't care much about battery life, since it's not my daily driver. So what app should I use ?
bubleman_2 said:
Yes, but I just want to maximize performance, I have two phones, and I want to overclock this one, so it's faster. I will take care of cooling. I don't care much about battery life, since it's not my daily driver. So what app should I use ?
Click to expand...
Click to collapse
You can't just use an app. You have to use a custom kernel, and the app used to control kernel parameters depends on the kernel.
"Stock" kernels are not modifiable via app.
V0latyle said:
You can't just use an app. You have to use a custom kernel, and the app used to control kernel parameters depends on the kernel.
"Stock" kernels are not modifiable via app.
Click to expand...
Click to collapse
Do you know a kernel that is overclocked? I tried Ryzen kernel and I still can't overclock it.
bubleman_2 said:
Do you know a kernel that is overclocked? I tried Ryzen kernel and I still can't overclock it.
Click to expand...
Click to collapse
I am not familiar with Redmi devices, so no. I would suggest looking through the various custom kernels here, and if the description of the kernel doesn't answer your question, ask in the threads. However, pursuant to Forum Rule #5, please don't post your questions more than once.
So what kernel and app should I use to oc it?
.