yashsingh1/xdaforums huggingface dataset:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Hi Stephen,

you are fast! Thank you very much for offering your assistence! I would be more then happy if you could put
[MENTION=341181]m0d hipp¥[/MENTION]'s posting to #2.

(Didn't know this is possible since some minutes ago - it's an awesome idea/function/service.)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Stephen:
I'll make the request now to have post #2 changed to him. It should be completed shortly! Will let you both know.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] cmattern:
Got it, building from 141-work now, will run with it today.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Stephen:
[MENTION=4405529]nvertigo67[/MENTION] & [MENTION=341181]m0d hipp¥[/MENTION] Hey guys, 2nd post has been added as requested.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Thanx.

OT: thanx to all xda-people, for keeping this great resource for interchanging knowledge and expirience up and running every day!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] m0d hipp¥:
Thanks to you both.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] t-shock:
Another mirror at MEGA NZ server.

https://mega.nz/#!aYNkERIb!QyFzj6IZAchSL0TqIn-ZDIrsZulStkbDZi0RF1oyJcg

I will upload it later on, to the AFH
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] m0d hipp¥:
I put yours in post 2 as well.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] bowlandspoon:
I'm assuming your using it in Legacy mode or does this ROM/Lineage actually have the OMS commits?

I didn't think Lineage had OMS commits dues to CMTE etc?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] lapapunk:
Just read that was saying by nvertigo67 a few pages ago.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] bowlandspoon:
Yup just went back and read that, thanks for the reply.

Shame though. Hopefully LineageOS will make a decision soon regarding theming.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] lapapunk:
I hope for this too.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] cmattern:
So I did a repo sync and immediate build against 141-work and it's been good, no issues with performance or FC apps. I noticed three differences from the cm014.1 build:

Battery life is reporting about 30% less

OpenCamera lags significantly on capture

Builtin Lineage Camera no longer lags on capture (lagging was the reason I started using OpenCamera so 2&3 basically offset but I really do like the OpenCamera features)

I'm going to do factory reset tonight and see if these issues were just due to cruft from multiple builds. FWIW I did wipe /system cache and dalvik before installing 141-work
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Factory reset in twrp is wiping caches and data. If you stick to (beautifull and redone OP; thanx to [MENTION=4827031]TheFrozen4[/MENTION]) OP you do that by wiping dalvik/art, system, data and cache.

For batt life: get bbs (betterbatterystats) from the thread here on xda (free) or from playstore (payed) to see what is drainingmyour batt.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
There is some hype of people claiming new camera blobs was released. This is due to a missleading commit message (it's only missleading, if you don't know the differences of laos and oss build system and don't look at the commit itself). This posting is for [MENTION=7896746]koenkk[/MENTION]'s gits, but aside from the line numbers it`s the very same situation for our rom:

https://xdaforums.com/showpost.php?p=70932180&postcount=652
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Duncan1982:
Very Detailed explanation & informative, now hopefully the conclusion is Satisfactory for those in doubt......:good:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
OT:

I think that's a good example on how information is spread over the net. I truely respect and apriciate the devs traped by this misinformation. I'm sure none of them was spreading this misinformation by intend to fool anybody!

Even more OT:

In politics we have seen recently what can happen, if you start spreading false information by intend... :(

Be awake, always ask for the source of information!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Duncan1982:
Like anything in life and please don't pray to "The t.v gods" its important & imperative that we learn to question..... Never ever loose that or you become subservient to the system.

It was great that nvertigo took interest (not to be all lord and mighty to disprove) he took interest and asked a question and investigated ....that I very much like....:good:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Vipeout:
Not sure if people are aware, but someone actually ported the OOS cam. I tried it and I confrim its working!

https://xdaforums.com/oneplus-3/themes/port-oxygenos-stock-camera-cm-t3451721

This was the last missing piece for me. Finally, this Rom i a complete experience for me :)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Best thing about N version compared to N version is, that it is installed as user app: no messing up system files! Great finding.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] cmattern:
Thanks, I'll get a look at bbs, it would be good to know the real reason. FWIW I had already been wiping system cache and dalvik, the factory reset WS just my version of the next step, in reality would have been faster peer the OP, old habits...

So the OpenCamera lag remains and I'll take that up with that Dev when time allows, built-in is very snappy and more than adequate to my need.

Battery life seems much improved but I'll know more by end of day.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
When reading your post the first time, I thought you are doing two steps (factory reset; and wiping art, system, data and cache), I just want to save 5 seconds of your lifetime... ;)

Give the battery one charging cycle (at least) to show its real power. (I know, it's hard not to flash every day, once the build system is up and running, though... ;) )
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Istvan_86:
Hello guys,

I want to try this optimized version of LineageOS for OP 3T and after a bit of reading this thread I have one question, the rom includes any form of root and if it has, can I use Magisk?

Thanks in advance.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
It's prerooted (laos superuser baswd on koush's superuser). I don't know about magisk, since I don't use it - which doesn't mean it's not working.

Make a nandroid and try. Please report back; I'm pretty sure you are not the only one interested in this.

If you need a build w/o root, let me know - [MENTION=3044422]mad-murdock[/MENTION], [MENTION=5226211]cmattern[/MENTION] or me will do that for you the next days.

(BTW: I'm waiting for requests to put the skip safetynet patch in - since I don't use any apps that try to forbid root or relay on safetynet, this will never happen if not requested.)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Istvan_86:
Thanks for the fast answer,

I was doing a back right now. For me skip safetynet it's very nice and Magisk do it.

I try to flash your rom today and try Magisk (if I'm not wrong Magisk removes other root forms) and post results here.

And for last, I think that I don't need a non rooted ROM. :D

Cheers.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] SourPower:
i wish we had more devs like you that are actually working with the 3t and not just putting out unified builds...

thank you for your time and efforts and i look forward to using this once i move off of stock lol

subscribed
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] m0d hipp¥:
Sure, add the "skip safetynet patch" in, why not? :)

Also, this is me being super nit-picky... but since we're on the topic of requests, when you change the battery icon on the status bar, is it possibly to display the percentage of the battery to the left of the status icon instead of the right side? I know it's not a big deal, but I feel like it clutters the time a bit. Maybe that's just me though. If there is an option for user to choose how they want it in the settings, that would be cool.

Also, just as a follow up to some questions I asked earlier on in this thread, has anyone run into the Mobile Radio Active bug with this rom? My understanding is that Nougat still doesn't have the "official" fix set in place for this bug, so would it be possible to apply the fix to this rom?

Another thing I noticed is I didn't see an option for dozing/hibernating the apps. Has this been moved, or just not added in this?

Also 1 other thing I noticed, and once again not a huge deal, just curious. When I run benchmarks like antutu on stock 3.5.4 I get around 160-167k score, but with this rom there is a significant drop. Is there a reason for this?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
I think you can. why? In the days, when this rom wasn't born yet and for laos roms was the root-enabler-zip not yet available - aka the week or two where no laos-root solution existed - I used magisk as well. I would be quiet surprised, if that has changed. But still, make a backup before testing.

And tell us your findings (=
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
To my knowledge it doesn't work with prerooted roms, anyway.

I want to stick to plain laos user expieience - so this would be a feature request to laos.

Sadly there is no such thing like official fix set. The abandond cm commit someone pointed me to is not really fixing this issue. But since I have idle batt usage of about 0.6 % per hour, I think I can say, I have not expirienced this bug, yet.

Do you mean the doze option in dev-ops from the time doze was experimental? If so: it's on by default now. But you can adjust this on a per app basis: Settings->Batterie->3dots->batterie-performance-foo-bar->select all apps

Honestly I give a **** on benchmarks numbers - but I like antutu for stability testing. For the current rom I run it twice: both times over 161,000 points. If you like high benchmark numbers, run it several times, get a kernel editor and change governor to performance (or echo on sysfs); before each test reboot and wait 5 minutes after reboot completed, before testing... but: speed is what you feel at your fingertips - not what antutu and collegs are measuring!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
I am not so sure. Even LaOS with root disabled comes with su, so you can enable it for ADB, just not for apps.

When running safetynet test app our ROM doesn't pass CTS test, nor the easier basic integrity check.

I was too uninterested in safety net to read into it. maybe I should. Can you link that patch, then I run a test build with it and try both with root, but disabled and without root.

Magisk should also always be a way to pass safety net on any LaOS ROM. Again, I tested it a while back on unified.

But something woke my interest now.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Istvan_86:
Hello both,

Magisk working 100% including safetynet without any kind of issues. You say somethiing about feature requests, I have 2 things in mind:

1-More configuraton options for alert slider or at least the same as OOS (maybe we have an alternative with some kind of app to modify that?)

2-More quick tiles settings

Excellent work here, I´m goiing to test it!!

Cheers.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] t0pg3ar:
Building goes wrong

I'm trying to understand more of the process of building Android, so I followed the Readme on GitHub to understand how to build this ROM and gain some first knowledge. Now, everything goes well, until the building begins: The "make clean" command of ninja fails. FWIW, I'm building on an x64 Ubuntu 16.10 with Java 8 (and the rest of the dependencies).

The following issue appears when just executing "make clean" (note that my real name was replaced by my nickname ;)):

/media/t0pg3ar/Data/Android/cm14/out/build-aosp_arm-clean.ninja is missing, regenerating...
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=7.1.1
LINEAGE_VERSION=
TARGET_PRODUCT=aosp_arm
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a
TARGET_CPU_VARIANT=generic
TARGET_2ND_ARCH=
TARGET_2ND_ARCH_VARIANT=
TARGET_2ND_CPU_VARIANT=
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-4.8.0-37-generic-x86_64-ith-Ubuntu-16.10-yakkety
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=NMF26V
OUT_DIR=/media/t0pg3ar/Data/Android/cm14/out
============================================
Checking build tools versions...
Starting build with ninja
ninja: Entering directory `.'
[100% 1/1] Entire build directory removed.
FAILED: clean
/bin/bash -c "(rm -rf /media/t0pg3ar/Data/Android/cm14/out/* /media/t0pg3ar/Data/Android/cm14/out/..?* /media/t0pg3ar/Data/Android/cm14/out/.[!.]* )"
rm: cannot remove '/media/t0pg3ar/Data/Android/cm14/out/host/linux-x86/bin': Directory not empty
ninja: build stopped: subcommand failed.
build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1

So, automatically I check whether that's true and yes, out/ isn't empty:

t0pg3ar@t0pg3ar:/media/t0pg3ar/Data/Android/cm14$ tree -a out/
out/
└── host
└── linux-x86
└── bin

3 directories, 0 files
t0pg3ar@t0pg3ar:/media/t0pg3ar/Data/Android/cm14$

I first thought this was due to ninja being outdated in the standard repos, so I got the most recent Linux binary for ninja from GitHub and placed it in ~/bin/ and then "chmod a+x"'ing it. Which worked fine, by the way:

t0pg3ar@t0pg3ar:/media/t0pg3ar/Data/Android/cm14$ ninja --version
1.7.2
t0pg3ar@t0pg3ar:/media/t0pg3ar/Data/Android/cm14$

However, this didn't help, as you can see. The building directory is not on ~, but on another internal drive with more space (4TB HDD vs. 256GB SSD). Do you guys know how to solve this issue? "sudo make clean" doesn't work either by the way (which makes me happy, because using sudo in this case doesn't feel right).
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
Great to hear it works. No need for further testing then for now.

About feature requests, we don't add anything that is not hardware related to stay as close to official LaOS as possible.

The alert slider though is another story. It might be possible. And yes, LaOS functionality lacks the one of OOS. No surprise though, since most UI patches are done for all devices in mind, by developers probably not owning a 3t. We are special.

---------- Post added at 10:06 PM ---------- Previous post was at 10:00 PM ----------

I guess it's connected to making clean before the first build. LaOS sets up some stuff even outside the out/ directory.

Try a full build first and then try the clean.

Also ninja is not a dependancy. It's just used from the compiled environment. I initially had the same impression, installed ninja and later uninstalled it again. It builds fine without it.

Some your out isn't empty, did you do a full build already?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Istvan_86:
Hehehe, ok about features ^^

I also detect that camera isn´t working, is this normal? I download open camera and works fine. :S
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] t0pg3ar:
It seems you're right! The error is part of the ./my-build command (as it automatically cleans) and knowing compilers, errors are bad :p So after running ./my-build, it popped up again. I simply tried to replicate it with "make clean" for the post above. It is tugging along nicely now. Takes forever on an hdd though... I'll keep you posted! Maybe it was some loose error without any further effects. We'll have to wait and see. Thanks for the reply!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
Should update the README then.

About forever. Yeah, it takes forever. I use 2 SSDs, one for source dir, 1 for ccache. Ideally one more for out/, but you can only have so many SSDs. With empty ccache it takes about 1:30h to build, with filled ccache a bit less than 25 minutes. Intel i7 6700k and 16 gigs or RAM. I know of people on notebook on the road who need 8 hours and more to build.

I miss the old times, when you could put out/ into a ramdisk.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] m0d hipp¥:
I wonder how my system would handle it.

