yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] mysky911:
We really enjoying your work too :D

[MENTION=5438598]RenderBroken[/MENTION] ,not sure we can flash this latest Touchscreen firmware from 3T ROM OOS 3.5.3. on Render Kernel R2?

http://xdaforums.com/showpost.php?p=69792046&postcount=1870 :cowboy:
[OnePlus 3 & 3T Cross Device Development] Konskl:
I think i noticed the same as well... Most of the times cfq used to be the best but i guess due to the optimisations in the render kernel fiops turns out to be better. Btw have you done a discomark test? If yes, which read-ahead value gave you the best scores?
[OnePlus 3 & 3T Cross Device Development] Jole7:
No i haven't try diskomark yet but ultimate read and write speeds comes out with Fiops and benchmarking readahed i say 4096 or higher.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
I have no idea. I have not had any issues with touchscreen problems so I haven't had to mess with such things. What kind of problems are you having?
[OnePlus 3 & 3T Cross Device Development] mysky911:
My understanding, Oneplus 3T updated touchscreen firmware to have faster touchscreen latency.

eng.stk ported to his kernel with firmware flashable zip. :)
[OnePlus 3 & 3T Cross Device Development] Stroky:
I did a test with diskomark and for me the fastest app opening where with a size of 128
[OnePlus 3 & 3T Cross Device Development] Jole7:
[MENTION=5438598]RenderBroken[/MENTION]
[OnePlus 3 & 3T Cross Device Development] aymahalawa:
Thanks for your great kernel, but i noticed that switching between recent apps will relaunch the app .

Even if i have only 3 apps opened

I am not running any kernel tuner apps , just flashed the zip over the stock

Edit : Only xda lab problem , the kernel is found not guilty :victory:

Great Work ?
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Thanks for reporting back the cause!
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Hey guys,

I am going to need some Testers for F2FS changes I have made. I have updated F2FS heavily. Please PM me if you are willing to test thoroughly. Thanks guys!

Things I have done so far:

Reset SDCARDFS and brought inline with CAF/Google instead of Samsung

Updated F2FS
[OnePlus 3 & 3T Cross Device Development] juginkrebs:
[MENTION=5438598]RenderBroken[/MENTION] I send you a PM

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3 & 3T Cross Device Development] Durrz:
Hi [MENTION=5438598]RenderBroken[/MENTION] I'm willing to convert to F2fs if you think it will be highly beneficial. Could you enumerate some benefits?
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
REally only converting /data would have any benefit. But you will need to make sure to backup everything onto a computer. This way you can just copy all your user data back when converted. Also, you will need to make sure from then on that the kernel or built in kernel from a rom will support F2FS. Or you will have boot issues.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
So I have been taking a small break. If anyone has been following my github you would see that I dev constantly. I was undecided about starting my CM14.1 kernel so I was working on finishing R3 up. I have finally decided that I want to go ahead and do a kernel based on CM14.1. I am planning on starting this either today or tomorrow. This means I should be releasing OOS-R3 around then as well.

Just wanted to give a heads up.
[OnePlus 3 & 3T Cross Device Development] Jole7:
That's awesome news i can't wait for the CM 14.1 kernel good work!

p.s give us the extra overclock steps too lol....
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
Just in time, rolling back to OOS :)

Waiting for the next R as always :highfive:

Oh and you better finish quickly before your laws come back home :D
[OnePlus 3 & 3T Cross Device Development] Puddi_Puddin:
:good: im waiting! You
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
[MENTION=5438598]RenderBroken[/MENTION] looks like your kernel won't see the CM tag after all ;)

Enjoying R2 on OOS 3.2.7
[OnePlus 3 & 3T Cross Device Development] habylab:
How so?
[OnePlus 3 & 3T Cross Device Development] kash296:
In the sense no more CM. :P If anything it'll be a kernel of Lineage XD Still, highly unlikely we'll see anything non-OOS at the moment from most devs.
[OnePlus 3 & 3T Cross Device Development] habylab:
I haven't been following this really, but I'm glad it's happened. I think CM had become stale.

I'm just surprised the business part of the company has brought down the community part with it... That has a huge history.

