yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
1. I think QCOM and such know better than I do why they use msm-adreno-tz. I have not change it from that yet since I have not played too much with simple_ondemand. I will give it a shot and see what I like best.

2. I was running FIOPS for a long time and decided to try out CFQ. Once again, QCOM and the rest would know best which to use. Though QCOM uses a middle of the road approach. I was getting better performance with CFQ. If anyone knows me they know that I prefer performance over battery. I don't try to neglect battery tuning but nowadays, we are always by a charger and if my phone can go from 6a (Time I wake up) to 10p (time I go to bed) and still have some life left, I am happy. I am not one to go for super stamina. Why have a sweet phone like ours if you settle for lags and such.

3. I was getting better performance with CUBIC than WESTWOOD on my N6. Still need to test further on OP3.

4. Touchboost is from the msm_performance hotplug driver. It can conflict and override cpu-boost. I would rather just have one boosting algorithm. This is also why I have it boost for 1.5secs instead of the normal 40 - 60ms. I also have the boost freqs set to interactives Highspeed freq. This way I can reduce freqs jumping all over the place. I will add a toggle in R2 to disable proper but in the mean time just set the Input Interval to 0.

True about cpu-boost

Also, I am going to assume you are running unencrypted if your default IO is NOOP. I need to adjust my script to set default IOSCHED when unencrypted. It has a different path.

Thanks bro. I will look into it. I couldn't see much so far.
[OnePlus 3 & 3T Cross Device Development] ritchiedrama:
Awesome. Thanks for the detailed reply. I like that you are down to earth and interactive with people using your creation.

I am sticking with your default setup for now; will give it a few days -- then try ZEN etc out for the schedulers. I am more battery orientated than performance, as the performance of this phone is hard to noticably decrease. My minimum req. is that I can achieve 6-7 hours Screen on time; but lately my idles have been the issue, losing 1% per hour idle is too much for me, and with OOS rom's I can't seem to get it lower, only with custom roms. But i'm giving freedom (1.6.1) with your kernel - 1.7 (3.2.8) i've had mad issues with draining seems 50/50 for people with that version.

I'll leave the CPU boost on too. Everything does feel exceptional :)
[OnePlus 3 & 3T Cross Device Development] kerymercury:
i would really like to use this kernel but every time i flash it my wifi wont turn on and i have to revert back to EX kernel which have the wifi module installation during the setup. Do i need to flash a stock rom first before i flash this kernel?
[OnePlus 3 & 3T Cross Device Development] ritchiedrama:
You need to flash stock kernel of your ROM first. So if that is OOS, just re-flash OOS.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Thanks for the kind words! I do this to learn and to teach others what I know. I do it because I truly enjoy it. Yea, I heard OOS has a bad idle drainage problem. I am planning to release a CM based kernel as well.

Flar uses a weird linking for wlan.ko when you flash his kernel. I should be able to adjust for it when flashing my kernel ontop.
[OnePlus 3 & 3T Cross Device Development] ritchiedrama:
I used to get great idle times on all roms, then something changed.

It all seems 50/50 with everyone.
[OnePlus 3 & 3T Cross Device Development] calvinistmac:
Hey [MENTION=5438598]RenderBroken[/MENTION] just came across this kernel as a recommendation from [MENTION=7598050]ritchiedrama[/MENTION]. I have to say this is a really nice kernel. Makes my OP3 perform beautifully. It runs smooth. I read through the whole thread to get myself familiar with it. This kernel is going to be my daily driver for quite some time. Thanks for all of the hard work!
[OnePlus 3 & 3T Cross Device Development] tssphysicsboi:
Will android pay work with this kernel?
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Thanks for the kind words! I put in alot of effort and thought into my work and I am glad that it shows through.

Not certain but I did make the change from Sultan that should allow it to work. If you try, let me know how it goes for you so I can know for future reference or look into fixing it. Thanks!
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
I am moving from Linaro 5.3.2 to Linaro 6.x. So far I am really enjoying the change. I do feel like it is an improvement over the previous toolchain. I have a few more changes incoming for R2 that I think you guys will enjoy.

