yashsingh1/xdaforums huggingface dataset:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] ngradt:
Hey! I just wanted to pop in and say thanks to the dev for maintaining this rom. Its been my daily driver for a looooooooooong time and the fact that its still getting tweaked and updated is awesome. Thanks :)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] brandontaz2k2:
Hey there. Also wanted to come in and say thanks for the great ROM. It is solid and runs like a champ :)

I do have a quick question however, with the OP3T stock ROM there was an option to switch between Wi-Fi frequencies 2.4GHz and 5GHz in the advanced Wi-Fi options. It looks like this option is not present in NLOS. I use this feature for my job for testing 2.4GHz Wi-Fi routers that also have 5GHz. The phone automatically connects to the 5GHz and there is no way to test the 2.4GHz unless you rename the network, which is not something I want to do on every job I go to. If anyone knows of an app that can change the Wi-Fi frequency to 2.4GHz or if the developer could be so kind to include that feature in the next update it would be greatly appreciated ;)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] abdulmajed1:
What are the update steps?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] AdroitAdorKhan:
What about your SS! It seems like an Xperia! :o Which one? Or, did u use any theme?!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] brandontaz2k2:
It was just an example, grabbed the screenshot from Google.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Encryption should work: https://xdaforums.com/oneplus-3t/development/rom-lineageos-14-1-t3547024/post74349018#post74349018
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Can somebody of the homebuilders try to build nlos-14.1, please? Is the resulting build booting at all?

I'm quite clueless: since topic n_asb_12-2017 is merged upstream I can't boot the resulting oneplus3t build, though the nlos-14.1 build for chagallwifi is still working fine. Because I havn't changed device, vendor and kernel, I have no idea, why the onplus3t builds havemstopped working!?!?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] cabrox:
Strange, i tried yesterday and gave me a warning of data corruption while encrypting, had to do a clean flash to solve it as a factory reset resulted in a bootloop.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
fs? log or pstore?

[MENTION=5073087]bu44er[/MENTION]: on what fs encryption worked for you?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
Hey [MENTION=4405529]nvertigo67[/MENTION],

Not sure if you remember me, I used to have your ROM flashed about 7-8 months ago, and was quite active here in the thread, I've just got a quick question for you:

