ViPER|Audio™ || ViPER|Atmos™

ViPER|DD+™

Stock | Sony™ | Beats™



Universal



for 5.x.x - 6.x.x.

Est. 12/09/2015

Tested first on Nexus 6





Got a Nexus 6 and want to try the very first official rom with ViPER|Atmos™ fully injected with no root whatsoever?

Become part of ViPER4Android history and flash the rom at the link below:

http://forum.xda-developers.com/nexu...ed-n6-t3318315



Not on Lollipop or Marshmallow?

Here is the link to my AndroidFileHost JB & KK folder:

https://www.androidfilehost.com/?w=files&flid=48267 Become part of ViPER4Android history and flash the rom at the link below:Here is the link to my AndroidFileHost JB & KK folder:

Official ViPER Packages

These three versions provide the ultimate compatibility across all devices in your quest for the ultimate experience in seamless sound enhancement.



!! Versions not described above are just for fun !!



!! Make sure /system has 50mb+ of available free space !!



!! If it is necessary for you to run Cyanogenmod 13 with its own SuperUser you must change Selinux from Enforcing Strict to Permissive as SuperSU is required for processing in Enforcing !!

!! Be sure to enable Storage Permissions for ViPER4Android through its App Info page !!

If you experience problems with the normal installation instructions, the awesome @dr.ketan has allowed me to link his Viper Fix 1.1.apk which will essentially disable all other effects from your system by eliminating their libraries from your audio_effects.conf using v4a instead. Flash this apk as a normal user app, open, reboot when prompted, boot to recovery and flash your desired ViPER package. You can find info and support as well as the apk at this link: http://forum.xda-developers.com/show...postcount=3079

and

http://forum.xda-developers.com/show...&postcount=658



It is possible your /system is dirty enough to require at least a System wipe in TWRP and a dirty flash of your current rom before flashing ViPER|Atmos™ if you experience any Force Closes or any other signs of an incomplete/failed installation.



!! Do NOT delete /system/priv-app/MusicFX !!

In initial testing I found that I had to move MusicFX back to get ViPER working and I haven't removed it since. I do disable it and recommend doing the same if it's not working "out of the box".



!! Audiophile™ Profile zip is NOT flashable !!

Extract both folders in zip into the following two directories:



Code: /data/media/legacy/ViPER4Android



Code: /storage/emulated/0/ViPER4Android It is possible your /system is dirty enough to require at least a System wipe in TWRP and a dirty flash of your current rom before flashing ViPER|Atmos™ if you experience any Force Closes or any other signs of an incomplete/failed installation.In initial testing I found that I had to move MusicFX back to get ViPER working and I haven't removed it since. I do disable it and recommend doing the same if it's not working "out of the box".Extract both folders in zip into the following two directories:and

Audiophile™ ViPER|Audio™ Active Settings

Experience ViPER|Atmos™ & ViPER|DD+™

ViPER4Android & Dolby Atmos™ - Enforcing and Permissive Selinux

ViPER4Android & Dolby Digital Plus™ - Permissive Selinux





When combined with ViPER running my Audiophile™ profile, optimal results can be achieved using the following settings in Dolby Atmos™ or Dolby Digital Plus™:





ViPER|Audio™ || ViPER|Atmos™ || ViPER|DD+™

Sony™ Beats™ Editions



The Xperia™ Z5 Premium Marshmallow audio system as well as the M7 Beats™ files shared by @



Short List of Reference Songs Used for All Sound Profiling



Best processing when used with 16 bit 44.1 kHz FLAC sources. Sound quality degrades deviating up or down from this format. Trust me, I have DSD that play at 30mbps and more. The resulting sound is absolutely massive!The Xperia™ Z5 Premium Marshmallow audio system as well as the M7 Beats™ files shared by @ androidexpert35 found here: http://forum.xda-developers.com/andr...ience-t3281603 , compliment ViPER|Audio™, ViPER|Atmos™, and ViPERDD+™ amazingly well. I was surprised how it fit in so seamlessly, adding a very welcomed and natural bass boost while retaining the Audiophile™ clarity. My favorite combination, by far.Best processing when used with 16 bit 44.1 kHz FLAC sources. Sound quality degrades deviating up or down from this format. Trust me, I have DSD that play at 30mbps and more.

Testing Environment

Some of your IRS files not active when loaded?

A discovery I made a long time ago that is still largely unknown:



For this to work ViPER4Android™ MUST be uninstalled from /data if applicable.

