yashsingh1/xdaforums huggingface dataset:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
UPDATE (Feb. security patch)

Build 20180214

Releasenotes:

This build requires firmware OpenBeta 15 (aka ob15). As always an archive of all firmwares can be found below in the firmware section of Downloads - the flashable firmwares are the original (file names starting with oxygenos* hold original fw files) OnePlus fw images. NLOS and 'old'-style bootlogos can be found down in this posting.

There has been some confusion on twrp versions, lately. For nlos always use the "original nougat twrp-3.2.1-0".

If you have issues with bootloops or access to data with some apps, use "original nougat twrp-3.2.1-0" to FORMAT(!) the data partition of the device:

Backup all your data (eveything under /sdcard/; i.e. Downloads, Vodeo, DCIM, etc...)

Boot to "original nougat twrp-3.2.1-0".

Tap on "Wipe".

Tap on "Format Data".

Confirm with swipe. This actually clears your complete data partition, including all data and encyption.

Check if the newly created fs is the type you want (ext4 and f2fs is supported) - eventually change it to your liking.

Just follow the OP's procedure for first installs from OP's "Installation" section (clearing data is allready done, of course).

Changelog:

Sync to upstream: Feb. Security Patch

Bootlogo choices

nlos_bootlogo-v0.1.zip

back_in_black_bootlogo-v1.0.zip

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

Happy flashing!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] m7d1:
Great build as usual thanks to keep it updated
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] vinoxflame:
Finally got some spare time, formatted my data partition and continue with the flashing procedure and............boom it boots successfully, no more stuck on boot animation.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Jxcorex29:
Why do you need ob15? I thought the OP3T was up to OB22 now.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] gamal001:
because this build still nougat.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Pssst... Sneak-Preview

Gotcha... ;)

Far from perfect, but usable: https://drive.google.com/open?id=1kJFApe-XZaRwOyJFXgbsff0fE65SFi_7

I have no fw package, yet. Currently I recomment [MENTION=7134312]knpk13[/MENTION]'s way: flash complete ob22 rom and boot it up once (no need to go through first time setup, just check, if it boots up; because if ob22 boots, nlos-15.1 ALPHA will boot, too). Use the new official twrp-3.2.1-0 (the unified one from 2018).

Many thanx to [MENTION=4860033]Arnova8G2[/MENTION] and [MENTION=377973]defcomg[/MENTION] for their great work on GCam and libs to make themmwork on non-Pixel-devices, and for let their works beeing used in NLOS Oreo! As many thanx to [MENTION=4487956]S4turno[/MENTION] for his awesome support for GCam in this thread. Recommended settings for included version.

Allow me one personal wish: if you comment on nlos-15.1 in the thread, set the title to "15.1". Thanx in advance.

Happy flashing!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] OschivoS4:
Notification Slider

Dear Sir,

Can you, or anybody confirm that the notification slider is working, and that i have a "full vibrate" mode without rooting the device and using aditional apps?

Thanks in advance.

**EDIT**

Before you guys punish me.

I am going to search this thread first ;)

Best regards.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] m7d1:
Notification slider is working.. but there is no option for vibrate mode, i think u need exposed to activate it..
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
Sweet. Make a new thread for 15.1? Oh and is NLOS Oreo any different from LOS Oreo?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
I havn't decoded if I rename/reuse this thread, or open a new one. Anyway, I won't open a new thread (or rename this one), before I'm happy with NLOS-15.1 as daily driver and I have all documentation updated (honestly I hope twrp's change fs to f2fs button is fixed to issue the correct command... otherwise the howto f2fs gets longish... ;) ).

LOS = Lineage OS

NLOS= nlos (los based, op3t optimized, feature enriched rom)

Mission Status: ALPHA

So far accomblished:

GCam

saftynet compatibility

allow gpu to drop lowest value (133MHz) instead of second lowest (2xxMHz)

added 2 out of 3 weather providers.

bootanimation

adjust AAPT

To do (at least):

