Audio Modding on the LG K20 Plus - LG K20 Plus Questions & Answers

Hello guys, so the story is I just loaded the Viper4Android Magisk Module onto my K20 Plus, and it sounds really neat. However, I now want to try out A.R.I.S.E Sound Systems on this device, and I am wondering what's the best configuration I could perhaps use on A.R.I.S.E for this device.

use this insead https://forum.xda-developers.com/android/software/soundmod-ainur-audio-t3450516
ARISE has a lot of useless bloat.

I am using Magisk with the following modules and it sounds amazing...practically on par with my old OnePlus 5T.
-03/17 release of Ainur Sauron (which is the last version to allow qualcomm vendor patching)
-V4A by ahrion
-Audio Compatibility Patch (to allow processing with streaming apps)
-Audio Modification Library
All of these are created by the same guys and designed to be used together. Flash them in the order listed and you will be in business and Viper will process for everything.

Related

[TASP] The Absolute Sound Project : Making Love Not War - BETA 13b [StereoFX BETA 2]

[TASP] The Absolute Sound Project : Making Love Not War - BETA 13b [StereoFX BETA 2]
Moderator edit:
Forum Rule 12. Using the work of others.
If you are developing something that is based on the work of another Member, you MUST first seek their permission and you must give credit to the member whose work you used. If a dispute occurs about who developed / created a piece of work, first try to settle the matter by private message and NOT in open forum. If this fails, you may then contact a Moderator and provide clear evidence that the work was created by you.
Convincing evidence will result in the copied work being removed. If there is no clear evidence that it was you who created the work, then in the spirit of sharing, all work will remain posted on the forums.
As an addition, developers have the right to hold exclusivity over their work for as long as it is deemed necessary by that developer. However, if the work is claimed as exclusive, it must remain as such. No selective sharing will be allowed (ie, allowing certain people to use it and not others). If the developer decides to start sharing the work with others, the work automatically becomes available for all to use, albeit with the relevant credit displayed.
When permission has already been given, unless there is a very valid reason, it cannot be revoked (same applies to major updates on the work). Under that same premise, permissions cannot be denied unless the work is exclusive or under extreme circumstances.
In plain English: If you want to keep your work exclusive, go for it. However, if you are going to share your work, do it fairly.
These rules apply to all software posted on XDA (including but not limited to ROMs, RUUs, apps, games, kernels, themes, icons, etc) unless that software comes with a license that waives these rules.
Click to expand...
Click to collapse
VISION:
The Absolute Sound Project is the audiophile's all-in-one one stop shop audio enhancement for the rooted Android OS.
The purpose of TASP is to give everyone the best sound experience possible on Android. There are other mods that do it just as good, if not better. The goal of TASP is to unite the end-user so flashing six different sound modifications becomes a thing of the past. TASP utilizes parts of many different audio enhancing modifications out to create the best experience for music on the Android OS, while adding its own personal touch to increase the overall quality of the VISION.
This mod is for the people, by the people. If you wish TASP to not use your work tell/yell at me via private message in a civil manner (we are adults) and all traces of what has been utilized for TASP from your modification will be removed. If not then you are probably already in the credits. If you are forgotten then say something. No big deal.
We are all adults. TASP wasn't created for myself, but for everyone else like myself who flashed mods like eXtremebeats, EOF EX, PureAudio, Project ERA, LolliViper, HK, HTK, etc. No one wants to flash eight different mods.
TASP is universal. Be together, not the same. Making love, not war.
- It is not recommended to use any other sound mod
- This mod deletes any previous versions of ViPER4Android, AudioFX, DSPManager, and MusicFX and replaces it with a custom V4À specifically catored to Material Design as well as android 5.0.2 users (see credits)
- 5.0.2 friendly but should work on KK
- Includes Dolby Surround & DTS Processing
- xLOUD, Harman Kardon, Beats, sforce all included
- [Alpha WIP] Creates a stereo effect for your device speakers (ie your galaxy s5 will play sound on your front earpiece and back speaker). I removed this because of the bugs
- Clean flash of your ROM with no other sound mods is recommended, especially since this is beta phase. If you have another mod installed I will ignore your bug reports
This mod is in BETA. I'm in the debugging process for several devices. If you're going to test this mod do not have other sound mods installed and be willing to support the debugging process (logs, tests, etc). Please support me with your device name and manufacturer and your experience(s) with flashing my mod (after a clean install of your rom).
HTC/Sony/TW devices are currently a hit or miss. Some find it works, other do not. Feel free to try it out though. AOSP/CM should work like a charm.
INSTALLATION INSTRUCTIONS:
1). Clean install your rom with no other sound mods installed. You can dirty flash your rom, but clean install (recommend) is always better (getting rid of orphan data)
2). If you're going to install another sound mod, do so before you flash mine (not recommended)
3.) Your phone needs to be rooted and SuperSU needs to be installed
4). Install the latest version of BusyBox
5). TWRP is the best recovery out there and is always recommended to be used rather than Philz/CWM/etc. Some users are experiencing trouble with errors (usually permissions) during the flashing process, this should theoretically fix that issue
6). If you're using 5.0+: download Selinux Mode Changer and set Selinux mode to permissive
7). If If you're using 5.0+: go into your rom's Developer Options and uncheck "Use NuPlayer". Some users experience compatibility issues with NuPlayer not working with V4A/Dolby, others do not. Better safe than sorry
8). Flash [TASP™] The Absolute Sound Project™ : Making Love Not War - BETA
9). Don't forget to WIPE! (cache/dalvik)
10). Reboot and enjoy the love making to your ears
NOTE: If Dolby or V4A don't work for whatever reason, flash the compatibility patch below as a final measure.
————————————
About V4A Compatibility Patch:
Flash the patch only if V4A/Dolby effects are installed, but not processing in some media players such as Spotify or Pandora.
V4A COMPATIBILITY PATCH CHANGELOG: DOWNLOAD
19/02/2015 - BETA 3:
- Better compatibility
Code:
[COLOR="red"][B]16/02/2015 - BETA 2:[/B][/COLOR]
- FC/Freezing fixes
- Enhanced compatibility
[COLOR="red"][B]12/02/2015 - BETA 1:[/B][/COLOR]
- Initial BETA Release
————————————
About StereoFX:
Utilizes both your phone's internal front and back speakers to create a stereo effect while also modifying internal/external speaker, Bluetooth, USB, headphones, HDMI, recording, mic, and call volume parameters.
STEREO FX CHANGELOG: DOWNLOAD
16/02/2015 - BETA 2:
- In-call speaker phone "no sound" fixed. Should be working as intended now
Code:
[COLOR="red"][B]15/02/2015 - BETA 1:[/B][/COLOR]
- Initial BETA Release
- Samsung Galaxy S5 and Nexus 5 devices confirmed compatibility
- HTC and LG phones are unsupported with this release, but will be supported in the future
————————————
About The Absolute Sound Project:
The audiophile's all-in-one audio enhancement that includes a custom-tailored Material Design version of ViPER4Android (latest) and Dolby Digital Plus equalizers.
THE ABSOLUTE SOUND PROJECT CHANGELOG: DOWNLOAD
18/02/2015 - BETA 13b:
- ViPER4Android XHiFi - (to force 32-bit audio) - is now included. I highly recommend using this at default settings,with Audio Reconstruction, and "Vocal Booster" FIREqualizer settings enabled, especially of you like your clarity/bass
- Added V4A/XHiFi persist script after dirty ROM flash
- Compatibility fixes
- Added init.d script to force selinix permissive
- Upgraded, replaced, removed, or downgraded broken libs
- Added PON-3 libs/effects
- SRS, sound image, vpt, DTS, and SFORCE changes
- Kept the "bass heavy libs" the same so don't say your bass punch is reduced
- Several dynamic behind the scene changes that I can't remember at this moment
Code:
[COLOR="red"][B]15/02/2015 - BETA 12:[/B][/COLOR]
- Changed alsa driver (no longer using [user=4388232]@ZeroInfinity[/user] alsa upon his request)
- Changed Dolby config upon request of [user=4388232]@ZeroInfinity[/user]
- Improved compatibility
- Updated all stock ROM effect libs with newer versions
- Added back in asound
- Less treble, more clarity
[COLOR="red"][B]14/02/2015 - BETA 11:[/B][/COLOR]
- New V4A 2.3.4.0 (LolliViper] with Material Design
- New effects such as normalizer and updated libs/effects such as VPT
- SRS, sforce, and alsa backend files
- HTC compatibility fixes
- Sony effect improvements
[COLOR="red"][B]12/02/2015 - BETA 10:[/B][/COLOR]
- Reverted a few SRS libs back to BETA 7 version because of loss of bass "punch"
[COLOR="red"][B]11/02/2015 - BETA 9:[/B][/COLOR]
- fixed v4a build prop lines missing
- updated spectrum libs
- added, changed, and updated more libs
- much greater difference in sound quality
[COLOR="red"][B]11/02/2015 - BETA 8:[/B][/COLOR]
- should fix HTC bootloop
- newer maxxaudiolibs
- build prop typo fixes, changes, and additions
- fixed mic not working unless in a call
- update binary script adjustments
- SRS, Sony, and sforce changes
- overall sound improvements
[COLOR="red"][B]07/02/2015 - BETA 7b:[/B][/COLOR]
- minor update, hence the "b": mostly build prop typo fixes and changes
[COLOR="red"][B]06/02/2015 - BETA 7:[/B][/COLOR]
- compatibility update: fixed the "No sim" and not being able to connect to the internet on some devices
- removed the pon3 libs that conflicted with installing the V4A drivers normally
- a few minor fixes and changes
[COLOR="red"][B]04/02/2015 - BETA 6:[/B][/COLOR]
- reverted a good amount of changes that were in BETA 5 and kept the good changes
- removed audio_policy.conf for the time being
- added updater script dolby permission lines
- updated or replaced outdated libs with the newest available
- re-added a few libs
- reverted audio_effects so bass is deep like BETA 3 & 4 with mid-high clarity range
- dolby should no longer force close. If it force closes you should still have the effects, it's just a symptom of different roms/devices/variants
[COLOR="red"][B]31/01/2015 - BETA 5:[/B][/COLOR]
- improved touchwiz, slimkat, cm11, and more HTC sense compatibility
- changed updater script a little.
- reverted v4a build prop changes
- updated or replaced some libs
[COLOR="red"][B]31/01/2015 - BETA 4:[/B][/COLOR]
- changed and restructured a few audio effects
- removed sony hearing protection audio effect
- added Samsung Touchwiz 4.4/5.0+ compatibility
- testing custom audio_policy.conf and v4a build prop tweaks. I need feedback on this one. If you don't have audio effects on v4a try setting all the v4a Tweaks in build prop to "false". Report back to me if you have to do this. This should fix the problem people have had in the past where no matter what they do, they can't get v4a to work normally with all media players
- updated sound alive libs
- other small tweaks
- cleaned up some unused libs
[COLOR="red"][B]29/01/2015 - BETA 3:[/B][/COLOR]
- sounds better than it has ever sounded thus far. Deep and high bass sounds good. Tested acoustic music, dance, electronic, dupstep, metal, rock. All sound more amazing than previous versions
- updated/added effects
- removed sonicmax effect that resulted in unnecessary sound amplification (thanks [user=5648292]@aki_007[/user])
- more srs tweaks and added some additional srs effects
- other changes/fixes
- more compatibility fixes for some HTC Motorola, and Sony devices (hopefully)
- added asound back in (test)
[COLOR="red"][B]28/01/2015 - BETA 2:[/B][/COLOR]
- Added a few Build.prop entries as well as changed existing ones
- tweaked srs config
- other changes/fixes
- compatibility fixes for some HTC and Sony devices (hopefully)
[COLOR="red"][B]28/01/2015 - BETA 1:[/B][/COLOR]
- Initial BETA Release
————————————
I recommend a clean rom install (preferred) but a dirty rom flash should do it(to get rid of deleted files).
ALSO if you end up not getting sound, uninstall the v4a audio driver, reboot, reinstall driver, and then reboot again and it will fix the nosound/no effect issue.
CREDITS (WIP):
@viper520, @zhuhang - Viper4Android and IRS files
@Ben Feutrill - Parts of eXtremebeats
@mrchezco1995 Parts of PON-3
@Hid3rs, @//.dax, @AndrasLOHF - Parts of LolliViper (ViPER4Android 2.3.4.0 Material Design w/ flat icon) and stereo mixer_paths (groundwork)
@kien_vip - Parts of HTK Audio Engine @Vinardo_ZzZ 2000 - Parts of Elements of Fidelity EX/ASDPE and amazing IRS files
@dryla - Parts of Beast Audio Mod
@scrosler - Parts of Harman / Kardon Sound Mod
@Ergo Proxy - Parts of OPO Sound Mod
@ibanez7 - Parts of Xperia Z3 Walkman Mod @ricardopvz - OPO MaxxAudio Libs
@Joe0Bloggs[/MENTION] - Phenomenal V4A IRS files
@aznrice2k4, @ZeroInfinity - samplerate.sh
RECOGNIZED CONTRIBUTORS:
@aki_007, @smeejaytee, @jmxc23, @churapa
_________________________
[TASP] The Absolute Sound Project : Making Love Not War - BETA [StereoFX BETA]​
Sounds interesting
After installing the last version I have same situation with my sound exactly I have no sound at all and phone gets laggy as well as I get FC with media storage
The mod works fine with the exception of the Dolby app. Also the music stops when I try to access the Dolby app. Overall most of the enhancements can be heard it is just the Dolby app probably due to the visualizer.
Can somebody test the difference between this mod and eXtremeBeats (they should both use the same V4A profile and headset)?
What are the differences between this mod and eXtremeBeats?
Retracted! unfortunately after I reboot I got a bootloop, tried dirty flashing my Rom but it still wouldn't boot without fc's from all over the place, so unfortunately this is not working for HTC m8
Sent from my HTC One_M8 using Tapatalk
jmxc23 said:
The mod works fine with the exception of the Dolby app. Also the music stops when I try to access the Dolby app. Overall most of the enhancements can be heard it is just the Dolby app probably due to the visualizer.
Click to expand...
Click to collapse
Have you tried once with putting dolby_ds.jar in your rom zip framework folder and fresh install of your rom..
The dolby doesn't work because when you install it with some mod.zip the android system tried to verify the signature which is missing in the framework file although Vinardo had signed it ..
but when you fresh install the rom with dolby in it the android skips its verification as the signature verfification mechanism isn't loaded yet and will load only after the rom boots up and So , you get to hide the dolby from that and make it work...
Its the most successful method till now...Try once and if it still doesn't work then you can restore your backup anyways.
The latest dolby deserves to be tried as it doesn't boosts much audio but adds a nice surround and a little bass but the surround is very good...Goes well with V4A and DCT
berda77 said:
After installing the last version I have same situation with my sound exactly I have no sound at all and phone gets laggy as well as I get FC with media storage
Click to expand...
Click to collapse
The best way to debug the situation is telling my your device, the rom you're currently running, give me a logcat of your bootloop, and it would be a good idea to compare the files in my mod vs the default files in your rom. See what my mod replaces. Make sure you're not running any other sound MOD. It WILL cause conflict.
FPSUsername said:
Can somebody test the difference between this mod and eXtremeBeats (they should both use the same V4A profile and headset)?
What are the differences between this mod and eXtremeBeats?
Click to expand...
Click to collapse
This combines eXtremeBeats with other sound mods, while also adding my own personal love and touch. So ebs is already included. . .
aki_007 said:
Have you tried once with putting dolby_ds.jar in your rom zip framework folder and fresh install of your rom..
The dolby doesn't work because when you install it with some mod.zip the android system tried to verify the signature which is missing in the framework file although Vinardo had signed it ..
but when you fresh install the rom with dolby in it the android skips its verification as the signature verfification mechanism isn't loaded yet and will load only after the rom boots up and So , you get to hide the dolby from that and make it work...
Its the most successful method till now...Try once and if it still doesn't work then you can restore your backup anyways.
The latest dolby deserves to be tried as it doesn't boosts much audio but adds a nice surround and a little bass but the surround is very good...Goes well with V4A and DCT
Click to expand...
Click to collapse
There's no other way to fix the problem? I haven't experienced this as of yet...
As for the mod. Is it working for you?
Simply the bsst. Flashing over TEST zip with blisspop
ahrion said:
There's no other way to fix the problem? I haven't experienced this as of yet...
As for the mod. Is it working for you?
Click to expand...
Click to collapse
NO for your mod and I can't find out what's wrong with it , although you and me have almost same files and same lines of codes..
Yes for dolby ... as @jmxc23 is using LOLLIPOP if he can disable signature verfifcation which I couldn't then it will work flawlessly....
berryman13 said:
Simply the bsst. Flashing over TEST zip with blisspop
Click to expand...
Click to collapse
You should dirty flash your rom first. I use BlissPop on my s5 which is why you don't have issues with it lol. . I changed a lot though.
Sometimes when you dirty flash all seems well... And then you clean flash and every is so much different.
aki_007 said:
NO for your mod and I can't find out what's wrong with it , although you and me have almost same files and same lines of codes..
Yes for dolby ... as @jmxc23 is using LOLLIPOP if he can disable signature verfifcation which I couldn't then it will work flawlessly....
Click to expand...
Click to collapse
I'm using lollipop as well...
I haven't taken a look at your mod yet. Link?
What exactly is going on? No sound? Bootloop? The best way I found to debug the situations besides a logcat is go through each and every file in TASP B1 and compare it to your rom files that my mod replaces. Then report back here with the files my mod replaced in your rom. Usually that does the trick.
ahrion said:
You should dirty flash your rom first. I use BlissPop on my s5 which is why you don't have issues with it lol. . I changed a lot though.
Sometimes when you dirty flash all seems well... And then you clean flash and every is so much different.
Click to expand...
Click to collapse
Ye mate I know. I checked out the zjp and its scope is huge. Haven't flashed anything yet but I do generally always dirty(ish) flash my ROM, gapps and kernel.
My device is a D800. ATT variant of the g2 and generally the second to best variant of the device besides ofc international which is D802 (most dev support).
I take it you run bliss 1.9 (released yesterday for me). I will clean flash it with micro gapps and the most solid kernel available for my phone, render kernel. Do you want me to flash it on my otherwise stock and rooted NVIDIA Shield? I'm glad to test as much as will benefit you.
berryman13 said:
Ye mate I know. I checked out the zjp and its scope is huge. Haven't flashed anything yet but I do generally always dirty(ish) flash my ROM, gapps and kernel.
My device is a D800. ATT variant of the g2 and generally the second to best variant of the device besides ofc international which is D802 (most dev support).
I take it you run bliss 1.9 (released yesterday for me). I will clean flash it with micro gapps and the most solid kernel available for my phone, render kernel. Do you want me to flash it on my otherwise stock and rooted NVIDIA Shield? I'm glad to test as much as will benefit you.
Click to expand...
Click to collapse
You can try to nshield. I know nothing of the tegra processor or software. It doesn't hurt to try.
How it the mod sounding for you? Bass, miss, clarity, lows, highs?
Great mod, however I can't get Dolby to work. It flashes and I am able to launch the application. However when it launches there is no FC it just automatically closes.
Here's a list that was pulled when it happened: https://www.dropbox.com/s/s3collkoglrrtxm/Log_2015-01-28_12-24-25.txt?dl=0
Device: Nexus 5
ROM: SlimLP
Riddlah said:
Great mod, however I can't get Dolby to work. It flashes and I am able to launch the application. However when it launches there is no FC it just automatically closes.
Here's a list that was pulled when it happened: https://www.dropbox.com/s/s3collkoglrrtxm/Log_2015-01-28_12-24-25.txt?dl=0
Device: Nexus 5
ROM: SlimLP
Click to expand...
Click to collapse
Are you running KK? This seeks to be KK exclusive.
ahrion said:
Are you running KK? This seeks to be KK exclusive.
Click to expand...
Click to collapse
No I am on Lollipop 5.0.2
aki_007 said:
NO for your mod and I can't find out what's wrong with it , although you and me have almost same files and same lines of codes..
Yes for dolby ... as @jmxc23 is using LOLLIPOP if he can disable signature verfifcation which I couldn't then it will work flawlessly....
Click to expand...
Click to collapse
It doesn't work someone will have to make it compatible with lollipop for it to work. People already made v4a compatible with lollipop albeit with some issues.
jmxc23 said:
It doesn't work someone will have to make it compatible with lollipop for it to work. People already made v4a compatible with lollipop albeit with some issues.
Click to expand...
Click to collapse
I'm running LP and I'm not having any issues. Try turning of Nuplayer in developer options of your rom.

