FORUMS

 View Poll Results: Which six (choose six) packages best represent the ViPER vision and should remain?

ViPER|Audio™ Stock
 
163 Vote(s)
43.01%
ViPER|Audio™ Beats™ Edition
 
51 Vote(s)
13.46%
ViPER|Audio™ Sony™ Edition
 
38 Vote(s)
10.03%
ViPER|Audio™ Sony™ Beats™ Edition
 
101 Vote(s)
26.65%
ViPER|Atmos™ Stock
 
103 Vote(s)
27.18%
ViPER|Atmos™ Beats™ Edition
 
49 Vote(s)
12.93%
ViPER|Atmos™ Sony™ Edition
 
49 Vote(s)
12.93%
ViPER|Atmos™ Sony™ Beats™ Edition
 
173 Vote(s)
45.65%
ViPER|DD+™ Stock
 
66 Vote(s)
17.41%
ViPER|DD+™ Beats™ Edition
 
27 Vote(s)
7.12%
ViPER|DD+™ Sony™ Edition
 
20 Vote(s)
5.28%
ViPER|DD+™ Sony™ Beats™ Edition
 
95 Vote(s)
25.07%

* ViPER|Audio || ViPER|Atmos || ViPER|DD+ 4.8/5.5 * Driver * Stock * Sony * Beats *

7,942 posts
Thanks Meter: 24,303
 
By guitardedhero, Senior Member on 24th November 2014, 09:58 PM
Post Reply Email Thread
Announcement from guitardedhero: The best ViPER4Android installations available!
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

Features:
5.x uses ViPER4Android 2.4.0.1 with its driver preinstalled
4.x uses ViPER4Android 2.3.4.0 with its Super Quality driver preinstalled
Dark Material theme
Works in Permissive and Enforcing Selinux
Works with no root as long as a Permissive kernel is installed
Installed in /system/priv-app
Advanced Linux Sound Architecture
Sony™ and Beats™ libraries and effects (No apk's or settings to look for!)
Library & 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.conf
Five custom audio_effects.conf files for the Sony™ Beats™ Editions
Deep Buffer removal from /system/etc/audio_policy.conf
Backup script to survive rom updates

Official ViPER Packages

ViPER|Audio™ is 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.

ViPER|Atmos™ 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.

ViPER|DD+™ 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.

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 !!

Installation:
Boot to recovery
Wipe > Advanced > Dalvik Cache, Cache
Install > ViPER|Audio™ OR ViPER|Atmos™ OR ViPER|DD+™
Reboot

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

Open v4a
Menu > Show Notification (block if desired by long pressing notification)
Menu > UI Setting > Expert
Menu > Save Effect Profile > New Effect Profile > "Stock" (this will help you find your working v4a directory)

Begin playing audio file
Open v4a
Uncheck Enable v4a
Check Enable v4a

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
and

Code:
/storage/emulated/0/ViPER4Android

Uninstallation and Removal:
The 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 device
Boot to recovery
Wipe > Advanced > System, Dalvik Cache, Cache
Mount > uncheck System
Install > current/compatible rom zip
Reboot

Audiophile™ ViPER|Audio™ Active Settings

ViPER4Android™ > Enabled

ExtremeBeats™ Perfection EQ Preset > 3.5, 4.5, 5.0, 3.5, 1.5, 1.0, 3.5, 4.5, 5.0, 3.5 (Enabled when needed)

Convolver > Enabled
Impulse Response > DFX Hip Hop Modern.irs or DFX Metal Rap Big Bass.irs
Cross Channel > 0%

Dynamic System > Enabled (Headset only, when needed)
Listening 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 > Enabled
Bass Mode > Natural
Bass Frequency > 40hz
Bass Boost > 10db

ViPER Clarity > Enabled
Clarity Mode > Natural
Clarity > 6db

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™:

Music profile
EQ Preset > Open (Flat to tame bass if needed)
Surround Virtualizer > Off
Dialog Enhancer > On
Volume Leveler > Off or On

The resulting sound is absolutely massive!

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 @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.

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.

Nero - 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

Testing Environment
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 amplifier
That 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

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.

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.

In a situation where you could really use all the settings available to other outputs while processing through Speaker tab in ViPER4Android™?
Swipe over to output tab with the settings you seek to use.
Menu > Lock Effect Mode
Now, 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.

Audio Focus causing processing issues?
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 editor
Add 44100 to voice_rx
Add 48000 to a2dp
Save changes
Reboot

Do this only if you experience no processing after a notification or voice call when ViPER4Android™ was processing immediately before the audio focus.

Quote:
Originally Posted by derekr44

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
is not seen the same as

Code:
sampling rates 8000|16000|48000|44100

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

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...)
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.

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.

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!:
@joetheshmo X 2!
@Roi007leaf X 3!
@churapa
@dingermtb
@jesssiii
@ffejy462 X 2!
@Brock Guffman
@NullyOne
@luigidk
@derekr44
@elevatorguy
@heleos
@J.Guido85
@bkkzak
@Rhonin86
@Unclecharlo
@stueycaster
@deebray36 X 3!
@GODSPD
@williwood X 2!
@meckipower
@JellyTooth
@jshamoon
Mikko L. (guest)