I have a i7 6800, 32Gb ram and 3 SSD's. Only caveat is I'm running on Windows 7x64, not on linux, so I might need to setup virtualbox or something. Hmmm. Trying to figure out what the best route to install a dev workspace for rom development.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
The BEST is installing a native linux. But as I heard from another dev how depends on windows, running the build in a VM - iirc he used vmware - only is about 10% slower than natively. This machine is also my gaming PC, but for building LaOS i prefer to reboot to arch linux and build there. None of my tasks are bound to windows, most run in browser (chrome user on all operating systems) so I dont mind much, which OS is running - on the contrary, I prefer Linux as long as no gaming is involved.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Mr_President:
This rom was the one that made me move from stock rom. And no regrets! Damn smooth and insane battery life!

---------- Post added at 04:02 AM ---------- Previous post was at 03:59 AM ----------

I've been using this camera app for a while now. I just wanted to ask you something. If you open the app, record a video, swipe into gallery and then try to play it back. Does the gallery app crash for you?

EDIT: Should mention that this is with v4.1, 1080p and LaOS gallery app. Haven't tried anything else
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
This one is easy: ninja is reporting an error (to do so, it hat to be there) from rm. This is the original error. rm can't recursivley delete out/.... This is to 99% an permission error. Try this: "sudo rm -rf out", and restart the build process. Try to remember what you have done: if you do your very first build after the initial repo sync, there shouldn't be an out dir at all.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Notification slider