To make my long story short, I've been getting constant battery drain, turns out it's because of "qcom_rx_wakelock", which is present whenever WiFi is turned on (no matter if I'm connected to any network or not). This is what I know so far, I believe it's a hardware issue, since it's present no matter what firmware or ROM I use, but I'm not 100% sure.

What I want to ask is if you've made any changes in this ROM/kernel that *should* reduce the likelyhood of said error occurring. If so, I'd be happy to go back to your ROM, just please let me know.

Thanks!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mumapizza:
its a good time to rethink EAS vs HMP. Eas pachtes are outdated maybe the situation changed by now that hmp will be the better choice. i used many hmp roms and dont experience any diffrence in smoothness or battery in comparison to this or other eas roms. This outdated and unofficial eas implemenation might also mean security problems who knows who checked it?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mumapizza:
your build flags are not the best for snapdragon 821.

Yours: https://github.com/nvertigo/android_build/blob/nlos-14.1/core/combo/arch/arm64/armv8-a.mk

source: https://developer.qualcomm.com/forum/qdn-forums/software/snapdragon-llvm-compiler-android/30197

https://github.com/AOSPA/android_build/blob/nougat-mr2/core/combo/arch/arm64/armv8-a.mk

correct me if im wrong
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
So ALL routers on your job have 2.4 and 5 GHz wlans configured to the same SSID? Since 802.11n as well as 802.11a/c are still in draft mode, this is surely something that CAN be done and MAY work with one device or an other. As sure: to achieve max. interoperability one should stick to 802.11 specs - draft or not.

That being said, this feature doesn't make sense on a mimo 2x2 device, since it can monitor BOTH bands.

Anyway, I'm happy to check the patches if they work with our kernel, frameworks and settings. Do you know, where to find them?

Read OP's update section.

It would be easy for me to answer the actual question with yes - because I'm announcing ALL changes in the changelog. On the other hand: I'm not planing to dig into this.

Thinking (and therfor rethinking) is always a good idea!

Unofficial: everything here is unofficial: NLOS is an unofficial los build... The eas implemntation is the official google opensource implemntation.

Outdated: outdated compared to what? They are the most current n implementation rebased against los and los-imported caf updates. Regarding bugs and sec hazards it seems much more frightening to me, that we use a kernel's EOL branch, and even this wasn't updated to current kernel.org version for over a year...

Anyway: development is on hold, since I can't make a booting build anymore. THIS IS A SHOW STOPPER.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
DEVELOPMENT IS ON HOLD! I CAN'T PRODUCE A BOOTING ROM ANYMORE! I can't bother with optimization, when the rom isn't booting at all.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] horqai:
What a bother for you :(
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
What is your point?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
I'm not able to produce bootable NLOS builds anymore. This means:

no updates

no development

The next sentence is burning in my heart: I can't recommend using NLOS any longer, since I can't update the sec level any longer. That's sad, but it's the way it is. And I prefer to admit that I'm not able to maintain a dedecated 3t build, then serving something outdated. If I find a solution I'll change the timestamp in the title again.

Thanx for using nlos.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
Rip. A good time to switch to oreo I guess. It was a good run.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] horqai:
I just wanted to express that it is sad that you spend so much time for developing this ROM and now stuck with a broken build at the moment / at the end. Like this new hyped game "Getting over it", when you fall down all the way. Nevertheless I'm far away from understanding what you are most of the time discussing here. So thank you for the work you've done so far!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] yannmrt:
That's really a sad news.

Your ROM is very nice, I use since long time now, and always get my phone working without any problems.

Even if some people are not happy or think it could be better for any reason, so let them talking and let do THEIR ROM.

They may forget you do this only on your free time, without any compensation. And this what make your and all developers very valuable are respectful people.

Thank for your time and all work you did and will continue to do. I REALLY appreciate.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Good news: found the little, ugly, hiding ****er! I'll make an sec patch updated build later today! :)

https://xdaforums.com/android/devel...ntegration-t3711635/post74830827#post74830827
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
UPDATE: December android security bullentin update (n_asb_12-2017)

Build 20171213

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.

Changelog:

Fix WireGuard kernel additions. (See: https://xdaforums.com/showpost.php?p=74830827&postcount=92) This one made my day... oh, yeah... ;)

mcpu: use cortex-a57, if 2nd cpu is kryo. — [MENTION=6468900]mumapizza[/MENTION]

Bootlogo choices

nlos_bootlogo-v0.1.zip

back_in_black_bootlogo-v1.0.zip

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

Happy flashing!

chagallwifi build will be updated during afternoon.

EDIT: chagall build available for download.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] xpissio:
Glad to see you're back. (Even if it was a short absence/problem)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mumapizza:
Compared to the current caf kernel used in for example the sultan rom. I dont know if lineageos updates their kernel according to caf but if you take the current caf kernel for nougat and sd821 and compare it to eas patched kernel I bet my arse the caf kernel will be better in every way possible.

The latest kernel would be from Nov. 20 retesting eas patched against this kernel would make sense, as this kernels are built and updatet with hmp in mind in comparison to half year old eas patches on dont know how old kernel.

https://wiki.codeaurora.org/xwiki/bin/QAEP/release

https://www.anandtech.com/show/9778/qualcomm-snapdragon-820-experience-hmp-kryo-and-demos
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
The problem was me being too sure I havn't changed k-sources (what was completely correct - but wireguard is patched-in/updated at build time). That wg is working with chagallwifi with thw new wg updates, doesn't help much, either. Having that not on my mind made me think I had patched the rom to agony - after checking each and every los commit after 9th of December.

