yashsingh1/xdaforums huggingface dataset:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] endursa:
Just a heads up for everyone

I'm using the feb 25th update and I tried a substratum theme in legacy mode (pixel UI to be precise).

While it works flawlessly, even when applying a android system component, one can not dirty flash the newest build from march 1st because of bootloop problems.

I then discovered that this is a known problem with 7.1.1. and substratum in legacy mode when using android system overlays.

The only why to circumvent this problem is to skip the android system part or to wipe before flashing.

I am not asking for support, i know that this is my fault, just wanted to let others know!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] DeadPicsel:
Has anyone experienced any lag with the latest build. I'm getting really slow application loading and a lot of app freezes and force closes.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Kris Chen:
At least, I didn't after dirty flash 0301.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Krissyzen:
I am not... it was a bit laggy for a few hours, then okay.

MB u should try to reflash with wipes?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Mayex:
How is camera quality of this rom compared to OOS?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
:D

For wiping (or better: clean flashing): I suggest you wait a bit. I've updated the blobs to OpenBeta3 (7.1.1 blobs instead of 7.0). I'll sync that now and will do a clean build. So chances are good, that there will be an update wthin 3 or 4 h. With nearly 400 blobs changed, it's a good time to clean flash that version... ;)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Krissyzen:
crap without stock camera mod.

with mod same but slowly
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mumapizza:
Its not crap tbf its decent; set quality to high in the camera app
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] t0pg3ar:
How do I make sure I am completely up with your repos? This is the path I follow:

1. git pull on Android/cm14/my_tmp/local_manifest, stating that git can ignore my edit of my_build.sh

2. repo sync

3. ./my-build in Android/cm14/

That always gives me a compiled ROM, but is it the newest one as well?

With that said, I'm going to (finally, I know) root 'n rom my device tonight, but I'm quite new to the whole encryption thingy. If I want to install this ROM, and I am on OOS 4.0.3 and using the pattern for encryption and fingerprint scanner for unlock, do I have to change anything about that before I install TWRP and nuke /system, /cache and /data?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] xpissio:
Can I ask one thing [MENTION=4405529]nvertigo67[/MENTION]? If OP didn't released updated sources of 7.1.1, how did you do? (It's only an information, not a critic)

:)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Update 20170304

Changelog:

blobs: update to 7.1.1 (OxygenOS OpenBeta3)

audio: update acdb ids for 7.1.1. — nvertigo (nvertigo/141-work, github/141-work, 141-work

blobs: add ome Camera postprocessing binaries. — nvertigo

misc updates from OxygenOS OpenBeta 3 (7.1.1) — nvertigo

TZ: update trust zone to TZ.BF.4.0.1-85373. — nvertigo

init: update build fingerprint to match OxygenOS OpenBeta 3 (7.1.1) — nvertigo

blobs: pin libuiblur.so. — nvertigo

op3: Stop inheriting from shared graphics driver repository — dianlujitao

Revert "msm: camera: Comment out upstream changes to get camera working" — nvertigo

misc: fpc1020: Increase fingerprintd nice value when screen is off — Sultanxda

ANDROID: ext4 crypto: Disables zeroing on truncation when there's no key — Michael Halcrow

UPSTREAM: udp: properly support MSG_PEEK with truncated buffers — Eric Dumazet

UPSTREAM: l2tp: fix racy SOCK_ZAPPED flag check in l2tp_ip{,6}_bind

ANDROID: mnt: remount should propagate to slaves of slaves — Daniel Rosenberg

ANDROID: sdcardfs: support direct-IO

ANDROID: sdcardfs: implement vm_ops->page_mkwrite — Daniel Rosenberg

Revert "sdcardfs: Flag files as non-mappable" — Bruno Martins

This is large step. If you're not clean flashing(*), wipe dalvik, system and cache (don't forget to umount /system before continuing to flash) and reinstall the VERY SAME version of gapps you used initially. Wipe data for Camera!

