Which ROM you are using? - Redmi K20 / Xiaomi Mi 9T Questions & Answers

Share your experience about ROMs of MI 9T ..
Which one do you use now and which one is your favorite and why?
It will help others to switch like me ?
Thank you in advance ?

I am too curious, as I've just bought a Mi 9T and haven't decided yet which ROM I'll try 1st !
From what I'm seeing, the options are MANY:
- LineageOS
- HavocOS
- AOSPExtended
- ExtendedUI
- Evolution X
- Pixel Experience
- Paranoid Android Quartz Alpha
- ....
- ....
I'm familiar already with LineageOS and AOSPExtended (with another device), both are REALLY good...
But from what i am reading, the most Feature Rich / Customizable of all is HavocOS ?

The best ROM to me, and the best customizable is MSM Xtended 6.0 with Anxiety as I/O Scheduler.
https://forum.xda-developers.com/mi-9t/development/rom-msm-xtended-project-v6-0-t4052911
Its customisation level is far beyond Havoc's 3.2, Lineage 17.1, AOSP Extended 7.0 and AOSip Quiche.

Lermite said:
MSM Xtended 6.0
Click to expand...
Click to collapse
SOLD !!!!!!
indeed, it has so many features I'm seriously considering abandoning Xposed for good!
I stopped reading at:
Code:
[B]- System[/B]
Sensor block per-package
Smart Pixel
Wakelock blocker
Amazing !!! :highfive::victory::laugh:
can't wait to flash it clean!

Lermite said:
The best ROM to me, and the best customizable is MSM Xtended 6.0 with Anxiety as I/O Scheduler.
https://forum.xda-developers.com/mi-9t/development/rom-msm-xtended-project-v6-0-t4052911
Its customisation level is far beyond Havoc's 3.2, Lineage 17.1, AOSP Extended 7.0 and AOSip Quiche.
Click to expand...
Click to collapse
I am curently using this ROM from 3 weeks.
What are the benefits of using Anxiety as I/O Scheduler?
Wich is the default? And how to change to the one you are using?

Octavian87 said:
I am curently using this ROM from 3 weeks.
What are the benefits of using Anxiety as I/O Scheduler?
Wich is the default? And how to change to the one you are using?
Click to expand...
Click to collapse
The customisation level of this rom is stunning but it isn't the smoothest.
According to the Aututu benchmark, this rom sucks during a specific test: "ROM random access" that gives only 4600 with the default I/O scheduler CFQ.
Setting Anxiety instead increases this score to more than 10000. This is like unleashing the rom.
My experience of the impact of this score to the everyday use come from my previous phone, the Redmi Note 5, much less powerful than the Mi 9T.
With this score at 1700, browsing a long list was laggy as hell, a real pain to the user.
With this score at 7000, browsing the same list was smooth.
That's why tweaking the I/O scheduler to boost the result to this benchmark test is useful, not only to get a higher score.
The scheduler can be set through any kernel tweaking app.
I use Smartpack Kernel Manager, but it isn't the only one.

Lermite said:
The customisation level of this rom is stunning but it isn't the smoothest.
According to the Aututu benchmark, this rom sucks during a specific test: "ROM random access" that gives only 4600 with the default I/O scheduler CFQ.
Setting Anxiety instead increases this score to more than 10000. This is like unleashing the rom.
My experience of the impact of this score to the everyday use come from my previous phone, the Redmi Note 5, much less powerful than the Mi 9T.
With this score at 1700, browsing a long list was laggy as hell, a real pain to the user.
With this score at 7000, browsing the same list was smooth.
That's why tweaking the I/O scheduler to boost the result to this benchmark test is useful, not only to get a higher score.
The scheduler can be set through any kernel tweaking app.
I use Smartpack Kernel Manager, but it isn't the only one.
Click to expand...
Click to collapse
I get now in antutu 11000 score for rom random acces with the default setting

My bad. I have many apps installed and perhaps one of them has waken up to do its business during the benchmark.
This bunch of apps also explains my score stays lower than yours.
I have to do these tests again to evaluate with more reliability the gain of the I/O scheduler Anxiety in place of CFQ.
Anyway, the MSM Xtended is the best rom for the Mi 9T regardless the benchmarks scores.
EDIT: I confirm I have to apologies. I've no clue what went wrong during my previous tests because the new ones gives different results.
They show that changing the I/O scheduler is pointless.
Here are my results with CFQ then Anxiety:

I'm getting 267000 points. Is ok. Any other settings we cand do for better perfomance and battery?

I've found why I've gotten only 4600 to the Rom Random Access Antutu test while the actual score is 11000:
I got the low score from MSM Xtended 6.0, but an earlier version that had another kernel the actual from 2020-02-17.
That means this score depends much more on the kernel than the rom.

I'm on MSM, tried Kernel Adiutor or Smarpack kernel manager.
When kernel manager started, CPU minimum frequency is forced to be 1.2GHz and no lower, even with CPU section untouched.
Without kernel manager, it can get as low as about 600MHz. So I gave up changing scheduler.
But anyway MSM is best rom as it is. It is more customizable than even havoc.
edit
I tried again and saw CPU frequency going down. Now let's see the scheduler.

I'm using msm extended as well but I'm having issues with Netflix, same for you guys? I get the 5.7 error. There is this magisk tweak but it reduces widevine to l3

Related

