@Greywolf_Va yeah, there have been reasons: OT which didn't stoped, etas etc.
On N I lost interest because people tried to force me to release stuff, I did in the end to make them happy but it's not an Android version I really spend time on. there's some stuff around that, but the core reasons.
Lineage cleans builds after a while and since lineage13 isn't official supported builds are gone after one cleanup (don't ask me why they don't keep the latest build at least).
On 14 there's no interest my side for the official tag (it's a tag, nothing else). I am compiling if I like and feel like I can do.
Back on topic here:
About the FC:
If it's reproduceable let me know, maybe reproduce the issue directly after boot and catch a Logcat (logact is a mess if a system is running for some time already)
I got ya..At least I see the slim6 project has the check for update function back in it so I will be aware of any security updated releases that come out in the future. I try not to go off topic if I can help it, but didnt really want to bug you privately with something that perhaps someone could have posted a link to go see the background on what all happened.. but it's all good there.. Sorry again for the OT question there.
In terms of the FC, I think it was mainly due to the open gapps nano packing... might be something buggy in it, not with the slim rom itself. When I reflashed the rom with the delta package, it's running smooth as silk. Setup wizard went through properly, was able to sync with my Tab A to copy my google account info, and it installed all my apps just fine. Will say it seems to run a lot smoother than the Lineage13 did on the same tablet.. I had a bit of lag on that one, and many times waiting on bootup from power up to launcher screen up to 5-6 minutes.. with slim it is a whole lot faster boot up time. Love being able to tweak the navigation buttons again. When I hit the recent apps button, the slim screen works as it should, no FC issues now. Just seems strange that with 6 running this smoothly, why 7 is having the lag issue with the gapps being installed.. Just brainstorming a bit, but has there been any inspection done of package installer clearing it's cache of temp files when the package has finished installing? I recall when we were working on one of the many windows beta's we had a memory resource leak that would creep up and start slowing down responsiveness and cause programs to lock up before we finally hammered that out (windows 95/98/2000/NT) think we fixed it in either xp or 7 where we finally found the code that was the cuplrit.. thats why I am just offering a possible avenue of exploration.