Skip to content

No driver found #101

Open
Open

Description

@Kiriox94

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)

Activity

  1. rabaimor commented on Aug 14, 2024

    @rabaimor

    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.

  2. Mahdi2808 commented on Aug 17, 2024

    @Mahdi2808

    Moi aussi le même problème

  3. DeanR97 commented on Aug 24, 2024

    @DeanR97

    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

  4. f41lbl0g commented on Aug 28, 2024

    @f41lbl0g

    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

  5. iscle commented on Aug 28, 2024

    @iscle
    Contributor

    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

  6. iscle commented on Aug 29, 2024

    @iscle
    Contributor

    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.

  7. SiCole180421 commented on Sep 18, 2024

    @SiCole180421

    Google changed things with the 9 series and they don't use HAL anymore, it's AIDL

    I also have the 9 Pro XL

  8. M0RT1M4R commented on Dec 3, 2024

    @M0RT1M4R

    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.

  9. Mahdi2808 commented on Dec 3, 2024

    @Mahdi2808
  10. M0RT1M4R commented on Dec 4, 2024

    @M0RT1M4R

    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.

  11. k9online commented on Jan 5, 2025

    @k9online

    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.

  12. Zooandbio4me commented on Mar 12, 2025

    @Zooandbio4me

    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

    I tried, I don't telegram much but if still an option let me know!

  13. iscle commented on Mar 20, 2025

    @iscle
    Contributor

    Well, I just bought a Pixel 9 Pro. I do have some motivation to get V4A working on my daily now ;)

  14. Zooandbio4me commented on Mar 20, 2025

    @Zooandbio4me

    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!!

  15. marked No driver found #116 as a duplicate of this issue on Mar 24, 2025
  16. Rikj000 commented on Apr 6, 2025

    @Rikj000

    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.

  17. bornaradusin commented on Apr 23, 2025

    @bornaradusin

    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

  18. ypatriot commented on May 22, 2025

    @ypatriot

    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

    Image

  19. ozmo998 commented on Oct 13, 2025

    @ozmo998

    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

  20. sh0x31 commented on Dec 28, 2025

    @sh0x31

    Well, I just bought a Pixel 9 Pro. I do have some motivation to get V4A working on my daily now ;)

    v8 + magisk on Pixel 9P still not work on the Pixel :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions