[MODULE][AUDIO] Jackshi Audio (improve the volume levels n moar) - Xiaomi Poco X3 NFC Themes, Apps, and Mods

Yo there.
Brief summary
My previous device was a Mi A1 which packed some punch on its audio jack output. It could go LOUUUUD. Obviously I found X3's sound very lacking in that regard but very good in other audio aspects. Upon inspecting MIUI's mixer_paths, I found out that qualcomm's codec ULP mode (ultra low power) is used by default when you plug in some headphones. AFAIK this mode disables the codec's dedicated headphone amplifier (or something close to it, didn't really investigate further after getting the results I wanted lol). But no. We don't want this.
Sooo?
This module will increase/boost your jack**** 3.5mm volume levels. It does this by enabling the HIFI mode provided by the SoC's codec and disabling its compander module. It also tunes both the analog and digital values to more optimal levels.
Why not just increase RX_blablablabla?
Becaaause, with that method you increase digital gain only, which introduces distortion and similar artifacts. We don't want that. Before increasing the digital gain as high as possible, we need to do it with the analog gain first. The module does this for you, using values based off my testing.
If you want to go louder still, edit the mixer_paths_wcd9375 file present inside the module zip and increase the RX Digital Volume values of the headphones-ce section. If you're using AML do the same on the .aml.sh file (it is 83 by default).
What about HPHR/L?
It is already maxed out by default (20) and doesn't work unless you disable qualcomms compander. This module disables the compander and actually reduces it to 19 just to be on the safe side. If you want to go higher still follow the same steps presented above.
Why LOHIFI and not HIFI?
From my testing, there's no difference between those two and I'll always favor the mode which is more battery friendly.
Compatibility
Should work with any audio mod out there as long as you use AML.
Can also be used standalone.
It has only been tested on the lastest Xiaomi.EU build but should work in any MIUI based ROMs and most likely AOSP ROMs too (didn't test yet but it SHOULD work).
If you want to be 100% sure it works on your ROM (AOSP or not) install AML and Ainur NARSIL. I'll also leave my narsil_useroptions if you're interested.

Interesting, but isn't Ainur Narsil module doing the same thing? Like removing compander for example?
Also, doesn't Ainur edit mixer_paths too for higher volume?

@SkaboXD Ainur doesn't adjust the volumes but yeah, you can use it to disable the headphones compander module as well (although I'm not sure if that actually works). AFAIK.

theres 2 zip which one should i flash? im on eu, no other audio mod installed.
nvm. im just stupid

its magisk module ?

zainnasai said:
its magisk module ?
Click to expand...
Click to collapse
It is, checkout the description.

_Yank said:
It is, checkout the description.
Click to expand...
Click to collapse
thanks bro

at least mention AML as Audio Modification Library (magisk module) once I totally had to think hard what it was. Also you made it sound with Ainur Narsil you can test it, not that it should 100% work with it and AML.
also looking at your narsil_useroptions, the value for impendance is wrong? it should be 48000 instead of just 48 for 48ohm
thanks tho, much appreciated.

_Yank said:
It is, checkout the description.
Click to expand...
Click to collapse
Where you can edit the volume of the Bluetooth ?

Related

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

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​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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/nexus-6/development/rom-stock-debloated-deodexed-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/android/apps-games/mod-dolby-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/android/software/audio-mod-dolby-digital-plus-universal-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/showpost.php?p=61858278&postcount=3079
and
http://forum.xda-developers.com/showpost.php?p=63425983&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/B008G...ony+xb90ex&dpPl=1&dpID=41dggsErE4L&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/android/software/mod-htc-beats-audio-beats-xperience-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/T3umvfdsg6nlsbyxiq7he7r5enu?t=Satisfy_-_Nero
Born of Osiris - Exhil∆r∆te https://play.google.com/music/m/Tbkw4olkiaj4ncvcuqimh6525oe?t=Exhilarate_-_Born_Of_Osiris
Bar 9 - The Beginning https://play.google.com/music/m/Tcdnzqm4nvitqtnxemjhb5dxwky?t=The_Beginning_VIP_Mix_-_Bar9
Stick Figure - Breathe https://play.google.com/music/m/Tf4jnzzlzx2vgqgpg6gqbckjrpe?t=Breathe_-_Stick_Figure
Tove Lo - This Time Around https://play.google.com/music/m/Tnwlggfz6k7rxth6lkpwympov74?t=This_Time_Around_-_Tove_Lo
August Burns Red - Echoes https://play.google.com/music/m/Txboufaitol43nwfehjwylplmii?t=Echoes_-_August_Burns_Red
August Burns Red - Black Sheep https://play.google.com/music/m/Ti4zm65ym6mfeb4leax6d7t7t6a?t=Black_Sheep_-_August_Burns_Red
Zomboy - Bad Intentions https://play.google.com/music/m/Tnojluypzn2cuirhwc4bhjohzdm?t=Bad_Intentions_Original_Mix_-_Zomboy
Liquid Stranger - Nintendo https://play.google.com/music/m/Tt3ngoekwqkzyre6bm4wlolew3u?t=Rocket_Fuel_-_Liquid_Stranger
All Shall Perish - There is No Business to be Done on a Dead Planet https://play.google.com/music/m/T5uq4qmmsrnepzwcztuzk6xmj4q?t=There_Is_No_Business_to_Be_Done_on_a_Dead_Planet_-_All_Shall_Perish
Crotchduster - Mammal Sauce https://play.google.com/music/m/T3szem6dbui32ghaiy2succx3uy?t=Mammal_Sauce_-_Crotchduster
Testing Environment​Headset
> Sony™ MDR-XB90EX http://www.amazon.com/MDR-XB90EX-In-Ear-Headphones-Japanese-Import/dp/B008G80FIU
Bluetooth
> Pioneer™ DEH80PRS http://www.amazon.com/gp/aw/d/B006Y...s=deh80prs&dpPl=1&dpID=41zvBwNuamL&ref=plSrch
> Focal™ Integration ISC 165 6.75" http://www.amazon.com/gp/aw/d/B0159...cal+isc165&dpPl=1&dpID=41eyRcNORfL&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/B00TT...ny+srs+x55&dpPl=1&dpID=51sgE76lJzL&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.
derekr44 said:
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
Click to expand...
Click to collapse
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/showpost.php?p=65346831&postcount=6223
Experiencing audio disturbances while using a custom kernel? Our friend, @Woody explains:​
Woody said:
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).
Click to expand...
Click to collapse
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/showthread.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!! :good:
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:
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. :good:
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.
Click to expand...
Click to collapse
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
ViPER|Atmos™ ReDUX™ Test Build Resource​
Click to expand...
Click to collapse
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.
User Content Area​
sonophilos said:
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
Click to expand...
Click to collapse
.
sonophilos said:
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
Click to expand...
Click to collapse
-decipher- said:
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.
Click to expand...
Click to collapse
tcat007 said:
Here's mine. Atmos setting "open" (left), surround on. V4a profile attached, irs: BBE Generic2.
Tcat007.zip is attached below.
Click to expand...
Click to collapse
-decipher- said:
Viper4Android Look:
CM13 theme engine theme: DEEPDARKNESS//. Screen below.
Click to expand...
Click to collapse
rolarocka said:
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
Click to expand...
Click to collapse
ranaxda200 said:
I'm attaching my all favorites convolvers. Hope it'll be useful for those who need it.
convolver.zip attached below.
Click to expand...
Click to collapse
Jimbus369 said:
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.
Click to expand...
Click to collapse
derekr44 said:
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...
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
Click to expand...
Click to collapse
tcat007 said:
If anyone wants a Red/Gold layer for v4a I have attached what I use.
Tcat-v4a.apk attached below.
Click to expand...
Click to collapse
dead0 said:
@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
Click to expand...
Click to collapse
stueycaster said:
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
Click to expand...
Click to collapse
RSDamasceno said:
@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=0B2NPIEc31bRpNV9VZW4wbzlXcXc&export=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.
Click to expand...
Click to collapse
abeloman said:
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.
Click to expand...
Click to collapse
adm1jtg said:
@guitardedhero sent you a pm
Also found these if u havent already seen them
http://en.miui.com/thread-71540-1-1.html
Click to expand...
Click to collapse
yep got it working on my N6.
downloaded your n5 lollipop V4A, installed SELinux Mode Changer, changed mode to "Permissive", and it works perfectly.
tflogic said:
yep got it working on my N6.
downloaded your n5 lollipop V4A, installed SELinux Mode Changer, changed mode to "Permissive", and it works perfectly.
Click to expand...
Click to collapse
Sweet man thanks. I'll get the OP set up soon with the zip.
AndrasLOHF said:
Sweet man thanks. I'll get the OP set up soon with the zip.
Click to expand...
Click to collapse
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.
Installed apk, set it to permissive and installed driver and then it worked.
zephiK said:
Installed apk, set it to permissive and installed driver and then it worked.
Click to expand...
Click to collapse
What did you set to permissive? And how did you set it to permissive?
recepo1 said:
What did you set to permissive? And how did you set it to permissive?
Click to expand...
Click to collapse
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.
zephiK said:
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.
Click to expand...
Click to collapse
Read the thread was just curious if it was a different method
tflogic said:
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.
Click to expand...
Click to collapse
Bi-product of compatibility mode.
Got it working. Thanks!!!
1: Set SELinux to PERMISSIVE mode
2: Installed zip via TWRP.
3: Installed driver upon app first open (super quality mode)
4: Allowed all root prompts.
5: Tried both compatibility mode and normal mode with unchecking NuPlayer
Anything I'm missing? It's still not working...
EDIT: It's Finally working... It's on compatible mode & super high quality driver.
Bjray said:
1: Set SELinux to PERMISSIVE mode
2: Installed zip via TWRP.
3: Installed driver upon app first open (super quality mode)
4: Allowed all root prompts.
5: Tried both compatibility mode and normal mode with unchecking NuPlayer
Anything I'm missing? It's still not working...
Click to expand...
Click to collapse
Double check the permissive app. I've had issues with it reverting to enforcing after a reboot. What music player are you using?
AndrasLOHF said:
Double check the permissive app. I've had issues with it reverting to enforcing after a reboot. What music player are you using?
Click to expand...
Click to collapse
Don't know exactly what fixed it but I'm using GPM.
Does it work when you play YouTube video's? Or just music player
Worked like a charm!
kepapas said:
Does it work when you play YouTube video's? Or just music player
Click to expand...
Click to collapse
It should process system wide when in normal mode.
I am unable to make this work.
I have permissive SELinux, I checked every time I rebooted my phone.
I redownloaded and reflashed the zip while wiping cache+dalvik via twrp.
Installed the super high quality driver and rebooted phone.
Tried compativility mode and normal mode with the dev setting off.
Rebooted and when I check driver status it says everything is enabled, but it is not processing.
Any help would be appreciated!
TmobileDash12 said:
I am unable to make this work.
I have permissive SELinux, I checked every time I rebooted my phone.
I redownloaded and reflashed the zip while wiping cache+dalvik via twrp.
Installed the super high quality driver and rebooted phone.
Tried compativility mode and normal mode with the dev setting off.
Rebooted and when I check driver status it says everything is enabled, but it is not processing.
Any help would be appreciated!
Click to expand...
Click to collapse
This might sound stupid but... What effect are you trying to activate and use? Try setting some of the effects to the extreme values to see if it changes anything, especially the EQ, seems like they only make noticeable differences at high values. And some effects just plain don't work it seems.

[MOD][v2.0.0 - 2016 05 09] MixerMod *Stereo Speakers + Audio Adjustments*

*T&C*
When posting in this thread be respectful to all members and abide by XDA rules/guidelines.
Do not re-use any included files/code in another project without prior permission.
I am not responsible for anything that happens as a result of using these files, instructions or commands/code.
Your destiny is your own.
Click to expand...
Click to collapse
MixerMod
Stereo speaker output and hardware level audio tweaks for the Moto G 3rd Gen.
Features
Survival Script
Multiple Editions
Backup / Restore
System-less Support
Customisable Installer
Audio Enhancements
(modified mixer_paths.xml)
Latest updates from CyanogenMod & Motorola
Volume boost for handset (in-call), headphones & tty
Stereo speaker output for media audio, speaker phone, system sounds, alarms, etc
***DISCLAIMER***
By using this mod you take full responsibility for, but not limited to, any damage that may occur to your device, data, ears, or musical taste, etc
You agree not to hold the author liable in anyway.
Do not blame me if; your sound stops, jaw drops, thermonuclear war starts or zombie apocalypse now
Click to expand...
Click to collapse
*Install at your own risk*
Compatibility
Device
Moto-G3 merlin
Moto-G3 osprey
Moto-E2 surnia
may work on other devices with similar hardware
ROM
(Android L 5.1.1 – M 6.0.1)
Stock Moto, CM based, AOSP
should work with any ROM/kernel
Requirements
A Compatible Device
Custom recovery (temporary boot or permanent flash) OR a file-manager with RW /system
(stock recovery has not been tested so pls report any results here)
NOT Required
Root, busybox, manual modifications
**NANDROID NANDROID NANDROID**
It is advised to always have a recent nandroid/twrp backup of /system (minimum) saved locally before making any critical system changes, so please do this before proceeding.
Click to expand...
Click to collapse
Installation
Flash MixerMod-install.zip from recovery
OR
copy/paste mixer_paths.xml to /system/etc and set file permissions to rw-r-r (chmod 644)
(optional) copy/paste 55-mixer.sh to /system/addon.d and set file permissions to rwx-rx-rx (chmod 755)
Reboot
Removal
Flash MixerMod-restore-CM.zip from recovery
(if updating OTA with stock Motorola ROM; flash restore-Moto.zip)
OR
Replace /system/etc/mixer_paths.xml with stock version or rename mixer_paths.xml.bak
(optional) delete /system/addon.d/55-mixer.sh
Reboot
**HINTS**​
Safe Usage​
Lower all android volumes to below 50% (system, in-call & media volume, etc) BEFORE installing for the first time (to ensure vol is not set to high upon initial activation).
Do not use high volume for long periods of time.
Your general listening volume levels should be set between 25%-75%
Only use max volume (75%-100%) for quiet sources as even the main speaker can distort at high volume.
When using your device in landscape: ensure buttons face up so the handset speaker is on your left and the main speaker is on your right (rotating your device will not change left/right output).
To equalise speakers; adjust the L:R balance/pan in your default AudioFX App or favourite media player, if the setting is available make L>R.
If you also have 3rd party sound enhancement/processing mods or libraries installed (EG Viper4android, Dolby, Sony, Beats, etc) then; It is recommended to use a balanced-soft-medium release as the volume increase in the louder releases may be too much and cause distortion &/or impact sound quality.
Click to expand...
Click to collapse
Most Importantly:
Please Enjoy !!
If you wish to use this mod or any of the included files/code for your own ROM build or mod;
Please first PM me a request with your project details and provide clear & appropriate credit when approved.
Testimonials
aSuperSaiyanG0D said:
I installed the boosted variant/edition on my moto g3 (osprey) along side the xtrememusic mod and gotta say..
Bravo man, bravo
...I like how the earpiece is a tad lower than the main speaker...like the HTC 10 sound (top speaker is for treble and bottom is for bass)
Click to expand...
Click to collapse
**WARNING**
The handset speaker on this device is not designed for media-audio playback and is not capable of matching the max volume or quality of the main speaker.
After installing this mod you should not play audio at high volume for long periods of time if you are concerned about damaging your speakers.
Click to expand...
Click to collapse
Downloads
<Android File Host> | <XDA Downloads>
<Changelog & Version Info>
<Addons & Tools>
<Guides>
<FAQ>
​
Credits & Thanks
@hp420 for testing & sharing MotoG3 system-wide volume boost
@chdloc for IIR biQuads discovery, app & info
@osm0sis for ZipScriptSign tool + testkeys and mountSU
@Alberto97 and CyanogenMod for updated system/device files + zip binary file
@lost101 and Motorola for stock system/device files
@Lukest85 (me) for sharing, coding & compiling this mod + discovering & activating stereo speaker output for this device
YOU; the XDA community for rockin' the casbah !!
Apologies if I missed anyone; Pls PM me!
Support
XDA PM or post in thread
Donations
XDA:DevDB Information
MixerMod, Device Specific App for the Moto G 2015
Contributors
Lukest85, Lukest85, Lukest85
Source Code: https://github.com/cyanogenmod/android_device_osprey-cm13/
Version Information
Status: Testing
Current Stable Version: 1.0.0
Stable Release Date: 2016-04-25
Current Beta Version: 2.0.0
Beta Release Date: 2016-05-09
Created 2016-04-25
Last Updated 2016-05-09
*MixerMod Editions*​Overview
From balanced -> loud
The main/right speaker volume increases and the handset/left is constant.
The handset speaker (left) has now been activated at max volume but it is still significantly softer than the main speaker (right) by upto 30dB at default ±0dB
Due to this limitation the only way to achieve L:R balance is to reduce the main speaker volume proportionately.
The balanced edition addresses this issue with ±2dB variance but the softest main spkr (right) & overall volume.
Considering the overall volume reduction of the balanced edition may not be practical or necessary for everyday use;
I have created separate editions with different volume levels within safe min/max range to hopefully suit most use cases and device setups.
The different editions can now be used to achieve the best available L:R balance for your desired overall volume;
If one edition is to loud/unbalanced then try the next edition down in volume
If one edition is to soft then try the next one up in volume
If you want a custom package just ask
Tech Spec
Activated: ±0dB for all outputs and ±0dB master volume (NOT balanced)
Details of other editions below
The following editions apply +10dB to the left spkr volume and ±0dB in-call
Balanced: -20dB to right/main speaker volume
Soft: -10dB to right/main speaker volume
The following editions apply +10dB to the left spkr volume and +2dB in-call
Medium: -4dB to right/main speaker volume
Loud: ±0dB to right/main speaker volume
The following editions apply +12dB to the left spkr volume and +2dB in-call
Boosted: +2dB to right/main speaker volume
All editions (excluding activated) include the following audio tweaks;
Master volume: +2dB
Headphones/tty digital volume: +2dB
Handset/Left speaker output gain: x4
Volume Chart
Code:
[B]v1.0.0 Pure Stereo[/B]
[B]Name - Master Spkr-L Spkr-R HPhones In-Call[/B]
activated - 84 84 84 84 84
balanced - 86 94 64 86 84
soft - 86 94 74 86 84
medium - 86 94 80 86 86
loud - 86 94 84 86 86
boosted - 86 96 86 86 86
[I](86 = +2dB) (default = 84 aka ±0dB)[/I]
Click to expand...
Click to collapse
*Changelog*​
Latest Stable Release
Code:
[B]2016-04-25 v1.0.0[/B]
[I]Initial Release[/I]
Audio:
*Stereo speaker output
*Digital volume optimization for all outputs
*All CM commits: new Low-Latency Recording path + xml fixes
Package:
*Backup/Restore
*Survival Script
*Multiple editions with differing volume levels
Older Releases
Code:
Not yet
Latest Testing Release
Code:
[B]2016-05-10 beta2 v2.0.0[/B]
Package:
*Bug fix for /system SuperSU install
*Additional error/failure notifications
Audio:
*Reduced processing for speakers (vs beta1)
*If IIR filters don't work try temp disabling hotword detection (OK google)
Editions:
*All-In-One
*System (no SU or /systemSU)
*IIR (alpha) Headphone biQuad filters
All other editions have been included in each of the above
Older Releases
Code:
[B]2016-05-09 beta1 v2.0.0[/B]
Audio:
*New routing for speakers (fuller sound, more chance of distortion at high vol)
*Adjusted SRS TruMedia and Analogue Volume for Headphones (may not work with every setup)
*Increased Headphone volume for each edition
*Adjusted L:R speaker balance/volume for each edition
New Editions:
*AIO (beta) All In One
Includes all editions for a personalised setup via mixer.prop file (change SETTINGS with txt editor)
*IIR (alpha) Headphone biQuads
Loud edition with Infinite-Impulse-Responce filters for headphones (qcom h/w level 5-band equalizer)
Default is passthrough (no change)
Package:
*Major overhaul of all scripts & files (inc. shell script instead of updater-script)
*Default install to /su
*Backup/restore to/from anywhere in local storage (int or ext) or not at all
*Utilise 'mixer.prop' config file for a customisable & personalised setup/restore (store anywhere in /sdcard)
*Volume level specs for editions now reside in mixer.prop
*Survival script now optional (via mixer.prop)
*zip size greatly reduced
*Support for addons
*Improve multi-device support
Upcoming Features
subject to change and in no particular order
Include system-less setup without SuperSU (init.d) currently manual process
GUI for installer/restore (AROMA)
Further audio improvements
Stay tuned
Please contact me if you wish to contribute and/or collaborate !
Click to expand...
Click to collapse
*Tools & Addons*​
Native to MixerMod
Due to XDA upload restrictions you will need to remove the last .xyz extension (ie .txt) from the filename of each attachment BEFORE utilising the addon.
Download from attachment or AFH​
Survival Script (addon.d): 55-mixer.sh
Keep MixerMod installed throughout ROM flashes (safe).
included in MixerMod-install.zip and also available separately.
Code:
See OP for install/removal instructions
Linking script (su.d): 55mixer
System-less SuperSU compatibility (/su)
will be integrated with future MixerMod-install.zip
Can be modified for /system/su.d or /system/etc/init.d compatibility
Code:
copy/paste a modified mixer_paths.xml to /su/etc and set file permissions to rw-r-r (chmod 644)
copy/paste linking script to /su/su.d and set file permissions to rwx (chmod 700)
reboot
Tinymix: binary file
Testing mixer_paths.xml changes live & on the fly.
usually already included in each ROM. This version is from the latest stock osprey Moto ROM.
Code:
copy/paste to system/bin
set file permissions to rwx-rx-rx (chmod 755)
Usage: run from terminal as su
Code:
tinymix ‘control’ ‘value’
(integer/number values do not require quotes but all controls DO)
Examples
Set the handset speaker master volume to default ±0dB
Code:
su
tinymix ‘RX1 Digital Volume’ 84
Set the main speaker master volume to default ±0dB
Code:
su
tinymix ‘RX3 Digital Volume’ 84
Query current volume levels (differs per output device ie speakers/headphones/in-call)
Code:
su
tinymix | grep Digital
Funky Beats: Spotify Playlist by @Lukest85
An eclectic mix of favourite tracks, hidden gems and new releases.
Check 'em out or follow along to get your groove on.
My starred playlist, in no particular order.
Shuffle, Press Play and Enjoy !
Free for anyone to listen online (browser or app, no premium account required)
Click to expand...
Click to collapse
Kernels with FauxSound Control
Currently in testing​
Use one of these kernels for additional hardware level audio enhancements & sound control.
Configure volume & gain levels from within your preferred kernel control app (eg Kernel Adiutor) or FauxSound compatible app
Inazuma Kernel by @zeeshanhussain12
AGNi Kernel by @psndna88
Click to expand...
Click to collapse
Recommended Audio Mods
HINTS
These have been tested on this device in conjunction with MixerMod and should not cause any conflicts, though you may need to apply a balanced/soft/medium edition of MixerMod.
​
Remastered System Sounds by @Locklear308
High quality system sounds, remastered in stereo.
More themed and ported system sounds available.
Take full advantage of your stereo speakers !
Evangelion System Sounds by @simonpunk2013
Futuristic system sounds, notifications and alarms.
Many more EVA themed goodies.
Ported from NERV ROM posted by @TakuyaZ
ViPER4Android MK-Mod by @metaspook
Modified version of famous V4A audioFX app by @zhuhang
Software equalizer with many tweaks + new sound drivers/library.
Standalone app.
Viper|Atmos SonyBeats by @guitardedhero
Well renowned AIO audiophile tweaking package with maximum compatibility. The new standard.
Third party sound enhancements, libraries, tweaks & software equalizers
Includes: ViPER4Android, Dolby Atmos, Sony & Beats sound libraries
Click to expand...
Click to collapse
Popular Sound Libraries & Effects
HINTS​
May not be compatible with every setup.
Only install ONE of the following mods at any given time as there may be some conflicts and/or overlap.
If you want a combo setup then search the respective mod's support thread and you should find something posted by @guitardedhero to suit your needs, if it's not already available in the OP.
XTREMEMusic by @androidexpert35
Ultimate compilation of many integrated sound libraries, effects & EQ.
Based on Project Desire, PON-3 & HTK Audio Engine, with many extras
Includes
ViPER4Android
XTREMEMusic AudioFX App
Optimisations for dual speaker devices
Re-sampling of 6144khz 64bit for Headphones and 192khz 24bit for Speakers
Qualcomm Hardware Effects for the onboard Snapdragon Hexagon DSP found in this device
Sound Libraries: HTC Boom Sound, Sony sForce Surround 3D, Sony DSEE-HX, Harmon Kardon, SoundAlive, Beats, SRS, DTS, MegaBass, Vivo Hi-Fi, Dirac, more
eXtremeBeats by @Ben Feutrill
Compilation of handpicked, tweaked & integrated sound libraries of very high quality, in the smallest possible package (2MB)
Includes
Sound Libraries: Sony xLoud, BeatsAudio, SRS, PureAudio Engine, more
No EQ app or apks
Compliments a ViPER4Android standalone install very well.
Project Desire by @PDesire
Compilation of many enhanced, custom made ans integrated sound libraries, with an EQ app.
Based on ReHeaR. Now EOL and open source.
Includes
Project Desire Audio Effects app
Custom Audio Engines: Harmoforia, Harmonia, CryRez/P2SE, Vibeuforium, more
Sound Libraries: SoundAlive, MaxxAudio, Dolby DTS, SRS, Sony, Beats, many more
ReHeaR by @jimRnor
A compilation of many custom and well known sound libraries & effects.
Base for many other sound mods on XDA
Includes
No EQ app
Custom Audio Engines: ZeXshO X, PMEE-HS, Harmoforia, Vibeuforium, Quantum
Sound Libraries: Maxxaudio, SRS, Dolby DTS, BeatBass, HTC Acoustic, Samsung SoundAlive, more
Click to expand...
Click to collapse
Similar Mods
Links for other devices will be added here​
Moto-G 3rd Gen
System-wide volume boost by @hp420
Boost all output volumes for stock-mono configuration.
Multiple editions with varied volume levels.
NOT directly compatible with MixerMod as they modify a common file.
Click to expand...
Click to collapse
*FAQ*​
Q: What does this mod do ?
A: Improves output audio quality by modifying system file/s for the hardware controlled audio configuration.
Checks device compatibility
Installs a modified /system/etc/mixer_paths.xml file for audio routing, output, volume/gain, etc
Preserves existing/stock system file/s as .bak until restored
Installs /system/addon.d survival script to preserve mod files across ROM flash/wipe
Includes the latest updates, fixes & cherrypicks from multiple sources (Vendor/AOSP/CM)
Q: Do Left and Right speakers output stereo or mono sound ?
A: Stereo.
This mod routes the Left audio channel to (only) the upper Handset speaker and the Right audio channel to (only) the Lower Main speaker.
Factory default routes both channels to only the lower main speaker for mono output.
Q: Are you sure the handset speaker is working ?
A: Yes, output is a lot lower than the main speaker due to device limitations.
To test put your finger over the main speaker or adjust L:R balance/pan so R=0 or L>R
Q: Is this mod safe to use ?
A: Yes; provided you do not manually modify the system files yourself (ie to increase the volume further or make other changes).
Q: Will this damage my speakers or ears ?
A: No, Provided you adhere to all warnings/instructions and do NOT modify any relevant system files manually.
Volume/Gain for all outputs are set to a safe level.
Q: Has anyone bricked or broken their device using this mod ?
A: No damage to any device has been reported due to using this mod, nor similar mods for other devices.
HOWEVER it is still recommended to make a Nandroid backup of /system before installing, not to playback audio at high volume for lengthy periods and do not make manual modifications to system files.
Q: I have a compatible device but the mod will not install or flash !
A: Please report details here and provide from build.prop your ro.product.device value and if possible any relevant log files such as /cache/recovery/last_log, logcat, etc,
Q: Is this mod compatible with xyz device ?
A: This mod is currently only compatible with recent Qualcomm Snapdragon based devices that use the onboard soundcard only.
Q: Can I try this mod with a device not listed as compatible?
A: Not recommended unless confident of h/w similarities to confirmed devices. Advise posting a request here with your mixer_paths.xml & device details so I can provide a test package.
Q: I still want to try this on an un-approved device on my own !
A: Test at your own risk but do not be surprised if you can no longer boot or experience audio issues/failure;
Flash a Test Release, as Stable Releases are restricted to approved devices only (see OP) or manually extract & install mixer_paths.xml as per OP.
Q: Should I expect any issues after installing ?
A: No
MixerMod has been confirmed to be error free & stable for all compatible devices listed in OP.
(may work on devices with similar h/w; post your mixer_paths.xml if you wish to test on a new device)
Q: After installing this MixerMod I have errors, problems, questions or requests to report !
A: Post in this thread with your original mixer_paths.xml(.bak)
Include as much relevant detail as practical: Device, ROM, kernel, any & all active sound mods or libraries, + non-stock audio settings/FX, etc
Q: What are your testing variables ?
A: Before any release I first test the new audio settings for a lengthy period of time on a Moto-G3 XT1550 osprey with different settings & variables to ensure no adverse effects:
MM 6.0.x ROMs
Custom kernels
Stock/built-in AudioFX, on vs off
3rf Party AudioFX apps/libraries
eg ViPER4Android, Dolby, Sony, Beats, etc
Multiple MultiMedia apps/players
eg Spotify, Poweramp, SonyMusic, GoogleMusic, Soundcloud, etc
Other sound/audio mods
eg eXtremeMusic, ExtremeBeats, Project Desire, etc
Various Headphones, IEM and external speakers
Built-in speakers with music, video, podcast & audio-test signals
Different environments & ambient noise levels
Volume/Balance measurements tested/recorded with a basic dB soundmeter.
Final field test and selection of each release/edition based on realworld results, compatibility and my personal experience.
Q: What are the Limitations of this mod ?
A: It will not walk your dog, laugh at your jokes or save you from an alien invasion.
I do not currently have access to suitable pro sound equipment so dB measurements for volume & balance are obtained via a basic soundmeter from another handset.
L:R Speaker orientation is locked ie Rotating your device will NOT swap Left/Right channels
Different sized h/w speaker drivers (handset vs main); to compensate for the smaller handset speaker this mod reduces the main speaker volume to achieve better L:R balance.
NB Without reducing the main speaker stereo sound would not be practical as the main speaker is too loud.
No 3rd party soundcard/DAC/DSP to utilise (ie only onboard Qualcom Snapdragon Hexagon processing is available for this device)
Click to expand...
Click to collapse
*Guides*​
General Inquiries
If you want me to make a custom file/mod for your specific setup (I'm happy to), are requesting a change to this mod, testing your own mod, reporting an error, tweaking your setup or just sharing your settings for others, then;
Post here or PM me, and include
Your desired changes
Original un-modified /system/etc/mixer_paths.xml(.bak) file
Details of your sound & device setup IE model, ROM, kernel, mods, etc
Specify any & all active sound mods/libraries + non-stock audio settings
To manually adjust your L:R speaker volume and achieve equal balance; Try A, B or C as follows.
A) via ROM audioFX app, your preferred media player w/pan, or a custom soundFX mod:
Adjust Left:Right output settings so L>R under Balance/Pan according to your preference.
**WARNING**
The following manual steps can be dangerous if a mistake is made and/or volume/gain is set to high/low so only do this if you are confident, have read all the provided info, follow the instructions implicitly and of course;
do so at your own risk, accepting all responsibility if any damage occurs.
B) via a file manager (root + RW /system)
edit/open file /system/etc/mixer_paths.xml in a text editor
Search or scroll for MixerMod under <path name=speaker />
Make your changes to XX for;
<ctl name='RX1 Digital Volume' value=XX />
<ctl name='RX3 Digital Volume' value=XX />
Where;
RX1=Left handset speaker
RX3=Right main speaker
XX sets the volume as a number between 74 and 94 in 1dB increments (stock=0:84 ±0dB)
Play some media and set Android volume <50%
Reboot to apply your changes
Test your changes & repeat the above until you are happy with the volume and balance
If you want to post your new settings please make sure to include any & all sound mods/libraries + non-stock audio settings.
C) Test temporary volume/gain levels live:
Start playing some media
NB I recommend a long playlist with varied but short music/video selections as when media focus shifts your changes will revert.
Run the following code from a terminal
Code:
su
tinymix 'RX1 Digital Volume' XX
tinymix 'RX3 Digital Volume' XX
Speaker: RX1=Left and RX3=Right
Headphones: RX1=Left and RX2=Right
Adjust XX and re-do the above until you are happy with the volume & balance
To save your desired settings edit /system/mixer_paths.xml accordingly (see above) then reboot.
Click to expand...
Click to collapse
Reserved
Reserved
omg, this is super cool! thanks.
---------- Post added at 09:28 AM ---------- Previous post was at 09:07 AM ----------
not really balanced though
HelpMeruth said:
omg, this is super cool! thanks.
Click to expand...
Click to collapse
Cheers ! 'most welcome and glad you like it !
HelpMeruth said:
not really balanced though
Click to expand...
Click to collapse
Which edition/s have you tried?
Do you have any other sound mods or libraries installed?
FYI
*Only the balanced release aims for equal L:R speaker volume as achieving this greatly reduces the main speaker volume.
*The L:R difference on my test device (osprey, stock, no other sound mods) with balanced edition ends up 0-3dB, varying slightly per frequency.
I am hesitant to lower the main speaker much more than it is already for this one but can do if requested.
*Stock/default/flat there is generally approx 30dB difference between the two speakers on this device, which is a lot for this scenario.
So perfect balance may not be practical for many situations.
*Currently L:R balance will even out as you choose a quieter edition of MixerMod (see the OP for more details).
*Volume levels for most releases can be tweaked so feedback is welcome but please provide device/setup info!
edit: Added this info to OP
i had balanced but noticed that the loudspeaker(the earpiece speaker) was a bit louder than the real speaker
HelpMeruth said:
i had balanced but noticed that the loudspeaker(the earpiece speaker) was a bit louder than the real speaker
Click to expand...
Click to collapse
osprey or merlin ?
osprey
HelpMeruth said:
osprey
Click to expand...
Click to collapse
The soft edition from OP will increase the main spkr a few knotches (10dB)
I've attached some alternate editions for you in case you only need a small change;
balanced2 will only reduce the handset spkr by 2dB
balanced3 will only increase the main spkr by 4dB
Alternatively
Run the below command/s in a terminal while audio is playing then let me know your results and I'll post a new edition for you.
(tinymix changes only last for that audio session)
Adjust main/right spkr
Code:
su
tinymix 'RX3 Digital Volume' 68
raise/lower the number until you are happy (OP balanced = 64 and stock = 84)
Adjust the handset/left spkr
Code:
su
tinymix 'RX1 Digital Volume' 92
raise/lower the number until you are happy (most OP editions = 94 which is generally the max without distortion)
Would this be safe to use alongside the xtrememusic mod?
Sent from my Nexus 7 using Tapatalk
I'm wondering how this works with ViPER4android. Would like to try it but not if V4a interferes as I really like it.
sent from my cdma X1548 Virgin Mobile Moto G 2015
Looking forward to trying this out
Will this need re-flashed everytime the official 13.1 Cyanogen nightly gets updated?
thx
aSuperSaiyanG0D said:
Would this be safe to use alongside the xtrememusic mod?
Click to expand...
Click to collapse
Sure is !
Currently MixerMod will not conflict with any other sound mods, though you may need to try different MixerMod Editions to get your desired sound/volume/balance.
Pls report results here for others with same setup.
Hedied4me said:
I'm wondering how this works with ViPER4android. Would like to try it but not if V4a interferes as I really like it.
Click to expand...
Click to collapse
There is a native headphone boost etc included in MixerMod and I can confirm it works very well in combo with V4A !
RE speakers; I would recommend to start with a balanced/soft/medium edition of MixerMod if you also use 3rd party sound libraries eg @guitardedhero 's Viper|Atmos packages, Sony, Beats, etc
bjzapp said:
Looking forward to trying this out
Will this need re-flashed everytime the official 13.1 Cyanogen nightly gets updated?
thx
Click to expand...
Click to collapse
Go for it, just set n forget !
no need to reflash MixerMod after a ROM upgrade addon.d survival script is included.
You should see a few messages from MixerMod in recovery during the process to let you know it's doing its thing...it will even backup the unmodified files from the new ROM before patching so you're never in danger.
Installed the boosted variant along side the xtrememusic mod and gotta say..
Bravo man, bravo ??
And actually I kinda like how the earpiece is a tad lower than the main speaker, kinda how I imagine the HTC 10 would sound (since the top speaker is for treble and bottom is for bass)
And yes I installed it on my moto g3 (osprey)
Disregard my signature ?
Sent from my Nexus 7 using Tapatalk
aSuperSaiyanG0D said:
Installed the boosted variant on my moto g3 (osprey) along side the xtrememusic mod and gotta say..
Bravo man, bravo ??
And actually I kinda like how the earpiece is a tad lower than the main speaker, kinda how I imagine the HTC 10 would sound (since the top speaker is for treble and bottom is for bass)
And yes I installed it on my moto g3 (osprey)
Disregard my signature ?
Click to expand...
Click to collapse
Thank you for the great report and review !! :good:
Excellent comparison too ! that's the limitation of the smaller handset spkr showing through but with lemons we make tasty lemonade :highfive:
Glad your enjoying it !
RE sig; No worries, I've an N7 somewhere as well.
If you don't mind I will add your comments as a quote/review in OP !?
Lukest85 said:
Thank you for the great report and review !! :good:
Excellent comparison too ! that's the limitation of the smaller handset spkr showing through but with lemons we make tasty lemonade :highfive:
Glad your enjoying it !
RE sig; No worries, I've an N7 somewhere as well.
If you don't mind I will add your comments as a quote/review in OP !?
Click to expand...
Click to collapse
Ayee thank you for taking the time to develop this little mod aha ?
And no problem you're more than welcome to ?
Sent from my Nexus 7 using Tapatalk

[Solved] How to remove audio distortion from all stereo phones with unequal speakers

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[Brought to you by a collaboration of Ainur and ARISE]​
Description of the issue:
The issue with all Oreo ROMs for mi max 2 right now, is that there is very apparent audio distortion at max volume.
The reason for that is this:
The phone uses a stereo setup with the earpiece acting as the left channel and the bottom loudspeaker acting as the right channel.
Of course those two speakers are not of the same quality or meant to play the same frequencies.
Reading a bit around the official miui forum you will find that the earpiece speaker is meant as a treble speaker playing mid to high frequencies and the bottom loudspeaker as a woofer playing low to mid frequencies or even high ones since it can.
Using an aosp Oreo ROM though loses that optimization and treats the two unequal speakers as equal with the result of having the earpiece rattle heavily when it must play a frequency under 550hz.
Using an equalizer such as the one included in Dolby Atmos Axon 7, to reduce every frequency Lower than 500hz worked to remove the rattle from the earpiece but also removed the bass from the bottom loudspeaker, which isn't the ideal solution.
The final solution was to implement a high filter pass (suggested by UltraM8/Sovetnikov from Ainur), which was elaborated upon and implemented by Joe0Bloggs from ARISE.
Description of included impulses:
If your left channel is the earpiece and the right channel is the bottom speaker, (which is true for mi max 2) you need one of the following impulses:
1) Hi-Low Speakerphone HiL:
Which simply applies a high filter pass of 500hz to the left channel
2) Hi-Low Speakerphone 4-Way HiL:
Which applies a high filter pass of 500hz to the left channel but also redirects those left channel frequencies that are cut-off and merges them with the right channel.
So in the scenario that the left and right channel have a difference you will he able to hear it instead of it being just cut-off
If your right channel is the earpiece and the left channel is the loudspeaker, (which may be true for other phones with a similar issue) you need one of the following impulses:
1)Hi-Low Speakerphone HiR:
Simply cuts off any frequency under 500hz with a high filter pass on the right channel.
2)Hi-Low Speakerphone 4-Way HiR:
Cuts off any frequency under 500hz from the right channel with a high filters pass but also redirects and merges it with the left channel.
To test which is your left and right channel, you can use anyone of the myriad left-right channel test videos in YouTube:
Left Right Channel Test
All the impulses are wav files and they are zipped in ImpulsesOxygen.zip, so you simply unzip them and import the wav file of your choosing in the JamesDSP Convolver.
Those impulses can also be used with ROMs of other phones that either come with dual-speaker setup or use a mod to create two channel audio.
Installation Procedure:
You will need to flash the following modules through Magisk (They can all be found in the Downloads section of Magisk Manager):
1) Ainur Sauron
2) Ainur JamesDSP (you can also use viper4a fx, but it has some bug when switching impulses)
3) Audio Modification Library
4) Audio Compatibility Patch
After flashing the requirements:
1) Reboot so all Magisk Modules are installed
2) Copy the impulse of your choosing (wav file) at 'Internal Storage/JamesDSP/Convolver' (I suggest you use the 4-Way HiL wav found in the zip for mi max 2)
3) Open JamesDSP
4) Enable the Master Switch on top of that window to activate JamesDSP
5) Enable the Convolver option near the bottom of that window
6) Select as Impulse your chosen wav file (4-way HiL for example)
Download:Mega.nz -ImpulsesJoe
(Or from the zip attachment in this post)
MD5sums of the attachments:
HiL: e9dc1fd5ce67793a60bc1d7bfb73eb72
HiR: 2ed4dab03e326643d72a7eec0f53b246
4-Way HiL: 96207e83552fc99a40e6012ff5646bbe
4-Way HiR: c0d88c31352d50ba350755f97a924266
ImpulsesOxygen.zip: 99149367d212c447d2427fd372eb2be5
Contact: For any clarifications feel free to contact @Joe0Bloggs on Telegram.
Thanks for putting the word out for this solution! :good:
Joe0Bloggs said:
Thanks for putting the word out for this solution! :good:
Click to expand...
Click to collapse
Good work man. Cheap stereo speakers can die another day.
:highfive:
Voidablazer said:
The issue with all Oreo ROMs for mi max 2 right now, is that there is very apparent audio distortion at max volume.
The reason for that is this:
The phone uses a stereo setup with the earpiece acting as the left channel and the bottom loudspeaker acting as the right channel.
Of course those two speakers are not of the same quality or meant to play the same frequencies.
Reading a bit around the official miui forum you will find that the earpiece speaker is meant as a treble speaker playing mid to high frequencies and the bottom loudspeaker as a woofer playing low to mid frequencies or even high ones since it can.
Using an aosp Oreo ROM though loses that optimization and treats the two unequal speakers as equal with the result of having the earpiece rattle heavily when it must play a frequency under 550hz.
Using an equalizer such as the one included in Dolby Atmos Axon 7, to reduce every frequency Lower than 500hz worked to remove the rattle from the earpiece but also removed the bass from the bottom loudspeaker, which isn't the ideal solution.
The final solution was to implement a high filter pass (suggested by UltraM8/Sovetnikov from Ainur), which was elaborated upon and implemented by Joe0Bloggs from ARISE.
You will need to flash the following through Magisk:
1) Ainur Sauron
2) Ainur JamesDSP (you can also use viper4a fx, but it has some bug when switching impulses)
3) Audio Modification Library
4) Audio Compatibility Patch
Now you simply have to reboot, open JamesDSP , enable the master switch, scroll down, enable convolver and select one of the attached Impulses.
(All impulses must be moved go the directory: InternalStorage/JamesDSP/Convolver)
If your left channel is the earpiece and the right channel is the bottom speaker, (which is true for mi max 2) you need one of the following impulses:
1) Hi-Low Speakerphone HiL:
Which simply applies a high filter pass of 500hz to the left channel
2) Hi-Low Speakerphone 4-Way HiL:
Which applies a high filter pass of 500hz to the left channel but also redirects those left channel frequencies that are cut-off and merges them with the right channel.
So in the scenario that the left and right channel have a difference you will he able to hear it instead of it being just cut-off
If your right channel is the earpiece and the left channel is the loudspeaker, (which may be true for other phones with a similar issue) you need one of the following impulses:
1)Hi-Low Speakerphone HiR:
Simply cuts off any frequency under 500hz with a high filter pass on the right channel.
2)Hi-Low Speakerphone 4-Way HiR:
Cuts off any frequency under 500hz from the right channel with a high filters pass but also redirects and merges it with the left channel.
To test which is your left and right channel, you can use anyone of the myriad left-right channel test videos in YouTube:
Left Right Channel Test
All the impulses are wav files and they are zipped in ImpulsesOxygen.zip, so you simply unzip them and import the wav file of your choosing in the JamesDSP Convolver.
Those impulses can also be used with ROMs of other phones that either come with dual-speaker setup or use a mod to create two channel audio.
Download:Mega.nz -ImpulsesJoe
(Or from the zip attachment in this post)
MD5sums of the attachments:
HiL: e9dc1fd5ce67793a60bc1d7bfb73eb72
HiR: 2ed4dab03e326643d72a7eec0f53b246
4-Way HiL: 96207e83552fc99a40e6012ff5646bbe
4-Way HiR: c0d88c31352d50ba350755f97a924266
ImpulsesOxygen.zip: 99149367d212c447d2427fd372eb2be5
Contact: For any clarifications feel free to contact @Joe0Bloggs on Telegram.
Click to expand...
Click to collapse
Can you please explain it in simple steps. Kind of noob friendly?
ridershahmir said:
Can you please explain it in simple steps. Kind of noob friendly?
Click to expand...
Click to collapse
Installation Procedure:
You will need to flash the following through Magisk:
1) Ainur Sauron
2) Ainur JamesDSP (you can also use viper4a fx, but it has some bug when switching impulses)
3) Audio Modification Library
4) Audio Compatibility Patch
After flashing the requirements:
1) Reboot so all Magisk Modules are installed
2) Copy the impulse of your choosing (wav file) at 'Internal Storage/JamesDSP/Convolver' (I suggest you use the 4-Way HiL wav found in the zip for mi max 2)
3) Open JamesDSP
4) Enable the Master Switch on top of that window to activate JamesDSP
5) Enable the Convolver option near the bottom of that window
6) Select as Impulse your chosen wav file (4-way HiL for example)
ridershahmir said:
Can you please explain it in simple steps. Kind of noob friendly?
Click to expand...
Click to collapse
Sure, for the user, all that's involved is
1. Have the problem--a phone that's got a big speaker and a little speaker for stereo and a custom ROM that isn't optimized for their difference
2. Test and find out whether the "small" speaker is for the left or right channel--using this video https://youtu.be/hTvJoYnpeRQ for example
3. Install the solution: the OP mentioned 4 programs but you mostly have to just make sure Ainur JamesDSP is working. Then copy the files from ImpulsesOxygen.zip to (InternalStorage)/JamesDSP/Convolver .
4. In JamesDSP, enable Master switch for Speaker and, some way down the menu, enable "Convolver enable" for convolver and choose one of the files from ImpulsesOxygen.zip as "Impulse response". Choose "hiL" or "4way hiL" if (referring back to step 2) your small speaker is for the left channel; choose "hiR" or "4way hiR" if your small speaker is for the right channel. Below screenshots are example config for the Mi Max 2 with small speaker for left channel.
ridershahmir said:
Can you please explain it in simple steps. Kind of noob friendly?
Click to expand...
Click to collapse
I really don't think it can be explained in simpler steps...
@Joe0Bloggs This is really nice, thank you for the insight. What do you think, can it be implemented on a system level without Ainur and Audio libraries?
sirdickens said:
I really don't think it can be explained in simpler steps...
@Joe0Bloggs This is really nice, thank you for the insight. What do you think, can it be implemented on a system level without Ainur and Audio libraries?
Click to expand...
Click to collapse
Someone more experienced in that level of modding can chime in here I hope... The OP was working on a modified mixer_paths that should have similar effect but it hasn't worked so far. The lines that were supposed to do the job read like this I believe
<ctl name="RX3 HPF cut off" value="MIN_3DB_850Hz" />
https://github.com/mozilla-b2g/device-flo/blob/master/mixer_paths.xml
The present approach with JamesDSP and convolver files does have more fine-grained control over the sound and the bandpass+phase shifted signal of the bass redirection channel in the 4-way filters should not be doable outside of JamesDSP or V4A.
Joe0Bloggs said:
Someone more experienced in that level of modding can chime in here I hope... The OP was working on a modified mixer_paths that should have similar effect but it hasn't worked so far. The lines that were supposed to do the job read like this I believe
<ctl name="RX3 HPF cut off" value="MIN_3DB_850Hz" />
https://github.com/mozilla-b2g/device-flo/blob/master/mixer_paths.xml
The present approach with JamesDSP and convolver files does have more fine-grained control over the sound and the bandpass+phase shifted signal of the bass redirection channel in the 4-way filters should not be doable outside of JamesDSP or V4A.
Click to expand...
Click to collapse
Sounds interesting, I am not an expert but will try and look into it.
Thank you for your kind explanation. I hope developers will also take a look at it.
Btw, stereo is awesome now! It would be interesting to tweak a bit more as I think earpiece might carry over a bit lower frequencies, thus pushing stereo even further!
AML has been included in Ainur Sauron, I can see AML libs and scripts inside the zip file. This is exactly what I did with my Max2, as I mentioned in MXM review, but I have lack of deep investment as yours, instead I use some other impulses and luckily fixed the problem too. Nice to see this thread since it can help other users. Btw, can you please write a guide to install these mods with SuperSu instead of Magisk? (AML can not install in recovery without Magisk)
romeo_coi said:
AML has been included in Ainur Sauron, I can see AML libs and scripts inside the zip file. This is exactly what I did with my Max2, as I mentioned in MXM review, but I have lack of deep investment as yours, instead I use some other impulses and luckily fixed the problem too. Nice to see this thread since it can help other users. Btw, can you please write a guide to install these mods with SuperSu instead of Magisk? (AML can not install in recovery without Magisk)
Click to expand...
Click to collapse
I don't know about AML but as far as I can tell the essence of the mod doesn't require you to install Ainur and only requires you to install one of JamesDSP and V4A, hence AML isn't necessary.
Joe0Bloggs said:
I don't know about AML but as far as I can tell the essence of the mod doesn't require you to install Ainur and only requires you to install one of JamesDSP and V4A, hence AML isn't necessary.
Click to expand...
Click to collapse
Ainur provide better audio quality. So if you only need to fix the distortion, Jame DSP or V4A is enough. But it's worth to install Ainur audio mod too, because the AOSP audio quality is worse. What I mean here is AML has been included in Ainur zip, we just need to install 1 instead 2 files.
Thank you worked very well for me. Even with Dolby atmos same time.
Whats that speaker PID count? Im not sure about the results of all this but seems that sound is improved
m1n15s said:
Whats that speaker PID count? Im not sure about the results of all this but seems that sound is improved
Click to expand...
Click to collapse
so Oreo for daily use is bearable
reversegear said:
so Oreo for daily use is bearable
Click to expand...
Click to collapse
I use oreo for months so for me was ok all this time if u mean sound wise i think now with those settings is better
Voidablazer said:
[Brought to you by a collaboration of Ainur and ARISE]
Description of the issue:
The issue with all Oreo ROMs for mi max 2 right now, is that there is very apparent audio distortion at max volume.
The reason for that is this:
The phone uses a stereo setup with the earpiece acting as the left channel and the bottom loudspeaker acting as the right channel.
Of course those two speakers are not of the same quality or meant to play the same frequencies.
Reading a bit around the official miui forum you will find that the earpiece speaker is meant as a treble speaker playing mid to high frequencies and the bottom loudspeaker as a woofer playing low to mid frequencies or even high ones since it can.
Using an aosp Oreo ROM though loses that optimization and treats the two unequal speakers as equal with the result of having the earpiece rattle heavily when it must play a frequency under 550hz.
Using an equalizer such as the one included in Dolby Atmos Axon 7, to reduce every frequency Lower than 500hz worked to remove the rattle from the earpiece but also removed the bass from the bottom loudspeaker, which isn't the ideal solution.
The final solution was to implement a high filter pass (suggested by UltraM8/Sovetnikov from Ainur), which was elaborated upon and implemented by Joe0Bloggs from ARISE.
Description of included impulses:
If your left channel is the earpiece and the right channel is the bottom speaker, (which is true for mi max 2) you need one of the following impulses:
1) Hi-Low Speakerphone HiL:
Which simply applies a high filter pass of 500hz to the left channel
2) Hi-Low Speakerphone 4-Way HiL:
Which applies a high filter pass of 500hz to the left channel but also redirects those left channel frequencies that are cut-off and merges them with the right channel.
So in the scenario that the left and right channel have a difference you will he able to hear it instead of it being just cut-off
If your right channel is the earpiece and the left channel is the loudspeaker, (which may be true for other phones with a similar issue) you need one of the following impulses:
1)Hi-Low Speakerphone HiR:
Simply cuts off any frequency under 500hz with a high filter pass on the right channel.
2)Hi-Low Speakerphone 4-Way HiR:
Cuts off any frequency under 500hz from the right channel with a high filters pass but also redirects and merges it with the left channel.
To test which is your left and right channel, you can use anyone of the myriad left-right channel test videos in YouTube:
Left Right Channel Test
All the impulses are wav files and they are zipped in ImpulsesOxygen.zip, so you simply unzip them and import the wav file of your choosing in the JamesDSP Convolver.
Those impulses can also be used with ROMs of other phones that either come with dual-speaker setup or use a mod to create two channel audio.
Installation Procedure:
You will need to flash the following modules through Magisk (They can all be found in the Downloads section of Magisk Manager):
1) Ainur Sauron
2) Ainur JamesDSP (you can also use viper4a fx, but it has some bug when switching impulses)
3) Audio Modification Library
4) Audio Compatibility Patch
After flashing the requirements:
1) Reboot so all Magisk Modules are installed
2) Copy the impulse of your choosing (wav file) at 'Internal Storage/JamesDSP/Convolver' (I suggest you use the 4-Way HiL wav found in the zip for mi max 2)
3) Open JamesDSP
4) Enable the Master Switch on top of that window to activate JamesDSP
5) Enable the Convolver option near the bottom of that window
6) Select as Impulse your chosen wav file (4-way HiL for example)
Download:Mega.nz -ImpulsesJoe
(Or from the zip attachment in this post)
MD5sums of the attachments:
HiL: e9dc1fd5ce67793a60bc1d7bfb73eb72
HiR: 2ed4dab03e326643d72a7eec0f53b246
4-Way HiL: 96207e83552fc99a40e6012ff5646bbe
4-Way HiR: c0d88c31352d50ba350755f97a924266
ImpulsesOxygen.zip: 99149367d212c447d2427fd372eb2be5
Contact: For any clarifications feel free to contact @Joe0Bloggs on Telegram.
Click to expand...
Click to collapse
Great, very very good work.Amazing sound now.
Thy for this outstanding workaround.
Would be really great if this could be implemented in lineageos as standard.
Greetz
Thank you so much for your clear explanation. Oreo sounds much better now. Again, thank you so much.
My oxygen audio is better now, dolby atmos & viper uninstalled :laugh:
Thank you ?????
Any update on getting this natively? I'm on a Pie ROM and would like to get this to work either with a kernel driver or custom module. Not really sure where to begin...Haven't built my own kernel or written an actual kernel driver in years but I would love to jump into some android dev with finding a solution to this.