[REF][SuperFriendly] Explanation of Governors, I/O Schedulers and Kernels [23-Nov]

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 XPlay 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 *
* Haven't gathered much needed information. Will add it later.
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
Credits
-droidphile
-kokzhanjia
Reserved for kernel infos
Sent from my WT19i
Yes, we do have kernels with Lionheart, lulzactive and intellidemand.
Nice reference cheers.
Sent from Xperia Play (R800a) with Tapatalk
CosmicDan said:
Yes, we do have kernels with Lionheart, lulzactive and intellidemand.
Nice reference cheers.
Sent from Xperia Play (R800a) with Tapatalk
Click to expand...
Click to collapse
Really ? Okay will add it in later
Sent from my WT19i
kokzhanjia said:
Really ? Okay will add it in later
Sent from my WT19i
Click to expand...
Click to collapse
Yeah LuPuS has Lulzactive, Virtuous, Intellidemand, Lazy, Ondemandx, Lionheart and Badass added (but no mention of LionheartX).
Turbo kernel also has intellidemand but the parameters have been modified quite a bit (by me) to suit our snapdragon SOC's better. I think wedgess also put these changes into LuPuS too (at least one of the ICS/JB kernels he builds he said he did). The browser mode still has no effect AFAIK but in my experience it's more battery-friendly and better performance than on-demand (thanks mainly to dbus_input ramping). But many users have reported slightly better gaming experience with SmartAssv2.
Great reference, this will be of much help to new comers, thanks for the hard work you put into this.
CosmicDan said:
Yeah LuPuS has Lulzactive, Virtuous, Intellidemand, Lazy, Ondemandx, Lionheart and Badass added (but no mention of LionheartX).
Turbo kernel also has intellidemand but the parameters have been modified quite a bit (by me) to suit our snapdragon SOC's better. I think wedgess also put these changes into LuPuS too (at least one of the ICS/JB kernels he builds he said he did). The browser mode still has no effect AFAIK but in my experience it's more battery-friendly and better performance than on-demand (thanks mainly to dbus_input ramping). But many users have reported slightly better gaming experience with SmartAssv2.
Click to expand...
Click to collapse
Yeah. Saw your work Nice one.. anymore in depth infos about kernels at here ? I want to add a bonus one for this..
paragroth said:
Great reference, this will be of much help to new comers, thanks for the hard work you put into this.
Click to expand...
Click to collapse
Thanks
Coloured signatures are nice
Nah that's pretty much it
Sent from Xperia Play (R800a) with Tapatalk
Throughout my experience(mainly from observing CPU speeds during music playback), I found that:
Scary:
Ramps up to max after reaching a threshold (50/60% CPU load) then slow scales down to match as 50-80% CPU Load @ X MHz. After a while if load lowers (30-40%), it will clock down to match the 50-80% load. You will see a lot of 100% @ low MHz with this governor.
SavagedZen:
It maintains a 80-90% CPU Load @ X MHz for a fairly constant load. This one also scales based on the Max CPU Freq. settings. So the lower your Max CPU Freq, the better it is at maintaining the CPU Load/MHz balance (for music playback at least).
I didn't look at the source, so these are just from observations only. So I might be talking out of my ass.
Also, having good CPU Load at appropriate CPU Speeds may or may not contribute to battery life. No experiments showed that yet iirc.
Monitoring done via "Diagnosis - System Information" an app that generates an overlay with whatever information your want ie cpu load, speed, memory free, used, disk io, network io, etc.
Refresh rate kept at 5 seconds to keep CPU Load interference minimal (lower than ICS/JB CPU Info overlay from Development, Settings tab).
Great thread, this should be sticky!
jabberwocky_one said:
Throughout my experience(mainly from observing CPU speeds during music playback), I found that:
Scary:
Ramps up to max after reaching a threshold (50/60% CPU load) then slow scales down to match as 50-80% CPU Load @ X MHz. After a while if load lowers (30-40%), it will clock down to match the 50-80% load. You will see a lot of 100% @ low MHz with this governor.
SavagedZen:
It maintains a 80-90% CPU Load @ X MHz for a fairly constant load. This one also scales based on the Max CPU Freq. settings. So the lower your Max CPU Freq, the better it is at maintaining the CPU Load/MHz balance (for music playback at least).
I didn't look at the source, so these are just from observations only. So I might be talking out of my ass.
Also, having good CPU Load at appropriate CPU Speeds may or may not contribute to battery life. No experiments showed that yet iirc.
Monitoring done via "Diagnosis - System Information" an app that generates an overlay with whatever information your want ie cpu load, speed, memory free, used, disk io, network io, etc.
Refresh rate kept at 5 seconds to keep CPU Load interference minimal (lower than ICS/JB CPU Info overlay from Development, Settings tab).
Click to expand...
Click to collapse
Nono you are right. I read these before and your observation is just about it, thanks for the info
chabbe11 said:
Great thread, this should be sticky!
Click to expand...
Click to collapse
Thank you
Sent from my WT19i with Real Xperia r1
Am I setting it up the right way?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I prefer using that minimum and maximum.
And would this screen off profile work, even if I have configured the main minimum? The 100mhz for screen off really saves a lot of my battery.
Sent from my R800i using Tapatalk 2
Gr8 helped me a lot in understanding alll of this .....
bhavei said:
Am I setting it up the right way?
I prefer using that minimum and maximum.
And would this screen off profile work, even if I have configured the main minimum? The 100mhz for screen off really saves a lot of my battery.
Sent from my R800i using Tapatalk 2
Click to expand...
Click to collapse
Yes it is right. I didnt really tried the other way that you mentioned, because i have No-Frills pre-installed in my settings..but i see it worked. Of course it will save battery.. Nice
piku2008 said:
Gr8 helped me a lot in understanding alll of this .....
Click to expand...
Click to collapse
Will add more soon About kernels, Is there any BFS kernels around here ? Most kernels are CFS..
Sent from my WT19i with Real Xperia r1
kokzhanjia said:
About kernels, Is there any BFS kernels around here ? Most kernels are CFS..
Click to expand...
Click to collapse
There was, I ported it over a few months ago. But I removed it because it was causing priority issues. The latest BFS patch for our kernel has some critical bugs, so I ditched it. When I get ext# fixed in .60 kernel up and going I will probably take another crack at it, backporting one of the more recent 3.x BFS versions.
One of the LuPuS kernels might still have na laternative BFS version, but I think wedgess stopped building it for the same reason as me.
CosmicDan said:
There was, I ported it over a few months ago. But I removed it because it was causing priority issues. The latest BFS patch for our kernel has some critical bugs, so I ditched it. When I get ext# fixed in .60 kernel up and going I will probably take another crack at it, backporting one of the more recent 3.x BFS versions.
One of the LuPuS kernels might still have na laternative BFS version, but I think wedgess stopped building it for the same reason as me.
Click to expand...
Click to collapse
I see, there are really few BFS based kernels out there. BFS is better in my opinion so i would like to elaborate more about BFS to attract more users.
Btw, one guy in Xperia Mini, Mini Pro and Active forums had already successfully making it up and running for stock and CM ROMs. Its already hitted version 2.3
Maybe you could get some help from him ? Name is Mesa Kernel.
Sent from my WT19i with Real Xperia r1
kokzhanjia said:
I see, there are really few BFS based kernels out there. BFS is better in my opinion so i would like to elaborate more about BFS to attract more users.
Btw, one guy in Xperia Mini, Mini Pro and Active forums had already successfully making it up and running for stock and CM ROMs. Its already hitted version 2.3
Maybe you could get some help from him ? Name is Mesa Kernel.
Sent from my WT19i with Real Xperia r1
Click to expand...
Click to collapse
I was using v0.313 of BFS, it wasn't that hard - just had to adapt the patch for the Xperia's stupid kernel. That version is so unstable and buggy, in fact all 2.6.x BFS patches were so problematic that the official page has removed them.
I'll check it out, if he back-ported BFS for Linux kernel 3.0 and has them on GitHub, otherwise it would be easier just to do it myself. But I have other more important concerns for Zeus development right now, BFS doesn't really bring any significant performance boost (which is why it is continually rejected from AOSP inclusion).
CosmicDan said:
I was using v0.313 of BFS, it wasn't that hard - just had to adapt the patch for the Xperia's stupid kernel. That version is so unstable and buggy, in fact all 2.6.x BFS patches were so problematic that the official page has removed them.
I'll check it out, if he back-ported BFS for Linux kernel 3.0 and has them on GitHub, otherwise it would be easier just to do it myself. But I have other more important concerns for Zeus development right now, BFS doesn't really bring any significant performance boost (which is why it is continually rejected from AOSP inclusion).
Click to expand...
Click to collapse
Oh... i didnt know that.. anyway, I don't think he has his github set up. I didnt saw a link to his github on his thread. And isnt BFS aimed for forward looking(like only performing on a task that is given without any concerns) ? I read about it at google docs about it. And i don't really know how to explain it clearly..
Good luck in your development my frirend. And this thread has been moved to General section. Hope you can find it and Nice to have another friend
Sent from my WT19i with Real Xperia r1
This is nice info,
Thanks
Thanks man. This is awesome. Much appreciated

benchmark lovers

while I realize that many people hate benchmarks the truth in my humble opinion as a windows hacker and android enthusiast is that benchmarks, run properly, can tell you a whole lot. there is some variances but usually that is from screen brightness settings, running at different core temps, background apps, widgets, and waving the accelerometer around like you just don't care lol. and you can say all you want to synthetic means nothing but the fact is even manufacturer's use benchmarks in their testing of new chips as well. just look at the current benchmarks from sd 600 vs sd 800 from qualcom. so I have decided to carefully benchmark every kernel myself to find what gives ME the best user expieriance. maybe it will help the dev's, maybe not. maybe it will help you, maybe you hate my dog and want to skin my cat.
a benchmark can tell you how well the kernel makes use of the hardware so for testing purposes I have used stock rom on all tests. I have set up my cold box for testing so that the cpu and gpu do not suffer and return quickly to normal and have set brightness at 50. testing is done stationary against the back of the cold box proped so that cool air flows over the systemboard. for testing purposes there is only the stock clock widget and micro cpu monitor and a few battery temp/sytem stats apps running. after each benchmark the tablet memory was swept. all benchmarks were run 3 times and the highest score given is used here unless there was a wild varient and then it was tracked down and all benches ran again. after contemplating it i ran some of these plugged up to the ac on my cold box and sometimes i forgot to plug it up. and some using debugging but i honestly doubt that had an effect. so at any rate my benches will probably be a little lower than yours on all these kernels as im running stuff to keep me informed in the background
im also not really comparing custom kernels to one another but I do to stock kernel, every last one of them are great and offer a lot of features you cant get with stock. all offer performance above stock if the proper settings are used and the overclocks are not to extreme for the framework. they are all also still works in progress so I think they will improve with the developers attention as time goes by. i started with stock kernel and ran antutu, quadrant, velimo, 3d mark ice storm, 3d mark ice storm extreme, basemark x, gfxbench 2.7.0 t-rex hd onscreen, gfx 2.7 egypt hd onscreen
stock kernel
stock ran well and i liked it, but i hated having to long press wifi to toggle and short press takes you to settings, wtf google?
edit.... so at any rate my benches will probably be a little lower than yours on all these kernels as im running stuff to keep me informed in the background
whatever flo 002 kernel
the kernel ran smooth and i liked it. i have the same complaints about it as i do stock. wtf google?
so on this kernel as you can see it functioned better than stock on every single benchmark. some were close but just a little better is...well...better.
jassy release 5 kernel
this kernel is set up to use an external kernel control app. it will not function worth a hill of beans without it in my testing. and even further than that it seems to not like trickster mod for me as it bench's higher with faux kernel control app paid version. real world expierance is good. fauxclock is set to 1.89 ghz CPU OC. cpu ondemand governor. snake charmer and mpdecision on. intelithermal at 60 and 80 respectfully. gpu at 487. gpu simple governor. fiops i/o at 512 read ahead. as you can see in cpu and gpu performance it face smashes stock kernel then kicks it while its down and makes it cry for momma. i dont know what the dude pasted into this kernel but i like it. jassy worked hard so we could have a full featured kernel that works well. release 6 = win, release 5 o yeah baby performance even ondemand. i could still kick this to performance governor lol
elementalx 0.7 kernel
settings with no external kernel control app.
1988 cpu overclock on each core. 487 gpu overclock. simple gpu governor. stock bus. stock voltage. no stw, dtw. the kernel ran well in real world performance. STW and DTW are awsome features by the way and i really like this kernel but didnt install them for testing purposes, one less potential irritation. as you can see it actually lost a bit from stock performance though in every benchmark except basemarkx and gfxbench 2.7 t rex. that tells me there is a problem with cpu performance in this kernel. also look at the cpu vs gpu in antutu vs stock kernel. so what i like this kernel and with lower clocks, dude it rocks. stw and dtw are wins.
elementalx 0.7
settings with no external control app.
1890 cpu overclock on each core. 487 gpu overclock. ondemand governor. stock bus.stock voltage. no stw, no dtw. again the kernel ran well in real world performance but as you can see it took a serious hit in performance at this cpu clock setting. the gpu features continue to score high though
elementalx 0.7 kernel
settings with no external kernel control app.
1728 cpu overclock on each core. 487 gpu overclock. ondemand governor. stock bus. stock voltage. no stw, dtw.
as usual really nice running and here the voltage values are more sane i guess. bested stock in every bench. i figure 1.9 ish before the poo poo hits the fan and performance benches go south rather than north. that seems about the same for the other kernels ive tested too. flar2 really has a winning kernel here with stw and dtw. highly recommend giving it a try
3flo v4 kernel
not testing this one yet as my boy doesn't even have the nexus 7 2013 but I tell ya, I got a good feeling about him. seems dedicated and excited.
Edit...he just got a mpdecision kernel booting and posting good scores but has a cores on touch problem for me. Very beta but it shows that even without a device you can build. Still got a good feeling about this one.
faux123 flo jb 4.3 001 kernel ulta
not coming. I can boot it and even run at highest settings but antutu ehh and im tired lol. maybe ill do it if the overclock structures are changed in some way but ehh not interested in this high on this chip.
faux123 flo jb 4.3 001 ES
settings. faux 123 kernel control paid version. 1.512 ghzcpu. mpdecision off. cpu governor ondemand. snake charmer on. stock voltages. intelli thermal 60 and 80. gpu 400 and ondemand. fiops I/o 512 read ahead.
so here you can see again the same slight loss in gpu performance which lead to slightly lower scores than stock. cool kernel though and I do like intelli thermal so
faux123 flo jb 4.3 001 kernel mainline
settings in faux123 kernel control app paid version. 1.83 cpu OC. CPU Governor ondemand. intelliplug. mpdecision off. eco modeoff. snake charmer on. stock voltages. intelli thermal 60 and 80. gpu 400. gpu governor ondemand. fiops I/o 512 read ahead.
so I found the kernel smooth in real world. I looked for my sweet spot and found it around 1.836-1.89 cpu. above that didn't really work out well for me. so in this great kernel the cpu benchmarks higher than stock but for one reason or other the gpu seems to bench lower than stock. all in all a great kernel and omg I love the idea of eco mode and I think with proper cpu governor and eco this kernel would rock some battery butt.
Tiny kernel
Coming soon

