[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
UPDATE: experimental build

Before you proceed to read start backing up your device (nandroid and i.e. titanium).

Have started your backups? Ok, then read this posting. It's longer. And boring. Though read and understand this posting before flashing.

While I was trying some stuff, putting a hidden present to Dialer.apk (anybody finding out, will understand that I don't want to discuss this in public - thanx) and doing some checks on [MENTION=5091734]dianlujitao[/MENTION]'s camera changes, reality knocks at my door: OpenBeta5 is out. Additionally to my idea of an experimental build (later - read on... ;) ) this contains the updated blobs from ob5 - which includes new firmware files but doesn't increment the trust zone.

This realese should be run on ob5 firmware and ships with this ob5 firmware. Flashable zips for ob5 firmware and uniblobs will be added later. (I'm pretty sure, that any firmware of 4.1.0 and newer will work, since the trust zone hasn't changed - but who knows, better use the firmware files with the very same version as the blobs.)

To get all this straight, the following changes will be in the next regular update:

Changelog:

Update all blobs to OxygenOS OpenBeta5. — nvertigo (see: https://github.com/nvertigo/proprie...mmit/c94a344b5ee12aa68fcab24f3500ea0c72973d9c for details)

microg: rebase our patches. — Nvertigo

magisk: delete magisk.zip after flashing. (This is only cosmetics, but left over install files are ugly and bad programming style.)— Nvertigo

magisk: rebase our patch. — Nvertigo

op3: Add missing & remove unused blobs — dianlujitao

op3: Update to OB14 blobs — dianlujitao (This is just to keep our source base konsistant with laos - our blobs are from ob4)

op3: Sort blob list — dianlujitao

init: set build description to OpenBeta5. — nvertigo

blobs: use aptX binaries from OxygenOS. — nvertigo

overlay: add some missing overlays. — nvertigo

Magisk: don't ship Magiskmanager. — nvertigo

The complete message of this one:

ingo@adler /usr/local/src/cm14/device/oneplus/oneplus3t $ git show b449fd9| head -n17
commit b449fd9300c802f06759a3c5fb06d7ad425d47f3
Author: nvertigo <nvertigo67@gmail.com>
Date: Fri Apr 21 16:18:36 2017 +0200

Magisk: don't ship Magiskmanager.

It' not a good idea to have MagiskManager installed as
system app. Leads to all kind of issues, if you try to
use beta versions or if you want to uninstall Magisk
all together. So we remove it again.

The MagiskManager stub is installed by the flashable
magisk.zip, anyway. On reboot the user is asked to
update MagiskManager from playstore. So this is no big
deal.

Remember to wipe system and reinstall gapps or microg.
ingo@adler /usr/local/src/cm14/device/oneplus/oneplus3t $

IMPORTANT for dirty flashers: if you tap on MagiskManager the first time, you will be let to playstore. Uninstall MagiskManger in playstore first, then immedietly install again - otherwise MagiskManager will not work! If you clean flashing following the OP, just ignore the last sentence, though following this step wouldn't do any harm.

Now for the experimental part:

A couple of weeks ago I've decided to do something, I always refused to do: hacking in the laos base without any device specific needs. I added the microg patches to support no gapps installations and I changed the buildin root to magisk to pass saftynet (in deed this rom was always able to pass saftynet, but the laos root solution was tripping saftynet). The most important consideration here was stability (neither the microg patches, nor installing Magisk do any harm to stability and safety/security aspects).

My opinion on theme engines has NOT changed: they do more harm then good.

On the other hand I want to be fair: if implementing OMS does not effect stability, safety/security, batt life and performance for people NOT installing substratum and using themes - why not giving OMS a shot. Honestly I have to admit, that there is an other very, very important reason, why I decided to test OMS: I love the way people behave here (everybody thinking now: good manner? his German character is breaking free... ;) Please read on...). I really appriciate the "vibes" here, and strongly belive, that we can have OMS here, without making this thread a theme's thread. I would like to have information here like:

Theme XYZ works flawlessly/not at all on this rom;

what I don't want to see here (and if I see such persisting OTs I will remove OMS from the rom again):

You need to dissamble XYZ.apk, change foobar and reassemble (including some true and interesting, but completely OT information). And other theme specific discussions.

So this is not only experimental on a technical level but also on a social level.

THE resource for using substratum is here: https://xdaforums.com/apps/substratum

The Substratum app can be found on playstore.

The main aim of intergrating OMS is giving the non-theme-users the same expirience as before, while allowing others the freedom of choice to break their stable installation with funny themes... ;) (3/4 sarcastic kidding; 1/4 truth).

[MENTION=306612]non[/MENTION]-theme-users: please report only NEW issue. I.e.: ff cam takes green images if hdr is active is long known and not connected to OMS at all. (Understanding this is one of the reasons, why I need a thread with grown up users - thanx.)

[MENTION=743812]theme[/MENTION]-users: let us know, which themes work for you on this rom. I'm looking for something like a reference theme, for testing the OMS implementation.

This OMS implementation is taken from LineageOMS. Many thanx and all credits for making OMS easily mergeble goes to LineageOMS. The reference thread is located here. Homebuilders need to use lineage_oms_merge.sh: use full qualified path name to lineage root - relative paths crossing symbolic links will NOT work.

All credits for the OMS code itself: https://github.com/SubstratumResources, which seems to be: Nathan Chancellor, Nicholas Chum (@nicholaschum) and Surge Raval (@surge1223) (if anybody of the three of you reads this: would you be so kind to point me to a list of creditable authors for SubstratumResources and LineageOMS, please?)

Once again: clean flashers sticking to OP procedures are fine. All others remeber to wipe /system (which means: after wiping system unmount system in twrp before flashing, and reflash the gapps/microg package you have originally used) and deinstall MagiskManager prior to install.

Thank you for reading through the complete posting!

ROM: lineage-14.1-20170422-UNOFFICIAL-nvertigo-EXP-firmware-oneplus3t.zip

MD5: 3d00020e4e79172cceb47d98b5c38f23

Mirror: will be added later

Happy flashing! Happy theming! Happy reporting! Happy Happy!

P.S.: [MENTION=341181]m0d hipp¥[/MENTION]: would you be so awesome to mirror this experimantal build (only ones for this one - other test- or experimental-builds doesn't need mirroring), thanx. Also: if you run into quota or other limits: I'm sure four or five versions is absolutly enough as history. Again: thank you very much for your efforts and resources!