[Magisk] AOSP dual speaker mod - Enable 24 bit output for PowerAmp on PIE

As i see many people flashing the old oreo stuff from Whiskey on AOSP which result in many bug, i decided to make a module to enable dual speaker mod, pseudo-HIM mode, and Gcam - stereo recording mod on AOSP
Feature:
+ pseudo-HIM mode, should make sound better and DAC toggle work
+ Stereo recording
+ Dual speaker - no mic breaking
+ I still attach the Poweramp 24 bit mod in attached file
Note:
+ Not working with ainur or narsil or any mixer path editing mod
+ Can work together with the Poweramp 24 bit mod attached
+ May have some unknown bug, report if you have any
For old OP:
Hello everyone
After a bit of work, me and @legacyeah manage to bring the great Legacy Audio Mod by @Rizal Lovins, in the form of a Magisk Module for quick installing and removing. We also manged to fix some bug found in the original audio mod.​
Features:
* 24 bit output on poweramp
* enable 384 khz resampling
* Working audio recording in video
*Based on and improve upon Rizal Lovins Legacy Audio Mod on XDA[/COLOR][/COLOR]
Notes: DVC in poweramp is bugged so DVC only work with 192, 96,48,44.1 khz resampling rate. Other resampling rate will need DVC disabled
*IMO sound quality is better compare to stock pie, it feel the same as stock LG sound quality*
Confirmed working on Havoc 0402 + Ainur with no other Audio mod or AML , other rom and compatibility with other audio mod need more tester
How to install:
1. On an AOSP Pie rom
2. Have Magisk working (if you dont know what magisk is and how to install it, search Google)
3. Flash the provided zip through TWRP or Magisk manager (Magisk manager may has bugs causing the zip not flashable)
4. Reboot
5. Enjoy ! (Music player may need further setting for 24 bit output)​
Note 2: If you find any bug, please feel free to report but please remember if you use this mod with other sound mod (like Viper 4 Android, DTS..) the bug will be noted but no promise for it to be fixed
Credit goes to:
@legacyeah for mic recording bug fix
@Rizal Lovins for the original mod
@SGCMarkus for providing AOSP for our device
And all the testers on telegram group
Update:
*18/2/19: add mod option to force enable HIM ( will cause sound distortion on normal headphone- dont complain)
*23/2/19: 24 bit mod HIM is now a separate module, you can install both module and enable one of your choice
*10/3/19: add 24 bit mod Dual speaker mod. Courtesy of @Dante63. Also cleaning up unnecessary file.
*6/4/19: With new device tree, AOSP now have working 24 bit output by default and HIM mode as well as DAC filter and sound preset working (with Ainur), those mod are depreciated. However, PowerAmp still need a mod to enable 24 bit output. Hence thread is updated with the necessary mod
*3/7/19: Add Pseudo HIM mod, dualspeaker mod, stereo recording.
I noticed that when i take any video from my device after installing this that voice is so much low when i play these videos on my device
Ziad Ajam said:
I noticed that when i take any video from my device after installing this that voice is so much low when i play these videos on my device
Click to expand...
Click to collapse
Low volume on video recording has been mentioned quite a long time on AOSP Pie. Are you sure it happend after flashing this mod. if so please specify: which rom, which camera app and which sound mod did you use?
Thanks man it works well with my v300s stock rom . thumbs up
Mrxyzl said:
Low volume on video recording has been mentioned quite a long time on AOSP Pie. Are you sure it happend after flashing this mod. if so please specify: which rom, which camera app and which sound mod did you use?
Click to expand...
Click to collapse
Actually audio recording was off when i use Gcam but was working well in other apps like snapchat and instagram. Now it works in every app but the recording voice is so weak.
---------- Post added at 06:31 PM ---------- Previous post was at 06:30 PM ----------
Ziad Ajam said:
Actually audio recording was off when i use Gcam but was working well in other apps like snapchat and instagram. Now it works in every app but the recording voice is so weak.
Click to expand...
Click to collapse
Android Pie Lineage OS 16
Ziad Ajam said:
Actually audio recording was off when i use Gcam but was working well in other apps like snapchat and instagram. Now it works in every app but the recording voice is so weak.
---------- Post added at 06:31 PM ---------- Previous post was at 06:30 PM ----------
Android Pie Lineage OS 16
Click to expand...
Click to collapse
So now all apps are having low volume recording or only the Gcam?
I wonder why this would happen because AOSP had low volume recording issue before.
Sent from my LG-H930DS using Tapatalk
Thread update with normal, high impedance mode and dual speaker mode
Working Very perfect in my LG US998 With pie DotOs and Dolby Digital Plus Mod.
No problems work good
So the dual speaker version has working mic?
Also, can you make a dual speaker+him version?
mark20120 said:
So the dual speaker version has working mic?
Also, can you make a dual speaker+him version?
Click to expand...
Click to collapse
I don't see why dual speaker don't have a working Mic.
I'll make one this weekend
It Works!
Mrxyzl, thank you very much. Speaker mod works fine. It would be great if you create a stereo mic mod for PIE camera. It's the only thing I miss in custom PIE roms. Thanks again
Stereo mod with HIM would be perfect.
Thread updated according to changes in new device tree. Add 24 bit mod enable for PowerAmp (only for those who use PowerAMP) other player like neutron and UAPP no need this mod
Mod no longer works after Poweramp v3 build 829 update. Running onHavoc os 2.5 may 20th update for LG V30 H930
Klimon5 said:
Mod no longer works after Poweramp v3 build 829 update. Running onHavoc os 2.5 may 20th update for LG V30 H930
Click to expand...
Click to collapse
thanks. i'll see what i can do this weekend
Edit: something is wrong on your side. mine work perfectly, btw need to enable DVC in order for 24 bit to work
Mrxyzl said:
thanks. i'll see what i can do this weekend
Edit: something is wrong on your side. mine work perfectly, btw need to enable DVC in order for 24 bit to work
Click to expand...
Click to collapse
I fiddled around with some settings. I fixed it. I have been using the 384kHz option with DVC disabled which works but sometimes I end up with the song skipping. I switched it to 192kHz with DVC enabled and that seems to resolve any issues I have. Why are the higher kHz options available if they don't work well or at all? Is it related to the way this mod is set up or how Poweramp is setup?
Klimon5 said:
I fiddled around with some settings. I fixed it. I have been using the 384kHz option with DVC disabled which works but sometimes I end up with the song skipping. I switched it to 192kHz with DVC enabled and that seems to resolve any issues I have. Why are the higher kHz options available if they don't work well or at all? Is it related to the way this mod is set up or how Poweramp is setup?
Click to expand...
Click to collapse
From my experience on stock, 384KHz drops it to 16bit and stops DTS from working.
Sent from my LG-H932 using XDA Labs
Found a way to make GCam record stereo audio
SDevil454000 said:
Found a way to make GCam record stereo audio
Click to expand...
Click to collapse
Much appreciated
Mrxyzl said:
Much appreciated
Click to expand...
Click to collapse
Updated stereo. Sound recording is louder and better quality.