I LOVE it the way it is: if you chose "priority only" for a position, go to Settings->Sound->Do not disturb->Priority only allows to configure, what is priority for you.

What setting are you missing from oos - perhaps we can help you to configure laos to you liking.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Istvan_86:
I´m a bit obsessive with some things and one of them is alert slider :D Your advice about priority it´s nice and I have got it in mind, but I have a enormously ridiculous list of contacts and set all the prioritys that I need is a work that I don´t want to do :D

I just need 3 options:

1-Vibrate for everything, emails, whatsapp, calls, etc

2-Only alarms (we have this)

3-Sound + vibrate for everything

Also I don´t know if I post that I have 2 extra issues, one of them very important:

1-Camera doesn´t work for me, using open camera without problems.

2-Of course, before try your rom I made a backup of my daily rom (FreedomOS) but now after I restore it, when Android starts it asks for a PIN I always use the same but it´s not recognized. Maybe it´s an issue related to the version of TWRP that I use to make the backup? I think that I made it with TWRP 3.03.4-0 and I updated to 3.0.4-1 to install your rom.

Thanks in advance.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
This is quite unspecific, as is my answer: camera is working here.

I havn't tried 3.0.4-1 yet, that's why I havn't changed the recommandation. But as with your first issue, a bit more information would be helpfull: fs? encryption or desktop pin? Have you tried resetting your desktop passphrase? Have you done the backup according to twrp-threads recommandations (setting both passphrases to nothing)? Have you checked with the twrp-thread if 3.0.4-1 has any regressions?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
1 is in power menu (activate in dev-ops; longpress power->select vibrate icon): it doesn't make sense to have it redundantly on the switch.

