These installers utilize my Unified installer that can install on Magisk OR System if Magisk is not detected (with Pixel support).
Credits of Originality:
- @zhuhang (Official Thread)
- Viper's Audio (Official blog)
If you already know which original v4a you want to use, just add 'old' for 22.214.171.124, 'mid' for 126.96.36.199, 'new' for 188.8.131.52, or 'mat' for material to the zipname prior to flashing
Make sure there are no spaces in the zipname
This is actually the first rule of xda forums: SEARCH THE THREAD BEFORE POSTING - There's just too many of the exact same thing being repeated. You'll save everyone (including yourself) a lot of time by doing this
LOGS, LOGS, LOGS!!!!
- If you make a post stating a problem without any logs, we can't help you and will likely just ignore it (we're not wizards)
- Get a full logcat. If using adb, use Code:
adb logcat -d > log.txt
- If using magisk, get the magisk log from magisk manager
- Get a TWRP recovery log immediately after flashing: Boot into twrp, install mod, navigate to Advanced -> Copy log, recovery.log will be on root of sdcard
On stock EMUI 8? No audio mods currently work with it. See this post for details
Most Common Issues:
- LDAC Issues? See this post for fix
- App not showing up in app drawer?
- This is typically a magisk only issue and means that it isn't getting mounted by magisk.
- Root cause could be lots of things. Good place to check is the magisk log. See what the last thing run was -> it's likely the culprit. Typical order of loading is: post-fs-data scripts run, system.props are loaded, mods are mounted, service.sh scripts are run
- Typical causes of this are post-fs-data scripts and/or other magisk mods such as ART optimization mod. If you modify ART to more of a speed setting, this kind of issue is more likely to occur (this isn't an issue with the ART mod, it's just the nature of ART itself - more speed = less accuracy)
- Crackling Sound while booting?
- This can be caused by v4a starting and being force closed during boot as a workaround for some problem devices (like OP5).
- Just delete the last 3 lines from the service.sh script (the "am start" line on)
- Alternatively, if you are on a devices that needs those lines, you could add "sleep 5" just before the am start line. Note that since this greatly lengthens the time the script runs, it could prevent other service scripts from running in time and so break other mods
- Another alternative is to remove the boot up sound: /system/media/audio/ui/PowerOn.ogg
- I/O error or driver install prompt or crashing app?
- This is typically caused by one of four things: another audio mod is installed (magisk only issue), magisk mounting issues, installer patching error (these have been pretty much worked out so unlikely), sepolicy issues
- Remove any other audio mods or install Audio Modification Library, check magisk log to ensure everything mounted, recovery log will reveal most install errors (also, check system and vendor audio_effects.cfg and ensure v4a entries are there with the right paths to libs set)
- Sepolicy is more complicated. Read through section 5.5 here for a quick background on it. Bascially, you need to take a full logcat, and search through it for any audit statements that may be related to audio and/or this app and make an allow statement in the service script of the mod. Just make a post with that info and once confirmed, we'll add it the next version of the mod
- If above doesn't fix it and you're using the material app, try using the original
- No sound processing?
- For as long as I can remember, after you first boot, you need to toggle the master power button in v4a for sound to being processing. This isn't for all devices of course but for a lot. It's just the nature of v4a.
- If the toggle trick doesn't work, see the last section on sepolicy troubleshooting
- Still no sound processing or no sound processing on some apps like youtube or other streaming apps?
- Remove any stock audio apps (like AudioFX), disable any eqs in music players
- Disable any kind of "direct volume" option in your audio app (like poweramp), this may called other things like "Volume boost / Voices sound lounder" (like in pocket casts)
- Open you vendor audio_effects.conf file and make note of anything under output_session_processing -> music -> then go under the effects section and comment out each effect section you have listed (music_helper is already done by aml)
- Try Audio Compatibility Patch
New ViPER4Android Materialized:
GO TO THE THREAD LINKED ABOVE. You don't need to flash any zips. Just install it as a regular apk, allow it to install the drivers, and you're good to go. For magisk users - it'll install it all to the magisk img so it'll pass safetynet - BACKUP YOUR PROFILES. For rootless users (or others who just want to flash it and forget it), go the thread above for the zip. DO NOT POST PROBLEMS WITH THIS APK HERE! Post it at the app thread (like above)
V4A XHiFI Download
ViPER4Android FX, App for all devices (see above for details)
ahrion, zackptg5, ViPER's Audio, zhuhang, ViPER520, Team_DeWitt
Source Code: https://github.com/therealahrion/ViPER4Android-FX
Current Stable Version: v1.7
Stable Release Date: 2018-07-17
Last Updated 2018-07-17