It's a shame there isn't another big community developed ROM, that innovative, to take over as the big leader. Slim, Omni all seem quiet these days.
[OnePlus 3 & 3T Cross Device Development] kash296:
Long way to go to be honest. Just gotta hope for the best with that.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Yea, its really sad that CM has been killed off. CM has been a staple of Android communities for a long time. Hers hoping that Lineage takes off and becomes a truly community driven projects that we all want it to be.

On another note, I have taken a small break from everything and are now coming back to Finish off R3. Alot of changes are incoming. I have updated F2FS heavily to be inline with CM and official Jaegeuk Kim source. Updated SDCARDFS to be inline with LA.UM.5.5 CAF. And many other small changes and updates.

I am testing this new build and will release if I am happy and it means RenderKernel Standards.

I am not sure what to do about the CM Kernel and will wait to see what Lineage will become.
[OnePlus 3 & 3T Cross Device Development] vinax89:
Wow, looking at your recent commits, I know you've been busy this past few weeks [MENTION=5438598]RenderBroken[/MENTION]
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Heck yea. I really dev all the time. I just test and I was about to release but was having an issue with up time. I was getting great performance but at about the 6th or 8th consecutive day, there would be a random reboot. I am pretty certain I have resolve the lock ups though so I will push out this latest build today for OOS-MM. I could continue to add more and more changes to it but need to stop at some point. I feel pretty happy about its current state. Since OOS-N source has not dropped yet, I will begin work on a new kernel for Lineage-N immediately.
[OnePlus 3 & 3T Cross Device Development] yung40oz84:
Sweet! That;s what I am awaiting custom kernel and I guess you will be adding the new stuff for f2fs to work with superSU?
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Of course! lol That was a great help from Arter.
[OnePlus 3 & 3T Cross Device Development] yung40oz84:
Sure was! Thanks!
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
since i knew the cause of the random issue of my CPUs locked at max freq, I am rolling back to OOS 3.2.7 (again) :D
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
What was the cause?
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
Facebook and its useless companion app Messenger were the causes. Confirmed by arter97 (check his twitter) and a facebook employee even declared it and briefly explained the cause in a tweet as well.

P.S. it is a server side related to a certain ad service, and it appears that, as per a lot of other users, the issue has been fixed. Still, I won't bear any more facebook till I feel the definite need for it.
[OnePlus 3 & 3T Cross Device Development] Durrz:
I'm hyped! Hope I get to flash this today :)
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Guys, I dun goofed. I have been sick the past couple days lol. I accidentally built R3 with the wrong, older toolchain. It was build with a 4.9.3 toolchain when I have setup my source to be built with 6.2.1. So with that, I am going to rebuild R3 and call it R3-Final. Sorry for the inconvenience. I am just a perfectionist when it comes to my releases and that may be why it takes so long for me to test. I had updated the download link in the above post.
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
I was about to report it is up and running here on OOS 3.2.7

looks like i have a redownload in order :)

Still it is blazing fast :good:
[OnePlus 3 & 3T Cross Device Development] vinax89:
Is there supposed to be a CPU hotplug? In kernel adiutor the category shows up. Thank you and hope you get well soo [MENTION=5438598]RenderBroken[/MENTION]!
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
I am guessing because core_ctrl is enabled but the parameters are all zeroed, same way as stock OOS
[OnePlus 3 & 3T Cross Device Development] vinax89:
No interface even in CPU hotplug section at Kernel Adiutor.
[OnePlus 3 & 3T Cross Device Development] Konskl:
[MENTION=5438598]RenderBroken[/MENTION] any plans to make a LOS kernel???
[OnePlus 3 & 3T Cross Device Development] kash296:
Yes. He mentioned that a few posts back, or in the previous page. Not sure.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Yes, it is incoming. I have already started work on it. I am just waiting for a good time to make the jump to the right N/LOS based rom. I have alot of data I need to backup and such.
[OnePlus 3 & 3T Cross Device Development] yung40oz84:
I cannot take the anticipation, lol
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Yea, I have finally been able to make the jump to Official LOS yesterday. I am running stock kernel at the moment just to get a feel of what is normal so when I start testing my kernel I can get an objective view of the performance to compare to. Hopefully I can get some test builds going today.
[OnePlus 3 & 3T Cross Device Development] comediiian:
hope you develop better and faster, then you play Battlefield...

