Viper4android - Moto X Q&A

Has anyone gotten v4a to work on the moto x? I used omit on the htc one and loved it!
Sent from my XT1056 using Tapatalk 2

mhsbrian said:
Has anyone gotten v4a to work on the moto x? I used omit on the htc one and loved it!
Sent from my XT1056 using Tapatalk 2
Click to expand...
Click to collapse
I got it to install and I could change settings and stuff but nothing seemed to be actually happening. I used it a lot on my GSII but I can't get it working on my at&t moto x.

mhsbrian said:
Has anyone gotten v4a to work on the moto x? I used omit on the htc one and loved it!
Sent from my XT1056 using Tapatalk 2
Click to expand...
Click to collapse
I'm using it on my AT&T Moto X right now. If you would like me to throw together a guide on how I installed it, I can a little later today.

TheNibbler said:
I'm using it on my AT&T Moto X right now. If you would like me to throw together a guide on how I installed it, I can a little later today.
Click to expand...
Click to collapse
If you threw together a guide, that would be amazing. I can't get v4a to stick. Probably has something to do with the fact that every time I try to install busybox, it is unsuccessful, so any words of wisdom would be amazing because I have an awesome stereo in my car, and would like to get better sound quality out of the Moto X. Thanks.

These instructions are for the AT&T Moto X using the Root/Write Protection Bypass by jcase. They are from memory but should be accurate.
1. Make sure phone is rooted
2. Reboot into recovery to allow modifications to /system
3. Install the Busybox installer from the play store and use it to install Busybox on your device.
4. Open up /system/build.prop in a text editor (I used root explorer).
5. Change the line
Ipa.decode=true to lpa.decode=false
lpa.use-stagefright=true to lpa.use-stagefright=false
6. Extract and copy ViPER4Android_FX/XHiFi.apk to /system/app/*here*
7. Change apk permission to rw-r-r (644). Reboot into recovery.
8. Run the Viper4Android app from drawer, allow root access.
9. When driver installation prompt, choose Yes to "Install/Update" and select CortexA9/15 with NEON.
10. Reboot normally.

TheNibbler said:
These instructions are for the AT&T Moto X using the Root/Write Protection Bypass by jcase. They are from memory but should be accurate.
1. Make sure phone is rooted
2. Reboot into recovery to allow modifications to /system
3. Install the Busybox installer from the play store and use it to install Busybox on your device.
4. Open up /system/build.prop in a text editor (I used root explorer).
5. Change the line
Ipa.decode=true to lpa.decode=false
lpa.use-stagefright=true to lpa.use-stagefright=false
6. Extract and copy ViPER4Android_FX/XHiFi.apk to /system/app/*here*
7. Change apk permission to rw-r-r (644). Reboot into recovery.
8. Run the Viper4Android app from drawer, allow root access.
9. When driver installation prompt, choose Yes to "Install/Update" and select CortexA9/15 with NEON.
10. Reboot normally.
Click to expand...
Click to collapse
Worked like charm.. Thanks a lot

TheNibbler said:
These instructions are for the AT&T Moto X using the Root/Write Protection Bypass by jcase. They are from memory but should be accurate.
1. Make sure phone is rooted
2. Reboot into recovery to allow modifications to /system
3. Install the Busybox installer from the play store and use it to install Busybox on your device.
4. Open up /system/build.prop in a text editor (I used root explorer).
5. Change the line
Ipa.decode=true to lpa.decode=false
lpa.use-stagefright=true to lpa.use-stagefright=false
6. Extract and copy ViPER4Android_FX/XHiFi.apk to /system/app/*here*
7. Change apk permission to rw-r-r (644). Reboot into recovery.
8. Run the Viper4Android app from drawer, allow root access.
9. When driver installation prompt, choose Yes to "Install/Update" and select CortexA9/15 with NEON.
10. Reboot normally.
Click to expand...
Click to collapse
Thanks so much!

TheNibbler said:
These instructions are for the AT&T Moto X using the Root/Write Protection Bypass by jcase. They are from memory but should be accurate.
1. Make sure phone is rooted
2. Reboot into recovery to allow modifications to /system
3. Install the Busybox installer from the play store and use it to install Busybox on your device.
4. Open up /system/build.prop in a text editor (I used root explorer).
5. Change the line
Ipa.decode=true to lpa.decode=false
lpa.use-stagefright=true to lpa.use-stagefright=false
6. Extract and copy ViPER4Android_FX/XHiFi.apk to /system/app/*here*
7. Change apk permission to rw-r-r (644). Reboot into recovery.
8. Run the Viper4Android app from drawer, allow root access.
9. When driver installation prompt, choose Yes to "Install/Update" and select CortexA9/15 with NEON.
10. Reboot normally.
Click to expand...
Click to collapse
Awesome! Worked for Sprint version as well!!:victory:

I'm on Verizon and cannot get busybox to install. I've tried both locations and it won't take. There is an option for custom location but I have no idea where to put it
Anyone else on Verizon get this to work?
---------- Post added at 06:49 PM ---------- Previous post was at 06:44 PM ----------
delete, found the answer

So I was able to get viper installed. However it seems to work sporadically. It'll work on Pandora but not Apollo or Google music.
Any tips to get it to work?? I downloaded a few equalizer apps from the ,market and they work fine. I did ,take sure to select viper as my eq app BTW. I froze the others and it still didn't work consistently.
Sent from my Nexus 7 using XDA Premium HD app

I'm on 4.4.2 and I was able to get V4A FX working, but I cannot get V4A XHIFI to work, anyone get this working? (on any moto x at all, not just 4.4.2?)
Thanks.

mslam02 said:
I'm on 4.4.2 and I was able to get V4A FX working, but I cannot get V4A XHIFI to work, anyone get this working? (on any moto x at all, not just 4.4.2?)
Thanks.
Click to expand...
Click to collapse
Xhifi is only up to 4.3 support right now.
Sent from my XT1058 using xda premium

Related

How to Disable Xposed on Lollipop when stuck in Bootloop

I have xposed running on my Nexus 5 lollipop 5.0.1.
After downloading and enabling a couple modules my phone is now stuck in a bootloop.
I tried clearing dalvik and cache it didn't help.
Is it possible to disable xposed from recovery?
EDIT: Solved.
Boot into Recovery (Power + Volume Down)
TWRP > Advanced > Terminal command
Create a file /data/data/de.robv.android.xposed.installer/conf/disabled, which causes Xposed to be bypassed:
Code:
touch /data/data/de.robv.android.xposed.installer/conf/disabled
Click to expand...
Click to collapse
Boot into Recovery (Power + Volume Down)
TWRP > Advanced > Terminal command
Create a file /data/xposed/disabled, which causes Xposed to be bypassed as well:
Code:
touch /data/xposed/disabled
Click to expand...
Click to collapse
Didn't work. Still stuck in bootloop.
bseos said:
Didn't work. Still stuck in bootloop.
Click to expand...
Click to collapse
what modules you have activated?
or
mv /system/lib/*.*.orig /system/lib/*.*
mv /system/bin/*.orig /system/bin/*
opssemnik said:
what modules you have activated?
Click to expand...
Click to collapse
It was between two modules. Can't remember the first one but the last one was XInstaller.
Anyway, got it solved using the below method:
Boot into Recovery (Power + Volume Down)
TWRP > Advanced > Terminal command
Create a file /data/data/de.robv.android.xposed.installer/conf/disabled, which causes Xposed to be bypassed as well:
Code:
touch /data/data/de.robv.android.xposed.installer/conf/disabled
very good
bseos said:
It was between two modules. Can't remember the first one but the last one was XInstaller.
Anyway, got it solved using the below method:
Boot into Recovery (Power + Volume Down)
TWRP > Advanced > Terminal command
Create a file /data/data/de.robv.android.xposed.installer/conf/disabled, which causes Xposed to be bypassed as well:
Code:
touch /data/data/de.robv.android.xposed.installer/conf/disabled
Click to expand...
Click to collapse
XInstaller seems to be causing a few issues, and I don't think its the app itself but the apps it allows you to install instead. I had the same issue after installing xInstaller. But now that you figured this out maybe I can try a few other apps out like xstana which for somereason refuses to install on lollipop devices...
.Ryker said:
XInstaller seems to be causing a few issues, and I don't think its the app itself but the apps it allows you to install instead. I had the same issue after installing xInstaller. But now that you figured this out maybe I can try a few other apps out like xstana which for somereason refuses to install on lollipop devices...
Click to expand...
Click to collapse
After disabling it I flashed the new xposed-arm-20150308.zip and installed XposedInstaller_3.0-alpha2.apk (I was on alpha1 previously)
Re-enabled xposed (deleted "disabled" file) and all is working fine now.
This thread definitely either needs to be made a sticky, or the contents needs to be in one of the already made sticky threads IMHO
Cheers
//edit
I tried this out on my phone to test (my xposed stuff is working just fine) but it doesn't seem to have disabled xposed at all?
Ex, app settings still functions (set my play store to be at 480 DPI and it's still opening in 480 DPI as it should...)
I made the necessary file you said with fx file manager, not through TWRP recovery though... I don't think it should make a difference though how I made the file, just that it's there.
Maybe my permissions on the file are messed up, I just thought of that..
//edit 2
Yup my perms were messed up, xposed is now disabled for me. Cheers for the info, now I know what to do when some shady looking module backfires on me lol
Thank you so much!!! This worked perfectly on Sprint LG G3 using Candy5 ROM!! Saved me!!
Just to report that the method failed on a Samsung Galaxy S6 Edge (SM-G925F).
I created succesfully the disabled file, but I was still having bootloops.
So I thought I forgot to set the file to 755, but then TWRP told me:
Code:
Updating partition details...
...done
E: Resource (font)-(fixes) failed to load
Kernel does not have support for reading SELinux contexts.
MTP Enabled
Now I hope to fix everything by reflashing the firmware again...
After successfully disabling xposed in order to get the device to boot, how do we reenable it? Because after uninstalling the module which caused the problem the framework is "not active". A reboot did not work.
Nokiacrazi said:
After successfully disabling xposed in order to get the device to boot, how do we reenable it? Because after uninstalling the module which caused the problem the framework is "not active". A reboot did not work.
Click to expand...
Click to collapse
Delete the "disabled" file in the folder op showed
jkyoho said:
Delete the "disabled" file in the folder op showed
Click to expand...
Click to collapse
Silly question but how can I delete it? I tried locating it using HTC file manager and es file explorer but cannot locate it.
Is there a command I can use using terminal emulator or something?
Thanks
Sent from my HTC One_M8 using XDA Free mobile app
Nokiacrazi said:
Silly question but how can I delete it? I tried locating it using HTC file manager and es file explorer but cannot locate it.
Is there a command I can use using terminal emulator or something?
Thanks
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
You need you use Root explorer or Es file explorer that supported Root and locate to /data/data/de.robv.android.xposed.installer/conf
Method 2:
You can even delete the "disabled" file in recovery by using file management, if you are using TWRP. Same as previous method, just locate to /data/data/de.robv.android.xposed.installer/conf
jkyoho said:
You need you use Root explorer or Es file explorer that supported Root and locate to /data/data/de.robv.android.xposed.installer/conf
Method 2:
You can even delete the "disabled" file in recovery by using file management, if you are using TWRP. Same as previous method, just locate to /data/data/de.robv.android.xposed.installer/conf
Click to expand...
Click to collapse
Thanks, method 2 worked a treat.
For some reason, even though I have root access, it wasn't showing in either root explorer or es file explorer, however, when looking through TWRP file management was all there.
jkyoho said:
Delete the "disabled" file in the folder op showed
Click to expand...
Click to collapse
can you please explain the process.
i entered the twrp and advanced and terminal command and went through the shown path yet i didnt see the file "disabled"
he has said to create a file; how could i create a file??
please explain the process...
cybercop007 said:
can you please explain the process.
i entered the twrp and advanced and terminal command and went through the shown path yet i didnt see the file "disabled"
he has said to create a file; how could i create a file??
please explain the process...
Click to expand...
Click to collapse
If you can't normally boot to system, boot to recovery(twrp or some other custom recovery which has file management function)
Try copy a small file like host or something, paste it the that /data/data/dev.*****installer/conf folder and rename it "disabled".
flashable zip´s
starbase64 said:
flashable zip´s
Click to expand...
Click to collapse
these will be very good to have! thank you!
starbase64 said:
flashable zip´s
Click to expand...
Click to collapse
Thank you!!!

[FIX] SCRFIX, a fix for DT2W/Sw2W lock screen freeze

The included file is a binary that runs a daemon that fixes the lockscreen freeze that happens with dt2w/sw2w kernels. It requires busybox to be installed on your device. If your screen is still unresponsive the first time you attempt to wake your device; shut your screen off, wait a couple seconds, and try again and it will usually work.
The executable will do nothing on its own, so you must either have it start on boot with an init.d script or manually in terminal. It has to be ran as root.
To install the zip boot into recovery and install it using your recovery's standard install method, like installing a kernel or ROM.
To install the binary simply put the file in /system/bin and give it executable permissions
Recovery installer zip:
https://docs.google.com/file/d/0B_hgNZE_j5sVd0Itb1V4RGhhOGc/edit?usp=docslist_api
Binary:
https://docs.google.com/file/d/0B_hgNZE_j5sVLU9wdDEzamFUV0U/edit?usp=docslist_api
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.
What this app does? How did you find it?
and after put in system/bin what to do next? how to run it?
Run it from the terminal command line, and it will continue to run in the background.
Its a quick and dirty fix that resets the touch screen driver when the screen is off.
If you copied the file to system bin you should be able to just type "scrfix" in your terminal and it will run in the background until your next reboot.
Alternatively you can just call it in an init.d script to have it start automatically on every boot.
I use SManager , give to scrfix su and boot privs it will work?
I haven't used that app personally, but it sounds like it should. Its normal for the program to seem like it exits because it spawns a child process that runs in the background that is owned by init (PID 1)
Or if you want to launch it manually, you can launch it in Terminal Emulator, but it will need started again on each reboot.
There is now a link to an installer zip for installation from recovery mode that comes with an init.d script included, for anyone using this method, please let me know if you encounter any issues with it. You may need to enable "trust system user" in your su application for it to work. The recovery installer was made with the ZipMe application.
Will this enable DT2W in cm12
Sent from my Moto G using Tapatalk
imranaryan said:
Will this enable DT2W in cm12
Sent from my Moto G using Tapatalk
Click to expand...
Click to collapse
If you will read the title, you would realize that this mod is a fix for a very common problem faced by dt2w users. If you want dt2w, flash a custom kernel like optimus.
I just tried this on my Moto E 2015 and I ended up flashing a zip I modified when I tried it on my Moto G some time ago. I've found that it does not work when applying dt2w with an app such as Kernel Adiutor. It does work if you apply dt2w with an init.d script, and make it so the scrfix script is ran before the dt2w script. You just have to change the numbers in the beginning of the script name to something like 01 and 02 with the scrfix script having the smaller number.
Thanks for the info, I may upload an updated zip that has the name change to make sure it runs first. Some times too (on my phone atleast) when the screen isn't responsive I'll turn the screen off for 3-5 seconds and try again and it'll usually respond.
---------------------------------------------------
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.
Please donate at:
http://www.PayPal.me/elrod16
Every bit helps, thanks!
elrod16 said:
Run it from the terminal command line, and it will continue to run in the background.
Its a quick and dirty fix that resets the touch screen driver when the screen is off.
If you copied the file to system bin you should be able to just type "scrfix" in your terminal and it will run in the background until your next reboot.
Alternatively you can just call it in an init.d script to have it start automatically on every boot.
Click to expand...
Click to collapse
i know this is an old forum but I just found it. How can I call it in an init.d script?
Just adding the line
scrfix
to a script.
---------------------------------------------------
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.
Please donate at:
http://www.PayPal.me/elrod16
Every bit helps, thanks!
elrod16 said:
Just adding the line
scrfix
to a script.
---------------------------------------------------
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.
Please donate at:
http://www.PayPal.me/elrod16
Every bit helps, thanks!
Click to expand...
Click to collapse
Would this be correct?
#!/system/bin/sh
/system/bin/scrfix
exit 0
Sent from my Moto E 2015 using XDA Labs
V-Droid said:
Would this be correct?
#!/system/bin/sh
/system/bin/scrfix
exit 0
Sent from my Moto E 2015 using XDA Labs
Click to expand...
Click to collapse
Yes, you'll also need another script with this:
#!/system/bin/sh
echo "2" > /sys/android_touch/doubletap2wake
This one needs to run after the previous script so you'll have to name them 98scrfix and 99dt2w. Also make sure their permissions are 0755.
---------- Post added at 08:46 PM ---------- Previous post was at 08:35 PM ----------
amarc78 said:
Yes, you'll also need another script with this:
#!/system/bin/sh
echo "2" > /sys/android_touch/doubletap2wake
This one needs to run after the previous script so you'll have to name them 98scrfix and 99dt2w. Also make sure their permissions are 0755.
---------- Post added at 08:46 PM ---------- Previous post was at 08:35 PM ----------
Click to expand...
Click to collapse
Im not able to change the script permissions, tried root browser but gave me an error. How can I change the permissions?
By the way sorry for the constant questions
Sent from my Moto E 2015 using XDA Labs
V-Droid said:
Im not able to change the script permissions, tried root browser but gave me an error. How can I change the permissions?
By the way sorry for the constant questions
Sent from my Moto E 2015 using XDA Labs
Click to expand...
Click to collapse
Try Root Explorer or ES File manager. As long as your rooted it should work.
amarc78 said:
Try Root Explorer or ES File manager. As long as your rooted it should work.
Click to expand...
Click to collapse
Still no luck, I tried root browser, root explorer and es file explorer all of them gave me the same error.
I also tried moving the file from the external SD card into the internal memory.
By the way, the way I create the scripts is in a .txt file, is this correct?
Sent from my Moto E 2015 using XDA Labs
V-Droid said:
Still no luck, I tried root browser, root explorer and es file explorer
Sent from my Moto E 2015 using XDA Labs
Click to expand...
Click to collapse
You need to put them in /system/etc/initd not on your sdcard.
amarc78 said:
You need to put them in /system/etc/initd not on your sdcard.
Click to expand...
Click to collapse
Thank you very much for all of your help, finally managed to change the permissions :laugh:
Sent from my Moto E 2015 using XDA Labs

Viper4android

I went back to using KitKat bc I was having issues with viper4android on Lollipop. Now I get notified that the driver failed to install. Can someone please tell me how to fix this? I'm rooted and I have busybox and supersu installed.
Same here. First I was on Lollipop and the drivers would install, but the effects wouldnt work. Back to KK and now it's saying that the Busybox installation found on my device does not work.
jwilla11 said:
Same here. First I was on Lollipop and the drivers would install, but the effects wouldnt work. Back to KK and now it's saying that the Busybox installation found on my device does not work.
Click to expand...
Click to collapse
I went back to Lollipop and it works now. Follow these steps:
To anyone on this rom who wants the instructions to install viper its very simple. Go here and download the GalaxyMod V2. Flash it through flashfire. Then go here and download Viper4Android or use standard from their site. Install viper like normal, choose your driver and reboot. After reboot go into poweramp and go to settings - audio - advanced tweaks - and uncheck directly control volume, and directly control bluetooth volume. Also make sure MusicFX is unchecked and all the equalizers are off so not to interfere with Vipers Sound. Open viper and click driver status and you should see that it is supported and processing.
I still install the ViperSU policy just in case I have any issues.
@dkeepitabuck @jwilla11
You also have to edit the following lines in /system/build.prop
Ipa.decode=true to lpa.decode=false
tunnel.decode=true to tunnel.decode=false
lpa.use-stagefright=true to lpa.use-stagefright=false
Click to expand...
Click to collapse
dkeepitabuck said:
I went back to Lollipop and it works now. Follow these steps:
To anyone on this rom who wants the instructions to install viper its very simple. Go here and download the GalaxyMod V2. Flash it through flashfire. Then go here and download Viper4Android or use standard from their site. Install viper like normal, choose your driver and reboot. After reboot go into poweramp and go to settings - audio - advanced tweaks - and uncheck directly control volume, and directly control bluetooth volume. Also make sure MusicFX is unchecked and all the equalizers are off so not to interfere with Vipers Sound. Open viper and click driver status and you should see that it is supported and processing.
I still install the ViperSU policy just in case I have any issues.
Click to expand...
Click to collapse
thisisapoorusernamechoice said:
@dkeepitabuck @jwilla11
You also have to edit the following lines in /system/build.prop
Ipa.decode=true to lpa.decode=false
tunnel.decode=true to tunnel.decode=false
lpa.use-stagefright=true to lpa.use-stagefright=false
Click to expand...
Click to collapse
I did everything you guys said except install the ViperSU policy, and it didn't work (V4A driver installed, but status was abnormal). Then I installed the ViperSU policy zip through Flashfire and now V4A works! Thanks so much. I don't know if editing build.prop is necessary, but I did it just in case. I now know that installing the ViperSU policy zip is necessary.
To the part about Poweramp: I use Walkman as my music player, which works fine with V4A. I just went into my application manager and disabled MusicFX.
To the OP, I didn't know how to edit build.prop until now, so in case you don't know, here's how:
1. download ES File Explorer.
2. click the symbol in the top left to pull up more options.
3. scroll down to Root Explorer and tap on it to turn it on.
4. find build.prop in system folder, tap on it, choose open with ES Note Editor, and edit in what the guy above said.

How to install Viper4android Fx on Moto X Android 6

Hi guys, I could not run Viper4android application on my device (android 6) . I haved installed apk then install driver . But Not thing change in sound effect. I tried to search and did not find out any error?
I need some help to run app with effect sound when play music!
Thank inadvance!
Well mine has problem of installing the sound driver.
通过我的 XT1096 上的 Tapatalk发言
duongnv1996 said:
Hi guys, I could not run Viper4android application on my device (android 6) . I haved installed apk then install driver . But Not thing change in sound effect. I tried to search and did not find out any error?
I need some help to run app with effect sound when play music!
Thank inadvance!
Click to expand...
Click to collapse
How did you install the viper4android via apk or you flashed from recovery?
duongnv1996 said:
Hi guys, I could not run Viper4android application on my device (android 6) . I haved installed apk then install driver . But Not thing change in sound effect. I tried to search and did not find out any error?
I need some help to run app with effect sound when play music!
Thank inadvance!
Click to expand...
Click to collapse
In order to install ViPER4Android, you'll need your system to be properly rooted, BusyBox must be installed, and SELinux Mode must be "Permissive".
I recommend this BusyBox installer, and you can get SELinux Mode Changer from here.
Then, after everything is properly set up, you must also disable your ROM (e.g. CyanogenMod-based ROMs' AudioFX)and/or player (e.g. Poweramp's equalizer)'s built-in equalizer, and switch ViPER4Android's FX Compatible mode from "Normal" to "Compatible".
duongnv1996 said:
Hi guys, I could not run Viper4android application on my device (android 6) . I haved installed apk then install driver . But Not thing change in sound effect. I tried to search and did not find out any error?
I need some help to run app with effect sound when play music!
Thank inadvance!
Click to expand...
Click to collapse
I was able to make V4A work on my Moto X 2014 with a fix.
If you do not have Busybox or permissive SELinux, follow the instructions our mate's posted above:
KazuhiroYasei said:
In order to install ViPER4Android, you'll need your system to be properly rooted, BusyBox must be installed, and SELinux Mode must be "Permissive".
I recommend this BusyBox installer, and you can get SELinux Mode Changer from here.
Then, after everything is properly set up, you must also disable your ROM (e.g. CyanogenMod-based ROMs' AudioFX)and/or player (e.g. Poweramp's equalizer)'s built-in equalizer, and switch ViPER4Android's FX Compatible mode from "Normal" to "Compatible".
Click to expand...
Click to collapse
After Busybox installed and SELinux on permissive, you flash the Viper zip and install the driver. Right after that you open a root enabled file manager and find system>vendor>etc. You'll see an audio_effects.conf.
(I suggest making a safe copy of this file).
Rename the original audio_effects.conf to audio_effects.bak.
Save and reboot. Now try using v4a again.
brunoperissotti said:
I was able to make V4A work on my Moto X 2014 with a fix.
After Busybox installed and SELinux on permissive, you flash the Viper zip and install the driver. Right after that you open a root enabled file manager and find system>vendor>etc. You'll see an audio_effects.conf.
(I suggest making a safe copy of this file).
Rename the original audio_effects.conf to audio_effects.bak.
Save and reboot. Now try using v4a again.
Click to expand...
Click to collapse
Was this procedure required for V4A to work on your Victara? Mine worked in every ROM I tested (all Marshmallow-based) by following the steps you quoted.
KazuhiroYasei said:
Was this procedure required for V4A to work on your Victara? Mine worked in every ROM I tested (all Marshmallow-based) by following the steps you quoted.
Click to expand...
Click to collapse
Yes. I was only able to enjoy v4a after this procedure.
It's worth pointing out that V4A is going to F up your Moto Voice
Popping into this thread real quick to provide some info,
Using compatibility mode with V4A is bad news, causes extra battery drain and problems with some apps.
For every single rom and device I've used 5.0+ I've followed the same procedure to install V4A, without using compatibility mode, without having to delete a file every time, etc.
Flash the "lolliviper" zip attached to this OP.
Followed by the "Build.Prop-Tweaks" and "Soundfix-LibFiles" attached to this post.
You'll also need a way of setting selinux to permissive after every boot if you're using CM or something else with selinux set to enforced. Something like SELinuxModeChanger available here will work.
If you don't have busybox installed, V4A will tell you and help you install it.
The V4A version included in the "lolliviper" zip is not the newest , you'll need to "Check Update" via the 3 dot menu and install the latest apk.
After all this, install the driver via the V4A app, reboot, and you're golden.
Flipz77 said:
It's worth pointing out that V4A is going to F up your Moto Voice
Click to expand...
Click to collapse
Didn't know that. I was only able to set v4a on a custom ROM, so that ship was long gone hahaha
it just stops working?
brunoperissotti said:
Didn't know that. I was only able to set v4a on a custom ROM, so that ship was long gone hahaha
it just stops working?
Click to expand...
Click to collapse
Actually it still "works" because it detects your launch phrase, but after that, half of the time it just hangs without hearing your command. Sometimes it'll randomly work, but it was too much of a botch to keep it that way. I've now resorted to Noozxoide Pro: it's still a system-wide mod with modes for headset, speaker and BT, but it's installed as a "standard" app, it doesn't mess with your system and it sounds boss!
I ran across this link on a similar search on the google machine, and it made V4A installation a breeze. No manual messing with kernel settings and whatnot: http://forum.xda-developers.com/android/software/viperaudio-viperatmos-3-8-sq-driver-t3289075
Battery life has been fine running this for about a week. I don't use Moto Voice so can't comment on that.
THANKS
brunoperissotti said:
I was able to make V4A work on my Moto X 2014 with a fix.
If you do not have Busybox or permissive SELinux, follow the instructions our mate's posted above:
After Busybox installed and SELinux on permissive, you flash the Viper zip and install the driver. Right after that you open a root enabled file manager and find system>vendor>etc. You'll see an audio_effects.conf.
(I suggest making a safe copy of this file).
Rename the original audio_effects.conf to audio_effects.bak.
Save and reboot. Now try using v4a again.
Click to expand...
Click to collapse
Thanks a lot, I was already discouraged, tried several versions of viper, on diferent roms, this was the only solution, but is necessary to remember that for this file to appear in the folder, you need to open the application and save a profile, even if empty, without it you can not find the file audio_effects
If u root ur device using magisk, u can install viper magisk module...it works fine on android 6.0 with selinux enforcing..
Sent from a Motobot

[SNAPDRAGON][EXYNOS] ViPER4Android [ZIP][FLASHABLE]

Disclaimer: I will take no responsibility if flashing this zip somehow causes you to go deaf, scares your cat, receiving of noise complaints from your neighbors, development of anti-social behavior, getting hit by a bus, a twerking grandmother, broken windows and/or any other imaginable royally screwed possibility.
Q: Will this work on other Samsung devices?
A: Maybe, I see no reason for it not to work on the S8 or S8+. Feel free to test it out and report back.
Credits: @zhuhang for ViPER4Android FX & XHiFI.
@partcyborg, @me2151, and @elliwigy for hooking us up with root.
Features: Systemwide ViPER4Android FX 2.3.4.0 (higher audio processing than newer versions) and ViPER4Android XHiFi.
Installation steps (make sure to read these before downloading the ZIP):
1) Make sure you're rooted.
2) Download either FlashFire (Snapdragon - thank you, @Chainfire) or install TWRP (Exynos).
3) Install BusyBox, to /system/xbin (otherwise, XHiFi will not work, only FX will).
4) Get Titanium Backup, ROM Toolbox PRO, or any similar application.
6) Freeze "Adapt Sound" and "SoundAlive".
5) Flash the attached zip.
6) Grant root permissions to both FX and XHiFi (you might have to uninstall the FX driver within the in-app settings to trigger this, if so, simply reflash the ZIP after having done so and reboot).
7) Reread step six.
8) Profit & enjoy.
Paradoxumical said:
Disclaimer: I will take no responsibility if flashing this zip somehow causes you to go deaf, scares your cat, receiving of noise complaints from your neighbors, development of anti-social behavior, getting hit by a bus, a twerking grandmother, broken windows and/or any other imaginable royally screwed possibility.
Q: Will this work on other Samsung devices?
A: Maybe, I see no reason for it not to work on the S8 or S8+. Feel free to test it out and report back.
Credits: @zhuhang for ViPER4Android FX & XHiFI.
@partcyborg, @me2151, and @elliwigy for hooking us up with root.
Features: Systemwide ViPER4Android FX 2.3.4.0 (higher audio processing than newer versions) and ViPER4Android XHiFi.
Installation steps (make sure to read these before downloading the ZIP):
1) Make sure you're rooted.
2) Download either FlashFire (Snapdragon - thank you, @Chainfire) or install TWRP (Exynos).
3) Install BusyBox, to /system/xbin (otherwise, XHiFi will not work, only FX will).
4) Get Titanium Backup, ROM Toolbox PRO, or any similar application.
6) Freeze "Adapt Sound" and "SoundAlive".
5) Flash the attached zip.
6) Grant root permissions to both FX and XHiFi (you might have to uninstall the FX driver within the in-app settings to trigger this, if so, simply reflash the ZIP after having done so and reboot).
7) Reread step six.
8) Profit & enjoy.
Click to expand...
Click to collapse
Won't installing busybox to system/xbin trip up safety net flagging your device as tampered/rooted? Also, if you have magisk, can't you just install the v4a module right from within magisk? I don't see the point in going through all these extra steps and flagging your device in safety net when you can just install the v4a magisk module. Not trying to be a ****, asking honest questions.
Works perfectly on my T-Mobile N950U! Thanks!
Sent from my SM-N950U1 using Tapatalk
xxx42069 said:
Won't installing busybox to system/xbin trip up safety net flagging your device as tampered/rooted? Also, if you have magisk, can't you just install the v4a module right from within magisk? I don't see the point in going through all these extra steps and flagging your device in safety net when you can just install the v4a magisk module. Not trying to be a ****, asking honest questions.
Click to expand...
Click to collapse
If you have a Snapdragon device, SafetyNet is already tripped due to the nature of the rooting process.
But if you have an Exynos device, by all means, use the Magisk module. This ZIP was intended for the Snapdragon variant (since that's what I have), but works on Exynos variants as well.
i flashed it n nuthin,i cant even find the in-app u wrote about
Was anyone able to install busybox and viper4android after getting rooted? I tried flashing the viper4android zip using flashfire but it doesn't seem to do anything and busybox installer will not install to any system location. Thanks in advance. Also, I have the snapdragon version and rooted using samfail.
lilviet93 said:
Was anyone able to install busybox and viper4android after getting rooted? I tried flashing the viper4android zip using flashfire but it doesn't seem to do anything and busybox installer will not install to any system location. Thanks in advance. Also, I have the snapdragon version and rooted using samfail.
Click to expand...
Click to collapse
same problem with me i flashed it n nothing happened..also u need to use busybox root it's the red icon version u probably using the old gray busybox
mister_propa said:
same problem with me i flashed it n nothing happened..also u need to use busybox root it's the red icon version u probably using the old gray busybox
Click to expand...
Click to collapse
Yeah, I used the old busybody version. I just went back to stock after a few hours of messing around with no results. My main reason for root and accepting the 80% battery limit is viper but since I can't get it working I went back to stock for now. Will try again once there is more development. Let me know if you do get it working.
mister_propa said:
i flashed it n nuthin,i cant even find the in-app u wrote about
Click to expand...
Click to collapse
mister_propa said:
same problem with me i flashed it n nothing happened..also u need to use busybox root it's the red icon version u probably using the old gray busybox
Click to expand...
Click to collapse
lilviet93 said:
Was anyone able to install busybox and viper4android after getting rooted? I tried flashing the viper4android zip using flashfire but it doesn't seem to do anything and busybox installer will not install to any system location. Thanks in advance. Also, I have the snapdragon version and rooted using samfail.
Click to expand...
Click to collapse
When you guys flashed it with Flashfire, which options did you enable/disable? Mind taking a screenshot of the preflash stage for me? Do you see the Flashfire installation screen? You should be able to see the ZIP flash progress script.
As for those having problems with installing BusyBox, if you're using Stericson's, you have to manually grant the storage permission.
Paradoxumical said:
When you guys flashed it with Flashfire, which options did you enable/disable? Mind taking a screenshot of the preflash stage for me? Do you see the Flashfire installation screen? You should be able to see the ZIP flash progress script.
As for those having problems with installing BusyBox, if you're using Stericson's, you have to manually grant the storage permission.
Click to expand...
Click to collapse
Just select the zip and start the flashing process. It went black then the flashfire process starts then phone reboots but no sign of the viper app anywhere. How do I manually grant permission? What is the best way to install busybox?
lilviet93 said:
Just select the zip and start the flashing process. It went black then the flashfire process starts then phone reboots but no sign of the viper app anywhere. How do I manually grant permission? What is the best way to install busybox?
Click to expand...
Click to collapse
I personally used BusyBox Pro by Stericson (he's an amazing developer), but I did have to manually grant the storage permission first by going to: App info > Permissions > Storage (toggle it on).
If this doesn't work, use BusyBox Installer (warning: it's riddled with ads).
As for Flashfire, try enabling the "mount system read/write" option.
Paradoxumical said:
I personally used BusyBox Pro by Stericson (he's an amazing developer), but I did have to manually grant the storage permission first by going to: App info > Permissions > Storage (toggle it on).
If this doesn't work, use BusyBox Installer (warning:it's riddled with ads).
As for Flashfire, try enabling the "mount system read/write" option.
Click to expand...
Click to collapse
Thank you for your help bro. I did what you said, busybox installed successfully. But after flashing with flashfire, even when checking mount, there's still no sign of viper after reboot
Sent from my SM-N950U1 using Tapatalk
kidbranz01 said:
Thank you for your help bro. I did what you said, busybox installed successfully. But after flashing with flashfire, even when checking mount, there's still no sign of viper after reboot
Sent from my SM-N950U1 using Tapatalk
Click to expand...
Click to collapse
That is the strangest thing, I can't imagine why the ViPER apps wouldn't show up. The only thing that comes to mind is... If you ran the fsck script after rooting, did you?
kidbranz01 said:
Thank you for your help bro. I did what you said, busybox installed successfully. But after flashing with flashfire, even when checking mount, there's still no sign of viper after reboot
Sent from my SM-N950U1 using Tapatalk
Click to expand...
Click to collapse
I had the same issue, but then in FlashFire, under settings I disabled Emulate framebuffer.. Now Viper4android is installed and working.
Does anyone who has this installed get freezes after reboots from time to time?
kirschdog1 said:
Does anyone who has this installed get freezes after reboots from time to time?
Click to expand...
Click to collapse
It freezes up all the time, even when requesting SU.
Sent from my SM-N950U using Tapatalk
Does anyone on Snapdragon have this and FM Radio working together? Unfortunately, I'm finding I can't run both. I don't know if it's my Viper settings or what. Any input would be appreciated as I don't want to have to choose between the two features if I don't have to
For those who had trouble on snapdragon try using latest Sam fail v2 if possible it works perfect on here if you follow directions. Few key things, disable emulate framebuffer in flashfire and when flashing enable mount read and write system, also make sure you install drivers in both v4a apps to enable root as root access is need for v4a to work properly after unistalling drivers and granting root reflash zip in flashfire to restore drivers and profit
I have problem with viper4android hifi can't read root access
jomolocco said:
I have problem with viper4android hifi can't read root access
Click to expand...
Click to collapse
If I remember correctly, there was something that said if you had this trouble, open app, uninstall the driver, Grant the permission, then re-flash the app.

Categories

Resources