[Android Software Development] sonophilos:
Presenting...

Dolby Atmos for Oreo Black 'n Cheese Edition - Unity 20180902

Changes:

Releasing this almost 4 weeks late, testing has been touch-and-go. Edit: I now operate on a ZTE Axon 7 (A2017U) on ZTE US stock 2.10B12 Oreo FW/ROM with its stock Dolby Atmos for Oreo, Magisk 16.7 (beta), and the ViPER module exactly as it appears below, so these releases are tested/working in that environment first. I do not utilize any other audio mods or AML with this environment, and ViPER is not (presently) functional for me in this environment, so I myself am not a reliable tester for full functionality of the Dolby Atmos for Oreo OR ViPER4Android modules OR their combination with AML at this time. This release is for Magisk 15.x/16.x and will not work properly with Magisk 17.x or with Android 9.0 Pie, nor is it intended to.

Updated base to Unity 1.7x FOR MAGISK 16. Numerous fixes from [MENTION=6037748]Zackptg5[/MENTION] including legacy volume button support. THIS RELEASE WILL NOT WORK WITH MAGISK 17.X OR ANDROID 9.0 PIE, PLEASE TRY 16.X/8.0 OREO BEFORE REPORTING ISSUES WITH THIS RELEASE.

If this zip does not appear as installable from Magisk Manager, flash via TWRP, install procedure is identical, just follow the prompts.

Custom "Black 'n Cheese Edition", "BlackRed", and "Inverted" themes for Dolby Atmos apk, inspired by @djdarkknight96's Sprite Substratum Theme.

Custom "Lover of Sound" dax_default.xml for Dolby Atmos - Music profile is preferred for intended effect but all profiles are configured differently to Dolby defaults. You can see the changes in this Google Sheet. Edit: The Dynamic profile may have issues on non-ZTE devices as its settings are left at ZTE/Dolby's defaults, including 'Mi Steering'. Use Music profile for intended/optimum effect.

--

Also presenting...

ViPER4Android 2.5.0.5 Black 'n Cheese Edition - Unity 20180902

Changes:

Releasing this almost 4 weeks late, testing has been touch-and-go. Edit: I now operate on a ZTE Axon 7 (A2017U) on ZTE US stock 2.10B12 Oreo FW/ROM with its stock Dolby Atmos for Oreo, Magisk 16.7 (beta), and the ViPER module exactly as it appears here, so these releases are tested/working in that environment first. I do not utilize any other audio mods or AML with this environment, and ViPER is not (presently) functional for me in this environment, so I myself am not a reliable tester for full functionality of the Dolby Atmos for Oreo OR ViPER4Android modules OR their combination with AML at this time. This release is for Magisk 15.x/16.x and will not work properly with Magisk 17.x or with Android 9.0 Pie, nor is it intended to.

Updated base to Unity 1.7x FOR MAGISK 16. Numerous fixes from [MENTION=6037748]Zackptg5[/MENTION] including legacy volume button support. THIS RELEASE WILL NOT WORK WITH MAGISK 17.X OR ANDROID 9.0 PIE, PLEASE TRY 16.X/8.0 OREO BEFORE REPORTING ISSUES WITH THIS RELEASE.

If this zip does not appear as installable from Magisk Manager, flash via TWRP, install procedure is identical, just follow the prompts.

Custom "Black 'n Cheese Edition", "BlackRed" and "Inverted" themes for ViPER4Android apk, inspired by @djdarkknight96's Sprite Substratum Theme.

All updated to ViPER4Android Materialized Reformatted base, thanks [MENTION=4539728]pittvandewitt[/MENTION] and [MENTION=7052175]Mr_White_214[/MENTION] for the excellent work. Reformatted is technically still in beta so there may be visual bugs (though I haven't encountered any).

--

If you intend to use these both together or with any other audio mods/modules such as [MENTION=6037748]Zackptg5[/MENTION]'s Notification Helper Remover (recommended, available in the Magisk Manager app's Downloads section), you will need to install Audio Modification Library (AML), also available in the Magisk Manager app's Downloads section, after installing all audio mods you intend to install. My (edit: former) preference and install order (was):

ViPER -> Dolby -> (NHR, other) -> AML -> watch AML install output carefully to make sure it detects/patches your chosen audio mods. The order they appear in the output is insignificant, it only matters whether they all appear or not.