yashsingh1/xdaforums huggingface dataset:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] wistlo:
Vote here for the first option. I'm not a ROM builder, just a user, and I received TWRP errors when trying to update a nightly. I was two weeks behind as my 3T had to go to Acer in TX for a camera replacement under warranty A little research and reading revealed a previous nightly with "firmware" in the name, and that was the necessary clue. Putting firmware in every update would increase file size. Sometimes that extra 50-100 Mb makes the difference between being able to nandroid a backup. Option 1 has an advantage in that it's immediately clear from the file history when new firmware goes out. With Option 3, it would require more research for those who don't (or can't) update with each release.

Speaking of "firmware", I have a framed copy of this cartoon in the guest bedroom. It's truth. Ask anyone who's stayed here; I've got custom firmware on my router and access point.... and it doesn't always work with their iPhones. The tl;dr explanation wiki is almost as funny as the cartoon itself.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
But wouldn't *option 3* be better in your case? You wouldn't have needed to download two whole ROMs, just because only one had the required fw.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] wistlo:
Go into the Magisk app and enable "hide" (mentioned in this thread previously).

I followed OP instructions closely (removed arm64 su), and this ROM dirty flashed is working flawlessly.

---------- Post added at 01:31 PM ---------- Previous post was at 01:28 PM ----------

Good point, but it's hopefully a rare event that I fall so far behind on nightlies. The clarity of which firmware goes where in the current method is worth the extra one-time download, to me.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
Yup, that worked. I swear I remember enabling "hide magisk" several times earlier. Oh well.

Even if you do fall behind on nightlies, with some organization under "older downloads/versions", it could be easily sorted.

Or just have the latest firmware linked to *every* new build, in case someone hadn't updated in a while. [MENTION=4405529]nvertigo67[/MENTION] do you see any sense in that system?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Vipeout:
I clean flashed and with the latest version, it cannot get Google assistant to work.

I always succeeded with the 'GetAssitant' app but this time no game :(

anyone know now to enable it? I have the most recent Google app installed Btw

Edit: come to think of it, I assume Google assistant is not compatible with microG?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Xellotath:
The latest FW is kept updated on the first post, right ? As long as this is the case it's fine to not keep up with every release, just check the post when you do update and grab the latest.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] cmattern:
[MENTION=4405529]nvertigo67[/MENTION] or [MENTION=3044422]mad-murdock[/MENTION] When you have a moment, for those of us rolling our own, should we be using 141-work or cm-14.1 at this time?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] SourPower:
Best rom and team for OP3T.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Krissyzen:
Hello again. Clean flashed latest build 2 days ago. And now my battery life is veeerrry awful and phone is a bit hot ( to compare with previous builds and oos). My regular apps, Android system, etc are draining so much battery. so am I the only one who experiencing smth like this? Should I dirty flash rom? Or try to clean flash again ? Also I tried to disable location track in privacy guard for Google services (Google app I deleted as usual), shouldn't I? mb it's all because of it?

Thx for any advices
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] endursa:
I noticed that the LITTLE core CPUs ramp up all the way to 2.1ghz, which is not supposed to happen i guess, since the max frequency of those is 1.6ghz?

A quick look at the CPU frequency table did indeed confirm this. (Screenshot)

Is this some kind of boost behaviour of the 821 i do not know about, or an error in the CPU frequency table? I can not check stock oos at the moment.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
[/COLOR]

There is no microG in this ROM. There is only a small patch, which enables installation of microG for those, who want to have it. If you still use gapps, nothing changed.

Remember, google assistant is something, Google must roll out for you. And Google rolling out updates via play store is a thing that can take a while and have delays.

I have google assistant without having done any specific tweaks for it. So maybe just wait a little.

My battery life seems fine. I would either wait 12-24 hours for the ROM to settle down, since battery consumption can be a bit high just after flashing. It should drop down though after said time back to normal. Or: Wait a bit to see if others report similar issues. If nothing like this happens, you probably should clean flash, since dirty flash failed.

---------- Post added at 10:19 AM ---------- Previous post was at 10:17 AM ----------

[MENTION=4405529]nvertigo67[/MENTION] always goes by 141-work is for latest ROM, cm-14.1 is for ROM before latest. So build from 141-work if you want to be in sync with ROMs here. I always build from 141-work. If you want to include firmware, build from firmware/141-work.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
OP updated

I've added this to the top of OP:

In addition this rom ships prerooted with Magisk and contains two patches (https://github.com/microg/android_p...aster/patches/android_frameworks_base-N.patch and https://github.com/microg/android_p...aster/patches/android_frameworks_base-N.patch) to be microG ready - this means freedom of choice to flash either gapps or install microG.

I also changed the first time installation instructions to reflect firmware installation and microG:

Download the ROM below in the downloads section (or from a mirror; see posting #2)

If you have downloaded a build with "firmware" in it's name, the needed firmware is included and installed while flashing. If you have downloaded a build without "firmware" in it's name, you need to flash the needed firmware BEFORE flashing the rom. You'll find the firmware flashable zips near the end of this posting. New files are added on top of the list.

Download exactly open_gapps-arm64-7.1-nano-20170120.zip (Note that any other version of Google Apps are known to have wide spread side effects - see posting #4; section "gapps' known issues"

Install latest TWRP from official TWRP thread for oneplus3/3T

Reboot into recovery.

Backup your current ROM and make sure you have backups of your data you want to keep.

Flash firmware if not using a build with "firmware" in it's name.

Wipe system, data and cache. (Before flashing anything, make sure the system partition is NOT mounted: TWRP-home->mount->uncheck system)

Flash LineageOS

Flash Google Apps (see posting #4; section "gapps' known issues"). If you want to use microG skip this step and install microG.

Reboot (as usual: first boot takes loooooong ;) )

As you can see, I'll stay with my way of shipping the firmware with the build itswlf if it has changed and providing flashable firmware packages as well.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Vipeout:
Very nice! I was going to suggest something like that. Honestly, the way it was handled before was very unclear, i.e. you would only know if manual FW installation was required if you have been following the thread and read the latest post related to the release.

For example, I didn't know that the 20170401 Rom had the FW already integrated, I also didn't know that the Beta FW was never than the 4.1.0 release as I had no idea there was already a beta out.

I ended up manually installing the beta, and when I had problems with Bluetooth I installed 4.1.0, only to find out it's actually older. Yes if you read the latest pages you will know this, but I don't always have time to read up on everything, I just wanna flash the latest stuff.

Anyhow, now it is clearly evident from the start page if a FW installation as needed or not, and also that the top FW is the latest (was not clear before) :good:

Maybe go the extra mile and add (latest) next to the FW just to be extra clear, I guess when people see "Beta" they might get confused and go for the one with "proper" version number
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] vavill:
try to build it myself

but this line in

BoardConfig.mk break kernel compilation
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
make.log?

What local_manifest branch are you using?

What's the output of:

ls -la my_tmp/local_manifest .repo/local_manifests
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] egren58:
Hi new to this forum but what is the difference between hoogle gaps and MicroG? also which is recommended?.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
"hoogle gaps" is more supported (obviously), whereas MicroG takes a bit more time to install (not literally the time it takes to flash a .zip, because it's not all you have to do, unlike with GApps), but you have more control over stuff, more privacy

(I have never used MicroG though, all I've just said I based off of stuff I read on XDA)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
build 20170404

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.

Old build is 4 days old, so a good time to create a new build for you guys.

Changelog

oneplus3: Fix touchscreen and keypad firmware update process — Sultanxda

oneplus3: Set restart level to related for all subsystems — Sultanxda

op3: Doze: Refactor — Bruno Martins

op3: Doze: Perform operations as current user — Gabriele M

Includes LaOS April fools' commits. Namely an (ugly?) new boot animation and the br0zip apk. Take a look at br0zip - I had quiet some laughs using it. (Laos April Fools' post)

Updated to latest LaOS sources

If you have not flashed lineage-14.1-20170401-UNOFFICIAL-nvertigo-firmware-oneplus3t.zip before, make sure to flash the OOS beta 4 firmware from OP before flashing this ROM.

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

MD5: 23b05376e0d5fc5b28fa0157685f79fa

Mirror: posting #2

Happy flashing!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
You are execlusivly allowed to follow the links I've given in OP:

https://microg.org/

https://xdaforums.com/android/apps-games/app-microg-gmscore-floss-play-services-t3217616

Additionally: https://www.google.de/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=microg+vs+gapps&* (hint, hint, hint!)

As stated in OP it's not about my preferences (or recomkendation) but about your freedom of choice. If you don't like reading and researching yourself microG shouldn't be your first choice.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
*hint hint hint: http://lmgtfy.com/?q=gapps+vs+microg

this usually teaches the user how to actually use google. They may or may not be smart enough to decrypt and find out how those words got put in the google search bar *wink*
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mcdachpappe:
first of all thank you great dev(s) for the implemention of the microG option.

i was curious about this so i decided to clean flash the rom (latest build: 0404) with mircoG instead of opengapps.

currently i want to wait a few days and charging cycles to see whether something has changed (battery life, overall performance) in a significant positive way and report back if thats the case.

HERE is another good guide which i followed to get microG working along with the playstore, contacts and calendar syncing support.

what i can say so far is:

- locations are working fine and fast

- downloading and updating apps via playstore works

- (google account) contact syncing works

- (google account) calendar syncing works

- (google) maps working - location

- magisk: safetynet is not able to check status (error: "no internet connection?") but no big deal for me (this should pass if you install "DroidGuard" - not tested yet)

- viper4arise working (with the magisk module ;) )

- if you are planning to use an adblocker with microG (like adaway) you should put "mtalk.google.com" on your whitelist (source)

//additional edit:

- push notifications are working as intended (such as whatsapp, email, etc.)

but still i got one question to the dev(s): [MENTION=4405529]nvertigo67[/MENTION] , [MENTION=3044422]mad-murdock[/MENTION]

im following your project since a few builds and i was wondering why my charging led keeps turning into green (indicates battery fully charged) at a battery level of 90% instead of 100%. this occured on every build - ive tested since march i think.

is this intended because the thread says that this build is optimized for the op3t? i guess it has something to do with the extended battery capacity of the 3t compared to the oneplus 3? or am i completly wrong? and yes i did use the search before posting this reply so dont blame me i havent found anything about this charging led "issue".

regards
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
The LED thing is no issue, differs with ROMs.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mcdachpappe:
thank you for this build.

but one thing:

this new bootanimation really s**** in my opinion :D for those of you who like to have the old "normal" one with this new build feel free to push the attached bootanimation.zip to /system/media with 0644 permissions and reboot..

big fat note:

this is not a flashable .zip file!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
Well, its the LaOS april fools' - who am I to remove it? (It's not yet removed officially - indeed only merged on 2nd of april.) Next build wont have it.

Checked br0zip app already? It's premium puns.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
[MENTION=4405529]nvertigo67[/MENTION] this guide is superb. Very in-depth but yet friendly to less tech-savvy users. Can you link it in OP somewhere please?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Done.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] vavill:
I change it to default cm14.1

It works.

Can you explain

why you use a relative path for cross compiler prefix ?

Is it for prebuild ccache?

By the way, I make under Windows subsystem .

I fix ijar , change bision and flex to 64bit.

https://review.lineageos.org/#/c/167539/
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] yannmrt:
How can we see which firmware we have installed?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Because of linaro. With your change you doesn't build this rom, but something without optimized kernel compiler. If I should help you to repair your build environment, I need the information I requested. If you don't like to stick to the README, don't give needed information, feel free to do so, but then you are on your own. This means: it's not meant to be disscussed in this thread. Thanx for your understanding.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] t0pg3ar:
Is it important to flash every single firmware, or can you skip one?

Say, I'm on FW 1, FW 2 comes out but I have no time to flash and when I have the time, FW 3's out already. Can I then upgrade FW 1 to FW 3 without flashing FW 2?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] vavill:
Thanks for relying, I have already built offical cm14.1 successfully under WSL.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Stefa.:
Thanks a lot for your work guys, really appreciated! ;)

I am also experiencing the same behavior with the LED while my phone is on charge.

Not an issue for me but I am also curious to understand while it behave like this :)

Sounds very interesting, looking forward to your report! Are also pushing notification working as expected for you?

I am also curious about microG because since years I am suffering for the "mobile radio active bug" concerning "GooglePlayServices".. maybe the way microG are implemented could be a solution to this problem :fingers-crossed:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
Congratulations! WSL FTW! Yet you are unable to supply the output of one single requested command. You must be a real linux guru and probably dont make any mistakes. That's why you compile on windows, right?

Anyway, either tell us the output of requested command or stop spamming the thread and wasting everyone's time. Thanks.

Edit: Also, how do you build official cm? You mean Laos, right? So how you build official Laos? You got their private RSA keys? Wow, good friends with Steve and Arcee then I bet! Ask them.

(Sorry, couldn't resist on this one)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mcdachpappe:
yes push notifications are working as intended. havent noticed any negative side effects yet.

i had the same lssue like you with google services (draining in idle mode 10 percent or more)

what i can say about battery till now is that i have an idle drain of about 0,20% / h with microG compared to the same setup and phone usage of 0,60% / h with gapps.

note that this is still my first charging cycle and it will probably change with the next charging cycle and upcoming days - positive or negative
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] vavill:
I am very sorry.

Sorry for my bad English.

I can't express my meaning correctly.

I build it from official repo.

I know that command output symlink of manifest xml.

But I use my manifest in order to make it work under WSL.

Successfully built it tonight.

Thanks you and op!

It take 3 hour longer then native Ubuntu.

If anyone interested, I will post my manifest tomorrow.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Stop posting OT, please. (second request)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
"VoLTE, our mascot, is also in the bootanimation on LineageOS 14.1 builds from 3rd April to 7th April"
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
hey [MENTION=341181]m0d hipp¥[/MENTION] - you still around? We miss your mirrrrroring.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
build 20170407 - Testbuild!

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.

This is a TEST build. [MENTION=4405529]nvertigo67[/MENTION] updated the toolchain/compiler. Though it runs fine for him and for me, there might be side effects we have yet to notice. Be sure to make a backup before flashing.

Changelog

update UBERTC/linaro to 5.x.x/5.4.1. — nvertigo

bluetooth: hci_sock: Fix warning detected by gcc 5.3.1 — NewEraCracker

tfa9890: tfa_container: Fix warnings detected by gcc 5.3.1 — NewEraCracker

Merge tag 'LA.UM.5.5.r1-04000-8x96.0' into cm-14.1-caf-8996. — Nvertigo

revert April fool jokes. — Nvertigo

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-20170407-UNOFFICIAL-mad-murdock-oneplus3t.zip

MD5: ce3112637bfbce1116465b2d6c08f7be

Mirror: posting #2

Happy flashing!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] m0d hipp¥:
Hey sorry guys. Been very busy with work and life lately. I'll quit slacking. Sorry about that.

EDIT: Updated post 2 :)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] serious96:
[MENTION=4405529]nvertigo67[/MENTION] here is the log from the local app that still detected root, do i get it right?

Edit: will you add RenderKernel EAS support for your build? Love to try your ROM and that kernel together.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] yannmrt:
I have some sound cracking when playing video or GPS navigation . Not sure if this is ROM related.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] yannmrt:
I notice e as well the picture from the front camera appear mirroring. So when you see the picture and have some writing taken, this writing appear like in the mirror. :silly:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] triad88:
Don't forget, the latest is a test build.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
It's been like that for a long time though.

I'm pretty sure you can download a camera app that can flip the photo for you after you've taken it.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Vipeout:
Hi all! with the 04.01 release, my Bluetooth is basically broken. Whenever I want to scan for a BT device in order to pair it, the whole phone freezes.

I tried a clean flash and it worked just fine, but after a while I started to notice interruptions and signal problems on my bt headphones. When I I tried to re-pair them, the exact same problem reappeared; phone freezes when when scanning for nearby devices.

I never had those issues on previous versions. I tried to track down the problem but I no luck :(

Is anybody else having Bluetooth issues?

EDIT: just tried the latest version posted above by Mad-Murdock, still the same freeze

I tried to create a log but because the whole phone freezes and I need to reset, the log ends up blank.

Btw, in regards to the new test Rom above, everything works, apart from the BT issue.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Can you tell us the exact procedure to reproduce that? I have no issues at all with bt: see attached screenrecord (BTW: I transfered the video via bt to my win box.) I tried also with wifi 2.4GHz activated (it's using the same freqs as bt, and is known to give side effects - but not here).

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

Can I assume, that when the issue occured you first did a clean flash with only gapps nano from 20170120 (or without gapps or with microg) installed?

EDIT: seems due to misbehaving app.

https://xdaforums.com/showpost.php?p=71775573&postcount=4600

[MENTION=535343]all[/MENTION]: please remember: BEFORE reporting an issue clean flash with only gapps nano from 20170120 (or without gapps or with microg) installed.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
It took me 47s to google:

https://forums.oneplus.net/threads/front-camera-swaps-sides-mirror-image.507391/

It's not a bug, but a feature. You can disable it in oos cams settings. Sadly Snap has no such setting - or I didn't found it. Perhaps that's worth a feature request for upstream.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mumapizza:
Can we have update date back in thread title pls?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Have you verified if it's working unrooted?

Flash uniblobs and go ahead.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
No.

Not enough characters left

@mad-murdock is doing the builds now, and he can't edit #1
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Vipeout:
Great find, thanks!

Yes I did the clean install with the recommended GAPPS package, problem started appearing after restoring my titanium backups. This already made me suspect some app misbehaving, but since I never had this problem in the past, there was only one new app that came to my mind that could cause the problems. Since removing it didn't solve the problem I didn't know what was the issue.

Anyhow, I don't use Fitbit like the guy you linked, BUT I do use Samsung Gear and Samsung Fit so I'm assuming one of these is the trouble maker. I'm at work now but when I have time I will test if removing them fixes the problem.

Again, big thanks for the find!

UPDATE:

Just froze all Samsung gear related apps in TitaniumBackup, and surprise surprise, BT works normally again ;)

Still no idea why it suddenly started to cause conflicts and not before