I am going to have the house to myself for about 10 days since my wife and kids went to go visit in laws. So I should have plenty of free time ;)
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Also, if anyone plays Battlefield 1 on pc and want to squad up. I would love to have you. My username RenderBroken. Go figure right? Let's do this.
[OnePlus 3 & 3T Cross Device Development] mysky911:
Great Kernel. Thanks [MENTION=5438598]RenderBroken[/MENTION].

However, I facing issue on all my changes to big cluster Interactive tuning will be reset very often(not after reboot). Same things happen to HMP Scheduler tunings.. Anything we can do it to prevent the reset??
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
This is news to me. Anyone else having the same issue and have any insight?

I will check it out. Thanks for the report!
[OnePlus 3 & 3T Cross Device Development] Shuvo_bd:
Awesome experience. I was on Franco previously. Flashed and using it since yesterday. So far it's fabulous. I m having very decent back up. Also it feels really snappy.
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
This wasn't happening here at my end
[OnePlus 3 & 3T Cross Device Development] mysky911:
Thanks for your support:D.. I tried with others kernel, but without same issue.

Thanks for your fast support;), i would like to try redo dirty flash Freedom OS 1.7 with stock kernel and reflash your best kernel for a try.

[MENTION=5438598]RenderBroken[/MENTION], anyway to check for the log for the reset issue? :confused:
[OnePlus 3 & 3T Cross Device Development] mysky911:
UPDATES: I tried to uninstall KernelAdiutor before reflashing job. Now everything OK.. No more RESET. Thanks [MENTION=5438598]RenderBroken[/MENTION] for your kind support.:good:
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Thanks for reporting back what the issue was. I will keep that in mind for other users that may experience the same issue.
[OnePlus 3 & 3T Cross Device Development] twist3d0n3:
Remember you from the moto g 1st gen days, good to see you here, render :)
[OnePlus 3 & 3T Cross Device Development] Stroky:
How is the battery life compared to Franco?
[OnePlus 3 & 3T Cross Device Development] Puddi_Puddin:
Try franco and see it yourself, borh are great..
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
Put in the words of Francisco himself

"Please don't be that guy" :)
[OnePlus 3 & 3T Cross Device Development] Stroky:
Guy's.....

I use the Franco Kernel...

I know that Franco is more on the battery side and this kernel here is more performance oriented.

So that's why I wanted to know how this kernel compares in terms of battery life.

Simple question, simple answer..

Could be so easy ;)
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
It sounds like it is too easy, but it isn't. It is generally not that good to post these questions in kernel threads. Some may consider it an offensive post, some may find it rude and whatnot. And even if we eliminate the ethics out of the equation, such opinion of X kernel better than Y is so much subjective and dependent on the user's usage patterns; something that can never be 100% the same for everyone. A ROM plays a role as well; a lot of people blame the kernel for having excessive battery drains and whatnot, while the real cause is a wakelock exceedingly depriving the device from going to sleep. And a lot more factors affecting the user's opinion of which kernel is 'better'.

So please, for everyone and not for you specifically, just DON'T ask these question, at least not in a kernel dev thread. Thank you.

Now go enjoy your stay here with this awesome masterpiece.

Ohh [MENTION=5438598]RenderBroken[/MENTION] your kernel made me roll back to OOS 3.2.7 ;) :highfive:
[OnePlus 3 & 3T Cross Device Development] habylab:
No 3.2.8 love?
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
It is just my data plan ran out early this month, and the throttled speed will download the zip in something like 6 hrs and I don't have that time to spend on it. Besides, the changelog is nothing crucial (1080p60 isn't my thing)

That's it, nothing shocking or anything like that
[OnePlus 3 & 3T Cross Device Development] habylab:
Oh that's fine, do you not have access to wi-fi then? Fair enough if not.
[OnePlus 3 & 3T Cross Device Development] xNAPx:
Any chance to have the kernel on CM13?
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
I am pretty candid and most of my normal users know that about me. I am not afraid to share my opinion.

Mostafa is correct in that in any thread, asking such a question can cause more harm than good. Now don't get me wrong, facts don't care about your feelings but these types of questions are so subjective that it's hard to give a concise answer in anyway that couldn't cast negativity in one direction or another.

I plan on working on it after releasing R2 for OOS. I already have a development plan in place and after finding out all the different pitfalls on the OP3's source when building 70+ test builds, I should be able to do the bringing fairly quickly.