How To Guide [ROOT] Realme GT2 Audio recording quality mod (magisk module)

I've made a mod to improve the audio quality in videos recorded with the camera. For me, it sounds much better than stock. If you try it, let me know what you think.
Installing it requires root and magisk:
1. Download GT2RecQualityMod[version].zip on the phone,
2. Open magisk,
3. Go to modules,
4. Click "install from storage",
5. Choose the file,
6. Reboot,
7. Test with stock camera.
This is my first attempt and it's tested only on my Realme GT2 (RMX3311/GDPR), Android 13 firmware C.10 and C.12, and with just the apps I have on my phone. If some apps don't work or the audio sounds like without the mod, please let me know.
Latest versions:
----------- GT2RecQualityMod1.2.zip -----------
- Updated recording profiles used by the Recorder app with improved loudness and clarity
- The rest is the same as in v1.1
----------- GT2RecQualityMod1.1.zip -----------
- Based on lvimfs (audio parameters like NS, EQ, Compresor etc.), with manual tuning of parameters in /odm/etc/lvimfs_params/LVIMFS_Parameter_ID4_MIC_Cam.txt
- I've disabled some audio processors like EQ's, Compressor, Limiter - that are not configured correctly
- Activated Wind Noise Suppression - and it works amazing! Tested by blowing into the mic )
----------- GT2RecQualityMod1.zip -----------
- Based on raw mic quality, it disables lvimfs (audio parameters like NS, EQ, Compresor etc.)
To Do: get rid of white/static noise without losing volume
Thanks for sharing, it's only replacing mixer_paths.xml and audio_platform_info.xml, right?
And a question wizard:
Would it be possible to copy the parameters or files from a custom rom for GT2 e.g. PixelOS, if that has good audio recording, or would it f*k something rom/device specific up?
Here are backups from my GT2 - RMX3311_11.C.10_EU_202303171905 if anyone needs, in /system/vendor/etc
Stock Camera got louder, but introduced noise.
Your Gcam Mod sounds the best, it's a bit quieter but 0 noise.
To adjust the volumes (mic sensitivity) you can edit mixer_paths.xml from the zip file. Search "handset-stereo-dmic-switch" and modify the marked values from below. Reinstall the module and reboot.
or
The working xml files are in /odm/etc those from system/vendor are not used by android anymore. You can edit them directly, after installing the Magisk module.
If you like to try the xml files from a custom rom (GT2 specific) you can replace mixer_paths.xml and audio_platform_info.xml located in /data/adb/modules/GT2RecQualityMod/odm-files/ and restart. files from odm-files are linked (mirrored) with those from /odm/etc
<!-- Lucian: here is the configuration set for camera apps. -->
<path name="handset-stereo-dmic-switch">
<!-- Lucian: added some options to play with volumes -->
<ctl name="TX_DEC1 Volume" value="84" />
<ctl name="TX_DEC2 Volume" value="84" />
...
...
...
<!-- Lucian: this also affect the volumes -->
<ctl name="ADC1 Volume" value="18" />
<ctl name="ADC4 Volume" va lue="18" />
</path>
Will do, i have tried the PixelOS ones, to save some time - the result is pretty much the same, louder with introduction of noise.
/here:
Can you attach those from PixelOS? I'll like to take a look
New release: GT2RecQualityMod1.1.zip
based on tuning the parameters of
/odm/etc/lvimfs_params/LVIMFS_Parameter_ID4_MIC_Cam.txt
- added and configured wind noise suppression / canceling
There are a lot of options in there, but not documented anywhere. I think the files are generated by "Qualcomm audio calibration tool" that requires license...
Qualcomm did something amazing with lvimfs_params, that allows the developer to tune every aspect of audio recording but Realme developers didn't care to do something good with this technology
If someone would like to contribute to the improvement of the audio quality, please give it a try! If we could remove the static noise it will be awesome, I think modifying the EQ to lower the static noise frequencies will help.
Regarding lvimfs_params, what I've learned so far:
lines containing "Operating Mode"
enables/disables that feature, like
0 // LVAC_LVAC_InputEq_OperatingMode disables the input equalizer, 1 enables it;
the following lines containing _InputEq_ are parameters like gain, band, frequency etc. that changes the aspects of recording.
There is no documentation, is just trials.
For changes to apply a reboot is required, maybe restarting service will be faster, but I don't know which one...
Have fun!
Have a much better sound obviously! I see one user did bitrate up mod, could you merge your mode plus 320kbps modification. Thank you!
Link
It is on my list, it won't improve much of the quality still. Now I'm more preoccupied on reducing the static noise. It will be included in the next release.
New release:
GT2RecQualityMod1.2.zip
- Updated recording profiles used by the Recorder app with improved loudness and clarity
- The rest is the same as in v1.1
Could not find a way to change the audio bitrate, if someone knows what file is responsible please help, I've tested all media_profiles(_V1_0).xml that I've found and none of them worked...
I played around with trying to get the Bitrate up but just managed to destroy Video Recording, so just as a pointer in my case only changing the Bitrates in the various recording <EncoderProfiles> in "media_profiles.xml" did not work.
I want to report some strange behavior. I face the problem with this mod on some applications. First, I'm on RUI C12 EU, with stock camera, I recorded three videos in a row and all of them have broken audio, the issue is feel like microphone have gain boost +30db sound was capped and distorted. The second app is element(chat/voice) when i try to record voice face again same problem. I will attach some samples to understand better.
When I disable the mod the issue still presents, only when remove the mod audio is stock/"fine".
@b0nb0n3v Something is wrong, but I don't know what... Do you have other magisk modules installed that could change mixer_paths.xml or lvimfs_params? Maybe they are conflicting.
I've attached a sample of how it sounds on my device. Stock camera, mod v1.2:
wizard8400 said:
@b0nb0n3v Something is wrong, but I don't know what... Do you have other magisk modules installed that could change mixer_paths.xml or lvimfs_params? Maybe they are conflicting.
I've attached a sample of how it sounds on my device. Stock camera, mod v1.2:
Click to expand...
Click to collapse
I have andreno gpu drivers and systemless host in the past i tried mixer_paths.xml for 320kbps mod but with no difference I decide to remove it. Could this mod couse this bug, it's removed long time ago? The problem is always when the sound/speech is lound on quiet place or low sound recording is fine. Tia
b0nb0n3v said:
I have andreno gpu drivers and systemless host in the past i tried mixer_paths.xml for 320kbps mod but with no difference I decide to remove it. Could this mod couse this bug, it's removed long time ago? The problem is always when the sound/speech is lound on quiet place or low sound recording is fine. Tia
Click to expand...
Click to collapse
Test if my mixer_paths backup a in the top of the thread makes a difference, if you don't have one yourself. Maybe the change stayed?
smashda said:
Test if my mixer_paths backup a in the top of the thread makes a difference, if you don't have one yourself. Maybe the change stayed?
Click to expand...
Click to collapse
Thank you I check the files and there are stock, my be I'm the private case with this "bug"...

Categories

Resources