fix toy-/toolbox, readd busybox (i.e. lineage bash isn't working interactivly, because "resize" command has ben stripped from toolbox, arp and some other ipv4 commands are broken etc.)

bringback wireguard

make rom microg ready again (I would really appriciate if somebody has a source for microg spoof signature and location provoders outside system patches)

As you can see, the "new thread or reuse"-question is not my next step.

BTW: my progress is much faster then I expected... :)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
15.1: beta01

Build 20180218

Releasenotes:

Since I progressed much better then I thought, the lineage team fixed quite some issues upstream, and I use nlos-15.1 as my daily driver for three days now, I decided to leave ALPHA and go BETA!

NLOS-15.1 relays on Oreo firmware. ob16 or later is needed, I strongly recommend using ob22 (because that's what I'm testing with): oxygenos-ob22-firmware.zip

NLOS-15.1 requires current, official twrp-3.2.1-0. If you expirience issues like bootlooping or issues accessing files on the data partition, you need to format your data partition:

boot to twrp

on the twrp home screen tap "Wipe"

on the Wipe-screen tap "Format Data", this formats your entire data partition to ext4, deletes ALL data and removes encryption (you can enable it again frommwithin the installed rom later)

wipe cache, dalvik and system

flash rom

flash gapps

optional: flash addonsu

If you want to run data on f2fs, you need to work around a bug in this version of twrp: in the "Change fs" screen "f2fs" is issueing a faulty command. And I doubt this will be fixed any time soon, so lets change the ext4 to f2fs manually:

After formatting data, before wiping cache, dalvik and system, complete the following steps:

OUTDATED! Working procedure can be found in this posting.

tap on the home icon to get to twrp's home screen

tap on "Mount" and untick data

tap the home icon again to get back to the home screen

tap "Advanced", then tap "Terminal"

a terminal with shell prompt opens, type:

mkfs.f2fs /dev/block/sda15

continue with wiping cache, dalvik and system

Changelog (all changes on top of lineageos 15.1 synced 18/02 at 10:00 UTC):

Oreo: track our own device, kernel, vendor and lineage repos. — Nvertigo

Call the installation of weather providers. — Nvertigo

Readd weather providers. — Nvertigo

Install GoogleCamera modded by Arnova8G2@xda. — Nvertigo

op3: Disable interactive load prediction — dianlujitao

NLOS: set LOCAL_NLOS_VERSION to beta01. — Nvertigo

Opt in LINEAGE_VERSION_APPEND_TIME_OF_DAY. — nvertigo

NLOS: include vendor/nlos/nlos.mk. — Nvertigo

oneplus3: Set recents and back to the sane layout — Darragh McGee

NLOS: set LOCAL_NLOS_BUILD to oneplus3t. — Nvertigo

AAPT: adjust config to the physical abillities of 3t's display. — nvertigo

NLOS: set LOCAL_NLOS_VERSION to ALPHA. — Nvertigo

op3t: init: allow the gpu to drop to 133 MHz on idle on op3t/sd821. — Nvertigo

net/wireguard: add wireguard importer — nvertigo

op3: defconfig: enable /proc/config.gz. — Nvertigo

op3: defconfig: set LOCALVERSION to NLOS. — Nvertigo

op3: defconfig: increase kernel buffer sizes. — Nvertigo

proc: Remove additional SafetyNet flags from /proc/cmdline — Sultanxda

proc: Remove verifiedbootstate flag from /proc/cmdline — Sultanxda

Use Pixel2Mod's libmmcamera_s5k3p8sp.so. Modded by defcomg@xda — Nvertigo

[SIZE="+2"]DOWNLOAD[/SIZE]​
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] horqai:
Thank you for this oreo build. It's running so far with no issue and feels very smoth.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] d3xtr0:
Same here - With your suggested gapps and ob22.

Thanks!!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] horqai:
15.1

Maybe I'm overlooking something but I can't get the encryption prozess started. Logcat shows:

02-19 11:16:24.399 E/Cryptfs (455): Orig filesystem overlaps crypto footer region. Cannot encrypt in place.

Any idea?

I've tried it with root and without. In flight modus and after wiping cache and dalvic etc.

I just see for a few seconds the green robot.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Would you all remeber to put 15.1 in the "Title" field of the posting form, if refering to 15.1, please? I consider ALL postings without that as refering to the threads title version!

