Related
UPDATED: Updated V4A flash file to Viper4Android v2.4.0.1 and added notes about the TabS AOSP Marshmallow custom ROM compatibility by Schischu.
The obligatory warning:
"I take no responsibility for what happens to your device if you follow this guide. This procedure works with multiple Audio/Video apps. It should work for any Samsung device, but I can't confirm, so feedback please if it works for your device."
- 3DSammy
Root with SuperSU is required either using a standard rooting method that trips KNOX or following this guide "[GUIDE] How to root without tripping knox - Kitkat and Lollipop, Locked bootloader" by ashyx. Having SuperSU installed and functioning is essential to get around Viper4Android's need for SELinux permissive mode which is not possible when you are using the Samsung stock firmware.
As of June 8th maximumentropy posted a method to use SuperSU to work around Viper4Android's need for SELinux permissive mode. This requirement was problematic on Samsung devices where the SELinux mode changer app did not work with the Samsung stock firmware.
The instructions and flash files below will allow both custom ROM and rooted stock ROM devices to install Viper4Android, an amazing audio replacement.
Note: V4A and the included flash file works with the AOSP Marshmallow custom ROM compatibility by Schischu. Any of the SoundAlive comments below can be ignored for this custom ROM.
Steps:
1) Download the two flash files "ViPER4Android-supolicy.zip" and "LolliViPER_TAB_S.zip" (at the bottom of this post)
2) Flash ViPER4Android-supolicy.zip and LolliViPER_TAB_S.zip with FlashFire or a Custom Recovery (e.g. TWRP) of your choice.
3) If you want Spotify to work and maybe other audio/video apps then Samsung's "SoundAlive" must be removed or disabled. Options:
Backup then freeze or delete "SoundAlive 2.0" with Titanium Backup
Backup then delete the "/system/priv-app/SoundAlive_Tablet_20" directory with a File Manager that has RW "/system" privileges
Remove "SoundAlive" with an app like "System Remover app" found on the Playstore
4) Reboot your device and then start Viper4AndroidFX and install its drivers when prompted then reboot once more
5) Start the Viper4AndroidFX app and configure audio for the device speakers/headset/bluetooth as desired. Please refer to Viper4Android XDA forum for details about the extensive options.
NOTES:
Be aware that if you do not disable/remove SoundAlive then Spotify will disable V4A until the next device reboot. Causing confusion about whether V4A is actually working reliably. Other audio apps may also demonstrate this tendency.
If you check the V4A driver status and audio is not playing the status will show "Processing: No" that should change to "Yes" when audio is playing and V4A is working correctly.
A Rule-of-Thumb with V4A is to make sure to turn off any Audio/Video player app's specific equalizers, gain controls, audio effects, ... etc, as they interfere with Viper4Android. If you still cannot get Viper4Android working with a specific app, that's not listed in this thread, then search first then if necessary ask on the V4A's XDA forum.
So far the following Audio/Video apps have been successfully tested with V4A:
Neutron audio player (Settings and uncheck Equalizer;Sound Sound;DSP-Effects->Surround Sound;Relay Gain;Normalization)
MX Player Pro (Settings->Audio->Volume Boost unchecked)
Spotify (If it is working properly the Spotify->Settings->Equalizer will directly display the V4A app)
TuneIn Radio
Google Music Player
PowerAmp (PowerAmp Settings->Advanced->Uncheck everything)
YouTube
ViralPro (a YouTube alternative)
Apps that do not work with V4A (likely due to the removal of "SoundAlive"):
Samsung's "Music" app (still plays audio but not by utilizing V4A processing)
Please post any apps not mentioned here, which you either get working or that have problems with after checking the V4A XDA forum.
If you have SuperSU working and have never tried V4A do so and you ears with thank you!
Credits:
zhuhang: For developing Viper4Android in the first place
Chainfire: For developing SuperSu and FlashFire
ashyx: For providing the "How to root without tripping knox - Kitkat and Lollipop, Locked bootloader" guide
maximumentropy: For posting the method and flash file to work around V4A's need for SELinux
AndrasLOHF: Who's post is where I grabbed the original V4A install script.
Schischu: For AOSP Marshmallow custom ROM
Zip file(s):
V4A install for a Tab S
Thanks worked like a charm. Been trying to figure it out for about a week
+1! Stable viper performance with LP, great sound, thank you so much!
Best, maris
Thanks man, It works like a champ and beats my Bose speakers same as S6
Brilliant job mate...
PS. I spent almost a week to switch between KK snd LP. Even S6 was easies with V4A
Worked great. Thanks
works great on my sm-T700 thanks..
Works great on my MOAR S5
will try on the tab s t705c.
3DSammy said:
Flash ViPER4Android-supolicy.zip and LolliViPER_TAB_S.zip
Click to expand...
Click to collapse
Hi and thanks a lot for helping others out with the notoriously difficult to install viper app.
I presume the supolicy zip is intended as an alternative to setting selinux permissive. Any negatives to using one method over the other?
Also, can you please explain what your application zip does exactly. Does it just install the original viper as a system application or did you make any other modifications?
Thanks!
schiphol said:
Hi and thanks a lot for helping others out with the notoriously difficult to install viper app.
I presume the supolicy zip is intended as an alternative to setting selinux permissive. Any negatives to using one method over the other?
Also, can you please explain what your application zip does exactly. Does it just install the original viper as a system application or did you make any other modifications?
Thanks!
Click to expand...
Click to collapse
Either method of getting V4A permissive mode will work but if you rooted and maintained KNOX the stock bootloader blocks SELinux from setting permissive mode so the supolicy is your only alternative. Besides I read a comment from Chainfire who indicates that using permissive mode system wide is poor security practice. On my Nexus 5 which is running marshmallow I found all I needed was two supolicies to get all my root apps running and they were for V4A and stickmount.
The supplied V4A flash file installs V4A in /system/priv-app, sets permissions and attempts to delete two apps that the stock Samsung firmware does not have. Those audio apps are in the Google stock firmware and do no harm as there is nothing to delete. The flash file is based off one for V4A on a Nexus 5. I choose to not delete the Samsung audio app as some people may want to back it up, besides I documented three ways to deal with that app.
I hope you enjoy V4A.
Sent from my SM-T800 using XDA Premium HD app
Dr.Ketan V4A fix for stock touchwiz android 5.0.2 work like a charm on my Tab S T705
Simple as install normal apk, one tap. Done. Here http://forum.xda-developers.com/showpost.php?p=61858278&postcount=3079
This thread is impressive it work !!!!
Thanks. Tried this on my tab S. Works.
RocketPlayer is another music app that works with V4A.
Wow, I wish I had seen this thread sooner. Maybe I can fix the sucky Bluetooth performance in my tab now! Can't wait to try it. Thanks!
Working perfectly in Galaxy Alpha (g850m - Exynos) with enabled root and native kernel, including the Mix Radio (without special settings).
Thank you so much you saved my travels to work !!!
Does V4A not work on KitKat? I decided to downgrade back to KitKat but can't get it to work.
noxarcana said:
Does V4A not work on KitKat? I decided to downgrade back to KitKat but can't get it to work.
Click to expand...
Click to collapse
Yes the app works on KitKat but the directory structure for apps on /system changed. I'd suggest going to the ViPER4Android XDA forum and searching for KitKat installs. That forum link is in the OP (first post).
Sent from my SM-T800 using XDA Premium HD app
3DSammy said:
Yes the app works on KitKat but the directory structure for apps on /system changed. I'd suggest going to the ViPER4Android XDA forum and searching for KitKat installs. That forum link is in the OP (first post).
Sent from my SM-T800 using XDA Premium HD app
Click to expand...
Click to collapse
Ok. Thanks for the reply!
Edit: So, I was't able to find anything there about Kitkat specific installation, but I did find someone that help me figure out what my issue was.
Wow.. Excellent its working on my samung J2 J200F
Very very thanks 3DSammy, I rooted my new samsung j2 only for viper4adroid and I tried a lot and failed and many times ended in boot loop but this time Great Success, Its working fine on Stock Rom with TWRP recovery. But its only working perfect in compatible mode only (normal mode just work for some seconds only then processing stopped) but no problem I am happy .
I am coming to the modding game after an year or so.. I have been seeing Viper4Arise a lot. I wanted to know whats was the difference between Android and Arise. If it is same, why the same name?
I have being trying to get V4Android working with a few roms. I would also like to know which roms are recommended for V4A or even V4Arise(if it performs as good as V4Android).
I have tried RR v5.8.0 but couldnt get V4Android working on it. Also tried Tugapower which is supposed to have V4Arise preinstalled but was so unstable that I dint get a chance to test Arise out. Currently I am sitting on a wiped phone and waiting for a reply here.
I would prefer a rom on which V4Android/(Arise?) installation is easy and has some customization(optional)
(I would really love it if you could provide a detailed guide for installing V4A if possible)
Thanks for any reply. Have a great day guys!
This worked for me, using magisk, with SELinux enforcing;
https://forum.xda-developers.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058
Installed via TWRP rather than using magisk for any of the modules.
I also flashed ahrion's Dolby Atmos module which works alongside V4A.
butterbeanmash said:
This worked for me, using magisk, with SELinux enforcing;
https://forum.xda-developers.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058
Installed via TWRP rather than using magisk for any of the modules.
I also flashed ahrion's Dolby Atmos module which works alongside V4A.
Click to expand...
Click to collapse
Trying it right now! Thanks! Trying on RR v5.8.3
Which rom did you use it on?
Edit^ OMG it worked!!!! thanks a lot!! I cant express how grateful I am right now. RR v5.8.2
I'm on oos beta 7
I think Viper 4 arise is a new team of people and some were working on The v4 Android but moved onto the new project.
Hi everyone,
I have been an android user for long now and have been a total fan of Vipers audio effects, dil by atoms and dolby surround and the sony music app which I have installed in every phone I have had starting with The Samsung note 2 till the Samsung S8 which I had till February this year after which I switched to a note8 exynos as I'm in India.
Eversince I updated to oreo most of the mods either don't install or get stuck in twrp recovery at "Magisk image found" And I have to force reboot.
I was pretty happy to find a post on XDA which had viper Sony music, sony sound effects and dil by atmos and other related goodies and there were oreo versions there.
Unfortunately they too either get stuck while flashing in recovery or if the in stall completes then the phone doesn't boot after reaching the flash in Sammy logo.
Have tried to use supersu instead of Magisk for root but it is a no go even then.
I'm running Delux Rom v6.1 rooted with magics and with sony music installed thorough magisk. The viper install through Magisk doesn't work as in it either fails to install driver or gets installed but does nothing when playing music.
Am downloading delux rom v 6.2 right now and will try again.. I would really appreciate any help or guidance to be able to have my config as I like it to be.
I have also tried weta rom 7.2 and it has the options to install viper and earlier had dil by too. The west rom controller shows the process is complete and successful says reboot is needed.. After reboot there is nothing in the apps menu or sometimes there's viper but it doesn't work.
On weta rom v 7.1 I am unable to get volte working even after manually installing the correct cab which is why I dropped it.
I look forward to help and as ice gem the learned and wonderful people on XDA Developers Forum, I cannot count the number of times I have been saved after bricking my phone by following the tutorials here.
Regards,
Centaur31
centaur31 said:
Hi everyone,
I have been an android user for long now and have been a total fan of Vipers audio effects, dil by atoms and dolby surround and the sony music app which I have installed in every phone I have had starting with The Samsung note 2 till the Samsung S8 which I had till February this year after which I switched to a note8 exynos as I'm in India.
Eversince I updated to oreo most of the mods either don't install or get stuck in twrp recovery at "Magisk image found" And I have to force reboot.
I was pretty happy to find a post on XDA which had viper Sony music, sony sound effects and dil by atmos and other related goodies and there were oreo versions there.
Unfortunately they too either get stuck while flashing in recovery or if the in stall completes then the phone doesn't boot after reaching the flash in Sammy logo.
Have tried to use supersu instead of Magisk for root but it is a no go even then.
I'm running Delux Rom v6.1 rooted with magics and with sony music installed thorough magisk. The viper install through Magisk doesn't work as in it either fails to install driver or gets installed but does nothing when playing music.
Am downloading delux rom v 6.2 right now and will try again.. I would really appreciate any help or guidance to be able to have my config as I like it to be.
I have also tried weta rom 7.2 and it has the options to install viper and earlier had dil by too. The west rom controller shows the process is complete and successful says reboot is needed.. After reboot there is nothing in the apps menu or sometimes there's viper but it doesn't work.
On weta rom v 7.1 I am unable to get volte working even after manually installing the correct cab which is why I dropped it.
I look forward to help and as ice gem the learned and wonderful people on XDA Developers Forum, I cannot count the number of times I have been saved after bricking my phone by following the tutorials here.
Regards,
Centaur31
Click to expand...
Click to collapse
I have been having the same issues too. It seems to be hit and miss. I tried WETA and it worked, but there were a few other bugs in the rom which basically meant I couldn't use it as a daily driver. However...Using @dr.ketan 's ROM, which I have to say is excellent and completely stable, I was delighted to find in the Rom Control, the ability to switch Viper4Android on and off. Simply select the number for Old or New (drivers) and then install the V4A APK and everything works flawlessly! Try it out and good luck!
tfaletau said:
I have been having the same issues too. It seems to be hit and miss. I tried WETA and it worked, but there were a few other bugs in the rom which basically meant I couldn't use it as a daily driver. However...Using @dr.ketan 's ROM, which I have to say is excellent and completely stable, I was delighted to find in the Rom Control, the ability to switch Viper4Android on and off. Simply select the number for Old or New (drivers) and then install the V4A APK and everything works flawlessly! Try it out and good luck!
Click to expand...
Click to collapse
Hi,
Thanks for the suggestion bug i did try out Dr. Ketan's rom and have used his roms starting from my note 2, then note 3, note 5, S8, s7 edge and on my current galaxy note 8.
On using viper for android i was getting random reboots and in the system setting if thers was no entry for it.
centaur31 said:
Hi,
Thanks for the suggestion bug i did try out Dr. Ketan's rom and have used his roms starting from my note 2, then note 3, note 5, S8, s7 edge and on my current galaxy note 8.
On using viper for android i was getting random reboots and in the system setting if thers was no entry for it.
Click to expand...
Click to collapse
Did you try installing V4A as a user app - Give it a shot. Also what version of Viper did you try?
Anyone is using Viper4Android FX v2.7.1.0 (Magisk Module)? Once installed, Google Camera doesn't work anymore. Tried to ask on the official thread
https://forum.xda-developers.com/android/apps-games/app-viper4android-fx-2-6-0-0-t3774651
but no answer....
Which version of Viper4Android are you using on a rooted Pixel 3a?
Fentadroid said:
Anyone is using Viper4Android FX v2.7.1.0 (Magisk Module)? Once installed, Google Camera doesn't work anymore. Tried to ask on the official thread
https://forum.xda-developers.com/android/apps-games/app-viper4android-fx-2-6-0-0-t3774651
but no answer....
Which version of Viper4Android are you using on a rooted Pixel 3a?
Click to expand...
Click to collapse
I've been using that version of viper since I got the phone and haven't run into any issues. I do however also have the audio modification library and audio compatibility patch modules installed as well. If those don't help, then I think there is a larger issue.
PS - I've used both the latest stable and the canary Magisk builds without issues.
sic0048 said:
I've been using that version of viper since I got the phone and haven't run into any issues. I do however also have the audio modification library and audio compatibility patch modules installed as well. If those don't help, then I think there is a larger issue.
PS - I've used both the latest stable and the canary Magisk builds without issues.
Click to expand...
Click to collapse
Which kernel are you using? I'm using ElementalX 1.05.
Tried with audio modification library and compatibily patch modules but didn't work. Everytime i start the google camera, it crashes.
Fentadroid said:
Which kernel are you using? I'm using ElementalX 1.05.
Tried with audio modification library and compatibily patch modules but didn't work. Everytime i start the google camera, it crashes.
Click to expand...
Click to collapse
I've used both stock and elemental kernels. I'm currently on elemental 1.05 with TWRP installed.
sic0048 said:
I've used both stock and elemental kernels. I'm currently on elemental 1.05 work TWRP installed.
Click to expand...
Click to collapse
Ok, so... same as me.
Really, i don't know where to start. I've flashed stock rom wiping everything some days ago. So, my phone is clean. I've the latest Magisk stable and elementalx 1.05.
All i can do is try to dirty flash stock rom again and install twrp, magisk and elementalx and try another time.
About audio compatibily patch, there are really too many options and i don't know where to start to install it correctly..... but i don't think google camera crashes because of that......
Same problem if i install Viper4Android FX Legacy module.
Fentadroid said:
Ok, so... same as me.
Really, i don't know where to start. I've flashed stock rom wiping everything some days ago. So, my phone is clean. I've the latest Magisk stable and elementalx 1.05.
All i can do is try to dirty flash stock rom again and install twrp, magisk and elementalx and try another time.
About audio compatibility patch, there are really too many options and i don't know where to start to install it correctly..... but i don't think google camera crashes because of that......
Same problem if i install Viper4Android FX Legacy module.
Click to expand...
Click to collapse
I would be surprised if the audio compatibility patch caused an issue too. Honestly I had forgotten about the initial options that I had to choose when I installed it. I just uninstalled it and reinstalled it and only chose the "notification remover" option and then opted out of the lib use (last option). I use the headphone jack, so I don't need a USB DAC (does this phone even have one?), nor do I use Spotify, etc.
However, it is important to install the audio modification library last. It should find both the Audio Compatibility Patch as well as Viper4Android and patch both to work together. I might suggest that you uninstall it, reboot, and reinstall it to ensure it is actually patching both audio modification. Also, make sure the driver is actually installed in Viper if you end up reinstalling any of these mods as you might find that the driver isn't actually installed. It's a long shot, but perhaps that would fix your issue.
I'm also using the leaked camera version 6.3.017.253834016 currently (because it has the night sight setting as a main option instead of buried in the "more" settings). But this really shouldn't matter and the stock camera app worked just fine too. Viper4Android is always one of the first mods I install on a phone and it has never given me a problem on my 3a XL or caused the camera to stop working.
sic0048 said:
I would be surprised if the audio compatibility patch caused an issue too. Honestly I had forgotten about the initial options that I had to choose when I installed it. I just uninstalled it and reinstalled it and only chose the "notification remover" option and then opted out of the lib use (last option). I use the headphone jack, so I don't need a USB DAC (does this phone even have one?), nor do I use Spotify, etc.
However, it is important to install the audio modification library last. It should find both the Audio Compatibility Patch as well as Viper4Android and patch both to work together. I might suggest that you uninstall it, reboot, and reinstall it to ensure it is actually patching both audio modification. Also, make sure the driver is actually installed in Viper if you end up reinstalling any of these mods as you might find that the driver isn't actually installed. It's a long shot, but perhaps that would fix your issue.
I'm also using the leaked camera version 6.3.017.253834016 currently (because it has the night sight setting as a main option instead of buried in the "more" settings). But this really shouldn't matter and the stock camera app worked just fine too. Viper4Android is always one of the first mods I install on a phone and it has never given me a problem on my 3a XL or caused the camera to stop working.
Click to expand...
Click to collapse
Tried exactly what you said. Same issue, Google Camera crashes on start. Every V4A version i tried, same thing.... Well, i don't know what to try more..... Asked on official V4A thread but no answer. Is there any way to provide logs to discover what happen?
EDIT: I've attached a logcat, if you know what could be the problem i will be happy
Dirty flashed August factory image, Elementalx, TWRP and Magisk. Same issue. Anyone who can help me taking a look at the logs?
Im on 2.5.0.5 and i have no issues so far with the camera app.
The only issue that i have is that v4a is marked as harmful by Google protect. Anyone else?
Pixel 2 xl user here with the latest viper4android on android 10, same camera app is crashing on me
stock 10 with sultan kernel installed and magisk 20.1
yabadabadooo said:
Im on 2.5.0.5 and i have no issues so far with the camera app.
The only issue that i have is that v4a is marked as harmful by Google protect. Anyone else?
Click to expand...
Click to collapse
Are you using Boldbeast recorder magisk module?
Mi drivers won't install any help appreciated
caballon said:
Mi drivers won't install any help appreciated
Click to expand...
Click to collapse
I've never had any real issues getting Viper4Android to work on Android 10, but I understand it is a common issue. Here is a Pixel 4 thread on installing Viper4Android on Android 10 and how they got it to work. The fact that it is on a Pixel 4 device is irrelevant. Perhaps this can help you get the driver installed.
PS - I should mention that I already was using the audio compatibility module and the audio modification module prior to moving to Android 10, so it is quite possible that is why I never experienced any issues.
sic0048 said:
I've never had any real issues getting Viper4Android to work on Android 10, but I understand it is a common issue. Here is a Pixel 4 thread on installing Viper4Android on Android 10 and how they got it to work. The fact that it is on a Pixel 4 device is irrelevant. Perhaps this can help you get the driver installed.
PS - I should mention that I already was using the audio compatibility module and the audio modification module prior to moving to Android 10, so it is quite possible that is why I never experienced any issues.
Click to expand...
Click to collapse
Thanks for the tip
Fentadroid said:
Are you using Boldbeast recorder magisk module?
Click to expand...
Click to collapse
I am. And the camera started working after disabling the boldbeast module.
There is viper4android for android11 or I need to wait?
Based on the research I've done we'll have to wait. There was an update to the magisk module September 12th but based on the change log it doesn't pertain to Android 11.
I wasn't able to enable tethering or install viper therefore I rolled back to 10 and will continue to monitor.
Thanks ?
Just tried this and it does seem to be working. Haven't fully tested it yet though. But I didn't bootloop and viper seems to work. Pixel 3a XL on Android 11. Rooted with Magisk Canary, e66b0bf3 (20425).
YouTube link
SirAugustine said:
Just tried this and it does seem to be working. Haven't fully tested it yet though. But I didn't bootloop and viper seems to work. Pixel 3a XL on Android 11. Rooted with Magisk Canary, e66b0bf3 (20425).
YouTube link
Click to expand...
Click to collapse
This worked for me the first time. Pretty much flash/reboot and you're done... no separate APK, no extra reboot to install the driver. I'm somewhat amazed.
jljtgr said:
This worked for me the first time. Pretty much flash/reboot and you're done... no separate APK, no extra reboot to install the driver. I'm somewhat amazed.
Click to expand...
Click to collapse
I can only imagine that whoever made this ZIP removed the need for the driver? I'm not quite sure either. But I scanned it for any malware or viruses and it is cleaned. Worked on the first flash and no bootloop so it seems to be legit.
I found mention of alpha versions of Viper being released elsewhere... I assume this is a product of that. I took a look at the scripts and it does mention moving native libraries around to various places and the embedded APKs and misc files looked similar to what I'd expect from the Android 10 version. It was just nice that the Magisk script did everything in one go instead of having to follow order-sensitive instructions with other Magisk modules then retrying the driver install until it stuck.
That said, the alpha thread said it cannot be used with the audio modification library module... bootloops to having your sim cards not be detected were reported until only Viper was installed.
Here is the alpha release post: https://forum.xda-developers.com/showpost.php?p=83525879&postcount=4371
The YouTube link has a matching CRC to this one.
I flashed this one, but it's distorting my external speakers and is buggy, but it does process...so BE CAREFUL. This will get you there until a more stable version is out.
https://www.youtube.com/watch?v=ltbJryJT1gg&feature=youtu.be
SirAugustine said:
Just tried this and it does seem to be working. Haven't fully tested it yet though. But I didn't bootloop and viper seems to work. Pixel 3a XL on Android 11. Rooted with Magisk Canary, e66b0bf3 (20425).
YouTube link
Click to expand...
Click to collapse
Working on LineagOS 18.1 on pixel 4a 5g. Thanks for the link.