Many thanks guys!!

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

Edit Archive:
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 script

Edit∆∆∆***
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=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.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.

XDA:DevDB Information
ViPER|Audio || ViPER|Atmos || ViPER|DD+


Contributors
guitardedhero

Version Information
Status: Stable
Current Stable Version: 4.8/5.5
Stable Release Date: 2016-03-15

Created 2016-03-04
Last Updated 2016-03-15

The Following 614 Users Say Thank You to guitardedhero For This Useful Post: [ View ] Gift guitardedhero Ad-Free
24th November 2014, 10:51 PM |#2  
guitardedhero's Avatar
OP Senior Member
Flag Little Rock
Thanks Meter: 24,303
 
Donate to Me
More
User Content Area

Quote:
Originally Posted by sonophilos

3/3/2016
Hey friends, Sonophilos here with an update:
You can update my Lover of Sound Profiles 5.2.1 to 4.7.1 as I have it set up with my suggested tweaks by changing the following:

Sonophilos-Speakers Profile: drop PlaybackAGC Max Output to -1.9Db (default) - was -1.0Db
Everything else is the same - smooth curve, +8.0Db Natural Bass, +8.0Db Natural Clarity, 0.0Db Output Gain

Sonophilos-Headphones Profile: drop PlaybackAGC Max Output to -1.9Db (default) - was -1.0Db
Drop Dynamic Bass to 16 Percent (was 20 Percent)
Everything else is the same - smooth curve, +8.0Db Natural Bass, +8.0Db Natural Clarity, -3.0Db Output Gain

With these settings at 8-9/15 volume "notches" (bearing in mind 10 is technically 100% on most devices, higher is pushing the limiter especially with audiofx like this) my speakers sound excellent and fill the room on the device speakers, my cheap desktop speakers or decent stereo alike;
in my Audio-Technica ATH-M50 s 8 volume is quite loud and isolating, 9 overcomes the sound of a dryer running next to me easily and 10 (highest before the Safe Headset Volume dialog comes up, I'm sure for good reason) it is absolutely deafening massive and crystal clear even at the peaks.

Update: the track I was testing the difference with. Massive and full-range sound. On A Brighter Note
I'm totally satisfied, @guitardedhero - thanks for your hard work!

Lover of Sound Profiles 4.7.1.zip is attached below.

2/29/2016
So after a couple sleepless nights of listening for every nuance of each build.prop from the XTREMEMusic project (some of which have already been suggested by other users and myself) I offer my refined tweaks and some reflections here:

Code:
# Make sure below enabled / added if not present
dev.pm.dyn_samplingrate=1
tunnel.audio.encode=false
audio.offload.gapless.enabled=true
audio.offload.buffer.size.kb=256
audio.offload.video=true
audio.offload.pcm.16bit.enable=true
audio.offload.track.enabled=true
audio.offload.passthrough=false
audio.offload.multiple.enabled=false
audio.offload.pcm.24bit.enable=true
# This is a multiplier - 4 = 4x48000Hz = 192KHz
# M9 has this by default, v4.7 adds this to ViPER section. 
# Use only one - I comment out duplicate default props so these take priority
af.resampler.quality=4
# These are default on M9 - add if not present
htc.audio.global.state=0
htc.audio.global.profile=0
htc.audio.q6.topology=0
htc.audio.global.speaker=1
#
## ViPERAudio ##
#
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
# This is a multiplier - 4x48000Hz = 192KHz rate
persist.af.resampler.quality=4
# Separate from default resampling, use both
persist.dev.pm.dyn_samplingrate=1
# ALSA props for ViPERAudio 4.7
ro.sound.alsa=snd_pcm
AUDIODRIVER=alsa
ro.sound.driver=alsa
clock.allow_streaming_errors=false
# Changed this to "best" as XM project had it
default.pcm.rate_converter=samplerate_best

#
# XTREMEMusic Experimental Props #
#
audio.offload.track.enabled=true
# 16bit offload and track are required for DSEE
audio.offload.pcm.32bit.enable=true
# 32 and 64bit might have no effect but no issues
audio.offload.pcm.64bit.enable=true
# ALSA Mixer (Experimental - no issues yet)
alsa.mixer.playback.master=Speaker
alsa.mixer.capture.master=Mic
alsa.mixer.playback.earpiece=Earpiece
alsa.mixer.capture.earpiece=Mic
alsa.mixer.playback.headset=Headset
alsa.mixer.capture.headset=Mic
alsa.mixer.playback.speaker=Speaker
alsa.mixer.capture.speaker=Mic
alsa.mixer.playback.bt.sco=BTHeadset
alsa.mixer.capture.bt.sco=BTHeadset

# HTC/Beats/Boomsound/Dolby associated props
ro.config.hw_dolby=true
ro.config.hw_dts=true
htc.audio.swalt.enable=1
# Can go as high as 14512 - this is a smooth value
htc.audio.swalt.mingain=1920
persist.htc.audio.pcm.samplerate=192000
persist.htc.audio.pcm.channels=2
persist.audio.vr.enable=false
htc.audio.lpa.a2dp=0
htc.audio.alc.enable=1
persist.audio.SupportHTCHWAEC=1
# These may have no effect but create no issues
support_harman=true
support_boomsound_effect=true

# Sony Edition associated props
# This seems totally necessary for some of Sony's effects - adding it was an audible change
mpq.audio.decode=true
sony.support.effect=0x1FF
ro.semc.sound_effects_enabled=true
ro.semc.xloud.supported=true
persist.service.xloud.enable=1
com.sonyericsson.xloud_enabled=true
ro.semc.enhance.supported=true
persist.service.enhance.enable=1
ro.semc.clearaudio.supported=true
persist.service.clearaudio.enable=1
ro.somc.clearphase.supported=true
persist.service.clearphase.enable=1
com.sonymobile.clearphase_enabled=true
ro.somc.cp.default_setting=true
ro.somc.xloud.default_setting=true
ro.somc.sforce.supported=true
persist.service.sforce.enable=1
com.sonymobile.sforce_enabled=true
ro.somc.sfs.default_setting=true
ro.somc.dseehx.supported=true 
ro.semc.dseehx.enable=1
persist.service.dseehx.enable=1
# Confirmed "semc"/"somc" are as on Xperia Z5P

# S Audio mod suggested props (from Xperia Z5P)
# SONY effect
#  Allocate bit for each effect.
#  If necessary, define effect list with logical sum.
#  EFFECT_DN        0x0001 (Dynamic Normalizer)
#  EFFECT_SF        0x0002 (S-Force)
#  EFFECT_CPHP      0x0004 (ClearPhase Headphone)
#  EFFECT_CA        0x0008 (ClearAudio)
#  EFFECT_VPT       0x0010 (VPT)
#  EFFECT_CPSP      0x0020 (ClearPhase Speaker)
#  EFFECT_XLOUD     0x0040 (xLOUD)
#  EFFECT_CAPLUS    0x0080 (ClearAudio+)
#  EFFECT_SPBUNDLE  0x0100 (Speaker Bundle)
#  EFFECT_ALC       0x0200 (ALC)

# Effect used by Speaker Bundle.
# EFFECT_SF | EFFECT_CPSP | EFFECT_SPBUNDLE = 0x122
sony.effect.custom.sp_bundle=0x122

# Effect used by ClearAudio+ headset
# EFFECT_CA | EFFECT_VPT | EFFECT_CAPLUS | EFFECT_ALC = 0x298
sony.effect.custom.caplus_hs=0x298

# Effect used by ClearAudio+ speaker
# EFFECT_CA | EFFECT_VPT | EFFECT_CPSP | EFFECT_CAPLUS | EFFECT_ALC = 0x2B8
sony.effect.custom.caplus_sp=0x2B8

# Noise reduction tweaks (Beta phase - seems working)
# These reduce in call noise by using dual mics
# Remove these if unsure if you have dual mics
htc.audio.enable_dmic=1
persist.audio.handset.mic=digital
# Legacy tweaks - these reduce noise noticeably
htc.audio.alt.enable=0
htc.audio.hac.enable=0
Do with this knowledge what you will. I offer no insight or support beyond that this setup is working flawlessly on my HTC One M9 with the ViPERAudio 4.6 Dark Sony Beats Edition (Permissive) I posted recently and the Lover of Sound Profiles I shared.

---------- Post added at 01:41 AM ---------- Previous post was at 01:35 AM ----------


Hey @guitardedhero just noticed this post after I made mine about the XM revival. As soon as you have a ViPERAudio Sony Beats 4.7 up I'll upload my Dark Permissive version and update that post to reflect the correct and working ALSA props.

--EDIT: I have revised and updated the build.prop section for v4.7 - users may want to copy the entire section starting with ViPERAudio and carefully paste over that section in build.prop. I also strongly recommend combing through default build.prop settings to make sure there are no conflicts or duplicates - this was totally necessary for me to achieve the glorious setup I have running as I type this.
I've also updated this post's attachments with ViPER|Audio™ 4.7 Dark Sony Beats Edition (Permissive) for users with Permissive Selinux only.

ViPERAudio_4.7_Dark_Sony_Beats_Edition_Permissive. zip is attached below

.

Quote:
Originally Posted by sonophilos

Hey @guitardedhero - here's my setup working with my Lover of Sound Profiles as of 2/8/16:

ViPERAudio 5.2.1 - Dark Sony Beats Edition (Permissive)

Once again, the only changes from ViPERAudio Sony Beats 5.2.1 are the replacement of the stock V4A APK with the Material Dark version, and the removal of the su.d folder and its entry from the updater script, for use with devices with an outside solution for Permissive Selinux, such as an init.d script or the Selinux Mode Changer app.

To clarify: If you have Enforcing Selinux this will not operate properly. If you already have Permissive Selinux set up on your device, or if your device has problems with supolicy scripts (as mine does), this should work excellently for you.

I've removed Atmos (rebased on just ViPERAudio) in this version as it was introducing severe popping, skipping and even slowdown to my sound even with every solution I've suggested so far implemented, which may be an issue unique to my device but it's not one I'm willing to tolerate. Atmos only really adds some volume and clarity to midrange and vocals, experientially, for me anyway, and the latest Lover of Sound Profiles easily compensate. I was also tired of having to mess with Memory Locker to keep Atmos from dying every time I started literally any other app besides it, Spotify and V4A.

--

Sonophilos (Lover of Sound) Profiles

Lock Effect Mode - Headset (so Speakers/Bluetooth get all ViPER options) - You will use separate profiles for Headphones and Speakers rather than the separate tabs. The Lover of Sound profiles include both preset as described below.
UI Setting - Expert (so you can see all these settings)

Sonophilos-Headphones:
PlaybackAGC - Enabled, Moderate / 4x Max Gain / -1.0Db Max Output
ViPER-DDC - Enabled, audio-technica ATH-M50 (set this to your headset after first install, then save over Headphones profile)
Spectrum Expansion - 0.5
FiREqualizer - (0.0, -0.6, -1.2, -1.8, -2.4, -3.0, -2.1, -1.3, -0.6, 0.0)
Convolver disabled, it's a major battery drain
Field Surround disabled, it's only really helpful on larger speakers
Differential Surround disabled, it's only really helpful on speakers spaced widely apart
Headphone Surround + Enabled, Level 1
Reverb disabled
Dynamic System enabled / High-End Headphone (v2) / 20%
^You may want to set this to Common Headphone (v2) or if you have one of the specific models listed use that preset
ViPER Bass - Enabled / Natural / 40Hz / 8.0Db
ViPER Clarity - Enabled / Natural / 8.0Db
Cure Tech+ Enabled, Moderate
AnalogX - Enabled, Moderate
Output Gain (-3.0Db) / Channel Pan 0.5:0.5 / Limit Threshold 0Db

Sonophilos-Speakers:
PlaybackAGC - Enabled, Moderate / 4x Max Gain / -1.0Db Max Output
ViPER-DDC - disabled
Spectrum Expansion - 0.5
FiREqualizer - (0.0, -0.6, -1.2, -1.8, -2.4, -3.0, -2.1, -1.3, -0.6, 0.0)
Convolver disabled, it's a major battery drain
Field Surround disabled, it's only really helpful on larger speakers
Differential Surround disabled, it's only really helpful on speakers spaced widely apart
Headphone Surround + disabled
Reverb disabled
Dynamic System disabled
ViPER Bass - Enabled / Natural / 40Hz / 10.0Db
ViPER Clarity - Enabled / Natural / 8.0Db
Cure Tech+ disabled
AnalogX - Enabled, Moderate
Output Gain 0Db / Channel Pan 0.5:0.5 / Limit Threshold 0Db

--

I recommend adding the following section to build.prop:

Code:
#
# ViPER4Android
#
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
ro.audio.samplerate=48000
ro.audio.pcm.samplerate=48000
You can set the bottom two higher - check in your audio_policy.conf under compress_offload to see how high the dynamic sampler will go. My HTC One M9's goes to 192000 and so I have those bottom two samplerate settings set to that.

I also recommend adding the two values to audio_policy.conf as described in the OP, and the use of Don't Pause! so notifications go to vibrate when music is playing instead of "ducking" or pausing the music stream.

The combination of this mod and profiles and tweaks is an absolutely gorgeous sound out of the internal speakers, realizing the potential of the device much better and adding some substantial volume, and the headphone experience is practically theatrical. The sound and its processing also defies being interrupted, making for an immersive headphone experience or lengthy playlist jam.

--Cheers all, from Sonophilos the lover of Sound.

ViPERAudio 5.2.1 Dark Sony Beats Edition Permissive.zip and Lover of Sound Profile 5.2.1.zip attached below

Quote:
Originally Posted by -decipher-

Hey, I'm using latest Viper|Atmos sony beats 4.5.1 and it's SUPERB. Maybe it's me, but I've noticed sound is noticeably cleaner compared to 4.4 beats only. I was thinking of contributing to the thread as a way of showing my appreciation so I'm sharing my settings here if anyone is interested, I use not so high quality earphones (30$ more or less) so these settings are oriented mainly to similar budget earphones.

Viper settings:
Headset:
Playback Gain Control: On (if you are using Poweramp, first switch off it's built in AGC)
Effect strength: moderate
Max Gain: 4x
Max output: -1.9 DB (for smoother output)
Viper DDC: Off
Spectrum Extension: On
Strength: 0.5 (switch off if you face bass distortion)
FIREquializer: Off
Convolver: On
Impulse Response: Tracks Regular 1.irs from here
Cross Channel: 0
Field Surround: Off
Differential Surround: Off
Headphone Surround+: Off
Reverberation: Off
Dynamic System: On
Select Listening Device: Common Earphone v2
Select Dynamic Bass: 3 percent
Fidelity Control
Viper Bass: On
Bass Mode: Natural
Bass frequency: 50Hz
Bass Boost: 10dB
Viper Clarity: Off
Auditory System Protection
Cure Tech: On
Binaural Level: Slight
Master Gate: Defaults (0)

For Dolby Atmos:
Music Mode
Intelligent Equalizer: Rich (middle preset)
Surround Virtualizer: On
Dialogue Enhancer: On

All surround processing will be done by Dolby Atmos Alone, without interference from Viper. Also All setting That I didn't mention were left with default value. Keep In mind that some IRS may or may not work if Viper is installed as system app, to solve this issue I thank @guitardedhero for explaining this, You must extract Viper4Android APK from the zip file and install it manually, this will make Viper a system AND user app, so full convolver functionality is restored.

Quote:
Originally Posted by tcat007

Here's mine. Atmos setting "open" (left), surround on. V4a profile attached, irs: BBE Generic2.

Tcat007.zip is attached below.

Quote:
Originally Posted by -decipher-

Viper4Android Look:
CM13 theme engine theme: DEEPDARKNESS//. Screen below.

Quote:
Originally Posted by rolarocka

Here are my settings with the Atmos Sony Beats Edition, they are perfect for me who hears mostly electronic music with in ears monitors.

Viper Ui setting is at moderate, headset tab
Spectrum extension at 0,1
Convolver with WavesMusic.IRS
Reverberation *sometimes* on with 25m2, 8m, 50%, 10%, 60%
Viper Bass on at 40Hz, 6dB
Viper Clarity on at 3,5dB
Anything else off.

Dolby Atmos is full on bass and highs, a bit of mids, music preset and manual equalizer, surround virtualizer, dialog enhancer and volume leveler are off.

Just try it , bass is punchy and the highs are crystal clear, mids are there too

A0001 - oneplus one

Quote:
Originally Posted by ranaxda200

I'm attaching my all favorites convolvers. Hope it'll be useful for those who need it.

convolver.zip attached below.

Quote:
Originally Posted by Jimbus369

Hi guys, I want share my experience with Viper4Android. I'm not an expert, but I like play with audio settings.

My configuration:
I9505 Jfltexx CM13 crDroid
ViPERAtmos 4.5.1 Sony Beats Edition
Sony Music 9.1.4.A.2.1 - 1.4 (Amazing!)

Headset:
Standard S4 audio Headset.

Bluetooth:
Philips PIX3L

Amplifier:
JBL ESC200

Low end things, I know...

Albums used for my test:
Eagles - Hotel California MFSL 1-126 Flac 2830 Kbps
Dire Straits - Money For Nothing MP3 128 Kbps
Ac/Dc - Dirty Deeds Done Dirt Cheap MP3 320 Kbps
Guns N' Roses - Appetite For Destruction MP3 320 Kbps
Paramore - RIOT! [Limited Edition] MP3 320 Kbps

Tell me how I can do better and where I have done something wrong. I want study something more about Differential surround, but I like it!

Dolby Atmos settings:
Intelligent Equalizer: Rich
Surround Virtualizer: On
Dialogue Enhancer: On
Volume Leveler: Off

Viper4Android profile is attached below.

I'm sorry for my english!

V4A_(Extreme_Profile_by_Jimbus369).rar attached below.

Quote:
Originally Posted by derekr44

Ok, I'll try my hand at sharing settings. I mostly listen to Trance and Progressive, heavy electronic sounds and lots of subtle details with harmonic chords. So I'm not positive how this will sound with other genres of music... It's not perfect by any means, but it's getting there. Plus I'm partially deaf in my left ear, so... :P

Zip: Viper|DD+ 4.5.2
Listening Device: VOXOA HD Wireless

Viper Settings
Spectrum Extension - Enabled
Strength - 0.6
Convolver - Enabled
IRS - BBE Wide Stereo.irs
Viper Bass - Enabled
Bass Mode - Natural
Bass Freq - 40Hz
Bass Boost - 6.0db
Viper Clarity - Enabled
Clarity Mode - XHiFi
Clarity - 3.5db

Dolby Settings
Dialogue Enhancer - On
Intelligent EQ - Rich, Bass+2, Treble+2

Quote:
Originally Posted by tcat007

If anyone wants a Red/Gold layer for v4a I have attached what I use.



Tcat-v4a.apk attached below.

Quote:
Originally Posted by dead0

@guitardedhero

For anyone interested, you can add the following lines to your build.prop. It may just be a placebo effect on my part but I have noticed a small difference with these added in. This has only been tested on the oneplus one with darkobas rom/lightning kernel however should work for others.

htc.audio.swalt.enable=1
htc.audio.swalt.mingain=2072
af.resampler.quality=255
persist.af.resampler.quality=255
persist.htc.audio.pcm.samplerate=48000
persist.htc.audio.pcm.channels=2
persist.audio.vr.enable=false
htc.audio.alc.enable=1
htc.audio.global.state=0
htc.audio.q6.topology=0
htc.audio.global.speaker=1
persist.audio.SupportHTCHWAEC=1

sony.support.effect=0x1FF
ro.semc.sound_effects_enabled=true
ro.semc.xloud.supported=true
persist.service.xloud.enable=1
ro.semc.enhance.supported=true
ro.semc.clearphase.supported=true
persist.service.clearphase.enable=1
com.sonyericsson.xloud_enabled=true
ro.semc.xloud.default_setting=true
com.sonymobile.clearphase_enabled=true

Quote:
Originally Posted by stueycaster

Check out this profile. I strengthened the reverb a little and cranked down the gain some so there shouldn't be any hissing. At least I don't get any.

FX:

Master Power:
Playback Gain Control: ✘
Viper DDC - X
Spectrum Extension - X
FIREqualizer:
Select Preset: Custom (see image)
Convolver:
Impulse Response: TruTheatre Surround Headphone Live Room.irs
Field Surround: ✘
Differential Surround X
Headphone Surround +:
Effect Level - 2
Reverberation:
Room size - 49m2
Sound Field - 10m
Damping Factor - 80%
Wet Signal - 20%
Dry Signal - 60%
Dynamic System:
Listening Device - unknown type 2
Dynamic Bass - 14%
Fidelity Control:
Viper Bass:
Bass Mode: Natural Bass
Bass Frequency: 78Hz
Select Bass Boost: 14.0 dB
Viper Clarity: ✘
Clarity Mode: Natural
Select Clarity: 6.0
Auditory System Protection ✘
Master Gate (Limiter)
Output Gain: -10.5dB
Channel Pan - 0.5 - 0.5
Limit Threshold - 0dB



Then I also use Dolby Atmos for nothing but a little extra surround. My earphones give a fairly balanced sound so this setup gives me a pretty balanced sound with a bit of a fat bottom, wide separation and a pretty decent ring. If your earphones are naturally bassy this profile will probably be pretty boomy. Anyway give it a try if you like. I hope you like it.

In case you need the TruTheater irs.



Stueycaster TruTheatre profile with TruTheatre IRS.zip is attached below.

Sent from my SM-N910V DE

Quote:
Originally Posted by RSDamasceno

@guitardedhero

I "created" a package with the profiles in #2 + with many many many profiles that collect long time, and upload here:
https://db.tt/4WIJXf8O
Mirror: https://docs.google.com/uc?id=0B2NPI...xport=download


V1
* 50 profiles (50 IRS + 2 VDC)
* All revised
* Initially created for personal purposes (Perhaps a profile does not sound good to your hardware set)
* All profiles tested in my Moto Maxx / JBL-J22 / Home Theater Samsung F5555WK via Bluetooth
* A good starting point for beginners
* Credit to the creator of the profile is the profile name (if possible!)


Next releases
* I plan to review more than 200 profiles that collect


Instructions:
Just extract to your ViPER4Android folder


P.S.: If you do not agree with my collection I can remove.









Profiles_(mega_pack)_v1.zip attached below

I "created" a package with the profiles in #2 + with many many many profiles that collect long time, and upload here:

.

* Initially created for personal purposes (Perhaps a profile does not sound good to your hardware set) *
* A good starting point for beginners *
* Credit to the creator of the profile is the profile name (if possible!) *

.

Change log V2:
* 100 profiles (62 IRS + 2 VDC)
* All revised with ViPERAudio 4.7.1 Sony Beats Edition
* All profiles tested in my Moto Maxx / JBL-J22 / Home Theater Samsung F5555WK via Bluetooth

Change log V1:
* 50 profiles (50 IRS + 2 VDC)
* All revised with ViPERAtmos 5.3 Sony Beats Edition
* All profiles tested in my Moto Maxx / JBL-J22 / Home Theater Samsung F5555WK via Bluetooth

.

Instructions:
Just extract to your ViPER4Android folder


Next releases
* I plan to review more than 170+ profiles that collect


P.S.: If you do not agree with my collection I can remove.








Profiles_(mega_pack)_v2.zip attached below.

I "created" a package with the profiles in #2 + with many many many profiles that collect long time, and upload here:

.

* Initially created for personal purposes (Perhaps a profile does not sound good to your hardware set) *
* A good starting point for beginners *
* Credit to the creator of the profile is the profile name (if possible!) *

.

Change log V3:
* 150 profiles (81 IRS + 4 VDC)
* All revised with ViPERAudio 4.8.2 Sony Beats Edition
* All profiles tested in my Moto Maxx / JBL-J22 / Samsung F5555WK via Bluetooth

Change log V2:
* 100 profiles (62 IRS + 2 VDC)
* All revised with ViPERAudio 4.7.1 Sony Beats Edition
* All profiles tested in my Moto Maxx / JBL-J22 / Samsung F5555WK via Bluetooth

Change log V1:
* 50 profiles (50 IRS + 2 VDC)
* All revised with ViPERAtmos 5.3 Sony Beats Edition
* All profiles tested in my Moto Maxx / JBL-J22 / Samsung F5555WK via Bluetooth

.

Instructions:
Just extract to your ViPER4Android folder


Next releases
* I plan to review more than 290+ profiles that collect










Profiles_(mega_pack_v3.zip attached below.

Added V4

I "created" a package with the profiles in #2 + with many many many profiles that collect long time, and upload here:

* Initially created for personal purposes (Perhaps a profile does not sound good to your hardware set) *
* A good starting point for beginners *
* Credit to the creator of the profile is the profile name (if possible!) *

Change log V4:
* 200 profiles (102 IRS + 4 VDC)
* All revised with ViPERAudio 4.8.1.1-2 Sony Beats Edition
* All profiles tested in my Moto Maxx / JBL-J22 / Samsung F5555WK via Bluetooth

Old change logs:
Change log V3:
* 150 profiles (81 IRS + 4 VDC)
* All revised with ViPERAudio 4.8.2 Sony Beats Edition
* All profiles tested in my Moto Maxx / JBL-J22 / Samsung F5555WK via Bluetooth

Change log V2:
* 100 profiles (62 IRS + 2 VDC)
* All revised with ViPERAudio 4.7.1 Sony Beats Edition
* All profiles tested in my Moto Maxx / JBL-J22 / Samsung F5555WK via Bluetooth

Change log V1:
* 50 profiles (50 IRS + 2 VDC)
* All revised with ViPERAtmos 5.3 Sony Beats Edition
* All profiles tested in my Moto Maxx / JBL-J22 / Samsung F5555WK via Bluetooth
Instructions:
*If you are upgrading delete the folder called STOCK inside the folder viper4android
Just extract to your ViPER4Android folder

Next releases
* I plan to review more than 220+ profiles that collect

Profiles_(mega_pack)_v4.zip attached below.

Quote:
Originally Posted by abeloman

Well. here's my contribution... Juanpro (Just Another Profile) only for Headset

I'm currently using JBL J22, and I think I have a decent performance with this settings... It should work well with most earphones and you can play with the "Dynamic System" (to get more bass according to your headset)... I borrow the template from @sonophilos (hope it doesn't mind) to share settings here, because I'm using another lenguage (:

PlaybackAGC - Enabled / Slight / 2x Max Gain
Convolver - Enabled / DFX Urban RB.irs
Dynamic System - Enabled / Common Earphone(v1) or (v2) *the choise depends on you* / 5%
ViPER Bass - Enabled / Natural Bass / 40Hz / 8.0 Db
ViPER Clarity - Enabled / Natural / 3.5 Db
Cure Tech+ - Enabled / Moderate
Output Gain - 3.5 Db *this depends on you*

Obviously the settings I didn't mention are default, or disabled. Personally I don't have any distorsion or crackle with rising "Output Gain", and even I play with the sound values from my kernel (my device without this modifications has a very low volume). Hope you like it!
Juanpro.zip attached below.

Quote:
Originally Posted by adm1jtg

@guitardedhero sent you a pm
Also found these if u havent already seen them
http://en.miui.com/thread-71540-1-1.html

The Following 77 Users Say Thank You to guitardedhero For This Useful Post: [ View ] Gift guitardedhero Ad-Free
24th November 2014, 10:51 PM |#3  
Senior Member
Flag Hayward, CA
Thanks Meter: 83
 
More
I tried but couldnt get it to work. Audio just doesnt sound the same without it. Im hoping that when Im finally able to install it, the sound quality from the speakers will improve. It gets plenty loud, and I think it does a great job of sounding "surround", but I was hoping for the same sound quality as the M8s boomsound speakers.
The Following 4 Users Say Thank You to Moostafa29 For This Useful Post: [ View ] Gift Moostafa29 Ad-Free
24th November 2014, 10:56 PM |#4  
tflogic's Avatar
Senior Member
Thanks Meter: 82
 
More
yep got it working on my N6.

downloaded your n5 lollipop V4A, installed SELinux Mode Changer, changed mode to "Permissive", and it works perfectly.
The Following 6 Users Say Thank You to tflogic For This Useful Post: [ View ] Gift tflogic Ad-Free
24th November 2014, 11:05 PM |#5  
AndrasLOHF's Avatar
Senior Member
Thanks Meter: 2,088
 
More
Quote:
Originally Posted by tflogic

yep got it working on my N6.

downloaded your n5 lollipop V4A, installed SELinux Mode Changer, changed mode to "Permissive", and it works perfectly.

Sweet man thanks. I'll get the OP set up soon with the zip.
The Following User Says Thank You to AndrasLOHF For This Useful Post: [ View ] Gift AndrasLOHF Ad-Free
24th November 2014, 11:30 PM |#6  
tflogic's Avatar
Senior Member
Thanks Meter: 82
 
More
Quote:
Originally Posted by AndrasLOHF

Sweet man thanks. I'll get the OP set up soon with the zip.

oh! forgot to mention thus but the only qualm I have with V4A on the device is that the "Driver Status" option is greyed out and unclickable. it doesn't really make a difference since I can notice sound effects changing whenever I'm messing around with the settings but I thought it might be mentionable.
The Following User Says Thank You to tflogic For This Useful Post: [ View ] Gift tflogic Ad-Free
25th November 2014, 02:32 AM |#7  
Inactive Recognized Developer
Flag New York, NY
Thanks Meter: 37,909
 
Donate to Me
More
Installed apk, set it to permissive and installed driver and then it worked.
The Following 5 Users Say Thank You to zephiK For This Useful Post: [ View ] Gift zephiK Ad-Free
25th November 2014, 04:51 AM |#8  
recepo1's Avatar
Senior Member
Flag Philly,PA
Thanks Meter: 200
 
More
Quote:
Originally Posted by zephiK

Installed apk, set it to permissive and installed driver and then it worked.

What did you set to permissive? And how did you set it to permissive?
25th November 2014, 04:57 AM |#9  
Inactive Recognized Developer
Flag New York, NY
Thanks Meter: 37,909
 
Donate to Me
More
Quote:
Originally Posted by recepo1

What did you set to permissive? And how did you set it to permissive?

If you read the thread, just get the app SELinux Mode Changer from Play Store and you can set it to permissive instead of enforcing.
25th November 2014, 05:00 AM |#10  
recepo1's Avatar
Senior Member
Flag Philly,PA
Thanks Meter: 200
 
More
Quote:
Originally Posted by zephiK

If you read the thread, just get the app SELinux Mode Changer from Play Store and you can set it to permissive instead of enforcing.

Read the thread was just curious if it was a different method
25th November 2014, 03:12 PM |#11  
danarama's Avatar
Senior Member
Flag Oxenhope, West Yorkshire, UK
Thanks Meter: 19,167
 
More
Quote:
Originally Posted by tflogic

oh! forgot to mention thus but the only qualm I have with V4A on the device is that the "Driver Status" option is greyed out and unclickable. it doesn't really make a difference since I can notice sound effects changing whenever I'm messing around with the settings but I thought it might be mentionable.

Bi-product of compatibility mode.
The Following User Says Thank You to danarama For This Useful Post: [ View ] Gift danarama Ad-Free
Post Reply Subscribe to Thread

Tags
atmos, beats, v4a, viper, viper4android

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes