yashsingh1/xdaforums huggingface dataset:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] lapapunk:
Yep, why not? Flash it and after this flash supersu or magisk, whatewer you like.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
https://xdaforums.com/showpost.php?p=58239877&postcount=3

https://xdaforums.com/showthread.php?t=2274119
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
First of all: thanx for the heads up.

On a first glance I thought that as well, but on a second look I found, that TB is working on my device with both options set. I'm just trying to guess for the reason. Gapps version came to my mind. Or something depending on when you run through firsttimesetup: I did a clean flash on 4th of March.

Gapps suckz!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
It's probably because the play services update didn't roll out for you (and for me) yet. It takes a week or slightly more until an Google update is rolled out to every device.

Like I don't have Google assistant yet, but others with same phone do. Not sure if it is random, but it sure feels like random.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Vipeout:
I would agree with mad-murdock. I dirty flashed the new Rom and so I didn't have to bother with TB, however reading about the restore issues I tried to restore one file just for testing purposes. And guess what? It got stuck in a restore loop. I then disabled Verfiy apps as suggested and boom!, restore working again. I update my gapps via XDA labs so i typically have the latest versions and am not dependent on the regional roll-out. Pretty sure as everyone gets the newest version, this will become a general problem.

Maybe address it in the first post? Otherwise I already see the flood of TB related posts coming :p

Btw this rom just keeps getting more awesome, great job :victory: Seeing that OP is still not fixing **** they have broken with OOS4, I guess I'm never going back (especially since OOS cam is now integrated natively).
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] endursa:
Just a quick comment on conservative gov.

I use it now for the third day in a row (conservative on big, rest standard kernel settings)

1. Scrolling is smooth, definitely an improvement in settings chrome and so on.

BUT I play pokemon go fairly regularly and there it seems that the big cluster is sometimes to "late" I can only describe it that way. Maybe it is just perception and something else is causing the stutters in pogo, or it is the gov. setting.

I will keep an eye and do comparisons for a few more days, but weekend is skiing time :)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] DeadPicsel:
Comments Removed because I did not read the OP and did not think before posting.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
I don't know. And you strictly decline to help to get to the reason.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
HELP!

I'm really frustrated. In OP I clearly describe which gapps to use. I asked many times to use this version, because it's the one, which is known to have the least problems.

I did a quick count: over 60% of the so called issues are the result of using some other package.

This is a waste of my time. Further more it's respectless to report issues, without following OP. The last case also shows, that people intentionally usw other gapps without mentioning... Really, really sad about this kind of behaviour.

I'm pissed! I'm thinking of stoping support here all together.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] DeadPicsel:
I did not strictly decline at all. I offered to provide logs and then managed to fix the issue. If you need the logs to help other people then I'll provide them.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
Dude, you really wasted everyone's time. And about 3 pages of this thread - which again is wasted time for everyone.

In the end, you dare to ask "what are logs?" - i mean, if you really don't know (lolcat), why not ask before? Just spam this thread, make everyone try to test your issue and reply with "I don't have this issue"

And then - at the very end - you tell us you use latest gapps. That's such an insult. As a user of the first hour of this ROM, having read all the crap that happens with gapps, you really dare to use other versions, run into problems, and then not even have the guts to tell us? Or try with suggested gapps? You claim to have flashed clean 3 times. Did you use your brain one time?

Really, please stop wasting our time. Your behavior is the prime example, other devs don't even read nor answer on their threads anymore.

The least you can do is not answer to this at all and LEARN something from this, but knowing you, this won't happen.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] kaza:
Thanks, gonna give it a try, I actually want to remove root completely ;)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] wistlo:
camera update; note on LineageOS vs. OOS responsiveness

Turns out the camera problem recurred. The camera seems to work after each fresh update or flash, but this could also be pure coincidence. The problem was initially very intermittent, but it has since started recurring more regularly. In any case, I have returned to stock and relocked the phone. The camera failed with both 4.0.2 and the OTA update. I submitted a ticket today for warranty repair. For the interim, I have replaced my 3T with an eBay HTC M8, and installed Lineage 14.1 on it. (Not a good week for Titanium Backup to suddenly begin tripping up on Google Play app verification). It is interesting to see how the LineageOS community accommodates differences in hardware while keeping the user experience almost the same.

I'll update this post with my warranty repair experience with OnePlus.

All this did give me an opportunity to briefly compare the responsiveness of the conservative-governor 20170307 Lineage build and stock OOS. Stock OOS responsiveness has improved from the November vintage, but the current Lineage still feels more responsive than the current OOS, especially with swipes and scrolls. (This is subjective, but based on observations made within a 4 hour period).

