yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] 7root:
Holy smokes, thank you so much. Please notify us when the work is done.
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
Game changers pop up every friggin day :cowboy:
[OnePlus 3 & 3T Cross Device Development] Scarface1991:
Will the next update fix this issue or not yet?

Btw best Kernel I tried yet if it wasn't for the camera "bug".
[OnePlus 3 & 3T Cross Device Development] stryker09:
Don't know how you're going to apply the patches for OOS on the ROM level... OOS is not OSS :(
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
I should have a pretty nice way to help performance issues on OOS based roms with very little trade off in battery. I actually think it may make battery better. This would be a cheap and easy way to get around the lack of EAS changes for OOS based roms.
[OnePlus 3 & 3T Cross Device Development] 7root:
What do you mean with "OSS"?
[OnePlus 3 & 3T Cross Device Development] Targaeryan:
Means not open source I would assume..

Tapatalk を使用して私の ONEPLUS A3003 から送信
[OnePlus 3 & 3T Cross Device Development] 7root:
They have a github: https://github.com/OnePlusOSS

OSS=Open Source Software
[OnePlus 3 & 3T Cross Device Development] Targaeryan:
Those are for device blobs/kernel sources.. They're not open source like aosp itself where you can download source code, change things/add features to it and compile a rom like LOS or PA.... The oos based roms are built off of full rom packages like the OB or official ones..

Source: I used to compile roms for n4 so I kinda know a thing or two..

Maybe if its not clear, someone else can this explain better..

Tapatalk を使用して私の ONEPLUS A3003 から送信
[OnePlus 3 & 3T Cross Device Development] abhibnl:
Does this mean a new experimental kernel for OOS roms?
[OnePlus 3 & 3T Cross Device Development] 7root:
Alright. Then I need to figure out how to add eas in another way. Thanks
[OnePlus 3 & 3T Cross Device Development] Targaeryan:
Np mate.. ? happy to help.. I would suggest to wait for what renderbroken has in store first for oos and go ahead after that ?

Tapatalk を使用して私の ONEPLUS A3003 から送信
[OnePlus 3 & 3T Cross Device Development] 7root:
Exactly what I had in mind!
[OnePlus 3 & 3T Cross Device Development] vibhoothiiaanand:
any support group or thread or google plus community for VERTEX OS .

BTW i have build successfully vertex OS for OP2.
[OnePlus 3 & 3T Cross Device Development] Targaeryan:
I think they're active in the AKT slack group.. I think you can find the link in the AKT thread in the discussions section..

Tapatalk を使用して私の ONEPLUS A3003 から送信
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
https://xdaforums.com/oneplus-3/one...zar-zenith-kernel-t3571781/page2#post71394841

a friendly heads-up, [MENTION=6745491]joshuous[/MENTION] now has his separate thread for his EAS ROM VertexOS

have fun :)
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
I am working on this still. Sorry to keep my OOS users waiting. I am trying to finalize my EAS changes for LOS since they will be carried over to OOS.
[OnePlus 3 & 3T Cross Device Development] Scarface1991:
Does it fix the problem with ROMs using the 7.1.1 camera blobs which resulted in camera crash?
[OnePlus 3 & 3T Cross Device Development] Targaeryan:
Should be.. He already mentioned its inline with LOS kernel..

Tapatalk を使用して私の ONEPLUS A3003 から送信
[OnePlus 3 & 3T Cross Device Development] ndarkside93:
I can confirm.

Working

With 7.1.1 blobs. Using it with vertex os and ob12 firmware and oos camera works great..

Edit. Google camera gives black screen, I'm assuming it's an HAL issue and not kernel
[OnePlus 3 & 3T Cross Device Development] Scarface1991:
Camera works but now the off screen gestures don't work anymore like the "draw a V fo activate flashlight".

Does your kernel support these gestures?

I'm on this ROM btw: https://xdaforums.com/oneplus-3/oneplus-3--3t-cross-device-development/rom-citrus-caf-t3505010
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Yea, those gestures work on the Vertex OS build I am on so it should work just fine for you.
[OnePlus 3 & 3T Cross Device Development] Scarface1991:
Ok that's weird, so I guess it's just a problem with the ROM then. After flashing the Render Kernel the menu "gestures" inside settings just disappeared and appeared again after I restored a backup of the stock kernel that came with the ROM.
[OnePlus 3 & 3T Cross Device Development] joshuous:
For gestures to work it requires both effort from ROM and kernel. Either one of them needs to implement a change to fix gestures. In my case, I fixed it ROM-side so that kernel devs don't need to change anything.
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
flashed R3 EAS LOS and everything is hokey-dokey :good:
[OnePlus 3 & 3T Cross Device Development] saberzaid:
Is the new version working with the oos beta 7.1.1
[OnePlus 3 & 3T Cross Device Development] 7root:
Probably not, since this is a LOS Version. OOS is not LOS and will not be compatible with a LOS kernel
[OnePlus 3 & 3T Cross Device Development] android extreme:
Hi [MENTION=5438598]RenderBroken[/MENTION] i've installed your HMP R3 LOS kernel on resurrection remix and all works well except for a thing: the cpu big cluster seems to be always offline. The issue start when i switch of the screen and after some minutes wake up the phone with double tap to wake. I've detected this issue with various app like cpuz and all tell to me that the big core seems offline. Is possible workaround this issue?

Hope the log attacked below will help you
[OnePlus 3 & 3T Cross Device Development] genuine55:
Hey guys does this kernel have the wakelocks disabled ? Thanks in advance RUNNING smooth by the way loving the kernel
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
It is not actually off. It is SELinux related where these apps fail to detect the big cluster. If you set SELinux to Permissive, you will immediately notice their presence in the apps you named.
[OnePlus 3 & 3T Cross Device Development] KforHorizon:
[MENTION=5438598]RenderBroken[/MENTION] just wanted to let you guys know.. after the addition of new EAS commits, the kernel goes back to 307 MHz with no problems at all. Keep up the good work. Cheers!!
[OnePlus 3 & 3T Cross Device Development] Pritster5:
Does the OOS EAS kernel work on OOS 4.1 that was released recently?
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
I think some minor ones are disabled by default but there are alot more that I give you the ability to turn off but are not turned off by default.

No, the OOS kernel is way outdated and will have to be redone completely.
[OnePlus 3 & 3T Cross Device Development] Pritster5:
Is there an ETA on the OOS kernel rework?
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
The Dev is working on a very big thing now, so as soon as this gets done, OOS kernel will be updated accordingly
[OnePlus 3 & 3T Cross Device Development] Pritster5:
Are you allowed to tell us what this very big thing is? Pretty Please?:p
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
I will leave that to [MENTION=5438598]RenderBroken[/MENTION]
[OnePlus 3 & 3T Cross Device Development] TotallyAnxious:
New batmobile? Sorry couldn't help myself lol
[OnePlus 3 & 3T Cross Device Development] Evokkimus:
Hey can anyone explain what Darknesssched has to offer? Alucard seems to be more for performance.
[OnePlus 3 & 3T Cross Device Development] joshuous:
I'll try to write something this week
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
Yes indeed your kernel seems to make the CPU have another thought before moving up the min freq when doing something like reading. Even with my utmost peak performance aiming set of tweaks, it still idles unbelievably well! Just slapped on my brand new Burnout_Extreme set of tweaks, and strapped on my seatbelts in my Mustang GT :cowboy:

And you telling me EAS handles sleep differently eh? Well that relates as well. Will keep the T47 rolling for a day or two and see how it goes, before hopping back in the steam train of EAS. :good:
[OnePlus 3 & 3T Cross Device Development] habylab:
Oh okay! Well the only issue I have are RR, so looks like I won't be much help. I hope it stays there next time so I can provide stats. When my phone won't wake up, the LED flashes like it is ready to wake up.

Edit: noticed the kernel version info hasn't been updated, says it was built on Wednesday 23rd? Did you build today's build then, or just didn't update that info?
[OnePlus 3 & 3T Cross Device Development] chinmai560621:
Can you support sdcardfs on f2fs for the data partition???! It's said to have a great effect. And can you try to look into arter97's kernel sources? It loads apps really faster than on any kernel.

Btw amazing battery life, reached 6 hr SOT!! Actually this kernel is one of the best ones out there, and so soon..
[OnePlus 3 & 3T Cross Device Development] XpellCZ:
Thanks for your great work!

What are features of your Non-EAS kernel? I know it supports F2Fs, but does it support sRGB?

Thanks for answer.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Yes it supports it.
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
Alright i hopped back to the EAS train. Here is a showdown based on the initial impressions:

1- idle drain reports a net current draw of ~70 mA most of the time and sometimes ~100 while the non-EAS kernel of yours used to report ~30 mA

2- Active drain is a bit inconsistent in sched, sometimes as low as ~150 mA and sometimes ~300 mA.

3- Cannot spot a pattern of the Frequencies used, very inconsistent as well.

4- sched seems to like CFQ so much

5- App launches are also inconsistent, verrrrry inconsistent. Sometimes exquisitely fast and sometimes a bit slow....

Schedtune_boost =8

UPDATE: it seems that it takes a longer while to reach the same idle drain rate. Left it for 30 minutes and it is now reporting 32 mA.

6- it seems that sched seems to favour the big cluster, it is most of the time working while little cluster is using lower freqs if not idling. I guess Google wanted to utilise its gold mines under hand; we both know that the big cores of the S820/S821 are golden, however, they are not as responsive to latency-sensitive tasks as the little ones (i tested that before with my Shotgun_v1.7+ profiles of interactive governor settings and then decided to retreat with the final v1.7.6) and that relates to the observed lower responsiveness. I guess tuning top-app will cure that. And since the sched_tweaks settings are pulled, there is almost nothing I can play with unlike your non-EAS kernel with interactive governor. And that may explain the inconsistent active drain (even while typing, the current draw jumps from as low as ~230 mA to as high as ~550 mA)

UPDATE 2: Big cluster most of the time uses the intermediate frequency steps and is a bit conservative in ramping up to higher freqs than 1555 MHz. Little cluster also maintains same behaviour except that it uses even lower freqs like 480 MHz, 652 MHz and such, and is a bit conservative ramping up the freqs above 1190 MHz, unless you tune up the gobal schedtune.boost value to higher than 10.

Hope I helped!
[OnePlus 3 & 3T Cross Device Development] Puddi_Puddin:
[MENTION=5438598]RenderBroken[/MENTION], haven't had a reboot since yesterday 6pm (it's now 9.45am) all night it was fine as well. First I thought the reboots where gone because of that I toggled off gestures while I had reboots the whole day but just not after I toggled it off Just when I went outside away from my WiFi my phone rebooted again..
[OnePlus 3 & 3T Cross Device Development] habylab:
Good insight! Wow, that schedtune is low. I set mine to 16 and was having massive issues with RR.
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
Just updated my post with more info/observations. Will keep updating it to gather all observations in one single post and keep it intact. :good:

Happy helping the community as always :)
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Hella Great info here! Some thoughts I have:

1. Yes, performance is inconsistent and I hope that fixing the proper use for TOP-APP will fix that. Right now, ALL tasks are boosted along with top app, so this means background, foreground, and system-background are all being boosted. This is the case because when the global boost is not in use, you have a bigger issue with performance.

2. For deep sleep, see #1 lol. Sleep is not working 100% either. Something is causing an issue and thus the RRs.

3. I really need those files I posted a few posts back from a Cyanogenmod rom. Or, I may just try to compile them myself.

I would just use my non-eas build I linked a few posts back in the meantime if you want a truly rock solid performer. depending on how the next few builds go, I may drop EAS all together ans just release special builds from time to time for the tinkerers out there.
[OnePlus 3 & 3T Cross Device Development] habylab:
I'd love to see EAS given some more love and become more stable - I'm sure it can be. Seems like a great idea!
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
No no no EAS kernel seems quite solid here. And if top-app is utilised, it is done! It gets a lot of credits for efficiency most of the time.

Anyways, I might revert back to non-EAS kernel, need to retune Interactive governor profile of mine.
[OnePlus 3 & 3T Cross Device Development] kalapapa:
I tried to find them but I could not find the exact ones listed. I would find some with similar names but I don't know if you want them

For example instead of libutil.so, I found libutils.so

Instead of power.qcom.so, I found power.default.so

Is this what you were looking for?
[OnePlus 3 & 3T Cross Device Development] tathagatab:
Right now I have 12 hours and 38 minutes of uptime since last unplugged, including 3 hours and 43 minutes of SoT, and 46% battery remaining.

FreedomOS 1.6.1 + EX kernel 0.28 + [MENTION=6187429]Asiier[/MENTION] 's XANA (battery-oriented) profile + Greenify.

All the time either on WiFi or LTE, with gps turned on occasionally. Youtube, light gaming, WhatsApp, MX Player, browsing (Firefox), talking, texting, some navigation using Google Maps. Screen brightness approx 50%.
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
I wont drop it. Just keep it as a side project.

No worries, I will just compile them myself.

Nice! My stats where just straight stock. Interactive, and cpu-boost, etc. No battery oriented changes. How bright do you keep your screen?

Also I have the final R1 Test build here and it will be a non-EAS build til I can get the binaries I need for EAS. I need to have ppl confirm that this build is solid before final release.

Thanks guys!

R1-T48-Non-EAS

Commit history
[OnePlus 3 & 3T Cross Device Development] gleggie:
How do I setup EAS? Would like to try this on OOS 3.2.8

Can I use EXKM?
[OnePlus 3 & 3T Cross Device Development] tathagatab:
50% or lower indoors, occasionally higher outdoors. Exact values determined by cf.lumen.
[OnePlus 3 & 3T Cross Device Development] njunxuan:
How great is the battery difference between the EAS and non-EAS. Has anyone tested both?
[OnePlus 3 & 3T Cross Device Development] Puddi_Puddin:
For the performance big, once EAS gets somewhat stable and optimized it will be awesome!
[OnePlus 3 & 3T Cross Device Development] njunxuan:
haha I'm using the EAS version now!! really enjoying the speed but still has occasional crashes
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
It is basically schedutil but with a boost tuneable to boost the detected load/util so that the system feels it is having more load than what is actually detected. It is like a foolish act to force the CPU to use a higher freq than the calculated one. [MENTION=6745491]joshuous[/MENTION] to confirm of course :)
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
sort of :cowboy:
[OnePlus 3 & 3T Cross Device Development] iaa85:
[MENTION=5060769]Mostafa Wael[/MENTION] good to see you here again, you helped a lot to make some profiles on boeffla kernel on oneplus two. Make me learn a lot!!!

Iaa85 from Brazil with Oneplus 3t

Powered by Phoenix Aex Rom
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
Of course I remember you and milestone2mod ;)
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
RK-LOS-N-HMP-R4 is HERE!!!

Things to note:

Updated Inline with LOS

Fixes WIFI issues

Adjusted default settings for more efficient input boosting.

Download

Changelog:

R4:

423a224 (HEAD -> rk-los-n-hmp-master, rk-los-n-hmp-r4-t1) power: oneplus_fastcg: Silence log spam

ad137b6 misc: Sync with OxygenOS 4.1.0 kernel release

54e93bb mdss: livedisplay: Fix memory leaks in mdss_livedisplay_update()

84155db (origin/rk-los-n-hmp-r4-t1) qcacld-2.0: Update to LA.UM.5.5.r1-03800-8x96.0

2fd238e Merge 86a83c93bfc72bf9d99314ff4e56642b8730f803 on remote branch

PS:

I am sorry for the lack of OOS support. I have been working on EAS pretty actively with [MENTION=6745491]joshuous[/MENTION] . We have been working to bring something completely new to Android and OP3(T). And I enjoy working on this project. This makes it hard to break off and start something new like OOS. I will work to get OOS builds out asap. You all understand that I do this work for myself, but I love to share what I do to you all. I love to share what I have learned to anyone that has a question of me. Thank you guys for your patience and allowing me to pursue the things that I am interested in. I have the best users on XDA!
[OnePlus 3 & 3T Cross Device Development] kscjx:
I just tried to flash R4 and I got an error. On the other hand R3 flashes fine without any issues. I'm on twrp 3.4.0.1 and 4.1.0 firmware.
[OnePlus 3 & 3T Cross Device Development] lapapunk:
something went wrong on your side! have same configuration as you, and on my side all good!
[OnePlus 3 & 3T Cross Device Development] kscjx:
I just found out the problem. It was a bad download. Redownloaded and its all good now. Thanks
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Thanks for letting us know! I wish more ppl that reported issues would report back when they have fixed it. Take care!
[OnePlus 3 & 3T Cross Device Development] keaheng:
I can't see new commits on github. The last one is on Mar 13, 2017
[OnePlus 3 & 3T Cross Device Development] evanxyj:
Will there be an EAS update???
[OnePlus 3 & 3T Cross Device Development] A Sad Napkin:
He already said there's a surprise coming. Don't ask for ETAs.
[OnePlus 3 & 3T Cross Device Development] Freak07:
You have to look at the right branch
[OnePlus 3 & 3T Cross Device Development] azzio4675:
which is the best between eas and hmp?
[OnePlus 3 & 3T Cross Device Development] ndarkside93:
Depends on your usage. EAS has improved but is more experimental. Better battery life at the expense of performance but getting better. He's spending a lot of time on it and the latest test build works for 99% of people quite well. Hmp is more mature and performs very well with lower battery life. It's up to you which trade off you want to make.
[OnePlus 3 & 3T Cross Device Development] azzio4675:
where can i found the test build?

---------- Post added at 09:44 PM ---------- Previous post was at 09:36 PM ----------

where can i found the test build?
[OnePlus 3 & 3T Cross Device Development] ndarkside93:
deletes
[OnePlus 3 & 3T Cross Device Development] azzio4675:
ok
[OnePlus 3 & 3T Cross Device Development] Pritster5:
Originally Posted by RenderBroken

Walt should be more aggressive :

https://drive.google.com/file/d/0B-G...w?usp=drivesdk

PELT is more conservative. This is what I am using and performance is great

https://drive.google.com/file/d/0B-G...w?usp=drivesdk

These are only for the latest test build (3/28) please feel free to report here or my thread about your experience. This is work that will be part of vertex as well. It is also a no frills build. No special features. Once done with eas base, then we can look into adding features.

Right here!
[OnePlus 3 & 3T Cross Device Development] neng24:
sorry for the noob question. will this also work on OP3T?
[OnePlus 3 & 3T Cross Device Development] keaheng:
Both link not working
[OnePlus 3 & 3T Cross Device Development] Pritster5:
Try this: https://drive.google.com/file/d/0B-GVJKBx9-GnU1BaMzI5dzl3LTA/view
[OnePlus 3 & 3T Cross Device Development] keaheng:
Thanks
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Please don't. These test build ONLY work with a certain other test build that has also not be released publically. I imagine that flashing my test builds on anything, other than what it was intended, ran like hammered dog crap.

I appreciate that you are trying to help though. Just there is a reason why builds are posted in slack and not here.

On this note. I have a new EAS build incoming. I can safely say that EAS now out performs HMP by a noticeable margin. This is not an exaggeration. This is not a boast. This is 100% legit and it ill blow you away. I will be moving from HMP as my Daily driver build for work and such (I work in IT so on the phone all the time) to EAS only.You will notice rom builds for EAS out there will be using the EAS base I have created and it will blow you away. I will be releasing my stand alone build asap. I think that I have reached a major milestone with EAS on my LOS branch and will be taking all my work to OOS. WIth my OOS kernel, I will be including a modified CPU-Boost driver that should imitate the input boosting occurring through the PowerHal on the EAS based roms. I am certain that OOS users should be able to achieve at or near the same level of performance I am reaching with LOS based EAS. Once again, I state, this is not an exaggeration. This is the moment we have been working towards, [MENTION=6745491]joshuous[/MENTION] on the Rom side, Myself on the Kernel side, we have truly reached a milestone.
[OnePlus 3 & 3T Cross Device Development] Konskl:
I suppose you wanted to say that EAS outperforms HMP by a noticeable margin :P i suppose that's just a typo. My question is when you mean outperforms HMP you mean in every scenario? Be it Performance or battery??? Really eager to find out ;) if there's any link for test version to get a taste I'd really want to try it out. Or else I'm just going to patiently wait for the final release ;)
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
lol yea, thank bro!
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
I would say that for my use pattern as a power user (Bluetooth, Listening to audiobooks and music all day, wifi connected 100% of the time with LTE, stock brightness, no greenify or naptime) I am able to get AT or higher SOT I normally get with HMP and it is way smoother. I promise you guys, its insane. I will release a test build that should even work on stock LOS. For those on LOS, please let me know how this test build work for you, I am really interested. This build will work best for roms made for EAS though.

But you guys tell me:

PELT (Should have better batterylife)

RenderKernel-OP3-LOS-N-EAS-R4-T51-STUNE-PELT.zip

WALT (Should be more interactive and responsive)

RenderKernel-OP3-LOS-N-EAS-R4-T52-STUNE-WALT.zip (Yes, that is the 52st test build)

Benchmark Screens

With PELT (More battery friendly IMO):

[IMG="PELT"]https://i.imgur.com/Romk1iD.png[/IMG]

This was with my WALT Build:

[IMG="WALT"]http://i.imgur.com/i0XzCIj.png[/IMG]
[OnePlus 3 & 3T Cross Device Development] Targaeryan:
Your test builds worked like a charm on aex eas build by siankatabg. Just thought you should know that it didn't run like hammered dog crap.. Running the pelt version.. Perf is good as well as battery! Nice werk.!
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Sweet thanks! Also "hammered dog crap" is trademarked. ;) Back when I used to build houses to pay my way through college, I had someone working for me that said that and it stuck with me lol.
[OnePlus 3 & 3T Cross Device Development] Targaeryan:
Nice!? I'll put a (tm) with it the next time I use it ?

I'm on 4hours plus sot with 40% left ? that's insane..

I think I'm gonna try walt next to see the difference!
[OnePlus 3 & 3T Cross Device Development] RenderBroken:
Hows that performance though?
[OnePlus 3 & 3T Cross Device Development] Antsu:
[MENTION=5438598]RenderBroken[/MENTION]

Are these test builds applicable to the latest VertexOS test build?