For 14.1 use the old, non unified twrp-3.2.1-0 from last year.

For 15.1: I've done the initial encyption with oos5, perhaps initial encryption isn't working yet. The other possibillity is that the new, unified twrp has f2fs more broken, then I thought and isn't usable at all. That would mean: use old 3.2.1-0 for changing to f2fs, then flash the new one before installing nlos-15.1...

...or use ext4... ;)

I hope I guessed the info you left out correctly... *lol*
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] horqai:
15.1

Yes and sorry, you are right I've used f2fs by following the procedure in the post above.

I did the installation with all the wiping again and as you mentioned, formatting the data partition with f2fs by using the old TWRP dedicated to the 3T did the trick:

Now data is encrypted and I also can enter TWRP with my pin and access everything.

Thanks
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] tomstrummer:
Camera FC

Search this thread, but search is awful, so sorry if i missed any report or discussion of this issue...

The included camera app doesn't work in 20180214. it FC's every time. This is immediately after installing the 20180214 build. Logcat is attached. I'm coming from stock OOS 5.0.1 so I should have all of the latest firmware.

Additionally, (this may be related) this link in OP to Beans Gapps which really just links to this other post are for 7.1 and TWRP will (rightly) refuse to install them on Oreo. I tried. So I used BeansGappsMini-arm64-8.1-5X6P.zip which seems to work.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Use ob15 firmware and 7.1 gapps for nlos-14.1.

Use ob22 firmware and 8.1.x gapps for nlos-15.1.

Current stable build from OP is 14.1!!!

In the last posting on 15.1 beta01 I linked a working gapps package.

[MENTION=535343]all[/MENTION]:

Would you all remeber to put 15.1 in the "Title" field of the posting form, if refering to 15.1, please? I consider ALL postings without that as refering to the threads title version!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] tomstrummer:
/facepalm. Thanks, of course you're right. I missed that this thread is for 14.x and I downloaded the 15.x beta because I wanted Oreo. It might make sense for nlos 15 to have its own thread? Or maybe it does and I didn't see it because it's not on the forum frontpage. Thanks again for pointing out what should have been obvious.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
Are LOS/NLOS kernels always upstreamed? (Or custom roms in general)

https://xdaforums.com/showthread.php?t=3626913&page=30

https://xdaforums.com/showthread.php?t=3738742
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] d3xtr0:
### NLOS 15.1

Sorry man, but on Tapatalk I'm not seeing the title field :(

On ext4 encryption is working. Using lastest twrp from blu spark.

Ps: why don't you use another base, with more customisation, like RR or AEX? Any reason why you chose LOS? Thanks!!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
Just a heads up for anyone using Magisk on 15.1

Magisk Manager 5.6.0 keeps crashing on NLOS 15.1

I was going to report the bug both here and in the Magisk Beta thread but apparently [MENTION=4470081]topjohnwu[/MENTION] has already been able to reproduce the bug as he reported in the Magisk Beta thread 3 days ago. Not sure if its the same issue but hopefully it gets fixed!

