So I know many of you enjoyed using this amazing mod in the past and something in our builds caused it to break after 4.3.1 roms started rolling out. Look no further as i have a fix for you that is guaranteed to work again.
Step 1.) For the first step you will need to edit your build.prop file found in /system folder. Personally i use Rom Toolbox lite (found here https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox&hl=en) as it comes with a built in build.prop editor and root browser and it is free. Some of these edits may already be in your build.prop so check the edits posted below to see if they are already there or just need a slight change before just adding it as having 2 of the same edits with a different value may conflict with eachother
the edits are:
lpa.decode=false
tunnel.decode=false
tunnel.audiovideo.decode=false
it may ask to reboot on some or just one of these but we can skip rebooting for now. once set we can now move forward.
Before starting the next step MAKE SURE YOU REMOVE AND UNINSTALL DSP MANAGER. you can do so via app manager in ROM Toolbox Lite.
Step 2.) Now we download viper4android according to your rom version. For 4.3.1 roms get this one https://play.google.com/store/apps/details?id=com.vipercn.viper4android4x&hl=en
Once downloaded and installed you will now have to copy and paste it from /data/app to system/app. When it finishes copying over delete the app from /data/app as it will not work otherwise. Make sure permissions are properly set to rw-r--r-- or 0644 in numerical terms. Rom Toolbox will make this whole process easier and faster.
At this point you will now reboot your device for the next step
Step 3.) Once rebooted open the app and it will have you install its driver Select cortex A8 option (3rd one down). It will ask to reboot but dont do it yet. Last thing to do is while in viper4android app hit the sttings button and you will see a long list of things. Select FX Compatible Mode and switch from Normal to Compatible mode and now you reboot for it to take effect and work.
After this you are all set to start setting your sound otions in viper4android and enjoy
I Give great Thanks to:
@zhuhang for making this great app/mod
@jrummy for creating rom toolbox (another amazing app)
@Bradl79 for the build.prop idea
@bbgreen for confirming this works
And Anyone else i may have missed
If i have PM me and ill gladly add them in
So far for the headset option i have the following enabled and set
Under MASTER POWER:
Enable V4A-FX is checked and powered on
Under FIREQUALIZER:
Enabled is checked and powered on
Select Preset is set to Rock
Under DYNAMIC SYSTEM:
Enable is checked
Select Listening Device is set to Common Earphone (v2)
Select Dynamic Bass is set to 2 percent
Under FIDELITY CONTROL:
Enable ViPER Bass is checked
Select Bass Mode is set to Natural Bass
Select Bass Frequency is set to 100Hz
Enable ViPER Clarity is checked
Select Clarity Mode is set to XHiFi
Select Clarity is set to 3.5 db
thats all i have set for now but i'm using skullkandy heaphones with this setup will vary for other headphone brands and models. with this setup it gets very loud and clear as well as amazing bass so dont damage your eardrums lol
Other aidio profiles can be found here by scrolling down to second post http://forum.xda-developers.com/showthread.php?t=2324454&highlight=viper4android
Thanks @sixcarnage for posting that as well
REV3NT3CH said:
So I know many of you enjoyed using this amazing mod in the past and something in our builds caused it to break after 4.3.1 roms started rolling out. Look no further as i have a fix for you that is guaranteed to work again.
Step 1.) For the first step you will need to edit your build.prop file found in /system folder. Personally i use Rom Toolbox lite (found here https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox&hl=en) as it comes with a built in build.prop editor and root browser and it is free. Some of these edits may already be in your build.prop so check the edits posted below to see if they are already there or just need a slight change before just adding it as having 2 of the same edits with a different value may conflict with eachother
the edits are:
lpa.decode=false
tunnel.decode=false
tunnel.audiovideo.decode=false
it may ask to reboot on some or just one of these but we can skip rebooting for now. once set we can now move forward.
Before starting the next step MAKE SURE YOU REMOVE AND UNINSTALL DSP MANAGER. you can do so via app manager in ROM Toolbox Lite.
Step 2.) Now we download viper4android according to your rom version. For 4.3.1 roms get this one https://play.google.com/store/apps/details?id=com.vipercn.viper4android4x&hl=en
Once downloaded and installed you will now have to copy and paste it from /data/app to system/app. When it finishes copying over delete the app from /data/app as it will not work otherwise. Make sure permissions are properly set to rw-r--r-- or 0644 in numerical terms. Rom Toolbox will make this whole process easier and faster.
At this point you will now reboot your device for the next step
Step 3.) Once rebooted open the app and it will have you install its driver Select cortex A8 option (3rd one down). It will ask to reboot but dont do it yet. Last thing to do is while in viper4android app hit the sttings button and you will see a long list of things. Select FX Compatible Mode and switch from Normal to Compatible mode and now you reboot for it to take effect and work.
After this you are all set to start setting your sound otions in viper4android and enjoy
I Give great Thanks to:
@zhuhang for making this great app/mod
@jrummy for creating rom toolbox (another amazing app)
@Bradl79 for the build.prop idea
@bbgreen for confirming this works
And Anyone else i may have missed
If i have PM me and ill gladly add them in
Click to expand...
Click to collapse
Been trying to get this to work for a while as well as you may recall from past comments. Sure this guide will produce a desired "universal" sound effect as before? I had no luck with SoundCloud getting processed by V4A after this. However, I may needed to retry steps verbatim on a fresh ROM install too as I had some other conflicting things to clean up along the way.
Idk about soundcloud...I does work like it did before in Apollo...my guess is that its directing to basic sound while using other apps or stuff like soundcloud
Sent from my ADR6425LVW using xda app-developers app
Nice find Rev! Works great.
Thanks for the write up I just tried it. Unfortunately it only seems to work with Apollo. When I try it with Power Amp or Pandora it no longer works. On my old sense 4.0 ROM viper4android would modify those programs as well Ive tried the current version and the version off the play store with the same results. Thanks for the write up though very easy to follow.
Please post any questions about Viper4Android here not just 4.3 ROMs.
Sent from my ADR6425LVW using Tapatalk
How To Bake Viper4Android into a ROM zip (BASED OFF OFF v.2322)
@REV3NT3CH Consider adding this to the thread (Not trying to hijack the thread) this may be super long
@PTuT @Chucktr you asked for a pm of how to bake v4a into a rom, i decided to post it here for everyone
If you dont want to download the apk and install the apk/drivers you can merge the drivers and app from your pc.
ill probably end up making a script for this but right now i don't mind copying it into new builds for now
Latest apk - http://www.mediafire.com/download/z1mqg58hz1sfais/ViPER4Android_FX_v2322.zip
driver - http://d-h.st/xHh
driver config - http://d-h.st/axM
i usually use 7zip for archive viewer ect..
1. Open the rom zip in 7zip or whatever you choose to use
2. In 7zip navigate to "system/priv-app/" and drag/drop the apk you downloaded into the 7zip window.
3. In 7zip back out of the "prive-app" folder and navigate to "system/lib/soundfx/" and drag/drop libv4a_fx_ics.so you downloaded into the 7zip window
4. in 7zip back out of "soundfx" & "lib" and navigate to "system/ect/" and drag/drop audio_effects.conf you downloaded into the 7zip window
Exit 7zip, Now you have the app and driver baked in the rom :good:
Now what happens when any of this stuff gets update?.... well
Drag/drop the latest apk to priv-app (obviously lol)
The Driver can be pulled from the inside the apk in the assets folder using 7zip. Use any of the drivers containing "libv4a_fx_ics_NEON" based on the quality of the driver they are named different but i use libv4a_fx_ics_NEON_HQ, rename it to libv4a_fx_ics.so and copy it to the rom zip
We cant use the JB drivers on jb or kk, only ics
i dont know how often audio_effects.conf gets updated but just add the fallowing to the audio_effects.conf in the rom zip (ONLY IF NEEDED) the download link above should be good fine good for a while:
Line 9 to 11 :
v4a_fx {
path /system/lib/soundfx/libv4a_fx_ics.so
}
Line 69 to 72:
v4a_standard_fx {
library v4a_fx
uuid 41d3c987-e6cf-11e3-a88a-11aba5d5c51b
}
all of this is based off of v.2322 so i cannot guarantee this to work within the next year or so ect... if someone updated something
bunchies said:
@REV3NT3CH Consider adding this to the thread (Not trying to hijack the thread) this may be super long
Click to expand...
Click to collapse
thanks for this...will deffinately be very useful and will do...your not hijacking bud your contributing to a very useful cause... you tha man @bunchies
Related
I have searched this but can't find my particular issue. I just flashed CM7 (previously had bionix). I followed the instructions on the CM7 wiki and all works smoothly and fine except in call volume.
It is extremely loud when I make/receive a call. When I adjust the volume it adjusts to what it is set to. How do I set the in call volume or solve this issue?
This may work with CM7's stock kernel. But I do know that if you flash a custom kernel like Glitch for say, then you could download a Call Script... http://androtransfer.com/fascinate/90call_vol.zip... With this file you can tweak all the call volumes to your liking.
Instructions (if you have Glitch kernel running):
1. Download the Call Script.zip
2. Extract the .zip
3. Move the file to your phone's internal SD card
4. In Root Explorer hit the "Mount R/W" button
5. Still in Root Explorer move the 90call_vol from the /sdcard to /etc/init.d
6. After it has been pasted into the init.d folder long press on the 90call_vol file and hit "Open in text editor".
7. Once the file is opened, the file will take you through the rest of the steps.
8. Once you have tweaked the settings in the file do a reboot and test out your phone. It may take a bit to find the perfect balance but with a little patience you will .
Thanks for the advice and guide. I just went through the steps and it is still way loud. When i place/make a call it is way loud and if I adjust the volume with the rocker buttons it goes to what the volume is "supposed" to be and what the screen is showing (hope that makes sense). Please help, I was stoked to run CM7 and this is making me want to do something else
sokey70 said:
Thanks for the advice and guide. I just went through the steps and it is still way loud. When i place/make a call it is way loud and if I adjust the volume with the rocker buttons it goes to what the volume is "supposed" to be and what the screen is showing (hope that makes sense). Please help, I was stoked to run CM7 and this is making me want to do something else
Click to expand...
Click to collapse
I was having the same issue on Glitch. Even if you're not on Glitch, I suggest flashing another kernel.
Sent from my SGH-T959 using xda premium
sokey70 said:
Thanks for the advice and guide. I just went through the steps and it is still way loud. When i place/make a call it is way loud and if I adjust the volume with the rocker buttons it goes to what the volume is "supposed" to be and what the screen is showing (hope that makes sense). Please help, I was stoked to run CM7 and this is making me want to do something else
Click to expand...
Click to collapse
No problem. But did you try these steps w/ the Glitch kernel (because I don't think the stock CM7 kernel supports Call Script)? I was having the exact same issue and the Call Script fixed the issue for me. I'll upload my Call Script (already tweaked) in a few. In the mean time I would suggest you look into Glitch, much better then the stock kernel in terms of battery, stability, and color. Plus it will allow you to fix the horrible loud distortion present in CM7.
Yes, I installed Glitch and edited the file as explained and still had the issue. even a screen of your file would be good, I tried all different settings from 0-3 and each started off way loud and then when I adjusted the volume it went to where it was supposed to be.
each time you edit the script, you want to reboot the phone for the settings to take effect. also, make sure all permissions are checked by longpressing on the script using root explorer, select permissions and check all selections.
with glitch kernel, set all incall boost to 0. the highest would be 1. settings 2 and 3 cause distortion. in any other kernel, i've found setting 3 is the same as setting 1 in glitch.
This worked perfectly for me! Glitch kernel on MIUI SGSII rom.
Thanks!
Se7eN43 said:
each time you edit the script, you want to reboot the phone for the settings to take effect. also, make sure all permissions are checked by longpressing on the script using root explorer, select permissions and check all selections.
with glitch kernel, set all incall boost to 0. the highest would be 1. settings 2 and 3 cause distortion. in any other kernel, i've found setting 3 is the same as setting 1 in glitch.
Click to expand...
Click to collapse
Question....I can't get this to work. I notice in the file it says, "just be sure you do the chmod and chown commands below in any case." I think that's the piece that people are missing, and I can't seem to figure that out. I tried to go into terminal emulator and say
Code:
chmod -R 750 /etc/init.d/
and
Code:
chown -R root:shell /etc/init.d/
...but for both commands, I get that the operation is not permitted. I think this is what is causing my changes to not apply correctly, and I can't seem to figure out how to do these two commands. Both the etc and init.d folders are set to r/w/x, as well as the file itself
Are these commands extremely necessary and if so, what can i do to more easily make them work?
Perhaps someone would be so awesome as to create a flashable script for linux dummies like myself?
jakemg said:
Question....I can't get this to work. I notice in the file it says, "just be sure you do the chmod and chown commands below in any case." I think that's the piece that people are missing, and I can't seem to figure that out. I tried to go into terminal emulator and say
Code:
chmod -R 750 /etc/init.d/
and
Code:
chown -R root:shell /etc/init.d/
...but for both commands, I get that the operation is not permitted. I think this is what is causing my changes to not apply correctly, and I can't seem to figure out how to do these two commands. Both the etc and init.d folders are set to r/w/x, as well as the file itself
Are these commands extremely necessary and if so, what can i do to more easily make them work?
Perhaps someone would be so awesome as to create a flashable script for linux dummies like myself?
Click to expand...
Click to collapse
You don't need to use Terminal Emulator. It's 100.1% easier to use Root Explorer. Here's what to do. These are similar to the steps I posted above, but I simplified it to make it easier for yah...
Instructions (While on Glitch):
1. Download the 90call_vol (To make it easier use mine which is already configured)
2. Move the file from your PC to your phone's internal SD card
3. In Root Explorer hit the "Mount R/W" button
4. Still in Root Explorer move the 90call_vol from the /sdcard and paste it into /etc/init.d
5. Now the most important step... REBOOT
6. Done! Now test your device
Yep, that's exactly what I was doing and still, when I make or receive a call, the in-call volume jumps up to max unless I turn it down. T. Then if I make or receive another call, the in-call volume jumps back up again. This cycle constantly repeats itself. No matter what, the actual in-call volume keeps jumping up to max.
Thanks for trying, though.
And you're on the Glitch kernel right?
Yep. Glitch V13...
Boo. First off thanks for the help and guide but unfortunately it does not work for me. I've tried this twice now on cm7 and miui fresh installs. Neither worked and I followed the steps exactly. Man this is lame. Is there a previous version of either miui or cm that doesn't have this issue?
N00B_IN_N33D said:
You don't need to use Terminal Emulator. It's 100.1% easier to use Root Explorer. Here's what to do. These are similar to the steps I posted above, but I simplified it to make it easier for yah...
Instructions (While on Glitch):
1. Download the 90call_vol (To make it easier use mine which is already configured)
2. Move the file from your PC to your phone's internal SD card
3. In Root Explorer hit the "Mount R/W" button
4. Still in Root Explorer move the 90call_vol from the /sdcard and paste it into /etc/init.d
5. Now the most important step... REBOOT
6. Done! Now test your device
Click to expand...
Click to collapse
This did not work for me.....
You all are selecting ALL permissions in the script with the script in the /system/etc/init.d folder correct? the permissions must be done while the script is in the init.d folder. If you make the permissions before moving the script over to the init.d folder, it will not work. It should look like rwxrwxrwx (Read Write eXecute) for the User, Group & Other fields.
How do get to the permissions? I didn't see that. Also, does anyone have a link to the original cm7 kernel to replace glitch if it doesn't work again?
Never mind. Got the permissions set and it still starts out loud, this is ridiculous.
wow... sounds like your phone just doesn't like you. haha.. kidding.
another thing you can do is use Script Manager from the Market.
run script manager
navigate to script (doesn't matter what folder the script is in)
select script (window pops up)
select "Su" (android skull & bone crosses icon)
select "Edit"
select "File Editor" (make sure the settings are what you want)
press the phones menu button to save (you may be asked to save again when pressing the back button to go one screen back, of course save it again.)
select "Run" (window changes)
select "Close"
you need not to reboot or set permissions using Script Manager, so go ahead and test.
if this works, you need to set the script to run at every boot using Script Manager by selecting the script again and select "Boot" (gear looking icon) and run again. (Su should still be selected as well)
if you end up tweaking the script again, just select "Run" after you are done editing, then "Close". no need to reboot.
IF this too does not work, then you might want to try a fresh install of CM7+Glitch without any other extras, besides the script just for testing. and if you are not on the latest CM nightly, i suggest you update to it.
Boo, my phone does hate me! It must know that I want a Galaxy 2 lol. Well I tried the script manager and it didn't improve. Right now I am on MIUI and like it but could try the CM7. Both ROMs with glitch 13 gave me the same issue. I wonder if my speaker is messed up or somethingm although previously on bionix it was okay...
Hi everyone,
I just did a clean install of omega v5.0 on my galaxy s4 (international version i9505). I've been playing around with the ViPER4Android mod and I've followed the following instructions:
1. Extract and copy ViPER4Android_FX/XHiFi.apk to /system/app/*here*
2. Change apk permission to rw-r-r (644). Reboot.
3. Run FX/XHiFi app from drawer, allow root access.
4. When driver installation prompt, choose Yes to "Install/Update".
5. Choose correct CPU Type. (Refer CPU Driver List)
6. After installation done, Reboot device.
7. If you want use only V4A, follow option1. If you want other existing effects to work, follow option2.
--->>Option1.
-----------8. Choose V4A(either fx or xhifi) in sound settings > music effects (Don't worry, both fx and xhifi will run together.)
-----------9. Make sure in V4A(both fx and xhifi), in menu option, FX Compatible Mode is set to Normal Mode.
-----------10. Download IRS and extract the .irs files to <storage>/ViPER4Android/Kernel/*here*
-----------11. Enjoy.
--->>Option2.
-----------8. Open up both V4A(both fx and xhifi), in menu option, FX Compatible Mode set to Compatible Mode.
-----------9. Download IRS and extract the .irs files to <storage>/ViPER4Android/Kernel/*here*
-----------10. Enjoy.
0. MAKE SURE YOU HAVE CHOSE THE CORRECT DRIVER. Refer OP.
0. MAKE SURE YOU HAVE BUSYBOX INSTALLED
1. Uninstall, reboot. Reinstall, Choose correct driver, reboot.
2. Don't use compatible mode yet, go to sound settings>music effects> and choose v4a(either fx or xhifi). Test.
3. If not working, switch to compatible mode, reboot, go to sound settings>music effects> and select previous effect. Test.
4. If not working, activate safe mode, reboot. Test.
5. If still not working, check
None of the instructions I followed above worked. Also, instead of moving the apk to system/app, I also tried installing as a normal apk and following the rest of the instructions and there has been no sound effect at all. Is there anything I'm missing out? Could anyone that managed to install v4a on the i9505 share with me how you got it to work?
Thanks in advance.
I've had a similar problem but with a Verizon S4. I've installed the apk normally, I've moved it to the /system/app folder and set the permissions accordingly, downloaded the correct drivers, etc. Close, but no cigar.
mrq701 said:
Hi everyone,
I just did a clean install of omega v5.0 on my galaxy s4 (international version i9505). I've been playing around with the ViPER4Android mod and I've followed the following instructions:
1. Extract and copy ViPER4Android_FX/XHiFi.apk to /system/app/*here*
2. Change apk permission to rw-r-r (644). Reboot.
3. Run FX/XHiFi app from drawer, allow root access.
4. When driver installation prompt, choose Yes to "Install/Update".
5. Choose correct CPU Type. (Refer CPU Driver List)
6. After installation done, Reboot device.
7. If you want use only V4A, follow option1. If you want other existing effects to work, follow option2.
--->>Option1.
-----------8. Choose V4A(either fx or xhifi) in sound settings > music effects (Don't worry, both fx and xhifi will run together.)
-----------9. Make sure in V4A(both fx and xhifi), in menu option, FX Compatible Mode is set to Normal Mode.
-----------10. Download IRS and extract the .irs files to <storage>/ViPER4Android/Kernel/*here*
-----------11. Enjoy.
--->>Option2.
-----------8. Open up both V4A(both fx and xhifi), in menu option, FX Compatible Mode set to Compatible Mode.
-----------9. Download IRS and extract the .irs files to <storage>/ViPER4Android/Kernel/*here*
-----------10. Enjoy.
0. MAKE SURE YOU HAVE CHOSE THE CORRECT DRIVER. Refer OP.
0. MAKE SURE YOU HAVE BUSYBOX INSTALLED
1. Uninstall, reboot. Reinstall, Choose correct driver, reboot.
2. Don't use compatible mode yet, go to sound settings>music effects> and choose v4a(either fx or xhifi). Test.
3. If not working, switch to compatible mode, reboot, go to sound settings>music effects> and select previous effect. Test.
4. If not working, activate safe mode, reboot. Test.
5. If still not working, check
None of the instructions I followed above worked. Also, instead of moving the apk to system/app, I also tried installing as a normal apk and following the rest of the instructions and there has been no sound effect at all. Is there anything I'm missing out? Could anyone that managed to install v4a on the i9505 share with me how you got it to work?
Thanks in advance.
Click to expand...
Click to collapse
im having the same issue - follow this thread ...some users are helping me out - - - http://forum.xda-developers.com/showthread.php?p=42958622\
That worked for me. Thanks a ton, mate.
Sent from my SCH-I545
Hello,
I wrote simple aroma installer for 4 apps and one mod.
Everything runs well, but after I reboot my device, there are no changes done!
This is my aroma config: http://pastebin.com/7LQgaXrp
This is my updater scripts: http://pastebin.com/Nt0bLRJC
As you can see, it's very simple
but I still can't find what is wrong that it doesn't apply selected mods :/
Do you know how to make it work?
Can you upload your aroma log as well, when I get to a PC ill take a look at your scripts but having the log can often help for quicker results
Sent from my Nexus 7 using Tapatalk 2
ok got to pc,
so first of all you're not setting permissions to the apps/mods being installed so yeah, that alone will keep them from working
also i see everything is going to /system, and in truth a lot of these are better suited for /data/app , but i guess thats your choice.
also, just a suggestion, but maybe just mount once data and system in the beginning rather than in each if/endif
and being this is so small feel free to just uncomment your set_perms at the end just do it all there (fix your permissions)
and not sure how you have the rest of the .zip set up, but you have your apps coming from lets say c/YouTube for example, and then going to /system
are these again in a folder like c/YouTube/app/youtube.apk ?
just wondering as you want to make sure its installed to /system/app or data/app
also not a huge deal but you may want to get rid of or at least change placement of those set_progress, i mean no biggy but when everything is completed you know
other than this all looks good! if after the changes things still dont work, post your new scripts as well as aroma log
best of luck!
Ok so I was having trouble getting viper audio mod to work with cm 11 based roms so after consulting with GoblinZ it seems he and irocevo figured it out and shared with me what was wrong. To start when i downloaded viper and installed it, removed dsp manager with titanium backup and installed viper audio drivers, it worked great.... Until I rebooted my phone then it was like I never installed the drivers, but they were still installed... So that was the issue I was having, couldn't get it to stick, so this is how goblinz instructed me to get it to work.
First you need viper audio mod [http://forum.xda-developers.com/showthread.php?t=2191223
Now download viper audio zip file and open with your file explorer, I'm using es file Explorer you must enable Root Explorer and Mount
/system as writable. Ok now don't install the viper apk located inside the zip just extract it to any folder you like, now copy the Viper audio apk file to /system/priv-app
Ok now one more thing, You must change the permissions on the apk file, so in es file Explorer you long press on the file, then press on more/properties then permissions, change them to
Owner: read write execute
Group: read write
Others: read
Now reboot and then you should see Viper4Android as an app in your app drawer, open then install audio drivers then at the top right of your screen you'll see three dots which is the menu for the app, check FX compatibility mode and check compatible, then check UI setting to moderate or expert.
That's it your done, hopefully this helps someone out cause I was really frustrated that i couldn't get this to work cause imo this is the best audio mod for Android.
Enjoy
Sent from my EVO using XDA Premium 4 mobile app
Or just install the app. Open titanium and convert to system app.
Open Viper and install driver of choice.
Dont reboot yet.
Edit your build.prop and change lpa.decode=false.
Reboot.
Profit.
The build.prop edit is the most important one. The only Roms it doesnt work is the last build of cm10.2 and that was because CM messed the rom and made it impossible for user to disable low power audio. Thus V4A didnt work no matter what. Evrrything else sense aosp cm etc just edit the build.prop entry and you are good to go.
Sent from my EVO using Tapatalk
Good stuff thanks
Sent from my EVO using XDA Premium 4 mobile app
..
Does the Viper mod have the option to increase the phones in call volume on the earpiece?
Sent from my EVO using XDA
This took me some hours this evening and a lot of trial and error but I was able to get it working. Note: if you are novice at playing with system files, don't bother to try this. It's not for the faint at heart. I can't provide support. You will also need Script Manger so you can fix permissions after placing the files. You must manually do all of this since we can't flash the zips! Make sure to Freeze the Sound Alive apk with TB also so there are no other music effects apps. Here's what I had to do:
1. Follow the instructions at this post first, extracting and placing files. Just don't reboot yet (thanks @TiTiB): http://forum.xda-developers.com/showpost.php?p=62365948&postcount=37
2. Download the two files mentioned here in this thread. You only need the audio policy script from the Lolliviper zip file to place in the system folder. Place the others from the ViPER4Android-supolicy.zip where needed: http://forum.xda-developers.com/galaxy-tab-s/general/how-to-installing-viper4android-v4a-t3136025
3. Take the latest Viper apk and place it in the system/priv-app folder.
4. Remember, make sure set all the needed permissions as you go along for ALL files above or none of this will work!
5. Reboot.
6. Open the Viper app, select the driver you want. Reboot.
7. If using Poweramp, you may or may not see the MusicFX control button whether you have it selected in advanced settings or not. I did not see it but it made no difference. Open the Viper app, turn on the settings and start playing music. Voila, it works! Works on my speaker too. Apparently permissive kernel isn't essential to make this work and that is the beauty of all this., because you can not use SElinux mode app on this kernel as some of you may know.
Have fun and good luck, at least you might be able to do this in much shorter time than I did.
One other thing I have found. You must set the scripts in system/su.d to run on boot with script manager so Viper will run after each reboot.
You can also get it to work by the following.
Install xposed
Install Wanam exposed module
In Wanam, under Security hacks
Disable Knox notification (I manually remove Knox)
Disable SEAndroid (changes to passive)
Install Viper4Android and update the driver
bishop0114 said:
You can also get it to work by the following.
Install xposed
Install Wanam exposed module
In Wanam, under Security hacks
Disable Knox notification (I manually remove Knox)
Disable SEAndroid (changes to passive)
Install Viper4Android and update the driver
Click to expand...
Click to collapse
I could not get Xposed installed after rooting, tried the latest apk, etc. I read on that thread Xposed has issues with stock LP Samsung ROMs so I just forgot about it. I could have tried placing the files in the flashable zip manually but it didn't seem worth the risk. I'm glad you got it going because that way sounds faster.