yashsingh1/xdaforums huggingface dataset:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] venomus001:
I tried franco's kernel just for the sake of testing since this rom was working with stock blob it did boot and work very well but i could not find a solution for the wifi driver then i flashed the uniblob-ob10 and switched to blu spark kernel (by the way i used TWRP blu spark latest edition to flash this Rom because they fixed the issue related to model recognition) for the wifi issue with 5ghz i could transfer files as large as 1 Go from and to the phone in a matter of seconds so nothing to report about that
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] FloGatt:
Here you go: https://xdaforums.com/showpost.php?p=72977728&postcount=5869

Depends on what i have to do ;)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Just have an eye on the recoveries - I belive looking at twrp versions is absolute sufficient; never seen a cwm or something like that for 3t or 3 - and make a posting with the list of twrps known to work with a link to the xda thread.

If you are a perfectionist on completeness you may want to add a list of known to fail twrps.

As soon as you have done the first version of the posting, we ask for moderators help to move your posting to #5 and I place a link to #5 instead of only referencing 3.0.4-1. If you find something or are being told of something (even if [MENTION=3013723]FloGatt[/MENTION] will do this, everything shared here is community stuff - it will in sum only get better, if we all share our findings and knowledge), you can easily change #5, because you are the author of #5.

Or you make your own thread (would go to news & guides, I think).

[MENTION=535343]all[/MENTION]:

Though I don't support mods, custom kernels or other versions of gapps, I'm happy to link other threads or postings, if one wants to give HOWTO's, lists or whatsever back to the community. The very same goes for microG or OMS/Substratum themes!

I do not know everything - in deed I see each day more topics I don't know a **** about. The support in this thread as well as the rom itself is only as good as your participation!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] TheGatorade:
Not a clean flash, I've been flashing every update for a while. By auto I mean "automatic optimisation" toggle that's under the battery profile. Even if it's on yt videos at 1080p60 lag unless it's set to performance.

Happens on every 60fps video for me, really every one (ex: [youtube]N8vaJaFCFYA[/youtube] )

I don't use substratum
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
The video runs like charme (though I think telling from the speed of speech of the blonde girl, this video was taken with 30fps... ;) ) at 1080p60. For the hardware 50fps is more demamding (on playback), since our screen fps is fixed at 60fps.

There's an issue with your current installation. Take a nandroid, do a clean flash with beans mini and only install youtube and check if it's gone. I consider you have excluded issues like network speed or webview (chrome stable or aosp (which is replaced by gapps) is ok. chrome beta has quite some issues.

BTW: "automatic battery optimization" makes optimized apps taking part in doze. This has no impact on forground apps when screen is on.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
You are kidding, aren't you?

(If not: complete logcat from boot until after you tried to get a fix. The snippet you send is completely useless.)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Looks like some other app is blocking access to the hal. This should not be possible on a clean install. The log in the zip is NOT from a clean install. Would yo try to install only rom, gapps. After first boot to system wait for 3 minutes before log in. Install only https://play.google.com/store/apps/details?id=com.android.gpstest&rdid=com.android.gpstest, delete aiding data (in overflow menu) and let gpstest get a fix (can take up to 15 min; mostly it takes 1 to 2 min for me, time can differ regarding position and visible sats).

Next build will have only source code updat2d, but gps config will be set to lineageos' config. Perhaps for some reason my optimized configuration does not work in your location with your carrier.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
UPDATE

Build 20170712

Releasenotes:

This build requires firmware OpenBeta 10 (aka ob10). A flashable zip for ob10 firmware is below in the firmware section of Downloads.

Changelog:

op3: Disable sound trigger — Sultanxda

oneplus3: Enable framework sched boost — Sultanxda

oneplus3: Don't offload formats unsupported by framework — Sultanxda

oneplus3: Don't offload PCM and FLAC formats — Sultanxda

oneplus3: Force triple framebuffering — Sultanxda

init: fix derp from resolving conflicts. — nvertigo

IMS: fix derp: remove some test settings again. — nvertigo

gps: revert gps.conf to lineageos op3. — nvertigo

op3: Abandon TARGET_UNIFIED_DEVICE flag — Bruno Martins

op3: Allow vendor init to override props — Michael Bestas

remove 32bit part of the gps stack again.

ROM: lineage-14.1-20170712-UNOFFICIAL-nvertigo-oneplus3t.zip

MD5: b9be93fa969fb8140ccfe5cae360bd2c

Happy Flashing!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
At the moment I take the time I need for this rom (including the support in this forum) from my sleep time. Since this is a complete different scenario, the two and a half hours I spended on your issue was wasted.

Every single minute I spend on xyz, is taken from the time I can spend on forum & rom.

I know I could do this all as fulltime job, and it wouldn't be enough, but because my time is really, really rare atm, I would like to ask everybody here to be as precise and complete with the description of an issue. Even if you think you can save your time with not going into detail, in the end it takes longer (if a solution is possible at all), and it takes my care, time and focus away from evolving the rom.

Excuse accepted.

This is a complete different scenario. Uninstall all gps testers (gps toolbox definetly has very strange side effects: when starting to dig into gps I wasted 4 nights, before relizing gt is generating quite some errors in the loc stack, especially with flp and last known location) but com.android.gpstest. Or clean install with only beans mini and com.amdroid.gpstest (and a root package if you want).

After installing gpstest, start the app and wait until you have a fix (do this in static position - aka not moving). If the fix is there, waitmuntil the speed is zero for at least 10 seconds. Now disable gnss (the switch at the top of gpstest). When gnss is disabled press the overflow menu and clear aiding data. Boot to recovery and wipe cache and data. Reboot to system. After giving the sim pin wait for 5 minutes to log in. Start gpstest (gnss should be switched on by default - if not, switch it on) and wait (first fix can take up to 15 min - while this time last known position is NOT available, so it does NOT make sense to use anything relaying on location. This includes i.e. camera apps allowed to geotag. If the fix is there and the speed is zero, end gpstest.

If this doesn't help, I have no clue whats going on on your device.

Honestly: I tested about 15 different source code setups (incl. taking the completemstack from stock and building everything from source [drop me a note if anybody wants to take a look at QMI header files]; using supl 1 and 2, using modem as nmea source and switching intermidiate position reporting on). In the end the time for first fix was always nearly the same: first fix after reboot 12 to 90 seconds. Following fixes between 1 and 5 seconds (with intermidiate it's always 1 sec, but if you take the accuracy under 20 meters to tell when there is a hardware fix, I'll end up with the very same numbers). And it's the very same numbers I've expirienced with the builds before the gps changes and stock oos.

I can't see any reason for the increased time to ff, nor can I think of one. Have you ever tried a real clean install (only beans mini and gpstest - without any additional apps restored/installed)?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
OP UPDATE

I've just added the following two lines near the top of OP:

If you find an issue, follow these instructions: https://xdaforums.com/showpost.php?p=58239877&postcount=3

Everybody has his very own definition of "clean flash" or "dirty flash". I use these phrases like descriped in this posting: https://xdaforums.com/showpost.php?p=58239877&postcount=2
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Thanx for the offer - I really appriciate that. But since everything is moving on, and the problem seems to be fixed, just be happy... ;) ...at least I am.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] nan0s7:
So I'm not sure if this is known to be an issue... but I'm coming from the OB10 and when I go to flash this ROM (after clean wipe & ob10 firmware flash, even tried un-mounting system) it comes up with an error 7, saying that I have a OnePlus 3 not 3T.... which is clearly wrong. :P I also made sure I'm using the latest TWRP (straight from the official site).
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] nan0s7:
Damn I must have missed that.... thanks!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Allready discussed in depth here: https://xdaforums.com/showpost.php?p=72985129&postcount=1548

That's three pages back! Use the thread search before spaming this thread with one day before answered questions, please.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] pogui:
No "fingerprint hardware available" after dirty flash over previos build. Any ideas what can i do?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
In the very first place: don't let the dev beg for logs!

The previous build, or a previous build? From the error I would guess you are running on incompatible firmware.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] DeadPicsel:
I had the same issue with fingerprint scanner not working.

It's not a ROM issue. I flashed the previous ROM from Nvertigo and then dirty flashed the new version. Fingerprint scanner works and I've had no issues.

I'd like to thank Nvertigo for providing a smooth, lag free, problem free ROM. You my friend are a god.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Do you mean: "nvertigo guessed correctly; it's a matter of the wrong firmware." If so: it's not necessary to flash the previous, ob10 firmware containing build. It's enough to flash ob10 firmware from the Download section of OP.

Sidenote:

I'm agnostic, but if I would belive in Jehova, Allah or God, I would be quite sure she does NOT need a phone nor our rom. I strongly belive "almighty" includes free, hardware-less calls... ;) (I'm kidding on us humans - not on Her. Though I don't belive in Her, I belive in religous freedom! I do NOT mean to offend anybodys religous feelings.)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] DeadPicsel:
Yeah flashing the ob10 firmware from your download section would replicate what I did.

Side Note

It was a compliment towards you, for the hard work you have done.

Side Note 2

I never know when you are being serious or when you are joking.

Lol
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
OT (thought two days... ....finally: can't stand that opportunity... ;) ):

*lol*

Excuse me, Sir, I had forgotten that the Lions will never win a penalty shoot-out, as Krauts have no sense of deadpan humour...:svetius::svetius::good::laugh::laugh::laugh:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] stalliongallery:
best smartphone ever used
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
That really has a lot to do with this thread.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] skothiya:
Home button and finger print sensor is not working after flashing this rom

What should i do?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] wistlo:
Is Build 20170712 what you flashed?

You probably need to update firmware. One way to do it:

1. Clean flash lineage-14.1-20170706-UNOFFICIAL-nvertigo-firmware-oneplus3t.zip (Note the "firmware" notation; this has updated blobs) Because you have to drop back to an older version, this will require a clean flash.

2. Flash Build 20170712

Alternatively you could directly flash the firmware files, available from links in original post.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] skothiya:
Thanks

it works perfectly
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Read... :(

The releasenotes cleaarly states: you need ob10 firmware.

https://github.com/nvertigo/firmware-3t/raw/master/archive/oxygenos-ob10-firmware.zip

This is also discussed/explained a page ago... :(

Would you mind to use thread search and reading before posting, please? Thanx in advance.

EDIT:

It's sufficient to flash the linked zip, wipe data (yes, sure!) and reboot. No need to reflash the rom.

All future builds will check for modem build time to avoid issues for people unwilling to read.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] hypnoc:
I downloaded the latest build a few times and md5 was always "360ff5ebb06677adf025c52c36af0356".

Does anyone else get the same as me or it's just me?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] FloGatt:
I geht the same hash. See attached screenshot.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
Me too
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Me too... ;)

You are right. Did a build for chagall the same time... and was quite exhausted... Sorry.

Thanx for heads up.

Will fix it soon - too tired tonight.

...ob11 is waiting to be inspected, too... ;)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] horqai:
This means better wait for the next build or is it save to install the latest build?

Cheers and thanks for all your work mate.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mcdachpappe:
if i install latest substratum app from playstore, themeinterfacer keeps crashing with your latest sources .. how do i get a usefull log for you/us?

/edit:

clean flashed with latest beansgapps on ext4 and fs2fs

/edit2:

seems to be kernel related.. flashes a custom kernel and theme interfacer ist fc'ing anymore

/edit3:

