Related
I am running CM6 A013 with oc-legend-cm-2.6.29.6 kernel. Everything seems to be working just fine except for the wifi. Has anyone gotten the wifi to work with the oc kernels?
I read in another thread that we could take the wlan.ko file from an old ROM. Does anyone have a copy of this file or would anyone be willing to pull the file so that I can test it? I really appreciate it.
same situation here. neither kernels work with cm6's wifi and hotspot. can someone fix this please! i really want my wifi back! i didnt do a backup before hand!
Im looking at this and it looks easier than just replacing the entire kernel like you guys did, read here from that guy's post above:
"How to do it for kernel_legend_13be9c9c:
At first, you should read zanfur's post and his patch.
I just modified two tables in acpuclock-arm11.c excluding his having written.
1. modify cpufreq.c to let SetCPU to access freq tables
2. modify acpuclock-arm11.c to let HTC Legend be able to overclocking
3. modify msm7227_defconfig to disable PERFLOCK [optional]
You might not need modify defconfig when you use SetCPU which can purchase in Android Market.
SetCPU can disable PERFLOCK by setting. ([menu] -> [Perflock Disabler])"
Click to expand...
Click to collapse
So, with that said, I would take that file or file(s) and replace them with the ones in our current kernel made for our phone... might work and your wifi won't be broken.
You guys are running a kernel made for a different device.
could some one say in plain english the exact steps to get the old kernel back? the one from CM6
lilhaiti said:
I am running CM6 A013 with oc-legend-cm-2.6.29.6 kernel. Everything seems to be working just fine except for the wifi. Has anyone gotten the wifi to work with the oc kernels?
I read in another thread that we could take the wlan.ko file from an old ROM. Does anyone have a copy of this file or would anyone be willing to pull the file so that I can test it? I really appreciate it.
Click to expand...
Click to collapse
That kernel is not built for our wifi chip. The kernel needs to be built for the BCM chipset and not the TI. Further, the wifi module needs to be in sync with the kernel build. Android 101.
I am not sure what we are going to gain from overclocking. There just doesn't seem to be any end goal, other than bragging rights on a benchmark where the Aria can only hope to be among the best of the mediocre CPUs. If it's for flash - forget it. We don't have the instruction set required in the CPU. The downside is the potential to add instability and confuse test results for mods that can actually increase functionality.
I like overclocking and running a couple benchmarks once in a while. For day to day use I'm more interested in downclocking but only if it can increase battery life.
Sent from my HTC Liberty using XDA App
the extra speed of the OC makes a big different on the games, that's the reason I like it... Games run smoother with the OC kernel.... do the test.. try to run Abduction with the stock Kernel for a while and then with the OC.. you'll see the difference... also Live Wallpapers with the stock kernel is choppy... it is smooth with the OC.
Hell my nexus one has been over clocked since the day I got it (rooted that same day ) not that a 1ghz phone really needs it. Well the Nexus One maybe for gaming but my Captivate and Vibrant on the other hand doesn't need it period. You won't get better performance gaming with any other android handset out there to date. Still my Captivate is over clocked to 1.2ghz lol. Like I say there's something fun about pushing the limits.
It really just another thing to tweak and play around with on your device. It's always fun to push the limits.
There are several reason why I would like to overclock. 1. The 3D photo gallery loads photos really slow with the stock kernel, but with an overclocked kernel the pics loaded very quickly. 2. It's nice to run a 3D game or two without chopping. Just to name a couple. It would be nice to have an Aria kernel that works with all of the phones hardware. And showing off benchmark number is nice as well.
Feel Free to post and give feedback ^_^
Also feel free to Vote the thread ^_^
Q&A is in Post 2
_____________________________________
Hi Everyone, Arrow here and this is my guide to find what is the best aosp setup for your evo or android. It is true when people say "every phone is different." However there is an average of people that get similar results. At the moment people have different interest such as some people want performance and some want to improve their battery life. Of course certain people want both but only some get both.
*Remember what i put here is an average and may be different on your evo*
AOSP GB ROM'S: Ok so to start off, these are aosp roms still being updated as of now.
CyanogenMod 7 (CM7) - The most famous aosp rom out there, all or almost all other aosp roms are based off of this rom. This rom has a stable rom and experimental nightly builds. Anyone will tell you that you can't go wrong by choosing this rom. and believe me you will enjoy it.
CyanogenMod 7 Thread
Miui - This rom has the longest battery life and is very customizable. This rom is based off of CM7 and is an excelent rom. However unlike CM7 this rom does not have 4g so if you are willing to sacrifice 4g then believe me this is your rom.
Miui Thread
Gingerbread Evo Deck - Ok so although CM7 is amazing decks gb rom has said to be the exact same thing but giving off better battery life. other then that it is pretty much the same thing with some minor tweaks and some bloat ware removed.
Gingerbread-Evo-Deck's Thread
Xplod E4G - Team Nocturnal designed this rom and it is pretty much CM7 with the Sony Launcher + their apps. This rom will give your phone a nice cool feel that other people don't have. If you like a lot of eye candy then get this rom because it is CM7 just with a different look and feel.
Team Nocturnals Xplod E4G RLS1.2
teh roxxorz said:
using Xplod: there's a 50/50 chance the new tiamat kernels [4.0.7+] may not boot, in that case, they should use 3.3.7.
Click to expand...
Click to collapse
ICS(mod7) - Team Blaze designed this rom and you can consider this rom like Xplod E4G, a rom just like CM7 with some minor tweaks but with a different look and feel. None the less this rom has something very special this is the closest rom to being like ICS (Ice Cream Sandwich). I 100% support this rom because they are doing the best they can to make this rom look and run as smooth as ICS. so if you want to look like your ahead of the game definitely get this rom.
ICS(mod7) Thread
AOSP GB Kernels: These are three kernels that i know of, if you know of more please let me know and i will add them.
Tiamat 4.1.0 - This is the latest kernel made by Tiamat and this is the only aosp kernel still being updated. This kernel on average gives people great performance but lacks on battery life. The main Governor for this kernel is SmartassV2 which is a balanced governor, good to turn on your phone and good to use on a normal day to day bases. For this kernel i do recommend using this governor. It does have SBC and Non-SBC kernels. *Side Note* (Some people say Tiamat 3.3.7 works better for them and is also known as the LEE Kernel because it was awesome like Bruce Lee and looks like Lee backwards [337])
Tiamat Website I also put the Zips in the Attachment (At The Bottom)
Savaged-Zen - This kernel is no longer being updated, however it is still amazing this kernel seems to be Tiamat's competition. Where Tiamat lacks on battery Savaged-Zen does not. However it's performance is not as good as Tiamat. This Kernel comes in two version BFS (Brain F***ed Scheduler) and CFS (Completely Fair Scheduler). BFS is said to give better performance and CFS is the normal kernel. This kernel only comes with SBC however you may download "SVZ Manager" which will allow you to turn SBC on or off. The main governor for this kernel i believe is on demand However i use smartass and a lot of people us InteractiveX.
Savaged-Zen CFS sbc I also put the Zips in the Attachment (At The Bottom)
Savaged-Zen BFS sbc in attachments (At The Bottom)
SVZ Manager I also put the Zips in the Attachment (At The Bottom)
GoDm0de - This Kernel was made by toastcfh and is no longer being updated. It is non-sbc and in my opinion definitely the best non-sbc kernel. This Kernel has insane battery life and a pretty good performance. If you do not want to use an sbc kernel i recommend for you to 100% use this kernel. The Governor for this kernel is set on on demand (i think) however i got the best battery/performance using Interactive.
GoDm0dE Kernel I also put the Zips in the Attachment (At The Bottom)
AOSP ICS ROM'S:
ICS rom by: the_Plattypus and it is still in Alpha testing. however the development for this rom is moving really fast so hopefully a beta will come soon.
EVO 4g Ice Cream Sandwich from source
ICS-evo-deck: This Rom is by kushdeck, After testing out Decks ICS Pre-Alpha 4 & 7 rom i conclude that although it is a alpha it can easily be used as a day to day rom. extremely fast and very snappy. only thing that i found not working was the camera. (Now on Alpha5)
[ROM][ICS][1-11-12][WIP] ics-deck-evo [alpha5]
All Decks ICS Pre-Alphas
All Decks ICS Gapps
AOSP ICS Kernels:
Jaredthegreat ICS - jared has the most advanced ics rom which is in beta 2 but does not have a working camera to check this rom go here:
[ROM's] -ICS- 4.0.1-4.0.3>[AOSP]<--~B.2.0~
Will post them when they are released!!!
Rom Manager/Kernel Manager:
Rom Manager: This is an app from the android market and is extremely useful for pretty much anything. you can back up your rom, you may go into boot loader and you can check if certain roms such as "CM7 Nightlies" have been updated. However people do prefer Amon Ra for flashing, which is another plus of Rom Manager it allows you to flash alternative recovery, which will flash Amon Ra for you.
Kernel Manager: This app was working before but has stopped now, however if it does start working again what it had was pretty much all the kernels that you needed for any rom. this app would allow you to flash a new kernel immediately by going to the kernel you want to flash.
Reserved
Q&A:
Q: What is SBC?
A: SBC stands for super battery charger. SBC is trickle charging, It stops your battery from dropping from 100% to 90% right when you take it off the charger. Some say that it harms your battery but i haven't seen any harm and plus it only costs $5 to get a new battery on Amazon.
Q: How to set up and flash your roms and kernels?
A: well my friend "Crossrocker" made a guide for this with everything you need. so just click to go to his thread. [GUIDE||Oct/23]Best AOSP(CM7|Decks|MIUI) configuration.
Q: What is the difference between governors?
A: This Thread by "RJackson" explains it all:SetCPU governors (explained)
But if you're too lazy to click it here they are:
As explaind by RJackson:
ondemand - Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see "up threshold" in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed. - SetCPU website
conservative - Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery. - SetCPU website
performance - Available in most kernels. It will keep the CPU running at the "max" set value at all times. This is a bit more efficient than simply setting "max" and "min" to the same value and using ondemand because the system will not waste resources scanning for the CPU load. This governor is recommended for stable benchmarking. - SetCPU website
powersave - Available in some kernels. It will keep the CPU running at the "min" set value at all times. - SetCPU website
userspace
A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor. - SetCPU website
Interactive - The 'interactive' governor has a different approach. Instead of sampling the cpu
at a specified rate, the governor will scale the cpu frequency up when coming
out of idle. When the cpu comes out of idle, a timer is configured to fire
within 1-2 ticks. If the cpu is 100% busy from exiting idle to when the timer
fires then we assume the cpu is underpowered and ramp to MAX speed.
If the cpu was not 100% busy, then the governor evaluates the cpu load over the
last 'min_sample_rate' (default 50000 uS) to determine the cpu speed to ramp down
to.
As explained by MDJ:
SMARTASS GOVERNOR - is based on the concept of the interactive governor.
I have always agreed that in theory the way interactive works - by taking over the idle loop - is very attractive. I have never managed to tweak it so it would behave decently in real life. Smartass is a complete rewrite of the code plus more. I think its a success. Performance is on par with the "old" minmax and I think smartass is a bit more responsive. Battery life is hard to quantify precisely but it does spend much more time at the lower frequencies.
Smartass will also cap the max frequency when sleeping to 245Mhz (or if your min frequency is higher than 245 - why?! - it will cap it to your min frequency). Lets take for example the 998/245 kernel, it will sleep at 245. No need for sleep profiles any more![/QUOTE]
As explained by teh roxxorz:
Lagfree - like the performance governor. It will scale the cpu to higher frequencies when needed, but not to 100% like performance, so you'll get a lil better battery out of it
SmartassV2 - A smarter smartass governor. Code was re-managed/removed to make it more optimized, and have better scaling performances
InteractiveX - a better interactive governor I believe; low scale cpu settings, for texting, browsing, ect, nothing intensive. I wouldn't use it for emulators, ect.
Q: Do you need PRL/Profile/Radio updates? Do you need to go back to sense based to do these still?
A: No you don't have to go back to sense to do these and you don't have to do these because Rom's will come with what you need. None the less if you would like to update your radios here is a thread by "Calkulin" where he keeps the latest radios updated: [ Radios ][ 9-5 ] All EVO Radio, WiMAX, PRI, NV & HBoot versions
Q: Does HDMI mirroring work on these roms?
A: As of this moment Miui and CM7 both have HDMI mirroring working, and sense all the other ones are cm7 with some tweaks they as well have HDMI working however from what i have read the only one that has not had problems with HDMI is Decks Gingerbread Rom
Q: Are all other major features (4G (except for Miui), bluetooth, front & rear camera, GPS, apps such as Netflix, Skype, Google Voice, Sprint Visual voicemail) all working at least as well as on a Sense or stock ROM?
A: Yes everything is working, however on CM7 and i presume on some others you also have to flash a gps fix which you can get from this thread: [GUIDE||Oct/23]Best AOSP(CM7|Decks|MIUI) configuration. and the Voicemail seems to have some issues for some people but works flawlessly on Decks with it's gapps + Voicemail which you may also get from this thread: [GUIDE||Oct/23]Best AOSP(CM7|Decks|MIUI) configuration.
Q:My wifi is connecting/disconnecting after a second, what should i do?
A: This answer was given to me by "teh roxxorz." This has nothing to do with your rom or kernel, do this:
Back up everything into Titanium Backup
Boot into recovery
wipe cache, Dalvik, and pretty much everything
reflash your rom,kernel and gapps (or if you would like to check out some other roms and kernels just click on the link in my sig)
once you've set up your phone download Titanium Backup from the market
in titanium backup restore all your apps ONLY!!! (don't get apps w/ data - only get apps, and do not get system data)
after this your wifi should be working just fine
Q: I am having wake issues?
A: Here is a Guide made by JBabey[FIX] Wake Issue (Android OS) - Combination of Radio/PRI/NV/Wimax/GPS !Solved!
Q: Can i make my 3g speed faster?
A: Yes, This answer was given to me by teh roxxorz:
You need to flash a sprint sense rom. I emphasize sprint because it won't work on the sense 3.5 roms, as they're all ports of other non sprint roms.
1. Flash sense rom
2. Obtain your msl, download msl reader from market, use it, write it down
3. type in ##3282# , input your msl (you can get this from the app msl reader)
4. Click edit mode > advanced
5. Scroll down to HHTD proxy port and address
6. Change the proxy port to 0 and proxychange the address to 0.0.0.
Q: How can I fix my GPS?
A: This answer was given to me by teh roxxorz:
- flash a sense rom
- open up the dialer
- Type ##GPSCLRX# or ##4772579#
- Your enter your MSL at the prompt
- Your phone will soon reboot > done
Q: Is there a guide like this but for sense roms?
A: Yes if you are looking for a sense guide rather than aosp then check out this thread by tropicalbrit
Q: What is your setup at the moment?
A: Rom - Decks 4.0.3 Pre-Alpha 7 ICS Rom
Kernel - Stock
Governor - Conservative
CPU Max/Min Frequency - 729/128
IncrediControl (app) - (-100) [I get to (-100) by first doing (-75) and leaving it there for 3 days and then I do another (-25)]
Car-o-Dope (CoD) setup
Nice setup. Thanks
Sent from my PC36100 using xda premium
Steven 1 said:
Nice setup. Thanks
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
and thank you for such a quick reply ^_^
Not too bad. Good thing on steering them to tiamat. Lemme know if you need anything.
teh roxxorz said:
Not too bad. Good thing on steering them to tiamat. Lemme know if you need anything.
Click to expand...
Click to collapse
lol i was about to message you to check out this thread, but actually i do need something. do you happen to know a description of: lagfree, smartassV2, and interactiveX? or at least where i can get one?
Green_Arrow said:
lol i was about to message you to check out this thread, but actually i do need something. do you happen to know a description of: lagfree, smartassV2, and interactiveX? or at least where i can get one?
Click to expand...
Click to collapse
Lagfree - like the performance governor. It will scale the cpu to higher frequencies when needed, but not to 100% like performance, so you'll get a lil better battery out of it
SmartassV2 - A smarter smartass governor. Code was re-managed/removed to make it more optimized, and have better scaling performances
InteractiveX - a better interactive governor I believe; low scale cpu settings, for texting, browsing, ect, nothing intensive. I wouldn't use it for emulators, ect.
Also, you should also disclose to people using Xplod: there's a 50/50 chance the new tiamat kernels [4.0.7+] may not boot, in that case, they should use 3.3.7.
And any reason you were gona message me?
teh roxxorz said:
Lagfree - like the performance governor. It will scale the cpu to higher frequencies when needed, but not to 100% like performance, so you'll get a lil better battery out of it
SmartassV2 - A smarter smartass governor. Code was re-managed/removed to make it more optimized, and have better scaling performances
InteractiveX - a better interactive governor I believe; low scale cpu settings, for texting, browsing, ect, nothing intensive. I wouldn't use it for emulators, ect.
Also, you should also disclose to people using Xplod: there's a 50/50 chance the new tiamat kernels [4.0.7+] may not boot, in that case, they should use 3.3.7.
And any reason you were gona message me?
Click to expand...
Click to collapse
pretty much so you can check it out and see if it was good, you seem to post everywhere i do and you seem to know a lot.
Green_Arrow said:
pretty much so you can check it out and see if it was good, you seem to post everywhere i do and you seem to know a lot.
Click to expand...
Click to collapse
Maybe there's a case of a stalker?! [kidding]
Though glad I could help. And thank you.
teh roxxorz said:
Maybe there's a case of a stalker?! [kidding]
Though glad I could help. And thank you.
Click to expand...
Click to collapse
No problem ^_^
Green_Arrow said:
No problem ^_^
Click to expand...
Click to collapse
Tis all good.
has anyone tried that ICS(mod7) rom?
Helpful threads for the win, thanks mr arrow
Sent from my PC36100 using xda premium
Nice helpful thread , I like that you attached the kernels seeing that a lot of people these days are always asking for links to them.
linsalata28 said:
Nice helpful thread , I like that you attached the kernels seeing that a lot of people these days are always asking for links to them.
Click to expand...
Click to collapse
thank you, and yea it was a pain for me to find them just to attach them lol
Toney Starks said:
Helpful threads for the win, thanks mr arrow
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
no problem ^_^
Green_Arrow said:
no problem ^_^
Click to expand...
Click to collapse
You could have asked I keep all of them just incase.
Edit: I quoted the wrong post lol.
I was talking about the kernels.
cnstarz said:
has anyone tried that ICS(mod7) rom?
Click to expand...
Click to collapse
i actually did, it runs really smooth and i believe atm everything is working. if there is anything wrong with it, then it was something cm7 did because it is the same thing with a few tweaks and a different look.
linsalata28 said:
You could have asked I keep all of them just incase.
Edit: I quoted the wrong post lol.
I was talking about the kernels.
Click to expand...
Click to collapse
oh lol i was like huh , and well now i know lol
Hi,
Thanks for guide... I am considering changing from
my stock rooted ROM, so very timely for me!
Some features that you don't mention or summarize
that may help me and others.
PRL/Profile/Radio updates? I believe you need to
go back to sense based to do these still? [yuk]
HDMI mirroring?
Are all other major features (4G (except for Miui),
bluetooth, front & rear camera, GPS, apps such as
Netflix, Skype, Google Voice, Sprint Visual voicemail)
all working at least as well as on a Sense or stock ROM?
Thanks in Advance,
Peter
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
Update
All the changes I made were merged into CoCore-refresh kernel (3.0.31) and 3.0.101 by TeamCanjica, so they will hit 'mainstream' in some time when they release another build.
This thread is over
/Update
Hi,
I've been working on this kernel for some time with improving undervolting in mind. It's based on CoCore Refresh r10 by CoCafe and of course the credit goes to him where it's due.
Main changes:
- rewritten liveOPP internals.
It improved stability a lot - it now allows to use 300/500/700/900 MHz frequencies with no problem and it allows to undervolt low frequencies even more. Freqs >1GHz are now stable at varm=0x32 (at least on my phone), which also saves a lot of power.
Freqs <=400 MHz now use 0x12 (0.925V) voltage by default - It's the original voltage for 400MHz and you can go even lower when undervolting
- rewritten Mali booster algorithm.
It's far from perfect yet, but it eliminated instability due to the fact, that CoCafe's mali booster and "original" booster (switching between APE 50/100 OPP) were working independently and could cause a crash when the original algorithm switched to APE_50_OPP while mali boost was active. APE_50_OPP voltage is 1V by default (0x18), so when clock is boosted to i.e. 700MHz and it switched to 50 OPP, the result was 350MHz @ 1V, which mihgt be too low.
- allow to set APE and DDR OPP with liveOPP
echo apeopp=25/50/100 > arm_stepXX and echo ddropp=...
before the kernel would set ape/ddr opp to 100 for freqs above 400MHz
- allow changing ape_50_opp voltage
echo 0xXX > /sys/kernel/mali/mali_gpu_vape_50_opp
- make wlan/mmc boost tunables available through sysfs in /sys/kernel/performance/*
- Memory split changed to 2G/2G and switch highmem off - it's not needed with this split
- removed some unnecessary drivers and moved others to modules to reduce kernel size
- changed kernel compression to LZO
- 631MB available memory
- 7800ms kernel boot time
Download & install:
Mediafire
That's partition image - flash it with dd:
Code:
dd if=kernel.mk-r1-release.img of=/dev/block/mmcblk0p15
It's also good to create a symlink from /system/lib/modules to /lib/modules - it'll allow modules to autoload, enable modprobe to work and also you can use KoControl app to manage module loading.
Source:
GitHub
TODO:
- create a package for flashing with recovery and place modules (7MB) in /system/lib/modules instead of a ramdisk
- touchbooster has a bug that causes it to limit max freq to 1000MHz on boost.
- figure out how to enable setting of minimal cpu freq - now touchboost always resets it to 100MHz
- add interactive gov from Zwliew kernel
- create more power optimized, auto tuning 'foreground' governor (long story)
My voltage settings
(default kernel voltages are more conservative - set those from init scripts and test them for stability!):
100 - 0x0f
200 - 0x10
300 - 0x11
400 - 0x12
500 - 0x14
600 - 0x18
700 - 0x1d
800 - 0x24
900 - 0x28
1000 - 0x2f
1050..1250 - 0x32
Mali gpu voltage
Default voltage from CoCafe is way too high - idx0 vape could be just 1V since that's the voltage, when mali is running at 1/2 speed (200MHz by default).
My settings (for safety they are 3 steps higher than the lowest working voltage for given freq).
#0 - 0x17
#5 - 0x1c
#9 - 0x23
I don't overclock the gpu - my low index is set to 0 (200MHz), and hi (boosted) to 5(400MHz), which is the original mali freq. That gives mi 100MHz when working at half speed. I don't use any fancy UI effects, so it's enough - when not plaing a game, mali is only working at 100/200MHz and only boosts when loaded. Params:
boost_low idx=0
boost_low threshold=30
boost_delay 2000
boost_high idx=5
boost_high threshold=220
Default kernel settings are left unchanged - set those manually from init scripts.
I place the thread here because I'm not allowed to post in developer forums (<10 messages limit).
MK
Wow. Thanks for your work, mate!
Most people are using CM or CM/AOSP based ROMs nowadays, but there are only a few people (like me) who still use Jellybean. So, I'll try your kernel very soon and I'll post a review after using it.
You joined XDA on 2010 and yet, this is your first post. That just doesn't feel right.. Anyways, keep up the good work, mate. :good:
Good to see another kernel developer for our phone! I'm on stock rom now, I will try it out
Sami Kabir;5571pro. [B said:
Wow. Thanks for your work, mate! [/B]
Most people are using CM or CM/AOSP based ROMs nowadays, but there are only a few people (like me) who still use Jellybean. So, I'll try your kernel very soon and I'll post a review after( using it.
Click to expand...
Click to collapse
The code is on github and there's no problem with merging it with some cm kernel. When I'll try my with some 4.4 again (so far each one had something broken and didn't suit me), I'll probably do it
You joined XDA on 2010 and yet, this is your first post. That just doesn't feel right.. Anyways, keep up the good work, mate. :good:
Click to expand...
Click to collapse
To keep it short let just say that I'm not a sociable type of guy... but when I have something of value, I try to share...
One more thing (most probably know it, but for those who don't) - 99% of "user experience" depends on the settings of governor, mali and touch booster - if you screw this up, no kernel will work smoothly. I had this problem with my first vanilla jb - it sucked as hell(ondemand), but when I set sampling_down_factor to 3-4 suddenly it was very smooth. Default gov params aren't always the best. Thats one of the reasons I'll try to write a governor that tunes itself and adjusts itself to the app currently in foreground - but that's just an idea and it'll take me some time to refresh all the math needed for it...
Anyway - enjoy the kernel.
Hmm I really wanna test this kernel, but I'm currently on Vanir
I definitely gonna follow your thread, it's good to know Janice is still alive and kicking
Reinkaos said:
Hmm I really wanna test this kernel, but I'm currently on Vanir
I definitely gonna follow your thread, it's good to know Janice is still alive and kicking
Click to expand...
Click to collapse
You can always ask rom's devs to merge my changes - it's just a few commits.
And how is that rom working for you? At the time I was checking up 4.4 roms each one of them sucked in a different way. Carbon was the closest (in fact it was the only one acceptable) to being useful (feature- and ui-wise), but it had some process spinning in the background and It was draining my batt (it was unkillable because it was a part of lock screen I think - the bug was known, but no fix available at that time).
If it's similar to carbon I might give it a try...
mkaluza said:
You can always ask rom's devs to merge my changes - it's just a few commits.
And how is that rom working for you? At the time I was checking up 4.4 roms each one of them sucked in a different way. Carbon was the closest (in fact it was the only one acceptable) to being useful (feature- and ui-wise), but it had some process spinning in the background and It was draining my batt (it was unkillable because it was a part of lock screen I think - the bug was known, but no fix available at that time).
If it's similar to carbon I might give it a try...
Click to expand...
Click to collapse
Well I use to be a Carbon die-hard fan before, but since the dev have got himself another device, so I just had to change rom.
And then I try Vanir. Surprisingly it's pretty stable, and we have official support by the Vanir team too.
Feature-wise its just as good as Carbon, but I kinda miss the pie, since Vanir doesn't have it.
And I think Vanir have a bit more features than Carbon do.
Anyway can you go lower than those cpu voltage on your OP? Or is it really not stable?
Mine's 1000 is at 0x2c, 800 at 0x20, and that's the lowest I can go.
And thanks for the gpu voltage :good: , I actually use that value now :laugh:
aioreu the
Reinkaos said:
Well I use to be a Carbon die-hard fan before, but since the dev have got himself another device, so I just had to change rom.
Click to expand...
Click to collapse
It's a pity... but I understand that's only the S Advance branch of Carbon thats dead - the rom itself is being developed further?
And then I try Vanir. Surprisingly it's pretty stable, and we have official support by the Vanir team too.
Feature-wise its just as good as Carbon, but I kinda miss the pie, since Vanir doesn't have it.
And I think Vanir have a bit more features than Carbon do.
Click to expand...
Click to collapse
I didn't like the pie ;P But if you say it's ok, I'll give it a try when I'm in the mood to reinstall everything on the phone...
Anyway can you go lower than those cpu voltage on your OP? Or is it really not stable?
Mine's 1000 is at 0x2c, 800 at 0x20, and that's the lowest I can go.
Click to expand...
Click to collapse
Actually I didn't recheck those two and focused on lower freqs - these were the limits with older LiveOPP, but now I can go to 0x22 and 0x2c.
In fact, 0x24 and 0x2f are already undervolted values - original are 0x28 and 0x32. But every bit counts, especially on higher freqs.
Thanks for the tip
But what's more interesting - 900MHz works at 0x23 (didn't test that before - just took a voltage halfway between 800 and 1000)... there's something wrong with this ARM_100_OPP, but I don't know what yet... Will test the rest again later and post my results.
And thanks for the gpu voltage :good: , I actually use that value now :laugh:
Click to expand...
Click to collapse
Your welcome
When I have time, I'll try to write how to quickly check undervolting limits for both cpu and gpu.
Mk
mkaluza said:
It's a pity... but I understand that's only the S Advance branch of Carbon thats dead - the rom itself is being developed further?
Click to expand...
Click to collapse
Yes, only for our device. It's not really dead yet.
The dev has been kind enough compiling new one once in a while.
I didn't like the pie ;P But if you say it's ok, I'll give it a try when I'm in the mood to reinstall everything on the phone...
Click to expand...
Click to collapse
Yeah, I could understand that. Too much of a hassle. Got to reinstall everything back again.
But you know, I always do clean flash, even with nightlies. Imagine backing up, factory reset and restoring everything in every 3-4 days.
But now I get really used to it
Actually I didn't recheck those two and focused on lower freqs - these were the limits with older LiveOPP, but now I can go to 0x22 and 0x2c.
In fact, 0x24 and 0x2f are already undervolted values - original are 0x28 and 0x32. But every bit counts, especially on higher freqs.
Thanks for the tip
But what's more interesting - 900MHz works at 0x23 (didn't test that before - just took a voltage halfway between 800 and 1000)... there's something wrong with this ARM_100_OPP, but I don't know what yet... Will test the rest again later and post my results.
Click to expand...
Click to collapse
No problem man, thought that information would be useful to you.
Yeah, it would be really nice to go lower, especially on 1000 and 800.
I'm gonna test the rest, and later I would let you know the lowest working voltage that I can go.
And honestly, I have no idea about kernel stuffs :silly: The least that I can do is to play around with it
Your welcome
When I have time, I'll try to write how to quickly check undervolting limits for both cpu and gpu.
Mk
Click to expand...
Click to collapse
Yes, please do. I would really appreciate that :fingers-crossed:
Reinkaos said:
Yes, only for our device. It's not really dead yet.
The dev has been kind enough compiling new one once in a while.
Click to expand...
Click to collapse
He also left a repo with build scripts and manual, so I'll try to build the rom.
Yeah, I could understand that. Too much of a hassle. Got to reinstall everything back again.
But you know, I always do clean flash, even with nightlies. Imagine backing up, factory reset and restoring everything in every 3-4 days.
But now I get really used to it
Click to expand...
Click to collapse
That's hardcore ;P I have patience to do it 1-2 times a year
Yeah, it would be really nice to go lower, especially on 1000 and 800.
I'm gonna test the rest, and later I would let you know the lowest working voltage that I can go.
Click to expand...
Click to collapse
mine crashed at 1000MHz/0x2c - I'm on 0x2d now and it seems ok
And honestly, I have no idea about kernel stuffs :silly: The least that I can do is to play around with it
Click to expand...
Click to collapse
You could always learn It's fun, all the info is there to read for free... all it takes is will and time
Yes, please do. I would really appreciate that :fingers-crossed:
Click to expand...
Click to collapse
I still cant post links, so you need to go to my github (mkaluza), open the i9070_kernel_CoCore-E repo and go to wiki on the right - there is a page "Undervolting janice". Hope this helps.
Mk
mkaluza said:
He also left a repo with build scripts and manual, so I'll try to build the rom.
Click to expand...
Click to collapse
Well that's a good news :good:
That's hardcore ;P I have patience to do it 1-2 times a year
Click to expand...
Click to collapse
LOL yeah
mine crashed at 1000MHz/0x2c - I'm on 0x2d now and it seems ok
Click to expand...
Click to collapse
I'm not sure if mine is really stable, gonna test it with your guide on github
You could always learn It's fun, all the info is there to read for free... all it takes is will and time
Click to expand...
Click to collapse
Yeah, I am learning right now
I still cant post links, so you need to go to my github (mkaluza), open the i9070_kernel_CoCore-E repo and go to wiki on the right - there is a page "Undervolting janice". Hope this helps.
Mk
Click to expand...
Click to collapse
So there are scripts that will provide me with some infos when doing UV-ing
And I'm not familiar with registers though, I only do it via liveopp, but still I'll try this
Thanks for the guide
Anyway I got a question about gpu, lets say my mali low_boost is 400 and high_boost is 480,
does it use the two freq only or it use the other freq in between 400 and 480 too?
P.S. hey you could just spam in OT threads to get 10 posts
Reinkaos said:
I'm not sure if mine is really stable, gonna test it with your guide on github
Click to expand...
Click to collapse
If you don't get random reboots/crashes than it is - when following my guide, the resulting voltage should be stable, but it isn't always so... I'ts just a starting point that can save you some initial crashes or the other way around - if it doesn't pass freq_jump test, then it isn't stable for sure
Anyway I got a question about gpu, lets say my mali low_boost is 400 and high_boost is 480,
does it use the two freq only or it use the other freq in between 400 and 480 too?
Click to expand...
Click to collapse
Only those two - three actually - also 200MHz (that is low_boost/2), but with ape_50_opp voltage, not the one from dvfs_config. There's not much point in doing any smarter gov because gpu intensive apps usually load it at 100% no matter how much power it has - they just have more fps then.
.P.S. hey you could just spam in OT threads to get 10 posts
Click to expand...
Click to collapse
Yeah, maybe, but if those are the rules, then I try to respect them - because I respect the community. (not because I'm some kind of by-the-book guy ;P I ride motorcycle and have already broken so many rules, that they would put me behind bars for life if anybody kept the count ;P).
mkaluza said:
I ride motorcycle and have already broken so many rules, that they would put me behind bars for life if anybody kept the count ;P).
Click to expand...
Click to collapse
You like adrenaline, heh
PS: Sorry for OT
mkaluza said:
If you don't get random reboots/crashes than it is - when following my guide, the resulting voltage should be stable, but it isn't always so... I'ts just a starting point that can save you some initial crashes or the other way around - if it doesn't pass freq_jump test, then it isn't stable for sure
Click to expand...
Click to collapse
Hey, just letting you know, about opptop script, we don't have prcmu-qos folder in /debug. I thought maybe it have a different name, but I couldn't find ape_requirements and ddr_requirements. The others are working fine
Only those two - three actually - also 200MHz (that is low_boost/2), but with ape_50_opp voltage, not the one from dvfs_config. There's not much point in doing any smarter gov because gpu intensive apps usually load it at 100% no matter how much power it has - they just have more fps then.
Click to expand...
Click to collapse
Thanks for the infos :good:
Yeah, maybe, but if those are the rules, then I try to respect them - because I respect the community. (not because I'm some kind of by-the-book guy ;P I ride motorcycle and have already broken so many rules, that they would put me behind bars for life if anybody kept the count ;P).
Click to expand...
Click to collapse
LOL, I'm curious though, what bike do yo own? Must be a real badass one
Force said:
You like adrenaline, heh
PS: Sorry for OT
Click to expand...
Click to collapse
I'ts more about freedom and versatility, but yeah sometimes I like to push it too
Reinkaos said:
Hey, just letting you know, about opptop script, we don't have prcmu-qos folder in /debug. I thought maybe it have a different name, but I couldn't find ape_requirements and ddr_requirements. The others are working fine
Click to expand...
Click to collapse
I forgot... this feature was written by me, so it's available only on my kernel for the moment. But it's not really that important - it was more for debugging purposes for me, now I left it as informative.
I'm trying to build Carbon rom for out phone since last night... when/if I'm done, I'll patch the kernel with my stuff and push it somewhere. What is your kernel version? I think that both carbon and vanir use the same, or at least similar one.
LOL, I'm curious though, what bike do yo own? Must be a real badass one
Click to expand...
Click to collapse
Not really I't an old BMW F650 - only 48 ponies (of which some might have already died of old age ;P). But in reality you can do most of the fun stuff with as little as 125cc Anything bigger is usefull for longer trips/highways/trips with passenger/etc... I mostly ride small country roads and light offroad, so I rarely go over 100km/h, so no badass machine is needed something like 350cc would be best I think. Actually - it's not the bike you ride, but how you ride it... and on narrow roads with many turns a bigger bike is event sometimes harder to ride...
mkaluza said:
I forgot... this feature was written by me, so it's available only on my kernel for the moment. But it's not really that important - it was more for debugging purposes for me, now I left it as informative.
I'm trying to build Carbon rom for out phone since last night... when/if I'm done, I'll patch the kernel with my stuff and push it somewhere. What is your kernel version? I think that both carbon and vanir use the same, or at least similar one.
Click to expand...
Click to collapse
Well ok then. Vanir got a 3.0.101 kernel. It's the same I think? I'll flash and test it when you're done, definitely.
Not really I't an old BMW F650 - only 48 ponies (of which some might have already died of old age ;P). But in reality you can do most of the fun stuff with as little as 125cc Anything bigger is usefull for longer trips/highways/trips with passenger/etc... I mostly ride small country roads and light offroad, so I rarely go over 100km/h, so no badass machine is needed something like 350cc would be best I think. Actually - it's not the bike you ride, but how you ride it... and on narrow roads with many turns a bigger bike is event sometimes harder to ride...
Click to expand...
Click to collapse
lol the biggest one I ever been on is about 130 cc. It's small, enough that you could squeeze through traffics
I don't know much about bike, but AFAIK those superbike need different kind of handling too.
Let's speak just about this kernel as for this is meant this thread
Please anyone tell me how to find the kernel link . I`m a noob at this part :silly: Thanks
pictorul20 said:
Please anyone tell me how to find the kernel link . I`m a noob at this part :silly: Thanks
Click to expand...
Click to collapse
Go here and see download link at top of page: https://github.com/mkaluza/i9070_kernel_CoCore-E
Download link : http://goo.gl/FvqPlg
Then check OP to see how to install it.
Force said:
Go here and see download link at top of page: https://github.com/mkaluza/i9070_kernel_CoCore-E
Download link : http://goo.gl/FvqPlg
Then check OP to see how to install it.
Click to expand...
Click to collapse
Many Thanks.
Hi, this is a friendly request for the senior devs on this forum. I am actually a noob when it comes to kernel compilation. So I wanted to ask if anyone here has already compiled or is willing to compile the latest stock kernel (from 3.6.1) with no other features except kcal controls. Because me and other OP2 users feel that battery life is best on stock kernel but the washed out display is absolutely disgusting. Also if it's not possible just us know, thanks in advance!
ThaRealSaad said:
Hi, this is a friendly request for the senior devs on this forum. I am actually a noob when it comes to kernel compilation. So I wanted to ask if anyone here has already compiled or is willing to compile the latest stock kernel (from 3.6.1) with no other features except kcal controls. Because me and other OP2 users feel that battery life is best on stock kernel but the washed out display is absolutely disgusting. Also if it's not possible just us know, thanks in advance!
Click to expand...
Click to collapse
Did you try boeffla's kernel? gives much better battery life than stock for me (1/3 longer, in any scenario i tested it).
If you still want to have stock kernel here are the kcal commits. just set up Virtualbox Ubuntu, set up build environment , download official op kernel source (the 6.0.0 version!) and cherry-pick the commits (google it).
If the effort is not worth it, use boeffla's or stock without Kcal.
I can try to help you if you're stuck, but mind that i'm just starting with compiling stuff myself.
wertus33333 said:
Did you try boeffla's kernel? gives much better battery life than stock for me (1/3 longer, in any scenario i tested it).
If you still want to have stock kernel here are the kcal commits. just set up Virtualbox Ubuntu, set up build environment , download official op kernel source (the 6.0.0 version!) and cherry-pick the commits (google it).
If the effort is not worth it, use boeffla's or stock without Kcal.
I can try to help you if you're stuck, but mind that i'm just starting with compiling stuff myself.
Click to expand...
Click to collapse
Yeah man I have tried boeffla. Performance is okay but battery isn't as good as stock imho. Maybe my settings affected it. Can you tell me which version of boeffla you use and what settings so maybe I can replicate your results. Thanks man.
ThaRealSaad said:
Yeah man I have tried boeffla. Performance is okay but battery isn't as good as stock imho. Maybe my settings affected it. Can you tell me which version of boeffla you use and what settings so maybe I can replicate your results. Thanks man.
Click to expand...
Click to collapse
Sure, i use boeffla 2.4-beta5, interactive battery extreme governor (u can tweak max frequency on little to 1200mhz), set little cores (i use 2, you can set it to 3-4 for more performance) set big cores to min0, max0 (if you need power to play games etc. set to min0 max 1-2) GPU underclocked to 27mhz, boost disabled, governor adreno (or powersave, might gives lags)
Further i installed xposed, greenify, amplify (there is a free version, but u have to compile it by yourself--> easiest with android studio).
And i followed this thread to maximize my battery life.
Tried several rom and kernel combinations, with this setup i get a sot of 5-6h with 48h of not charging or 7-8h in less than 24h. But on Lineage 13 its even better... (trying to compile a custom oxygenos, debloated, without playstore, F2FS capable right now but not able to activate F2FS)
If you're interested in the ext4 image, tell me (its untested though).
wertus33333 said:
Sure, i use boeffla 2.4-beta5, interactive battery extreme governor (u can tweak max frequency on little to 1200mhz), set little cores (i use 2, you can set it to 3-4 for more performance) set big cores to min0, max0 (if you need power to play games etc. set to min0 max 1-2) GPU underclocked to 27mhz, boost disabled, governor adreno (or powersave, might gives lags)
Further i installed xposed, greenify, amplify (there is a free version, but u have to compile it by yourself--> easiest with android studio).
And i followed this thread to maximize my battery life.
Tried several rom and kernel combinations, with this setup i get a sot of 5-6h with 48h of not charging or 7-8h in less than 24h. But on Lineage 13 its even better... (trying to compile a custom oxygenos, debloated, without playstore, F2FS capable right now but not able to activate F2FS)
If you're interested in the ext4 image, tell me (its untested though).
Click to expand...
Click to collapse
Damn dude these settings sound a bit extreme doesn't your phone lag like hell lol. And oh hey that sounds really interesting! Is it based off 3.6.1? And what kernel have you implemented it with. Right now I'm testing HalogenOS (loving it so far) but when I feel like switching again I would love to try your build. Link me!
ThaRealSaad said:
Damn dude these settings sound a bit extreme doesn't your phone lag like hell lol. And oh hey that sounds really interesting! Is it based off 3.6.1? And what kernel have you implemented it with. Right now I'm testing HalogenOS (loving it so far) but when I feel like switching again I would love to try your build. Link me!
Click to expand...
Click to collapse
I don't even have microlags (with other kernels and this settings it lags like hell, idk why boeffla doesn't)
However, app opening speed and switching between apps is a bit slower than usual).
Idk what the official source's base is (i guess 3.5.8) as i could'nt boot it up yet. Kernel is original kernel (with F2FS activated by me), i'll change this when it boots with f2fs.
I'll send you the link when i have time