Finally, a general comment about following the OP in these threads. Last month I replaced a water heater and missed a step in the online product description (but not on the fitting's data sheet) stating that pipe tape must be used. Worse, I ignored a manufacturer's note and instead stretched the idea that my old exhaust vent would be "good enough". Result: soaked utility room and family wondering about "new heater smell" all through the house. (I haven't told them that was the start of CO poisoning. They get mad enough with me when their phones don't work.) I now have the pipe fittings properly sealed and a new vent through the roof. Moral of the story: If there's a sentence in a guide or OP on xda (or anywhere), I have learned the hard way that it's usually there for a good reason.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Jaizu:
Excuse me, does this ROM includes fast charge? What's the charge rate? Could someone look that in Ampere please?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Xellotath:
Is fast charge a rom feature? I thought it was tied to the device and not accessible by the rom.

Regarding installation, preparing to flash this rom the steps look fine except I am unsure what the "renamed blobs" are for and whether i should flash these as part of a normal (clean) install of this rom. Advice would be appreciated!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Kris Chen:
Correct !
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] lapapunk:
Battery life

Clean install, latest build, Magisk, gapps. All stock.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
Hey, when trying to flash I get an error in TWRP (error code 7) (assert failed: oppo.verify_trustzone(...))

What am I doing wrong?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] lapapunk:
Go to first post, download openbeta firmware, and flash it before rom.

That's all you need to do.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
Cheers!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
Everytime after I make a backup with TWRP (3.1.0), when I reboot, it's as if I wiped all data and just freshly installed Lineage (I have to go thru first time setup again, all settings are gone)

Is that because of the new TWRP version?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] lapapunk:
Yep, seems it's a main reason. Flash previous twrp build. More stable is 3.0.4.1
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
Yup, I re-installed 3.0.4, I was just hyped to try the adb-backup thingy, but I couldn't even restore, so it's whatever.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] horqai:
There is a new TWRP 3.1.0.1 out. That should fix this issue.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Xellotath:
I'd appreciate others confirming this before i risk it :D
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
I'll just stick to 3.0.4, I'm not doing any advanced stuff, as long as it can make/load backups, and flash stuff, I'm fine with it :D
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
My network default setting hides my phone number when calling others, but when I try to change that (Phone app -> menu -> settings -> calling accounts -> *sim card*) I get an error saying "com.android.phone has stopped".

Is there any workaround?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Xellotath:
Haven't used those settings before, but can confirm i also get the error when i go there.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Hjanos95:
Most likely caused by this change
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
What exactly is a QTI package? How does one install it?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
What exactly happens when you flash it? Tried without Gapps just to see if it's that?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] DeadPicsel:
I flashed Gapps and everything worked. What I encrypted my Google account had been removed and every time I added one the account never stayed, I would click play store and it would ask me to sign in again
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
Broken f2fs is known to loose random data. If in the future you encounter more such issues, no matter what ROM, then it's for sure f2fs.

Could also be broken Gapps. Some builds/days are buggy. Try Gapps from another day.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] DeadPicsel:
What Gapps did you use?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
open_gapps-arm64-7.1-stock-20170125 - but judging from the setup dialog, they are also not totally flawless.

I miss the day when you had one Gapps build that everyone used. Bugs where figured out and fixed fast. Now there is a new build every day. How to figure out bugs there? Especially deep lying stuff that only surfaces in battery drain or sync issues days or weeks after install.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] DeadPicsel:
I have just had a working ROM, I then encrypt and I am stuck on the Linage OS boot animation with button lights lit up? I just want a working dedicated build where features work lol.

---------- Post added at 01:28 AM ---------- Previous post was at 01:03 AM ----------

For some reason my data partition is formatted to f2fs when I encrypt, is this normal? I have checked before encrypting and my data partition is ext4 and everything works, as soon as I encrypt the phone will not boot and the only thing I can see that has changed is data has been formatted to f2fs.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
What is formated: the real partition or just the volume? sde15 or dm-0? If you wantmto change the fs you need to format sde15 (and not the volume dm-0): fastboot format data.

changing fs has to be done to the partition, not the volume.

If you wonder what I'mmtalking about, go to 3.0.4-0 twrp thread at the oneplus3 forum. There are ready to use flashable zips for changing fs.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
I must update my initial statement on dirty flashing - and update my first post.

I did what a good rom user should do when switching to a new rom and wiped all data and started anew. I had random battery usage spikes that did make me do so. After wiping, the battery seems way better.

