yashsingh1/xdaforums huggingface dataset:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Everything is linked against the overwritten source build version, since the copy directive does NOT generate any intermediates, which are needed to link against.

This is not only more reliable, but ensures the modules are NOT build from source and everything needed for linking is in place - this breaks extract-files because of the LOCAL_EXPORT_C_INCLUDE_DIR, which needs to be set manually:

https://github.com/nvertigo/proprie...mmit/ac310738409bfdd35c2dbcf6f650dcec25bed6e1

https://github.com/nvertigo/android_frameworks_av/commit/14a6aa0e0d95fa4ca8731c83909cebbf0d2f8e0d

https://github.com/nvertigo/android...mmit/2fa744162b35fa111aefc3c6ed56c07d61351b08

For me this does work the same as our implementation + our implementation does not break op5 cam. Since I don't like splitting one package (framework/av) into a source build part and a blob part and I havn't tested all side effects (found so far: laos gallery crashing now and then) I'll stay on our implementation for now.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
I think you need to report your post to be moved.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Yeah, I know. But I'm not in a hurry; and when it was about the mirros posting (#2), the posting was moved, when we ended the discussion - I can't proof, but I gues it was before(!) the request. And if it's not time critical for me, why generate a report-message for the mods? I strongly belive they find enough of those, without my report... ;)

As long as you (rethorical: not [MENTION=7134312]knpk13[/MENTION], but all users) find the apks, I'm happy.

Amyway, thanx for the heads up!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
UPDATE (sec patch August)

New build is ready for download (known location). Regular announcement follows - don't wanted to hold back the build til tomorrow. Happy flashing. Who can't find OPCam and doesn't know what to do, does not deserve additional cam apps.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
Lol a mod may not stumble upon this post without a report. I reported it for you, so should be done soon haha. Earlier I kept trying this rom and switching back to OOS. Now this rom is my daily driver.

Also, I tried vertexos, and was really impressed with EAS (no microstutters all the time!! ; Better than even OOS) [MENTION=6745491]joshuous[/MENTION] (no offense to you of course nvertigo). It's designed to be very professional too, though it seems to lack some basic customization options like center clock. I hope EAS comes to either LOS or OOS officially soon. Or centre clock comes to vertex. Both work for me. I did try microg for a while but I switched back to gapps after a while. And my battery life on LOS is much lower than on OOS though I use a full black substratum theme for all apps. :(

Also I feel stupid and guilty that I don't understand all the technical posts made by you and joshuous. I'm like wtf are they talking about. I wanna learn too! :)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Yes, you are guilty. It's your fault, that I can't find a timeframe to make an announcment. Here, see the mess you are responsible for... *lol*

EAS TEST BUILD: 20170812

Started here: https://github.com/EAS-Project/android_device_voxpopuli [MENTION=6745491]joshuous[/MENTION] explains intergrating eas in a way I can understand)

Kernel: BrokenRenderKernel (https://github.com/RenderBroken/OP3-LOS-kernel), with this two patches:

https://github.com/nvertigo/android_kernel_oneplus_msm8996/commits/eas-br (the first two)

device: https://github.com/nvertigo/android_device_oneplus_oneplus3t/tree/141-eas

vendor: https://github.com/nvertigo/proprietary_vendor_oneplus/commits/141-work

All credits for working eas: [MENTION=6745491]joshuous[/MENTION], [MENTION=5267409]Azai[/MENTION]dl, [MENTION=5438598]RenderBroken[/MENTION]

All blame for broken parts: me ;) (If debugging is finding errors in the code - developing has to be the process of putting bugs in... ;)

The kernel sources base is dating back to May - so the last cve are missing: kernel sec patch level is 5th of May for the kernel.

ROM: https://drive.google.com/open?id=0B_f72wz8rwc6LS05LWdadllWZGc

MD5: https://drive.google.com/open?id=0B_f72wz8rwc6OHhlMHo3OTI0UEU

I hope the guilt is not too hard to take... ;)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
****, just as I switched to vertexOS as my daily driver to test EAS thoroughly. Lol. Thanks for the EAS build, can we dirty flash it over previous builds or do you recommend a clean flash?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Iflashed dirty, but wiped system and reflashed beans mini and suaddon. Rule of thumb: dirty flash and sew what happens - if issues occur: try clean flashing.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
From vertexOS FAQ:

14. Why is the security patch in "About phone" outdated?

This ROM tracks CAF, which lags behind AOSP by a bit. However, you shouldn't be worried about this because CAF brings in the latest security commits even when the stated security patch level in "About phone" is outdated. Trust me, I've compared the commits of our CAF tag with the latest AOSP branch commits, and also with the Android Security Bulletin. Please just wait patiently for CAF to update the security patch string. I can easily change it and 'cheat' you guys, but I'm never going to do such a thing. So please be patient and know that your device has the security patches.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
You quoted the answer to your question: the cve patches to the kernel solve sec risks. cve patches are part of the sec patches. The rom is sec patched to August, but the kernel sources havn't received this sec patches since May.

I tried to rebase the eas patches on top of 141-work (or los/cm-14.1 for this matter) for two nights, but failed to... I thought it's just fair enough to inform about this matter of fact.

EDIT:

The sec patch level is the opposite of outdated: it claims a standard I can't deliver atm. It's reading 5th August, but kernel is only patched to end of May.

[MENTION=535343]all[/MENTION]: if somebody is interessted in helping to rebase the eas patches on top of los kernel, I can push my changes. Drop me a note. I think my error is in resolving one of the "easy" conflicts, by always choosing the eas code... Apart from this really minor sec impact, I think vertex-/render-kernel is no bad choice!!! (It's really a great piece of software! Thanx again!)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
Are you using renderbroken kernel or renderzenith kernel?

Your build seems to be working wonderfully so far. Improved battery life imo, and reduced microstuttering.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Tiggy_Drum:
Dirty flashed successfully over lineage-14.1-20170810-UNOFFICIAL-nvertigo-oneplus3t build without any wipe.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
RenderKernel by [MENTION=5438598]RenderBroken[/MENTION].

Changing the kernel is more or less just a proof of concept.

If I'll fail on rebasing the eas changes on top of our laos based kernel, I'll drop the eas again: we talk about 393 commits, the only way to get this to our rom in a timely manner, is rebasing the commits, add merge fixes above, so I can easily rebase all this on an laos kernel update.

I don't panic if I try to merge nearly 400 comits, and the second is bailing out. I'm willing to work some nights without sleep on this, but I surely don't do this on every laos kernel update. I don't want to relay on other people's work, either. The equitation is: if I'm not ready to get this merged, my rom is not ready for eas.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
I noticed a bunch of errors while scrolling through matlog. Does it mean anything? Logcat attached. [MENTION=4405529]nvertigo67[/MENTION]

I'm tagging [MENTION=6745491]joshuous[/MENTION] too as the errors seem to be related to the vox populi power Hal.

Edit: Check next post (for the correct logcat). I uploaded the wrong one here.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Hmm... In the logcat I can't find the vp errors!?!?

I'm running the next test build, will see if I can find the vp errors.

EDIT:

I would like to suggest, that you use at least 1 Mio. setting for logcat in dev-ops. I think in the time between the screenshot and taking the logcat was enough to overwrite them.

Do you remember, if the "E"s occured directly after boot/screen on/etc, or a determinable action?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
SORRY!!! I uploaded the wrong logcat!!

Edit: no I just opened matlog because I was having microstutters and thought maybe something was wrong with EAS (because vertex had no microstutters with EAS; even oos had microstutters) and I saw a bunch of errors. So I reported it with a logcat.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] joshuous:
Has the error been fixed?

Failed to acquire lock means one of two things (off the top of my head):

1. Perfd is turned off. Turn it on by typing "start perfd" in terminal. Issue can be the result of incorrect init.rc setup or SELinux denials.

2. The perfd blob is not compatible with the libqti-perfd blob, since they need to be correct to communicate with each other.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
There will be a next testbuild today with RenderZenith Kernel baked by UBERTC gcc 6.4.1. On the build I'm testing atm, I see this error exactly one time. Followed by the initing message.

ingo@adler /usr/local/src/cm14/device/oneplus/oneplus3t $ grep Vox /mnt/export/data/Downloads/incoming/logcat.txt
08-16 11:56:43.498 1192 1844 E Vox Populi PowerHAL: Failed to acquire lock.
08-16 11:57:01.228 3092 3092 I Vox Populi PowerHAL: Vox Populi Power HAL initing.
08-16 11:57:58.647 3092 4150 D Vox Populi PowerHAL: LAUNCH HINT: ON
08-16 11:57:58.648 3092 4150 I Vox Populi PowerHAL: Activity launch hint handled
08-16 11:57:59.814 3092 4574 D Vox Populi PowerHAL: LAUNCH HINT: OFF
ingo@adler /usr/local/src/cm14/device/oneplus/oneplus3t $

No denial found (but found a bad derp for busybox). I guess perfd is ready to answ8er just a split second too late, but it's a guess: from just after the initing messege, I just see a lot of the launch hint triples (on - handled - off). If this is the case, I would say it doesn't matter as long as the connection is finally established. (@joshouos: would match with my observation, that changing to RenderZenith let me feel a real difference.)

EDIT:

General question: do we use both power hals (power.msm8996 from VoxPopuli and power.default from hardware/libhardware) or is the one from libhardware obsoleted by VoxPopuli?

EDIT2:

I hope you talk of libqti-perfd-client - since I have no libqti-perfd at all (nor it's found in OxygenOS:

ingo@adler /usr/local/src/cm14/vendor/oneplus $ find oneplus3t -name \*perfd\*
oneplus3t/proprietary/vendor/bin/perfd
oneplus3t/proprietary/vendor/lib64/libqti-perfd-client.so
oneplus3t/proprietary/vendor/lib/libqti-perfd-client.so
ingo@adler /usr/local/src/cm14/vendor/oneplus $ find ../../../oxygenos/ -name \*perfd\*
../../../oxygenos/system/vendor/bin/perfd
../../../oxygenos/system/vendor/lib64/libqti-perfd-client.so
../../../oxygenos/system/vendor/lib/libqti-perfd-client.so
ingo@adler /usr/local/src/cm14/vendor/oneplus $

EDIT3: fixed. (Propably the single one at startup was a side effect of my busybox sepolicy rule - or timing on boot up is different, when switching off the device before.)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
I have no idea what you're talking about (too technical). :(

Do you mind explaining what the error was and whether it'll cause any difference now that it's been fixed?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Update eas-testbuild

Build 20170816

This is build with RenderZenith kernel, updated perfd blobs and a fix for a wrong pathname (busybox wasn't labeled to toolbox).

Remember the complete eas implementation is from vertexos (https://xdaforums.com/oneplus-3/one...kernel-vertexos-blazar-zenith-kernel-t3571781). Without the afford and genius of these guys, it wouldn't be possible to test (or use) AES on our rom. Reading this thread is highly recommended! Especially the general (and the not so general) explenations from [MENTION=6745491]joshuous[/MENTION] are worth every single second you read. Sometimes he's writing as lengthy as me, and every sentence is valuable.

ROM: https://drive.google.com/open?id=0B_f72wz8rwc6dTRSYjU5aEJLcTg

MD5: https://drive.google.com/open?id=0B_f72wz8rwc6UF9XV1Iwd0h0cDQ

(Don't be afraid to flash. It's a testbuild, because I've changed the kernel again. I use this build (besides some fixes) for two days now, and think it's rock solid.)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
When I have no clue, why something has an effect on something completly unrelated, I talk of "side-effects"... *lol*

Boot timing: we are on a multicore systems (some boot-up processes are handled at the same time. If power.msm8996 is ready just before perd is ready, power hal fails on getting a lock on perfd you see the error message.

It is _possible_ that the denials on busybox are causing a short delay. It's also _possible_, that the different boot sequences (you may have noticed happy-dance (the led is fading from blue to cyan and back and forth) is not always shown). This differnce _could_ also impact the timeframe perd is up. I have no proof for one or the other, but both possibilities seems plausible to me.

EDIT: (forgot that part of your question)

When bringing back busybox, I decided not to dublicate the rules for toolbox, but just to label bosybox as toolbox_exec object. This allows busybox to work on the same files like toolbox. Apps using commands of busybox are grated the same access rights as if they call a toolbox module.

It's ok, if you don't understand this - in deed I expect nobody to understand selinux and sepolicy, that's why I skipped this explanation. I had a hard time understanding selinux - and still havn't made real friendship with it. Knowledge of fs access rights and posix acls deffinetly is an obstacle on the way to understand selinux - ok, for me it was, YMMV.

After understanding the structure of selinux, I became quite good at debugging and fixing sepolicy issues... Before that, it was literally impossible for me to do something else then writing: "sepolicy is broken." ;)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
The strange flashlight issue

OOS cam is trigering the disabled flash light in a way, that it is no longer usable and can even reboot your phone. I don't think I can fix this soon - if at all: if I would change the framework to work with OOS-Cam, it will be broken for other apps and framework.

Hacking in smali files is not something I'm very used to or gifted at, if someone wants to do so, I would kindly ask to go straight to op5 cam.

Workaround:

After using oos cam under 15%, force close oos cam before trying to switch on the flash (no matter, if activated by gesture or tile).

If I have the choice putting some commits in the kernel or hacking java, I would always go for merging and conflict resolving...

EDIT:

This is only true for op5 cam. No issue, if you use op3 cam or Snap.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] lapapunk:
[MENTION=4405529]nvertigo67[/MENTION]

Hey man. Thank you so much, I'm glad that you opened for such new things like eas.

Latest build as dirty make bootloop. But dirty flashing after wiping the system and cache make it work.

Thanks.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] xpissio:
Hi [MENTION=4405529]nvertigo67[/MENTION], what do you think about the (maybe) introduction of DCI-P3 mode?

https://review.lineageos.org/#/c/184995/

Do you approve/like it?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
Works fine for me. Also don't see any more of those vox populi errors.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] lapapunk:
Did you saw new sRGB profile? It's almost the same as dci-p3.

---------- Post added at 18:25 ---------- Previous post was at 18:22 ----------

Maybe something corrupted on my side. But after I've wiped system partition all became fine, booted as usual.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
One after the other. I've seen the topic branch, and I think if tested it goes to los.

At the moment I'm thinking of an update path, if I have answered that for me, I can start thinking of importing changes.

BTW: look at the last commit on 141-eas keenel branch: after zswap was working I did a sync and clean build. Suddenly zswap stopped working... That's a clear sign of lack of focus... need to slow down a bit... ;)

Atm I'm happy enogh with the last testbuild: it's stable and bugfree enough to work as daily driver. I can't manage to support two builds. First I thought I make one testbuild, publish a "normal" build - and take my time to get aes patched in the kernel. Also I did not expect Zenith working that flawlessly wit los above (it was more: "one try on Zenith will not hurt"-desperation build. *lol*

On openness:

The only luxury I allow myself as rom builder is: if it's not related to stability, I deal with, which I'm interested in. EAS is in this category - customizable Clock (no offense meant, just a good example - is not.

Ican't emphasize enough, it's a good idea to read in https://xdaforums.com/oneplus-3/one...kernel-vertexos-blazar-zenith-kernel-t3571781
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
If you are talking of this https://github.com/VertexOS-Devices...mmit/6163855f5500167e3225c3c36682ad8d90157e39 , yes I know. That's one of the things I'm considering to decide, how to go on.

Don't think too much on this. If I test system near changes (like oms, busybox or changing the entire kernel) I always wipe system, dalvik and cache and reflash beans and suaddon after the rom, so I really don't know, if the steps in between (aka builds I test only myself to see if something's working) or my flashing routine saved my from that bootloop. Though the last nights were exhausting (and super interesting) I'm sure I have only seen booting and not-booting kernels, but no bootloop. Not-booting means: stuck in boot process that early, that I can't get adbd to respond.

On the can't get lock error: if you reboot from system to system: one single error, after that it works with NO further error. Booting the device from power off state: no error at all.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] buzzqw:
that's fair.

thanks for you answer

BHH
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Want to share a good laugh

(Meanwhile it has become hard to quote this nonsens, instead of deleting it - but read on...)

Yesterday I found this: https://github.com/sultanxda/patcher/blob/cm-14.1-oneplus3/custom/frameworks-av0.patch

The Date:-line in the actual patch...

Karma at its best: not just proving me being an pedantic idiot - but let me find out my self, while [MENTION=6745491]joshuous[/MENTION] is showing me one of the most interesting technical innovations (regarding kernel<->android integration) of the last years... *this is not multi-hal, but multi-lol*

Sorry Neil, sorry Josh, sorry Universe - and thanx to all of you.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Vipeout:
Sry I'm a bit lost now. Noticed that opcam was missing in latest builds then read here it was due to some conflicts with changes in the HAL implementation.

But in one of your posts above you said it's only relevant for op5 cam...?

So in a nutshell, can I manually install the op3 cam or will it make my phone explode, melt or, even worse, turn it into an iPhone?

Thanks
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
Install them from this post [MENTION=4208174]Vipeout[/MENTION]
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Maybe, I don't know that posting (BTW: you mentioned a user instead of giving the link to a posting.)

And since you (@knpk13) have initiated the move of this posting, I guess you meant to let [MENTION=4208174]Vipeout[/MENTION] there.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Vipeout:
Much obliged, to both of you :highfive:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
FIX: Camera issues

The apk I recommended (the one with kxzxxx in it's name) is not working (it has additionally the 32bit part of the libs, when shipped inside the rom, it had only the 64bit libs). This also breaks Snap.

Uninstall the old apk, install this one: https://drive.google.com/file/d/0B_f72wz8rwc6SV9VTXRXMVdfeFk/view?usp=drivesdk , wipe data of Snap and OnePlusCamera and reboot.

Rom update: I was very busy to patch los kernel for aes, I`ve not forgotten the blobs update, nor the rom update. You can expect a real great update later today!!!

EDIT:

something with our cam implementation is broken. It's not related to the eas changes. Checked for that some hours, now. Sadly, I have lost track of time and have no build, rather then a apropriate release posting... Will get some sleep, now.

Sorry for the delay, but I really love this new build and don't want bad ux on the first official eas build, because of me focused that much on eas, that I forgot everything else (what is true, in deed - but without that focus this task would have been overdemanding for me).
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
UPDATE (eas, ob13, some candy)

Build 20170823

Releasenotes:

This build requires firmware OpenBeta 13 (aka ob12). This build will install the updated firmware and no further action has to be taken. An archive of all firmwares can be found below in the firmware section of Downloads.

With the help and assistance of [MENTION=6745491]joshuous[/MENTION] and [MENTION=5438598]RenderBroken[/MENTION] I'll managed to apply the patches from https://github.com/EAS-Project/msm8996-eas to the most current los kernel. VoxPopuli is a custom power hal utilizing the schedutil governor to make use of eas. All credits for EAS and VoxPopuli are owed to these two opensource jedi's.

Finally I proudly present the latest evolution of this rom featuring

EAS

Since I have not slept to fix the camera, let me keep it short: it's just a damn good idea.

Impacts on UX? Your job to tell me - my job is done for now... ;)

Good time for a clean flash, though I don't think it's neccesary. If you encounter issues after dirty flash, try the method which includes wiping system and reinstalling beans mini.

Changelog:

Fingerprint: Speed up wake-and-unlock scenario — Sultanxda

telephony: Hack GSM and LTE signal strength — Sultanxda

LockClock: Remove wakelock — Sultanxda

cherry-pick EAS (...I'm not listing tgem here: see above links for details)

add VoxPopuli

Blobs: update to ob13

op3t: camera: use libmmcamera_interface.so from ob9. — nvertigo (cam fix)

op3: Remove duplicate time_daemon service definition — Sultanxda

op3: Add the high performance VR feature — Jonathan Wicks

op3t: init: update build fingerprint to OxygenOS OpenBeta 13. — nvertigo (github/141-eas

releasetools: remove custom updater script. — nvertigo

remove_packages: power.default. — nvertigo

blobs: libqti-util: pin prebuilts from OP5 (7.1.1/NMF26X/06271211

blobs: add libqti_performance. — nvertigo

EAS: blobs: iop: pin prebuilts from OP5 (7.1.1/NMF26X/06271211

EAS: blobs: perfd: pin prebuilts to marlin, 7.1.2, NZH54D. — nvertigo

op3: Add DCI-P3 entry to color profiles (RenderZenith version

sepolicy: fix pathname for busybox. — nvertigo (work

toolchain: switch to UBERTC gcc 6.4.1. — nvertigo

TARGET_UNOFFICIAL_BUILD_ID: show this is build with EAS. — nvertigo

op3: Ensure that perfd is properly started — joshuous

EAS: Implement Vox Populi Power HAL — joshuous

EAS: init: Initialise EAS default values — joshuous

EAS: init: Start perfd after all perfd properties have been set — joshuous

EAS: init.qcom.rc: Create /data/misc/perfd — joshuous

EAS: Import Marlin perfd policies — joshuous

EAS: Set ENABLE_SCHEDBOOST — joshuous

Camera- and Gallery-Download (fixed versions)

[SIZE=+2]DOWNLOAD[/SIZE]​

Happy flashing!