yashsingh1/xdaforums huggingface dataset:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
I confess i use - prepare yourselves - f2fs for my build host. Since I only have 2 SSDs, it makes sense. We will see soon, with transition to 4.10 kernel, if I run into troubles. But i doubt it. (using arch linux, they are fast on updating. Running 4.9.11 kernel right now. Will be 4.10 once point release hits.)

About the Service Provider. Would have never guessed you meant that. And I really have no clue. Ask a mod.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mumapizza:
It feels like the touch latency got worse after 24. update
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] lapapunk:
Can't confirm it. Clean flash with latest gapps. All good, smooth and fast.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Chuck Bartowski:
What camera do you use? OOS port with HAL1 enabler?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mumapizza:
Dirty flashed but it is smooth and fast like you said and no frame drops whatsoever but when i drag something on screen it just catches with my movement a bit late
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Update 20170225

Changelog:

update security patch level to 20170205

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

MD5: ced335fcdc5cfd41c00b5d51feb7eedf

Mirror: posting #2
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] molestro:
Has anyone with 2 factor authentication on their Gmail account successfully signed in on initial setup? I've had to use another phone with nfc setup the last 2 times I tried this rom because it would permanently stay waiting for text message verification. Official Lineage and most other roms do this successfully, just curious if it's just me.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Are you using gmail as system or as user app? What about inbuild email app - does it fail, too?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] molestro:
I'm talking about first flash setup, signing in to recover your information from your account. I believe it's through the Google Play Services and it sends an automated text message it automatically verifies. I think it may be privacy guard because the prompts I get on initial setup appear to be from privacy guard asking for permission to access things I don't get on the other roms. It's not a big deal, I can always sign in after the fact but I prefer to on initial setup. Gmail is always installed as a user app for me because I always flash Pico gapps but I have tried the recommended nano package and have the same results because no email is used in this process I'm talking about. Thanks for the quick response.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] DeadPicsel:
I use the built in camera app in LineageOS.

I did not know there was a OOS Camera with HAL 1 enabler. Do you have a like for it?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Ah, ok. Gmail was misleading me, I didn't get that you was talking of firsttime setup of google account.

That is really strange, because official weeklies and this rom do not differ in this regard.

Have you tried skipping google account and set ip up from settings to see if any peemission requests show up? What's in the logs?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Chuck Bartowski:
Yeah, of course.

Here you go: https://xdaforums.com/oneplus-3/themes/port-oxygenos-stock-camera-cm-t3451721

Install the apk and flash the HAL1 enabler zip.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Remember the hal1 enabler is a mod: don't report any cam bugs after using this zip, and be prepared, that buildin cam will act unpredictable.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] cmattern:
I've got in interesting mystery that I'd appreciate some help with.

Quick background: I started building Lineage myself on 20170101 to keep my HTC m8 updated until builds were automated and to work on correcting some seLinux issues preventing encryption which I was able to address. Also built Lineage for my Nexus 6p until I got my 3t and I began building from [MENTION=4405529]nvertigo67[/MENTION] 's repo. All this to say I know the basics but not to say that my problem might not be something VERY basic that I'm missing.

So starting about a week ago any ROM that I built from this repo fails to complete the boot. It will come up to the prompt for my PIN, accept it if I input soon enough but regardless of the decryption process, the boot will stop, screen will turn off and phone will not respond. Status LED goes out then comes back a solid white.

On the build process side I've gone as far as to start from scratch (new directory, fresh repo sync, etc.) using [MENTION=4405529]nvertigo67[/MENTION] 's changing only:

TARGET_UNOFFICIAL_BUILD_ID := nvertigo

to

TARGET_UNOFFICIAL_BUILD_ID := cmattern

and

WITH_SU := true

to

WITH_SU := false

[MENTION=4405529]nvertigo67[/MENTION] 's builds run fine as do the OFFICIAL unified builds so it's something about my environment. I've tried to collect a logcat via ADB but the shutdown comes before the phone starts dumping. Any suggestions on next steps would be welcomed.

My rationale for rolling my own is simply that I'm a flashaholic who craves a daily build and that I want to have the builtin su disabled so that I can use phh superuser which lets me put a PIN in front of any escalation.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] molestro:
Everything works fine skipping initial setup and signing in there, just trying the initial setup never actually sends the text message to continue verification. I'm at work now but when I get home I'll try to repeat the situation and get some logs.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
local_manifest is up to date? If you have roomservice.xml make sure, that the oneplus3t.xml is loaded by repo sync AFTER roomservice.xml by renaming the symlink to zz-oneplus3t.xml.

Have you tried building from branch 141-work?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Next misunderstanding on ky side: when you say you needed a second nfc-able phone to set it up, I thought it wasn't working at all. So you have at least two workarounds.

One more question: If you try firsttimesetup, doea the sms arrive at all?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] cmattern:
Will check on these, thanks!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] molestro:
The SMS never arrives. All other parts of the login process work just fine from what I can see. The secondary device set up through nfc works. Skipping initial setup then logging in gets the SMS to arrive as well. Just doesn't work automatically through the initial setup. When I use the official weekly it takes less than 30 seconds to receive and authenticate the SMS and the SMS appears in the notifications once I complete the setup. On the previous build and on the 25th build no SMS was ever received until I skipped the skipped the setup and manually verified the text message. When I grab logs I'll try to get the official weekly logs to compare.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] cmattern:
Progress:

I don't have a roomservice.xml so I moved past that one.

I tried building from work-141 changing nothing and was able to boot just fine, THANKS!

It occurred to me that perhaps, for some strange reason, this might be tied to my setting the use su to false so I'm trying another build with that set and will let you know what the outcome is
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
true. [MENTION=4405529]nvertigo67[/MENTION] and I always build from 141-work, meaning even though he pushes to cm-14.1 with much care, that branch is basically not tested most of the time.

also, if you do those changes to su and build id, do you remember to revert them before repo sync? if not, repo sync will skip updating device/oneplus/oneplus3t. i used to do all this manually, but by now, i just modifed my build.sh file to sed the changes in before building, and sed them out after building, so git does not see any changes and repo sync finishes without further interaction.

if something seems fishy, i check the "git status" of my_tmp/local_manifest/, device/oneplus/oneplus3t/ and vendor/oneplus/ and/or "git diff 141-work origin/141-work" (for manifest) or "git diff 141-work github/141-work" (for the others). i actually recently had a difference in the local_manifest git, where i couldn't find the source of and finally just deleted and checkout'ed that branch anew. that difference was related to blobs and - if for some reason you have the same - it might explain your behavior. (many if's there, but still worth noting)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
Another thing I watched more closely lately:

When I am done building, I still have a java process hanging in the background taking nearly 5gb of RAM. This seems to be after every successful build. Anyone else noticing this?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] cmattern:
Great info. I did get a good no-su build from work-141 and will dig into the other matters you mentioned tomorrow of Monday.

Thanks again to [MENTION=3044422]mad-murdock[/MENTION] and [MENTION=4405529]nvertigo67[/MENTION] !
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
This is the jack server:

ingo@adler /usr/local/src/cm14/device/oneplus/oneplus3t $ ps aux|grep jack|grep -v grep
ingo 17757 3.6 29.2 9967808 4791488 ? SNl Feb23 136:47 java -XX:MaxJavaStackTraceDepth=-1 -Djava.io.tmpdir=/tmp -Dfile.encoding=UTF-8 -XX:+TieredCompilation -cp /home/ingo/.jack-server/launcher.jar com.android.jack.launcher.ServerLauncher
ingo@adler /usr/local/src/cm14/device/oneplus/oneplus3t $

That's ok. Server is fired up, but never shut down. If you like - kill it.

Or just trust the linux memory management: meanwhile I did a kernel build with -j256 (easiest way to consume LOTS of memory at once) - now the resident part of the memory has been shrinked:

ingo@adler /usr/local/src/cm14/device/oneplus/oneplus3t $ ps aux|grep jack|grep -v grep
ingo 17757 3.6 0.6 9967808 110976 ? SNl Feb23 136:48 java -XX:MaxJavaStackTraceDepth=-1 -Djava.io.tmpdir=/tmp -Dfile.encoding=UTF-8 -XX:+TieredCompilation -cp /home/ingo/.jack-server/launcher.jar com.android.jack.launcher.ServerLauncher
ingo@adler /usr/local/src/cm14/device/oneplus/oneplus3t $
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Yes and no: on the one hand you are right (we build from 141-work all the time), on the other hand cm-14.1 is always exactly the last (not the current) published build. So for cm-14.1 is not only build tested, but also "running tested" for about 4 days by all of us.

[MENTION=5226211]cmattern[/MENTION]: can you give me the output of "git status && git branch -a && git lg1", please?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] cmattern:
On branch 141-work

Your branch is up-to-date with 'origin/141-work'.

nothing to commit, working tree clean

* 141-work

cm-14.1

remotes/origin/141-no-common-blobs

remotes/origin/141-work

remotes/origin/HEAD -> origin/cm-14.1

remotes/origin/cm-14.1

remotes/origin/cm-14.1-no-common-blobs

remotes/origin/oneplus/oneplus3t_N

* a5447ef - (6 days ago) Stop inheriting from shared graphics driver repository. — Nvertigo (origin/cm-14.1-no-common-blobs)

* 8abe124 - (13 days ago) op3t: use nvertigo's proprietary_vendor_qcom_binaries. — Nvertigo

| * 56fa7f6 - (9 days ago) Stop inheriting from shared graphics driver repository. — Nvertigo (origin/141-no-common-blobs)

| * aeb9505 - (13 days ago) op3t: use nvertigo's proprietary_vendor_qcom_binaries. — Nvertigo

| * dcf25e9 - (3 weeks ago) branches: use 141-work for Nvertigo's gits. — Nvertigo (HEAD -> 141-work, origin/141-work)

|/

* faeee26 - (2 weeks ago) Added a section about partitions and sizes to README — Sven Dawitz (origin/cm-14.1, origin/HEAD, cm-14.1)

* 8478606 - (3 weeks ago) README: fix an other derp. — Nvertigo

* 2aa20a9 - (3 weeks ago) README: fix an other derp. — Chuck

* c619ed2 - (3 weeks ago) README: current lineageos repo is about 46GB. — Mad-Murdock

* 24d94f6 - (3 weeks ago) manifest: add missing device/oppo/common; thanx to cmattern@xda. — Nvertigo

* 41d0d8b - (3 weeks ago) README: fix ugly derp: it's .repo/local_manifests; found by cmattern@xda. — Nvertigo

* 9098bda - (4 weeks ago) fix the curl call from sudo. — Nvertigo

* b05cb41 - (4 weeks ago) oneplus3t.xml: add linaro 64bit kernel toolchain. — Nvertigo

* db8f660 - (4 weeks ago) README: fix missing filename. From: cmattern@xda & mad-murdock@xda — Nvertigo

* 4a64aaf - (4 weeks ago) mark HOWTO as beta. — Nvertigo

* 22297f6 - (4 weeks ago) add in mad-murdock@xda's comments and ideas. — Nvertigo

* 79aa380 - (4 weeks ago) add gitconfig-example to README — Nvertigo

* 67e1ea3 - (4 weeks ago) add git aliases. — Nvertigo

* 621afba - (4 weeks ago) add my_build.sh to README. — Nvertigo

* 4d8a2e1 - (4 weeks ago) rename README.md to README. — Nvertigo

* 5b295eb - (4 weeks ago) add my_build.sh; add detailed build instruction to README.md. — Nvertigo

* 2119d59 - (4 weeks ago) local_manifest for building LineageOS with UBERTC/linaro and Snapdragon LLVM. — Nvertigo

* 1776b46 - (5 weeks ago) initial commit: set up local manifest to build OSS for oneplus3t. — Nvertigo (origin/oneplus/oneplus3t_N)[cmattern@clotho local_[cmattern@clotho local_manifest]$
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
I disagree. I stumbled over this, since it prevents a second build. Building with it running will exit the build process early with an out-of-memory error.

Killing the process and restarting the build always works for me.

I must confess, I am a bit low on overall memory, since my running chrome instance takes up about 5gb with all my tabs open. Still, i never had to close chrome after killing the resident java/jack process.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Interesting. My jack server gets reused and never grows above about 10 GB virt size. Since I only reboot my build host for kernel updates I'm sure I've done at least 20 builds with the same jack instance. Most properly differences of the dist's configuration (swapiness, lmk, limits,...). How much physical and virt mem do you have on your build host?

ingo@adler /usr/local/src/cm14/my_tmp/local_manifest $ free
gesamt benutzt frei gemns. Puffer/Cache verfügbar
Speicher: 16390616 6710048 5112588 216 4567980 9066740
Swap: 33347580 1012144 32335436
ingo@adler /usr/local/src/cm14/my_tmp/local_manifest $

Rule of thumb: for swap partition use at least twice of the sice of physical mem.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Please use code tags!

I will put cm-14.1 on level of 141-work today. I'm pretty sure your problemmwas, that you have build without qcom blobs due to an old manifest. Always update your local_manifest prior to repo sync.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
no swap, because no spinner.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Krissyzen:
hello. thx for the best 3t custom rom!

Ive a little request..

can u add Westwood or Westwood+ TCP algorithm, please? tried to install custom kernels but they don't work
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] cmattern:
Apologies for the lack of code tags, that was pretty bone headed... I'll avoid responding in the middle of the night to save readers eyes' and my dignity :)

As to updating my local_manifest, that would be a git pull correct? I took a look at my local_manifest from a broken and working build and don't see any difference

[cmattern@clotho ~]$ ls -l /home/cmattern/android/cm14.20170225/my_tmp/local_manifest
total 16
-rw-rw-r--. 1 cmattern cmattern 465 Feb 22 16:44 gitconfig.example
-rwxrwxr-x. 1 cmattern cmattern 574 Feb 22 16:44 my_build.sh
-rw-r--r--. 1 cmattern cmattern 2797 Feb 23 02:30 oneplus3t.xml
-rw-rw-r--. 1 cmattern cmattern 4491 Feb 22 16:44 README
-rw-rw-r--. 1 cmattern cmattern 973 Feb 22 16:44 zz-remove-unused.xml
[cmattern@clotho ~]$ cksum /home/cmattern/android/cm14.20170225/my_tmp/local_manifest/*
1850956302 465 /home/cmattern/android/cm14.20170225/my_tmp/local_manifest/gitconfig.example
2770749945 574 /home/cmattern/android/cm14.20170225/my_tmp/local_manifest/my_build.sh
350801190 2797 /home/cmattern/android/cm14.20170225/my_tmp/local_manifest/oneplus3t.xml
2287745527 4491 /home/cmattern/android/cm14.20170225/my_tmp/local_manifest/README
2649250846 973 /home/cmattern/android/cm14.20170225/my_tmp/local_manifest/zz-remove-unused.xml
[cmattern@clotho ~]$ ls -l /home/cmattern/android/cm14/my_tmp/local_manifest
total 16
-rw-rw-r--. 1 cmattern cmattern 465 Feb 25 08:44 gitconfig.example
-rwxrwxr-x. 1 cmattern cmattern 574 Feb 25 08:44 my_build.sh
-rw-rw-r--. 1 cmattern cmattern 2797 Feb 25 16:07 oneplus3t.xml
-rw-rw-r--. 1 cmattern cmattern 4491 Feb 25 08:44 README
-rw-rw-r--. 1 cmattern cmattern 973 Feb 25 08:44 zz-remove-unused.xml
[cmattern@clotho ~]$ cksum /home/cmattern/android/cm14/my_tmp/local_manifest/*
1850956302 465 /home/cmattern/android/cm14/my_tmp/local_manifest/gitconfig.example
2770749945 574 /home/cmattern/android/cm14/my_tmp/local_manifest/my_build.sh
350801190 2797 /home/cmattern/android/cm14/my_tmp/local_manifest/oneplus3t.xml
2287745527 4491 /home/cmattern/android/cm14/my_tmp/local_manifest/README
2649250846 973 /home/cmattern/android/cm14/my_tmp/local_manifest/zz-remove-unused.xml
[cmattern@clotho ~]$

but the fact that my rig was broken and now it's not is huge! Thanks!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
I want to stay as close as possible to lineageos kernel; this is not written in stone, but without a good reason, I will not add anything. If you expect to close the gap in wifi throughtput compared to oos, I have to disappoint you: allready tested, no difference.

I'm hunting for this gap since over 4 weeks to no avail; but different congestion algorythems are definetly not the source.

For custom kernels: all custom kernels are made for unified builds. unified builds need to hold the display drivers for 3 and 3t. Since originally they have a the same name, the unified builds use a hack to rename those files for 3t. custom kernels expect those non original altered filenames on a 3t device...

To use kernels for unified builds on this non-unified rom, you need to copy or move the blobs to their hacked file names.

Or you flash the uniblob-4.0.3.zip from Download section of OP.

DONT REPORT ANY ISSUES AFTER USING THIS ZIP!

If you think it's a rom issue, do a clean flash (don't forget to wipe system) and reproduce the issue before reporting.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Krissyzen:
it's not a ROM issue I think. thx for blobs, personally I don't care about custom kernels but Blu spark for example adds Westwood TCP algorithm and I wanted it (I was on oos with Blu spark for a month at least and (MB it's placebo!!) I think that speed and overall network stability was better on oos. meanwhile ur rom is so awesome, so good and I decided to stay with it. so that's why i asked u to add Westwood.. (even disabled by default)

thx for answer, great job
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] t-shock:
Any help would be appreciated
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Really don't know. Have you tried to use aosp llvm? Have you set up your system to save coredumps and examined the dumps with gdb? How about the suggestion in the log (filing a bug report)?

I've never seen this errors, so there is quite a propability your build environment isn't sane.

EDIT: do you use a vm? How much ram is assigned?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Krissyzen:
oops Ive another question..

does this ROM show bluetooth device remaining battery ℅ like iphone do? searching this feature for OnePlus :c

if not, any ideas how to enable?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] DeadPicsel:
I've just run a benchmark using AnTuTu Benchmark and it scored pretty low 130137. Is there any way to improve performance.

My phone seems fine most of the time, it's only now and again that it lags for a second and then performance seems to come back.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
https://xdaforums.com/oneplus-3t/development/rom-lineageos-14-1-t3547024/post70940838
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] rori~:
Don't know how it is on iPhone, but this ROM shows a battery bar (of connected device) next to Bluetooth icon in statusbar.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Mr_President:
Hey man! What Pixel Launcher zip are you using? Cause I found several. And on the build from 2017/2/24, longpressing Home button opened up both Google Now AND in app search on the homescreen. Even though I specifically set it up to do an in app search.

Does it do that for you too on the newer builds? Not sure if it's the zip I installed or a bug in the rom/LOS issue :silly:

PS: This did not happen on the rom from 2017/2/10 which I had installed previously. But that Pixel Launcher came from an Open-Gapps package with a gapps-config file setup.

Edit: Clarification. Nowadays the Google Now app is opened and search is engaged in it. When setting in app search on the older rom, it would just engage the searchbar that is on the homescreen.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] molestro:
So, things get curiouser and curiouser. Upon previously completely formatting my phone, I installed the official lineage weekly from the 23rd and setup a clean install on a completely empty phone. The automatic process for 2 factor sign in during initial setup worked flawlessly. I decided after a day to give the 25th build of this rom and this process didn't work. I decided I'd do clean installs on the official and this build to get logs to compare so we could figure out what's going on. Now every rom fails to complete this process. I've tried the official which worked previously, it fails, and now I've tried multiple different roms from multiple different build dates and no rom, even roms previously that worked, fail. I don't know what's going on but I've got other options to sign in and this rom functions spectacularly regardless. I think some stuff gets left behind from the previous roms even after a factory reset (without wiping data) so for the sake of posterity I am going to wipe everything once again and try this rom one more time to see if there's something to my theory. Wish me luck.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
If batt goes under 10 % one big core is disabled. It gets enabled again, if you load it to 50 - 60 %.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Forget about factory reset for one second. If you want to do a clean flash in twrp wipe dalvik, system data and cache. Prior to anything else go to twrp-home->mount and uncheck system. Flash rom and gapps nano from 20170120. Even if you don't like that version, try it.

If you wipe dalvik, system, data and cache, the only things left from previous roms is the firmware. Just to be sure you can flash the 4.0.3 firmware from OP. If really paranoid you can use wipe_misc script from twrp.

What really surprises me, is that the sms is entirely lost. If it wasn't processed on the phone, it still should be in messages after the failed login attempt. Have you checked your google account for failed logins and/or other messages?

Have you checked the devices logs?

On a side note: since the 2-factor login works if initially skipped and performed later from within the rom, I consider this more as an small anoyence then a show stopper.