yashsingh1/xdaforums huggingface dataset:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
...and I thought the patching for oms is obsolete in o... ...sadly there is no "rootless oms patch". It seems to be less then on n, but in frameworks/base and packages/apps/Settings there are many patches...

Do you know, if I only need to patch the projects, which have an o branch, or do I need to port for the other projects the mr2 patches myself? (https://github.com/SubstratumResources)

EDIT: too much effort and time is needed. I don't even understand what is needed to patch and how to determine which patches are needed. Since I'm happy with dark style, I will not spend more hours on rootless oms, at the moment - getting nlos-15.1 more reliable is my first priority for now. Get andromeda if oms-rootless is important for you. (Perhaps this is a more robust way, then wildly patching in the heart of frameworks... ;) )
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] cabrox:
I'm the only one getting less cell network coverage (LTE and even H+) with this build? Pretty sure it has something to do with the new firmware (ob22).

Someone else experiencing this?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
15.1

More propable the missing signal strength hax/fix from [MENTION=4800121]Sultanxda[/MENTION]... Will have a look. Compared to oms, I know which git and what commit... *lol*
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
[MENTION=8779119]cabrox[/MENTION]

I think I read that OOS artificially inflates your signal strength. So it shows more bars even if the signal is not that strong. LOS doesn't do that. Bars are pretty subjective and I'd suggest relying on dBM instead. The threshold for the bars could be different from rom to rom.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
15.1: beta03

Build 20180223 (fallen asleep before build has finished, so don't be comfused by build date)

Releasenotes:

NLOS-15.1 relays on Oreo firmware. ob16 or later is needed, I strongly recommend using ob22 (because that's what I'm testing with): oxygenos-ob22-firmware.zip

beta02 users can just dirty flash beta02 (don't forget to wipt cache and dalvik after the dirty flash!) Since GCam is updated, I recooment wiping GCams data.

Changelog (synced lineageos 15.1 02/23 at 21:30 UTC):

Update GoogleCamera to GoogleCamera-Pixel2Mod-Arnova8G2-V5.apk. — Nvertigo

Allow location providers also outside of /system. — danielegobbetti

Add signature Spoofing permission — Benoît Mauduit

telephony: Hack GSM and LTE signal strength — Sultanxda

makeSignalStrengthFromRilParcel() is used for both solicited and
unsolicited requests, so we can hack it to send better signal strength
values to the modem backend. This significantly helps in areas where
GSM or LTE signal is poor but usable, in which case the modem would often
disconnect completely or fall back to a lower network mode (resulting in
poor UX).

Also, always report a valid ASU for LTE, even when the signal noise is
considered to be terrible, and adjust the threshold for terrible signal
noise in the signal icon as well.

op3t: blobs: pin defcomg@xda's libmmcamera_s5k3p8sp.so. — Nvertigo

op3t: gps: XTRA: use https and check for version 3. — Nvertigo

WireGuard-0.0.20180218.

Merge remote-tracking branch 'lineageos/lineage-15.1' into linux-stable/merge-15.1 — Nvertigo

[SIZE="+2"]DOWNLOAD[/SIZE]​

Happy flashing!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Good point! I failed so often on guessing, what people mean, that I don't claim to be sure on this.

But I guess [MENTION=8779119]cabrox[/MENTION] is talking of exactly the same problem [MENTION=4800121]Sultanxda[/MENTION]'s hack is adressing:

In my basement I have 3g or H+ without this patch - with the patch I get lte and sometimes lte+. Honestly I've never compared the bars. I've always looked for type and data rate. Both are considerablaly increased after applying this patch: uploading a 15.1 build via tethering takes about 20 min without the patch, but less then 8 min with it - why look at bars... ;) (Of course this only applies to bad coverage [i.e. basement] - with really good signals there is no difference.)

Let me know your expirience...
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] TheGatorade:
This update fixed the video recording bug, thanks! So on point! :)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Which bug?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] TheGatorade:
With the previous build I tried recording but my video files always came out corrupted, tried snap, modded gcam 4 and 5, open camera, they all produced corrupted videos. After flashing this update they all work..
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
15.1

Strange, worked for me.

You know, you need to uninstall shiped priv-app, before you can use an other GCam? Havn't checked with OpenCamera, but video recording was good for me since beta01.

[MENTION=535343]all[/MENTION]: please report bugs. Otherwise I think everything is ok and go rc. That's much more important then feature requsts at current stage!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] TheGatorade:
I came here to report it and found rom update :D

Anyway I haven't noticed any more bugs. Signal strength was the only problem and that's good too now.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Was a great reminder! Since I don't give too much focus on the bars, I always remembered to put the hack in again, when I saw the data rate when uploading a just finished rom... ;) In other words: I always remembered too late... *lol*
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
15.1

NLOS-15.1 is now here.

Would be great, if someone could check the OP for completeness, links working and everything changed to 15.1 (or oreo for that matter). Thanx in advance.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
Goodbye NLOS 14.1 thread, prepare to get removed from my subscribed threads list.

Since you asked us to check the op... The new op still says Android 7.1.2 and LOS 14.1 instead of Oreo lol in multiple places.

The linked microg patches seem to be for nougat. Cmxlog links to 14.1 and the currently know issues link doesn't seem to work. Rest of the links work and everything else seems fine. Also might want to add a link to the GCam mod thread since you're using that.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
...you're going to mis the last nlos-14.1 build... ;)

Which will be around the middle of March with March Security patches.

-> NLOS-14.1: EOL!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
UPDATE (March security patch) [EOL]

Build 20180309

Releasenotes:

This build requires firmware OpenBeta 15 (aka ob15). As always an archive of all firmwares can be found below in the firmware section of Downloads - the flashable firmwares are the original (file names starting with oxygenos* hold original fw files) OnePlus fw images. NLOS and 'old'-style bootlogos can be found down in this posting.

This is most propably the last NLOS-14.1 build. I want to say "Thanx" to all users. Please feel invited to to use NLOS-15.1!

EOL.

Changelog:

Sync to upstream: March Security Patch.

boeffla_wl_blocker: defconfig: enable wl_blocker. — nvertigo

wl_blocker: add more wakelocks to the default block list — Francisco Franco

boeffla_wl_blocker: update to wakelock blocker driver v1.1.0 — andip71

boeffla_wl_blocker: update to wakelock blocker driver v1.0.1 — andip71

boeffla_wl_blocker: add generic wakelock blocker driver v1.0.0 — andip71

WG: squash WireGuard-0.0.20180304. — nvertigo

Bootlogo choices

nlos_bootlogo-v0.1.zip

back_in_black_bootlogo-v1.0.zip

[SIZE=+2]DOWNLOAD[/SIZE]​

Happy flashing!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] xpissio:
For a second I read "15.1 [EOL]". I got a little scared. :)

By the way, it has been a nice trip.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Relax, I'm an old ass bastard honoring good old versioning... ...unlike twrp.... *lol* [SCNR]
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] xdtyui:
I am still using the latest 14.1 can I encrypt through security in settings? Thanks!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Should work. (last time tested around Juli 2017)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] xdtyui:
That worked, thanks!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] apascual89:
Your recommendation is perfect. All these packages that remove built in stuff are just problematic. Harder to pinpoint possible issues.

To avoid the alert slider issue you can remove the CM setup wizard dependency from oppo-common by reverting this commit

I know you've been discussing the ril and tethering issues. I've been using source built ril without issues. I added this for tethering.

Oh and BTW I'm giving your toolchains a try :good:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Would be great if you could try a clean install with nano from 20170120, and confirm slider is working.

