[Moto Maxx Android Development] fgl27:
Below are some workaround for the most know problems.

Apps problems:

Android update always changes permission and some app may have some problems not related to Nougat caming from Marshmallow or lower, so check for app updates and know that may need some time until all app are 100%., give them the permission related to the featuring you are trying to use.

Pictures related:

One thing that I notice regarding permission is if you have a app that access a folder that was created in older OS this app may be able to access this folder but not fully access the files like the below example.

You take a picture or a screenshot and can't see or share it with some normal none root apps, the simple fix is just erased/delete the DCIM and or Pictures folder under "virtual sdcard" (or any folder were you face a picture or file related) off course backup the files to another folders first, then let the Nougat service recreate the folder if is a camera related (or manually make the new folder if is a custom folder mane by you), it will automatic recreates after you take a new picture or screenshot, test to see if the problematic app can see the new just shot pic/screen shot and restore yours files back to the new folder.

GPS / Radio:

Changing the ROM may cause GPS lock problem...

This help also applies to cases related to "no SIM Card" or "no Cell Signal level" in status bar.

To solve is necessary to erase the radio status, that can be achieved via this zip "Clean_modem_status.zip" flash it via TWRP no wipe is need.

If after you find any problem related to lost of signal, re-try the flash of "Clean_modem_status.zip", if the problem persist, flash latest radio.img version via fastboot (aka "via bootloader")

mfastboot flash radio radio.img

find the radio.img inside the stock ROM xml.zip, some xml.zip and fastboot for windows can be found here (click here)

Random Power off or reboots:

To identify if the device random reboot or simply power it self off check the prop "ro.boot.bootreason" if it is like the example bellow:

[ro.boot.bootreason]: [power_key_press]

Check the prop using :

Kernel Audiutor app > logs section > search in a log > mark getprop > search key word "reason".

If you have the above the device didn't reboot it power off.

If the Random power off are related to battery, BCL can help mitigate the problem.

BCL can be controlled via BHB27 kernel adiutor Power and battery section.

Lowering the BCL Max frequency or Making the number of hot unplugged core higher will help to mitigate the CPU power.

But if the problem persist is necessary to change the BCL low and high voltage threshold to higher values to make BCL to start sooner, the recommendation is to set they to 3700mV (Low) and 4000mV(High) and if the problem is resolved after that, the device stops randomly power it self off, lower the values 100mv it until you find a perfect value, or if the problem persist make the values 100mV higher.

XT1254 only

VVM app (VVM may only be accessible via play with the link, click here and chose open with play), VVM may not work correctly google has it on version is free and seems to work 100% Google voice, the in the ROM phone app also has a dedicated option for voice calls