[Nexus 6 Themes and Apps] guitardedhero:
Apollo with ViPER? If you mean Atmos, it's functioning properly as always. This is automatic for me so I never think about it with Atmos FC reports but this is directed at all who use ViPER|Atmos™ package editions:

How To Use ViPER|Atmos™

If Dolby Atmos™ is installed with ViPER4Android it is imperative that ViPER4Android is functional for Dolby Atmos™ to even open up without a FC. Once ViPER4Android is confirmed working, that is when you want to open Dolby Atmos™ to confirm it's functioning.​

I'll add that to the OP when I catch up on the more important users' reports.

I've written the install script to handle various dirty flashes properly so please do and report the status. It's always possible a dirty rom flash is required to get a proper ViPER|Audio™ installation.

Sorry for not specifying as I was in a rush this morning and wanted to make these available before the work day, I'll explain later.

Beats™ Editions use the files shared by [MENTION=5627933]androidexpert35[/MENTION] found on his original thread here: http://xdaforums.com/android/software/mod-htc-beats-audio-beats-xperience-t3281603

These are system files and processes with no apps or gui's. On ViPER|Atmos™ Editions I wouldn't recommend adding any DSP with a GUI anyway as there are two already with ViPER4Android and Dolby Atmos™.

Adding these Beats™ files has made ViPER|Atmos™ Beats™ Edition my favorite package yet. I'm sure it's awesome without Dolby Atmos™, possibly even better, but I have to stick with ViPER|Atmos™ for testing purposes.

Yes, flash in TWRP. If you have 5x/6p you may need to mount Vendor in TWRP before flashing ViPER|Audio™

Last night with my initial testing of ViPER|Atmos™ Beats™ Edition was when I realized something was wrong with my 3.0 base. What I noticed was no ViPER4Android in App Drawer but was in /system/priv-app. No patching was done to the audio_effects.conf's and audio_policy.conf. I got the patching part sorted but still could not get ViPER4Android installed. What finally worked was manually deleting the folder in /system/priv-app, rebooting, copying folder back into /system/priv-app, set permissions for apk and its folder, and reboot. No problem since. I was blindsided by this unexpected occurrence so I immediately yanked the first Beats™ Edition attachments from my post last night. If you are faced in a similar situation, please delete the v4a folder, reboot, copy v4a folder, set permissions, reboot.

The persistent install driver prompt when using ViPER|Audio™ packages will always be an audio_effects.conf override. If an overriding audio_effects.conf is not patched by the install then it needs to be hunted down and deleted. I attempt to delete /vendor/etc/audio_effects.conf with my install script but you may have to mount Vendor in TWRP before flashing ViPER|Audio™ packages.

Have you tried deleting the file? I will always recommend Root Explorer as it's never plagued with the random quirks reported about other file managers.

Also, have you tried mounting Vendor in TWRP before flashing? The install script is supposed to delete /vendor/audio_effects.conf but delete the file if it remains after flashing.