Related
Hello everyone
I have been really confused about this and i want to confirm if Viper4Android is working on our phone or not... And if its working can someone write a short guide on how to install Viper4Android and its drivers...
Working great.. no special things for installation... just install app, open app and install driver, reboot
mhp1995 said:
Hello everyone
I have been really confused about this and i want to confirm if Viper4Android is working on our phone or not... And if its working can someone write a short guide on how to install Viper4Android and its drivers...
Click to expand...
Click to collapse
Not working here. always asks to install the driver after reboot.
To get it working all I did was root my phone, installed viper4android.
After opening the app it asked to install the drivers I let it, then rebooted
everything worked just fine.
Viper4Android needs your phone to be on Permissive Kernel.
Working!!! Ty everyone will post a link and how-to install guide in my thread
bmwkeith said:
Not working here. always asks to install the driver after reboot.
Click to expand...
Click to collapse
you probably forgot to set your selinux to permissive. download selinux mode changer here on XDA and the u'll be able to install the driver
Anyone know how to get convolver to work with CM 12.1 nightly on z00A?
Hi, can somebody confirm that Viper4android works without issues on the original rom?, i mean by this that after a reboot the app starts itself, as in my case I have to start the app to get its functionality working on my player
Thanks
is viper4android safe? It asks for a lot of permmisons
yeah viper4android is safe i have been running it since my galaxy s3 and never looked backed best app i have ever come across as far as boosting audio quality.
also guys having problems with not hearing any differance i had the same problem at first then i found a thread in general with a modified audio_policy.config file i had to replace with the original one then v4a worked a charm also kernel has to be permissive too so try it again with the modified audio_policy if you gave up because i nearly did
Not really working for me. I did the se permissive then installed v4a then installed driver and reboot. Now I'm using it mainly for Spotify and it works sometimes but then sometimes it will stop working unless I unplug the headphones and plug back in or sometimes it just stop working at all
Download the viper 4 android guitardedhero bought in my Zenfone max working.
Hello.
after successfully rooting my G4 and installing busybox.. I have also installed V4A. however, after installing the drivers, I can't get them to actually work.. (driver status shows unsupported and abnormal.)
anyone knows if V4A works with the G4? and if so, how did you get it to work?
thanks!
Gammawing said:
Hello.
after successfully rooting my G4 and installing busybox.. I have also installed V4A. however, after installing the drivers, I can't get them to actually work.. (driver status shows unsupported and abnormal.)
anyone knows if V4A works with the G4? and if so, how did you get it to work?
thanks!
Click to expand...
Click to collapse
You need to set kernel to permissive. Selinux switcher apps will correct your issue.
I set to permissive installed v4a of viper and used awesome player instead of nu player. Yet changing eq doesnt do anything
auggie246 said:
I set to permissive installed v4a of viper and used awesome player instead of nu player. Yet changing eq doesnt do anything
Click to expand...
Click to collapse
TUrn off any EQs that you may have on in your music player.
And if you go into the settings menu > Driver status > What do you see here?
After setting to permissive you should get a different message at the bottom when you access V4A compared to when you didn't have it (If you kept note)
Here is a great guide how to make it work: http://forum.xda-developers.com/g4/general/to-root-apps-t3165390/post62107040#post62107040
In addition to the above, I had to force enable V4A and switch to FX compatible mode to get Spotify to work. My other apps worked without those changes.
About gave up for months, then it clicked in my mind when i saw a post mention to make sure all other audio apps redirect eq to viper, and if not, change them. Even if you dont use a certain audio player app, change it too.
Problem is, i could not get the lg music app (which i never use) to change the equalizer to viper, it just had it's own default settings, so i ignored it. So i decided to revisit the lg app, and froze the app with link2sd, i also froze the lg video app too, just in case. Rebooted and now viper sees NEON and i can even run without compatibility mode (which did not work consistantly for me) .
I tried all steps to get this to work, not sure what other things are needed for everyone else, but i tried moving viper to system, installed selinuxmodechanger, maybe this can be uninstalled now, i have no idea. I have no plans to fix what isnt broken and find out myself, so just try freezing lg music app for starters.
Hope it works for you, if so, let the community know what steps you had to do!
I've spent way too long trying to get this working without any success.
If I flash a custom ROM (ie. Pure Nexus), I can flash the ARISE zip (ARISE+Deuteronomy+2.94+Modular+AROMA+Installer.zip) and it works perfectly. No driver issues, or anything.
When running stock, rooted, after flashing the above zip file, it appears to flash successfully, but when I open the app after rebooting, it always says that the drivers are missing and offers to install them. If I choose the option to install the drivers, it always fails.
I learned that if you're on stock, you have to flash a custom kernel before it'll actually flash (and auto install the apk), so I tried with franco and elemental kernels.
Does anyone know the steps I'm missing? I'm wondering if maybe it's because I need busybox, but I'm not sure where to install busybox (or the best method).
I know there has to be a way to get this working. I'm sure I'm missing something simple.
Thanks in advance!
eleazar123 said:
I've spent way too long trying to get this working without any success.
If I flash a custom ROM (ie. Pure Nexus), I can flash the ARISE zip (ARISE+Deuteronomy+2.94+Modular+AROMA+Installer.zip) and it works perfectly. No driver issues, or anything.
When running stock, rooted, after flashing the above zip file, it appears to flash successfully, but when I open the app after rebooting, it always says that the drivers are missing and offers to install them. If I choose the option to install the drivers, it always fails.
I learned that if you're on stock, you have to flash a custom kernel before it'll actually flash (and auto install the apk), so I tried with franco and elemental kernels.
Does anyone know the steps I'm missing? I'm wondering if maybe it's because I need busybox, but I'm not sure where to install busybox (or the best method).
I know there has to be a way to get this working. I'm sure I'm missing something simple.
Thanks in advance!
Click to expand...
Click to collapse
I think not only do you need Busybox (you should just be able to download this from the play store now you're rooted) you will also need a way of setting SELinux to permissive. Try The SELinux toggler.
rename/remove /vendor/etc/audio_effects.conf
grifforama said:
I think not only do you need Busybox (you should just be able to download this from the play store now you're rooted) you will also need a way of setting SELinux to permissive. Try The SELinux toggler.
Click to expand...
Click to collapse
Shawn haz root said:
rename/remove /vendor/etc/audio_effects.conf
Click to expand...
Click to collapse
Thank you both! I will try all of those solutions right now.
When I tried to install busybox via the play store installer to /system/xbin/, it says "It looks like the installation of BusyBox was not successful. Try installing to a different location, that may resolve the issue".
My understanding is that I need to put it in /system/xbin. Do you guys have any ideas? The busybox installer was granted root when I first opened it, so I know it has root access. :\
eleazar123 said:
Thank you both! I will try all of those solutions right now.
When I tried to install busybox via the play store installer to /system/xbin/, it says "It looks like the installation of BusyBox was not successful. Try installing to a different location, that may resolve the issue".
My understanding is that I need to put it in /system/xbin. Do you guys have any ideas? The busybox installer was granted root when I first opened it, so I know it has root access. :\
Click to expand...
Click to collapse
I'd be interested to hear how you get on.
I have Viper4Arise installed, Busybox installed, and it appears to be working (sometimes it just doesn't) but when it does, I don't hear any difference when I apply my convolver irs .
grifforama said:
I'd be interested to hear how you get on.
I have Viper4Arise installed, Busybox installed, and it appears to be working (sometimes it just doesn't) but when it does, I don't hear any difference when I apply my convolver irs .
Click to expand...
Click to collapse
When I was running custom roms, it worked perfectly and I could tell a major difference in the music.
How did you get busybox installed? I can't figure out why the play store installer is failing. It's also failing for my friend on his Pixel XL (also rooted)
eleazar123 said:
When I was running custom roms, it worked perfectly and I could tell a major difference in the music.
How did you get busybox installed? I can't figure out why the play store installer is failing. It's also failing for my friend on his Pixel XL (also rooted)
Click to expand...
Click to collapse
If you install an app called "root browser classic", the second you open it, it requests to install an add on which is busy box. Then close and open it again and it asks to update which takes you to the Google play store then installed the busy box app. Not exactly a conventional way but I just tried and it installed. Not sure if that will help you or not.
Root browser
https://play.google.com/store/apps/details?id=com.jrummyapps.rootbrowser.classic
Busy box
https://play.google.com/store/apps/details?id=com.jrummy.busybox.installer
I also installed this with no issues
https://play.google.com/store/apps/details?id=stericson.busybox
Shawn haz root said:
If you install an app called "root browser classic", the second you open it, it requests to install an add on which is busy box. Then close and open it again and it asks to update which takes you to the Google play store then installed the busy box app. Not exactly a conventional way but I just tried and it installed. Not sure if that will help you or not.
Root browser
https://play.google.com/store/apps/details?id=com.jrummyapps.rootbrowser.classic
Busy box
https://play.google.com/store/apps/details?id=com.jrummy.busybox.installer
I also installed this with no issues
https://play.google.com/store/apps/details?id=stericson.busybox
Click to expand...
Click to collapse
Thank you! That jrummy busy box installer worked perfectly the first time. I confirmed in the stericson version that busy box is really installed.
I went ahead and flashed the arise zip file, and it has an option to set SELinux to permissive. Unfortunately upon reboot, it was the same drivers not installed error
I'm now thinking my issue might be the audio_effect.conf file. I've tried Solid Explorer (my go to file explorer) and Root Browser that you linked above. Both explorers have been granted root, but neither can actually rename the file (or delete it). Jrummy's app just says operation denied, while solid explorer shows the file gone, but if you refresh, it's right back where it was. I'm struggling to find a way to mount system r/w in either app. Do you have any ideas? :\
I tried to find a tool to set SELinux to permissive and i found lots of kernel tuning apps, but none that actually allowed setting permissive. Even Franco's own app for his kernel doesn't have that option (he said it's something about trying to keep it more secure). Hopefully the arise zip is really setting it properly, it's just the audio_effects issue causing my problem.
Thanks again for your help, guys!
Sorry for the noob question.
Running a Pixel 2XL - Pie April '19 Security Build, Magisk v19.0. When trying to install Viper4Android FX v4.1, I have tried seemingly every combination of options, but cannot get the 2.5.0.5 driver to install.
Both the material and regular app install and as a system or user app. Just the driver never gets installed?
Please advise if I've missed something obvious - thanks in advance!
Try flashing in TWRP.
miked2332 said:
Try flashing in TWRP.
Click to expand...
Click to collapse
working with magisk v 18.1 without problems
Latest Canary working also.
Google always tries to disable the root
@pepins: It's not that Google always tries to disable root, Play Protect always tries to disable the Material Design version of the V4A app.
@Switch Blade: When you tried updating it hung for a while on the prompt to update, then it threw up a message to reboot? After rebooting, did it prompt to install the driver again? I encountered that and it's probably a bug in the install script for the module. You need to head to the Magisk thread for the module and bring this up. That said, installing through TWRP, as recommended in the first reply to your post, is the way to go here.
Strephon Alkhalikoi said:
@pepins: It's not that Google always tries to disable root, Play Protect always tries to disable the Material Design version of the V4A app.
@Switch Blade: When you tried updating it hung for a while on the prompt to update, then it threw up a message to reboot? After rebooting, did it prompt to install the driver again? I encountered that and it's probably a bug in the install script for the module. You need to head to the Magisk thread for the module and bring this up. That said, installing through TWRP, as recommended in the first reply to your post, is the way to go here.
Click to expand...
Click to collapse
I get the update driver everytime on first install when if I have reset phone or reinstall Magisk and have to use recovery. After that I can update or reinstall in Magisk.
Sent from my Pixel 2 XL using XDA Labs
miked2332 said:
Try flashing in TWRP.
Click to expand...
Click to collapse
Tried flashing from TWRP - same issue, upon openning Viper4android app, tells me the driver isn't installed - then fails on IO.
Weird
Check Magisk see if viper is in SU. If not Go-to viper app info clear data and turn storage off. Sometimes this make Magisk ask for SU for viper. Makes it work sometimes.
I had to use this method for a while to get it to work. Also I have musicfx disabled in apps. Had to do that on my Nexus 6 and just kept on doing it. Uninstall Viper reboot.
Install Viperfx don't reboot
Install audio modification reboot.
It can be done in TWRP also. If you reflash either of those a second time it uninstalls them if you didn't know.
I'm not a developer I pretty much just mess with these things until they work for me.
Sent from my Pixel 2 XL using XDA Labs
miked2332 said:
I get the update driver everytime on first install when if I have reset phone or reinstall Magisk and have to use recovery. After that I can update or reinstall in Magisk.
Click to expand...
Click to collapse
Of the three devices I installed V4A on the P2XL was the only one to have an issue. Normally it's not an issue, so what changed this time I don't know. Anyway, the other two devices, a Moto X Pure and a Galaxy S4, installed the driver through Magisk without difficulty. As mentioned, flashing V4A in TWRP on the P2XL resolved things.
Strephon Alkhalikoi said:
Of the three devices I installed V4A on the P2XL was the only one to have an issue. Normally it's not an issue, so what changed this time I don't know. Anyway, the other two devices, a Moto X Pure and a Galaxy S4, installed the driver through Magisk without difficulty. As mentioned, flashing V4A in TWRP on the P2XL resolved things.
Click to expand...
Click to collapse
I tried just installing opposite features today didn't work. On my phone it goes 2.5.0.5. Old Style, System App, and after the update I have to choose no on the last. It's my 1 reason for using root.
Sent from my Pixel 2 XL using XDA Labs
Try SeLinux Permissive apk
This happens every now and then for me; especially if I'm updating V4A after being on an older version for a long time...
I've forgotten where I've seen/read it, but many times you can't simply update it and/or install the driver from the app. What I end up doing (forced to do) is to uninstall the app (from within Magisk), reboot, and re-download/re-install it (searching for module from within Magisk app) and it should (usually) install the driver again...I usually install it by selecting the 2.5.0.5 and "material" version and as a "system app"...
I dunno why...but this seems to do the trick, but I have to do it frequently now and then...
I use Magisk module that works for speakers, but not with headset.It happens only to me?
miked2332 said:
Check Magisk see if viper is in SU. If not Go-to viper app info clear data and turn storage off. Sometimes this make Magisk ask for SU for viper. Makes it work sometimes.
I had to use this method for a while to get it to work. Also I have musicfx disabled in apps. Had to do that on my Nexus 6 and just kept on doing it. Uninstall Viper reboot.
Install Viperfx don't reboot
Install audio modification reboot.
It can be done in TWRP also. If you reflash either of those a second time it uninstalls them if you didn't know.
I'm not a developer I pretty much just mess with these things until they work for me.
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
These steps allowed me to install the driver!!!! Thank you!
Installed fine for me. Using Magisk 18.1 though.
Here are more instructions (if some continue to have problems) and a Viper profile for XDA members to try out. Works very well to make the phone speakers sound good.
https://forum.xda-developers.com/pixel-2-xl/how-to/viper4android-pixel-2-xl-stereo-speaker-t3919285
I've been trying to get viper4android working on Android q for quite some time but the module and the app itself does not want work at all. Plus when viper asks you to install the driver from the app it will end up in a bootloop. Has anybody found a temp workround for it?
Device: Pixel 2 XL Android version: Q Beta 3
I'm having a similar issue, only the driver install is asked again upon reboot ;_;
Thats only why i rollback from Q.
Total**** sound without
Ok, got it working on beta 3, using the apk 2.7.1.0 from XDA. It appears to install as a magisk module, along with AML. It didn't work on my first try, then all was good. I need to run it in compatibility mode from the menu. https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
In android P what version did you use?
Always used the magisk repo version before- I tried this many times on Q, with and without AML, but always got the dreaded install driver dialogue. Also tried SE Linux permissive, but no luck. I've never used the apk before, but am sat here now listening to music quite happily. It's survived a couple of reboots (just checking).
1959best said:
Ok, got it working on beta 3, using the apk 2.7.1.0 from XDA. It appears to install as a magisk module, along with AML. It didn't work on my first try, then all was good. I need to run it in compatibility mode from the menu. https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
Click to expand...
Click to collapse
Hm, I just tried that. I downloaded the one off XDA LABS and checked compatibility mode on the app. Still showing up as driver not installed. Viper4Android is literally the key element for my phones such a good module.
Try another reboot?
Knxed_ said:
Hm, I just tried that. I downloaded the one off XDA LABS and checked compatibility mode on the app. Still showing up as driver not installed. Viper4Android is literally the key element for my phones such a good module.
Click to expand...
Click to collapse
I just upgraded to Android 10 on my Pixel 2XL and have Viper running now. Download stable 2.7.1.0 from XDA Labs, grant root with Magisk. Check compatibility mode THEN install the driver. Restart, make changes, and then be sure to check "Attach audio effects" in settings once you make your changes.
ifellouttabed said:
I just upgraded to Android 10 on my Pixel 2XL and have Viper running now. Download stable 2.7.1.0 from XDA Labs, grant root with Magisk. Check compatibility mode THEN install the driver. Restart, make changes, and then be sure to check "Attach audio effects" in settings once you make your changes.
Click to expand...
Click to collapse
Mhh doesn't work for me this way.still asking for driver after reboot lol
Thanks. Worked for me on second try. Followed the instructions rebooted didn't work, installed drivers again rebooted and then it worked.
pa.pn2 said:
Mhh doesn't work for me this way.still asking for driver after reboot lol
Click to expand...
Click to collapse
Same here sadly...
sidhaarthm said:
Same here sadly...
Click to expand...
Click to collapse
Ok, here's what you gotta do to get it to work, this is the ONLY method I've had consistently work for me from beta 3-public release(did it an hour ago and worked perfectly)
First, uninstall any viper you have also make sure you completely uninstall audio modification library if you have it installed, not disable, uninstall it and reboot after uninstalling what I've listed.
After you're all booted back up, install viper from labs (link in this thread)(Also, forget about compatibility mode, don't use it) now open viper but do NOT install the driver yet, just open the application then go to magisk and install audio modification library but dont let magisk reboot the phone after it installs. Once installation completed, go back to viper and install the driver and let it reboot. Once booted, go straight to magisk and DISABLE audio modification library (uncheck the box next to it if you dont get what I mean) don't uninstall it. After disabling AML head back to viper and install the driver again. Now once rebooted is the moment of truth, if you open viper and its installed you're obviously done but if it's not installed you have to take this next step: don't install the driver just yet, go to magisk and re-enable AML then back to viper and install the driver. I don't see why this would not work for you guys, I know this isn't the easiest tutorial to follow but make sure you follow it to a T, if you mess any step up you need to start from scratch and uninstall both AML and viper and start again.
Good luck guys and may the audiophile Gods be on your side through this process!
1dopewrx05 said:
Ok, here's what you gotta do to get it to work, this is the ONLY method I've had consistently work for me from beta 3-public release(did it an hour ago and worked perfectly)
First, uninstall any viper you have also make sure you completely uninstall audio modification library if you have it installed, not disable, uninstall it and reboot after uninstalling what I've listed.
After you're all booted back up, install viper from labs (link in this thread)(Also, forget about compatibility mode, don't use it) now open viper but do NOT install the driver yet, just open the application then go to magisk and install audio modification library but dont let magisk reboot the phone after it installs. Once installation completed, go back to viper and install the driver and let it reboot. Once booted, go straight to magisk and DISABLE audio modification library (uncheck the box next to it if you dont get what I mean) don't uninstall it. After disabling AML head back to viper and install the driver again. Now once rebooted is the moment of truth, if you open viper and its installed you're obviously done but if it's not installed you have to take this next step: don't install the driver just yet, go to magisk and re-enable AML then back to viper and install the driver. I don't see why this would not work for you guys, I know this isn't the easiest tutorial to follow but make sure you follow it to a T, if you mess any step up you need to start from scratch and uninstall both AML and viper and start again.
Good luck guys and may the audiophile Gods be on your side through this process!
Click to expand...
Click to collapse
Take a bow good sir, it worked! Had to follow the steps to the end as first time around it didn't work. Now seems to be alright (see attached)
For anyone else wondering, I upgraded from Aug 9.0 build to Q (020) last night by flashing the factory ROM without wipe. Rooted, ads disabled and now ViperFX working. Life is goooood :angel:
sidhaarthm said:
Take a bow good sir, it worked! Had to follow the steps to the end as first time around it didn't work. Now seems to be alright (see attached)
For anyone else wondering, I upgraded from Aug 9.0 build to Q (020) last night by flashing the factory ROM without wipe. Rooted, ads disabled and now ViperFX working. Life is goooood :angel:
Click to expand...
Click to collapse
I think it also worked for me now but in your screeny it says not enabled.same with me.
But i have all the options for speaker headphones usb etc.think it worked
pa.pn2 said:
I think it also worked for me now but in your screeny it says not enabled.same with me.
But i have all the options for speaker headphones usb etc.think it worked
Click to expand...
Click to collapse
Ah yeah, it's probably because I hadn't enabled it until that time. Here's a fresh screenie
sidhaarthm said:
Ah yeah, it's probably because I hadn't enabled it until that time. Here's a fresh screenie
Click to expand...
Click to collapse
what do you mean with didnt enable it?
i did all the steps, i can adjust all settings but if i play something in g music it still says not enabled....what did i miss?
pa.pn2 said:
what do you mean with didnt enable it?
i did all the steps, i can adjust all settings but if i play something in g music it still says not enabled....what did i miss?
Click to expand...
Click to collapse
By enabling, I meant turning on the master limiter and other settings. I adjusted mine with a nice YouTube track playing in the background and it all worked a treat. Yet to do my Bluetooth earphones though
sidhaarthm said:
By enabling, I meant turning on the master limiter and other settings. I adjusted mine with a nice YouTube track playing in the background and it all worked a treat. Yet to do my Bluetooth earphones though
Click to expand...
Click to collapse
I switched on the master and now its working.awesome find
@1dopewrx05 I followed your mini tutorial to a T and it worked perfectly. Thank you for taking the time to do this, I really appreciate it. Just updated my old faithful to 10 earlier and gonna mess around with some of the neat features. I can't live without Viper, it's essential to me.