yashsingh1/xdaforums huggingface dataset:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
What makes you think that? If I was unpolite, it was not intended. This really left me clueless.

I meant the headset model.

I don't want to start thinking of the possibillity that the 3t models itself are different... ...that would mean... ....uhh, no, I don't want to think that... ;)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
I would use the one from extras. It's integrated. What more can you want? Also, you get a status bar icon, if an app is using root. I dont see any advantages on SuperSU. Plus you can switch the integrated one on and off as you like. I guess thats relevant for safetynet, but I never tested it. Safetynet has no importance for me.

---------- Post added at 09:38 PM ---------- Previous post was at 09:31 PM ----------

We used latest 20170201 build to test that issue.

About the models - and also [MENTION=4405529]nvertigo67[/MENTION] - there are indeed 3 different models that differ in network hardware: https://en.wikipedia.org/wiki/OnePlus_3T#Network_compatibility

But OnePlus handles them all with the same ROM. Question is, why did it work, then not work, then work with another ROM again. There might be things outside of the ROM involved.

Still, before looking into this again, can you please flash the build we tested with - 20170201 - and if you still hear a crackling noise, make sure to send the logcat? To do this, you can either connect a PC and do adb logcat or use one of the many free logcat apps from play store. Make sure you start logging before the phone call.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] DeadPicsel:
Oh no you wasn't impolite or anything. I've been brought up to not complain when someone is doing something for free or with little gain for themselves.

My headphones are the Sennheiser Momentum In-Ear. They work with every other device fine and I've never had any issues with them, I know you was not saying I had but I just wanted to mention it.

If you could replicate and fix the issue then I'd use LineageOS as my daily driver and wouldn't look back.

---------- Post added at 10:53 PM ---------- Previous post was at 10:49 PM ----------

It was that build that made the crackling noise come back. The one from the 26th was fine. I will gladly flash the ROM again and test and I can get logs for you, that's no issue. I won't be able to do it until next month now as I'm going away for work conferences and will need my phone working fully for work.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] freepenguin84:
Appreciate your detailed answer very much, thanks for that!

But isn't it possible, from a technical point of view, to handle these issues with a unified build? Like install different blobs depending on which device was identified during the flash procedure? Same with a certain power_profile.xml for each device and maybe all the other important differences. Is it just more complex or definitely not possible at all? Personally I like the idea of a dedicated build very much and would rather install this instead of the official unified one. I just want to understand why it must be a dedicated build to get the advantages you mentioned.

Update: OK, just read [MENTION=4405529]nvertigo67[/MENTION]'s post (https://xdaforums.com/showpost.php?p=70781750&postcount=2) again. It seems to be possible but simply isn't done yet.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
Caution!

Encryption with this ROM does not seem to work.

To test an issue in TWRP crashing, I had to backup all my data to PC. During this test I formated data many times and also removed the encryption. I restored my phone and the system worked fine - it just was not encrypted. So i used settings -> security to encrypt my phone. I was warned about the process taking several reboots and several hours. It was done after minutes and only 2 reboots. I suppose it crashed. After this my password is not accepted anymore - neither by TWRP nor by Laos.

Don't worry about me, I am fine and know how to work this out. But be warned. And [MENTION=4405529]nvertigo67[/MENTION], please put a warning in the OP. If people have to encrypt their phone, they should do a nandroid backup, flash OOS 4.0.2 and encrypt it with that ROM. Once encrypted they can restore their nandroid backup.

For now I restore my phone unencrypted. Maybe we can figure out tomorrow, whats the reason for this, when I let the encryption crash again. Boy, what a long night...
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
The builds are ok. As long as you use them with the fw version they depend on. (Yoda says: "You're perfectly safe - as long as you don't do something stupid..." *lol*)

substratum:

Theming can be a *****... ;) I always said so! So, you could have known... ;)

Sometimes home is not working when s is runnig - sometimes fcing s is sufficient, sometimes I need to lock and unlock to have home back... For me it's working beside above glitches. Did you have oms7 support in s or legacy? Build from branches as stated in announcment? Theme issue? Side-effect from subtile changes of the source tree in an other place... idk.

edIt: perhaps upstream (laos or oms) changes. Havn't synced since release, to test my changes in a known to build good environment, to avoid this possible side effect.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mcdachpappe:
i never had any issue like you said there.

oms7 support, build from branches as stated in announcement, no theme issue as its crashing if i open substratum app for the first time. no changes at other place in device tree that could affect substratum (as far as i know).

time will solve my issue i guess. thanks for your sources, builds and support.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
I have this not only on op3t, but on chagallwifi, too.

How do you tell you have OMS7 support, if you can't enter substratum settings?

I don't think so, meanwhile I found an other dev, who has the same issue on chagallwifi. But time will show.

Sidenote: my patching and building scripts are the starting point. Building a rom is more then running some scripts and wishing time will sort out the issues. I always thought learning git and gnu make is most important to start building own roms, considering it is allready second nature to read logcats. But my consideration seems to be entitely wrong.

If you use my scripts directly after "repo sync", the only difference I can think of is how the sync is done. Because of my paranoia and because my source tree is patched and after editing there might be a checkout on a branch (m/cm-14.1 checkouts are detached), I always sync this way:

ingo@adler /usr/local/src/cm14 $ cat my-reset-hard
#!/bin/bash

repo sync --prune -d

repo forall -c git reset --hard
repo forall -c git clean -f

repo sync --prune -d

repo status
ingo@adler /usr/local/src/cm14 $

Have you tried to flash the rescue zip?

EDIT:

The dev with the same issues just told me resyncing and repatching solved this. I guess the TI needs an update since the interface version has increased. I'd recommand syncing with the above snippet, rerunning my-pick and build again. if it's still crashing get a log.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
UPDATE (ob11)

Build 20170722

Releasenotes:

This build requires firmware OpenBeta 11 (aka ob11). It's included in this build and is installed during rom flash. A flashable zip for ob11 firmware can be found below in the firmware section of Downloads.

Changelog:

Update to ob11 blobs and firmware.

Update to latest LineageOMS patches.

Update ThemInterfacer — nvertigo

ARM: dts: 15801: Move 0x29 to dsi on command — dianlujitao

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

MD5: lineage-14.1-20170722-UNOFFICIAL-nvertigo-firmware-oneplus3t.zip.md5sum

Happy Flashing!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mcdachpappe:
thank you for the recent update. could you please explain me this change: "Update ThemInterfacer — nvertigo" i cant see anything in your repos. Im just curious
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
I'm glad you ask:

This "update" is just the actual check if everything is synced correctly - the actual update is done by repo sync. I added it to make clear: patching the source tree on a large scale requires more care, then just running a script.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] technotravel:
I screwed up something during my latest flash. Also flashed (what I thought is) the latest microg version - but now my phone is stuck with the initial install wizard. It breaks down after the WiFi connection page - I can't get any further than that.

I have tried with a previous version, too, but the same result. How can I get out of this loop?

Thanks for any helpful hint

Chris
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Have you tried just skipping the wlan setup (and set it up later from settings)?

I havn't the time to test this, but it should work: clean flash just the rom (and only a root packege, if wanted - nothing else), boot up and got through first time setup. Reboot to recovery and flash latest microg. Boot to system, install fdroid and get yoUr ptefered location provoders. (I would reboot again at this point just to be save, that gms finds location when triggered the first time.) If you have grabbed a microg package with playstore, ps should work after logging in to your google account.

If this also fails: you can try flashing rom and beans, setup the device, and follow one of the uninstalling gapps recipies.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mcdachpappe:
in sim settings (see attached screenshot) there was a couple of builds ago a setting which was called "use advanced 4g mode" or something similar. i hope you know what i mean because i cant remember the correct phrase. was there a reason for the removal or do i miss something?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
It's there. Own build or mine? Have you messed with preferred network type?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] horqai:
I'm missing this option too. Last build of you. But to be honest it could be possible that I played around with the network settings. But is this important and if how to bring it back.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
If playing with some settings one should have a backup...

Since I don't know, what your carrier is offering, I would set the first option like in my screen shot.

The only change I can think of is this (BTW: I doubt 9 is good for Europe - at least not for German Vodafone):

https://github.com/LineageOS/androi...ab0#diff-1bfdf454d8424a44e0d7aea2290ee3d1R121

On the other hand: this patch is in for quite some time. It wasn't working though, because this patch fixed override props:

https://github.com/LineageOS/androi...mmit/a0b69b43f567bbdd6e24f8eda33a82ab23641189

But this is used on both last builds. I see absolutly no reason that this behavior changed from 0719 to 0722, because the questionable commit was in 0719 already.

Would be interested in more feedback. Atm I tend to put in 22 here.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] technotravel:
Hi nvertigo67,

yes, I have tried all this, and repeatedly. It doesn't make a difference to skip the wlan setup - just an additional warning screen before the wizard closes forcefully.

Also a clean flash with only the latest ROM (or an earlier one) and without any other zips to flash - same result. I don't know how to get out of this loop. An internet search suggested to stop one of two existing setup-wizards and to assign certain rights - but in my case, there is only one and the privileges button is greyed out.

Would it help to flash the original firmware from one-plus, at least temporarily? If so and you know a place where I can find instructions on how to proceed, I would be grateful.

Thanks

Chris
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mcdachpappe:
thank you for your quick answers. i think the option is missing for more then 2 builds but i never mentioned it. im not sure either.. strange thing that the option is still there for you. im trying to build a new version with property_set: ro.telephony.default_network 22 and telephony.lteOnCdmaDevice 1 (just for testing).

i dont think that i messed around with preferred network types.. i dont even know how to. im using your (clean synced) branches for my builds. just a couple of additions - no big deal and they have nothing to do with networking.

//edit:

those 2 changes didnt bring the enhanced 4g lte mode back :/
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
I have no idea. But there can't be more then one wizard: beans is replcing laos wiz and if you doesn't flash any gapps, there is only one. At least when flashing rom and beans it should go through the setup. What exactly happens when you install only rom and beans?

When I find a time slice I'll try a clean flash, but I can't promise when.

What exacr version of beans are you using?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
I won't support your own builds any longer: if I ask you to do something (i.e. on sync), never get a response, nor a makelog, nor nothing; then without knowing if the build environment is fixed, you came up with the next issue.

As told many times: I take the time to do support here from my sleep time. For me it feels really bad, if I try to solve your issue, and never get feedback (is you build environment sane again? How did you solve it? Or do you just ignore oms? Why do I need to beg every time for information to help you? Have you checked the state of each git?)

I'm really low on time, and every time slice I use to fix your builds, is taken away from others (i.e. if you reed here, you know that I have to check the clean installs - this is much more important, then fixing your builds). In this situation it would just sensible to build without additional changes - at least to give me a link to the additional changes - but you say they are there, but I don't tell you what... This attitude was the last drop to stop supporting your builds. You may think it's normal to have the dev begging for info, logs or whatever. For me it's annoying. And I will care for me.

For the lte setting: I doubted that these two commits are the reason - but I don't know of any other changes related to radio. Gimme the time to check a clean install.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mcdachpappe:
i didnt asked for support for my builds - i just asked you if you got the same issue like me. next, a different user (@horqai) said that he has the same issue and he isnt even using my build.

and i told you that im using your clean repos. the oms thing is solved with the updated themeinterfacer and didnt had something to do with my build at all (time fixed it).

i appreciate your work and your support.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] technotravel:
Hi - thanks for the reminder of the beans! I hadn't tried these actually (ever), because my aim is to have a google-free phone.

Whatever screwed up so thoroughly my setup-wizard - after installation of the beans it was gone! First came all the google requests for permission to spy on me, then the regular wizard went through smoothly. Afterwards, I just did a new clean of your ROM install without beans and all is well. Now I will try microg again.

Thanks for you patience! I hope this info may help other who get to this nasty wizard loop.

Chris
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
This was with beans 0610. Works without gapps, too.

These two tests incl. backing up before and restoring after took two hours. With all the postings to gather information and deal (think, search, go through code lines) with the missing lte option "issue" this adds up to over 3 h

Exhausted

The following is not ONLY meant for you, but for every single one, who feels offended, misunderstood or in any way disapointed:

The sad realy sad point is, which makes me think of just building and announcing and dropping support here alltogether is:

One of these would have saved these time nearly completly:

Follow OP.

Report with sufficient information

I see the next passive agressive lazy excuse posting - here is the answer: use your brain. It's not that difficult! If I the issue occurs, check your setup and changes. For a wrong placed icon twrp version is propably unimportant, but it's clear if an issue occurs after a flash, that twrp version gapps version, setup of storage matters: to know this it's not needed to have any additional knowledge then just your own brain. Now just read OP and check against your versions.

If you can't solve it by that, use your brain once again in a grown up way: if you can't solve it, give me a chance to solve it. Therefor I need - not so surprising for the brain users - a way to reproduce it and a logcat (if possible, what is true for most issues with a running rom).

If thinking is too demanding: read the link in OP, or search xda on how to report an issue. Some details of what you have already tried, saves my time, too (and most of the time this also saves us all from wasted bandwith and ugly to read threads...).

And once again (but I promise, it's the last time for this posting... ;) use your own, normal every days knowledge) - of course: problems like the misplaced icon require a less detailed description. But for some problems, an reproducable, step by step description including exact info on versions of software used (not "latest" or "the version I always use") is ncessary. Flashing or/and radio issues belong to the .... group of the (filled it by thinking?)

I know it's not meant personaly respectless in any way - but for me exact this thoughtless habbit pattern (what shows up more and more reguallary - not only in this thread) has become matter of health.

That's why I wonder if I should stop support here.

On the other hand would this be unfair for most of the other users... ...and I like the idea of open source, community builds. Building without support is only half of the game... It was really hard for me dropping build support (and I'm still not happy with it), but my day has only 24 hours.

I think I need to oversleep this. :( :( :(
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] yannmrt:
I flash dirty since long time and still have this option.

Other feed back about GPS, since you "put your hand on it" it fix a bit faster and accuracy is better.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Me too. And I have it on clean flashes, too.

After investigating this (yeah, was to upset and annoyed to sleep) I still doubt that default setting for network mode "9" is the best choice: it doesn't matter for dirty flashes, because the setting you used last on your setup is NOT overrode (iregular verb? Not sure...) by a dirty flash. On a clean flash there is no previous setting, and it takes quite some time till lte: first I see a gsm connect (first 2G, after over 20 s 3G, after 20 s more finally lte...).

Beeing able to give you this numbers implies, that I started the setup (swipe up after giving the sim pin) AFTER I've seen the lte symbol. The order seems to be exactly the order of the description. For "9": gsm, wcdma, lte. For "22" (if selected - description in list does not match description if selected regarding order): lte, tdscdma, cdma, evdo, gsm, wcdma.

On the country side of north-east Germany vodafone is not offering cdma if gsm is available, or not at all (didn't find a way to force cdma or one of it's evolutions).

In the logs I can see, if I have configuered "22" lte is setup first and on the ux side, I have a lte icon on a clean flash after about 10 s (compared to ~20 s + ~20 s + ~10s (for first 2g connect ) = ~50 s.

I'm not 100% sure, but I guess if the advanced lte switch is missing, the setup was started while radio was on 2g, setup is not pulling additional lte setup. I can reproduce the missing advanced lte switch, when setting networkmode to something WITHOUT lte at all. After a reboot the advanced lte switch is gone (this is just my recomandation to get back the lte switch, but vice versa [and a bit more forcefull, since I disable lte this way alltogether]).

I wouldn't think this is connected to not beeing able to finish first time setup, but the coincidence suggests - at least - to consider a connection.

I want to encourage you, to play with the gps settings.

I went back to originally laos gps config for compatibility reasons (i.e.: most carriers nowadays offer SUPL v2, most of the SUPL v2 offering carriers also offer a fallback to SUPL v1 - but I know of not a single carrier offering SUPL v1 with a v2 fallback (I'm not even sure if this is possible at all). So using v1 will serve more carriers then v2.)

Not using radio as nmea source is just a matter of security, since I don't know (missing docu on izat module - meanig here the silicon part, the hardware) if this would enable someone to remote track you. I just don't want to be the one, who made tracking even simpler.

Using v2 and nmea source radio will propably decrase ttff and acc even more. (considering your carrier is offering v2 - if unlucky your carrier is one of the rare ones, only offering v1).
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Vipeout:
I just found out that my front camera is not working, neither with the oneplus cam nor with the cyanogen cam. The op cam takes the pic but then freezes, the cyanogen cam just crashes.

I tried clearing cache/data for both apps but no game. I searched, but it seems no one else here recently had any issues with the front cam.

Am I missing something? I noticed there were some camera changes in a recent update, but I would be surprised if that broke the front cam , especially because I cleared the caches

Btw its only affecting photos, I can record videos with front cam with no problems

Edit: I have no idea why but after refusing to work the whole day and several restarts, it suddenly works for no apparent reason...
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] technotravel:
No, there seems to be an issue. After reading your post, I tried it out and indeed - the picture taken by the front camera doesn't show in the gallery mode (when swiping to the right).

However, it was later sent to me through my Nextcloud auto-upload - so maybe it's a problem with the gallery view? It still doesn't show there, but the picture was really taken.

Chris