Anyone get this working yet?
I installed V4A 2.7.2.1 on my P6P and it works fine. I had to use the apk instead of the magisk module version since the module doesn't work for me.
1. Install the V4A apk
2. Open it, grant root and let it install the driver
3. After reboot, replace the V4A post-fs-data.sh with the custom one (I forget where I got it from) and reboot again
4. Configure V4A and done.
xpdragon said:
I installed V4A 2.7.2.1 on my P6P and it works fine. I had to use the apk instead of the magisk module version since the module doesn't work for me.
1. Install the V4A apk
2. Open it, grant root and let it install the driver
3. After reboot, replace the V4A post-fs-data.sh with the custom one (I forget where I got it from) and reboot again
4. Configure V4A and done.
Click to expand...
Click to collapse
where did you override `post-fs-data.sh`??
i could only find the files in this location (by running find -name "post-fs-data.sh" in a root adb shell:
./dev/r2IgVpl/.magisk/modules/ViPER4AndroidFX/post-fs-data.sh
sarabraj.singh said:
where did you override `post-fs-data.sh`??
i could only find the files in this location (by running find -name "post-fs-data.sh" in a root adb shell:
./dev/r2IgVpl/.magisk/modules/ViPER4AndroidFX/post-fs-data.sh
Click to expand...
Click to collapse
/data/adb/modules/ViPER4AndroidFX
xpdragon said:
/data/adb/modules/ViPER4AndroidFX
Click to expand...
Click to collapse
thanks! had to chmod+x the file but after the reboot it works like a beaut!
These are the steps I used on my OnePlus 9 and they worked on my 6 Pro as well. Didn't need to mess with any post fs stuff:
1. Install Ainur Narsil in Magisk
2. Install AML in Magisk
3. Install V4A
4. Reboot and should be good (if not, continue to step 5)
5. Disable AML in Magisk (don't uninstall, just disable) and reboot
6. Re-enable AML, reboot and now you should be good
rickysidhu_ said:
These are the steps I used on my OnePlus 9 and they worked on my 6 Pro as well. Didn't need to mess with any post fs stuff:
1. Install Ainur Narsil in Magisk
2. Install AML in Magisk
3. Install V4A
4. Reboot and should be good (if not, continue to step 5)
5. Disable AML in Magisk (don't uninstall, just disable) and reboot
6. Re-enable AML, reboot and now you should be good
Click to expand...
Click to collapse
For me, I will try the method with post-fs-data.sh replacement first since it is simple and straightforward. If it doesn't work, I will resort to the above steps. The post-fs-data.sh replacement worked with my OnePlus 7 Pro, OnePlus 8 Pro, Pixel 6 Pro, and Galaxy Tab S7+. However, I had to use the above steps for my OnePlus 9 Pro since the sh script didn't work for this phone.
xpdragon said:
For me, I will try the method with post-fs-data.sh replacement first since it is simple and straightforward. If it doesn't work, I will resort to the above steps. The post-fs-data.sh replacement worked with my OnePlus 7 Pro, OnePlus 8 Pro, Pixel 6 Pro, and Galaxy Tab S7+. However, I had to use the above steps for my OnePlus 9 Pro since the sh script didn't work for this phone.
Click to expand...
Click to collapse
No worries, you're free to try whatever method you like! I just thought I'd post mine because v4a is very finicky and there's no harm in having multiple methods of trying to get it to work
This is odd. I use Amazon music HD and Viper won't work with that at all but works with Deezer 100%, spotty on Tidal (some songs yes, some no).
rickysidhu_ said:
These are the steps I used on my OnePlus 9 and they worked on my 6 Pro as well. Didn't need to mess with any post fs stuff:
1. Install Ainur Narsil in Magisk
2. Install AML in Magisk
3. Install V4A
4. Reboot and should be good (if not, continue to step 5)
5. Disable AML in Magisk (don't uninstall, just disable) and reboot
6. Re-enable AML, reboot and now you should be good
Click to expand...
Click to collapse
Man it's been a long time, but am I crazy or is these available from WITHIN magisk after rooting or do I have to go download these? I haven't rooted since first year I had my OP6 and if I recall correctly magisk modules could be found within magisk and installed from storage if downloaded elsewhere... No I'm concerned I didn't root/ install magisk correctly
xXxG0dzRAgexXx said:
Man it's been a long time, but am I crazy or is these available from WITHIN magisk after rooting or do I have to go download these? I haven't rooted since first year I had my OP6 and if I recall correctly magisk modules could be found within magisk and installed from storage if downloaded elsewhere... No I'm concerned I didn't root/ install magisk correctly
Click to expand...
Click to collapse
Me too i haven't rooted since my one plus 6t all i care about is adaway and viper nothing else i hope theres a guide to get viper working soon
xXxG0dzRAgexXx said:
Man it's been a long time, but am I crazy or is these available from WITHIN magisk after rooting or do I have to go download these? I haven't rooted since first year I had my OP6 and if I recall correctly magisk modules could be found within magisk and installed from storage if downloaded elsewhere... No I'm concerned I didn't root/ install magisk correctly
Click to expand...
Click to collapse
No you are not crazy, I just noticed that the canary version of Magisk doesn't seem to the repo inside of the app.
I've attached the necessary files and it seems we may have to rely on GitHub for future updates
Full disclosure: I do not own a pixel 6 pro. But I thought I'd offer a super simple and possibly working fix for V4A on your device. Using my pixel 4a 5g and running A12.. Ive been running the same version of V4A for the last year.. and it worked on A11 and A12. It's simply plug and play. One time flash of the zip, immediately reboot and done. Nothing more is needed. No replacing files. No Ainur. And AML isn't needed either.
Works perfect on my device. Installs 2.5.0.4 (and not 2.7.x). But honestly, it's the same thing for all intents and purposes.
Like I said, in the interests of being totally honest -- I have no clue if it'll work for you. I hope it does. As V4A is essential for the best possible sound. Especially when using headphones.. it transforms my sound from walkman to a Bose when using them. With a few tweaks, it literally feels like I'm at the concert and the music is coming from every different direction. Absolutely indispensable, this app!
Ps... I'm only on your all's forums because I'm super jealous and wanna pretend that I have a p6p. Probably sounds super gay, but I just wanna hold one.
Here's the link to the zip. I haven't seen anyone say that it didn't work for them. Also, the zip says that it's for Android 11. But that's because it came out before 12, and the existing v4as we're only working for Android <10.
If this one doesn't do the trick, I'm guessing it's just 1 step/tweak away from doing so. Lemme know if it works for y'all. Good luck and God bless.
https://forum.xda-developers.com/attachments/viperfx_android11-zip.5417203/
bubbyj said:
Full disclosure: I do not own a pixel 6 pro. But I thought I'd offer a super simple and possibly working fix for V4A on your device. Using my pixel 4a 5g and running A12.. Ive been running the same version of V4A for the last year.. and it worked on A11 and A12. It's simply plug and play. One time flash of the zip, immediately reboot and done. Nothing more is needed. No replacing files. No Ainur. And AML isn't needed either.
Works perfect on my device. Installs 2.5.0.4 (and not 2.7.x). But honestly, it's the same thing for all intents and purposes.
Like I said, in the interests of being totally honest -- I have no clue if it'll work for you. I hope it does. As V4A is essential for the best possible sound. Especially when using headphones.. it transforms my sound from walkman to a Bose when using them. With a few tweaks, it literally feels like I'm at the concert and the music is coming from every different direction. Absolutely indispensable, this app!
Ps... I'm only on your all's forums because I'm super jealous and wanna pretend that I have a p6p. Probably sounds super gay, but I just wanna hold one.
Here's the link to the zip. I haven't seen anyone say that it didn't work for them. Also, the zip says that it's for Android 11. But that's because it came out before 12, and the existing v4as we're only working for Android <10.
If this one doesn't do the trick, I'm guessing it's just 1 step/tweak away from doing so. Lemme know if it works for y'all. Good luck and God bless.
https://forum.xda-developers.com/attachments/viperfx_android11-zip.5417203/
Click to expand...
Click to collapse
just flash in magisk?
Viper's been so finicky with this device, working on some platforms and others not.
Doesn't work at all with Bluetooth and earbuds for some reason.
rickysidhu_ said:
No you are not crazy, I just noticed that the canary version of Magisk doesn't seem to the repo inside of the app.
I've attached the necessary files and it seems we may have to rely on GitHub for future updates
Click to expand...
Click to collapse
Much appreciated, thanks for confirming for me since these days it seems a little more challenging to find info around here than it was a fear years ago. Granted it's also been a while since I've been on a XDA device subforum at release trying to root. After rooting this baby last night though I feel like a noob all over again, seems like the process changes a pretty good amount each time I dive back in with Google trying to make it harder and harder with each major version update.
Edit: oh boy, I still have my cringey post banner from years ago... Yikes.
bubbyj said:
Full disclosure: I do not own a pixel 6 pro. But I thought I'd offer a super simple and possibly working fix for V4A on your device. Using my pixel 4a 5g and running A12.. Ive been running the same version of V4A for the last year.. and it worked on A11 and A12. It's simply plug and play. One time flash of the zip, immediately reboot and done. Nothing more is needed. No replacing files. No Ainur. And AML isn't needed either.
Works perfect on my device. Installs 2.5.0.4 (and not 2.7.x). But honestly, it's the same thing for all intents and purposes.
Like I said, in the interests of being totally honest -- I have no clue if it'll work for you. I hope it does. As V4A is essential for the best possible sound. Especially when using headphones.. it transforms my sound from walkman to a Bose when using them. With a few tweaks, it literally feels like I'm at the concert and the music is coming from every different direction. Absolutely indispensable, this app!
Ps... I'm only on your all's forums because I'm super jealous and wanna pretend that I have a p6p. Probably sounds super gay, but I just wanna hold one.
Here's the link to the zip. I haven't seen anyone say that it didn't work for them. Also, the zip says that it's for Android 11. But that's because it came out before 12, and the existing v4as we're only working for Android <10.
If this one doesn't do the trick, I'm guessing it's just 1 step/tweak away from doing so. Lemme know if it works for y'all. Good luck and God bless.
https://forum.xda-developers.com/attachments/viperfx_android11-zip.5417203/
Click to expand...
Click to collapse
Didn't work for me. Driver wouldn't install
anyone get viper to work with bluetooth?
rickysidhu_ said:
These are the steps I used on my OnePlus 9 and they worked on my 6 Pro as well. Didn't need to mess with any post fs stuff:
1. Install Ainur Narsil in Magisk
2. Install AML in Magisk
3. Install V4A
4. Reboot and should be good (if not, continue to step 5)
5. Disable AML in Magisk (don't uninstall, just disable) and reboot
6. Re-enable AML, reboot and now you should be good
Click to expand...
Click to collapse
I can confirm this has worked on my pixel 6 pro, had to go all the way to step 6 but it ultimately worked. Thanks!!
Btw, Does anyone know the folder location for the presets?
Edit: After going through steps 1-6, I also tried uninstalling Ainur Narsil and after rebooting the phone, V4A still works. Just a heads up.
vibrantliker said:
anyone get viper to work with bluetooth?
Click to expand...
Click to collapse
Yup using right now,with my Pixel buds
Related
Someone Give me full Guide to use Viper4android On oneplus 3
I used 3.2.6 Oxygen Os
No
Running Android since 1.5..... Boosted OP3
theres a way to ask
the problem with Vpier or any othe audio mod is that it breaks your Mic in video calls like skype or Duo. you will have to use headsets everytime.
Search for Arise number 3.5 for oneplus 3 , flash the file and you will have working Viper on your phone. very simple to setup.
Also let me know if your mic works after that
westentertainer said:
theres a way to ask
Click to expand...
Click to collapse
How to install? :silly:
Amar5373 said:
How to install? :silly:
Click to expand...
Click to collapse
you can read,can't you? so read...and I forgot, search is your friend....
Ajaykumar21066 said:
the problem with Vpier or any othe audio mod is that it breaks your Mic in video calls like skype or Duo. you will have to use headsets everytime.
Search for Arise number 3.5 for oneplus 3 , flash the file and you will have working Viper on your phone. very simple to setup.
Also let me know if your mic works after that
Click to expand...
Click to collapse
Really I never noticed this issue on my g3 in the past year.
Madhawk1995 said:
Really I never noticed this issue on my g3 in the past year.
Click to expand...
Click to collapse
Problem is specific to OP3. I think this op3 forum only
Sent from my ONEPLUS A3003 using Tapatalk
Nilshalok said:
Someone Give me full Guide to use Viper4android On oneplus 3
I used 3.2.6 Oxygen Os
Click to expand...
Click to collapse
Find the search button
Mine got BT device error after flashed arise.
No sound on BT and op3 confused when connected.
If you guys wanna try then try.
I found this solution in some thread. You need custom recovery and rooted device. I have stock, but this also worked for me when I had Resurrection and Freedom ROMs. This is a systemless install. No problems whatsoever with microphone in any app.
1. Install Busybox. Then install the directories into /bin and /xbin.
2. Open the Viper Fix apk. Click apply fix, it will ask you for root permission. (https://www.androidfilehost.com/?fid=24588232905720548)
3. Reboot into recovery. Flash the V4A_v2 zip* (https://www.androidfilehost.com/?fid=24588232905720547)
4. Once rebooted, open the V4A app and install the drivers. Will ask you for root.
5. Reboot and enjoy.
*The zip file removes audio fx and previous versions of v4a if you have any, and is systemless. it will also clear cache and davlink and reboot so its really simple. also, you don't need to change SE permissions, this zip works with both equally the same
Cheers.
nuMEral said:
Mine got BT device error after flashed arise.
No sound on BT and op3 confused when connected.
If you guys wanna try then try.
Click to expand...
Click to collapse
I had the same issue, do you by any change install it together with Dolby Atmos? I use ARISE Leviticus and noticed that the version of Dolby Atmos there breaks BT for me, but uninstalling DA via Titanium and then flashing latest DA, version R6.5, solves it for me (http://forum.xda-developers.com/android/apps-games/mod-dolby-atmos-t3109446).
It's a bit cumbersome but I got it to work by:
1. Flash ARISE package through Recovery
2. Boot up and uninstall DA via Titanium
3. Flash DA via recovery
siwan05 said:
I had the same issue, do you by any change install it together with Dolby Atmos? I use ARISE Leviticus and noticed that the version of Dolby Atmos there breaks BT for me, but uninstalling DA via Titanium and then flashing latest DA, version R6.5, solves it for me (http://forum.xda-developers.com/android/apps-games/mod-dolby-atmos-t3109446).
It's a bit cumbersome but I got it to work by:
1. Flash ARISE package through Recovery
2. Boot up and uninstall DA via Titanium
3. Flash DA via recovery
Click to expand...
Click to collapse
I installed only arise number via TWRP.
Thank you for your help, I will try it again when I have time.
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.
So, I finally setup RR v8.6.8 and everything seems to be working alright -- got Magisk (still on v22.1) passing SafetyNet and all.
My question here is aimed at getting any recommendations fellow forum users may have for setting up V4A, something which can be tricky sometimes -- e.g., on my PX3, there's at least one module one has to flash beforehand to get everything working smoothly...
As I didn't find any dedicated thread, I'm assuming everything works fine just by flashing the ViPER4Android FX Magisk module and it will disable the ROM's AudioFX; am I mistaken?
pnin said:
So, I finally setup RR v8.6.8 and everything seems to be working alright -- got Magisk (still on v22.1) passing SafetyNet and all.
My question here is aimed at getting any recommendations fellow forum users may have for setting up V4A, something which can be tricky sometimes -- e.g., on my PX3, there's at least one module one has to flash beforehand to get everything working smoothly...
As I didn't find any dedicated thread, I'm assuming everything works fine just by flashing the ViPER4Android FX Magisk module and it will disable the ROM's AudioFX; am I mistaken?
Click to expand...
Click to collapse
do a FULL recovery backup (boot/dtbo/system/vendor/data)
try, and if anything goes wrong = restore
i personally use the rootless driver (install in recovery)
and after reboot i install the apk
pnin said:
So, I finally setup RR v8.6.8 and everything seems to be working alright -- got Magisk (still on v22.1) passing SafetyNet and all.
My question here is aimed at getting any recommendations fellow forum users may have for setting up V4A, something which can be tricky sometimes -- e.g., on my PX3, there's at least one module one has to flash beforehand to get everything working smoothly...
As I didn't find any dedicated thread, I'm assuming everything works fine just by flashing the ViPER4Android FX Magisk module and it will disable the ROM's AudioFX; am I mistaken?
Click to expand...
Click to collapse
The V4A app that installs the Magisk module does not disable AudioFX. I would recommend giving the default way a shot for starters (install the app, give root rights, let it install the module, reboot) and see if it works. If it doesn't, the first step you should try is to enable legacy mode from the settings. If that doesn't work as well, you can try a few troubleshooting steps from here. Good luck!
Viper4Android for Google Pixel 6/6 Pro and most other devices on Android 12...
It the time of testing this Method, it worked in November 2021 and December 2021 builds for my Google Pixel 6....
1) Make sure your BL is unlocked and you are ROOTed via Magisk.
2) 1st I installed the attached Viper4Android file WITHOUT opening it.
3) The 2nd file Which is the FIX for Android 12. That can be flashes via Magisk BUT DONOT REBOOT.
4) Once you have installed apk and flash FIX.zip via Magisk, now Grant Magisk SU Rights, Install Driver's, let it automatically reboot.
5). Viper ~~>Settings~~> Legacy Mode Flipped On
6) Enjoy
*Edit*
ADDED Status Screenshot
that's just copying the same post-fs-data.sh file we've been using since like 2019
Roll3r said:
that's just copying the same post-fs-data.sh file we've been using since like 2019
Click to expand...
Click to collapse
And is stolen from here, without any credit
Typhus_ said:
Hello!
I've got Viper4Android version 2.7.2.1 working on Android 12 without the need for any other module installed and with SELinux enforcing.
I've found another thread where other users where talking about Viper on Android 12 and saw THIS post by @TheExoduser.
That solution, in fact, works, so I came up with a simple Magisk module that just changes the script.
All that this "fix module", attached bellow, does is to update the post-fs-data.sh script, included on official installer by @Team_DeWitt and deletes itself after replacing the script.
This is done after 20 seconds upon the reboot, we have to do on Magisk, after installing the fix.
As soon as the script is changed and the fix gets deleted by itself, you may need to enable Legacy mode, on Viper4Android app, choose your desired options and reboot the device again.
If you don't reboot again you won't notice any audio change.
Sometimes a second reboot is needed (faced that during my tests).
Hope this helps.
Cheers!
Click to expand...
Click to collapse
No problem. As long as it helps other users I don't mind that anyone shares it to the world. Credits would be nice though but... whatever...
Merry Christmas to everyone.
Cheers!
DanielF50 said:
And is stolen from here, without any credit
Click to expand...
Click to collapse
Stolen fair and square yo!