• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[APP][ALL ROOT SOLUTIONS][6.0+]ViPER4Android FX 2.7

Search This thread

Xj748

Member
Feb 5, 2021
10
0
E allora non saprei. Se c'è una custom ROM per il tuo telefono magari può aiutare, se no non saprei.

Allora ok. Se c'è una ROM personalizzata per il tuo telefono forse potrebbe essere d'aiuto, altrimenti idk.
si ce n'è solo uno, ma viper4android funziona su youtube, spotify, lettore musicale, suonerie, ma non sui giochi... non capisco perchè... su tablet samsung elabora qualsiasi applicazione...

Mod Edit:
"yes there is only one, but viper4android works on youtube, spotify, music player, ringtones, but not on games ... I don't understand why ... on samsung tablet it processes any application ..."

@Xj748
Please use English. This is an international forum and English is absolutely mandatory.
Thx for your cooperation.
- mrjuniork (Forum Moderator)
 
Last edited by a moderator:

SickCuriosity

Member
Nov 26, 2015
26
5
si ce n'è solo uno, ma viper4android funziona su youtube, spotify, lettore musicale, suonerie, ma non sui giochi... non capisco perchè... su tablet samsung elabora qualsiasi applicazione...

Mod Edit:
"yes there is only one, but viper4android works on youtube, spotify, music player, ringtones, but not on games ... I don't understand why ... on samsung tablet it processes any application ..."

@Xj748
Please use English. This is an international forum and English is absolutely mandatory.
Thx for your cooperation.
- mrjuniork (Forum Moderator)
Potresti provare a registrare i log di Viper mentre gira un gioco, magari scopri cos'è che sta andando storto. Non so come si faccia ma sono sicuro che da qualche parte su questo forum lo trovi. Se ce la fai prova a postare i log che quando ho tempo ci do un'occhiata.

You could try saving the logs from Viper while running a game, you might find out what's going wrong. Idk for sure how to get viper logs but I'm sure on this forum you'll find it. If you manage post them here so we can take a look.
 
  • Like
Reactions: Xj748

Xj748

Member
Feb 5, 2021
10
0
Far funzionare correttamente Viper, specialmente su modelli meno comuni, richiede un po' di tentativi ed errori.
Le soluzioni più comuni sono: non i moduli Magisk denominati "Audio Modification Library" e "Audio Compatibility Patch". Quindi imposta la policy selinux su "permissive", puoi farlo con un'app come questa.

Meglio se disinstalli prima Viper, fai queste cose, riavvia e poi reinstalla Viper. Queste sono le soluzioni più comuni, se dopo non funziona ancora non sono sicuro di cos'altro fare. Ci sono molti trucchi diversi intorno ai fili, utilizzati e altri no. Puoi anche provare le impostazioni "modalità legacy" e "modalità compatibilità" di Viper, ma potrebbe più problemi di quanti ne risolvano.

Buona fortuna...



Ti rispondo in italiano visto che sembri italiano.

Far funzionare Viper correttamente, soprattutto su modelli meno comuni, va un po' a tentativi.
Le soluzioni più comuni sono: installa i moduli Magisk denominati "Audio Modification Library" e "Audio Compatibility Patch". Poi setta la policy selinux su "permissive", puoi farlo con un'app apposta tipo questa .

Meglio se prima disinstalli Viper, fai queste robe, riavvii e poi reinstalli Viper. Queste sono le soluzioni più comuni, se dopo ancora non funziona non so bene che altro fare. Ci sono un sacco di trucchi vari in giro per i thread, a qualcuno aiuta e ad altri no. Puoi anche provare le impostazioni "legacy mode" e "compatibility mode" di Viper, ma potrebbe creare più problemi di quelli che risolvono.

In bocca al lupo...

MOD ED : Anche se si apprezza la tua iniziativa per aiutare questo utente, avresti poter fornire anche una traduzione in inglese che ha aiutato altri utenti a visitare questo thread.

Ogni volta che pubblichi in un'altra lingua, fornisci una traduzione inglese anche come da Regola 4.

/TNSMANI, Moderatore Senior
thank you 🙏 but unfortunately it didn't work 😩 ... yes I'm Italian!
 
Last edited:

XODS

Member
Sep 6, 2016
38
0
OK let me know. If you want to upload the file to the telegram site but don't have access, I could potentially send it for you. Let me know.
Running the first command returns and error.