Why the huge performance discrepancies between Rom's ?

Bit of a general question here, but I am getting some really wacky benchmark scores. They're all over the place and id like to know if any of you guys have found a rom and kernel that just works.
I've tried quite a few custom rom's now both Lollipop and Marshmallow, and they've all offered underwhelming performance (Not much faster than my old 801 soc device).
Albeit for the exception of resurrection remix, of which gave me phenomenal in game performance and AnTuTu scores within the 7700 range. A HUGE improvement over stock and other custom Rom's. Unfortunately Resurrection Remix 6.0 is by far the buggiest rom I've loaded, soft reboots everywhere, no working camera and artifacts.
Any recommendations for a good rom ? or should I be focusing on kernels with say stock Oxygen OS ?
I would say stay on OOS so that you can use all Sensors (FP and LF) and give Boeffla Kernel a try. Gives me amazing performance and pretty good benchmarks if i configure the Kernel to give me max performance (i dont do this often because a Benchmark score says nothing). With a balanced setting on the Kernel you get good Battery life and a good performance for daily use.
Use stock with Boeffla, guaranteed stability and from what others have posted with their tweaks seems best option. Everything else looks too experimental or unstable.
just use kernel auditor and use these settings; govenor-interactive, scheduler-row, readahead-1024, in virtual memory dirty ratio-30, dirty background radio-10, swappiness-10, Z-ram-250, under entrphy read-128, write-256. you will hit over 90,000 on antutu with stock rom. I've used these setting with stock with stock kernel, skydragon and oxyslim. i prefer stock now, i just uninstalled the apps i don't use plus oemkitlog, oneplus telephony, com.codeauroroa.img
But why should you even bother with Z-Ram when you have 4GB RAM in this phone?
Doesnt make any sense for me ...
Scherzengel said:
But why should you even bother with Z-Ram when you have 4GB RAM in this phone?
Doesnt make any sense for me ...
Click to expand...
Click to collapse
It is totally pointless in a system with 4GB (even 3) RAM, wouldn't add performance since CPU now has to compress/decompress data on the fly - but what I'm wondering is: does Android have ZRAM by default or is this added? If it's added, lose it. If you were running an emulator this would be a hit.

[Guide] Fixing major CM13 bugs

This thread is meant to help you fix major cyanogenmod 13 bugs. CM 13 based ROMs are very nice, and probably the best way to being the android marshmallow experience to the m7 but they suffer from several problems.
Let's cut to the chase:
1. Camera: install cameringo from the play store, it works flawlessly. Also, cameramx works but expect some fc here and there.
One could argue that neither app is as good as HTC's stock camera app. But sadly they're the only options I'm aware of right now. Plus the m7's cam isn't all that good to begin with. If photography is your top priority you should consider another device.
2. IR blaster: install Asmart remote IR or ct remote from the play store. Both work for me but I recommend trying both and then keep whichever you prefer.
3. heat/battery issues: install no frills or set CPU app from the play store. I Peter no frills as it shows the current settings (so you can memorise them in case you decide to revert later). Kernel auditor is very good too.
Lower the maximum CPU speed to 1.134 GHz. You can change that whenever you need to, but 1.134 provides good battery life without compromising much performance. However before you run a benchmark or any other CPU hungry app remember to increase the max CPU speed back to the highest value.
set the I/o scheduler to bfq. cfq is OK but I prefer bfq. Google I/o bfq vs cfq to learn about the difference.
Set the CPU governor to intelliactive, interactive or smartmax. They're considerably better than ondemand. Smartmax results in lower performance but slightly better battery life. interactive is a very good all around governor. Intelliactive is an enhanced version of interactive. Experiment with all available choices. intellidemand is good too but I prefer intelliactive or interactive. Experiment with all available options your kernel provides. You should be able to figure out your favorite governor thru trial and error.
for more info about CPU governors check out this thread:
http://forum.xda-developers.com/showpost.php?p=59289777&postcount=1
for more info about I/o schedulers:
http://forum.xda-developers.com/showpost.php?p=59289783&postcount=3
Credit where it's due:
@Bharat Makhija directed me to Asmart remote IR, here's his thread:
http://forum.xda-developers.com/showpost.php?p=64405484
Another member directed me to cameringo & cameramx but I can't find the post or remember his name
If that was helpful don't forget to hit the thanks button
Got any other suggestions? Please share them
PS: I'm on crdroid ROM which doesn't have other major bugs.
Great post, I've been wanting to try CM13 on my M7, but I read there were too many bugs. Thanks!
Please test mod Camera Cm13 http://forum.xda-developers.com/oneplus-one/themes-apps/app-cameranext-gallery-cm13-t3305917