:D :D :D
[OnePlus 3 & 3T Cross Device Development] yung40oz84:
This would be outstanding!!!!
[OnePlus 3 & 3T Cross Device Development] showofdeth:
Already have ElementalX installed and more than happy with it. What does this kernel offer over others?
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Hard to say for sure but I have most of the features that ElementalX has but I also like to make more changes to the scheduler to work more efficiently. I also like to keep certain subsystems in line with CAF. You would need to look at my source code compared to his.

I like Elemental since it makes small necessary changes. I try to keep things minimal as much as possible but like to update certain things via CAF, Linaro, and Google commits. This is why I test for so long. I could release a new build all the time that has small incremental changes but I like to release proper updates that have been vetted to be stable.

But like I said, I really like Elemental so you cant go wrong there.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
lol Whatever!

https://battlefieldtracker.com/bf1/profile/pc/renderbroken
[OnePlus 3 & 3T Cross Device Development] comediiian:
hahaha :D :D

nice SPM btw :D
[OnePlus 3 & 3T Cross Device Development] Jole7:
Lol
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Well, now that kernel source has dropped officially. I will need to figure out where I want to go from here. I really want to continue with LOS so I will give them time to update binaries and such for N and I will continue with my first N kernel for it. After my first build for LOS, I will do an updated Build for OOS once it settles down abit.
[OnePlus 3 & 3T Cross Device Development] yung40oz84:
I need render! lol
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
I KNOW! I am ready to start building but with the new source drops, everything changes. I don't want to start building Render for LOS and then have to start over for a second time. Main thing I see being done is for LOS, the maintainer would need to overlay LOS ontop the new OOS Source. But there are a ton of commits that are going to be duplicates since Official OOS looks to be based on LA.UM.5.5 (If I remember right) and CM14 was pulling alot from that branch. So the will need to a complete bringup to do it proper. I thought about going ahead and doing it myself but It may be completely different from LOS source in the end and that would mean way more work for me. So its hard to find a starting point.
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
Take your time and see what suits you, you know we all will be waiting for you any time once you raise the checkered box flag ;)
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
I think I am going to move to Freedom OS 2.2. I was on [MENTION=5767887]NevaX1[/MENTION] 's M based Rom and loved it. The added features on top of a great stock experience made it so that flashing a custom rom was not necessary. Especially when the stock kernel is based on CAF like it is. Back when I was deving for LG and such, their Stock kernels were so drastically different from CM's clean source that there was a big difference in performance and such. With the OP3, that gap has been easily closed. I am planning on moving ahead with a new Stock N based build while waiting for LOS to rebase their N based kernel.

Sorry for the wait LOS Guys.
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
Sounds about time to move back to OOS, but this time I will be using OOS N instead ;)

Also, would you mind checking your PM on your slack group(s) :)
[OnePlus 3 & 3T Cross Device Development] njunxuan:
I was wondering if work is still being done on the EAC branch! Was really excited to see the potential battery optimisations :)
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
I will not be working on EAS just yet. I will first do a build for Stock N. Then most likely do another build for LOS once they are done rebasing. Then after all of that, I may work on a new project all together. EAS needs Rom side changes to be fully supported and working properly. So I will try to just build a Rom and Kernel from LOS Source just for EAS. Hopefully, I can get the ball rolling for other Rom Devs to add support for EAS. I am hoping it catches on and others take up the torch. This is my goal.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
OOS-N-R1 is HERE!!!

Download

Things to note:

Has most if not all major features

Does NOT have Overclocking - Still deciding the best path to take

You really need to see the changelog below for details. There are many changes made.

But people know me by now and know that I shoot for stability and performance over bleeding edge commits. I tend to track CAF on most major subsystems.

Changelog:

HERE

PS: I am now going to work on a new project for Stock N and may need testers. I am really excited to see where it goes.
[OnePlus 3 & 3T Cross Device Development] vinax89:
Thank you for the release! I am eager to try your LOS and your new project by the way. :good:
[OnePlus 3 & 3T Cross Device Development] drdexter1989:
I'll give a try to your kernel and leave feedback soon.
[OnePlus 3 & 3T Cross Device Development] calvinistmac:
Looking forward to giving this a shot!
[OnePlus 3 & 3T Cross Device Development] drdexter1989:
I'm getting amazing battery life with this kernel + AKT ZHANA profile. Thanks you
[OnePlus 3 & 3T Cross Device Development] Durrz:
Any chance of getting a backlight dimmer option for the kernel?
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
LOL, it was there. Must have missed it when I did the final rebuild for R1. I will add it back in.

Currently working on EAS. For those interested, check out my github.
[OnePlus 3 & 3T Cross Device Development] Rawwrius01:
You are the best :D will the EAS Rom based on oos or lineage ?

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
I wanted to tease that! :D

Keep it rolling, you're the MVP :victory:
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
Get ready.

It's about time...

#BraceYourselves #EAS #NextIsNow

:cowboy:
[OnePlus 3 & 3T Cross Device Development] Rawwrius01:
Need it !

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
EAS for OOS-N is here!!!

Not sure where you put this build or how to label is but here we go. I have been working hard to create a build of EAS for Stock N. I was looking through the different source files for OOS-N and noticed that there were still some pieces of EAS left in. So I decided to try out EAS again. I have been working on getting EAS from Google to merge into out Stock Source. I am VERY happy with the results. Please flash at your own risk but I am certain that as long as you are on an OOS-N based rom, you should be just fine. I also believe that EAS is now ready as a daily driver and that the performance I get with it is comparable (finally) to Stock N as I was getting the same discomark times and other tests I had done performed beautiful.

Download

things to note:

Its EAS from Google Pixel, what more is there to know! Check Source link below for more details.

Source Link
[OnePlus 3 & 3T Cross Device Development] vinax89:
Oh my goodness! I think I shat my pants :good::good::good:
[OnePlus 3 & 3T Cross Device Development] peshellas:
Amazing work mate, can't wait for Mostafa to create a Kernel profile built with eas in mind. :fingers-crossed:
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Its harder to do since with EAS you use schedutil as the governor and there inst hardly anything to tweak there.
[OnePlus 3 & 3T Cross Device Development] vinax89:
Thank you [MENTION=5438598]RenderBroken[/MENTION]! Are there any pieces of code that we can manipulate to turn into switches to "tweak" the kernel behavior?
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Still mainly limited to allow the scheduler to decide the best frequency and voltage to use per given task. You can adjust the schedtune.boost value though. I dont have enough time to explain this further right now but its set to 12 for /dev/stune/top-app/schedtune.boost

You can bump this up but the more you bump it up, the harder it will be to get to idle.
[OnePlus 3 & 3T Cross Device Development] vatsal8286:
What is the benifit of EAS?

And my phone getting too hot after flashing EAS bulid...
[OnePlus 3 & 3T Cross Device Development] Puddi_Puddin:
U can Google it, also if you flash it look at your Cpu frequencies. Main benefits is a overal smoother experience with max battery efficiency.
[OnePlus 3 & 3T Cross Device Development] Konskl:
How to flash the eas kernel if I'm already in blu_spark? If someone's kind enough to tell me step by step I'd greatly appreciate it :)
[OnePlus 3 & 3T Cross Device Development] svandasek:
Hello OP, is it compatible with the 3T too? Or do you plan to make it unified?
[OnePlus 3 & 3T Cross Device Development] madsponge26:
Dirty flashed the rom after that flash this kernel.
[OnePlus 3 & 3T Cross Device Development] vatsal8286:
Cpu uses max freqncy all the time...batrery draining so quickly...phone is getting hot..where am i wrong?
[OnePlus 3 & 3T Cross Device Development] vatsal8286:
Also look at this....:crying:
[OnePlus 3 & 3T Cross Device Development] Puddi_Puddin:
Flash = Profit. Take a backup of system and boot since the kernel modifies it. Then you'll always have a backup!

Interesting.. Is this Experience rom?
[OnePlus 3 & 3T Cross Device Development] vatsal8286:
Yup..experiance rom 10.1!

What should i do?
[OnePlus 3 & 3T Cross Device Development] Puddi_Puddin:
I've encountered this on different kernels as well. My experience is that Experience rom doesn't like other kernels too much, it's really strange. I do recommend you to try Freedom OS.

You could try out this https://xdaforums.com/oneplus-3/how-to/potential-fix-cpu-battery-drain-aosp-t3543369 not sure if it works, haven't tried it!
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
EAS (specially when considering that we are using the schedutil governor) has mind of its own, and there isn't much to fiddle with :)

I flashed the kernel (of course :D ) and i am analysing it. So far, it is very very impressive!

A hell of thanks to [MENTION=5438598]RenderBroken[/MENTION] :)
[OnePlus 3 & 3T Cross Device Development] vatsal8286:
Look at this...:crying:
[OnePlus 3 & 3T Cross Device Development] manjartens:
Had the same problem. I flashed supersu stable 2.79

, reboot and No more heat. Hope i could help.
[OnePlus 3 & 3T Cross Device Development] candiesdoodle:
Let it settle down buddy. U have been on it for like 13 mins.

Give it a couple of hours
[OnePlus 3 & 3T Cross Device Development] DespairFactor:
Custom ROMs may cause issues with WiFi, not sure how he is loading the module, I know on CM in previous OP devices we needed to compile the qcacld driver inline for it to work properly.
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
This sounds incredible! Will do what it takes to test that Kernel !! EAS for OP3, that is very incredible!! I am just speechless, can't say how exhilarated I am just to flash that kernel. Shame i am on Nougat and have to charge and flash OOS, would like to just flash it now. I am on it!!

Thanks Thanks....million of thanks! :good::good::good:
[OnePlus 3 & 3T Cross Device Development] Jole7:
Render kernel is here great news many thanks man
[OnePlus 3 & 3T Cross Device Development] abhibnl:
Welcome to op3 forum Render. Looking forward to try this baby out soon.
[OnePlus 3 & 3T Cross Device Development] ZeNiXxX:
[MENTION=5438598]RenderBroken[/MENTION]

wow nice to see you here in the oneplus 3 world. I was always using your kernel on my lg g2. Cant wait to see your magic happen to cm-kernel :)
[OnePlus 3 & 3T Cross Device Development] NOSTALGIA:
im so late but welcome [MENTION=5438598]RenderBroken[/MENTION]
[OnePlus 3 & 3T Cross Device Development] 1337jay:
Wooah, yet another great developer for this awesome device!

Thanks for doing this, [MENTION=5438598]RenderBroken[/MENTION].
[OnePlus 3 & 3T Cross Device Development] =dave=:
Looks very promising.

Testing it for the last hour now and what I can say so far:

1) seems very smooth

2) when the device is idling, little cores rarely dip below 556 MHz, BIG cores rarely below 883 MHz, even sometimes occasional jumps all the way up to 2150 MHz
[OnePlus 3 & 3T Cross Device Development] tmimaesk:
Yea I lowered the schedtuneboost to 8 and now it enters 307 mHz.. default was 20
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
SUPER POST!!!

Yea, EAS is what I was looking for as well.

1. Did you look here for the log: /sys/fs/pstore/console-ramoops ? This is the only one that will survive a reboot.

2. Sorry, I had it set higher for testing. I needed to see that it was working. Setting stune like this should help:

/dev/stune/schedtune.boost to 10.

Remember, this boosts the minimum frequency to use per task by 10%. So this also means that you will not be getting 307MHz while doing any task, other than idle I should say. I have set another tunable:

/dev/stune/schedtune.prefer_idle to 1 to enable

Oh, you didnt know? This is only for Froyo. yea, sorry bout that.

Thanks for the heads up!

I think settings to 10 will be a daily driver. I am still working on this though. I have setup cpusets, meaning that I can set tasks per core, etc. I am working on setting the top-app tasks as the only ones that get boosted while letting foreground and background tasks not be boosted at all. I have just not found a way to do so yet. CM uses a binary to handle setting and mirroring cpuset/top-app to stune/top-app. Its not easy to implement something and inject via kernel. Still, I feel that I can figure it out.
[OnePlus 3 & 3T Cross Device Development] =dave=:
thank you for your hard work! devs like you, with such a drive to deliver real progress, is what keeps this community alive!