[ONE Original Android Development] The Dork Knight Rises:
Dirty flashed 20160831 on 20160827 and everything's smooth :good:

I see you found your solution, but I had already clicked the multi-quote button, so I'll say something about this anyway.

In MM, I think the WiFi connection dialog automatically selected "No certificates" for the authentication certificate thingy (not sure, but we'll, I didn't have to manually choose an option), but in N you explicitly have to select one of the options or the Connect button will be grayed out.

If you were used to just directly inputting your identity and password on MM, you'll just need to select the "Do not authenticate" (something similar) as an additional step in Nougat. That's all.

I think that's the reason. If you dirty flash, directly flash GApps right after flashing ROM. Do not boot in between, or things will go haywire.

If anyone needs an explanation (this may not be a factual representation of what really happens, this is just what I have inferred from my experiences and experimentation):

- In case of this ROM, on clean flashing, we don't flash GApps. This is because if you flash GApps on a clean data partition, Setup Wizard will launch when you boot the first time (and currently the ROM doesn't have the automatic GApps permission patches, so your Setup Wizard will keep crashing when you boot). So you just boot into the GApps free ROM once, to populate your data partition. Next time when you flash GApps, it doesn't launch Setup Wizard, so you can go into Settings and manually give permissions etc...

- Now once you've booted, you most likely update some of the GApps that have been flashed to system (sometimes this is done automatically in the background, like for Play Store or Google Play Services). Note that the APKs that were written to system, remain there (that's how the "Uninstall Updates" button in the App Info for system apps works)

Any updates are installed to data partition, and the newer data partition overrides the system partition version during normal usage

- Now if you dirty flash the ROM, it fully overwrites the system partition with a clean system image, hence removing the system GApps APKs (most custom ROMs have a "GApps survival script" which automatically preserves GApps when dirty flashing, but of course a pure AOSP ROM like this doesn't have that)

So if you don't flash GApps before booting, the GApps that you updated will be crashing, as the data partition installations cannot find their parent APK in system. This is why when dirty flashing you should ideally reflash GApps.

I just flashed 20160831 and the SystemUI Tuner mod works perfectly on it. I dont have the "internal storage access" bug either, as [MENTION=6363737]7u5h4r[/MENTION] reported, so maybe that's a MultiROM specific bug, or it might have happened due to some entirely different reason for him.

The boot animation zip in my guide is the Marshmallow boot animation and I haven't noticed any graphical issues on it, it looks perfect to me. Also I definitely prefer Marshmallow boot animation over the bo-"ring" animation in Nougat :p

But if you want, someone posted a Nougat boot animation a few posts back, but apparently it's not "crisp" (I haven't flashed it so I don't know what exactly that means).