In a situation where you could really use all the settings available to other outputs while processing through Speaker tab in ViPER4Android™?

Audio Focus causing processing issues?

Quote: Originally Posted by derekr44 Originally Posted by The audio_policy.conf edits worked. One thing to note (I found out through trial and error) is that the freqs need to be listed in numerical order on those line items (not just added to the end). For example:



Code: sampling rates 8000|16000|44100|48000



Code: sampling rates 8000|16000|48000|44100 is not seen the same as

Snapping or popping sounds? Upgrade your kernel's minimum frequency to 422mhz or higher (Nexus 6, device may vary) or switch to ondemand-based governor. See @wrongway213's post here for more info!

http://forum.xda-developers.com/show...postcount=6223



Experiencing audio disturbances while using a custom kernel? Our friend, @Woody explains:

Quote: Originally Posted by Woody Originally Posted by Back in the day, when Viper4Android started, it only worked on JellyBean 4.1 ROMs. This was when it was new and the iterations were just as fast as they are in this thread. Everything was finally figured out once Viper got to version 2.3.3.0 and then finally 2.3.4.0. Just about the same time that the final version of Viper was completed, KitKat came around with it's new experimental run time called ART. At that time, you could choose between either ART or the traditional Dalvik runtimes. But that choice came with a word of caution-"ART might not work with certain apks." At the same time, the Linux kernel was updated.



So now you have a SoundMOD that was reasonably perfected (and unfortunately abandoned as there has been no update since), a new Android OS and an updated Linux kernel that all needed to work together. Not saying that v4a was instrumental in a change of general ideology, but with so many people using it, many preferred sounds quality over battery quality. Let's not get all high and mighty on the Viper Is King train, as it was not the first to do what it does. If you've been around Android since Froyo/GB times, but more specifically the Galaxy S1/2 series, you should remember Supercurio's VoodDoo Sound Control. For the time, it blew anything away that was available and had a GUI apk that you could tweak. That was then, this is now; but really still talking in the KK days.



Since the sound mod was the greatest thing to headphones since aluminum, people wanted it to work on their custom ROMs/Kernels. In comes faux123 and his tweaks to his kernels that allowed for ramdisk injections of audio patches (generally AnyPatch kernels are what you will mostly find as it uses the "stock" ramdisk as a foundation). So if you ran a kernel during the middle 2013 to 2014, most had the Faux sound patch, as it allowed for peak sound for the device through the use of a custom kernel (this is why most kernels now days have a sound section in their .conf files or GUI). It lasted forever and is still being incorporated in custom kernels to this day (check your Kernel Thread OPs/GITs ). Since kernel devs are few and far between, they tend to either work closely together, cherry pick commits or try depart themselves from each other.



Android moves to Lollipop and ART is no longer optional, like in the previous KitKat. LP also introduced 2 kernel toolchain updates over it's lifetime. This caused kernel devs to tweak their setups and Governors. There were still the usual suspects like Interactive, On-Demand, Performance and Conservative, as well as all their derivatives. At this point sound mods were still working mainly because of the Faux sound and/or Franco patches were being included in most kernels and being built from AnyPatch kept that possible. Viper4Android worked as advertised, even after the /system folder structure had also changed).



Now comes MarshMallow. Again with another folder structure change and the adaptation of custom recoveries to be able to properly wipe them. Ever wonder why you can't find your Profile and Kernel folders when you dirty flash? I figured it out shortly after MM came out. The thing was, with the new OS, something in the kernel changed and now my trusted Interactive governor was creating popping and cracking sounds. I actually posted (should read the few posts after mine as well. They talk about Faux's sound too and my realization that On-Demand removes the popping and cracking) in this thread about it when it was under previous management by kah-el. Here are my final findings regarding using On-Demand over Interactive.



So what does this all mean? It means that if you have popping and cracking, you should switch your kernel governor to On-Demand or one of it's derivatives. Some other culprits can be if you are running a Permissive or Enforcing kernel and/or ROM. If you don't know if you are or not, open a terminal and type (without the quotes) "su" [ENTER] "setenforce" [ENTER] and see which number it puts out. 0=Permissive; 1=Enforcing. You can change this without the SELinuxpolicy changer apk by using the commands above. Some kernels, such as ElemetalX, have a radio button that you can tick at installation to have it as Enforcing or Permissive. Even though the latest zips from OP are getting more directed to being able to be used with Enforcing, it would be good for you to know what yours is. I run Permissive and will for the foreseeable future (Google it to find out why). You also need to check your gain strength and if it is set too high. Louder doesn't mean cleaner.



On-Demand isn't for everyone, but we have to find out why the Interactive governor ramps up the frequencies too fast and the audio portion of the kernel effects the output of Viper. This is something that a new kernel dev upstart could really make his mark in the Android custom kernel/sound mod world. *Hint*Hint* Until then, I don't mind On-Demand and SIO (I used to use Deadline but started to get RRs, though those were probably self-inflicted).

If using auxiliary port on Nexus 6, make this a routine:

(Since ViPER|Atmos™ testing this has not been necessary so far...)

Feel free to share this wherever with whomever, no credit or permission needed as this is still the work of the developers below. If you feel obligated to give credit when sharing please include those below.

Enjoy the zips attached below and provide any feedback you have.



4.3 is now using the Super Quality Driver to correct an oversight from I don't even know when. The Power Saving Driver file size is the exact same as the Super Quality Driver so somewhere along the way, it got mixed up and placed in the ViPER packages. The MD5 for the Super Quality Driver ends in "27a5" if you want to check libv4a_fx_ics.so on your device in /system/lib/soundfx.



Edit∆∆********

4.3.1 modifies the install script to accommodate every scenario of switching from different ViPER packages. No wipes necessary and no need to update unless you are wanting to try a different package. 4.3.1 also introduces the ViPER|DD+™ Stock version with no additional Beats™ and Huawei™ files.



Edit∆∆*********

4.4 introduces the phasing out of Huawei™ as part of the official packages as I was never fully convinced of any contribution, but highly suspect its inclusion caused many issues. All 4.4 packages include complete removal of Huawei™ files in the install script so no wipes are ever necessary. I don't plan on adding any Beats™ removal lines into the script as I fear that might delete stock files on HTC devices and that will certainly cause issues and be a very irresponsible act on my part. Essentially, this means a desire to try a Stock package will require a System wipe followed by a dirty flash of your rom before flashing a Stock package, otherwise, you'll still end up with the Beats™ files.



Edit∆∆∆

4.5.1 introduces the Xperia™ Z5 libraries and effects from @



Edit∆∆∆*

4.5.2 makes minor changes to the Supolicy script to make it compatible for all SuperSU users in an Enforcing Selinux environment (Thanks @



Edit∆∆∆**

5.0 includes the latest ViPER4Android 2.4.0.1 and its driver as well as a minor tweak to the Supolicy script



Edit∆∆∆***

5.1 brings Material Dark back to ViPER|Audio™ courtesy of @



Edit∆∆∆****

5.2 returns the official ViPER4Android apk into all ViPER packages. This makes for a better flashing experience and the Material apk's can always be easily copied over the existing official apk if desired. 5.2 also includes /system/etc/sony_effect to all Sony™ Beats™ editions. Lastly, all 5.2 packages include a Version Info text file in /system and include more removal lines in the installation script for third party v4a installs including those included in some roms.



Edit∆∆∆*****

5.2.1 removes the /system/etc/sony_effect folder introduced in 5.2. A system wipe will be required to remove this folder as deleting through my installer might delete stock files on some Sony™ devices. Alternatively, this file can be manually deleted to avoid a system wipe if desired. 5.2.1 also removes the data removal of ViPER4Android during installation.



Edit∆∆∆******

5.3 adds the following lines to /system/build.prop:

[QUOTE]audio.deep_buffer.media=false

lpa.decode=false

tunnel.decode=false

tunnel.audiovideo.decode=false

lpa.releaselock=false

lpa.use-stagefright=false

persist.sys.media.use-awesome=1



Edit∆∆∆*******

4.6 continues work using the previous ViPER4Android 2.3.4.0 after reports of the new ViPER4Android apk being a downgrade in sound quality. This is not an unreasonable assumption given that the new apk only provides one compatible driver with no reference to its purpose being more sound quality driven or more power saving driven. I am testing this now and would have to say this is definitely the recommended version rather than 5.3 which uses the new apk. 4.6 also includes the /system/build.prop lines from 5.3 which have proven to be very beneficial to Audio Focus and curing all problems experienced with the supolicy scipt on Enforcing Selinux. Honestly, everything seems absolutely perfect and I can't see anything improving this build other than sound enhancements that are later found.



Edit∆∆∆********

4.7.1/5.4 introduces Advanced Linux Sound Architecture into all packages. Dark Material returns with an available Light Material switcher flashable in recovery. Edit∆∆*******4.3 is now using the Super Quality Driver to correct an oversight from I don't even know when. The Power Saving Driver file size is the exact same as the Super Quality Driver so somewhere along the way, it got mixed up and placed in the ViPER packages. The MD5 for the Super Quality Driver ends in "27a5" if you want to check libv4a_fx_ics.so on your device in /system/lib/soundfx.Edit∆∆********4.3.1 modifies the install script to accommodate every scenario of switching from different ViPER packages. No wipes necessary and no need to update unless you are wanting to try a different package. 4.3.1 also introduces the ViPER|DD+™ Stock version with no additional Beats™ and Huawei™ files.Edit∆∆*********4.4 introduces the phasing out of Huawei™ as part of the official packages as I was never fully convinced of any contribution, but highly suspect its inclusion caused many issues. All 4.4 packages include complete removal of Huawei™ files in the install script so no wipes are ever necessary. I don't plan on adding any Beats™ removal lines into the script as I fear that might delete stock files on HTC devices and that will certainly cause issues and be a very irresponsible act on my part. Essentially, this means a desire to try a Stock package will require a System wipe followed by a dirty flash of your rom before flashing a Stock package, otherwise, you'll still end up with the Beats™ files.Edit∆∆∆4.5.1 introduces the Xperia™ Z5 libraries and effects from @ jancsessz 's Xperia™ Z5 port as well as a change in the supolicy script pointing to /su/bin/supolicy for the latest SuperSU systemless root for full ViPER4Android functionality with Enforcing Selinux. 4.5.1 also begins the phasing out of the Beats™ only editions to keep a manageable number of packages.Edit∆∆∆*4.5.2 makes minor changes to the Supolicy script to make it compatible for all SuperSU users in an Enforcing Selinux environment (Thanks @ Shadowghoster !). 4.5.2 also cleans the install script in all packages by removing the former Huawei™ removal lines which should no longer be necessary at this point. Users with a fully functional 4.5.1 installation should not feel compelled to update to 4.5.2, this is for everyone else or if you're flashing ViPER again because your rom update wiped your system in the installation process. Finally, Beats™ only editions will continue for those that have incompatibility issues with the other packages.Edit∆∆∆**5.0 includes the latest ViPER4Android 2.4.0.1 and its driver as well as a minor tweak to the Supolicy scriptEdit∆∆∆***5.1 brings Material Dark back to ViPER|Audio™ courtesy of @ Viper4713 's themed 2.4.0.1 apk. 5.1 also no longer removes ViPER4Android's /data/app installation or /data/data (app data) thanks to @ -decipher- 's thorough testing and reports.Edit∆∆∆****5.2 returns the official ViPER4Android apk into all ViPER packages. This makes for a better flashing experience and the Material apk's can always be easily copied over the existing official apk if desired. 5.2 also includes /system/etc/sony_effect to all Sony™ Beats™ editions. Lastly, all 5.2 packages include a Version Info text file in /system and include more removal lines in the installation script for third party v4a installs including those included in some roms.Edit∆∆∆*****5.2.1 removes the /system/etc/sony_effect folder introduced in 5.2. A system wipe will be required to remove this folder as deleting through my installer might delete stock files on some Sony™ devices. Alternatively, this file can be manually deleted to avoid a system wipe if desired. 5.2.1 also removes the data removal of ViPER4Android during installation.Edit∆∆∆******5.3 adds the following lines to /system/build.prop:[QUOTE]audio.deep_buffer.media=falselpa.decode=falsetunnel.decode=falsetunnel.audiovideo.decode=falselpa.releaselock=falselpa.use-stagefright=falsepersist.sys.media.use-awesome=1Edit∆∆∆*******4.6 continues work using the previous ViPER4Android 2.3.4.0 after reports of the new ViPER4Android apk being a downgrade in sound quality. This is not an unreasonable assumption given that the new apk only provides one compatible driver with no reference to its purpose being more sound quality driven or more power saving driven. I am testing this now and would have to say this is definitely the recommended version rather than 5.3 which uses the new apk. 4.6 also includes the /system/build.prop lines from 5.3 which have proven to be very beneficial to Audio Focus and curing all problems experienced with the supolicy scipt on Enforcing Selinux. Honestly, everything seems absolutely perfect and I can't see anything improving this build other than sound enhancements that are later found.Edit∆∆∆********4.7.1/5.4 introduces Advanced Linux Sound Architecture into all packages. Dark Material returns with an available Light Material switcher flashable in recovery.

XDA:DevDB Information

ViPER|Audio || ViPER|Atmos || ViPER|DD+

Contributors

Version Information

5.x uses ViPER4Android 2.4.0.1 with its driver preinstalled4.x uses ViPER4Android 2.3.4.0 with its Super Quality driver preinstalledDark Material themeWorks in Permissive and Enforcing SelinuxWorks with no root as long as a Permissive kernel is installedInstalled in /system/priv-appAdvanced Linux Sound ArchitectureSony™ and Beats™ libraries and effectsLibrary & Effect entries in /system/ect/audio_effects.conf, /system/vendor/etc/audio_effects.conf, /vendor/etc/audio_effects.conf, and /system/etc/htc_audio_effects.confFive custom audio_effects.conf files for the Sony™ Beats™ EditionsDeep Buffer removal from /system/etc/audio_policy.confBackup script to survive rom updatesis for those only wanting ViPER processing. There is also a Stock version that has no additional files or effects for those seeking a pure "vanilla" ViPER4Android installation.includes @ worstenbrood 's Dolby Atmos™ found here: http://forum.xda-developers.com/andr...atmos-t3109446 , fully functional in Enforcing. There is also a Stock version without the additional effects for a pure "vanilla" ViPER|Atmos™ experience.includes Dolby Digital Plus™ courtesy of @ aki_007 which can be found here: http://forum.xda-developers.com/andr...ersal-t3078802 and is the perfect solution for those experiencing issues with the Dolby Atmos™ app. Both are fantastic and extremely similar in sound and identical in setup. This is certainly not a downgraded ViPER|Atmos™ but just another available option for the user. Dolby Digital Plus™ requires a Permissive Selinux environment so packages including DD+™ also include a Permissive script during the installation to avoid any issues after the installation. There is also a stock version without the additional effects.Boot to recoveryWipe > Advanced > Dalvik Cache, CacheInstall > ViPER|Audio™ViPER|Atmos™ViPER|DD+™RebootOpen v4aMenu > Show Notification (block if desired by long pressing notification)Menu > UI Setting > ExpertMenu > Save Effect Profile > New Effect Profile > "Stock" (this will help you find your working v4a directory)Begin playing audio fileOpen v4aUncheck Enable v4aCheck Enable v4aThe best and easiest way to remove this and any other /system mod from your device is to dirty flash your rom after wiping System in TWRP. Before you begin, make sure you have a compatible rom zip on your internal storage as an OS will need to be installed. As long as you do not Factory Reset or check Data or Internal Storage, your data will be left intact but with a fresh /system partition.Verify compatible rom zip is on deviceBoot to recoveryWipe > Advanced > System, Dalvik Cache, CacheMount > uncheck SystemInstall > current/compatible rom zipRebootViPER4Android™ > EnabledExtremeBeats™ Perfection EQ Preset > 3.5, 4.5, 5.0, 3.5, 1.5, 1.0, 3.5, 4.5, 5.0, 3.5Convolver > EnabledImpulse Response > DFX Hip Hop Modern.irs or DFX Metal Rap Big Bass.irsCross Channel > 0%Dynamic System > EnabledListening Device > Common Earphone v2 (I use Sony™ MDR-XB90EX - http://www.amazon.com/gp/aw/d/B008G8...E4L&ref=plSrch Dynamic Bass > 14%ViPER Bass > EnabledBass Mode > NaturalBass Frequency > 40hzBass Boost > 10dbViPER Clarity > EnabledClarity Mode > NaturalClarity > 6dbMusic profileEQ Preset > Open (Flat to tame bass if needed)Surround Virtualizer > OffDialog Enhancer > OnVolume Leveler > Off or OnNero - Satisfy https://play.google.com/music/m/T3um...Satisfy_-_Nero Born of Osiris - Exhil∆r∆te https://play.google.com/music/m/Tbkw...Born_Of_Osiris Bar 9 - The Beginning https://play.google.com/music/m/Tcdn...VIP_Mix_-_Bar9 Stick Figure - Breathe https://play.google.com/music/m/Tf4j...-_Stick_Figure Tove Lo - This Time Around https://play.google.com/music/m/Tnwl...ound_-_Tove_Lo August Burns Red - Echoes https://play.google.com/music/m/Txbo...gust_Burns_Red August Burns Red - Black Sheep https://play.google.com/music/m/Ti4z...gust_Burns_Red Zomboy - Bad Intentions https://play.google.com/music/m/Tnoj...l_Mix_-_Zomboy Liquid Stranger - Nintendo https://play.google.com/music/m/Tt3n...iquid_Stranger All Shall Perish - There is No Business to be Done on a Dead Planet https://play.google.com/music/m/T5uq...l_Shall_Perish Crotchduster - Mammal Sauce https://play.google.com/music/m/T3sz...-_Crotchduster Headset> Sony™ MDR-XB90EX http://www.amazon.com/MDR-XB90EX-In-.../dp/B008G80FIU Bluetooth> Pioneer™ DEH80PRS http://www.amazon.com/gp/aw/d/B006Y4...amL&ref=plSrch > Focal™ Integration ISC 165 6.75" http://www.amazon.com/gp/aw/d/B0159B...RfL&ref=plSrch > Two unknown 6" subs in a ported box> Old Kicker™ 2 channel 250 watt amplifierThat completes my service van setup where most testing takes place.> Sony™ SRSX55 Portable Speaker http://www.amazon.com/gp/aw/d/B00TTW...JzL&ref=plSrch If ViPER4Android™ still shows in App Drawer after dirty flashing your rom (while you're checking for free /system space and BusyBox) then uninstall from App Drawer or delete /data/app/com.vipercn.viper4android_v2-1.After flashing ViPER|Atmos™ or ViPER|Audio™, setting everything up, and confirming everything is functioning, extract the ViPER zip.Tap on the apk in the extracted location to "install an update to this built-in application."Tap Open and dismiss the only instance of "ViPER4Android has stopped" that you will see.ViPER is now installed in /system and /data allowing you to enjoy every IRS in your collection.Swipe over to output tab with the settings you seek to use.Menu > Lock Effect ModeNow, this locked output tab will be the only settings used while processing audio. Remember to unlock effect mode if this is only for certain scenarios when done.I haven't had an opportunity to devote enough time testing audio_policy.conf edits but here's a couple that seem to help with no processing after audio interruptions:Open /system/etc/audio_policy.conf in text editorAdd 44100 to voice_rxAdd 48000 to a2dpSave changesRebootDo this only if you experience no processing after a notification or voice call when ViPER4Android™ was processing immediately before the audio focus.Turn off ViPER Headset profile by unchecking Enable ViPER in Headset tab.Slooowly insert auxiliary cord into phone port, if Google Voice Search opens that's even better, but not required.Play desired audio file with desired audio player.Open ViPER and turn ViPER Headset profile back on by checking Enable ViPER in Headset tab.Thanks to @ viper520 & @ zhuhang for the glorious ViPER4Android™.Thanks to @ worstenbrood for the Dolby Atmos™ dap_r6.5.zip and the necessary scripts inside which I was able to edit for this Installer.Thanks to @ aki_007 for Dolby Digital Plus™, providing more options for the user and allowing me to extend the compatibility range for devices that might have issues with Dolby Atmos™Thanks to @ BSDgeek_Jake for the highest quality IRS files on XDA - http://forum.xda-developers.com/show....php?t=2439254 Thanks to @ maximumentropy for the updated Enforcing script for systemless root.Thanks to @ androidexpert35 for the fantastic Beats™ files for the Beats™ editions.Thanks to @ tupac4u for providing the perfect rom base for the ViPER|Atmos™ Edition Nexus 6 rootless rom.Thanks to @ dr.ketan for allowing me to link to his Viper Fix apk, useful when the normal ViPER installation doesn't work for you.Thanks to @ Viper4713 for the Material v4a apk's.Thanks to @ Hitti2 for the OP imagery.Thanks to @ -decipher- for the ViPER|Audio™ banner.Thanks to you guys for always providing feedback and never settling for anything but the best!And my biggest thanks to these generous donators!:Many thanks guys!!Edit Archive:Edit∆∆∆*********4.8/5.5 are rebased on Xperia™ Z5 Premium Marshmallow's audio system.Using the entire Z5 Premium library with a custom audio_effects.conf incorporating only what is included in the mod.Five custom audio_effects.conf locations and correct naming schemes which provide the most compatibility yet.Sony Effect build.prop section.Updating only requires the deletion of existing ViPER|Audio™ and Sony Effect build.prop lines if present to prevent duplicate entries.Stable4.8/5.52016-03-152016-03-042016-03-15