sidenote: logs: just plain ascii without color in code tags or as ziped file are better to handle (i.e. grep for " E ").
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Exactly! Side effects are much wider, then I ever thought. Did I tell you allredy, that gapps suckz? ;)

Oh, yes, I understand. On the other hand, since we know of this now, it's a good way, to tell a "wrong" version of gapps is used. Will think about it.

Yes, I think that's a nesseccary one. Just waiting for [MENTION=5226211]cmattern[/MENTION]s feedback, he is just trying to solve tethering on AT&T. I'm on source build libril since yesterday and it's working flawlessly - I'm very carefull about libril changes, since there a rumors around, people use their mobiles for phone calls... ;)

Welcome. Honestly: using UBER for the kernel doesn't make a real (I mean feelable at your fingertips) difference, but using the qcom llvm makes a difference as well in smoothness as in batt life. Perhaps using some UBER >5 makes a difference, but that's very low on my priorities. If you want to try, tell me, what toolchain you want to try: aarch64-linux-android-5.x-kernel or aarch64-linux-android-6.x-kernel.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] TheFrozen4:
You are absolutely right, there's only so much you can do. Your OP is great as it is.

That is something I really appreciate. I've learned a lot the past few weeks. I know my way around coding in general, but Android is a pretty complex system with many, MANY subsystems and dependencies left and right. Following the discussions around this ROM is very helpfull in grasping the whole thing.

Thanks, me too! I love your work. Donation has been made, I know it's not much but hopefully others follow. ;)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] DeadPicsel:
I removed every single app am restarted my phone. I had the intention of restoring each app one by one until the fault came back.

Unfortunately this didn't work. I removed my apps and restarted and the crackling issue was present.

Is there any other way of finding the fault, I have a feeling this will be tricky.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Julian_os:
I flashed the rom version from the 3rd, booted, set up. Back in recovery, flashed stock gapps (latest) and slider is working
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] vincedyne:
Been on the hunt for a stable ROM with a bit more customizations than stock.

I finally found it! Thanks!

Camera seems to be working rather good, only random tints once in a while [emoji5]
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
I'm sure you followed the thread and read the changed OP, and therfor you know this configuration is no longer supported since 2 days in this forum.

[MENTION=4827031]TheFrozen4[/MENTION]: that's exactly, what I was talking about... :( If you have any idea, how to change this, I'd be more then happy to add to OP. I'm sure, we will see all related issues again, sooner or later - I bet for sooner... ;)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] WhipeeDip:
Alert Slider Fix

With talk of gapps breaking the alert slider, I found the fix. (Thanks to nvertigo67 for pointing me to this thread from elsewhere and TheFrozen4 for figuring out it was gapps's fault)

In terminal, run:

su -c 'settings --cm put secure cm_setup_wizard_completed 1'

Source: https://github.com/opengapps/opengapps/wiki/Notes-for-CMSetupWizard
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Removing apps and restart is not the same as clean installing - you would be surprised what lefovers are still there...

May I ask, which gapps you are using? Sound mods? music app? Equelizer? Anything regarding audio?

I forgot to report: tested with cabled galaxy s3 headset: no crackling or noise on the other side.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] DeadPicsel:
I use poweramp and mxplayer pro but that's about it. I have Kodi installed and all cast but no sounds mods or equalizers.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Nice finding! Cool workaround.

I think removing the cause (by using a gapps package, that let you complete the CMSetupWizard, which makws the workaround obsolete) is better then to work around.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] TheFrozen4:
I see. :)

Well, I can suggest a couple of changes to the OP that I believe would make it a bit more ... resilient ... against people like me. :good:

I understand why you would say this. Also why you said this about the real fix/workaround in code, suggested earlier. And, you are not wrong. However think of the implications: you will need to test and link to a working gapps package that is not too old (think months, not days). No matter the actual cause (inconsistency of gapps), I believe you will do yourself a huge favor if you implement the fix by removing the code dependency that, by the looks of it, simply enables the slider no matter the status of the SetupWizard. Consider it a buffer against gapps issues that causes your ROM to fault. Because you know where people will complain about whatever fault they find. :)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] vincedyne:
Would it be possible to remove the 5 fingerprint limit? ?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Vipeout:
How is screen on time for you guys? I am now at 32% with 2h17min SOT.

Standby time is great, but I only get about 3.5h SOT
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
I think yes - but it's not high on my priorities.

If someone wants to step in: I accept format-patch (my favorite), pointers to commits and even pull requests on github (I'll cherry-pick those, since I hate the ugly merge pull request comments in my gits histories).
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Consistant to my observations: standby/doze is slightly better then stock - screen on is considerable worse. I get roughly 5h (livedisplay screen mode is off and reduce batt is on; adaptive brightness is set, brightness slider at about 1/3, using natural profile (aka sRGB)).
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Vipeout:
You consider 5h SOT bad? :eek:

I have pretty much the same settings, except for live Display (Dispaly Mode automatic, Standard Color profile). I changed it to same settings as yours, let's see what happens. Although I doubt it will magically give me 1.5h more screen time
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] cmattern:
This is a nice way to build in the workaround and appreciated but I'd like to get to the root of the issue which seems to be that the ril we have been using is feeding up incorrect data. I was about to explain that I have a Nexus 6p running Lineage 14.1 that tethers successfully with out the need to modify buildprops thus proving that there is a problem with the ril in this build when the light bulb over my head went off (or on..) I grabbed my 6p, booted it up and checked the buildprops, the fix you listed was in there all of the time :eek:

[MENTION=4405529]nvertigo67[/MENTION] I apologize for not having thought to look there first. :( I have a build running now and will let you know what I find. It may just be that this is not at the ril level after all which would make solving it more important as it would affect all, or at least many builds.

My fascination here is at making LineageOS useful and accessible to the masses without the need for buildprop edits while still complying with carriers. Folks like us can hack all day and will continue to do so but OpenSource should not be just for us.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] lapapunk:
[MENTION=4405529]nvertigo67[/MENTION]

Hi. Thank you so much for your work. It's amazing. I'm in love in "natural" mode in live display, because it's exactly the same as sRGB mode in oxygen. Btw you was asking about other color profile, and I must say, that for me they all sucks.. Until I was switched Natural profile.

I have one more question for you. Can I use substratum with your builds?

P.s.

Your build is first after oxygen that will be my daily rom.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] t-shock:
I'm using substratum and everything is perfect.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] cmattern:
So I got the build up and installed, wiped system dalvik and cache and installed, had some issues that seemed to be related to older settings so did a data wipe and restored from backup. In the 141-work build tethering is still only enabled when net.tethering.noprovisioning=true which seems to have come with the build but it may have just carried over inspite of the wipes, either way the source libril did not fix the issue and the issue is not specific to the 3t.

I'll poke at this as time allows.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] apascual89:
On a side note, Acworth area? I'm in Dallas, GA area.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] cmattern:
Well how about that! We must do coffee some time.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] apascual89:
Yeah I added the llvm, quick question, as long as it's there in the source it'll be used if I have the Flag in board config set? Right?

My responses got lost in the quote lol sorry
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] cmattern:
Out running errands and noticing that the 141-work seems to be showing down Open Camera (noticeable capture lag) and much worse on battery life. Let me switch back and see of it's just my imagination.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
I'm not used to rr's source, and changes compared to laos. in laos it's just

BoardConfig.mk:TARGET_USE_SDCLANG := true

BTW: atm I have issue compiling the linaro 5.3.x version of gcc kernel toolchain - 6.x builds ok, but it's too beta for my taste.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Yes. But I should have given my numbers from stock: 7h on a regular basis. I have tomsay: stock had timemto settle - laos not: always flashing new test-builds... ;)

It's about usecase: atm I'm mainly check settings, try to reproduce issues, using terminal, hangouts, whatsapp and - yes, surprise - making or taking calls.

You shouldn't compare to my numbers, but to your own stock expirience: 25 - 30 % less sot is bad - that was my point.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Not on my side.

When using 141-work remember it's my working branch, also keep in mind, that some changes in device, kernel and vendor are connected. So, when working with 141-work sync often and always sync all three gits. Since laos cm-14.1 is heavy work in progress, it's possible to fetch a regression from upstream, depending on the time of last full sync.

Later today I'll push a new build with source build libril, with net.tethering.noprovisioning=true (if you find the root of the culprit, we revert that) and synced laos.

I have not decided finally, if I revert the check for cmsetupwizard completed.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
No. I want to build plain laos. It's just a matter of time, that cm theme engine is added.

I don't like theme engines anyway: just a new battlefield for random side effects. Look through the thread, please. You will realize, that I wasted at least 70% of my time on hunting phantom issues, not connected to the rom, but by gapps. Can you imagine what a broken theme would do to this thread? If people insists on using gapps packages, that proved are proved to have issues; I don't want to emagine what happens, ifma broken theme produces strange side effects: I can quit development, I can quit my job and argue the whole day here on broken themes, just to get "yes, but..." answers all the day.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] lapapunk:
Yes, I understand you. It's the right way.

But, it's so sad in same time.

Anyway, thank you so much.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Schrotty35:
Lol ok.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Update 20170206

Changelog:

switch to source build libril

update build fingerprint

remove dublicate dependency

fix device model logic

fix tethering for some providers (i.e. AT&T)

IMPORTANT:

I have no mapping for the new display calibration file, I tried my best to guess them, but I don't like guessing. So I need your help: go to settings->display->livedisplay and check the modes. sRGB is now called "natural" since the description matches what I see. Check all the modes, also eye5 and eye7, and tell me, if I set them right: i.e.: Hey, nvertigo, what shows up as cinema is photography. Thanx in advance for your assistence!

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

MD5: 4ddcc11017d1f37b9c731b693d5446ad
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] cmattern:
Hey [MENTION=4405529]nvertigo67[/MENTION] is this now committed to the cm-14.1 branch?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] m0d hipp¥:
Mirror: http://www.x-null.net/xda/nvertigo67/lineage-14.1-20170206-UNOFFICIAL-nvertigo-oneplus3t.zip
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
Hey maybe you can ask a mod to move your post to the first page. Then you can keep editing/updating it with new mirror links for the ROM.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] m0d hipp¥:
I don't think I would be able to do that since it's nvertigo's thread. He usually updates it when he comes across my post so I will tag him so he sees this and he can add it to the first post.
[MENTION=4405529]nvertigo67[/MENTION]
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
If the OP (nvertigo67) thinks it's a good idea and agrees to it, you or the OP can ask a mod (by reporting the post) to move your post to the first or second page. I've seen it happen before, so I'm sure it's possible.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Stephen:
We would have to have agreement from the OP to make changes to the first post. We dont edit without their knowledge.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] vincedyne:
Seems like camera blobs are out officially? Read on other threads..

https://github.com/OnePlusOSS/android_vendor_oneplus_8996N

Is this possible to add easily?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
No. Absolute impossible to add them, since this rom allraedy uses them since day one of this rom... ;)

https://github.com/nvertigo/proprietary_vendor_oneplus/blob/141-work/oneplus3t/oneplus3t-vendor.mk

Lines: 88, 93 and 94
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Use the source, Luke... ;) If you use the lg1 alias you can see it's only in 141-work. Before putting this in cm-14.1 I want to wait some days, to see if the new libril is breaking something I've overseen.

Rule of thumb: cm-14.1 holds the last known to be good changes; or in other words: cm-14.1 is the last build - not the current. Let's call it my way of very minimal QM.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] vincedyne:
Ahhh. Hoped that it'd be a fix for the tints ?