For now im using Magisk 15.3 instead of 15.4 as a workaround.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Tiggy_Drum:
This is not a ROM problem but magisk. There is a fixed APK in the magisk poll. You had to install 15.4, uninstall magisk app and install the fixed APK.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
Love the ROM and all the up to date goodies, though there a couple of nifty features from OOS that I miss :(

Is there anyway to enable sRGB mode on this ROM? Everything looks so saturated.. its uncomfortable.

Also, is there anyway to not make the button backlights light up when you touch the screen? They should light up only when touching the buttons. (Which is the my desired behavior)

I can't find the option for centre clock or circle battery either.

Edit: Set srgb mode using kernel adiutor. Can someone explain tcp/ip algorithms to me? Everyone says Westwood is the best for some reason that I don't understand but I couldn't find Westwood.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
That's a simple one: I like los. It has exactly the amount of additions for me. "Dark Style" was the only feature I was missing (since cm-10.x, which was much darker by default)...:good::good::good:

srgb IS there (kernel-wise), but the color modes have to brought back to livedisplay first, before there is an comfortable way to access it.

Since you are using magisk, there is a "semi-comfortable" way. Make a module (or use one of the magiskmscript locations), which issues this command:

echo 1 >/sys/devices/virtual/graphics/fb0/srgb

.Of course you can use this command on a shell (terminal or adb), too. Unsetting works with

echo 0 >/sys/devices/virtual/graphics/fb0/srgb

The "button doesn't lit up, when screen is touched" will be in the next beta (later today) - fixed it last night. (As well as bringing up dash charging indication again.)

For symbol, position and other statusbar tunings it's the same as for livedisplay: let's patiently waiting for upstream implementation.

Let's see what the future shows. Let me get up the basics, before fideling with kernels...

I.e. getting the shell back to accepting cursor buttons and pathname completion is more annoying for me, then getting the newest kernel patches. Of course, your milleage may vary.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
Does anyone know how to change the encryption password? I had a 3x3 pattern as my encryption password on OOS, but I now want to use a 4x4 pattern. Changing the password/pattern only seems to change the screen lock password, not the encryption password.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
ext4 or f2fs?

f2fs: broken as initially encrypting (currently only possible on oos - hint: nandroid on external usb stick)

ext4: don't know (EDIT: see next posting: ext4 initial encryption and passwd/pin/pattern-changing is working.)

BTW: remember 14.1 about a year ago? Quite similar, isn't it?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] goosebickel:
15.1

Encryption went through fine for me with ext4. I Formatted data before installing the beta version. Everything running smoothly so far.

Thanks for the great build
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
Edit: I'm ALREADY encrypted, just want to change the passphrase for encryption. And I wasn't sure if you could do that on even OOS, because I don't have much experience with encryption. I just went ahead and encrypted last time because i get problems with forceencrypt on OOS wiping all my data even when I flashed magisk last time. Apparently they keep changing things rip.

Edit 2: Are you telling me I have to FORMAT THE ENTIRE DATA PARTITION AGAIN if I'm encrypted and want to change my encryption password????????

I'm on f2fs because that is the default FS. Yeah I lost my data a couple times lol and the latest format was f2fs on OOS5 and it's encrypted. But I don't know how to change the encryption password.

Also, btw I have a tiny cute 128gb USB C drive now to backup all my phone data in case I have encryption issues again lol. Tired of losing my data so often because of OOS forceencrypt. Used to just run it unencrypted.

And wow so many sweet changes all in one build, I really don't know how to dance though xD

I could however conduct an orchestra of puppies to bark a celebratory song lol.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] d3xtr0:
Hey

I'm sorry to be me the one whose gonna tell you but.... Yes, the only way is to format data, as far as I know there's no way to change the encryption secret.

Sorry :)

---------- Post added at 08:37 PM ---------- Previous post was at 08:30 PM ----------

Eheheh exactly what I expected :)

What would be the impact of having hardware key binding like RR?

I'll try the new build tomorrow. Thanks
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
Your work deserves a donation. How do I donate lol?

And I guess I could use gravity box for centre clock and other small stuff till they add it upstream in LOS. Like I literally have the perfect setup without unnecessary bloat features. Great performance and stability and everything and freedom to use whatever I want like microg (though I don't use it). Also that it's op3t specific and has the customization options that make sense and takes care of minor annoyances like the keys lighting up when you touch the screen. I have no idea why LOS thinks that's a good idea, it's so dumb. Like you even fulfilled my request to upstream the kernel lol you're so cool xD and you communicate a lot with your users. On the topic of minor annoyances, could you add the commit made by Lord boeffla in his kernels which disables the hardware keys if the touchscreen is in use to prevent accidental touches? I'll try to find the commit if you need a specific link.

---------- Post added at 11:44 PM ---------- Previous post was at 11:32 PM ----------

Oof.. that's so stupid. Is that how encryption works on other devices too? Like windows, linux, Mac, etc? You can't change the encryption passphrase without literally formatting the entire drive? I'm assuming you can't remove encryption without formatting either?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] d3xtr0:
Not sure but in my t540p I can change the password but the encryption is at hardware level(?)

Well... Probably I have to Google that.

But yes, remove encryption on android is only able by formatting data.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
15.1 (also true for 14.1)

Som general thought on f2fs vs. ext4:

ext4 is by far the supirior of both in nearly every regard. IT's feature wise much more sophisticated, it's faster in real life (properly trimmed) and - without any doubt - it's much better tested. Theorethically f2fs should behave better with battery - and peehaps is, but I couldn't proove that in real life: neither on one, chagallwifi nor op3t.

On speed: 18 month back I 've done some testing on my build host (when changing the system disk to ssd): building the (build-host's-)kernel with -j9 (amd fx8150) it took 4:50 with ext4 (journaled) and 5:05 with f2fs.

I also found that proper partition allignment has more influence on speed then the fs itself: on an intentionally misalliegned partitions the kernel compile take over 12 minutes for both fs. All android device's partition tables I've seen so far are properly alligned by the oem!

If one wants a stable, evolved and well tested fs, go for ext4.

I use f2fs to get trapped before you get trapped, because the worst point on f2fs are the api changes with poor backward compatibility.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
15.1

Changing the encryption password/pin/pattern if you use f2fs with nlos-15.1:

I assume a twrp backup of OOS was done right after initializing encryption. (This may be stored in the encrypted data partition, since we do NOT need to reformat - but I recommend using an external device for nandroids!)

boot to twrp

from twrp (advanced->file-manager) delete /data/system/locksettings.db - this makes life easier

nandroid your nlos-15.1 installation

restore OOS nandroid (and delete /data/system/locksettings.db, if you havn't done so before backing up your OOS installation)

boot to OOS, you need to give your current encryption passwd, but no lockscreen passphrase, just swipe up

In OOS go to settings and change your lockscreen passphrase (password, pin or pattern): you get asked if you want that booting should be passphrase secured, say yes. Now the new passphrase is uswd asmencryption passphrase

boot to twrp

you will be asked for the new encryption passphrase on twrp startup

restore your nlos-15.1 installation

reboot to nlos

give new encryption passphrase

swipe up to enter nlos

in settings set a lockscreen passphrase

Note: you won't loosw any data, but your lockscreen passphrase.

Note: I highly recommend to delete locksettings.db before doing any nandroids. It makes life easier.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Different libs, api and kernel drivers: you can't compare across devices.

Correct, but the origin question was about changing the passphrase, which is something completely different, and most important: you CAN change the passphrase without loosing data.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
Hmm kind of a roundabout method and I was willing to try it, until I realized I can't choose a 4x4 pattern on OOS as my encryption passphrase rip. XD

Is the procedure same if I switch to ext4, as you claim it's better?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Since cm10 "vibrate mode" and "silence" are part off the power menu. These options havn't been brought up again upstream (hey, we are beta, and I'm sure it'll be back sooner or later).

If there is an existing, working, non-intrusive, not breaking current implementation of notification slider, nor future power menu breaking patch, I'll add it. But since I'm happy with los' implementation, I will NOT make this patch myself.

We had exactly this discussion one year ago. I offered exactly the same. No one offered a slider patch, so far.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
I know there's a patch for that on the OnePlus 2 since I use a customized LOS rom by Seraph08 on my OP2. I think there's one for the OP3T but honestly I just the alert slider to toggle between normal and alarms only (vibrate), so I don't really care either way. But if someone needs the feature, I could try finding the patch.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Sorry, dude. Now, reading your posting, I realize my "workaround" doesn't work for other patterns then 3x3 (yeah, I remember you mentioned that).

On the other hand: since nlos can't change the encryption passwphrase, you can implement different passphrasws for encryption and lockscreen: i.e. 10 digit pin for encryption and 4x4 pattern for lockscreen... Doing the microsoft trick (calling an issue a feature) I would say, this is increased swcurity... *lol*

Honestly: for best encryption user expirience and rom intergration, you are currently better of with ext4.

BTW: has anybody realized, that oos is resetting cache ALWAYS to ext4 on each reboot, no matter if you have changed it to f2fs? (Note: cache on f2fs works like charme with nlos.) I would be interested in the reason, why oos wants cache to be ext4.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] TheGatorade:
15.1 beta2 working fine with ext4 /data, Magisk beta and rooted Substratum. Can't wait for rootless OMS patch :D

This rom looking good, surprisingly stable for a beta