Removed
Reserved
So this post will be dedicated to information about EAS in general.
EAS is a completely different breed compared to the conventional HMP system, where it serves an entirely different purpose of achieving the optimal balance between performance and efficiency, with the latter taking the top spot. EAS achieves that via cleverer tasks placement, by which the system determines which is the more efficient cluster for the task to be processed by, as well as categorising the different tasks into cgroups (top-app, foreground and background, in order from highest priority to lowest priority respectively) by which each cgroup receives its sliver of the available firepower (cpuset). EAS also offers the capability of inflating the perceived load, that's determined by the load trackers, of the task in any of the cgroups via its schedtune.boost setting, and whether the task should be processed by all the cpu cores available or only by the cluster the task has been placed on via its schedtune.prefer_idle setting. One of the key features of EAS is lifting almost all the processing from the governor to the CPU scheduler (no it is not the I/O scheduler, something different) and letting it take much much more control, leaving the CPU governor to only do the frequency determination part, which unsurprisingly relies heavily on data supplied by the scheduler. With all that said, it is easily deduced that EAS is not all about governors and governor settings and the like, rather a much cleverer solution that serves the purpose of seeking the best balance between performance and efficiency, and to ensure the CPU is not overdoing a task or the CPU governor is overshooting a simple task, which would attribute to needlessly draining a lot of power as a natural consequence. EAS is about ensuring you get the smoothest UI possible while retaining as much power as possible. However, that does not mean that EAS is lame poor when it comes to performance. Sometimes, if not in most cases, this cleverer tasks placement makes tasks get processed faster, a point that is already proved quite well by the EAS-supporting non-OOS based custom ROMs like VertexOS, ZeNiTy-RR and PAEX. Conserving battery does not necessarily mean crushing performance. This explains that app launches are on-par with HMP if not ahead of it sometimes.
Now on to your question. After going through that brief explanation of EAS, i think your question is actually invalid, since it is not an apple-to-apple comparison anymore. EAS seeks for the optimal balance between performance and efficiency. Should there be a commit to improve performance while not being at the expense of efficiency, EAS should have that stuffed in, whereas HMP is prioritising performance higher than efficiency by design. What Burnout does is taking HMP and making it even more performance oriented, hence it is very unlikely to face micro lags with it. However, HMP still misses the cleverer tasks placement, which can show its canines if you have so much processes going in the background, where in that area EAS takes the lead quite noticeably.
Conclusion: You should try and see what suits you more. But something i can safely say is, EAS is more than satisfactory when it comes to performance from the perspective of a man that always seeks the best performance available, and with the battery gains you yield with EAS, it can go better.
Hope i helped and clear the confusion.
Thanks to @Freak07 for the message.
Reserved
This post will be dedicated to information about Wireguard in general.
WireGuard is a next generation secure VPN tunnel for the Linux kernel, with modern yet conservative cryptography and simple design principles. It is meant as a replacement for OpenVPN and for IPsec, and generally has better performance and security characteristics than both. It also is much easier to use. The whitepaper was peer reviewed for NDSS17 and the protocol itself has been formally verified. Since it lives in the kernel, it not only is very fast, but it is able to integrate in clever ways that are quite nice for battery life and overall smoothness. There are already commercial VPN providers offering services using WireGuard, and it is very easy to run your own WireGuard servers as well.
How to use?
0. Make sure you're running a ROM or kernel that supports WireGuard.
1. Install the WireGuard app: https://play.google.com/store/apps/details?id=com.wireguard.android
2. Sign up for AzireVPN: https://manager.azirevpn.com/en/auth/register
3. Generate and download a configuration file from: https://www.azirevpn.com/cfg/wg
4. Import it into the WireGuard app using "Add from file"
5. You're done
My first impression is that the overall performance has improved, lightning fast responsive touch. Glad to see sound control added, finally I can set up the output speaker desired level when needed. Changed the tcp congestion to westwood as my preference over cubic.
Good job done with the Alize kernel, congratulations to the developer.
Enviado desde mi XT1805 mediante Tapatalk
Thanks for this super cool features , testing
Sent from my XT1804 using XDA-Developers Legacy app
Using with Pixel Experience 64bit.. Never felt so much speed and fluidity in my hand before. With stock settings it's executing everything before I left my finger. Battery seems good so far too
Sent from my XT1806 using Tapatalk
Pixel Experience rom + Alize kernel
Most of the time wi-fi, G+, Tapatalk, Telegram, Chrome, YouTube... normal usage.
Enviado desde mi XT1805 mediante Tapatalk
mrbojangle69 said:
Pixel Experience rom + Alize kernel
Most of the time wi-fi, G+, Tapatalk, Telegram, Chrome, YouTube... normal usage.
Enviado desde mi XT1805 mediante Tapatalk
Click to expand...
Click to collapse
Did you tweak the kernel if so in what way? Or did you flash and forget?
jrubi.arseven said:
Did you tweak the kernel if so in what way? Or did you flash and forget?
Click to expand...
Click to collapse
The only thing I tweaked was the tcp congestion, changed it from cubic to westwood. The rest of the options are the default set up. Honestly I don't think that change to make the difference though.
Enviado desde mi XT1805 mediante Tapatalk
Awesome work buddy, ill give it a go
jrubi.arseven said:
Did you tweak the kernel if so in what way? Or did you flash and forget?
Click to expand...
Click to collapse
I recommended using schedutil Governor and maple Io scheduler , This is based on performance and battery factor
Will this work with cosmic os?
ElectricDrifty said:
Will this work with cosmic os?
Click to expand...
Click to collapse
Is cosmic 64 bit and Oreo...?
ElectricDrifty said:
Will this work with cosmic os?
Click to expand...
Click to collapse
If cosmic is 64 bits Oreo, it will work.
This kernel work on any Oreo rom which is 64 bits, so approximately all of our 8.x rom.
Yea it's working in cosmic, battery life is osm......
DonSolo said:
Using with Pixel Experience 64bit.. Never felt so much speed and fluidity in my hand before. With stock settings it's executing everything before I left my finger. Battery seems good so far too
Sent from my XT1806 using Tapatalk
Click to expand...
Click to collapse
Which ROM are you using?
jhonnyx1000 said:
Which ROM are you using?
Click to expand...
Click to collapse
Just a hunch but he did say he was running Pixel Experience in his first sentence.
Sent by way of magic
AlizeEAS - SANDERS
What's new? (vSeven)
- Upstreamed to 3.18.92
- EAS is reimplemented from Google's commits.
- Schedutil is default cpu governor.
Download: Click here
Awesome kernel, good job man.
tankks
Related
Introduction
"It takes few hours to make a thread but it doesn't even take few seconds to say Thanks"- arpith.fbi
Click to expand...
Click to collapse
Code:
Don't be afraid to ask me anything.
I won't bite, but I might lick you.
Just thank me for this super brief thread.
Give credits to this thread by linking it if you're using any of my info.
Thank you to you too
Have you unlocked your bootloader of your current device ? If so, read it ! If not, learn the benifits ! :victory:
What is this thread about ? It is a very brief explanation of every governors and schedulers to let you find the best combo for your device.
I've been searching a lot about informations about Kernels, Governors, I/O Schedulers and also Android Optimization Tips. No matter its Google or XDA or other android forums. I will go into it and try the best I can to find these infos. So I thought of sharing it to here for the Mini, Mini Pro, Active and also Live with Walkman users.
My main reason to share this is to benefit users for better knowledge about Kernels, Governors, I/O Schedulers and Tips on Android Optimization. I'm not aware of whether where this should be posted, its related to kernels, governors and schedulers so I think it would be best if I share it to here. Yes, I wrote it word by word with references.Happy learning. :angel:
After months on XDA, no matter its in a development forum or Off Topic forum. Users kept on asking what's this what's that. And I'm sure that not all members will understand what is it until they bump into my thread
FAQs regarding on :-
-I/O Schedulers
-Kernel Governers
-Better RAM
-Better Battery
-FAQs
*Will add more when I found something useful.
Click to expand...
Click to collapse
I do a lot of asking by PM, to learn, it doesn't matter whether its a stupid one. (People who know me understands)
With my experience and lots of asking. I managed to find a lot of infos that we can use to optimize our phone.
I will try to explain as clear as I can.
Governors :-
-Smoothass
-Smartass
-SmartassV2
-SavagedZen
-Interactivex
-Lagfree
-Minmax
-Ondemand
-Conservative
-Brazilianwax
-Userspacce
-Powersave
-Performance
-Scary
-Lulzactive *
-Intellidemand *
-Badass *
-Lionheart *
-Lionheartx *
-Virtuous *
* Not yet available in current kernels in this forum
Explanation
OnDemand
Brief
Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point, OnDemand will rapidly scale the CPU up to meet the demand, then gradually scale the CPU down when it isn't needed.
Click to expand...
Click to collapse
Review
Brief says all. By a simple explantion, OnDemand scales up to the required frequency to undergo the action you are doing and rapidly scales down after use.
Conservative
Brief
It is similar to the OnDemand governor, but will scale the CPU up more gradually to better fit demand. Conservative governor provides a less responsive experience than OnDemand, but it does save batter
Click to expand...
Click to collapse
Review
Conservative is the opposite of Interactive; it will slowly ramp up the frequency, then quickly drops the frequency once the CPU is no longer under a certain usage.
Interactive
Brief
Available in latest kernels, it is the default scaling option in some stock kernels. Interactive governor is similar to the OnDemand governor with an even greater focus on responsiveness.
Click to expand...
Click to collapse
Review
Interactive is the opposite of Conservative; it quickly scales up to the maximum allowed frequency, then slowly drops the frequency once no longer in use.
Performance
Brief
Performance governer locks the phone's CPU at maximum frequency. While this may sound like an ugly idea, there is growing evidence to suggest that running a phone at its maximum frequency at all times will allow a faster race-to-idle. Race-to-idle is the process by which a phone completes a given task. After that it returns the CPU to extremely efficient low-power state.
Click to expand...
Click to collapse
Review
Good at gaming, Really good. Disadvantages are it may damage your phone if too much usage.
Powersave
Brief
The opposite of the Performance governor, the Powersave governor locks the CPU frequency at the lowest frequency set by the user.
Click to expand...
Click to collapse
Review
Set it to your desired minimum frequency and you won't have to look for your charger for once in a while.
Scary
Brief
A new governor wrote based on Conservative with some Smartass features, it scales accordingly to Conservative's way. It will start from the bottom. It spends most of its time at lower frequencies. The goal of this is to get the best battery life with decent performance. It will give the same performance as Conservative right now.
Click to expand...
Click to collapse
Review
Hmm.. Overall I don't see any difference. After I understand its main objective. I was very curious and decided to use it again. Results are the same.. No difference. Report to me if anyone has tested this.
Userspace
Brief
Userspace is not a governor pre-set, but instead allows for non-kernel daemons or apps with root permissions to control the frequency. Commonly seen as a redundant and not useful since SetCPU and NoFrills exist.
Click to expand...
Click to collapse
Review
Highly not recommended for use.
Smartass
Brief
It is based on the concept of the Interactive governor.
Smartass is a complete rewrite of the code of Interactive. Performance is on par with the “old” minmax and Smartass is a bit more responsive. Battery life is hard to quantify precisely but it does spend much more time at the lower frequencies.
Click to expand...
Click to collapse
Review
Smartass is rather the governer that will save your battery and make use of your processor for daily use. Like the brief explantion said " Smartass will spend much more time on lower frequencies." So logically you don't need for sleep profiles anymore.
SmartassV2
Brief
Theoretically a merge of the best properties of Interactive and OnDemand; automatically reduces the maximum CPU frequency when phone is idle or asleep, and attempts to balance performance with efficiency by focusing on an "ideal" frequency.
Click to expand...
Click to collapse
Review
This is a much favourite to everybody. I believe almost everyone here is using SmartassV2. Yes, it is better than Smartass because of its speed no scaling frequencies from min to max at a short period of time.
Smoothass
Brief
A much more aggressive version of Smartass that is very quick to ramp up and down, and keeps the idle/asleep maximum frequency even lower.
Click to expand...
Click to collapse
Review
In my personal experience, this is really useful for daily use. And yes, I'm using it all the time. It may decrease your battery life. I saw it OC itself to 1.4 gHz when I set it to 1.2. Good use. Recommended.
Brazilianwax
Brief
Similar to SmartassV2. More aggressive scaling, so more performance, but less battery.
Click to expand...
Click to collapse
Review
Based on SmartassV2. But its advantage is a much more performance wise governor.
SavagedZen
Brief
Another SmartassV2 based governor. Achieves good balance between performance & battery as compared to Brazilianwax.
Click to expand...
Click to collapse
Review
Not much difference compared to SmartassV2. But it is a optimized version of it.
Lagfree
Brief
Again, similar to Smartass but based on Conservative rather than Interactive, instantly jumps to a certain CPU frequency after the device wakes, then operates similar to Conservative. However, it has been noted as being very slow when down-scaling, taking up to a second to switch frequencies.
Click to expand...
Click to collapse
Review
Used it before. Like the name of the governor, I didn't experience any lag whatsoever. Another governor based on performance, but not battery efficient.
MinMax
Brief
MinMax is just a normal governor. No scaling intermediate frequency scaling is used.
Click to expand...
Click to collapse
Review
Well.. it's too normal that I can't really say anything about it..
Interactivex
Brief
InteractiveX governor is based heavily on the Interactive governor, enhanced with tuned timer parameters to optimize the balance of battery vs performance. InteractiveX governor's defining feature, however, is that it locks the CPU frequency to the user's lowest defined speed when the screen is off.
Click to expand...
Click to collapse
Review
A better understanding from the brief to you users, this is an Interactive governor with a wake profile. More battery friendly than Interactive.
Due to current kernels doesn't have these governors. I will be delaying the explanation, its very interesting. If you want it ASAP, post below
-Lulzactive *
-Intellidemand *
-Badass *
-Lionheart *
-Lionheartx *
-Virtuous *
**********************************************************************************************************************************************************************
I/O Schedulers(thanks to droidphile)
Deadline
Goal is to minimize I/O latency or starvation of a request. The same is achieved by round robin policy to be fair among multiple I/O requests. Five queues are aggressively used to reorder incoming requests.
Advantages:
Nearly a real time scheduler.
Excels in reducing latency of any given single I/O.
Best scheduler for database access and queries.
Bandwidth requirement of a process - what percentage of CPU it needs, is easily calculated.
Like noop, a good scheduler for solid state/flash drives.
Disadvantages:
When system is overloaded, set of processes that may miss deadline is largely unpredictable.
Click to expand...
Click to collapse
Noop
Inserts all the incoming I/O requests to a First In First Out queue and implements request merging. Best used with storage devices that does not depend on mechanical movement to access data. Advantage here is that flash drives does not require reordering of multiple I/O requests unlike in normal hard drives.
Advantages:
Serves I/O requests with least number of cpu cycles. (Battery friendly?)
Best for flash drives since there is no seeking penalty.
Good throughput on db systems.
Disadvantages:
Reduction in number of cpu cycles used is proportional to drop in performance.
Click to expand...
Click to collapse
Anticipatory
Based on two facts
i) Disk seeks are really slow.
ii) Write operations can happen whenever, but there is always some process waiting for read operation.
So anticipatory prioritize read operations over write. It anticipates synchronous read operations.
Advantages:
Read requests from processes are never starved.
As good as noop for read-performance on flash drives.
Disadvantages:
'Guess works' might not be always reliable.
Reduced write-performance on high performance disks.
Click to expand...
Click to collapse
BFQ
nstead of time slices allocation by CFQ, BFQ assigns budgets. Disk is granted to an active process until it's budget (number of sectors) expires. BFQ assigns high budgets to non-read tasks. Budget assigned to a process varies over time as a function of it's behavior.
Advantages:
Believed to be very good for usb data transfer rate.
Believed to be the best scheduler for HD video recording and video streaming. (because of less jitter as compared to CFQ and others)
Considered an accurate i/o scheduler.
Achieves about 30% more throughput than CFQ on most workloads.
Disadvantages:
Not the best scheduler for benchmarking.
Higher budget assigned to a process can affect interactivity and increased latency.
Click to expand...
Click to collapse
CFQ
Completely Fair Queuing scheduler maintains a scalable per-process I/O queue and attempts to distribute the available I/O bandwidth equally among all I/O requests. Each per-process queue contains synchronous requests from processes. Time slice allocated for each queue depends on the priority of the 'parent' process. V2 of CFQ has some fixes which solves process' i/o starvation and some small backward seeks in the hope of improving responsiveness.
Advantages:
Considered to deliver a balanced i/o performance.
Easiest to tune.
Excels on multiprocessor systems.
Best database system performance after deadline.
Disadvantages:
Some users report media scanning takes longest to complete using CFQ. This could be because of the property that since the bandwidth is equally distributed to all i/o operations during boot-up, media scanning is not given any special priority.
Jitter (worst-case-delay) exhibited can sometimes be high, because of the number of tasks competing for the disk.
Click to expand...
Click to collapse
SIO
Simple I/O scheduler aims to keep minimum overhead to achieve low latency to serve I/O requests. No priority quesues concepts, but only basic merging. Sio is a mix between noop & deadline. No reordering or sorting of requests.
Advantages:
Simple, so reliable.
Minimized starvation of requests.
Disadvantages:
Slow random-read speeds on flash drives, compared to other schedulers.
Sequential-read speeds on flash drives also not so good.
Click to expand...
Click to collapse
VR
Unlike other schedulers, synchronous and asynchronous requests are not treated separately, instead a deadline is imposed for fairness. The next request to be served is based on it's distance from last request.
Advantages:
May be best for benchmarking because at the peak of it's 'form' VR performs best.
Disadvantages:
Performance fluctuation results in below-average performance at times.
Least reliable/most unstable.
Click to expand...
Click to collapse
**********************************************************************************************************************************************************************
Android Optimization Tips
Want more free RAM/Better Battery Life/More performance ?
There's a lot of ways available for optimizing. Some of them are crap and some of them are actually useful.
Here I will guide you on HOW TO MAKE FULL USE MY TIPS.
Guides/Explanation that needs Modding
LowMemoryKiller (thanks to pikachu01)
LowMemoryKiller is a constant debate between more free RAM and more multitasking capabilities as free RAM.
It is actually a feature in the Android OS for better memory management.
You can read more about it HERE
This is an important feature due to the perennial problem of having low free memory causing lagginess and slowness in launching apps. When you have free memory lingering around the number of 40MB or less, the Android OS just lags like LOL.
What this would mean is, you would want to tweak the LMK to not have the situation of it having less than 40MB (or even close to that).
The modern Linux machine in the Android ecosystem relies on a mechanism called Low Memory Killer (LMK) to consistently free up RAM. This is due to Android's internal mechanism of caching apps (and never fully exiting them) when you press the back button. This is to enable faster app switching and provide a seamless experience for apps usage model. Android also, by itself will also constantly look for often used apps to cache them for faster app opening. This will happen even before your system fully boots.
Now, when you mention LMK, the most obvious thoughts that come up are minfrees and Out Of Memory (OOM) groupings. Yes, those two are integral parts when it comes to LMK. The issue here is that no one actually mentioned that there are two LMK systems in Android, that being:
- Linux LMK
- Android Dalvik VM LMK
Both are separate entities that kills/removes app/dalvik cache from RAM when RAM reaches a certain level.
What confuses most people is that the OOM groupings of both mechanisms have the same names being (Android 2.3 based):
LMK App Categories
FOREGROUND_APP: Your apps in the foreground, being used currently, interfacing with the user.
VISIBLE_APP: Visible app that is still viewable by the user, but not interacting with the user, example could be apps that reside in the status bar, and giving live information i.e. Os monitor graphs.
PERCEPTIBLE_APP: App that the user can still perceive i.e. Music app that is playing music.
HEAVY_WEIGHT_APP: RAM heavy apps that are not being interacted with, but will be a pain to load if its information is cleared in the memory.
SECONDARY_SERVER: App that acts as a secondary server. Not sure what this really means, but client-server thingy but secondary? Could be something that syncs with an app, but is not syncing currently?
BACKUP_APP: App that is currently making a backup (like Titanium backup?)
HOME_APP: Your launcher.
HIDDEN_APP: An exited app that still significant residual memory in the RAM. Exited only some time ago, or is constantly used by the user.
EMPTY_APP: An exited app that only has small remnants of residual memory in RAM. App that is exited quite some time ago.
Click to expand...
Click to collapse
*NOTE I don't really understand OOM Groupings. This is what I learned from the link in the description above.
HEREis Gustavo RD78's thread that users could follow up on OOM Groupings
Want some more about OOMs? Tell me !
Guides/Explanation that uses Apps
-SOON
Guides/Explanation that uses Scripts
Delayed. basically will be reviewing each script available. Will start from this forum's scripts devs be ready to think more on describing you scripts
.BTW, here's The List of Scripts
BONUS!
Manner lessons.
Click the THANKS button whenever somebody helped you.
Also click THANKS to modders and themers and devs. It is understandable that not everybody could donate but clicking a THANKS might also make thier day. They are also humans though. If you were the modder / themer / dev, would you hope people thank you when they're enjoying your work ? YES!
so be respectful to anyone that work tirelessly to provide you with thier ROM, Script, Mods, Themes, etc..
and Click Thanks to them.
Click to expand...
Click to collapse
Would I like a Thanks ? YES OF COURSE
Credits
pikachu01
droidphile
Knight47
Wiki
Google
kokzhanjia
PM me if you THINK you should be here.
Kernel Info
Collecting reviews. Anyone send me your review and i will highly credit you.
If by the time I think I need to update, I will be adding my own review.
*NOTE PM me first to let me know if you're doing it. That way I will give you time and wait you.
FAQ
reserved for questions that are asked frequently
great work bro
very nicely explained and everything
bro i think Knight47 also explained same thing in ray forum...its better u add his credits also
mv_style said:
great work bro
very nicely explained and everything
Click to expand...
Click to collapse
Lol really took me a long time collecting infos. Making me crazy by describing the governors and schedulers.
Anyway Thanks
Sent from my WT19i
sandy7 said:
bro i think Knight47 also explained same thing in ray forum...its better u add his credits also
Click to expand...
Click to collapse
Added.. just saw it.. i think mine is much more brief ?
Sent from my WT19i
kokzhanjia said:
Added.. just saw it.. i think mine is much more brief ?
Sent from my WT19i
Click to expand...
Click to collapse
yup i can see...nice work.
Thanks Sandy..
Very nice explanation bro... Brief and to the point...
Sent from my WT19i using xda app-developers app
Nyc Work bro...briefly Explained...:thumbup:
Sent from my ST15i using xda premium
Excellent job !!
rachit.rc96 said:
Very nice explanation bro... Brief and to the point...
Sent from my WT19i using xda app-developers app
Click to expand...
Click to collapse
Thanks bro.. worked hard for this
Sent from my WT19i
dynamic_4444 said:
Nyc Work bro...briefly Explained...:thumbup:
Sent from my ST15i using xda premium
Click to expand...
Click to collapse
ctragas said:
Excellent job !!
Click to expand...
Click to collapse
these comment motivates me a lot. Thank you. I appreciate it.
Anyone give suggestion please? In depth kernel info first or faq first?
Sent from my WT19i
Hmmm...not bad...
Best Explanation so far i've seen bro
Thanks
http://forum.xda-developers.com/showthread.php?t=1369817
Till-Kruspe said:
Hmmm...not bad...
Click to expand...
Click to collapse
TeamIndia said:
Best Explanation so far i've seen bro
Thanks
Click to expand...
Click to collapse
Thank you. benefit users here
Sent from my WT19i
Yesterday I unlocked the bootloader on my phone and flashed a new kernel. And I was looking for some explanation of the governors..and here it is, just like that Thank you buddy, it really helped me
[email protected] 2
Patrol619 said:
Yesterday I unlocked the bootloader on my phone and flashed a new kernel. And I was looking for some explanation of the governors..and here it is, just like that Thank you buddy, it really helped me
[email protected] 2
Click to expand...
Click to collapse
Great
Sent from my WT19i
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The buck stops here
Project Background
This kernel makes things BETTER. Without tons and tons of over exaggerated fluff
"But BB...What about INTelligentSuperBOOSTXX5MillionPOINT5MegaBlast?!?!?!? Can you add this!?". While I appreciate all the great and free work that several great individuals do for the community. I personally don't see the need to alter any of these TEGRA/Board drivers a whole lot - not on these latest generation of devices. Things run pretty well I think.
"Why don't you just run the stock kernel then you sick low-life waste of space?"
Because, I still think improvements can be made.
I think there's a lot of good intentions out there to make improvements in the kernel-space, BUT:
I've observed a variety of things that were prevalent a couple of years ago and that are still prevalent today. (1) A lot of small things are changed - and advertised as a huge improvement, (2) some tunables are adjusted and advertised as a huge change/improvement but end up being a regression because they were never tested, or (3) some code is merged that causes regressions and it turns out that self-inflicted bugs are being chased around.
Zen is an attempt at improving the stock kernel. That's it.
Project Summary
The Zen kernel has always been oriented at improving the experience for desktop mobile users as much as possible. This iteration of the series is no different. The goal is simple: Improve the experience.
BFS CPU Scheduler
BFS is an alternative CPU scheduler to the stock kernel's CFS. BFS features a simple single-runqueue O earliest virtual deadline first design. There is no need for excessive balancing to achieve fariness on multiple runqueues, nor is there a need for strict NICE values.
The goal of the Brain **** Scheduler, referred to as BFS from here on, is to completely do away with the complex designs of the past for the cpu process scheduler and instead implement one that is very simple in basic design. The main focus of BFS is to achieve excellent desktop interactivity and responsiveness without heuristics and tuning knobs that are difficult to understand, impossible to model and predict the effect of, and when tuned to one workload cause massive detriment to another.
Click to expand...
Click to collapse
Anyway, not going to get into it much but you may find more information in post 2, or throughout this thread (I explained a bit more details about it around page 4).
Also, check these out:
BFS FAQ
BFS Wikia
Android/Tegra 3.10 BFS Port
What is different about this and the 3.10-ck1 bfs v440 patch available on ck.kolivas.org
Backport fixes and features (not SMT NICE) from up to bfs v460ish
Some of Alfred Chen's upstream synchronization and refactoring of BFS methods (linux-3.18/19-gc branch)
My own syncing with mainline as well as backporting
support for tegra yield notifiers
What does this mean
Suspend/Wake issues that were killer on bfs v440 for 3.10 are not present in this port - these issues have been resolved.
You should NEVER report any issue related to this kernel upstream. Not android, linux, or BFS related. Do not report any issues anywhere but here.
"How about the performance?"
This kernel is all about interactivity by default.
The default rr_interval is set to 6. The logic is the human eye cannot detect jitter until about 7ms. Try lowering it if you want to increase interactivity. Try increasing it to achieve higher thoroughput.
-------------------------
Zen/Shamu Features
BFS CPU Scheduler
@flar2 Wake Gestures
USB Fastcharge Support
Fsync SysFS Interface
Overclocking support to 2.5GHz
FIOPS + BFQ in addition to the stock ROW, CFQ, Deadline, No-op I/O schedulers
Several misc upstream updates/fixes.
zRam support
@osm0sis AnyKernel2
---------
Releases
Wipe /cache before flashing for best results
DIRTY FLASH ROM FIRST!
If you have any issues or if you are coming from another custom kernel.
DIRTY FLASH ROM FIRST IF COMING FROM ANOTHER CUSTOM KERNEL
3.10-zen1 "Dollar Drink Night"
First Release/Features:
BFS CPU Scheduler by Con Kolivas. Backport from v461 and Alfred Chen's -gc branch ported to android/tegra 3.10 by me
BFQ + FIOPS I/O Schedulers in addition to CFQ (default), ROW, Deadline
Interactive governor sync'd up with ZenKernel_Shamu
EXT4 from v3.10.y
Several misc. memory leak, race condition fixes, etc. picked from v3.10.y
CPU overclocking up to 2.5GHz
Wake gestures from @flar2
MM+VM Changes from upstream v3.10.y
2A Charging Support
Fsync toggle support
3.10-zen1 AnyKernel Zip (Use for any ROM)
Legacy Releases
3.10-zen0 "Warranty Voided"
Changes:
This is just experimental
Make sure it works
Changes
3.10-zen0 AnyKernel Zip (Use for any ROM)
Thanks guys, and enjoy. Feedback is always appreciated.
XDA:DevDB Information
Zen Kernel, Kernel for the Nexus 9
Contributors
bbedward
Source Code: https://github.com/bbedward/ZenKernel_Flounder
Kernel Special Features:
Version Information
Status: Beta
Current Stable Version: 1
Beta Release Date: 2015-04-19
Created 2015-04-19
Last Updated 2015-04-19
this is untested + experimental.
I fixed a BFS suspend issue in my first test kernel and resolved f2fs issues.
This is here because somebody suggested it to me as the general section is not a good place to be.
AnyKernel zip uploaded
Love your kernel on the nexus 6. And I'm sure I'll love it on the n9!
Thanks man!
omvir said:
Love your kernel on the nexus 6. And I'm sure I'll love it on the n9!
Thanks man!
Click to expand...
Click to collapse
Thanks, if I didn't think -Zen was the best option then it wouldn't exist
I wanted to try this but I guess I'll have to wait till the official 5.1 is out. I'm still running stock ROM with a custom kernel so that puts me on 5.0.1.
time_shock said:
I wanted to try this but I guess I'll have to wait till the official 5.1 is out. I'm still running stock ROM with a custom kernel so that puts me on 5.0.1.
Click to expand...
Click to collapse
Doesn't matter, this is on stock 5.0 base. I use AnyKernel so it's probably compatible with 5.1 too
bbedward said:
Doesn't matter, this is on stock 5.0 base. I use AnyKernel so it's probably compatible with 5.1 too
Click to expand...
Click to collapse
I see why you thought this I just copy pasted my n6 thread
Made some changes.
bbedward said:
Doesn't matter, this is on stock 5.0 base. I use AnyKernel so it's probably compatible with 5.1 too
Click to expand...
Click to collapse
I bootlooped on AICP....went back to Fire and Ice.
Sent from my Nexus 9 using Tapatalk
So in daily usage, what effect should I notice after flashing this kernel? I read lots of your QA and such but still unsure.
Phantom Pt. II said:
So in daily usage, what effect should I notice after flashing this kernel? I read lots of your QA and such but still unsure.
Click to expand...
Click to collapse
I'm not even sure this 0 build works I may have to package an entire ramdisk and quit trying AnyKernel because of all the different 5.1 and 5.0 stuff going on here.
But the point is to add things that matter and things that make a difference. You probably don't care about having 3 alternative random number generators built in the kernel, or about having slightly more optimized memcpy/memmove operations. Not that those things aren't necessarily good, but what's the difference you'll notice with and without those - nothing on the other hand maybe you care about real performance and battery improvements, fast USB charging ,upstream stability, etc, etc.
This is where Zen comes in. Cut out everything except what matters. BFS helps me make a real difference in the performance and battery department.
How does it benefit performance? Well the stock scheduler has lots of overhead with 1 run queue per CPU, huge balancing algorithms, huge fairness calculation algorithms, many tunables. Stuff that's probably pretty essential if you have 64+ logical CPUs where you need to have the separate runqueues to avoid contention issues that come from such a setup. BFS chooses 1 run queue shared by all the CPUs. By design it is able to be fair without big balancing algorithms, interactive without focusing on countless priority calculations, and perhaps most importantly if you run 4 jobs on 4 CPUs it will keep those CPUs busy with a consistent load. On the stock scheduler they may tell you to run -8 or so jobs on a 4 CPU system to keep things busy.
You see a focus on a power-aware CPU scheduler lately as well. What they are doing to achieve that is keep jobs on the left most CPU cores keeping the other ones idle more. On BFS, these power aware things are not applicable because it requires no such load balancer. BFS uses sticky tasks to keep jobs on a CPU which aids in allowing other CPUs to idle more frequently. So when you see 1 CPU get busy 1 CPU will scale in the CPU frequency driver rather than unnecessarily scaling multiple CPUs after balancing.
Anyway, why doesn't google use it if it's so good - because it isn't mainline essentially. It will never go mainline unless they add a pluggable CPU scheduler interface (not in the foreseeable future) because it isn't applicable for a wide variety of systems (specialized for light-NUMA desktop type workloads). Google has had it in an experimental android branch before, but going so far away from mainline takes away a big aspect of support that you get from staying mainline (you get a bug and you can't rely on mainline support)
Why have no other kernels implemented it if it's so good? (They have now, since I brought it here and on the N6) probably because they didn't think it was worth the time to bring back the newest implementation to 3.10 or they didn't have the know how (the official 3.10 -Ck BFS patch is quite old, and broken with suspending - which is why I started the back port/sync process to begin with) so maybe others tried it and gave up.
Anyway the difference between a non-zen nexus 6 and a zen nexus 6 is a noticeable one. It's the only one I believe makes a noticeable performance difference (without over clocking or ramping up frequency scaling). Many claim it makes a noticeable battery difference too, without sacrificing touch boost or killing frequency scaling (in other words, it isn't making lag for better battery life)
Anyway enough rambling. Its coming here to the nexus 9 because I want to continue to support 2014+ nexus devices with my kernels and perhaps one or two other flag ships (I touched the S6 but there's one kernel per variant, their default config is incomplete, typical Samsung mess)
Also there will be a 100% free and open source GPL zen app. Which I think has a brilliant framework and a lot of potential. But that's limited by my time currently.
Let me understand this?
OK, bfs seem to be really smooth but what I'm trying to understand is that bfs is like i/o scheduler right?
AllanJacques said:
Let me understand this?
OK, bfs seem to be really smooth but what I'm trying to understand is that bfs is like i/o scheduler right?
Click to expand...
Click to collapse
No.
1.) I/O scheduler handles how requests to the disks (EMMC/Sdcard in this case) are served (order served first, etc.)
2.) The requests to get disk time are all coming from the CPU. (From the tasks getting CPU time)
3.) The CPU scheduler handles when, for how long, and how to serve the tasks that want CPU time. All factors considered such as keeping things fair between all the CPU cores, tasks that will do blocking due to an I/O wait or synchronization locking.
--BFS (Brain F*** Scheduler) is the CPU scheduler in (3). It is the only well-known replacement to the stock kernel's CFS (completely fair scheduler). I'm sure there have been others since CFS, but I haven't really heard about any. Some one and dones mostly.
What you are thinking of are the I/O schedulers which are completely separate, and only related to how requests to the EMMC/Disk are served. You and many are confusing BFS (Brain F*** Scheduler, CPU/Process scheduler) and BFQ (Budget Fair Queueing, I/O, disk scheduler)
See (both BFS and CFS are preemptive schedulers):
http://en.wikipedia.org/wiki/Scheduling_(computing)#Short-term_scheduling
http://ck.wikia.com/wiki/BFS
Got it!
One last question, BFS rr_interval can be tweaked? What does it do?
AllanJacques said:
Got it!
One last question, BFS rr_interval can be tweaked? What does it do?
Click to expand...
Click to collapse
You have millions and millions of tasks/processes going through the CPU in seconds.
Each task is waiting in line to be scheduled.
When BFS schedules said task, it is allowed to run for a maximum of RR_INTERVAL.
So by default at 6 (ms), a task cannot run for more than 6ms at a time. If it will take longer than that it will be "preempted" by another task, and will have to go back in the queue and wait until it is scheduled again (given a deadline).
If you raise it to 300, for example, a task will be allowed to be running for up to 300ms at a time. (Maybe a task has to wait for for disk time, which may take 100ms or something, etc.)
It is said that the lower value would mean lower latencies seen by the user, and a higher value would see higher thoroughput. 6 is default because it is determined the human eye can't detect jitters below 7ms. You can try lowering it/raising it. See what works best.
I used to always get battery drain on brain f kernels back in the day when it first came out. I look forward to any improvements since then.
dictionary said:
I used to always get battery drain on brain f kernels back in the day when it first came out. I look forward to any improvements since then.
Click to expand...
Click to collapse
The old implementations never sync'd up very well with mainline suspend/wake stuff. Since ~3.12 or so they have - and the one on this kernel (and the N6 kernel) do as well :good:
bbedward said:
The old implementations never sync'd up very well with mainline suspend/wake stuff. Since ~3.12 or so they have - and the one on this kernel (and the N6 kernel) do as well :good:
Click to expand...
Click to collapse
That makes me happy. Will report findings. Thanks again
Working well on CM 12.1 unofficial!
I know this isn't the kernels fault, its googles fault but the interactive governor tunables suck! Do you have any suggestions ? Can you work your magic? Currently its kind of stuttery!
omvir said:
Working well on CM 12.1 unofficial!
I know this isn't the kernels fault, its googles fault but the interactive governor tunables suck! Do you have any suggestions ? Can you work your magic? Currently its kind of stuttery!
Click to expand...
Click to collapse
I will sync it up with the same interactive of zen on the N6. Looks like the tegra version of interactive is a bit older.
B14CKB1RD
Kernel for the Motorola Nexus 6
B14CKB1RD Kernel is made with stability and suitability for what uses you want from your phone. I like a happy medium of minimal and just the right amount of features added in as to not be overbloated. As usual happy flashing. Just note i am not responsible if you the user messes up your phone. I will always be around to help in any way i can so if any issues arise please feel free to send me a pm. ABSOLUTELY NO TROLLING, BASHING, OR ARGUING on the post please. Actions will be taken and you will loose my personal support.
Feel Free to Join us on our public Telegram Chat B14CKB1RD Kernel Nexus 6 Users
https://t.me/B14CKB1RDN6
Note: This kernel is Permissive by default but does allow Enforcing. Also this is NOT force encrypted
Downloads:
For Latest Nougat build:
Download Here
Click to expand...
Click to collapse
For Last Marshmallow build:
Download Here For Upstream Version
Download Here For 3.10.40 Version
Click to expand...
Click to collapse
How to Install:
Boot to recovery
Wipe Cache
Wipe Dalvik/ART Cache
Flash Kernel .zip
Reboot to profit
Click to expand...
Click to collapse
Features:
Governors:
Barry_Allen
Chill
Conservative
Dancedance
Darkness
Interactive
Nightmare
Ondemand
Performance
ZZMoove
I/O Schedulers:
Bfq
Cfq
Deadline
Fiops
Maple
Noop
SioPlus
Zen
TCP Congestion Controls:
Bic
Cubic
Highspeed
Htcp
Hybla
Illinois
Lp
Reno
Scalable
Sociopath
Vegas
Veno
Westwood
Yeah
Other:
Built using B14CKB1RD AnyKernel made by Snuzzo
Updated to latest August mr1.6 Google patches
Linux Kernel 3.10.107
Built with gcc 8.0 toolchain self compiled from GNU/Linaro
KEXEC MultiRom Support
CPU UnderClock
Adreno Idler
CPU OverClock
GPU UnderClock
GPU OverClock
Simple GPU Algorithm
Adreno Idler
Input CPU Boost
AutoSMP Hotplug
Mako Hotplug
State Helper
UnderVoltage Control
CFS Scheduler Policy
LZ4 Compressor/Decompressor
F2FS Support
ExFAT Support
Flar2 Wake Gestures
Franco High Performance Audio
Franco Sound Control
Battery Optimizations
Enhanced Power Efficiency
Fast Charge
Wakelock Controls
Adaptive Low Memory Killer
Power Suspend Mode
State Notifier Mode
Kernel Mode Neon
Asynchronous FSync
Dynamic FSync
Updated LED Blink support
Backport and Updates of LED qpnp driver from Nexus 6P
And many more..
Notes::
For maximum stability. Before I flash each update of my kernel, I go to settings>apps>Kernel-AduitorMod>storage and wipe the cache and data for it for a fresh new setup. I do this because when and if i do add or remove a feature you set on boot and its not there. it may cause conflict.
Starting with Version 1.9. The current rom you're on must have the latest google security patches as of august 2016 in order for wifi to work properly.
If you come across a bug or issue please do not spam the thread. either pm me or reach me on hangouts or g+ by [email protected]
Grab the kernel adiutor i use from here
Grab the version of Viper4Android i use from here
Source:
click here
Frequently Asked Questions:
Q: What is the difference between Upstream and the 3.10.40 version?
A: Upstream (currently 3.10.107) has the latest kernel patches from the Linux kernel upstream updates from kernel.org where as the 3.10.40 is where Google has left the kernel at stock for the n6. Basically it's just updates from Linux Mainline that have fixed issues found in their code. For those that also don't know, Android is a mobile form of Linux and uses the Linux kernel.
Click to expand...
Click to collapse
Q: Whats your current setup using the modded kernel aduitor from yoinx?
A: Darkness governor
CPU Min Frequency is at 300mhz
CPU Max Frequency is at 2496mhz
GPU max frequency is at 600mhz
Hotplug is set to AutoSMP with 4 Max cores online and 2 Min cores online
Screen Color Profile is set to Deep Black Colorful
Sounds Volume Gain is set to 4
DoubleTap2Wake is set to Fullscreen
Vibration is set to 50%
TCP is set to Sociopath
Everything else i leave AS IS.
Click to expand...
Click to collapse
Credits & Thanks
@Snuzzo (for teaching me all he knows about kernel and his code used on many devices)
@hellsgod (for his support, code, and friendship)
@frap129 (for his specially made 6.3.1 toolchain)
@apophis9283 (For his friendship, help and contributions to android)
@xanaxdroid (for his toolchains)
@buckmarble (for his code and contributions)
@Xileforce (for his code and contributions)
@franciscofranco (for his code, contributions and audio tweaks)
@faux123 (for many of his awesome kernel contributions and code)
@flar2 (for Gesture Wake Controls and)
@savoca (for his work and code such as kcal control)
@DespairFactor (for his code and contributions)
@DragonHunt3r (for his code and contributions)
@alucard_24 (for his code and contributions)
@bbedward (for zen decision and his code and contributions)
@Yoinx (for his awesome work on kernel adiutor and general help)
@RenderBroken (For his code, contributions and his friendship)
AOSP for having all this a possibility with open source
All Other Developers who make android a great hobby to enjoy
All of my testers and users thank you for keeping me going.
To any other devs i missed...all your work is very much appreciated. if you feel i should put you on the list let me know via pm and ill gladly do so
Get while it's hot folks.. This one is a beast
Which apps for control kernel synapse ?
cool.boy said:
Which apps for control kernel synapse ?
Click to expand...
Click to collapse
I use kernel aduitor
cool.boy said:
Which apps for control kernel synapse ?
Click to expand...
Click to collapse
Definitely kernel auditor. Much nicer ui, and easier over all
Sent from my Nexus 6 using XDA
---------- Post added at 01:07 AM ---------- Previous post was at 01:06 AM ----------
Mmmmm faux sound control. Tasty. Any chance of your personal settings?
Sent from my Nexus 6 using XDA
Nice!
Welcome back to the fold! Can't wait to try this out.
not balanced said:
Welcome back to the fold! Can't wait to try this out.
Click to expand...
Click to collapse
Glad to be back...and trust me I'm not done yet lol
REV3NT3CH said:
Glad to be back...and trust me I'm not done yet lol
Click to expand...
Click to collapse
Excuse me sir,but i have to ask..
What is different from other kernels,your kernel?
have you done any development for this particular phone?
or just a basic kernel?
im telling you this because i cant find a kernel or a ROM with real development A.K.A coding.
i see that most roms just have features like advanced reboot and framework stuff.
and about kernels i see a lot of overhead,so many choices about tcp congestion, i/o schedulers, cpu governors and stuff,without even explaining what a particular governor has different from the other or tcp congestion choices...
Sorry if this is insulting,will delete asap if you are insulted.
Cheers! :highfive:
The Funky Pear said:
Excuse me sir,but i have to ask..
What is different from other kernels,your kernel?
have you done any development for this particular phone?
or just a basic kernel?
im telling you this because i cant find a kernel or a ROM with real development A.K.A coding.
i see that most roms just have features like advanced reboot and framework stuff.
and about kernels i see a lot of overhead,so many choices about tcp congestion, i/o schedulers, cpu governors and stuff,without even explaining what a particular governor has different from the other or tcp congestion choices...
Sorry if this is insulting,will delete asap if you are insulted.
Cheers! :highfive:
Click to expand...
Click to collapse
Actually there is a whole thread floating around on XDA that explains each governor and what makes them unique as well as I/O Schedulers and TCP controls. Ive put together this kernel with what I feel has the right amount of features needed without over bloating it with them like some and having more than the average minimalist style kernels. Also the more a kernel is overbloated the more chance of bugs you will have as well as it bogging down the overall speed. I do plan on putting some more originality to it like my own governor I'm working on as well as a few other features ive had planned for the future. The biggest thing is stability first and I try to achieve that as much as humanly possible while still getting the best speed, battery life and user experience possible. So whilst currently it has what others have seen here and there ive also spent days finding that right sweetspot of what's been needed to achieve that in the huge world of open source and not just including what's specific to nexus 6 only. I did have a ROM out at one point back in lollipop but has not been around since...that did have originality to it. And will again possibly in the future. Ive worked on and maintained for a few separate devices in the past and was more well known for those older devices. Sad to say besides those few ROM builds I posted last year. Ive been absent in the public scene for about a year total lol. I needed that absense and hiatus away from here for quite a few reasons. I'm one of those ones that's chill and not a "insert bad word here" haha. To simply put it Android is a very fun hobby when no drama is around. And I enjoy sharing my hobby
Sent from my Nexus 6 using Tapatalk
hi,
Can i also ask something?
Are the default settings good for daily use? I just want to flash, that's all.
Droidphilev said:
hi,
Can i also ask something?
Are the default settings good for daily use? I just want to flash, that's all.
Click to expand...
Click to collapse
Sure. I further tweak it with what's available for best use for how I use my phone. I'll also gladly share how I have it set up personally
REV3NT3CH said:
Sure. I further tweak it with what's available for best use for how I use my phone. I'll also gladly share how I have it set up personally
Click to expand...
Click to collapse
Why not? Will follow your settings then
Droidphilev said:
Why not? Will follow your settings then
Click to expand...
Click to collapse
It'll be a bit gotta get the kid on the bus and get some breakfast
REV3NT3CH said:
Actually there is a whole thread floating around on XDA that explains each governor and what makes them unique as well as I/O Schedulers and TCP controls. Ive put together this kernel with what I feel has the right amount of features needed without over bloating it with them like some and having more than the average minimalist style kernels. Also the more a kernel is overbloated the more chance of bugs you will have as well as it bogging down the overall speed. I do plan on putting some more originality to it like my own governor I'm working on as well as a few other features ive had planned for the future. The biggest thing is stability first and I try to achieve that as much as humanly possible while still getting the best speed, battery life and user experience possible. So whilst currently it has what others have seen here and there ive also spent days finding that right sweetspot of what's been needed to achieve that in the huge world of open source and not just including what's specific to nexus 6 only. I did have a ROM out at one point back in lollipop but has not been around since...that did have originality to it. And will again possibly in the future. Ive worked on and maintained for a few separate devices in the past and was more well known for those older devices. Sad to say besides those few ROM builds I posted last year. Ive been absent in the public scene for about a year total lol. I needed that absense and hiatus away from here for quite a few reasons. I'm one of those ones that's chill and not a "insert bad word here" haha. To simply put it Android is a very fun hobby when no drama is around. And I enjoy sharing my hobby
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
well said..
First of all,im sorry for my post, i sounded like a ***** who cries for the best rom and kernel..
I dont know very good english,my native languange is Greek and im from the poorest families you can find in Greece. my very first android smartphone was the international Galaxy S3 EXYNOS and since then i found myself very passionate about android,hold this in your mind-EXYNOS.
this phone was my everything ,i used it to even watch tv and movies on the royal navy that i served for 1 year..and i just became very addicted to XDA and the community in general..
That time,HUGE things going on (development and coding wise).
we had some developers that-i dont know why (they had the money to purchase something better)they loved this phone.
in particular JustArchi..
so much dedication for one phone..
he even booted LINUX inside android via a custom app he coded.
so much optimizations
so much care to the community..
it was a blast..
BUT it just seems i cant find this ecosystem and dedication and above all the excitement from developers to do something different instead of just Blisspop ressurection remix blazing fast rom SUperduper fast etc.
it is the originality that bothers me in this phone.
and im so jeallous i cant code by my self because i wanted to be software engineer but i dropped school with good grades to go to work and contribute to income (money) to my family . (my dad is not in family,and i didnt talk or see him in years)
Anyways,to the topic,it would be nice to see something different!
keep it up,dev.
:good:
Droidphilev said:
Why not? Will follow your settings then
Click to expand...
Click to collapse
Take your time. It's just a hobby so...
BTW: the kernel works on stock and CM based?
Droidphilev said:
Take your time. It's just a hobby so...
BTW: the kernel works on stock and CM based?
Click to expand...
Click to collapse
Yes it works on aosp and cm based roms
Sent from my Nexus 6 using Tapatalk
Droidphilev said:
Take your time. It's just a hobby so...
BTW: the kernel works on stock and CM based?
Click to expand...
Click to collapse
I'm using it on CM13 so far it's pretty solid
Awesome good to see your kernel again Rev3nT3ch, always room for a good permissive kernel.
Thanks my friend
Kernel good, mako hotplug cause's app stoppage and bsod's and also only two cores online?
Edit: only if turned on by the way, so kept off everything ok
Sent from my Nexus 6 using Tapatalk
Hello folks!
This thread is intended for sharing, please be kind. Any suggestions would be appreciated
A few days ago I was tired of having my Mi3 running on stock global dev MIUI 8, it was inefficient system with really bad memory management. On my experience, the MIUI tend to run out of memory. In some case, after a few hours of usage the system cannot reclaim the occupied RAM, thus making the system lags a lot and generate excessive heat!
Yes, MIUI is a feature-rich ROM, and the Mi ecosystem is a pretty mature ecosystem. However, those all greatness needs a lot of power to run on our 3 year old device. After a few research I decided to switch to CM13 ROM.
With efficiency in mind, I do my research and tinkering with my device to get the best setup possible without losing performance. The results are AMAZING! I can use my phone for a whole day without recharge in the mid day. All of this with huge improvement on performance, Real Racing 3 highest graphic setting without any noticeable lag! CPU and battery temperature are now significantly lower (43-47C idle / light tasks, 55-57C heavy gaming). Now that I've found the best setup, I want to share it with you folks! Here we go:
Mi3W 64GB
CM13 ROM snapshot build
CM kernel (automatically flashed while flashing CM13 zip through TWRP)
Screen resolution changed to 720x1280 use this guide
Modded interactive CPU governor (see screenshot below)
Undervolt (see screenshot below, this one really helps reduce CPU working temperature)
Noop I/O scheduler
Reduce aggresiveness of LMK (see screenshot below)
Thats all folks, hope this guide will get our Mi3 having another year of flagship-grade experience! Cheers! :highfive:
How did u undervolt
kingnikpic said:
How did u undervolt
Click to expand...
Click to collapse
It depends on the kernel used. Cm kernel that he used supports undervolt. Careful when undervolting though as too much of it can cause cpu instability and reboots.
kingnikpic said:
How did u undervolt
Click to expand...
Click to collapse
Yes, it depends on the kernel used. Some kernel support undervolting while others don't. You need to flash kernel that support undervolt.
solazz said:
It depends on the kernel used. Cm kernel that he used supports undervolt. Careful when undervolting though as too much of it can cause cpu instability and reboots.
Click to expand...
Click to collapse
While testing CPU voltage value, don't tick "apply on boot" option until you find the most stable voltage without causing system reboot or crashes. Every CPU has different limit on how far you can undervolt, but you can use the values on my screenshot as guidance (Snapdragon 801 / MSM8974-AB only)
Wow!! Thanks a lot bro. I'll fiddle now with my phone.
miui8polska，i cant root it .can you give me a supersu.zip?
Sent from my MI 4LTE using XDA Labs
Random reboot after setting undervolt just likes yours
z1d4n21 said:
Random reboot after setting undervolt just likes yours
Click to expand...
Click to collapse
Undervolting (and clock adjustment, in general) pretty much is a case-per-case basis, so different handsets (even if it's the same type of device) may have different setup. Try lowering it first incrementally and test it, until you have it stable enough.
rxl.noir said:
Undervolting (and clock adjustment, in general) pretty much is a case-per-case basis, so different handsets (even if it's the same type of device) may have different setup. Try lowering it first incrementally and test it, until you have it stable enough.
Click to expand...
Click to collapse
Ok thanks i will test it later
Hi all, I'm happy with LOS performance during light and medium tasks, but my device stutters more than I'd like during heavy tasks (e.g. maps, waze, etc) and app switching. Since battery life has been great, I'm willing to sacrifice some SOT for a more buttery UX. If that's even possible...
I started by changing performance profile from balanced mode to performance mode... and I can honestly say I don't notice a difference.
Now I'm just starting to experiment with changing the CPU and GPU governors using Kernel Adiutor. I've changed both little/big CPUs and GPU from interactive to performance. I'm not sure how to measure the results, but my feeling is that all around performance has increased, but the device still struggles with heavy tasks and app switching.
Anyone else have success tweaking? Please share your methods
JT-on said:
Anyone else have success tweaking? Please share your methods
Click to expand...
Click to collapse
Hi,
Use may be a custom kernel to tweak more.
And here a thread to know about tweaks:
https://forum.xda-developers.com/general/general/ref-to-date-guide-cpu-governors-o-t3048957
The best perf i got is with CPU gov bluactiv and io schedulers tripndroid.
But i did not tweaks all possible values.
I guess a lag will always be present as we have 2gb RAM phone
Disable fsync, set governor to darkness and scheduler to maple.
JT-on said:
Hi all, I'm happy with LOS performance during light and medium tasks, but my device stutters more than I'd like during heavy tasks (e.g. maps, waze, etc) and app switching. Since battery life has been great, I'm willing to sacrifice some SOT for a more buttery UX. If that's even possible...
I started by changing performance profile from balanced mode to performance mode... and I can honestly say I don't notice a difference.
Now I'm just starting to experiment with changing the CPU and GPU governors using Kernel Adiutor. I've changed both little/big CPUs and GPU from interactive to performance. I'm not sure how to measure the results, but my feeling is that all around performance has increased, but the device still struggles with heavy tasks and app switching.
Anyone else have success tweaking? Please share your methods
Click to expand...
Click to collapse
you can use custom kernel and increase performance
i set my governers to lionfish and disable fsync and i/o sceduler to maple its works great
chrisleLP said:
Disable fsync, set governor to darkness and scheduler to maple.
Click to expand...
Click to collapse
alimir98 said:
you can use custom kernel and increase performance
i set my governers to lionfish and disable fsync and i/o sceduler to maple its works great
Click to expand...
Click to collapse
Thanks both for the replies. What kernel do you use? And is there a trade-off when disabling fsync?
JT-on said:
Thanks both for the replies. What kernel do you use? And is there a trade-off when disabling fsync?
Click to expand...
Click to collapse
You can search for it for more info. But TL;DR, fsync prevents data loss when a sudden power outage happens. For example, you are saving something then you accidentally restart your phone for some reason, there is a chance, repeat, a chance of data loss. A whole year of having it disabled, I haven't had any loss.
chrisleLP said:
You can search for it for more info. But TL;DR, fsync prevents data loss when a sudden power outage happens. For example, you are saving something then you accidentally restart your phone for some reason, there is a chance, repeat, a chance of data loss. A whole year of having it disabled, I haven't had any loss.
Click to expand...
Click to collapse
Was working in parallel thanks for the TL;DR. For anyone following this thread, here's more info fsync https://forum.xda-developers.com/showthread.php?t=2244162.
JT-on said:
Was working in parallel thanks for the TL;DR. For anyone following this thread, here's more info fsync https://forum.xda-developers.com/showthread.php?t=2244162.
Click to expand...
Click to collapse
You are very much welcome.
JT-on said:
Thanks both for the replies. What kernel do you use? And is there a trade-off when disabling fsync?
Click to expand...
Click to collapse
using HD kernel with spectrum..its pretty good,,
new Astral kernel is looking good..its in beta stage but working perfectly fine
JT-on said:
Hi all, I'm happy with LOS performance during light and medium tasks, but my device stutters more than I'd like during heavy tasks (e.g. maps, waze, etc) and app switching. Since battery life has been great, I'm willing to sacrifice some SOT for a more buttery UX. If that's even possible...
I started by changing performance profile from balanced mode to performance mode... and I can honestly say I don't notice a difference.
Now I'm just starting to experiment with changing the CPU and GPU governors using Kernel Adiutor. I've changed both little/big CPUs and GPU from interactive to performance. I'm not sure how to measure the results, but my feeling is that all around performance has increased, but the device still struggles with heavy tasks and app switching.
Anyone else have success tweaking? Please share your methods
Click to expand...
Click to collapse
changing data and cache partition to f2fs make it really smooth.
and with HD kernel it makes it even smoother.
Again for anyone following, here's a link to popular HD kernel for Honor 5x, https://forum.xda-developers.com/honor-5x/development/kernel-hotdog-2-0-1-t3544887
While gaming, set the governor to performance for maximum smoothness.