I know I can't audit every single line of a source build rom, but with my dev philosophy that doesn't allow me to push a rom with well known security riscs. YMMV.

And exactly that situation was reached - I was sure I've checked everything, before "git status" wrote in bold red letters: "Idiot, of course the k-source was altered!" (Na, ok, the exact phrase was an other - but the letters were red... ;) )
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
God, I missed that... *lol* Why do you think a kernel based on oss (which in turn is caf based) isn't caf based... *lol*

Our latest upstream meege is https://source.codeaurora.org/quic/la/kernel/msm-3.18/tag/?h=LA.UM.5.5.r1-06100-8x96.0 upstream comitted on 20th of October... We are missing https://source.codeaurora.org/quic/la/kernel/msm-3.18/tag/?h=LA.UM.5.5.r1-06300-8x96.0 atm, but I'm sure it's merged soon. This is indeed a little bit behind - I can live with that... ...and wouldn't call it really outdated.

While writing and searching the links I found this: https://github.com/LineageOS/androi...mmit/67239ee11dcdd68c49905a4d129ce64f251c70d0

(Murphy hits again: the squashed commits was pushed minutes after my sync for the last build... ;) )

This will be in the next build.

Since marlin has switched to O I don't expect any updates to the n-eas-kernel, but I'll check from time to time.

To make it short: I don't agree on "nlos kernel is outdated". I have registered, that you don't like eas. NLOS is about freedom. Why don't you run nlos with a hmp kernel? (It's really easy, since I have switched to the unified hack blob layout.)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mumapizza:
Look at these guys own numbers with eas: https://xdaforums.com/showpost.php?p=69762512&postcount=2

its wasnt even beating hmp back then, all im saying is by now it might be even worse. and the userpoll of this thread shows its pure placebo
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
I haven't noticed a difference lol. I just heard it's supposed to be better and this rom had it, so I used EAS.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] TheGatorade:
Encrypt it with stock rom and then flash this one.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Karma can be a ***** (mostly, when dating Mr. Murphy... ;) ):

I just merged the 06300 branch, just to find ALL versions of wireguard prevented the resulting kernel from booting. Then I decided to do the complete drill:

current NLOS kernel (caf-06100): works with older wg kernel code - but not with current wg sources.

current NLOS kernel WITHOUT eas patches: works with older wg kernel code - but not with current wg sources.

new NLOS kernel (caf-06300): neither is working.

new NLOS kwenel WITHOUT eas patches: neither is working.

wg is work in progress, and [MENTION=5434776]zx2c4[/MENTION] tries to serve all roms/kernels. That's a tough goal, and I'm pretty sure he will accomblish this. Let's see what the next days/weeks will happen on wg's side. I'm looking forward to getting the modulized version (wireguard.ko). Since the app needs root previlegs anyway, it should be possible to load/unload the ko on demand from within the app. This would allow the rom/kernel to work/boot - even if an update to wg is errornous (wg isn't working then, of course).

I tend to temporary drop wg and wait till building ko is fixed. But I'll check again, when doing the next update.

For the poll: does anybody know how to change/remove it?

For the placebo: I don't feel any difference on speed, too. For my usecase bat lasts 5 -7.5 % longer. Both expiriences my differ according to different usecases. At least I havn't expirienced any drawback. As somebody, who follows this thread for a longer time, you might remember my personal main reason for switching to eas wasn't and isn't supirior speed or bat (as long as not worse then stock los kernel), but themdesign itself. I'm quite sure in the future we need more intelligent resource managment (freq in relation to workload, responsiveness, foreground/background balance, temperature, real-time demands, ideally assumptions on "what happens in the next split second to - example only - next 10 minutes" and so on). EAS is a step in that direction. I don't say it's the best solution, nor the only one (qcom's perf framework is a different approach, i.e.) - but it's a new and more complete approach then hmp (atm - of course! I'm rethinking how to proceed on a regular basis).

I.e. a scheduler, which is good enough for bsd on a pdp11 will not serve a 8996 soc. Even if the pdp11's powersupply could serve thousands of msm8996s... *lol*

It's only rock'n'roll - but I like it! ;) I always claimed I just like the design idea. voxpopuli has an inner beauty to me.

It's completly ok, that you prefer hmp. Feel free to use an other kernel, please. I don't want you to come to my oppinion (and my preference for eas is just an oppinion) - I want maximum freedom of choice for NLOS users!

The "new" kernel (merged caf-06300) without wg is attached. unzip and flash the contained boot.img as image in twrp.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mumapizza:
that might have changed by now

try compiling it with a different toolchain
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Maybe. The numbers are from the last two weaks, compared to the time between my gps optimizing and eas bringup. That are in deed the only two time frames, when I had a chance to observe three charging cycles. I'm always curious - but I don't know how to get those time frames...

just using the plain los kernel and stating after 12 h or so it's better or worse, would be not a fair test.

Perhaps one of the homegrowers is willing to jump in here - if so, drop me a note, and I'll prepare the branches.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Dhairya:
wait new kernel i am getting issues with the latest build aftr flashing this wakelock and deepsleep got me trouble is it only me even heating while charging is occurring aftr flashing this sorry for my english ?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Havn't tried charging yet - but over night drain and usage drain seems normal to me. Try wiping cache/dalvik. To go back just dirty flash the rommagain, or get the boot.img out of the rom's zip.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Dhairya:
did it so the new boot.img has issues of wakelock and drain u mean latest version is good <3
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
No. I mean, what I've written: I'm NOT expirience any drain or wakelocks. And I've suggested to try cleaning caches. If that doesn't help, try the last kernel, YOU implied it's better... ;)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Xellotath:
Double checking: it's safe to use "twrp-3.2.1-0-oneplus3t.img" for us? no more need to stick to "3.0.4-1" ? (OP in https://xdaforums.com/oneplus-3/one.../recovery-official-twrp-oneplus-3-3t-t3543391 needs updated?)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
I've switched to 3.2.1-0, when debugging the non-booting kernels. Both are doing their job.

Thanx for the heads up, will change OP to "most recent".
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Xellotath:
-delete-
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
End of EAS support

...it's all [MENTION=6468900]mumapizza[/MENTION]'s fault! Kill the messenger... ;)

Honestly: [MENTION=6468900]mumapizza[/MENTION] was right when suspecting the EAS merge beeing the cause for the mysterious issues. Obviously the KBuild/Kconfig on my eas enabled keenel was running fine with exactly the configuration I've used - changes, like enabling modules yield some really strange effects...

I want to emphazise I don't know if the patches or my merge was the root ofnthis breakage, but I guess it was my merge.

Though I still like the idea of EAS, I stick to my policy of only adding something, which doesn't break anything:

EAS is droped.

[MENTION=6006342]Homegrow[/MENTION]ers: I'm going to make the nlos-14.1 branch "eas-free" and keep the current state (eas enabled) as nlos-14.1-eas. If somebody wants to track down the eas issue, feel free to start from nlos-14.1-eas. This means also, the nlos-14.1 keeps unbuildable, till I'm finished.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mumapizza:
is there any reason for this not to be in lineageos sources? -> https://github.com/sultanxda/androi...mmit/8eb7f7797a19cf476b7785a1cac78a1270ef1b55
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Immortalis:
Quick question: does padlock in recents work? Every AOSP ROM I've tested seems to have problems with keeping app in RAM and I'd like to test this one
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Differences from ob15 to 4.5.1 are marginal (not sure without so3ce, but it seems to me just the dates in the firmware blobs have changed). aptx codecs are only shipped with open betas, but not with releases (ask OnePlus on that). If you want to use aptx from beta with release, you need to pin the aptx stuff, or they will void if extract-files.sh is run against the unpacked 5.4.1 zip.

If it's not working like expected on los chances are rare it's working on nlos. If you would give us a test-sczenario,msomebody will check and save you from a clean flash.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Immortalis:
Just open a few apps you'd like to be kept in memory - for example dialer, messaging, camera, click the padlock icon on every one of them and wait a few hours - the apps should open instantly and there shouldn't be a loading screen.

In OOS for example, padlock locks in memory and locks from being deleted from recents.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
It IS working - until lmk and/or background limits kick in.

You are just wanting me to cry about the removel of eas: resource managment has grown ****ing complecated (it's relaly similar to eas and scheduling). Currently we are in an situation, where this increased complexity is addressed in many places - and not all of the "places" know of each other. Without digging into this in depth, I think if you want an app to stick in ram, you not only need to tell frameworks, but bg limits need to be changed as well as lmk parameters... - propably iop is also in this process, I belive... Then again: if you stick more to ram then its size can bear, you need to override the pad locks... If you have patches I'll look into them - but it's far behind my scope to code this.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Immortalis:
Sorry, but I didn't say anything about eas removal - I was just asking about reliability of the feature. Please calm down.

First sentence is enough for me, thx.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
I know you doesn't ask for it. You didn't get my point: resource mangagment has become more complex. To handle increased complexity in an appropriate way, we need a smarter approach to take all subsystems in account. For scheduling a smarter approach (even if only a first step) was eas. Your issue is an other aspect of the increased complexity: I would like to address this (as I likes to address it in anmother area with eas).

I'm not uppset at all - I'm sad I can't fix it, aa I'm sad I needed to remove eas. If I'm uppset, my postings have an other "sound" (long term users know that).

Short: I know resource managment is MUCH!!! improvable - sadly I lack the abillities to fix it this weekend... ;)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] shawek:
For me,last build won't boot.nano gapps,superuser,twrp86.1...Boot time is long(never ending),blue led keeps blinking like its doing something,but phone stays at NlOS logo.let's wait and see what others say,maybe its only me.

Sent from my One+3T
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Exact versions, please. Otherwise the information is useless to help you, as well as to keep others informed.

I'm using currently

twrp-3.2.1-0

ob15 fw [obligatory!]

[optional: nlos-bootlogo]

Beans mini (0725)#

addonsu-14.1-arm64

without any hussles.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] opethrocks:
The newest build 12/17/2017 will not boot for me. I'm using twrp-3.2.1-0 to flash 1. Ob15 firmware 2. Nlos 12/17/2017 3. Addonsu-14.1-arm-64 3. Beans mini gapps 07/25/2017.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] horqai:
No issues here. I've used Magisk for root.

Wiped system, dalvic cache and cache.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] shawek:
Twrp bluespark 86.1

Clean flash(full wipe except internal storage)

Nlos 17.12(last build)

Open nano gapps 15.12

Superuser.zip 2.85 sr5

Busybox 1.27.2 yds universal

*Phone stays at NLOS boot logo while blue light blinking*:thumbup:

Edit:I think it has to do something with superuser...

Sent from my One+3T
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] wistlo:
20171217 not booting, reverted to 20171213

Boot failure (boot animiation ran 6+ hours)

Dirty flash from 20171213

Nano GAPPS from original post (but many updates via Play since, as this is dirty flash)

Magisk 14.0 (removed by .zip as first install .zip, reinstalled after NLOS flash)

TWRP 3.1.1-2 (working for 3+ months)

Phone boots into boot animation, then stays there.

Restored 20171213 from full nandroid backup.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Really strange. Are you sure about bootanimation or is it bootlogo? If it's really the boot-animation get pstore, please.

I've dirty flashed from 13 to 17 without any probs.

Substratum theme?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] spida_singh:
Dirty flash here worked fine

ROM

Gapps Nano

Magisk

Magisk Modules

Wipte cache / dalvik

Used blu spark latest twrp

Thanks
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] opethrocks:
I tried all night to boot the 12/17 build. I tried switching back twrp 3.0.4-1, using magisk instead of add-on su, and even full wipe to no avail.