Battery Life on CAF based kernel/ROM. Android 7.1.2

Please correct me on anything that I'm about to post below. I will correct it ASAP. Here Goes:
Here's what I've noticed since switching from a stock based ROM (Viper 9) with using EX Kernel to LOS 14.1 or AICP 7.1.2.
From what I've researched, these AOSP builds are using a MSM8960 kernel on our apq8064 board. It is also CAF based kernel as well. MSM8960 is very very similar to APQ8064. Which is why it works on our M7. APQ8064 support ended on CAF around ICS/JB days (from what I've skimmed in the CAF changelog). I've been researching different tunables on the interactive gov and the Ondemand gov. I'm trying to find the best settings to extend the battery while on 7.1.2. To me, it just dies too quickly with default gov tunings either on LOS or AICP. I'd like for other users to post their settings and which gov they are using while on 7.1.2. I'll post my settings as soon as I find the right combination on either the interactive gov or the OnDemand gov.
Edit: I've noticed that by disabling MPDecision and disabling at least 2 cores, battery life has improved. What I have been doing when I play a game is re-enabling the other 2 cores and switching to interactive gov for better in-game experience. I also set the min GPU freq. to 400mhz. Another tunable I adjust is the sync freq in the interactive gov. When gaming I set to either 918mhz or 1026mhz depending on how much load the app places on the cpu.
I've also been tinkering with L Speed app (root required as well). Enabling a profile caused my phone to exhibit a faulty touchscreen. Cherry-picking the optimizations I want doesn't have the same effect.
Which ROM supports customizable turntables or what kernel? I don't use ondemand anymore, it's always interactive for the CPU and simple for the GPU on my end.
i use a kernel manager like Kernel auditor or EX Kernel manager to adjust kernel settings. With those to apps you must have root.
93zx7 said:
i use a kernel manager like Kernel auditor or EX Kernel manager to adjust kernel settings. With those to apps you must have root.
Click to expand...
Click to collapse
Yes I have root, but i'm saying do you have a custom kernel?
zeeBomb said:
Yes I have root, but i'm saying do you have a custom kernel?
Click to expand...
Click to collapse
technically it is. It supports dt2w and s2w. It was linked from the AICP 12.1 Nougat thread

Categories

Resources