yashsingh1/xdaforums huggingface dataset:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
Build 20170411

Disclaimer: Since [MENTION=4405529]nvertigo67[/MENTION] is busy for the time being, he asked me to build and upload new ROM versions every few days.

It's that time again to update your ROM. No side-effect reported from last test-build, so we consider it stable.

Changelog

No changes, except updated to latest LaOS sources

Note on firmware: This build requires OOS beta 4 firmware. If you get an TZ error while flashing, make sure to flash OOS beta 4 firmware first. It was included for users having flashed lineage-14.1-20170401-UNOFFICIAL-nvertigo-firmware-oneplus3t.zip.

ROM: lineage-14.1-20170411-UNOFFICIAL-mad-murdock-oneplus3t.zip

MD5: 6b76cd3366c9beb3df1aa30d6a8deb2a

Mirror: posting #2

Happy flashing!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
you mean the one from open beta 4? good idea - guess [MENTION=4405529]nvertigo67[/MENTION] has missed that part.

He is quiet busy currently, but that part should only be copying over some files. Next build might have it in.

Thanks for reminding!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Vipeout:
I have the test build installed, is there any difference, i.e. Should I flash this build over the test build?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
Sure. It is updated to latest LineageOS sources, meaning it gets all the love that the LaOS devs merged the last 4 days.

It just has no 3t specific changes, like kernel or device setup.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] yannmrt:
But is not snap that is normally with this and LOS ROM? Now I get confused
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
Yes, but he added the OOS cam. Read the OP.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] rookey:
I currently have the official LineageOS 7.1.1 ROM on my phone ... should I be able to flash this one without losing all my data, or could I flash it over the existing one?

The ROM sounds awesome, I would love to get rid of as many Google apps as possible on my phone..
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
You're not going to lose any of your data, but you can't dirty flash either. Just wipe dalvik, cache, system and data, then flash this rom
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] themcfly:
Just a quick question if anyone can answer. I'm trying out both the official and this rom for my 3T.

I saw in the official that video/audio call on Facebook Messenger did not work, and searching the topic multiple suggested to change the SELinux policy to Permissive. Trying out your rom, I see that indeed the calls work, but the policy is still Enforcing. What gives? Was any specific commit added to fix the messenger calls? Thanks in advance.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
Probably, yes. I know, [MENTION=4405529]nvertigo67[/MENTION] put a lot of work into fixing selinux permissions from both LaOS and underlying OOS. Probably fixed whatever was causing that issue doing so.

Hard to tell you which commit. It's way easier to create the error on OOS (or whatever rom) and parse the log to get the faulty policy.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Oh, well, kids, indeed you are confused... *rofl*

It's all in the commits... I don't use "ported oos camera", I have added the blobs for oos camera to my vendor git. So each time I update the blobs from a new oneplus release (ob4 atm), the cam is also updated:

ingo@adler /usr/local/src/cm14/vendor/oneplus $ git lg1 -- oneplus3t/proprietary/priv-app/OnePlus*
* d29bf52 - (vor 12 Tagen) Update all blobs from OxygenOS OpenBeta 4. — nvertigo (nvertigo/firmware/141-work, github/firmware/141-work, firmware/141-work)
* fe1474b - (vor 4 Wochen) update all blobs from OxygenOS 4.1.0. — nvertigo (nvertigo/firmware/cm-14.1, github/firmware/cm-14.1, firmware/cm-14.1)
* 6ad015b - (vor 5 Wochen) add OnePlusCamera, OnePlusCameraService, OnePlusGallery and required libs from OxygenOS OpenBeta 3. — nvertigo

For selinux/sepolicy - it's one of these (not only the fb commit):

ingo@adler /usr/local/src/cm14/device/oneplus/oneplus3t $ git lg1 -- sepolicy/untrusted_app.te
* 60d47c7 - (vor 5 Wochen) sepolicy: address another bunch of denials. — nvertigo
* 0ec4552 - (vor 5 Wochen) sepolicy: address a bunch of new denials. — nvertigo
* 517976f - (vor 8 Wochen) sepolicy: address fb manager fc caused by denial. — nvertigo
* dc696ad - (vor 9 Wochen) sepolicy: address some more denials. — nvertigo
* fb315b0 - (vor 2 Monaten) sepolicy: address various denials. — nvertigo

I guess the sum of these rules

ingo@adler /usr/local/src/cm14/device/oneplus/oneplus3t $ git diff laos/cm-14.1 141-work -- sepolicy/untrusted_app.te
diff --git a/sepolicy/untrusted_app.te b/sepolicy/untrusted_app.te
new file mode 100644
index 0000000..889d142
--- /dev/null
+++ b/sepolicy/untrusted_app.te
@@ -0,0 +1,9 @@
+allow untrusted_app rootfs:dir { read open };
+allow untrusted_app sysfs:dir read;
+# address fc due to denial for fb manager
+allow untrusted_app lock_settings_service:service_manager find;
+
+allow untrusted_app debugfs:file getattr;
+allow untrusted_app proc_stat:file { open read };
+allow untrusted_app sysfs:file read;
+allow untrusted_app tombstone_data_file:dir search;
ingo@adler /usr/local/src/cm14/device/oneplus/oneplus3t $

Yoda says: "Use the source, Luke."
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
Any changes with OOS 4.1.3 firmware?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] gr546jmn5:
So I'm coming from OOS 4.1.1 - I was wondering, does this rom successfully use VoLTE and VoWiFi? I see no icons for that.

Also, I have several apps set to authenticate via finger print sensor, yet it's either glitchy now or maybe I'm not doing something right, 7/10 times it brings up Google Assistant rather then just identifying me to whatever app is waiting for my fingerprint. What would be the easiest or safest method of correcting this?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] 186Y:
I had this same problem so I changed Google Assistant to double tap home button instead of single hold.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
I'm not sure if we want to use 4.1.3 over ob4: telling from the original Oneplus changelogs 4.1.3 doesn't have the bugfixes (i.e. touch latency, improved EIS) from ob4. I have not the time atm to check this - perhaps they just copied the 4.1.1 changelog and forgot to add latest additions; on the other hand oos 4.1.3 is missing features from oos ob4 (i.e. reworked launcher)...

Feel free to check on precompiled binary level, whats going on in 4.1.3 and tell us.

I use neither - so I can't tell you for sure. But I have added this commit on 20170125.

Will be fixed in next build: https://github.com/nvertigo/android_frameworks_base/commit/9c1451948436cdaa3e8635b1f2f23bbe17691c0b
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
Would love to do it myself. Can you tell me how?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
For each of 4.1.1, ob3 and 4.1.1 oos zips: unzip, change block sparse image to mountable system.img (sdat2img.py) , mount system.img, copy (cp -a) content of mounted system to an empty dir (in this dir initialize git, add the copied files and store it in a branch, which name should refer to the oos version). Now git diff 4.1.1 to ob4 and 4.1.1 to 4.1.3; compare both outputs file by file. For each different file (not the diffs, but the diff of the diffs) try strings, readelf, java or apktool on the different files (strings and readelf for unix bins and shared objects; java for java files; apktool for apks) to tell what the differences are. Have fun and don't allow the characters to blur in your vision... ;)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Compare changelog for 4.1.3 vs. ob4

The touch latency fix and the EIS improvement seem NOT to be in 4.1.3. I still think we are better of using ob4 blobs.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] wistlo:
Fingerprint authentication does not cooperate with home-longpress. Assign home-longpress to no action if you are using fingerprint reader.

I did that and now successfully use fingerprint authentication. Amazing how addictive and convenient it is.

EDIT: i missed this before I posted this, sorry. Fix is coming.

The level of ongoing refinement in this optimized ROM is impressive.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Workarounds like this wwill not be nesseccary after next build. See above.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mcdachpappe:
[MENTION=4405529]nvertigo67[/MENTION]

first of all i want to thank you for your documentation at your git repo. i have now successfully built my own environment and synced already all the neccessary files to my virtual machine.

but im not able to build lineage completly and im currently running out of ideas and i hope that you could help me out or give me a hint how to solve my problem (make.log see below).

ive setup ubuntu 16.04.02 and installed openJDK 1.8 on my virtual machine - sync runs fine.

within building via ./my-build (i followed closely your readme) it fails (while buildingprocess at 5%) with the following error: #### make failed to build some targets (02:24 (mm:ss)) ####

do you got any advice? or do you need more informations? it would be great if you could help me out.

//EDIT:

tried building now several times and it gets stuck at different spots. my current error is now:

[...]
ccache: error: execv of ../../../../../../prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-5.x/bin/aarch64-linux-android-gcc failed: No such file or directory
[...]
ninja: build stopped: subcommand failed.
build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1

//EDIT2:

nvm - its currently building. i dont know what exactly did the trick, but i did a fresh setup of my environment but this time i installed these

bc bison build-essential curl flex g++-multilib gcc-multilib git gnupg gperf imagemagick lib32ncurses5-dev lib32readline6-dev lib32z1-dev libesd0-dev liblz4-tool libncurses5-dev libsdl1.2-dev libssl-dev libwxgtk3.0-dev libxml2 libxml2-utils lzop pngcrush rsync schedtool squashfs-tools xsltproc zip zlib1g-dev

and i installed java-jdk7 (just in case this time).

now im my buildingprocess is around 11% (never have been that far yet) and it keeps running :)

i used this source to build my environment.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
You are building unified from the official laos gits, now. No 3t optimization, no UBERTC, no SDCLANG, no magisk, no oos cam, no selinux fixes. I don't mean to offend you, but would you please find some other place, to discuss that, because it's not about this rom.

That being said, let's go back to your original question: It seems to me, you have messed up the usage of local_manifest. If you want to build THIS rom, stick to the README. After repo sync, check if all the gits from my local_manifest/oneplus3t.xml are in place. I.e.:

ingo@adler /usr/local/src/cm14 $ repo sync prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-5.x/ prebuilts/snapdragon-llvm/toolchains/llvm-Snapdragon_LLVM_for_Android_3.8/prebuilt/linux-x86_64
Fetching project nvertigo/llvm-Snapdragon_LLVM_for_Android
Fetching project nvertigo/aarch64-linux-android-5.x
Fetching projects: 100% (2/2), done.

ingo@adler /usr/local/src/cm14 $ ls -la prebuilts/gcc/linux-x86/aarch64/ prebuilts/snapdragon-llvm/toolchains/llvm-Snapdragon_LLVM_for_Android_3.8/prebuilt/
prebuilts/gcc/linux-x86/aarch64/:
insgesamt 20
drwxr-xr-x 5 ingo ingo 4096 5. Apr 20:29 .
drwxr-xr-x 6 ingo ingo 4096 2. Aug 2016 ..
drwxr-xr-x 7 ingo ingo 4096 30. Jan 18:35 aarch64-linux-android-4.9
drwxr-xr-x 9 ingo ingo 4096 5. Apr 20:29 aarch64-linux-android-4.9-kernel
drwxr-xr-x 9 ingo ingo 4096 5. Apr 18:10 aarch64-linux-android-5.x

prebuilts/snapdragon-llvm/toolchains/llvm-Snapdragon_LLVM_for_Android_3.8/prebuilt/:
insgesamt 12
drwxr-xr-x 3 ingo ingo 4096 5. Apr 20:22 .
drwxr-xr-x 3 ingo ingo 4096 27. Jan 10:22 ..
drwxr-xr-x 9 ingo ingo 4096 5. Apr 20:22 linux-x86_64
ingo@adler /usr/local/src/cm14 $

These commands need to be executed in the root of your build tree. If the outputs differ, please give me the output of

ls -la .repo/local_manifests/

If the relative path is problematic for your environment, this may be related to the build machine: native or vm? Posix compliant fs (i.e. ntfs, cifs import and some others are NOT sufficient)?

For java: I use icedtea 3.3.0 to build OpenJDK 8. (On gentoo each and every package is build from source - any precompiled OpenJDK 8 package should do.)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mcdachpappe:
you got me wrong. i said that i used the source mentioned above from the official lineage to build my environment (needed libs and java version and so on for my fresh vm).

and to build the rom itself im using your stuff from your repo and so on. ive set up everything like you mentioned in your readme.

but thank you doe your answer
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] rookey:
Just a small question: what is the "OxygenOS ob4 firmware" in the 2nd post for?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Sorry, dude. When I read "source" my brain resolves that to source code - not to source of information... expectation and perception put brains in a tunnel... ;)

??? For flashing - of course.

Please reread OP. It's explained there. ob4 refers to OpenBeta4 - that's the nessecary firmware for current builds.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
Hey guys,

I am late with building. Was busy playing Diablo 3.

Expect a up-to-date build tomorrow. Probably.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] yannmrt:
You have the right to have a private life and do what ever you want. Even though we are waiting for your build, take your time and enjoy the weekend ;)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
It seems to me that eversince I flashed your builds, LiveDisplay's automatic function doesn't work.. again.

It refuses to switch to night mode (I have location enabled, just like on prev. builds), though when I reboot, it does work for that particular night. Any ideas?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mcdachpappe:
same for me.. after reboot the night mode works for 1 night and then ive to reboot to get it working again.

im on latest mad-murdock build 20170411
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Since [MENTION=3044422]mad-murdock[/MENTION] and me build from the very same sources I doubt it's a problem of his builds. This issue is reported in the official thread as well. It's also not limited to oneplus' devices: https://www.reddit.com/r/LineageOS/comments/5slslc/livedisplay_not_working_for_time_of_day/ Sadly we have to wait for a upstream fix. Meantime you could try to work around with tasker at fixed times.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
Wasn't trying to say that murdock screwed something up, just noticed that I was having this issue again around when he started putting up builds.

Beforehands, using vertigo's builds, LiveDisplay was a lot more consistent - worked for 3-5 days in a row, then not for a night, and again for a good couple of days.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
UPDATE android-7.1.2_r2 base

REVOKED: safetynet broken

Build 20170415

This build requires firmware 4.1.0 or later. OpenBeta 4 (aka ob4) firmware is HIGHLY recommended!

Changelog:

op3: Remove fpc delays after authentication cancelled — dianlujitao (HEAD, nvertigo/141-work, m/cm-14.1, github/141-work, 141-work

init: update fingerprint to 7.1.2. — nvertigo

init: set fingerprint to OxygenOS OpenBeta 4. — nvertigo

Upstream has broken the complete git history for the kernel (properly because of a forced push) - reapplied all rom specific patches. Since the history was destroyed, I can't tell what was added upstream. Diff of all changes: https://github.com/nvertigo/android_kernel_oneplus_msm8996/compare/cm-14.1...nvertigo:141-work

ROM: lineage-14.1-20170415-UNOFFICIAL-nvertigo-firmware-oneplus3t.zip

MD5: 59fdeb9d839613bcce36dfee38d32c53

Happy Flashing!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
God bless.

Also, mind fixing the link? :D

(https://drive.google.com/open?id=0B_f72wz8rwc6VFJ0LWdMdUw5cU0)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Fixed. Thanx.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
OT: for the native English speakers: do I highly recommend something, or do I strongly recommend something? If both is possible: which one is more forcefull? Thanx.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
I'm no native, but I pay attention to stuff like this, also learn them in school, both are possible, and "strongly recommend" is more forceful.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] SourPower:
Strongly is more 'forceful' haha
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] cmattern:
[MENTION=4405529]nvertigo67[/MENTION] I am a native English speaker. The difference is subtle but in my opinion [MENTION=7264930]Lada333[/MENTION] is correct.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Stefa.:
Thanks for your always awesome work ;)

A little feedback: I have tryied to clean flash (twice) this build + gapps (op ones) and I experienced continuosly a crash of the Lineage OS "configuration procedure app" after having selected the language "Italian" and then "Configure as new device" option.

Reverted back to 20170401 build and everything works perfectly.

Hope this could help.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
My bad: Since I dirty flashed, I missed thinking about gapps. LineageOS was updated to 7.1.2 - this could have broken installation with 20170120 gapps. You could try dirty flashing.

Since I'm low on time, I don't know, when I'll find the time to check and test. Would someone be so kind to check a clean flash with current nano package, please?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] PerryRhodan:
Hey guys.

Since the latest build I am not able to pass SafetyNet.

I always get a profile mismatch.

No matter if I perform a clean flash or flash dirty over an older version where the check passes successfully.

I set the hide button...

Thanks!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] ArchGalileu:
Me too, can't pass safety net...
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Confirmed. Will look into it.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] t-shock:
I followed the guide for the microG but Play Store doesnt seem to work at all (RH-01 error)

Any idea?

Thanks

Edit: I opened Play Store using mobile data and it magically worked
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Safetynet

I'm lost in commits...

Can someone tell me which build (properly one of [MENTION=3044422]mad-murdock[/MENTION]s builds) was the last one safetynet passes, please? I also need to know the exact and complete kernel version. Thanx in advance!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Stefa.:
I hope to help you on this with this feedback even if I am not so expert:

I am on "lineage-14.1-20170411-UNOFFICIAL-mad-murdock-oneplus3t" (with microG, so maybe this could be the cause of this behavior) now and after enabling the "magisk hide" from magisk settings I am not even able to start the Magisk SafetyNet check because after I click on the test start the message "Impossibile to check SafetyNet, no Internet?" (tested on mobile data and on WiFi).

More than this, but it's not related to SafetyNet, from this build I am experiencing continuos "Hangouts" start crashes every time I try to start the application.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Hangouts and google+ use undocumented api features: they don't work with microg.

No, doesn't help. I need the kernel version of the last working build. Thanx anyway.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
BUILD 20170415 revoked: safetynet & no clean flash possible

I worked the whole night on this and can't find any solution. Also this build fails on a clean flash.

Since no one seems interested in helping ironing out one or an other and I'm really busy the next couple of months, I don't know, when this two show stoppers will be solved, I decided to delete the download.

Use [MENTION=3044422]mad-murdock[/MENTION]s build from 0411 for now. This is the last good build for now.

Please don't report any issues on builds newer then [MENTION=3044422]mad-murdock[/MENTION]s 20170411 build.

Please remove 20170415 from any mirrors.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] cmattern:
FWIW I usually build my own my because it's satisfying. My builds broke on 4/15 and I didn't have time to fix things, I noticed and installed this build and noted the same issues with Magisk but figured it was something about my phone in particular. Yesterday I wiped everything out and started with clean source last night and mine is working fine including Magisk. If this is still an issue when I get home tonight I'll reload the suspect build (I have a copy on my phone) and pull the needed into.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
I'm pretty sure that SafetyNet worked with 0411. What else do you need help with? I'm free for a few more days, happy to help.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] DunklerLordChuckles:
Some news: The old gapps package doesn't work with 0415 build, yes, but dynamic gapps does.

With installing the mini package I was able to clean flash 0415 build without any problems. Though I'm not able to pass safety net (It throws CTS profile mismatch even though magisk hide is active). But at least we can clean flash the build, the error seems to be the fact that the old gapps package might not be compatible with 7.1.2.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] twoxa:
Anyone using microG can share their experience?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Roach2010:
Hi [MENTION=4405529]nvertigo67[/MENTION]

I don't use your build but from looking at your github it seems obvious to me why your build is failing safetynet, this commit changes the build fingerprint to something that hasn't passed CTS and so the SafetyNet check fails. Simply revert this or use a valid fingerprint and you should be sorted.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Screen off batt usage about 25% better then gapps. Very quick gps lock. Playstore, notes, maps, calendar sync, contacts sync working like charme.

No hangouts. No google+. Push notifications some times delayed (Whatsapp - hangouts substitute - sometimes over 3h delayed) or dosn't work at all for some apps (i.e. SpiegelOnline).

The push notifications issue made me return to gapps - no time to dive in, but relaying on real time push notifications for my job.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Derp^2... You are right, of course. Fingerprint has to comply to oos versions - not to android base of lineage... Thanx - sometimes I'm really blind to the issues in my thoughts (the deepee the night...). Will fix that as soon as possible.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Great finding! Thanx. Would you please provide a link and the exact version?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] DunklerLordChuckles:
Of course :)

I'd provide the download link but that unfortunately isn't possible since the 10 post rule :( But here is the XDA link, that should work-

https://xdaforums.com/android/software/gapps-dynamic-gapps-t3487192

I tested it with the 04042017-build (I might be able to send it via pm) but it'd also work with 1504 (with build im referring to gapps, not the Rom :))
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] dank101:
Fix tonight?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Thanx. The link to the thread is awesome. As soon as a second user reports success, I'll change the OP.

Yes. I fixed the source last night, but felt asleep before building. I'll publish a newmbuild later today.