:/ $ su
ce 0 >> /sbin/.magisk/modules/ViPER4AndroidFX/post-fs-data.sh' <
touch: '/sbin/.magisk/modules/ViPER4AndroidFX/post-fs-data.sh': No such file or directory
setenforce 0 >> /sbin/.magisk/modules/ViPER4AndroidFX/post-fs-data.sh
:/ #
 

Skaifer

Member
Oct 12, 2016
11
2
27
Huawei P9 Lite VNS-L21 | EliteROM 7.7 | Android v7.0 | Kernel 4.1.49-EKR-v7.3 | Latest possible updates | Magisk 23

Hi there!
So, after several days of tinkering and rebooting my phone a couple dozen times, trying different versions of ViperFX, patches and tips, I've decided, that I have to ask for a help.

I've managed to get working driver with the latest version of ViperFX-2.7.2.1. Wasn't working at first, it didn't want to install the driver, but after hell of amount attempts to get working other versions, tried again latest. It said it could not copy an empty HTC profile file at 6-th step, I deleted it, then it installed just fine.

There are no patches installed right now or other mods. All is working in legacy mode except driver states abnormal in these situations:
  • Turning master switch off/on.
  • Connecting/disconnecting bluetooth earbuds
  • Turning on Headphone surround+.

Basically, after the device being changed, driver can not launch again until I reboot, then it works until next device change. So if my earbuds reconnect my ears are 'bleeding', because without driver sound level is too high.😅 I've tried to kill audio server (su -c killall -q audioserver), after clearing cache and force stopping app, but it does not help - only restart. If any logs can be helpful let me know what should I collect exactly.
Problem solved. I installed audio compatibility patch and modification library. Removed all mods and cleaned up. Then followed this guide flashed trough recovery dolby atmos and then ViperFX provided there. Dolby app is not present, I'm not sure if it even gave any result. But ViperFX is working finally without errors and I'll leave it there.
 

observingman

Senior Member
Mar 24, 2013
159
19
Problem solved. I installed audio compatibility patch and modification library. Removed all mods and cleaned up. Then followed this guide flashed trough recovery dolby atmos and then ViperFX provided there. Dolby app is not present, I'm not sure if it even gave any result. But ViperFX is working finally without errors and I'll leave it there.
This works !
 
  • Like
Reactions: Skaifer

zgfg