found the reason. im home-building from your sources and the kernel runs in enforcing state (setenforce 1) after cooking. in enforcing state, themeinterfacer keeps crashing. after turning it to permissive, themeinterfacer runs fine (and even overlays are working again).

i was using your sources for quite a long time now and the kernel was always in enforcing mode but themeinterfacer never had a problem. this fc occures since your latest kernel patches i think.

do you have got any advice or clue why this is now happening? no big deal to run in permissive mode, but i like to keep it enforcing as long as i can.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
Edit/Update: Investigating certain stuff mentioned here further, it turns out, some of the were wrong, or not right by today. I cannot strike-trough the whole text, so I leave this disclaimer.

Why do I think, a dedicated LineageOS build is better than a unified build like the official one?

This is my personal view from personal experience plus some facts from [MENTION=4405529]nvertigo67[/MENTION] thrown in. If I talk about "the unified build" I refer to the unofficial LineageOS build which is right now becoming the official unified LineageOS build for both 3 and 3T

The Facts

The OnePlus 3 and 3T differ in hardware. The blobs - the part custom ROMs like LineageOS take from the latest official ROM, not being available as open source, mainly things that can be described as firmware or drivers for example for camera or LTE unit - are different. About 80% of them are different if you compare OOS 4.0.2 for 3 with 3T. Yet a unified ROM has one set of blobs for both phones. Usually using the blobs for OnePlus 3.

The batteries in both devices are different. But unified builds use the same power_profile.xml (a file used to build a ROM) which does not address the differences. Have you ever experienced your 3T on custom ROM takes ages to charge from 90% to 100%? That's the reason.

OnePlus themselves - having a unified codebase for 3 and 3T - do not build one ROM, but 2 dedicated ROMs for both devices. They probably have their reasons.

The experience

Battery life seems better.

It's hard to say if that is an issue on all custom ROMs or connected to how I use my phone. It might be the same on unified LineageOS in the end. But this part is about my experience.​

The before mentioned slow loading to 100% doesn't exist.

The fingerprint sensor works better. Less laggy and more like 100% correct than like 80%. It works like on OOS and not like on the unified build I used before.

The ROM feels more smooth and reactive than the unified ROM I used before.

This was my first impression when switching. It is very hard to compare by usage, yet things like switching home screens and pulling down notification area felt way more smooth after switching to this ROM.​

Google Camera works. It doesn't work on most unified ROMs nor on stock OOS. Update: turns out it works on all latest LineageOS now, now matter what build.

One last thing, this is (unofficial) LineageOS after all. We don't add any fancy features that are not in LineageOS (yet). All the changes are hardware related. LineageOS does a great job being feature proof and stable - we don't want to change this.

P.S.: I will use this post to add to my signature.

Hope this answers your question :)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] t-shock:
[MENTION=3044422]mad-murdock[/MENTION]

Your post is well written and you explain everything. Thank you

But I will have to disagree with you on the battery life. On the unified build I had better battery life with almost the same usage by 30-45 mins more SOT. Whereas on this one, the performance is much much better BUT the battery life is almost 4 h SOT

edit: Just now I saw that you said that every Lineage build might be pretty much the same. This is just my experience
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
I have battery - especially during screen off - very similar to stock OOS. But as I said, battery life is a very personal experience and greatly depends on what apps you use. Wiping every now and then and restoring user apps via Titanium also helps to fight the battery issues that can arise by often upgrading your ROM.

Cool though you can confirm what I personally experienced about smoothness. Makes me feel more comfortable about this claim.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
On official vs. unofficial: https://xdaforums.com/showpost.php?p=70506975&postcount=196

3T only - why that: https://xdaforums.com/showpost.php?p=70781750&postcount=2

Most propably you mixed up the threads - the question doesn't make sense on a dedicated build thread, since official will be unified.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
IMPORTANT!

On gapps:

Disclaimer: gapps suckz!

gapps is often an issue, that's why I suggsted a one single package - with later packages then 20170120 nano (btw: the link in OP is the official opengapps Archive, this is original opengapps) I had similar issues, like the ones described here. Now we see, that this package (whichmI still use without issues) makes problems for others. I'd like to put a recommandation in OP, that works for all.

When reporting issues with gapps, please give the exact version (date and package), to find a version, that works for all, itnwoupd be also helpful, if you report what is working for you.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
On battery life:

always remember, that it takes at least one complete charging cycle (sometimes 2 or 3) to get stats setteled and mak a jufgment on battery life. Since I flashed the last week each day 6 or 7 times (I test changes to my satisfaction before pushing a rom), I'm the last one to ask, how batt behaves long term... *lol*

My impression is, that standby/doze is marginal better then stock, screen on batt usage is consiserable worse (about 15 %) then stock.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
I just had a very pleasant phone talk with [MENTION=4405529]nvertigo67[/MENTION], using my PS4 headset with builtin microphone.

No crackling noise at all. Cannot help you there.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] DeadPicsel:
Is the headset you used wired or wireless. It's definitely an issues. There was a few people who noticed it.

Is there anyone else who can test this please.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Vipeout:
The one you linked in OP works for me, no issues.

Question:

Since the ROM come pre-rooted, is there any benefit in installing SuperSU? Namely the SU addon package from https://download.lineageos.org/extras

Over in the offical thread they list it as an optional download, so I was wondering what might be the benefit of this?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Formerly su was built-in in userdebug builds, laos changed that, becausw aome apps refuse to work, if the device is rooted. I reenqbled su on userdebug again, so this rom comes with laos built-in root. So ne nwed at all to flash laos root. Some apps like [MENTION=631273]Chainfire[/MENTION]s SuperSU over laos build-in (or flashed) superuser, if you run into issues with the built-in root, you can try to flash SuperSU (I haven't tried, since I'm happy with the buildin root.)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] t-shock:
[MENTION=4405529]nvertigo67[/MENTION]

A small yet important for me issue that I just found out is:

My second sim card (Vodafone GR) is my mobile data sim card and I use it only for internet. But the phone cannot find 4G/LTE network and thus it only runs at H+

This doesnt apply on the first card (Cosmote GR) whereas the 4G works perfectly

I tried to change the sim cards, it didnt work

I flashed 4.0.2 firmware and modem, it didnt work

I flashed 3.5.4 firmware and modem, it didnt work

I has the very same issue with the MIUI Chinese variant but I never experienced it on another LineageOS build

Thanks
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
The headset [MENTION=3044422]mad-murdock[/MENTION] was using, is a wired one - sound quality was superb. I'll get the next days an old wired samsung headset, and we test again. May I ask (propably answered, but I can't find it) you which model you are using?

Does anybody here owns a original wired oneplus headset? If so, would you mind sharing your expirience?

I would also be interrested in reports on bt-headsets, bt-car (aka handsfree) and so on.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
If the second sim doesn't work on slot1, either, the sim is problematic and not the slot, so I guess without seeing logs, it could be apn settings. Try kanging apn config from a build your second sim is working.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] DeadPicsel:
First of all don't think I'm nagging or being unappreciative because I'm not. I'm grateful for the work you have done and I'm grateful for the help and support the community offers.

The only reason the wired headset issue is an issue is because I use my phone for work. There are times when I have lengthy conversations with customers and holding my phone up to my ear gets tiring and uncomfortable.

I just don't understand why the issues was present in the unified builds, went away with your build and hotfix img from the 26th but came back when you did the build with built in hot fix. I've not tried anything since the build that had the integrated hotfix because I needed my wired headphones working lol.

Are you asking what model of phone I have or model of wired headphones that I have?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] t-shock:
My second sim works on both slots. Just the 4G wont work (3g works just fine)

The sim works just fine on other handset/rom

Weird enough now everything works

Nope it is broken again

The 4G works on the SIM1 Slot but not in the SIM2 Slot