Keep in mind: this rom has updated firmware. TZ is increased.

(*) It's a good moment to clean flash!

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

MD5: 03ca5b07da9cf2fa7dd15419f6025af6

Mirror: posting #2

OP is updated for uniblob and firmware.

Happy flashing!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
local_manifest: if you want to build with updated blobs use 141-work (you need to flash firmware for OpenBeta3 from OP) - if you want to build with updated blobs and updated firmware use firmware/141-work.

fs_crypto: I use pin instead of pattern - but what you describe is exactly what I have done when going from 4.0.1 to this rom.

We devs have a cyborg rsync build in - which allows us to receive new sources mentally... *lol* SCNR

lineage team (in deed it's mainly [MENTION=5091734]dianlujitao[/MENTION]) is doing a great job in keeping kernel/oneplus/msm8996 up to date with caf and oneplus. If oneplus (please keep in mind OP means Opening Post) doesn't release source, no one - neither [MENTION=5091734]dianlujitao[/MENTION], me or anybody - can merge something. I've pulled blobs and some settings from OpenBeta and reverted a commit, that was needed for the old blobs... (honestly I guessed the last one - and it works...)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] xpissio:
Oh ok, thanks for the answer. (and for builds too!)

Only last things, have I to flash the OpenBeta 3 firmware for the new build?

And by reading the OP, I can't flash stock OpenGapps, true?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Krissyzen:
for me even stock is bad..so.. no offense. with stock mod it's barely okay.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] DeadPicsel:
Have there been any improvements to fingerprint scanner or performance the new build with 7.1.1 blobs?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Schrotty35:
Only gapps from 20.1 will work correct? I have read this on first Post. Why can not use a newer version?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] dannycardoz92:
you can but as mentioned in the op there are many reasons why you should stick to the listed ones. refer to post 4
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Never had any issues with fps on this rom - there is nothing to improve.

The same goes for performance: I never expirienced the lags and fcs you mentioned...
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
These are two... ;)

builds with the string "firmware" in it's name come with firmware included.

You can - I just don't support installations with those. But I see no reason at all to do so: it will give you only disadvantages with exactly NO advantage.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mumapizza:
Where is one-hand ui? Do we have this?

It becomes laggy below 15% or 10% battery
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
What is one-hand ui? If it is in laos, it's in this rom, too - if laos doesn't have it, or if it's disabled by default, we don't have it.

>=10% one big core gets disabled. That's the oneplus3t lineageos default behavior.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] xpissio:
They merged it 22 hours ago. (https://review.lineageos.org/#/c/162175/)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Can't see added setting in that commit. What is one-hand ui? What should it do? How is it activated, if there is no settings in the commit?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] xpissio:
It's that feature that make screen smaller.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Mayex:
With mod quality is the same as on OOS but but app is slow, or quality with mod is same as without mod?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
Is it just me, or do you also feel the rom handles smoother? I mean, it was smooth all the time, but with the new blobs it somehow feels smoother. Not sure if I only imagine that.

TWRP will ask you for a password. If you use pattern, it translates like this:

7 8 9

4 5 6

1 2 3

So you pattern is basically a number which twrp will expect you to enter. I personally would recommend a 10+ digit PIN number.

In case you didn't choose "ask for password on boot", the password you have to enter in TWRP is "default_password"
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] xpissio:
Flashed the latest build, all working nice!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Just Passing By:
Deleted
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] SourPower:
It's for small handed peeps :cyclops:

I guess it kinda outs your phone into "window mode" with a bigger black dead surrounding around on top, top left and left side of the screen (if using right hand) vice versa for lefty.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] nadejo:
Im kinda confused with that "unmount system thing" before rom install. Do i need to remount it before flashing gapps or that "laos su addon"?

And should i stay on 4.0.3 fw or flash the new beta firmware because of the new blobs? I know its mentioned in the op but i thought maybe its not updated because the latest update isnt listed there aswell.

Thanks
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] TheFrozen4:
Or, hm, you know, toilet quality time. :cool:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Krissyzen:
quality without mod isn't okay for me (worse than oos)

with mod quality is the same (don't forget to flash mods HAL) as stock but after shot u need to wait a few seconds while photo is processing (I don't remember processing on oos..) burst mode works fine, but quality..well quality of burst mode is crappy even on oos I think.

so camera is VERY important to me and I can say that with mod it's okay

also I can see in change log that nvertigo67 updated some camera blobs... wanna test, MB it's the same as on oos without mods
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Hihihi... this is so great, ther is NO setting. But reading the code makes one smart:

Settings->Buttons->Home-Button->longpress: set to either left hand or right hand. After that longpress home-button.

The more I've read the source, the broader my smile gets... When I saw the one-hand ui the first time, I had to laugh out load. Tastes differ (and that's good), but I would call that function "Castration Of a GreatmDisplay"... *lol* Never mind, I hope you enjoy that function!

(even multi win is working in that mode... ;) )
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
After wiping system twrp mounts system. This leads to problems with flashing. So after wiping system, go to twrp-home, klick on mount and uncheck system.

The zips with the string "firmware" in it's name contain the firmware. I answered that many times allready!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] DeadPicsel:
That's dead strange. Something has changed as I clean installed the latest ROM and OMG it's as smooth as silk and as fast as a Supercharged Mustang.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] nadejo:
Not complaining here but i can see no difference in performance or batterylife compared to unified official builds. I played some games and tested the scrolling smoothness in many apps. And also loading times in many apps/games. I did this with and without latest ex kernel on official and this build with allways the same tweaking. And its all the same performance wise. Anyways thanks for the efforts. And i dont want to offend the dev. Im just beging honest- there is no difference. Ive also noticed some minor glitches when trying to pull the notif. drawer. And fingerprint Sensor isnt flawless aswell, not better than in official builds. You have to press it multiple times sometimes.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
I confess it makes little sense on our device -at least for people with decently sized hands- but on phablets and tablets it might make sense - especially for writing with a swype-style keyboard.

That always bugged me. No swype-style keyboard has a decent solution for big screens and one-handed swyping. This might be a good solution, especially since you can switch in and out of that mode easily.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Experimental kernel

Propably you have read this article: https://www.xda-developers.com/onep...s-with-conservative-governor-for-some-reason/

Sadly laos stock kernel has conservative governor disabled. The attached boot image includes the very same kernel as the last build, but with conservative, ondemand and userspace governors enabled. The included init.qcom.power.rc is patched, so conservative governor is uswd for big cpu cluster. If you want to check mario's advice just flash attached boot image.

Happy flashing!

boot-opt3-lineageos-conservative
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] wistlo:
Does this mean I can use a kernel manager (such as this) to experiment in real time with different governor settings? (Mostly interested in comparing interactive and conservative in real time. My experiments with frequencies, schedulers, etc. on other phones never yielded any improvements.)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
The article mentions only OOS. Is this applicable to LAOS as well?

[MENTION=3242790]wistlo[/MENTION] yes you can use a kernel manager app for that
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Kris Chen:
Report back after flashing this boot image: It was a little laggy when 1st scrolling in any opened app. After using a period of time, it's getting more smoothly and without too much difference if comparing to interactive mode.

Reminder for those before flashing this boot image: You have to flash SuperSU again after flashing boot image if your phone was rooted.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] wistlo:
camera improvement [updated 2017-03-07]

My 3T camera appears to be working normally with this update, after a couple of weeks of suffering with intermittent problems.

Before this update, the 3T rear camera would intermittently stop focusing or stabilizing. I was convinced this was a hardware issue.** After taking the advice to clean flash 20170304, now I cannot make the camera focus fail!

[FIXED] 20170307 - removed ported camera before flashing, built-in Oneplus camera works as expected The only issue I have found is that photo flash does not work using this port of the OnePlus native camera. The flash works on that camera for video, and will illuminate to focus but fails to fire. The OnePlus camera's "HQ" mode never worked correctly before I installed this new ROM and firmware version.

All other cameras (Open Camera, FV-5, Google Camera) work as expected, including flash and focus. . All of them (as well as scanner and bank deposit apps) previously were failing to focus 50-75% of the time. Still true, 20170307.

Notes:

Regarding clean flash: Google Play and Titanium make clean flashing barely more laborious than a dirty flash. I used to avoid clean flashing whenever I could, unless specifically required to clean flash. For this update, I took the recommendation. Unlike the bad old days, this did not add an extra half-day to get the phone configured.

** I was SO convinced this was bad hardware, in fact, that I purchased a second-hand HTC M8 to use as daily driver while my OnePlus was at the shop for warranty service. (I would have restored the 3T to stock before sending and tested the camera, and probably would have realized I did not have a hardware problem). It's OK as we could use a backup daily driver here. I could also sell it locally with Lineage installed for more than I bought it (or at least try to). The M8 is my wife's current phone and is aging very well, still very responsive and it's well-supported by the Lineage OS community.) Another cheap backup option that runs Lineage is the Samsung Galaxy S III, which allegedly is the device Donald Trump still uses (though I somehow doubt he's unlocked and flashed it to current security standards). I also have Lineage running on a Moto G LTE (Peregrine), but messed up SIM card slot by using a nano-to-micro adapter, a no-no with that Moto series.)

Kernel: I am also now running the conservative-enabled kernel (details on this here).

---------- Post added at 10:14 PM ---------- Previous post was at 10:03 PM ----------

My 3T was rooted with the Lineage OS extras addonsu-arm64-signed.zip, and I did not need to reflash that after updating the boot img. (not using SuperSU here). Edit: Not necessary with this ROM, as it's already rooted.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
That's the question... ;) I don't know but I want to know - so I made the image.

Exactly. You need to reflash everything, which modifies the ramdisk of the boot image. SuperSU is one of them.

This rom is build with superuser - no need at all to flash addonsu.

[MENTION=535343]all[/MENTION]: Thanx for the feedback.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] luisangel89:
Ok guys question. I've flashed the latest build and I know that under the known issues it says decryption is not working for TWRP. I tried to reboot into recovery and my 4 digit PIN didn't work. I rebooted the phone and thank God I was able to reboot normally. How can I reboot into recovery of the password/PIN is not working in TWRP? I'm confused. Any help would be great.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
The known issues talks about encrypting a not-encrypted /data partition. Not what you say.

About your issue, I would GUESS you selected no on the question "ask for pin on boot". If so, you encryption password is "default_password" (without the ") - enter this in TWRP and you should be fine.

On a side note: Having default_password as your password on an unlocked phone is not very smart. better choose yes on the "ask for pin on boot" question.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] xpissio:
I have to report one bug, sometime LiveDisplay doesn't work, and I have to reboot. Am I the only one?

Inviato dal mio ONEPLUS A3003 utilizzando Tapatalk
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] cmattern:
I seem to have another NBSIW (Newbie Builder Self Inflicted Wound).

Updated per the updated OP re: OpenBeta3 and the 20170304 build by [MENTION=4405529]nvertigo67[/MENTION] works great. HOWEVER building on my own and pulling from firmware/141-work I now end up with graphics issues that result in (at least) an invisible pin input keypad, the prompt and input window are visible, just no keypad. I can get the pin sequence correctly (after a few tries) to decrypt but again I'm prompted for the for the initial unlock after full boot with an invisible keypad. Not generally usable and clearly preventable.

Edit: In the process of troubleshooting I've gone as far as starting my build environment from scratch starting at line 78 of https://github.com/nvertigo/local_manifest/blob/cm-14.1/README

Any clues would be welcomed and I hereby submit myself as an example to others.... :)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
You need some cherry-picks to get the rom play nicely with 7.1.1 blobs. Look at my_pick.sh.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
I have the same issue - but for months and even before this ROM. It's something I wait to be fixed upstream.

Workaround is to set it from automatic to night and back to automatic in the morning. At least a bit easier than rebooting.

Big fan of <2500 color temperature a few hours before I go to bed. Easy to achieve on PC on either operating system.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] luisangel89:
Thank you for you response. What in end up doing was under security directed "Remove separate encryption password." I rebooted into recovery and my 4 digit PIN that in use when I reboot my phone won't worked!

---------- Post added at 04:34 PM ---------- Previous post was at 04:31 PM ----------

It WORKED. I'm not sure why stupid auto correct
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] D3m0x:
Hello guys

I have a problem with this ROM.

Everytime I go into recovery and I flash something, the ROM comes totally wipe after reebot, once and once again and I have to setup all over again.

Previously I was using Freedom OS 1.3
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Krissyzen:
I think it's not ROM issue. are u using latest 3.0.4-1 TWRP? I flashed stock camera HAL and it's okay :/ (I am using latest TWRP, latest ROM, also my phone is not encrypted)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] 186Y:
I had the same problem a few builds back. You need to use twrp-3.0.4-1-oneplus3.img
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] ram4ufriends:
Use latest TWRP or format to ext4
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] nadejo:
Its no f2fs issue. Had the same. You have to format all using the recovery also internal sd. Do this only if your rom wipes your storage at bootup
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] D3m0x:
I just did the same as you mention here.

I wipe everything including int.sd

I flashed the last TWRP 3.0.4-1 and then flash the ROM again.

Now everything seems to be working fine.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Mayex:
Is camera quality on par with OOS after camera improvements?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] nadejo:
I think there are no issues with f2fs using latest recovery.

The problem is many people wipe the internal sd the first time using twrp when they switch to ext4 and think the problem was f2fs. Staying on f2fs is safe as long you format the storage using latest twrp recovery. I never had any issues with f2fs.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
Thats not true. Once you have random files disappear after rebooting/installing a rom, your filesystem is broken. Formatting does fix this (not wiping though, since it only deletes files), but if you use different roms with different f2fs implementations, it might happen anytime again.

So, what to do in case you loose data out of the blue?

If you only use one Rom, a simple wipe->advanced wipe will solve the issue.

If you tend to use different roms the only secure way is switching to ext4.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Update 20170307

IMPORTANT: If you have installed the package com.oneplus.camera (i.e. OOS Camera port)myou need to uninstall that prior to flash this build!

Changelog:

ship with OnePlusCamera and OnePlusGallery

March security patch

enable ondemand, userspace and conservative governors

overlay: disable camera_restart_preview_onPictureTaken. — nvertigo

op3: Update for stock 7.1.1 blobs Patchset 6 — dianlujitao

defconfig: enable conservative, ondemand and userspace governors. — nvertigo

use BUILD_PREBUILT for OnePlusCamera, OnePlusCameraService and OnePlusGallery. — nvertigo

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

MD5: 8d707932169b9c907831058c662f490b

Mirror: posting #2

Happy flashing!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Uninstall oos camera port and flash 20170307. OnePlusCamera and OnePlusGallery are included in the rom now. Flash, hdr, hdra and hq are working.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] xpissio:
Thanks for the update, I really appreciate OOS camera and gallery, and March patch too. :)

Already flashed it.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Since I lack a "photographic eye" I would be interested in feedback on the picture quality of OnePlusCamera (especially compared to OnePlusCamera on OOS).
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Egor Gunko:
Good day everyone, are builds stable enough as daily driver, is volume slider works, any bugs, how's performance?

And is there still red dm-verity label at start?

thanks :)