Senior Member
Oct 10, 2016
5,874
3,334
viper4android latest magisk module not working on:
POCO F1
Pixel Experience Plus ROM
Android 11
Magisk v23
SELinux: Enforcing
There many posts describing how to install, generallythere are two methods (AML or MagiskPolicy rules), and the same can be found also in different other threads on XDA, Telegram channels, YouTube, elswhere.
Please do some search and try.
I have Mi 9T with A11 and V4A works with no issues (installed by using Magiskpolicy rules in the module's post-fa-data.sh script
 
  • Like
Reactions: cmch

cmch

Member
Dec 29, 2016
40
5
Xiaomi Poco F1
There many posts describing how to install, generallythere are two methods (AML or MagiskPolicy rules), and the same can be found also in different other threads on XDA, Telegram channels, YouTube, elswhere.
Please do some search and try.
I have Mi 9T with A11 and V4A works with no issues (installed by using Magiskpolicy rules in the module's post-fa-data.sh script
i research a lot😮💨, and aml method didn't worked for me, installing app didn't worked for me, telegram channels didn't helped me infact they said go to official xda and ask there only, official magisk modules didnt worked for me, v4a legacy mode didn't worked for me, youtube didn't helped me cuz munchy video provided two methods and both of them didn't worked, unlike others i am fearful of bootloops( even when i have a nandroid backup), ALTHOUGH MAGISK POLICY IS A NEW THING SO PROBABLY ILL TRY THIS.


EDIT: i was using old AML instead of ainur narsil, now viper is working on legacy mode.
 
Last edited:

observingman

Senior Member
Mar 24, 2013
159
19
Hi,
I am currently using the latest version in mi mix 2 with crDriod Android 11; It works, but I cannot create/edit/delete/rename presets; If I try, nothing happens, e.g. ... If I create a new profile, it seems to work, but if I go back to profiles, it is not there.

The same happens renaming, etc.: The app does not complaint, but it does nothing.

In the preset associated folders there is nothing...
 
  • Like
Reactions: grandpajiver

Vulsilthur

Member
Dec 26, 2014
7
0
How do I fix the "error: could not remount system to rw"
I thought this was systemless? I can't follow any installation guide, because I can't install the driver at all

Magisk 23, Oneplus Nord OOS 11.1.4.4.AC01BA
 

zgfg

Senior Member
Oct 10, 2016
5,874
3,334
How do I fix the "error: could not remount system to rw"
I thought this was systemless? I can't follow any installation guide, because I can't install the driver at all

Magisk 23, Oneplus Nord OOS 11.1.4.4.AC01BA
Sorry, I messed the thread and now I see you're talking about V4A

It works for me on A11 (but diff phone)
 
Last edited:

Vulsilthur

Member
Dec 26, 2014
7
0
Ancient guides for ancient Android versions do no more apply for read-only SAR

Do you refer to the 'error' in TWRP?
Magisk has nothing to do with TWRP - Magisk applies only when you boot to Android

And even in Android, with Magisk, you cannot directly edit/write to /system.
Instead you must use Magisk modules that will write their changes to:
/data/adb/modules/<module-dir>/system/...
and Magisk will then, at booting, mount that to /system/... - that's the Systemless changes mechanism
No, I mean when I start the app, it prompts me to install the driver, but it can't install the driver due to "error: could not remount system to rw"
 

zgfg

Senior Member
Oct 10, 2016
5,874
3,334
No, I mean when I start the app, it prompts me to install the driver, but it can't install the driver due to "error: could not remount system to rw"
Then again it applies what I wrote you about the modules.
By using Systemless manner, they apply changes to /system at the time of booting/initializing Magisk.
/system is not rw that your app (designed for old Android version) could write to
 

zgfg

Senior Member
Oct 10, 2016
5,874
3,334
No, I mean when I start the app, it prompts me to install the driver, but it can't install the driver due to "error: could not remount system to rw"
Sorry, I messed the thead and now I see you are talking about V4A

It works for me on A11, but diff phone than yours

Btw, are you using the latest V4A module from Magisk repo?
 

Vulsilthur

Member
Dec 26, 2014
7
0
Sorry, I messed the thead and now I see you are talking about V4A

It works for me on A11, but diff phone than yours

Btw, are you using the latest V4A module from Magisk repo?
Yes, I am. I've tried to look for solutions in this thread and other places, but I can't get the driver to install due to the aforementioned error.

Edit: Now it's saying "installation failed at patching system"
 
Last edited:

Vulsilthur

Member
Dec 26, 2014
7
0
Alright, for anyone else facing the "installation failed at patching system/could not remount system to rw" issue, I got it to work by wiping the phone and installing another ROM.
 

Joe199799

Senior Member
Sep 7, 2014
827
283
Sorry I've been away for awhile if anybody has any interest I have a preset for Skullcandy Crusher ANC it might work for other headphones not sure. I took about 3 hours to hammer this one out so if you do try it please let me know what you think.


I also have a pair of Sony wh-1000xm4 that I have a WIP preset going I'll try to hammer that one out when I get the time if anybody is interested in that one as well.

I name the presets weird things because I spend so much time trying to make them the best they could possibly be.
 
  • Like
Reactions: jfishbone311

applyscience

Senior Member
Nov 25, 2016
98
22
OnePlus 9
I see comments here giving people a hard time for not doing a "more detailed search" to get this to work but I would reply with the facts that

you use to always just be able to install it from magosk repo and people are use to that.

if the default way changed, it should be documented in the release notes of the package.

I see an update came out weeks ago and the latest release note showing in magisk is from almost a year ago to the day.

so go ahead and give then a hard time (whatever makes you feel superior and better about yourselves) but I would say the lack of documentation in release notes is the real problem.

even if it's too much info, give people a heads up. either way, it's no excuse to stop documenting why updates are being released in the place most users grab it from.

seeing how people are replied to with such attitude when the Dev couldn't even be bothered to update revisions makes me happy I found a better solution due to this apps lack of functionality / documentation

EDIT. not only does it have no revision updates for almost. a year now, the first paragraph is written as if you would be stupid to a assume more would be needed to be done via its "no hacky workarounds" and that the app "handles ALL of that now" good grief.
 

Attachments

  • Screenshot_20210909-234709704 (1).jpg
    Screenshot_20210909-234709704 (1).jpg
    414.5 KB · Views: 77
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 526
    ViPER4Android FX
    YF7EJvAcFH9ZuuytKO91DimKH-TQUvYOaA-gmdBrioXY-LSgtjoadLI17gtaGgIkR6KBXyVA4IXtcdjfLdQ=w2880-h1608

    By pittvandewitt and MrWhite214

    Introduction
    Many users are enhancing their smartphone audio experience with the popular ViPER4Android software, but some of us have a hard time installing the driver or they don't like the look of the app. As a solution for these troubles we have rewritten the 2.4.0.1 app source and added all 2.5.0.5 features to it. Many more features have been implemented too.
    With our huge success of ViPER4Android 2.6 we decided to completely rewrite the ViPER4Android app in Kotlin. This allowed us to squeeze out the remaining bugs and clean up the code even more. After a long time of waiting for you and developing for us, ViPER4Android 2.7 is finally here!
    There are many new features and improvements compared to 2.6, of which some can be found in the changelog. Hit the download button to check it out yourself!

    Downloads
    You can download the latest version on XDA Labs
    If you were pointed here for the installer by @Zackptg5, the link can be found here

    pittvandewitt's vdc service
    If you've always wanted to get the most neutral and arguably best sound coming from your headphones, make sure to join the VDC service to request a file!

    Donate
    You can donate to us via PayPal or buy our donation package from XDA Labs with extra features!
    Donate via PayPal
    Buy our donation package *coming soon*

    Dev Note
    If you want to include the app in your work, you're free to do so as long as you give proper credits

    Legal notice
    We are not associated with vipersaudio nor audlabs.
    Stating their Github readme we're free to use the driver as long as it's not used commercially.
    The driver parameters are obtained from the 2.4.0.1 source. The graphical EQ interface is inspired by the Cyanogenmod DSP application
    The app is still named ViPER4Android, because the driver isn't any different from what ViPER ACOUSTIC provides.
    Renaming it without changing anything would be considered kanging, which is not what is going on here.

    Credits
    ViPER ACOUSTIC for the driver
    Bappo for Swedish translation
    pittvandewitt for Dutch translation
    sazuke0703 for Thai translation
    R1DEN for Russian translation
    Hede for Danish translation
    gloeyisk for Indonesian translation
    LCS for Chinese simplified and traditional translations
    razor84 for Turkish translation

    Installation
    Download and install the APK from XDA Labs
    Follow the instructions when opening the app

    XDA:DevDB Information
    ViPERAndroid, App for the Apps & Games

    Contributors
    Team_DeWitt, pittvandewitt, Mr_White_214

    Version Information
    Status: Stable
    Current Stable Version: 2.7.2.1
    Stable Release Date: 2020-10-27

    Created 2018-04-09
    Last Updated 2020-10-27
    133
    Currently on the wishing list
    • Car mode / head unit detection
    • More translations. If you're interested, take a look over here to find the files. Fork the repo and make a pull request to get your translation merged in next release!
    • EMUI (Huawei) 8.0+ refuses to load the driver. Ask ViPER ACOUSTIC for a 64bit driver (Can't fix)
    • Updated driver that does not require selinux injections or the libstdc++ dependency workaround (Can't fix)

    Before reporting:
    Make sure you use the latest APK provided on XDA Labs
    Make sure any other audio mod is disabled/removed before installing the driver. We really cannot afford fixing every single device setup, especially when it's not related to the app


    If you would like to report a bug, pm @Team_DeWitt using the following format:
    [Describe the problem and your steps you take to reproduce it]
    [Phone brand and model]
    [OS (ROM) + Android version]
    [Root method (in case of magisk: core or full)]
    [Provide a link to your log file]
    115
    Changelog

    2.7.2.1
    • Improved loading logic for convolution files
    • Fixed an issue when installing the module on older Magisk versions
    • Bug fixes
    • Stability improvements


    2.7.2.0
    • Android 11 support
    • Automatically save/restore settings based on the device type/name
    • Add preset widget
    • Reworked presets
    • Performance improvements
    • Close service when no music playback is active if legacy mode is disabled
    • Add optional crashlytics to help improving future versions

    2.7.1.6
    • Support Magisk 20.3
    • Long press a feature to show description
    • Material theme update
    • Support scoped storage on Android 10+ (Preset dir is now /sdcard/Android/data/com.pittvandewitt.viperfx/files/Preset)

    2.7.1.0
    • Support Magisk 19
    • Add compatibility setting
    • Add ability to attach to sessions
    • Fix preset loading bug
    • Switch from setools to magiskpolicy
    • Important release notes: Link

    2.7.0.0
    • Full rewrite in Kotlin
    • New UI
    • Presets can be managed in the app itself
    • Effects can be set more precisely with seekbars
    • Min API 23
    • Uses 2.5.0.4 driver only
    • Audio routing bug fixed
    • Driver status bug fixed
    • Cross device effect changing bug fixed
    • App follows system dark/light mode (can be toggled with google messages e.g.)
    • Installation is faster and more versatile
    • Notification settings
    • Reduced APK size significantly

    2.6.0.5
    • Add app shortcuts (7.1+)
    • Minor interface redesign
    • Fix muffled sound
    • Fix options not applying
    • Fix profile conversion
    • Introduce vdc service
    • Improve performance
    • Update driver installation
    • Update chinese translations, thanks to KiSS

    2.6.0.4
    • Retain service after clearing recents
    • Emergency service.sh fix
    • Support Magisk core mode
    • Fix profile load loop
    • Recover speaker service
    • Fix convolver
    • Support Pixel devices
    • Use su.d if possible
    • Force global effect mode
    • Add Korean translation by @nebulac

    2.6.0.3
    • Fix /system install and uninstall.
    • Add temporary workaround for the convolver
    • Updated strings

    2.6.0.2
    • Fix FC while installing the driver
    • Add root check before installing the driver
    • Removed lucky patcher check
    • Capitalized driver status outputs
    • Updated strings

    2.6.0.1
    • Fix profile loading
    • Fix assets bug
    2.6.0.0
    • Initial Release
    101
    2.7.1.0 released

    Yay it's finally time to release an update

    And with this release come a few important release notes:
    Support for Magisk prior to v19 is dropped.
    If you did not use magisk, you need to reflash your /system partition and reinstall the driver
    An audio attach setting is added too to improve compatibility and it needs some explanation:
    For every time you play a song, the audio player should send information about what session the audio is played on, so equalizer apps can attach to that session.
    Session 0 is the default but deprecated session. Most of the time V4A processes just fine at session 0, but if it doesn't you can enable this switch and Viper will attach to other sessions. Note that if you don't have any session open, the driver status will say abnormal, which makes sense.
    There is the need for a switch, because in a lot of cases audio players do NOT send the information when a session is closed. So they keep the driver occupied and this mutes all other audio streams, including session 0 which is the fallback session.
    To make this problem a bit less bad, I excluded session 0. But when you still run into this problem, the solution is not to kill viper but to kill the audio app that was playing music previously.
    Bad design, I know. But it's not my fault. You should contact the developer of the music app to fix their crappy code and send a broadcast when audio playback stops/pauses.
    This switch makes ACP obsolete.

    Other things that have improved:
    I've seen multiple issues with android pie where the viper library wasn't detected any longer because a dependency is removed since the update. A workaround is shipped in the new release.
    The compatibility mode switch has been added back. This seems to be mandatory for car mode and some android q builds.
    An issue when loading presets has been resolved

    Download can be found on labs as always: Link
    89
    Answers to some related questions

    Help, the driver status says no
    • In case of Enabled: no; Please flip the Master limiter switch and go sit in a corner for a while
    • In case of Processing: no; If you use an application that uses audio sessions, enable session attaching in the settings. If that does not work, the audio is routed over session 0. You might want to try Audio Compatibility Patch from the Magisk repository in this case.

    What happened to the profiles?
    • They're now called presets. They are reworked to use independently per device, a feature that was very welcome. Because of many technical changes and improvements on how the preset is stored and loaded, they are not compatible with older versions than 2.7. You will have to recreate them by hand unfortunately. You can access the menu by pressing the selected device in case you missed the huge showcase when you first launched the app after installing the driver

    Why does your Magisk module not work?
    • Probably because you installed some other mod that also has an audio_effects file in it. Whatever module gets loaded last will become active
      The easiest way to bypass this is to let the app build a module after you installed all your favorite audio mods, and delete all files containing audio_effects in the other modules
      AudModLib will not come in handy this time, because the app doesn't flash a zip that AML can intercept

    Where can I find the source code?
    • You can't. And there is an obvious reason for that: This app is more sensitive to kangers who start selling this app, likely after adding their bullsh*t to it, rather than to people who actually want to help improve the app. Something like that already happened in the past to other audio software here on xda. Not really something we want to see happen again

    Where did the Selinux switch go?
    • What..? Are you really that careless security wise?
      The app handles this in a much more sophisticated way now. It injects only the absolute necessary rules to allow V4A to process, fully automatically

    Help, why do I still experience service drops?
    • Probably because doze is kicking in because Android doesn't like long running services. The service has been implemented the way the docs suggest. You can try excluding it from doze. Alternatively you can check out dontkillmyapp.com for tips

    Do you have a zip file for me?
    • No. There is no point in providing a zip file anymore. The driver installation is written from scratch and actually works now

    How do I uninstall the driver?
    • Use Magisk Manager to delete the module. If you use another root solution, you can dirty flash your rom or just leave it there