Related
I rooted my MY4G and installed IG last week...nothing else..i have added some little stuff like setCPU, terminal emulator, etc.
I keep reading about dif Kernels and i have no idea if i need to install one or what they do over the ice glacier i all ready installed.
explain all this too me please.
thanks
Different kernels just have different features. The stock kernel that comes with Iced Glacier is already a custom kernel (Gr8Gorilla's 1.8 GHz v.05). If I remember right, this kernel didn't have UV (Under Volting). There are many different features offered with each kernel choice. Such as:
OC (Over Clocking support): This just allows you to go higher than the factory settings.
UV (Under Volting): This means the kernel's voltage tables have been lowered to attempt to save battery life.
MinMax: This feature keeps the CPU running at the set minimum and maximum settings.
Smartass: Scales the CPU "intelligently." It acts in lieu of SetCPU profiles by scaling the processor down for screen off.
There are also different scaling types enabled in different kernels. Just give them a flash to see if you like them! Make sure you remember to do a nandroid first. Happy flashing!
- What is UNDERVOLT
- Benefits of UNDERVOLT
- Standard Voltages
- Software needed
- Procedures and how to test
- Side Effects
- Results
What is UNDERVOLT (UV)
It's very simple meaning, the translation itself says it "under voltage".
UNDERVOLT is you decrease the voltage pattern of the manufacturer. But you may be wondering. Voltage of what? What we can decrease via software are: processor voltage which is divided into (core voltage and internal voltage) and decrease the voltage of the video card. There are other voltages via the kernel but only among some of them, ram voltage and voltage of the screen. But here we deal only with CPU and GPU.
Undervolting on ICS
The procedure is exactly the same. Programs for testing and process are the same too. With just a detail specifically.
- After many fought discovered that the voltage supported for Ginger can be used in IceCream with just a detail. STEP Clock 500mhz. I do not know why but it's no use simply use less frequently than 925mV that will hang. Then start by this voltage.
- Another important detail is that we do not have undervolt on "internal voltage" only on "core voltage"
Benefits UNDERVOLT
Simple, fast and direct; conserve battery power. Give more time to use on our mobile without having to reload.
Voltage pattern
This voltage is determined by the standard kernel. I'll put here the voltages of the stock kernel, custom kernel but each uses a different voltage from one another but that does not interfere with anything in our procedure.
I'll try to explain a little more how it works. This voltage to which I refer is measured in mV (millivolts). And each step (frequency) of the processor or video card possesses a voltage. Up link because it would not use a high voltage is used with the processor 1.200mhz be used with the processor at 200 MHz for example.
Standard voltages of the processor:
1.200mhz - 1.250mV 1.100mV internal core voltage and voltage
1.000mhz - 1.150mV 1.100mV internal core voltage and voltage
800mhz - 1.050mV 1.100mV internal core voltage and voltage
500mhz - 950mV 1.000mV internal core voltage and voltage
200MHz - 900mV 1.000mV internal core voltage and voltage
Standard voltage of the video card:
267mhz - 1.000mV
160MHz - 950mV
Programs needed:
Undervolting:
There are three most commonly used today
- Tegrak Overclock Ultimate * paid
- Voltage Control * free and paid
- SetCPU paid *
Each of these has its special qualities cited I quote the principal.
Tegrak: one who can do UNDERVOLT kernel in stock and only one who can do UNDERVOLT the internal voltage.
Voltage Control: the interface is more user friendly and compatible with most custom kernel.
SetCPU: was or still is the most popular but today there are better and does not work right UNDERVOLT on the video card.
For the tests:
- 2nd Core (enables the use of the second core constant)
- Super PI
- Linpack
- A video about 5min
- Antutu, quadrant, nenamark2
- NEAK CPU Stress Test *new
I will leave here already written about how to use them when I quote them in part of the procedure does not have to explain.
Super PI: he runs the option 512kb, which is longer but it uses calculations is a good way.
Linpack: perhaps the most sensitive UNDERVOLT I know. Click several times in multi-thread around a 20 to 30 times.
Quadrant, Antutu and Nenamark2: they are not very sensitive to UNDERVOLT, sometimes you run three times and it does not crash but hangs running the Linpack test but they UNDERVOLT video card.
Video: never tested particularly well, but has a staff recommends that the xda that way.
Neak Stress Test: just click in Start StressTest and wait 2 minutes.
Procedures and Form of testing
1st step: with 2nd Core App enabled two core always
2nd step: choose what you want to test. If the processor or video card. No matter what the procedure is the same.
Step 3: in what you choose (processor or video card) you have to go by parts and if choosing a lot of different voltages because otherwise if you do not know where to catch the problem was. I will explain in detail how to and have done the process.
If you chose to start with the processor. In this case opting for the core voltage.
For a UNDERVOLT efficient and successful you must EVER use maximum frequency and minimum frequency = you use this form for all frequencies tested.
Simply put, your seven 200MHz processor (both maximum and the minimum) and a voltage just choose the frequency that we use in the case is 200MHz. I recommend starting by choosing from more aggressive to the nearest standard. I say this because it is good to know what is the most aggressive right from the begining that after staying in doubt whether or not hold out that much voltage. Start trying to put 850mV for 200MHz. Below 850mV only Tegrak Ultimate and Extreme Voltage Control. Once you set and has fought better because not waste time testing. +25 Choosing start again only the last selected voltage. Always after crahsed i recommend increase +25 for morenprecision.If it worked to get the battery of tests as explained in the "required programs" and beyond the specific tests you'd better get moving on the phone as if you were using on a daily basis to see only crashes.
After you have found a value (mV) to 200MHz you can already go to the frequency of 500mhz and 500mhz repeated by setting maximum and minimum. This procedure will be used for all testing so from now on I'll just give tips on values to be used it may be that people who have never seen it before not knowing where or by voltage (mV) choose. Quote values that are already below the maximum that can support values below that have never seen anyone get so I'm saving time for you.
500mhz - try starting with 850mV
Perform all tests and follow.
800mhz - try starting with 900mV
Perform all tests and follow.
1.000mhz - try starting with 1000mV
Perform all tests and follow.
1.200mhz - try starting with 1.100mV
*this voltage what i recommend was extremely low, lower values is crazy. If you dont want start with extreme undervolt i recommend start all with values above with more 50mV
After you have performed all the tests and have found the best voltage to each of you can already start to test the video card.
As the process of the video card is the same used in the processor and you must be tired of testing will resume.
Set maximum frequency = minimum frequency
267mhz - start with 900mV
160MHz - start with 800mV
Step 4: After you have set all your voltages at their respective frequencies of both the processor and video card. You can set back their frequency and maximum frequency of at least according to his need. Default values:
Processor: 200MHz - 1.200mhz
Video: 160MHz - 267mhz
5th step: Perform all possible tests with it all set up for you. And see if it's stable. If locks, will be difficult to identify where the problem was so important to give a great attention when they are testing each setting its own.
Side Effects
There are two very distinct. One is the freeze and the other is SOD (Sleep of Death) which is when the cell no longer responds after he entered into deep sleep, having to restart the phone.
Cause it may be some factors. Some devices simply do not like UNDERVOLT, another reason is the more likely you used a voltage more than it should. And another cause is that your kernel + rom + app UNDERVOLT not done well. Sometimes replacing any items solves the problem.
Eric's Undervolting Settings for ICS
Who don't want find your own undervolt.
200mhz (875mV)
500mhz (950mV)
800mhz (1025mV)
1000mhz (1100mV)
1200mhz (1200mV)
Result
One goal of this topic is exactly the result. Any testing, evaluation that shows the benefit of UNDERVOLT is welcome.
And you find your own configuration that is much more efficient than picking up some numbers of the other settings thereby obtaining a better result. This is not a "MAGIC" this is REAL.
Show your.
*** Important to read before you do.
I am not responsible for any damage that may occur on your mobile. My UNDERVOLT was done exactly as written above. I've never seen the reports and facts that this process has damaged some mobile.
If this tutorial helped you give something a simple thank you.
i will update here to undervolt our galaxy s3
Great work Eric A very useful reference.
MistahBungle said:
Great work Eric A very useful reference.
Click to expand...
Click to collapse
Thanks my friend. I stay glad read your post.
My only problem is i dont know perfect english so is difficult to me express really want to say.
Sent from my GT-I9100 using Tapatalk
Great info mate.
Don't loose sleep over the whole "magic" thing.
Sent from my GT-I9100 using XDA App
Your english is fine mate This guide will be a fantastic reference for people new to undervolting their phones.
eric-filth said:
Thanks my friend. I stay glad read your post.
My only problem is i dont know perfect english so is difficult to me express really want to say.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Great work Eric A very useful reference.
MistahBungle said:
Your english is fine mate This guide will be a fantastic reference for people new to undervolting their phones.
Click to expand...
Click to collapse
Thanks. But i need try better my english
So this is my only reason to create this thread, try to help people make your own undervolt with best values.
Sent from my GT-I9100 using Tapatalk
Jimmykwliu said:
Great work Eric A very useful reference.
Click to expand...
Click to collapse
Thanks for your post.
I will try to sleep now. This thread cost about 5 hours to be wrote
Sent from my GT-I9100 using Tapatalk
eric-filth said:
Thanks for your post.
I will try to sleep now. This thread cost about 5 hours to be wrote
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
mate..well done for the thread. one your english is fine i agree with MistahBungle and second this makes it even more clearer to a lot of users out there who are just starting regarding the pros and the cons of undervolting. well done
Thanks man, getting today my S2, this will come in handy!
nice guide buddy ;-)
hello mate again sorry to bother you. just to let you know i put a link of your thread on my first post on my thread so people know a bit more regarding undervolting and can read regarding the pros and cons of undervolting and get a bit more of a knowledge...Thanks again and hope you do not mind me doing that. Great work and great stuff again
X-Plosiv said:
Thanks man, getting today my S2, this will come in handy!
Click to expand...
Click to collapse
Hehe thanks. Thats right, unfortunately it took me to do this.
virus786 said:
nice guide buddy ;-)
Click to expand...
Click to collapse
Thanks my friend.
Stifler69 said:
hello mate again sorry to bother you. just to let you know i put a link of your thread on my first post on my thread so people know a bit more regarding undervolting and can read regarding the pros and cons of undervolting and get a bit more of a knowledge...Thanks again and hope you do not mind me doing that. Great work and great stuff again
Click to expand...
Click to collapse
You not boring me hehe you are doing one great favor for us. Thanks again my friend.
Sent from my GT-I9100 using Tapatalk
Guys im waiting simone release your app do stress cpu and we can use it to test the stability of undervolt with this app. When he release i update the topic.
Enviado do meu Galaxy S2 usando Tapatalk
nice
thts a nice post eric an the eng is good....well ive tried some wierd settings an yes its true the phon jus dies off,some sett are good an stable...so this thread is good for newers who need good info.....cheeerz
rocky23 said:
thts a nice post eric an the eng is good....well ive tried some wierd settings an yes its true the phon jus dies off,some sett are good an stable...so this thread is good for newers who need good info.....cheeerz
Click to expand...
Click to collapse
Thanks buddy. This guide is not perfect because has some words can not express properly. But still helping people
Enviado do meu Galaxy S2 usando Tapatalk
Guys, Simone developer of Neak Kernel released app to stress test our cpu. And i add in our test. Check out.
https://play.google.com/store/apps/details?id=com.neak.tester
Enviado do meu Galaxy S2 usando Tapatalk
i think 2nd core only works on certain kernels. doesn't work for me
ogk-slay said:
i think 2nd core only works on certain kernels. doesn't work for me
Click to expand...
Click to collapse
What your kernel?
But you can make test without 2nd core. Probally the app tester like super pi, linpack, antutu, etc will use second core. I recommend use program only for safety.
Enviado do meu Galaxy S2 usando Tapatalk
Do we have a kernel settings thread? (a la color profiles)
I'm curious to see what settings others have tried out, why and what were the results
Of course. Did you search?
http://forum.xda-developers.com/showthread.php?t=2039607
Nexus 4 Color Settings [spreadsheet]
Sent from my iPad 4
mitchdickson said:
Of course. Did you search?
http://forum.xda-developers.com/showthread.php?t=2039607
Nexus 4 Color Settings [spreadsheet]
Sent from my iPad 4
Click to expand...
Click to collapse
This guy owns an iPad and even he can search. What is wrong with people?
mitchdickson said:
Of course. Did you search?
http://forum.xda-developers.com/showthread.php?t=2039607
Nexus 4 Color Settings [spreadsheet]
Sent from my iPad 4
Click to expand...
Click to collapse
Yes, I did search. You misread my post. I'm not a complete idiot.
I'm not looking for color profiles. I'm looking for a kernel settings thread LIKE the color profiles thread. (hence why I used "a la" in my phrase - prep. In the style or manner of)
For example:
CPU Bin: Faster
Kernel Used: Linaro franco r161
TCP Congestion: Westwood
Scheduler: Row
Min: 384
Max: 1512
Governor: Conservative (up_threshold: 98)
MPDecision: Off
Temp Limit: 70
Voltages: -100
Etc...
derekr44 said:
Do we have a kernel settings thread? (a la color profiles)
I'm curious to see what settings others have tried out, why and what were the results
Click to expand...
Click to collapse
all our phones react differently to different kernels and kernel settings. its recommended that you try out different kernel and kernel settings on your own, find what you and your personal device likes the best. what works absolutely perfectly for me, might work absolutely horrible for you. also, about voltages and lowering them, our devices handle voltages different too, some can undervolt a lot, while others can undervolt at all.
simms22 said:
all our phones react differently to different kernels and kernel settings. its recommended that you try out different kernel and kernel settings on your own, find what you and your personal device likes the best. what works absolutely perfectly for me, might work absolutely horrible for you. also, about voltages and lowering them, our devices handle voltages different too, some can undervolt a lot, while others can undervolt at all.
Click to expand...
Click to collapse
Yup. Settings are different for everyone/every device, just like the color profiles. What some may like as darker blacks might look crappy in my own eyes. And yes, different devices react differently to the same settings.
While I can toy around with kernel settings all day long, I'm just curious to see what others have tried. This gives the option for others to cherry pick an idea that they may not have thought of before. For example, I saw in one of your posts about ramping up up_threshold to 98 while I had mine at 85. I wouldn't have thought of that on my own.
derekr44 said:
Yup. Settings are different for everyone/every device, just like the color profiles. What some may like as darker blacks might look crappy in my own eyes. And yes, different devices react differently to the same settings.
While I can toy around with kernel settings all day long, I'm just curious to see what others have tried. This gives the option for others to cherry pick an idea that they may not have thought of before. For example, I saw in one of your posts about ramping up up_threshold to 98 while I had mine at 85. I wouldn't have thought of that on my own.
Click to expand...
Click to collapse
thats why i recommend experimenting. many times you run into a combo of settings that you never expected nor anyone thought to try, and works great. or ask in the kernel thread that you are using, i know that in the trinity kernel thread you would get lots of replies for sure
generally, with those kind of threads that youre asking about, xda looks down upon them. after one gets started, people will start arguing/flaming about which kernel is best. of course, everyone will claim that the kernel they are using is best. then it goes downhill.
and my post about that ondemand setting only works best if the up threshold is 98 AND the sampling rate is 15000
simms22 said:
thats why i recommend experimenting. many times you run into a combo of settings that you never expected nor anyone thought to try, and works great. or ask in the kernel thread that you are using, i know that in the trinity kernel thread you would get lots of replies for sure
generally, with those kind of threads that youre asking about, xda looks down upon them. after one gets started, people will start arguing/flaming about which kernel is best. of course, everyone will claim that the kernel they are using is best. then it goes downhill.
and my post about that ondemand setting only works best if the up threshold is 98 AND the sampling rate is 15000
Click to expand...
Click to collapse
Thank you for the constructive reply.
Sent from my Nexus 4 using Tapatalk 4 Beta
derekr44 said:
Yup. Settings are different for everyone/every device, just like the color profiles. What some may like as darker blacks might look crappy in my own eyes. And yes, different devices react differently to the same settings.
While I can toy around with kernel settings all day long, I'm just curious to see what others have tried. This gives the option for others to cherry pick an idea that they may not have thought of before. For example, I saw in one of your posts about ramping up up_threshold to 98 while I had mine at 85. I wouldn't have thought of that on my own.
Click to expand...
Click to collapse
I'm not sure if there is a kernel settings thread (haven't found one), but faux has posted some recommended settings for his kernel, and osm0sis has a link to his Franco settings. Look in the links below:
http://forum.xda-developers.com/showpost.php?p=34502823&postcount=2
http://forum.xda-developers.com/showthread.php?p=34951507#post34951507
I've also been toying around, but I've kept it to a minimum since I really don't know what I'm doing when tweaking the more advanced kernel parameters
Hey guys,
I wanted to get everyone's feedback and experiences between the 3 kernels. I realize that every device behaves differently, but was curious about which ones people have tried, if they found any cool things about specific ones they really liked Or if you wanted to share your experience about the latest build.
Thanks!
Trinity and franco are about the same, but trinity>franco.
KTmanta is in a totally different league, it offers total customization and imo is the best kernel just because of that.
Franco and Trinity are all about performance where ktmanta is about battery optimizations and customizations.
I haven't used Franco or trinity in a while, I know they score higher in benchmarks if that means anything at all.
Sent from my SCH-I535 using xda app-developers app
I think everyone knows my preference, but they are all good kernels. Unfortunately this tablet is not on Franco's priority list and does not see much development. I dont believe it has a 4.3 compatible version yet and the last release has a serious bug that causes SoD for most people.
I like Trinity and KManta for different reasons (those stated above). If I need to squeeze out battery life, I go with KManta and tweak the settings accordingly. But for my day-to-day use, I like Trinity for its smoothness. Just my two cents
Awesome input guys! Real useful information.
How would you guys describe KTManta when just using the stock values? When you guys say "customization", do you guys mean the voltage settings and stuff like that? I've been flashing for years, but have never really understood how that worked. Which is funny, because I am an experienced PC overclocker. People say the concept is very similar. If KTManta's customization options were removed, would it be then comparable to Trinity? Or would it still be better without all the options?
Would you guys say Trinity still has decent battery life? Compared to KTManta at stock values?
Which one does Chrome work the best with?
Thanks!
Stock for stock Trinity is better because Morfic hardcodes overclock and undervolt values into the kernel and sets up all that stuff as his stock settings for the kernel. KTManta allows you to do those things and WAY more, but does not set them up as stock values because Ktoonsez prefers to keep the default settings for his kernel closer to the default settings of the stock AOSP kernel. So while Trinity may have -50mv undervolt to everything and a GPU overclock of 620MHz (I think that is the speed?), KTManta allows you to go +/- 200 mv to any frequency step for CPU or GPU that you feel like and also allows OC to 2.1GHz on CPU and 720MHz on the GPU if you want to, as well as RAM OC if you want to, and control of the scaling of every part of the chipset, again if you *want* to. But it doesnt set any custom stuff as default since everyone's device is unique and people want to do different things with it. That is why we have pre-made settings available from various users so that you can load custom values to try out without having to go through a bunch of experimentation yourself.
I don't know if the answer to my question is somewhere hidden between the thousands of threats but I did try to find it before(including Google and YouTube) and would be more than happy to get a reply.
I'm using custom Kernels since the Note 2 but was never able to put more time and afford in to understand how they actually work and always used the default settings.
Now I'm trying to get some knowledge on Kernel settings and what is safe to change and what not. I'm very interested on how a Kernel works and how I can boost both battery life and/or performance as well as the basic knowledge of the Kernel settings.
At the moment I'm trying to explore with trickster mod to kinda learn by doing but I always get really bad results in testing or no big changes when I change the governor. Also I'm a little afraid in messing up my phone and therefor don't change the settings much. What I know is that the same Kernel can have different outcomes on different Note 3's so please do not post just your Kernel and settings without explanation cause I would like to find the most suited Kernel and settings for my Note.
Sooo...Some help and explanations would be more than appreciated.
4aces said:
I don't know if the answer to my question is somewhere hidden between the thousands of threats but I did try to find it before(including Google and YouTube) and would be more than happy to get a reply.
I'm using custom Kernels since the Note 2 but was never able to put more time and afford in to understand how they actually work and always used the default settings.
Now I'm trying to get some knowledge on Kernel settings and what is safe to change and what not. I'm very interested on how a Kernel works and how I can boost both battery life and/or performance as well as the basic knowledge of the Kernel settings.
At the moment I'm trying to explore with trickster mod to kinda learn by doing but I always get really bad results in testing or no big changes when I change the governor. Also I'm a little afraid in messing up my phone and therefor don't change the settings much. What I know is that the same Kernel can have different outcomes on different Note 3's so please do not post just your Kernel and settings without explanation cause I would like to find the most suited Kernel and settings for my Note.
Sooo...Some help and explanations would be more than appreciated.
Click to expand...
Click to collapse
I can give you a brief (easy) explanation with comparisons to try to get you to understand what a kernel is.
A kernel is your phone's driver (like a car) where it adjusts settings of the hardware and controls how each individual part interacts with each other.
There is a reason you take a car to get tuned up, and that is because a car can go berserk as there is no "maintaining force" - YOU or the person who tunes your car makes changes to the car to make sure it does not overheat, use less power per mile travelled, control how much windshield fluid is being released or how much torque force required to ensure the car does not snap XXXXXX when going at a speed of YYYYYY.
These options are beyond the manufacturer's decisions, and therefore when people flash a kernel you immediately trip KNOX (N9005). You can give your phone less power to process, more power to process (not recommended), speed up the CPU/limit the CPU, control governors on how the disk I/O (input/output) is being handled and/or control how much the phone will swap to it's virtual memory when it reaches no memory.
People think use a custom kernel! It saves you a ton of battery life!. This statement is partially wrong. You have to understand how a kernel reacts to your phone. Even though I know that lite kernels like Wootever's Custom N3 has the best battery life, this is because it has less tweaks and features that may boggle the user, and may allow for subsequent battery life extension compared to CivZ's SneakyKat or Imoseyon's LeanKernel. By inserting new tweaks into the kernel, you allow to have more "useful" features that may add to the "driver's knowledge" - Color tweaking, Fast charge over USB, CIFS support, all are extras that the kernel supports. To save power, developers remove the junk that the manufacturers added and added their own settings to make sure they get the result they would like, then they would share it to the public. However, people recommend custom kernels as they get more options when they flash it, as well as ridding of a lot of the stock settings that manufacturers love setting (default governors, lowest CPU frequency, etc)
CPU governors work by controlling how much speed is used at a given time, a good description of what each governor does is listed here: http://forum.xda-developers.com/showthread.php?t=1736168
I/O governors (simply speaking) control how files and requests are being handled by the system, a good description of what each governors is listed here: http://forum.xda-developers.com/showpost.php?p=23616564&postcount=4. Good way to understand this is if you learnt programming and you learnt the Stack/Queue ADTs in a programming language, it describes things better when looking at the descriptions in the link above.
Adjusting Synapse/Trickster would not get you anywhere to getting the best battery/best performance out of the phone. You will have to experiment and check which kernel is best with your phone, according to your SOC_PVS value. SOC_PVS value is how Qualcomm decides your processor's manufacturing "rank" and if you compare a low rank to a high rank, you will see that you can use less power to operate a high ranked chip compared to a low ranked counterpart. As most governors rely heavily on how the code is handled by the system, you should always go for the kernel that fits your system, and setting configurations depending on your system's likings. By following other people's configurations you risk sporadic reboots and incompatibilities, as not all phones are built the same way.
Things you should not touch if you are afraid of destroying your phone: Overvolting and Overclocking, as these may fry your device if you don't know what you are doing.
Any questions - click reply to this, or else I won't see it!
nicholaschum said:
I can give you a brief (easy) explanation with comparisons to try to get you to understand what a kernel is.
A kernel is your phone's driver (like a car) where it adjusts settings of the hardware and controls how each individual part interacts with each other.
There is a reason you take a car to get tuned up, and that is because a car can go berserk as there is no "maintaining force" - YOU or the person who tunes your car makes changes to the car to make sure it does not overheat, use less power per mile travelled, control how much windshield fluid is being released or how much torque force required to ensure the car does not snap XXXXXX when going at a speed of YYYYYY.
These options are beyond the manufacturer's decisions, and therefore when people flash a kernel you immediately trip KNOX (N9005). You can give your phone less power to process, more power to process (not recommended), speed up the CPU/limit the CPU, control governors on how the disk I/O (input/output) is being handled and/or control how much the phone will swap to it's virtual memory when it reaches no memory.
People think use a custom kernel! It saves you a ton of battery life!. This statement is partially wrong. You have to understand how a kernel reacts to your phone. Even though I know that lite kernels like Wootever's Custom N3 has the best battery life, this is because it has less tweaks and features that may boggle the user, and may allow for subsequent battery life extension compared to CivZ's SneakyKat or Imoseyon's LeanKernel. By inserting new tweaks into the kernel, you allow to have more "useful" features that may add to the "driver's knowledge" - Color tweaking, Fast charge over USB, CIFS support, all are extras that the kernel supports. To save power, developers remove the junk that the manufacturers added and added their own settings to make sure they get the result they would like, then they would share it to the public. However, people recommend custom kernels as they get more options when they flash it, as well as ridding of a lot of the stock settings that manufacturers love setting (default governors, lowest CPU frequency, etc)
CPU governors work by controlling how much speed is used at a given time, a good description of what each governor does is listed here: http://forum.xda-developers.com/showthread.php?t=1736168
I/O governors (simply speaking) control how files and requests are being handled by the system, a good description of what each governors is listed here: http://forum.xda-developers.com/showpost.php?p=23616564&postcount=4. Good way to understand this is if you learnt programming and you learnt the Stack/Queue ADTs in a programming language, it describes things better when looking at the descriptions in the link above.
Adjusting Synapse/Trickster would not get you anywhere to getting the best battery/best performance out of the phone. You will have to experiment and check which kernel is best with your phone, according to your SOC_PVS value. SOC_PVS value is how Qualcomm decides your processor's manufacturing "rank" and if you compare a low rank to a high rank, you will see that you can use less power to operate a high ranked chip compared to a low ranked counterpart. As most governors rely heavily on how the code is handled by the system, you should always go for the kernel that fits your system, and setting configurations depending on your system's likings. By following other people's configurations you risk sporadic reboots and incompatibilities, as not all phones are built the same way.
Things you should not touch if you are afraid of destroying your phone: Overvolting and Overclocking, as these may fry your device if you don't know what you are doing.
Any questions - click reply to this, or else I won't see it!
Click to expand...
Click to collapse
First of all thank u very much for the detailed response. That was exactly what I was looking for. I will get back to you after going through the awesome links you were posting with some more knowledge
One thing which came straight in my mind was how do I know if I have a low or high rank from the soc_pvs_value and where do I find it?
Thanks again!
4aces said:
First of all thank u very much for the detailed response. That was exactly what I was looking for. I will get back to you after going through the awesome links you were posting with some more knowledge
One thing which came straight in my mind was how do I know if I have a low or high rank from the soc_pvs_value and where do I find it?
Thanks again!
Click to expand...
Click to collapse
Anytime
You can either install Synapse (If your Kernel supports it, and click on the button under CPU), or check here:
Code:
/sys/devices/system/soc/soc0/soc_pvs
The higher your number, the better.
nicholaschum said:
Anytime
You can either install Synapse (If your Kernel supports it, and click on the button under CPU), or check here:
Code:
/sys/devices/system/soc/soc0/soc_pvs
The higher your number, the better.
Click to expand...
Click to collapse
I ran out of "thanks" so u get it tomorrow. But thanks again. One more thing:
How do I know if I have a high number/between which numbers does the value wary? My soc_pvs is 3.
4aces said:
I ran out of "thanks" so u get it tomorrow. But thanks again. One more thing:
How do I know if I have a high number/between which numbers does the value wary? My soc_pvs is 3.
Click to expand...
Click to collapse
You got a rather good number.
The lowest is 0, and the highest is 6. I have 2 but I don't undervolt so this is not an issue
nicholaschum said:
You got a rather good number.
The lowest is 0, and the highest is 6. I have 2 but I don't undervolt so this is not an issue
Click to expand...
Click to collapse
Can't thank u enough!!! Now I will be off to some reading and testing
nicholaschum said:
You got a rather good number.
The lowest is 0, and the highest is 6. I have 2 but I don't undervolt so this is not an issue
Click to expand...
Click to collapse
Aaand one more question.
What is the difference in tcp congestion control (cubic/reno) and what does it change?
4aces said:
Aaand one more question.
What is the difference in tcp congestion control (cubic/reno) and what does it change?
Click to expand...
Click to collapse
That seems more of a Trickster Mod specific tweak.
It is more of a network speed tweak which you can read here: http://en.m.wikipedia.org/wiki/TCP_congestion_avoidance_algorithm
In simple words, you have to understand what Network Congestion is, and how queues affect how much data is being transmitted. When too much data is being carried in a link or a node, the quality of service would deteriorate. To do Congestion control, it affects how much data is being transmitted through each node systematically. This is rather complicated to explain using simple terms as this is a mathematical formula which processes how much data is being transmitted.
Cubic is used by many default linux kernels. Like CPU governors, these are data transmission governors, and it is best if you use the one better for your TCP/IP connection (Carrier or Wifi)
nicholaschum said:
That seems more of a Trickster Mod specific tweak.
It is more of a network speed tweak which you can read here: http://en.m.wikipedia.org/wiki/TCP_congestion_avoidance_algorithm
In simple words, you have to understand what Network Congestion is, and how queues affect how much data is being transmitted. When too much data is being carried in a link or a node, the quality of service would deteriorate. To do Congestion control, it affects how much data is being transmitted through each node systematically. This is rather complicated to explain using simple terms as this is a mathematical formula which processes how much data is being transmitted.
Cubic is used by many default linux kernels. Like CPU governors, these are data transmission governors, and it is best if you use the one better for your TCP/IP connection (Carrier or Wifi)
Click to expand...
Click to collapse
Just read the answer in the link u posted. Stupid me.
Sorry for taking up your time.
nicholaschum said:
That seems more of a Trickster Mod specific tweak.
It is more of a network speed tweak which you can read here: http://en.m.wikipedia.org/wiki/TCP_congestion_avoidance_algorithm
In simple words, you have to understand what Network Congestion is, and how queues affect how much data is being transmitted. When too much data is being carried in a link or a node, the quality of service would deteriorate. To do Congestion control, it affects how much data is being transmitted through each node systematically. This is rather complicated to explain using simple terms as this is a mathematical formula which processes how much data is being transmitted.
Cubic is used by many default linux kernels. Like CPU governors, these are data transmission governors, and it is best if you use the one better for your TCP/IP connection (Carrier or Wifi)
Click to expand...
Click to collapse
I have another question. If I want to oc or uv is there any script I have to use or can I just apply/test right away?
4aces said:
I have another question. If I want to oc or uv is there any script I have to use or can I just apply/test right away?
Click to expand...
Click to collapse
Just use the main interface of either Trickster or Synapse. I use Synapse personally as my kernel provides the best interface on Synapse.
nicholaschum said:
Just use the main interface of either Trickster or Synapse. I use Synapse personally as my kernel provides the best interface on Synapse.
Click to expand...
Click to collapse
What I found out so far is that the device runs smoother on performance based governors with cfq or sio scheduler. The best results I had so far was on lean kernel and ael kernel. I'm using the last at the moment cause it has a lot of settings to play with
But it seems that I'm still miles away from finding the best settings.
4aces said:
What I found out so far is that my device reacts not good on performance based governors & schedulers. The best results I had so far was on lean kernel and ael kernel. I'm using the last at the moment cause it has a lot of settings to play with
But it seems that I'm still miles away from finding the best settings.
Click to expand...
Click to collapse
I could give you some recommendations that would work well decently with 2-3 PVS valued processors.
Interactive Governor
No OC, No UV.
I/O schedulers Internal: cfq 512kb
I/O schedulers External: cfq 512kb
Dynamic Fsync Enabled
PowerSuspend driver enabled
Mdnie enabled, 0.39%
FastCharge Enabled
GPU Governor: Simple Ondemand 450MHz
I use CivZ's SneakyKat but Wootever's Custom N3 has the best battery life. If you want features you should play with CivZ's, if you like 6h screen on then you should play with Wootever.
You don't have to follow these values, but I spent days restarting my phone finding the best "average" configuration for devices ranging in my state. I found that Intellidemand didn't do so well and Interactive prevented any sporadic reboots that I got while on Intellidemand. Also read aheads of above 512kb doesn't show much speed enhancements. Synapse is great as it tells you whether your boot is successful or not, and now all my boots get Completed.
Notice: Do not soft reboot when configuring Kernels, Kernels don't get loaded properly/doesn't get reset properly so use Full reboot when configuring
cpu lock
I tried gaming with different kernels and governors and encountered a strange issue. Especially in candy crush after playing for a while the cpu locks (sometimes on 14k sometimes 12k). Reboot fixes it but I'm still curious why it locks.
@nicholaschum any idea?
Btw. my favorite settings so far are intellidemand with deadline gr8 performance and battery life is OK.
4aces said:
I tried gaming with different kernels and governors and encountered a strange issue. Especially in candy crush after playing for a while the cpu locks (sometimes on 14k sometimes 12k). Reboot fixes it but I'm still curious why it locks.
@nicholaschum any idea?
Btw. my favorite settings so far are intellidemand with deadline gr8 performance and battery life is OK.
Click to expand...
Click to collapse
That's a bit weird, did you have powersaving turned on? But I assume it's off.
I think you should disable your kernel mod application in Application Manager and test it out, if it's a problem with Synapse/Trickster then one setting is a bit problematic.
nicholaschum said:
That's a bit weird, did you have powersaving turned on? But I assume it's off.
I think you should disable your kernel mod application in Application Manager and test it out, if it's a problem with Synapse/Trickster then one setting is a bit problematic.
Click to expand...
Click to collapse
Nope that's why it's strange. Even got it after clean flash without setting/installing any Kernel related apps.
Tested other games and they work fine so I deleted candy crush and so far no cpu lock. No idea why, that's why I was curious
4aces said:
Nope that's why it's strange. Even got it after clean flash without setting/installing any Kernel related apps.
Tested other games and they work fine so I deleted candy crush and so far no cpu lock. No idea why, that's why I was curious
Click to expand...
Click to collapse
I don't play Candy Crush so I wouldn't know..haha
nicholaschum said:
I don't play Candy Crush so I wouldn't know..haha
Click to expand...
Click to collapse
Lol. Me neither from now on... (my kids will be sad though) Still can't really belive the game caused it