TL;DR: If you come from another Laos rom: WIPE

---------- Post added at 11:25 AM ---------- Previous post was at 11:19 AM ----------

I agree, go to twrp thread. I just wrote instructions on how to do that stuff over there. Futher assistance over there.

https://xdaforums.com/showpost.php?p=70807913&postcount=231
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] t-shock:
I tried following the guide on github for building my LineAge OS 14 but as a total noob with this I can find device/oneplus/oneplus3t

if I use the repo sync device/oneplus/oneplus3t, it gives me this

t-shock@t-shock:~/LOS/cm14$ repo sync device/oneplus/oneplus3t
error: project device/oneplus/oneplus3t not found

Any help?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
Just "repo sync". No arguments. It parses XML files to download all dependencies.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Please give me the output of "ls -la .repo/local_manifest" it should contain a symbolic link to ../../my_tmp/local_manifest/oneplus3t.xml
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Pre-story: repo sync was successfull but the commands in my_buils.sh doesn't know of oneplus3t; so I told [MENTION=4350960]t-shock[/MENTION] to repo sync only the device tree. Obviously the manifest for oneplus3t is missing in his build tree, and now ww find out why... ;) Thank you, anyqay.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
UPDATE

Rom in #1 is updated, this build makes all boot.img flashes obsolet, since it contains all the changes.

From now on I put a timestamp in threads title, to quick-check if an update is available.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] t-shock:
What's the changelog except the boot.img?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Vipeout:
Just installed this, so far I'm happy :)

Would anyone be so kind and upload the stock OP3t ringtones and Notifications for me?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
You are missing the gits from local_manifest; make without breakfasting or lunching the device can't work anyway.

Let's do it step by step:

Please post the output of "id && ls -la my_tmp/local_manifest && cat .repo/local_manifest/oneplus3t.xml"
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Changelog is in OP, the local changes as well as a link to lineageos changes.

I'm not legion - I'm one person. Ican't update OP answer pms and work on the rom at the same time - please be a bit more patience with me...

BTW: I'm fixing sRGB at the moment...
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] DeadPicsel:
I've juts flashed the latest build and so far it's smooth as the previous version was.

The one issue I have, is a present crackling or static noise when using wired headphones. I've had friends and family complain that they can hear the noise when I use my headphones, the noise goes away when I unplug my headphones.

The same issue was present when I was using the unified builds. It was not present when I was using OOS and it wasn't present in the previous build.

Does anyone have any ideas?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Hjanos95:
I don't know, but it seems to me they changed one possible crash to another.

I will get home in around 3 hours, I can then build an installable zip with this change reverted in the correct files.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
Oh wow, that would be very much appreciated!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] lapapunk:
Second cicle
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
QTI should be this file: /system/framework/qti-telephony-common.jar.

I can confirm the issue, and will revert this one. If this fixes the issue, I'll publish the build later today or tomorrow.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
Sounds good, I'm surprised how quickly you responded, and thank you for actually caring about it! :D
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
You are lucky: while syncing my repomI looked here the first time after two days... Timing... ;)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Thanx for the heads up - saved me quite some time debugging.

You are right: reverting this commit allows to usw simmsettings again. Build is uploading.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Update 20170312

Changelog:

fix sim settings: reverted https://review.lineageos.org/#/c/163399

sepolicy: address another bunch of denials. — nvertigo

sepolicy: allow userinit to write in sysfs. — nvertigo

sepolicy: address a bunch of new denials. — nvertigo

sepolicy: allow userinit.sh to configure cpufreq. — nvertigo

sepolicy: rename log.te to logd.te. — nvertigo

remove OnePlusCameraService: not needed. — nvertigo

perf/core: Fix concurrent sys_perf_event_open

sctp: avoid BUG_ON on sctp_wait_for_sndbuf — Marcelo Ricardo Leitner

op3: Remove CONFIG_TIMER_STATS — dianlujitao

ipc/shm: Fix shmat mmap nil-page protection — Davidlohr Bueso

ANDROID: ion: check for kref overflow — Daniel Rosenberg

qcacld-2.0: Remove obsolete set/reset ssid hotlist — Srinivas Girigowda

mpi: Fix NULL ptr dereference in mpi_powm(

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

MD5: d48954fd1b5847e6dec917937c213b35

Mirror: posting #2

Happy flashing!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] xpissio:
Just flashed the new build with the new TWRP 3.1.0-1 (coming from another custom ROM 7.1.1), all worked correctly!

And the phone is working really nice now, of course. :)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
That was fast, god bless!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] cmattern:
I'm running the latest TWRP (3.1.0-1) and having no issues.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Jaizu:
Last recovery, last beta firmware, last rom version, wiped data system and cache, unmounted system and installer stucks at "Patching system image unconditionally..."

Tried with the previous TWRP version and same problem persists. I will just give it some time, but I don't think this will end installing, since it got a few mins stucked on that already.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Kris Chen:
Get in directory of /system/tmp,and copy file of twrp.txt to your computer,then open it.

It will tell you where error it is.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Bad Download? Have you checked md5?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Jaizu:
Not sure why it happened tbh. Reinstalled stock and then proceed again and it's working now.

EDIT: Why camera has less features than camera on Dirty Unicorns 11.2? Tested with Camera2 probe from playstore
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
I don't know du rom. Perhaps differences in hal, blobs and/or setup. Or any combination of these.

BTW: camera2 api (aka HAL3) is disabled in order to get 7.1.1 camera blobs working.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Jaizu:
Idk, maybe you can/should check how they did it, camera was working fine and on 7.1.1

The problem with DU is that they don't have fast charge so that's a big nope to me
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
No. The way du has setup the whole camera stuff would break laos Snap. I won't change this rom in a way that any original laos feature will break.

BTW: I'm very happy with the current status of the camera. Image quality is like stock. Only raw is missing. I can live with that.

BTW2: I do not see any reason, why dash charging shouldn't work on du. It's integrated before they started building unified (meaning: du has dash charge since the first build for 3t):

https://github.com/DirtyUnicorns/an...mmit/b68c717279b5d7de1488b622883a1c4cc8c5bba7
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Jaizu:
Alright, let's end this notification here, don't want to spam your thread to your users about stuff they just don't care. Already reported DU team that Dash Charge isn't working and they will work on that. Until then I will go back to stock rom.

If you want to still talking about ROMS and stuff you can PM me and I will give you my Telegram if you want to, however I'm not a dev, all I did was building 1 ROM by myself syncing from DU sources, I can't even add features, patches etc yet.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] chaztro1892:
Flashed the ROM using twrp 3.0.3-1. Finished setting it up and took a backup. Rebooted and I had to go through setup again. Did that and then flashed twrp 3.1.0-1. Rebooted and it made me do the setup once again. My apologies if this was answered already, but has this behavior been seen before?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] chaztro1892:
Sorry. Found the answer. My dumbass was searching the wrong thread.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
Yes, forget 3.1.0

Just use 3.0.4-1
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] chaztro1892:
Awesome. Thanks.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] horqai:
Is there a setting like in the last stock rom to toggle IPv6 connectivity? This is really helpful while using an VPN.

But in general super stable and fast rom!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
"like in the last stock rom"

>Why is <this> OOS feature missing?

<Because this is LineageOS.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
If you have issues after updating twrp - ask in twrp thread. (Ifnyou ask there, give them information on fs and encryption.)

For me this sounds like some incompatibility with the fs used on your data partition. Format data (not just wipe, but reformat!) from within twrp - you may also want to change the fsmfrom f2fs to ext4.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] chaztro1892:
I actually updated to twrp 3.1.0-1 and reflashed everything. Completed setup and tools backup. All good now. Thanks.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] derAndroidler:
Sorry for my newbie questions. Is this ROM completely working? Stable without errors and everything working fine including camera etc.?

Do you prefer this ROM or official lineage OS? And why?

Thousand thanks for your answers.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] lapapunk:
Trust me, it's better than official laos with stock camera quality from oos. All nice, just give a chance for this rom, you will be impressed. For now it's my daily rom, later i will give some battery feedback.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Of course NOT: no os is proofed to be completely issue free... The way you ask, the honest answer is clearly: no.

I consider this rom as beta status. Though I use it as daily driver, I can't recommend this to someone looking for completely working rom.

I prefer this rom because I prefer running roms on my devices I have compiled from source myself... ;)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mcdachpappe:
awesome rom, got i running now for 3 days without any errors or fc's.. thank you

but i think there is a bug with the notification led. the chosen settings wont apply to the received notifications (e.g. whatsapp). if i choose for example long and fast in settings it remains default. no big deal but worth to mention
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Thanx for the kind words.

Will look into. I have changed the color for whatsapp (but left the timings alone) - that is working like charme. But I can't change the color for k9 notifications, since k9 has it own setting. Wild guessing now: if the app itself is requesting color and/or timings the laos notification setting does not mess with that, but just pass it to led...