I am hoping Oneplus releases their camera binary asap since that is really the only reason why I am still on OOS. I normally build more for roms I currently use.
[OnePlus 3 & 3T Cross Device Development] xNAPx:
Eagarly waiting I'd really love to try out your kernel
[OnePlus 3 & 3T Cross Device Development] calvinistmac:
What's stopping you? CM?
[OnePlus 3 & 3T Cross Device Development] xNAPx:
Yes
[OnePlus 3 & 3T Cross Device Development] Durrz:
Really excited for this! R1 already is buttery smooth,and battery efficient. Hope R2 delivers even more :)
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
I am hoping to release R2 today or tomorrow and then starting work on CM-R1 immediately after. It will be based on their cm-14.1 branch.
[OnePlus 3 & 3T Cross Device Development] weeka89:
Yaaay :D
[OnePlus 3 & 3T Cross Device Development] mysky911:
I am ready to flash it....:D

Hope to get more speed + battery life... :p

YeeHaa!! :cowboy:

---------- Post added at 03:09 PM ---------- Previous post was at 02:40 PM ----------

So excited for this. [MENTION=5438598]RenderBroken[/MENTION], Just asking whether R2 will be tuned for A57 or A53? :cowboy:
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
whoa whoa whoa!! That is hecka dice! Waiting for that!! :cowboy:

---------- Post added at 05:21 PM ---------- Previous post was at 05:19 PM ----------

May i ask what do you exactly mean with A57 and A53 ?
[OnePlus 3 & 3T Cross Device Development] Antsu:
Maybe something related to this: https://github.com/franciscofranco/one_plus_3/commit/9d9f63b385ff8308a3654668e4565da2dcf52d46
[OnePlus 3 & 3T Cross Device Development] mysky911:
I means the parameter when compiling using toolchain Linaro 6.x.. :D

I read some where posting Snapdragon 820 kryo core is more to A57 compare A53..

Just for extra knowledge to learn from [MENTION=5438598]RenderBroken[/MENTION]. :p
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
I doubt I would make a change like that. I don't like making optimizations that I am not sure of. Franco knows his stuff, no doubt but I would rather be sure that that change is helpful rather than harmful. When it comes to makefile flags, I tend to let the toolchain handle optimizations rather than adding a million compiler flags.
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
On stock OOS, specifically in /vendor/etc i found some proprietary scripts calling the big A57s. And i too remember that somewhere it was called as A57 as well
[OnePlus 3 & 3T Cross Device Development] Durrz:
Best news I've read all day! :)
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Testing my final test build and if all goes well I will release before the day is done. I have put in alot of work into this next build and will be carrying over all Render Kernel commits/changes over to my CM14.1 kernel.
[OnePlus 3 & 3T Cross Device Development] mysky911:
:good:

:victory:
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
R2 is here!!!!

R2 IS HERE!!!!

Download

Things to note:

Alot of cool changes in this new build. I have synced with CAF LA.UM.1.5.5 with regards to /kernel folder and a few other places in the kernel that I find important. I have brought in a number of new scheduler changes that make task placement decisions based on C-States of each core along with many other changes in the scheduler.

Re-did Overclocking by using [MENTION=3637908]kairi_zeroblade[/MENTION] 's work.

Building using Linaro 6.x Toolchain now

Added support for F2FS on /CACHE and /DATA. Now when you flash my kernel, it will replace the FSTAB to add support to any Ramdisk.

Added Adrenoboost by request

Updated Interactive to be inline with CAF LA.UM.1.5.5 - Essentially added Prediction support from the Scheduler. When "enable_prediction" enabled, interactive will no longer use highspeedfreq. For more info, see HERE

See the in depth changelog below for greater detail!

Changelog
[OnePlus 3 & 3T Cross Device Development] kash296:
You have delivered Christmas presents a week early, santa. Nice!! :D
[OnePlus 3 & 3T Cross Device Development] Durrz:
Flashing! Thank you so much for your work :)
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Now that R2 for OOS is out of the way, I plan on working on my CM14 based kernel. I should be able to port over nearly all changes I have made for R2-OOS. So for those that are wanting this kernel for CM, just hang tight.
[OnePlus 3 & 3T Cross Device Development] v7:
R2 stuck at bootlogo and is bootlooping.

Checked the MD5 and it matches.So not a bad download.

PS:I was running stock rooted kernel.

Edit: Doesn't boot with clean flash either.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
What rom you flash on top of?
[OnePlus 3 & 3T Cross Device Development] v7:
3.2.8
[OnePlus 3 & 3T Cross Device Development] calvinistmac:
Running this on FreedomOS 1.7 (3.2.8) flashed over top of Nevax's patched stock kernel. No issues.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Can you try this build out? I have removed the FSTAB Replacement scripting:

R2.1

Let me know and I will make the needed changes. Thanks!
[OnePlus 3 & 3T Cross Device Development] Durrz:
Had this issue also. Although a clean flashed worked for me.
[OnePlus 3 & 3T Cross Device Development] v7:
Still no luck.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
So at least that is not the issue. . . hmm
[OnePlus 3 & 3T Cross Device Development] calvinistmac:
You seem to have the worst luck with kernels man. :D
[OnePlus 3 & 3T Cross Device Development] v7:
Haha!

Maybe coz I test a lot ;)
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Not all phones were created equal.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
So I believe I found the cause, the issue was with the new OC Method I was using from Xceed Kernel. Apparently, there can be issues with speedbin 1 using these new changes. So I have reverted back to old OC Method and will re-release R2 Shortly. Anyone who has previously download R2, please re-download. I will create a new post pointing to it when ready.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
R2 is here. . . .again!!!!

Download

Things to note:

Alot of cool changes in this new build. I have synced with CAF LA.UM.1.5.5 with regards to /kernel folder and a few other places in the kernel that I find important. I have brought in a number of new scheduler changes that make task placement decisions based on C-States of each core along with many other changes in the scheduler.

Building using Linaro 6.x Toolchain now

Added support for F2FS on /CACHE and /DATA. Now when you flash my kernel, it will replace the FSTAB to add support to any Ramdisk.

Added Adrenoboost by request

Updated Interactive to be inline with CAF LA.UM.1.5.5 - Essentially added Prediction support from the Scheduler. When "enable_prediction" enabled, interactive will no longer use highspeedfreq. For more info, see

Changelog
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
[MENTION=5867207]v7[/MENTION] Santa got a new xmas gift here :)
[OnePlus 3 & 3T Cross Device Development] Durrz:
If previous version is working, should we still reflash the revised version?
[OnePlus 3 & 3T Cross Device Development] mysky911:
Oh No!! :crying: The first release of R2 really fly on my op3... It provide a bit lower voltage( just the highest clock 2.3/1.7 is higher voltage)... This will save more battery life if i am not using the top OC speed....

Please let us use the new lower voltage...:crying:
[OnePlus 3 & 3T Cross Device Development] chinmai560621:
May I know what's this adrenoboost? Couldn't find out.
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
It is equivalent to EX's GPU Boost I think.
[OnePlus 3 & 3T Cross Device Development] Rawwrius01:
Heavy Thing man......Really great Kernel ! Keep ist up.

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3 & 3T Cross Device Development] habylab:
This is something I'd like to know as well actually.

Edit: says in post before new release to use the new one, so I shall.
[OnePlus 3 & 3T Cross Device Development] Jole7:
Please leave the higher overclock frequencies at 2.34 / 1.78
[OnePlus 3 & 3T Cross Device Development] mysky911:
[MENTION=5438598]RenderBroken[/MENTION], Can we request back the first R2 Overclocking frequencies and Voltage? Maybe we can have 2.1/1.5 as default frequencies on booting up for stability ... User choose to OC after bootup if their phone got no issue with higher clock speed..
[OnePlus 3 & 3T Cross Device Development] weeka89:
I guess that every user here knows how to edit his own frequencies by himself, it's the devs build and he chooses how to build it
[OnePlus 3 & 3T Cross Device Development] Jole7:
Then why don't you make a new kernel if it's so easy?
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
I am still looking into OC. I have a lead to what the issue could be and may be able to re release with the new oc. It appears to be a problem with speedbin1 users though I haven't verified.

Mainly, I don't like releasing builds that are not completely stable and unfortunately, R2 first released to be unstable for some users though, I was not one of them.
[OnePlus 3 & 3T Cross Device Development] weeka89:
I'm not the one complaining
[OnePlus 3 & 3T Cross Device Development] Rawwrius01:
[MENTION=5438598]RenderBroken[/MENTION]

First thanks for your kernel.

I'm on f2fs cache only and got some problems with WhatsApp notify delay.

The messages only arrive when I open WhatsApp and wait a few seconds.

Eng.stk write something about that in one of his changelogs (see screenshot the last line) I think. Maybe you found a solution or have an answer for my problem.

Sorry for my English :D

I'm on freedomos 1.7 render kernel no mods cache f2fs.

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3 & 3T Cross Device Development] Jole7:
Neither do i
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Thanks! I will take a look. I have really enjoyed eng.stk's work for a long time now.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Let me know if you can test a new build for me. Or if anyone else is using F2FS and Whatsapp and knows what he is referring to.

Thanks guys!
[OnePlus 3 & 3T Cross Device Development] Rawwrius01:
Sure I would test [emoji14] but I'm only on cache f2fs the last time I tried data f2fs I soft bricked my phone :D

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
No, that is fine. I just want you to recreate the same issue you were having with F2FS and Whatsapp. Here is the test build:

OOS-R3-T1
[OnePlus 3 & 3T Cross Device Development] Rawwrius01:
Okay will report. It happens when I'm playing games or the phone is in standby. Better yet optimization is off for WhatsApp.

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
I guess for proper debugging of that issue, /data needs to be on f2fs. Not sure tho, I might be wrong.

Also, why are you in f2fs for cache partition only? It is most beneficial on /data more than anything else. /system may be arguable, but /cache is barely used and barely possess any read/write operations and if I remember correctly that was stated by eng.stk before repeatedly. Also stock OOS now uses f2fs only for /data and not /cache or /system.

Actually maybe switching /cache back to ext4 and only using f2fs for /data may solve your problem ;)
[OnePlus 3 & 3T Cross Device Development] Konskl:
[MENTION=5438598]RenderBroken[/MENTION] yo !!! R2 is awesome reallt smooth ;) btw I noticed that you changed the default i/o scheduler to fiops. I thought you preferred cfq mostly. Is fiops supposed to give better performance than cfq???
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Thanks for the kind words!

I like to change certain things up from time to time to make sure that the benefits I see are not placebo and that I am not developing inside an echo chamber. This is also why from time to time I like to try out other kernels. But I mostly run my own kernel.
[OnePlus 3 & 3T Cross Device Development] Durrz:
Thank you so much for your work [MENTION=5438598]RenderBroken[/MENTION]! Was able to achieve 1% idle drain for 7 hour sleep period.Best results I've ever gotten on a kernel. Will continue to test and update you on performance and battery :)
[OnePlus 3 & 3T Cross Device Development] ryshd296:
I am waiting for CM 14.1 kernel.

I want to use your kernel.

Is it released?
[OnePlus 3 & 3T Cross Device Development] calvinistmac:
For crying out loud!!!!! If it was released it would've been posted. Please read the original post before posting.
[OnePlus 3 & 3T Cross Device Development] kash296:
you want to use the kernel? great! you can use it on OOS. The dev clearly mentioned he'll take some time :P :) So give him time. In the end, you're benefitting from his hard work, remember that :)
[OnePlus 3 & 3T Cross Device Development] ryshd296:
Really it is!

I must thank you.

Thank you!
[OnePlus 3 & 3T Cross Device Development] Konskl:
That makes sense. Not sure about app opening speeds but fiops right now seems to be smoother in scrolling in chrome facebook instagram. Not sure if that used to be always the case but as per my usage it seems better right now. However I've got to point that your kernel is the first one where fiops is running than cfq. Not talking about synthetic benchmarks just real life usage. Again ty for your work. :)
[OnePlus 3 & 3T Cross Device Development] Rawwrius01:
The thing is that I soft bricked my phone the last time I tried data f2fs. I spend a whole day to restore my settings and data (slow internet+ some gigabyte music photos...) I haven't much time between study and work so it isn't easy for me to switch. Maybe I'll finde some time in the weekend. But I think I will wait for official nougat. It sounds much easier to switch then.

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
Fair enough. Great decision to wait for Nougat, since it will natively support f2fs :good:

---------- Post added at 09:41 AM ---------- Previous post was at 09:31 AM ----------

People with f2fs and using whatsapp, can you try to disable fsync and see if it fixes that for you?
[OnePlus 3 & 3T Cross Device Development] Jole7:
Fiops is the best according to my tests