[AINUR AUDIO] SAURON MK III [paused] | NARSIL MK I [upd 09.09.2021]

{
"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"
}
[AINUR AUDIO] (named after John R.R Tolkien mythology) mod was conceived on 12th January 2016 at Russian 4pda forum, with an idea to create the ultimate universal tuning solution, that can help people get more from their devices in terms of audio capabilities. Ever since that time we have been aiming at achieving new heights & providing you with a set of different mods (now archived): Pandora as universal SW optimizer, Nero as coloration fx remover, Kronos & Atlant as specific variety of device dependent mods with heavy tuning for different qualcomm cpu's. This allowed us to experiment & to find limitations of what can be tuned in terms of software & hardware within different smartphone configurations.
We were also first to successfully implement hex disassembling method for proper effects porting. Further hex investigations showed that other audio "mods" contained nothing but huge amounts of bloat files, that needlessly took up massive amounts of space on system partitions. Our disagreement with the developers of said mods at times resembled a genuine "war". The discovery of our disassembling method, proper implementation of basic mods & port addons (along with quite a bit of patience) brought you our best solution yet, to help optimize sound on your android device and reach the desired high level of quality, regardless of device manufacturer or cpu.
To go further we now starting a new era of audio mods with a brand new SAURON modification to bring you best sound ever in the audio modding history.
From Mordor
With love
Press:
Head-Fi
Contact & Socials
Official website
Telegram chat (brace yourselves - memes ahead!)
VK group
Facebook group
Discord group
Reddit discussion
ADDITIONAL INFO:
Android audio mods mythbusted
FAQ
[Ainur Audio] team
@UltraM8 /[email protected], @stake263, @red_naxella /[email protected], @SashaSmile, @doma999, @Mostafa Wael, @Zackptg5, @defcomg, @ahrion, @AlienCreature7, @LazerL0rd, @james3460297, @Skrem339
Like our work?
Support us!
Paypal
News
New years greetings & Sauron MK II launch
Sauron MK III preparations. Seeking community help!
[Ainur SAURON] MK III
Named after villain from Lord of the Rings mythology - SAURON, this mod automatically detects your device specs (soc/android sdk/rom/oem/proprietary stuff), and performs all of the possible audio patches that might boost sound. Sauron is system-wide modification - all of the patches are aimed to rework system components for androids audio subsystem and should work for headphones/speaker/bt. There is no app/UI.​
Click to expand...
Click to collapse
MOD IS ON PAUSE, IS NOT UPDATED FOR LONG TIME AND WON'T BE ANYTIME SOON
Basic features:
- Android 5.0 - 9.0 support
- Unity installer by @ahrion and @Zackptg5
- Qualcomm/Exynos/MTK/Kirin/Rockchip/Spreadtum cpu's support
- ARM 32/64 bit support
- Android SFX blobs eplacements (musicfx & audiofx apps might no longer work)
- Cherry picked setprops
- Automatic su.d/init.d/addon.d detection
- Supported roots: Magisk 18+ /SuperSu/CMsu/PHH/LosSU/No root
- AML addons ready
- OTA surviving
Advanced features:
- Qualcomm codec mixer tunings
- Htc u11/u11+, m9, 10, m8 speaker amps patches and additions
- OnePlus 5/5T, Mi 8UD/EE, Mi a2. Pixel 1/XL, Pixel 2/XL, Pocophone speaker amp DSP modifications
- Forced Hexagon DTS Headphone:X module processing, mixer controls & custom config
- * DAC powered devices mixer edits:
- LG v20/30/30+/g6/g7
- LeEco x800/x900
- Nubia z11/z9/z9m
- Axon 7 (moved to custom kernel)
- Lenovo vibe X3
* Parameters forcing for DACs is achieved with mixer additions, thus either framework, or service apps can reset some values back to stock. Sorry, but it seems like device manufacturers doesen't want us to mess with these thing. There is a solution, but unfortunately it won't happen till probably next major version.
User determined features:
You can set these features with sauron_useroptions (UO) file, by placing it to the root of the internal storage. Installer will place the file there during the install, if it's not there already. After resetting values you have to reinstall Sauron each time you want to try/set something new. Some of the stuff there can break sound completely - there is no fix for that, you have to reset stuff back & don't use some of the features that breaks normal use of your device.
I've commented pretty every single thing there with all the info I know by this moment, make sure not to bother me with questions like "wut is dat XXXX feature for, dude?" please
- ACDB replacements
- Universal remover for compressor SFX
- Universal install for Fmas effect
- Qualcomm shoebox & audiosphere effects
- Qualcomm codec bitsize, impedance and discretization forcing
- Compander remover
- Aptx/hd libs, props & hexagon cappi libs install
- Reverb effects for PCM conversions
- Audio policy patching
- Codec power gating remover
- Qualcomm BT scrambler resamling
- Exynos codec resampling
- MTK gain setter
- MTK Impredance setter
- MTK high-pass filter remover
Installation:
!! Debugging !!​READ CAREFULLY​For an error during TWRP - get ainur_debug logs, that are generated to sdcard during install.
Sauron is located in sbin/.magisk/img /ainur_sauron , or sbin/.core/img /ainur_sauron for magisk - this is your starting point.
1. Make sure you don't have anything set in UO, before posting something doesn't work as intended. Check clean install (UO unset) in the first place.
2. For bootloop you'll need to provide ADB logs
3. For any bug after bootup (ie weird device behavior, sound loss, etc) - use matlog app to generate logs
ALL the wrong logs for your issues will be completely IGNORED
VERY IMPORTANT !
Study sauron_useroptions carefully - some combinations could lead to huge sound problems (as it's mentioned in the file), that WON'T be determined as issues. You have to find and you working combo on your own!
Click to expand...
Click to collapse
Installation
Magisk users with /dsp mounting error should flash with twrp!
MKIII archive - download and flash with TWRP/Magisk
Changelog:
Code:
MK III 12.08.2019
- Unity 4.4 update
MK III 27.05.2019
- Installer fixes
MK III 03.05.2019
- Unity 4.1 update
MK III 31.03.2019
- Unity 4.0 update
- magisk 19 support
- qualcomm 855 support
- various installer fixes
MK III 01.01.2019
- Fully reworked installer (unity & aml updated)
- Support for MTK/Kirin/Exynos mixers
- SFX blobs rebased (including new base for MTK/Kirin/Exynos)
- Reworked props
- New UO features:
- qualcomm acdb replacements, power gating disabling, bt scrambler resampling
- Exynos codec resampling
- MTK codec mixer edits: gain setter, impedance setter, high-pass filter remover
- Reworked UO features:
- Qualcomm codec bitsize & discretization forcements are deepen to support Hexagon DSP as well
- Reworked mixer edits for qualcomm powered devices
- Reworked kernel modules blobs & Hexagon dsp modules
- Further experiments with aptx/hd, including better support for Pie
- Experiments with speakers amplifiers DSPs: (Pixel 1/XL, Pixel 2/XL, Htc u11/11+/12/m9, Mi a2, Mi 8EE/UD, Oneplus 5, Pocophone)
MK II.II 19.06
- AML update & fix
MK II.II 13.06
- AML/Unity update
MK II.II 02.05
- UO detection critical fixes
MK II.II 01.05
- unity update
- various fixes
- UO updated
MK II.II 18.04
- installer fixes
MK II.II 15.04
- unity update
- minor edits & fixes
MK II.II 24.03
- audioserver fixes
- better Treble (Oreo & P) compatibility
- removed policy patches for better AML compatibility
MK II.II 22.03
- Op3/t & Op5/t fixes
- Minor Oreo edits
- Various minor edits
MK II.II 17.03
- Various fixes & edits
MK II.II 11.03
- Android P support
- Various fixes & edits
- Axon7 patches moved to kernel by Skrem339
- Sfx libs changes
- Htc m7-m9 rt5501 & 5506 jack amplifier patches (libs hex patched by UltraM8)
- Htc u11/u11+ speaker amp patches (beware, it blows :) )
- Pixel devices experimental amp patches (sailfish, marlin, taimen, walleye)
- Qualcomm RX HPH edits for HiFi mode
- Oreo aptx/hd, ldac added by LazerL0rd
- Fmas edits
- UO file edited
- Axon7 patches moved to kernel by Skrem339
MK II.I 26.02
- Unity 1.3 update
- Various fixes
- New UO
MK II.I 20.02
- Critical installer fixes
- Completely reworked core libs
MK II.I 07.02-08.02
- Unity installer
- Critical bug fixes
MK II.I 06.02
- SFX libs install logic patches
- Minor bug fixes
MK II 13.01
- aml 2.9
- got rid of hw dolby
MK II (beta 1 - stable) 31.12-01.01
- Revamped installer
- Unity/AML v2.8
- Added UO logic
- Rebased SFX libs
- Removed alsa
- HTC U11/U11+ speaker amplifiers patches
- HTC m9/m8/10 amplifier drivers additions (possibly reroute headphones path with tfa amp)
- Full Oreo (8.0+) support
- OP5/5T speaker amp drivers additions for tfa9890
- Added Qualcomm Shoebox 3d and Audiosphere audio effect libs, props & mixer controls
- Added Fmas effect libs & props
- Added UO controls for impedance, bitsize & discretization
- Added snap 820/21/35 Speaker boost & voltage edits from Oreo
- Added Hexagon DTS Headphone:X module, mixer switchers & controller config
- Added Hexagon Dolby modules & mixer switcher
- Added Qualcomm BT resampler (idk if it can even work)
- Reworked props + added some new found by hexing
- Set higher value for preallocated DMA memory buffer
- Added kernel modules for QC codec
- Added APTX/HD libs, props & hexagon cappi libs
MK I.IV.II
- Installer critical fixes
- magisk v13 support
- new sfx libs
MK I.IV.I
- Installer critical fixes
MK I.IV
- Installer critical fixes
- Added [user=4544860]@osm0sis[/user] busybox
MK I.III.I
- Installer fixes
MK I.III
- Installer fixes
- New libs base + SFX patches
- Qualcomm dac patches from older versions
- HTC patches from older versions
MK I.II
- Installer fixes
- SFX patches
MK I - I.I
- New libs base
- Survive Rom dirtyflashing
- Bug fixes
You are not allowed to use any parts of this mod in your own roms & mods!​
Ainur narsil [ mk i ]
NARSIL in Tolkien’s legendarium was the sword that defeated Sauron villain.
This Mod cleans android sfx from both stock and OEM effects as much as possible - delivering unbound sound the way hardware (internal codecs/dacs/amps) was meant to sound by manufacturer. It’s a system-wide modification - meaning it should affect general playback outputs: headphones/speaker/bt). There is no app/UI.
Click to expand...
Click to collapse
Basic features:
- Android 4.0 - Q support
- MMT-EX installer by @Zackptg5
- Supports most SOCs
- ARM 32/64 bit support
- Cherry picked setprops
- Automatic su.d/init.d/addon.d detection
- Supported roots: Magisk 18+ /SuperSu/CMsu/PHH/LosSU/No root
- AML addons ready
- OTA surviving
- Android SFX tract removal
Advanced features:
- Qualcomm/MTK/Exynos mixer patcher
- Speaker amps calibration replacements for some devices
- * DAC powered devices mixer edits:
- LG v20/30/30+/g6/g7/v40
- LeEco x800/x900
- Nubia z11/z9/z9m
- Axon 7 (moved to custom kernel)
- Lenovo vibe X3
* Parameters forcing for DACs is achieved with mixer additions, thus either framework, or service apps can reset some values back to stock. Sorry, but it seems like device manufacturers doesen't want us to mess with these thing. There is a solution, but unfortunately it won't happen till probably next major version.
User determined features:
You can set these features with narsil_useroptions (UO) file, by placing it to the root of the internal storage. Installer will place the file there during the install, if it's not there already. After resetting values you have to reinstall Narsil each time you want to try/set something new. Some of the stuff there can break sound completely - there is no fix for that, you have to reset stuff back & don't use some of the features that breaks normal use of your device.
- OEM sfx restorer (in case of bugs)
- ACDB replacements
- Qualcomm codec bitsize, impedance and discretization forcing
- Compander remover
- Audio policy patching
- Codec power gating remover
- Qualcomm BT scrambler resamling
- Exynos codec resampling
- MTK gain setter
- MTK Impredance setter
- MTK high-pass filter remover
Installation:
!! Debugging !!
READ CAREFULLY​For an error during TWRP - get ainur_debug logs, that are generated to sdcard during install.
Sauron is located in sbin/.magisk/img /ainur_sauron , or sbin/.core/img /ainur_sauron for magisk - this is your starting point.
1. Make sure you don't have anything set in UO, before posting something doesn't work as intended. Check clean install (UO unset) in the first place.
2. For bootloop you'll need to provide ADB logs
3. For any bug after bootup (ie weird device behavior, sound loss, etc) - use matlog app to generate logs
ALL the wrong logs for your issues will be completely IGNORED
VERY IMPORTANT !
Study narsil_useroptions carefully - some combinations could lead to huge sound problems (as it's mentioned in the file), that WON'T be determined as issues. You have to find and you working combo on your own!
Click to expand...
Click to collapse
Installation
Since 04.03 supports only magisk flashing
NARSIL MK I
download and flash with Magisk
Narsil is not yet added to magisk repo. Will do soon!
Changelog:
Code:
09.09.2021
- MMTEX canary magisk support
01.01.2021
- Installer fixes
- Realme fixes
09.04
- MMT-EX installer fixes
27.03
- MMT-EX installer support for magisk 20.4
04.03
- MMT-ex installer
- aml support update
MK I 27.05.2019
- Unity update
- Various compatibility/device specific fixes
MK I 27.05.2019
- Initial release
[Addons] ported audio effects & standalone DSPs
These are third-party effect ports & standalone DSPs which can be used on their own, or combined with Ainur mods.
To use multiple Ainur mods/addons magisk users have to install AML module from magisk repo
JamesDSP ->
DTS HPX & X Ultra ports->
Ciaomeme audio+ mod for several xiaomi devices->
Discontinued:
These are old addons that are no longer updated &/or upstreamed to new unity/aml.
Dolby->[/URL
Bang&Olufsen icepower port [URL="https://forum.xda-developers.com/showpost.php?p=70935959&postcount=1027"]->
Arkamys effect port ->
Dirac effect port ->
Fiio's V4A irs convolvers ->
KERNELS
Audio kernels, packed with various features​
Axon7
CAD Project by @Skrem339
This project was created to let you get full control over DAC:
1) /sys/module/snd_soc_ak4490/parameters/oversampling_freq
Sets DAC's oversampling frequency(default 768000(max))
2) /sys/module/snd_soc_ak4490/parameters/selected_filter
Sets DAC's filter:
1 slow
2 short delay sharp
3 sharp
4 short delay slow (default)
3) /sys/module/snd_soc_ak4490/parameters/superslow
Sets state of Supperslow filter:
0 off (default)
1 on
Downloads & Support
The ugly thruth about effects ported from other devices
Xda's sound mods history goes deep down in ages, but there is one particular myth that stays strongly. This myth is based off idea that we can port some external software effect from one device to another. That is completely wrong & most technologies CAN'T be ported.
Almost a year and a half i got my htc m8 drowned & I bought myself meizu m2 note. This device has the worst audio u can imagine, so i started modding it. The first idea was to use well known mods from android software development section. Still I was really unsatisfied with the audio, so I started "porting" & mixing things on my own. After a while i teamed up with several guys from 4pda, that stated "Dude, u do everything wrong. Most of the stuff u are using is not working". OK. So, instead of believing in their words I googled how to make logs, got myself a proper Disassebler & start discovering on how things are working for real.
It's been a huge drama over this thread between me & Arise team. But they are sitting on the very top of the junkyard & there are plenty of "port" mods in this xda section, where things are even worse. I understand that users & evangelists of these mods will call me idiot & stupid, but several people that asked "hey guys, can u explain me how does *thatparticulartechnology* works?" & those people never had a chance to have clear answers. Have u ever interested why? Because people don't know. They think, they can pull several apk's, libs, jars, etc - and this makes effects to work. Well in some cases like Dolby, previous MaxxAudio builds, Am3D, Arkamys - that will work. But for most others it WON'T EVER (well there is a trick, but no one except one guy can do that).
Now I'm gonna share with you all of my findings:
Beats Audio. It's been a very huge history in putting beats libs & binaries into mod's. The first thing you need to consider - beats are deeply bind in HAL. Original HTC m7 flinger has special beats switchers in it, that control the whole effect. Beats API then is tied to Sense framework & several others files. If we open the original file from the M7 - we see that the effect starts with reference to 16A44 substream, and then goes on distributing to multi-channel substreams. So the only thing u need to do - port flinger from m7 to the desired device. The only way to do that - closed arm porting - that is a very tricky way I still don't understand, but Sun_dream successfully did that several times (last time he ported H/K to m9 from m8). Well, we also can replace the HTC M8 flinger with beats one entirety – it will work, but this trick works only under MM. No way to replace flinger on MM & up. All of those "dummy-binaries" like "beatsbass", "beatsnormal", renamed libraries & other stuff - is just nothing but a trash that never worked properly & never will.
Pictures:
Beats API in flinger lib
Harman/Kardon & Jbl. Another HTC technology that people desperately want to port. H/K switcher stays in flinger just the same as Beats. The only way to fully port that - using closed arm porting, but still u would need Htc device for that. There is no other way.
Harman/Kardon from Huawei. I never examined Huawei's pad flinger, but having "libaudioflinger.huawei.so" libs in "ports" is a real surprise. As u can see it refers to original flinger to set HiFi setup. Not every HAL has those connections, or they are written in another way, so the libs won't work on many devices. Also, note that original MediaPad has Kirin CPU, which is different from Qualcomm, MTK & Exynos - the purpose of having H/K from is highly debatable.
Pictures:
Hifi setup
SRS. From the dark ages of android, SRS was used by HTC to optimise your video experience. From 2015 Sony placed it in their XperiaX & XZ. If htc was using it for video stuff, sony uses it for speaker & virtualizer bundle. The problem behind porting it - the good all flinger & HAL. Yes, SRS is also written in flinger, so no way it will work outside original device.
What surprises more - is edits devs make to srs configs for those devices that originally has it - like Project Yume pushes the eg compressor value to 15000. While the maximum is only 1. Even if this effect works for your device, dear devs change it so deep, that it becomes non working)
DeeHX & LDAC. Sony’s Dseehx optimization works ONLY with proper player (Sony’s default music player & PowerAmp) that has DseeHX API. Even when you port SOMC & try to switch DseeHX you won’t hear any audible changes as this thing is also deeply integrated in the whole framework. If you take a look at Z2/Z3 threads - u can see, that before Sony made DseeHx for Z3, people tried to port it from Z5 & failed. Even when Sony finally made it working on Z3 the cap was 96 upsampling) This thing is very specific & hw dependent, so claiming that you have successfully ported - is ridiculously stupid.
Speaking of Ldac - i didn’t examine it deeply, but my guessing is that it is tied to adtp policy, which can’t be replaced with just your wish.
When you make a port of Sony features - you clearly can hear some noticeable changes to audio - i guess that is work of Xloud &/or Clearphase &/or ClearAudio. I didn’t found anything in logs, when i was playing with files from XZ & X. So let’s call this stuff as “partially working”.
DTS. There are various devices having DTS - vivo, asus, acer - but none of them are truly working. For example vivo stuff relates to huge amount of files in the system which works only on vivo. Asus DTS is seeking for particular app (which devs are deleting, cause it can’t be properly porter and modified) & for special flinger that has “Icepower” switcher in it, or at least has set the “fasttrack” to “false”. I’m waiting for acer jade2 - so i can take a look at it’s implementation of DTS, but as far other phones are very hw & framework dependent, I highly doubt it can be ported.
Audio_effects Configs. Now that is the “greatest” & the funniest part of all. I can imagine that “modders” are lazy enough, they don’t want to use disassembler & google. But writing mad configs - is a real disaster. Devs call this “method” an “engine” - what they basically do is putting a non working effect like “eagle_pipeline” (that is used in DTS effects) & trying to stick to standard proxy lib) The whole config in a typical way is written for soundfx API to take part in rendering the audio - like “preeffect” bundle is setting echo cancellation & controls gain, rewerbwrapper is controlling the amount of reverberations & is typically used for aux setup, etc. That is why most of audio_effects configs looks the same, with small integrations of other effects phone developers put into it, so that their own effect will work. But you can’t load unloadable effect (any of those i wrote above), by mixing it with standard API. HAL would appeal to particular library & particular uuid of the effect & only then, if needed will load standard API to render the sound.
This info i was collecting for last half a year. I might be wrong in several places, but I guess you got the main idea: most of effect technologies rely much on particular frameworks & Hw stuff. I’m not sorry for being rude to several people over this thread & there are several other guys i disrespect even more for trashing the whole AD&H section with their crap (no, not Arise guys, as i said - they are just the top of the junkyard). This whole situation leads me to idea, that 90% of “modders” doesn't know what they really do. What is even worse - other people take their work & use it in their projects, so after a while everyone believes that this stuff is truly working. That huge amount of partially working “mods” are trashing your system partition with up to 200+ mb of useless files! “Modders” make ridiculously stupid mistakes, but users still admire & praise them. I don’t need to soothe my ego that much, I just want to warn users of that rubbish: please, don’t be fooled! Make your own research!
Ainur FAQ
What happened to pandora, atlant, and nero?
The best of each have been combined into one: SAURON. These are now all deprecated and will no longer be supported.
Are there any pre-requisites?
Yes, busybox is required. Starting with Sauron MK I.III.I, @osm0sis' busybox is bundled with Sauron so you no longer have to worry about it.
What other audio mods are supported alongside ainur audio mods?
Only audio mods using @ahrion's audio modification library (aml). Others may not work, cause weird issues, and/or completely break everything.
Is there any particular order in flashing these audio mods and other aml audio mods?
Not anymore. This was fixed in Sauron MK I.IV
Will these mods survive dirty flashes/OTA updates:
If your rom has addon.d support, yes, so a dirty flash will not remove them. See the Uninstallation section below for proper removal
Supported Root Methods and Corresponding Location of Scripts:
Magisk 12 or newer - /magisk/ainur_modname
Systemless SuperSu - /su/su.d
System SuperSu - /system/su.d
Rootless - /etc/init.d *Note that your rom must have init.d support for these scripts to run. With Sauron MK I.IV.II, init.d support will be automatically added if it is not already present.
What if my root method is not supported?
You can try to use init.d override. Create an empty file on the root of your sdcard called 'ainur_initdoverride'. Then flash the installer and it'll install scripts for init.d. Make sure this file is present during the uninstallation too.
What if I use magisk but want it installed to system so my device boots faster?
Use magisk override. Create an empty file on the root of your sdcard called 'ainur_magiskoverride'. Then flash the installer and it'll install the files to system instead of magisk img. Scripts are still installed to magisk img though for magisksu compatibility (won't affect boot time much at all). Make sure this file is present during the uninstallation too.
Things To Do Before First Installation:
MAKE A BACKUP
If using magisk version < 13, create an empty file on the root of your sdcard/internal storage called 'ainur_propcompatibility'
Remove any other audio mods (Clean flash may be necessary here)
If using magisk, read the Troubleshooting Section for Magisk here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 and check that your phone is compatible with magisk: https://github.com/topjohnwu/Magisk/issues. If there's a device support issue open for your phone, then it's probably not supported yet
Installation:
Follow the previous section
CREATE ANY AINUR OVERRIDE/COMPATIBILITY FILES ON SDCARD AS NEEDED ABOVE (KEEP THESE FOR UNINSTALL TOO)
Flash the following in order: Rom, root method, ainur module
If using magisk, disable busybox in magisk manager
Magisk Troubleshooting:
If you're spontaneously losing root/weird magisk stuff happening:
Did you disable busybox in magisk manager? If yes, try the following
Go to battery optimization settings and disable battery optimization for magisk manager
Disable magisk hide
If you're seeing weird stuff in twrp involving data partition or see 'Error 2' when installing anything involving magisk
Boot into twrp
Go to Advanced -> terminal
Type:
Code:
e2fsck -f data/magisk.img
Say yes to prompts to repair errors
**Note that in some rare instances, the magisk img is too corrupt to be recovered. In these cases, you'll need to uninstall/reinstall magisk
Uninstallation:
Flash the corresponding uninstaller
OR Clean flash rom
Note: If you're on a rom that doesn't support addon.d (like stock), a dirty flash will work too.
Safety Net:
Safety net will only pass if rootless or using magisk. Here are the steps to pass safety net with magisk:
Open magisk manager
Go to settings
Enable magisk hide and reboot
Still note that Safetynet is a losing battle. See here: https://forum.xda-developers.com/showpost.php?p=68424605&postcount=2
UPDATE: Google has made some kind of update to safetynet so it will no longer pass with magiskhide. This is being working on in v13 betas.
Ainur Module Updating:
Flash the uninstaller for the version of the module currently installed
Flash installer for new version of ainur mod
Does this install any apps like viper4android or just modify system files? Also, will viper work with this mod if not installed?
yung40oz84 said:
Does this install any apps like viper4android or just modify system files? Also, will viper work with this mod if not installed?
Click to expand...
Click to collapse
They will work with v4a & Dolby ports
how do unclog system, i dont see how u say arise clog system arise good sound. i try ur mod to see if it has no clog. what is clog about arise? what files make arise clog, how is it mod not clog
RatchetPanda said:
how do unclog system, i dont see how u say arise clog system arise good sound. i try ur mod to see if it has no clog. what is clog about arise? what files make arise clog, how is it mod not clog
Click to expand...
Click to collapse
Mad configs, Many "ported" features work only on original devices, as they are tied to flinger, or other libs. Sony features - it's placebo. Samsung features work only on Exynos, and won't on MTK or QC, and vice versa. Dts - won't work anywhere except Huawei or Vivo (where did they came from). Beats & SRS from m7 - work only with m7's flinger (Sony Xperia X Performance also has SRS written in flinger). Arise also has many libs ripped off music playes - those libs won't work outside player apps! The same with other mods. You can look into logs on your own to define what is properly working & what's not.
UltraM8 said:
Mad configs, Many "ported" features work only on original devices, as they are tied to flinger, or other libs. Sony features - it's placebo. Samsung features work only on Exynos, and won't on MTK or QC, and vice versa. Dts - won't work anywhere except Huawei or Vivo (where did they came from). Beats & SRS from m7 - work only with m7's flinger (Sony Xperia X Performance also has SRS written in flinger). Arise also has many libs ripped off music playes - those libs won't work outside player apps! The same with other mods. You can look into logs on your own to define what is properly working & what's not.
Click to expand...
Click to collapse
Hey the audio effects conf puts the music players libs in effect globally like neutronmp.so you'll find being used in arises audio effects conf. @guitardedhero can we clear the water before war breaks out like I already see its going to
See libs are not being thrown in at random
So is this a mod that just modifies system?
Sent from my LG-D852 using Tapatalk
metrohackz said:
See libs are not being thrown in at random
Click to expand...
Click to collapse
Now show the logs, that it's running without any errors & flinger got them working) I highly doubt it woukd without connection to service app (for example Ice from Asus shown in the picture).
viddy135 said:
So is this a mod that just modifies system?
Sent from my LG-D852 using Tapatalk
Click to expand...
Click to collapse
Yep. It ups your sound quality, without having junk libs - thats what we were aiming. You will definetly hear it)
UltraM8 said:
It ups your sound quality - thats what we were aiming. You will definetly hear it)
Click to expand...
Click to collapse
Trying now
Sent from my LG-D852 using Tapatalk
Okay here's a better question what the hell are you guys using to produce the effects if theres no audio effects conf or anything like that it looks like this is some libs thrown together with nothing to call on those libs to be used regardless if its placebo or not arise still is superb over this so whatever arise is using to clog the system is actually pretty darn nifty.
metrohackz said:
Okay here's a better question what the hell are you guys using to produce the effects if theres no audio effects conf or anything like that it looks like this is some libs thrown together with nothing to call on those libs to be used regardless if its placebo or not arise still is superb over this so whatever arise is using to clog the system is actually pretty darn nifty.
Click to expand...
Click to collapse
He patches the audio_effects with the library path and uuid. This guy, these guys, know what they're doing. Trust me, this is not another one of those "goons" threads. :good:
metrohackz said:
Okay here's a better question what the hell are you guys using to produce the effects if theres no audio effects conf or anything like that it looks like this is some libs thrown together with nothing to call on those libs to be used regardless if its placebo or not arise still is superb over this so whatever arise is using to clog the system is actually pretty darn nifty.
Click to expand...
Click to collapse
We are using audio libs EVERY android phone has by default) Just extractetd from right places & mixed for perfect audio output. Doma999 even deleted all of the "soundfx" folders - and guess what? Audio still works, he's even saying its way better for him (on htc m8). Will try this hack later on my devices.

Grace UX for 92xT/92xW8 (Noble & A8) Call audio fix

Hey guys! For those who have a s6 or s6e from canada or T-Mobile US (92xW8/92xT), there is a fix for call audio for Grace UX roms using Arter97's N7 Port Kernel, Noble and maybe A8. I have tested (On Noble v6) that the call audio works and CERTAIN (All will work with workaround from below) apps will playback music and videos. It is a known issue and I was hoping that someone would be able to complete the fix and be able to play music locally stored our devices.
Locally stored music does not seem to be working but, some apps below are some I tried using and I did label the apps working or not with some notes. System audio is perfectly fine, from phone calls to notifications, it seems limited to playing locally stored music. Please view "edit 2", I managed to get around the local music issue.
Here are apps I have tested: YouTube(Working), Spotify(Working), Sammy Music(Not Working), Google Play Music(Working, GPM Streaming library only), Blackmusic Player(Not Working)
Call audio fix I used can be found here: http://forum.xda-developers.com/tmo...x-patch-call-audio-fix-t-w8-grace-ux-t3449303
Kernel that must be used (Download the correct one please!): http://forum.xda-developers.com/gal...development/arter97-kernel-galaxy-s6-t3171246
Credit goes to s.raa for N7 audio fix, credit goes to arter97 for kernel
EDIT: A8 confirmed working! Only features not working on T/W8 is AOD and Blue light filter, both of which won't work until someone has been able to compile a kernel with the proper ramdisk and correct fixes for those features and call audio.
EDIT 2: I managed to get locally stored music to play . What I did was remove "Hearingdro_v52" and "SoundAlive_41" from /system/priv-app and install A.R.I.S.E Sound Systems and Dolby Atmos.
I will add a note here: I have not tried just removing "Hearingdro_v52" and "SoundAlive_41". You may try it if you don't like Viper4Android and Dolby Atmos (Which this mod is based on), but I can guarantee that installing this mod makes the audio work with local music files.
Let's hope that we don't always have to do this workaround in the future. But for now, here are the instructions.
here is the XDA link to their thread (Credit goes to the team): http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
Steps (For installing A.R.I.S.E):
Download A.R.I.S.E Sound Systems Deuteronomy 2.33 (and optionally, Dolby Atmos addon for Deuteronomy)
Simply remove "Hearingdro_v52" and "SoundAlive_41" from /system/priv-app
Reboot into recovery
Make a backup of system (This mod replaces lots of files, and in case you don't like it, you can go back)
Flash A.R.I.S.E Sound Systems Deuteronomy 2.33 First
(Optional, only if you also downloaded Dolby Addon) Flash Dolby Atmos addon for Deuteronomy
Reboot and enjoy the working audio with local music files
I tested on A8 Ported ROMs and works fine...
I wish that someone help us with a FIX for tamerlan kernel, with this we can use a Blue Filter and AOD in ported ROMS.
Thanks in advance.
esphinxed said:
I tested on A8 Ported ROMs and works fine...
I wish that someone help us with a FIX for tamerlan kernel, with this we can use a Blue Filter and AOD in ported ROMS.
Thanks in advance.
Click to expand...
Click to collapse
The fix wouldn't be that simple though, it would require a ramdisk change for sure and some other fixes for call audio. It would also need the fixes for both Grace UX and AOD and blue filter.
I would try to compile a kernel, but I have no idea what fixes are needed and what files need to be included for AOD and blue filter.
Thanks for letting me know the audio works on A8 ports!
FQuimson23 said:
The fix wouldn't be that simple though, it would require a ramdisk change for sure and some other fixes for call audio. It would also need the fixes for both Grace UX and AOD and blue filter.
I would try to compile a kernel, but I have no idea what fixes are needed and what files need to be included for AOD and blue filter.
Thanks for letting me know the audio works on A8 ports!
Click to expand...
Click to collapse
Thanks for you support... and if you need a tester for new kernel, please let me know, i still trying to make a mod for this too.
esphinxed said:
Thanks for you support... and if you need a tester for new kernel, please let me know, i still trying to make a mod for this too.
Click to expand...
Click to collapse
I'm pretty sure that Maqical is already testing a kernel with Note 7/A8 ports. The kernel could already be in the works.
Updated OP with a workaround I figured out to play local music files

Shox Extreme Requirements

I really agree that the latest version of Shox Extreme v3.7 @PrasadSable is really a game changer for sound on the Z2 Plus.
But many are asking about it's compatibility as Dolby is currently not working in Treble Roms.
Thus flashing the Shox mod will totally disable audio input and output unless...
You install Audio Modification Library from Magisk Repository.
It is universally compatible with all Oreo Roms irrespective of being Treble or not.
Thus once you install this in magisk, you get the mod running on both speakers with enhanced loudness.
Tested on all Treble ROMs by myself.
You can adjust the quality with the default audiofx too. Dolby would not be necessary.
I hope I could help.

APTX,APTX HD,LDAC,AAC,SBC and Dolby modules

APTX,APTX HD,LDAC,SBC and Dolby modules
Looks like the modules for APTX,APTX HD,LDAC,AAC are broken on Mi A2
My Shanling DAC recognizes with my APTX Bluetooth headphones and even the REDMI 3S phone supports the LDAC,APTX HD with nitrogen OS
MI A2 tries to connect with AAC and it fails to produce any audio with it. Neither does it work with APTX,HD,LDAC modules with selection from developer options
I had to force it to look for SBC coding
Tried to have with magisk \TWRP flash for APTX modules and no luck , upon Boot its its lost in Vendor Libs
Hope someone finds a way to have it implemented
BTW i got Dolby module installed with Magisk and works like charm
Regards,
Diaz
diazneoones82 said:
APTX,APTX HD,LDAC,SBC and Dolby modules
Looks like the modules for APTX,APTX HD,LDAC,AAC are broken on Mi A2
My Shanling DAC recognizes with my APTX Bluetooth headphones and even the REDMI 3S phone supports the LDAC,APTX HD with nitrogen OS
MI A2 tries to connect with AAC and it fails to produce any audio with it. Neither does it work with APTX,HD,LDAC modules with selection from developer options
I had to force it to look for SBC coding
Tried to have with magisk \TWRP flash for APTX modules and no luck , upon Boot its its lost in Vendor Libs
Hope someone finds a way to have it implemented
BTW i got Dolby module installed with Magisk and works like charm
Regards,
Diaz
Click to expand...
Click to collapse
In the meantime use the feedback app to report it
Benjamin_L said:
In the meantime use the feedback app to report it
Click to expand...
Click to collapse
I would, if that didn't need a mi account. don't have one., don't want one.
fairyrobot said:
I would, if that didn't need a mi account. don't have one., don't want one.
Click to expand...
Click to collapse
I just submitted report and it didn't ask me to make an account. If you don't report it it might not get fixed.
APTX,APTX HD,LDAC,SBC and Dolby modules
I have submitted report on feedback app. hope it gets fixed
diazneoones82 said:
APTX,APTX HD,LDAC,SBC and Dolby modules
Looks like the modules for APTX,APTX HD,LDAC,AAC are broken on Mi A2
My Shanling DAC recognizes with my APTX Bluetooth headphones and even the REDMI 3S phone supports the LDAC,APTX HD with nitrogen OS
MI A2 tries to connect with AAC and it fails to produce any audio with it. Neither does it work with APTX,HD,LDAC modules with selection from developer options
I had to force it to look for SBC coding
Tried to have with magisk \TWRP flash for APTX modules and no luck , upon Boot its its lost in Vendor Libs
Hope someone finds a way to have it implemented
BTW i got Dolby module installed with Magisk and works like charm
Regards,
Diaz
Click to expand...
Click to collapse
I'm currently on a 9.0 rom and my rather old MDR BT headset connects with HD audio and uses AAC. I can switch off HD and run with SBC by default.
My Sony MDR 1000X is connecting fine with AAC.
AAC also working fine here. Nothing else though
diazneoones82 said:
APTX,APTX HD,LDAC,SBC and Dolby modules
Looks like the modules for APTX,APTX HD,LDAC,AAC are broken on Mi A2
My Shanling DAC recognizes with my APTX Bluetooth headphones and even the REDMI 3S phone supports the LDAC,APTX HD with nitrogen OS
MI A2 tries to connect with AAC and it fails to produce any audio with it. Neither does it work with APTX,HD,LDAC modules with selection from developer options
I had to force it to look for SBC coding
Tried to have with magisk \TWRP flash for APTX modules and no luck , upon Boot its its lost in Vendor Libs
Hope someone finds a way to have it implemented
BTW i got Dolby module installed with Magisk and works like charm
Regards,
Diaz
Click to expand...
Click to collapse
Which mudule exactly did u installed?
rafihasan710 said:
Which mudule exactly did u installed?
Click to expand...
Click to collapse
I tried every Oreo related zip for APTX\HD - Magisk and recovery zip install and no luck ..Post reboot i do not se them in Libs and lib64 for Vendor and system files
I have also edited the build prop file to make sure entry is there for aptx,hd and ldac
APTX,APTX HD,LDAC,SBC and Dolby modules
rafihasan710 said:
Which mudule exactly did u installed?
Click to expand...
Click to collapse
I tried every Oreo related zip for APTX\HD - Magisk and recovery zip install and no luck ..Post reboot i do not se them in Libs and lib64 for Vendor and system files
I have also edited the build prop file to make sure entry is there for aptx,hd and ldac
Can you share link for Dolby Module & work fine for Mi A2?
I'm on stock ROM, I enabled programmer(developer) mode, then at programmer's options a menu about Bluetooth codec is shown, the options include very codec, APT-X, APT-X HD, LDAC etc.
I have no APT-X BT devices yet to test, so could someone with APT-X or LDAC headphones try this ?
Maybe Xiaomi can't get it to work themselves...
apt-x on Mi A2? Yesss! i did it! https://forum.xda-developers.com/mi-a2/help/apt-x-mi-a2-yesss-t3854813

Categories

Resources