You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I installed the magisk module and the application then I restarted my phone and yet it still tells me that the driver is not found (I took the version of the module corresponding to the version of the application)
Reacted by Z1xus, Narwhal, Danon556, Rikj000 and hiiamboris
Same here, except for me it worked until I updated LineageOS and Magisk (I have no idea which one broke it). Now it says "No driver found" for me as well.
after a bit digging, i found, that there is no audio_effects.xml in "/data/adb/modules/viper4android-re/system/etc" and "/data/adb/modules/viper4android-re/vendor/etc"
in /odm there is no audio_effects file.
thes files do exist on my oneplus, but not on the Pixel
i dont't know, if this has anything to do with it or if its helps.
Seems pixel 9 series devices have a different audio layout and no audio mods are working. Hoping a solution can be found. the audio effects files are in system/etc. modifying the zip says installed, but the driver is still not found after rebooting
Unfortunately I don't have a Pixel 9 to test (only a Pixel 7 which works as expected in the latest version).
I will try to look into the Android source code and see what is going on. If anyone with a Pixel 9 and some command line / linux knowledge is willing to help, please contact me on telegram: https://t.me/iscle. Please, don't contact me asking for help, it will be published here when a solution is available.
Update: I've been looking into it with some help of and it looks like it will take some time to get fixed. Maybe JamesDSP devs find a better solution, but it looks like we'll have to create a HAL that registers the effect.
I ran into that same issue. What got me thinking was the version number of the magisk module what says 0.6.1 but the app is the 0.6.2.
So I was unzipping the magisk module and looked for that string.
Found it in the file "module.prop" in line 3 "version=v0.6.1" and changed it to "version=v0.6.2"
Since I had issues with the whole folder zipped back so magisk would install it I just opened the magisk module in 7z, deleted the "module.prop" and dragged & dropped the modified file back in, closed 7z and done.
Since I am completely new to V4A I am not sure if the greyed out entries in the app are normal or depending on my system.
Greyed out are:
Playback gain control
FET compressor
Convolver
Headphone surround+
Reverberation
I tried "legacy mode" on or off. Also used bluetooth headphones and wired ones. Same result.
I am running Samsung Galaxy S7 (Exynos, SM-930F) with Lineage OS 19 (Android 12), Magisk 28002 canary.
i installed it with modification for module.prop" in line 3 "version=v0.6.
*1*" and changed it to "version=v0.6.*2*" and i reinstall it with magisk
but now they dont have any icon viper to launch it please help me
Le mar. 3 déc. 2024 à 01:57, M0RT1M4R ***@***.***> a écrit :
Hi,
I ran into that same issue. What got me thinking was the version number of
the magisk module what says 0.6.1 but the app is the 0.6.2.
So I was unzipping the magisk module and looked for that string.
Found it in the file "module.prop" in line 3 "version=v0.6.*1*" and
changed it to "version=v0.6.*2*"
Since I had issues with the whole folder zipped back so magisk would
install it I just opened the magisk module in 7z, deleted the "module.prop"
and dragged & dropped the modified file back in, closed 7z and done.
Since I am completely new to V4A I am not sure if the greyed out entries
in the app are normal or depending on my system.
Greyed out are:
- Playback gain control
- FET compressor
- Convolver
- Headphone surround+
- Reverberation
I tried "legacy mode" on or off. Also used bluetooth headphones and
wired ones. Same result.
I am running Samsung Galaxy S7 (Exynos, SM-930F) with Lineage OS 19
(Android 12), Magisk 28002 canary.
—
Reply to this email directly, view it on GitHub
<#101 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BKMH2QFZH3Z7VOGY76CAO4T2DT6Y3AVCNFSM6AAAAABJL52RS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJTGMYDGMZSGY>
.
You are receiving this because you commented.Message ID:
***@***.***>
I would try to deinstall magisk module and the app first and then reinstall magisk module, reboot, reinstall app from 0.6.2 release. You have to have both.
Working after Android 15 update with crDroid rom on a OnePlus 7 Pro using the slightly updated fork linked above, however I wouldn't say this original project is "abandoned" when the author literally just posed to this ticket at the very end of August lol
I had been using this projects builds up until recently with A13/A14 GrapheneOS & my Pixel 6a without issue.
Unfortunately I don't have a Pixel 9 to test (only a Pixel 7 which works as expected in the latest version).
I will try to look into the Android source code and see what is going on. If anyone with a Pixel 9 and some command line / linux knowledge is willing to help, please contact me on telegram: https://t.me/iscle. Please, don't contact me asking for help, it will be published here when a solution is available.
Regards,
Iscle
I tried, I don't telegram much but if still an option let me know!
Well, I just bought a Pixel 9 Pro. I do have some motivation to get V4A working on my daily now ;)
DUBZ!!! I'm willing to help in any way possible... I have a stupid system in my car, with my P7 pro with working V4A, the bass was intensely better. Thank you!!
Thank you @M0RT1M4R,
I've did the same as you described here:
I ran into that same issue. What got me thinking was the version number of the magisk module what says 0.6.1 but the app is the 0.6.2. So I was unzipping the magisk module and looked for that string.
Found it in the file "module.prop" in line 3 "version=v0.6.1" and changed it to "version=v0.6.2"
And it resolved the issue for me! 😄
For others with the same issue,
here is the re-zipped Magisk module which I'm using now,
with module.prop altered to be v0.6.2: V4A_Magisk_Module_0.6.2.zip
The Driver version inside the Viper4Android v0.6.2 app will still say v0.6.1,
however now it works again 🙂
@iscle, going forward, I'd recommend you to always release both the Viper4Android app + Magisk module,
with identical versioning, even if one of them didn't have any changes,
to hopefully prevent this issue from happening again in the future.
Activity
rabaimor commentedon Aug 14, 2024
Same here, except for me it worked until I updated LineageOS and Magisk (I have no idea which one broke it). Now it says "No driver found" for me as well.
Mahdi2808 commentedon Aug 17, 2024
Moi aussi le même problème
DeanR97 commentedon Aug 24, 2024
I do have the same Problem on my Pixel 9 Pro.
On my Oneplus 9 Pro it works.
after a bit digging, i found, that there is no audio_effects.xml in "/data/adb/modules/viper4android-re/system/etc" and "/data/adb/modules/viper4android-re/vendor/etc"
in /odm there is no audio_effects file.
thes files do exist on my oneplus, but not on the Pixel
i dont't know, if this has anything to do with it or if its helps.
i do also have attached a log:
logcat.txt
f41lbl0g commentedon Aug 28, 2024
Seems pixel 9 series devices have a different audio layout and no audio mods are working. Hoping a solution can be found. the audio effects files are in system/etc. modifying the zip says installed, but the driver is still not found after rebooting
iscle commentedon Aug 28, 2024
Hi!
Unfortunately I don't have a Pixel 9 to test (only a Pixel 7 which works as expected in the latest version).
I will try to look into the Android source code and see what is going on. If anyone with a Pixel 9 and some command line / linux knowledge is willing to help, please contact me on telegram: https://t.me/iscle. Please, don't contact me asking for help, it will be published here when a solution is available.
Regards,
Iscle
iscle commentedon Aug 29, 2024
Update: I've been looking into it with some help of and it looks like it will take some time to get fixed. Maybe JamesDSP devs find a better solution, but it looks like we'll have to create a HAL that registers the effect.
SiCole180421 commentedon Sep 18, 2024
Google changed things with the 9 series and they don't use HAL anymore, it's AIDL
I also have the 9 Pro XL
M0RT1M4R commentedon Dec 3, 2024
Hi,
I ran into that same issue. What got me thinking was the version number of the magisk module what says 0.6.1 but the app is the 0.6.2.
So I was unzipping the magisk module and looked for that string.
Found it in the file "module.prop" in line 3 "version=v0.6.1" and changed it to "version=v0.6.2"
Since I had issues with the whole folder zipped back so magisk would install it I just opened the magisk module in 7z, deleted the "module.prop" and dragged & dropped the modified file back in, closed 7z and done.
Since I am completely new to V4A I am not sure if the greyed out entries in the app are normal or depending on my system.
Greyed out are:
I tried "legacy mode" on or off. Also used bluetooth headphones and wired ones. Same result.
I am running Samsung Galaxy S7 (Exynos, SM-930F) with Lineage OS 19 (Android 12), Magisk 28002 canary.
Mahdi2808 commentedon Dec 3, 2024
M0RT1M4R commentedon Dec 4, 2024
I would try to deinstall magisk module and the app first and then reinstall magisk module, reboot, reinstall app from 0.6.2 release. You have to have both.
Or maybe since this project seems to be abandoned what I did see to late you could try ViPER4Android FX Redesign (ViperFX RE) here on github.
k9online commentedon Jan 5, 2025
Working after Android 15 update with crDroid rom on a OnePlus 7 Pro using the slightly updated fork linked above, however I wouldn't say this original project is "abandoned" when the author literally just posed to this ticket at the very end of August lol
I had been using this projects builds up until recently with A13/A14 GrapheneOS & my Pixel 6a without issue.
Zooandbio4me commentedon Mar 12, 2025
I tried, I don't telegram much but if still an option let me know!
iscle commentedon Mar 20, 2025
Well, I just bought a Pixel 9 Pro. I do have some motivation to get V4A working on my daily now ;)
Zooandbio4me commentedon Mar 20, 2025
DUBZ!!! I'm willing to help in any way possible... I have a stupid system in my car, with my P7 pro with working V4A, the bass was intensely better. Thank you!!
Rikj000 commentedon Apr 6, 2025
Thank you @M0RT1M4R,
I've did the same as you described here:
And it resolved the issue for me! 😄
For others with the same issue,
here is the re-zipped Magisk module which I'm using now,
with
module.propaltered to bev0.6.2:V4A_Magisk_Module_0.6.2.zip
The Driver version inside the Viper4Android
v0.6.2app will still sayv0.6.1,however now it works again 🙂
@iscle, going forward, I'd recommend you to always release both the Viper4Android app + Magisk module,
with identical versioning, even if one of them didn't have any changes,
to hopefully prevent this issue from happening again in the future.
bornaradusin commentedon Apr 23, 2025
Module.prop doesn't seem to be working on the pixel 9 pro xl March update :/
tried modifying myself and using the above provided file
ypatriot commentedon May 22, 2025
Helo everybody,
I'm just succesfully run release 7.2 apk with 0.6.1 driver in my allwinner K2001N 7.1.1 head unit , it works perfectly
ozmo998 commentedon Oct 13, 2025
I'm running realme ui 6 android 15 on my realme 10 pro plus.
And the same problem not working no driver found
Is there any possible solution for this
sh0x31 commentedon Dec 28, 2025
v8 + magisk on Pixel 9P still not work on the Pixel :(