3 is allready there: laos stock setting on position down.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
That's a well known TWRP issue. Searching the TWRP thread would have solved it.

In TWRP, go to File Manager, navigate to /data/system and delete locksettings.db. You have to do this after each and every restore.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Istvan_86:
I´ll check this as soon as I have a bit of free time, I´m at office right now.

1-I have my OP 3T encrypted and I have set a 6 digits pin to enter android after input simcard pin.

2-I don´t know how can I reset my desktop password if I restore my previous backup. (I think that for desktop you mean enter launcher right?)

3-About twrp-threads recommandations and set passphrases to nothing, I don´t know what is that. I read a lot in TWRP thread but I don´t remember read something about that and I don´t see that option inside TWRP.

4-I think that 3.0.4-1 is the recommended version in the thread to flash

5-I use EXT4 for System + Cache and F2FS for data

6-I´m a bit noob reporting logs or similar, how can I provide more info for you?

Thanks in advance.

---------- Post added at 12:01 PM ---------- Previous post was at 12:00 PM ----------

I also try this and post results. Thanks!!!!!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] t0pg3ar:
I went from building on 1 SSD to 1 HDD, the time to build doubled. I'm on an Intel i7 6700k and 16 gigs of RAM as well by the way. No ccache here though.

What happened was that at first build, I got a missing dependency. I believe it was the package "schedtools". Well, after installing that I ran ./my-build again to restart building, but the cleaning failed because of the error above. I nuked everything later on and began anew. While the error's still there, the ROM gets built perfectly. I tried to build 2 times, the second time with the full out directory of the first build. While it couldn't be emptied completely (the were still some subfolders of out/), building went fine. I guess the error doesn't have an influence on building.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Istvan_86:
Delete locksettings.db fix that issue, I need to restore my original rom because I must do a small travel tonight. Tomorrow at early hours I restore the backup of your rom for the entire weekend an test it. :D
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
make clean is working wundefull. Can we please check, why the rm command failed?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
you sure you didnt work with different user and/or root in any of your attempts? since there is no real other reason i can think of that doesn't allow you to remove out/*
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] t0pg3ar:
I checked the folder for its rights and I am the complete owner. There's nothing weird about it. I just tried it again: It cannot remove out/* because of its subdirectories, although it executes rm -rf. It now also includes "rm: cannot remove '/media/t0pg3ar/Data/Android/cm14/out/host/linux-x86/framework': Directory not empty", which is odd, because it didn't do that earlier. However, the fact that the folder cannot be removed doesn't seem to have an influence on building. I do see the error message when using ./my-build, but the make command follows through and doesn't quit. I'll just leave it be for now. It is odd nonetheless.

EDIT: Hold on, there is a file!

t0pg3ar@t0pg3ar:/media/t0pg3ar/Data/Android/cm14$ ls -la out/host/linux-x86/framework
total 1980
drwxrwxrwx 1 t0pg3ar t0pg3ar 4096 feb 9 21:28 .
drwxrwxrwx 1 t0pg3ar t0pg3ar 4096 feb 9 21:28 ..
-rwxrwxrwx 1 t0pg3ar t0pg3ar 2016745 feb 9 10:55 .fuse_hidden000ef4390000000f

Now where did that come from?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
Are you by any chance not on an Unix file system, but on ntfs or another?

There really is no reason for rm to fail.