[Android Software Development] guitardedhero:
Let me take a moment to personally apologise to each of you having had a rough couple of days resulting from changes introduced in the last build, possibly even more.

Even though I did not acknowledge what was being reported for 20180129-1, I did read the many reports and I knew that a significant shift was necessary for the next build I would make available to you guys.

I spent the first 24 hours or more addressing the obvious and the not-so-obvious, and then spent the previous 24 hours on the boot scripts which yielded full support for Enforcing SELinux mode.

It may not matter much to many of you, but requiring Permissive SELinux mode for anything I make available on a scale such as this feels like defeat and gives an appearance of irresponsibility/laziness, so this is a huge gain for me, personally.

The requirement for Permissive SELinux mode possibly could have been limited to few devices such as the OnePlus 5, but that is the only device I am able to test and can confirm that Enforcing SELinux mode is every bit as supported on my OnePlus 5 as it was on Permissive SELinux mode.

For those that like fun facts, this port was done entirely on the OnePlus 5 device as the timing correlated precisely with some serious marital problems placing me on friends' couches for about a month without my laptop. I've been home for nearly two weeks straight now.

Please try today's zip without any "tambourine dancing" except for cases where the default installation is NOT what is desired as well as for those already determinating that one or more files simply will not get along with the rest of the system.

Also, remember that any single update can make or break previous experiences on previous versions, and, of course, a different rom grants the same possibilities.

Finally, do not accept a bootloop scenario has occurred until a second forced reboot fails to successfully boot. As with SELinux mode, however, this anomaly could be unique to OnePlus 5 as well.

I still have quite a bit of catching up to do, but I am more psyched than I have been from the very beginning of porting this Dolby system, so hopefully that sends some good vibes towards you guys.

I have quite a demanding expectation on everything I do, but especially this particular port for some reason (it is likely the need to escape the ARISE umbrella for once since it started lol) but I am confident that you guys will direct this port's final improvements impressively.

Final thought, I swear lol...

Very soon, I will provide links for access to a Google Drive database for audioserver binaries (likely post #3). Please do not confused this with what is in the port, I have that already lol. I am interested in the native audioserver to the firmware on which the port is installed. I did not go as far as using a database like this for Axon 7's Nougat Dolby Atmos port, but I am sure some of you here witnessed how easily and quickly I was able to successfully predict success or failure with astonishing accuracy using nothing more than the native audioserver 's file size. Sizes are different in Oreo, but there may be more to it than that as well. Only one way to find out, though! :good: