I'm not a dev so i cannot help you with bugs etc... I will not take any creds regard this program only wanted to share what i know and as always i'm not responsible for anything that happens to your devices..
Sorry for my bad English..
I've found a working method for V4A to work on Nexus 5X, and i know there are many threads about this...
I was looking around and found some solutions, but it seemed like there was not a specific thread about installing or was actually working.
It does not seem like you need permissive kernel for this to work (I've tried both Permissive and Enforcing, and both work).
Nexus 6's V4A have worked, but it it's missing audio focus sometimes. I've not got any FC. Dolby and Dolby Plus works too
I'm running:
ROM: ResurrectionRemix MM v5.6.4
Kernel: Jolla Kernel v6.0-Beta
Recovery: TWRP v3.0.0-0
What you will need:
-Nexus 5x (obviously)
Busybox (Recomended): meefik (Free)
Busybox: Stephen (Stericson) (Free)
Viper4Android (Recomended, but Doby is not included): Nexus 5 V4A
Viper4Android: Nexus 6 V4A
Install Method
1. First download Es File Explorer (or any other file explorer with root/system access).
2. Open File explorer and grant read write permission (in es file explorer you must go to left side panel and grant root access and then click on the text and choose "Mount R/W"). Then give "/", "/system" and "/vendor" r/w permission.
3. Afterwards you go to "/system/vendor/etc/" rename "audio_effects.conf" to "audio_effects.conf.bak" (in case something goes wrong or if you want to go back later. This is because V4A makes its own version of "audio_effects.conf". You will have to do it because in MM and V4A does not r/w for some reason.. It will then make its own file and it will work. If you want to go back to normal, just delete the "audio_effects.conf" V4A made and delete the ".bak" at the end of the original file. Also uninstall the driver from V4A, then use a system app remover to delete V4A. Then reboot).
4. Install the Busybox Version you prefer from Google Play Store. I'm currently running Busybox v1.24.1 (installed to "/system/xbin")
5. Go into recovery and take a backup (just to be on the safe side) before you flash the V4A of you liking, but I would suggest LolliViper (I will only link to the website not the file itself).
Then your done, if you have any questions or need help I can try my best. i cannot promise i can help tho..
Related
I'm struggling with installing Viper4Android on my device.
I tried installing using either the apk from the original thread (http://forum.xda-developers.com/showthread.php?t=2191223). It install successfully but I keep getting a driver install prompt, after installing the driver and rebooting.
Things I already tried without success:
- Installed BusyBox with BusyBox app (https://play.google.com/store/apps/details?id=ru.meefik.busybox)
- Setting the SELinux mode to permissive using SELinuxModeChanger app (http://forum.xda-developers.com/showthread.php?t=2524485)
- Setting the SELinux mode to permissive using flashable permissive.zip
- Installing the apk from the Material design Viper4Android thread (http://forum.xda-developers.com/android/software/app-material-viper4android-2-3-4-0u-t3190352)
- Flashing the .zip from the same thread.
I'm currently running Android 6.0 GPE, flashable version (http://forum.xda-developers.com/showthread.php?t=2708589)
Root access is granted through SuperSU, so no problem on that matter I suppose.
2. With a File Manager(Solid Explorer Recommended) locate " /system/etc/htc_audio_effects.conf" and rename "htc_audio_effects.conf" to "htc_audio_effects.bak" (Renaming this file will make it inactive but while keeping it backed up just in case this doesn't work for you, however it appears this file is not needed as no negative effects occur, and this should fix V4A.)
3. Reboot Device.
And if this doesn't work I thin you should grant storage permission for V4A under settings. I hope I can help you!
Duccibreeezy said:
2. With a File Manager(Solid Explorer Recommended) locate " /system/etc/htc_audio_effects.conf" and rename "htc_audio_effects.conf" to "htc_audio_effects.bak" (Renaming this file will make it inactive but while keeping it backed up just in case this doesn't work for you, however it appears this file is not needed as no negative effects occur, and this should fix V4A.)
3. Reboot Device.
And if this doesn't work I thin you should grant storage permission for V4A under settings. I hope I can help you!
Click to expand...
Click to collapse
Thanks mate!! This worked for me.
Thanks for ur help
Enforcing is set by default on CM 13 so I tried to find some fixes trying to make it work then I got lucky.
If you want the new version of ViPER4Android you can download it here.
Firstly I advice you to install ViPER first (Do not open it yet) then go to Developer Options and disable the root access after that you can reboot to recovery and flash this and here is the link where the flashable zip came from.
Screenshot Here
You can enable the root access after boot and install the audio drivers. If you want to place ViPER4Android on the system you can use Lucky Patcher. (Trust me it helps)
Thanks to zhuhang for the app and AntonPanos for the flashable zip and lastly mobiusm.
Various links in Google world. Some worked. Others had issues. To keep this simple I am going to attach two files to use. This is based on the use of Magisk for rooting your setup. It does NOT work if you are only using SuperUser. The mods that stated how to do this with SU did NOT work for me, so I will not include anything with regards to that. Again, this is working for me with latest just posted Android 7 firmware for my SM-G925T and rooted with Magisk and TWRP recovery installed. Please don't ask if you are not rooted or no TWRP or whatever. They ARE required and Magisk is required too. Plus go to Playstore and make sure BusyBox is installed. I would also uninstall any prior versions of Viper prior to doing this. Or use Titanium BU to delete so as NOT to have competing files. After the above, take the attached file audio_effects.conf and replace the one located in your system\etc folder. The file is zipped simply to allow uploading. This is NOT installable from recovery. Simply unzip to use the conf file. Disregard the backup file in this zipped upload. The .bak is not needed. You will need an app like root explorer to do this. Make sure you set the file permissions the same as the app you are replacing. This is important. Permissions must be the correct same as the original file. Finally...take the attached v4afx_v1.4 zip and install from TWRP recovery. Reboot and should be good to go. If done correctly the left menu in viper that shows driver status will show everything processing, enabled, and working when Viper is ON and music is playing
Added webcam shot showing driver status. A screen shot would remove that window showing driver status.
Do you randomly lose root after this install?
First, this is my setup.
Running stock rooted with elemental x kernel.
OS - Jan Patch
Magisk - v16.2
Magisk Manager - v5.6.4
Elemental X- P2-1.05
Twrp - latest
I did search as best I can on these forums but found just bits and pieces and still no solution. If there is one mods please delete and I'll search again.
So my issue is at some point I could no longer overwrite files to my system. I do have a modified host that I did awhile back and that sticks. But I can no longer overwrite that and others. I have es file pro and it can't do it. When I check permissions for system to be rw it switches back to ro when I go back into permissions. I have root browser by jrummy and that lets me change files but it doesn't stick after reboot. I also un checked the radio button avb/dm-verity in Magisk Manager but it too doesn't stick when I back out of app and go back in. Did I not do something correctly when installing Magisk? In Magisk thread it says your /system will only be modified if root is installed to /system. But doesn't explain how to do that. Sorry for long post, hopefully someone can point me in the right direction.
Edit:
Solved.
I got it, I think those two radio buttons are settings for when you update magisk or patch boot. They were both selected by default, so I unchecked them and installed magisk v16.0 through the manager and now I can write to system. Es File Explorer still not working but at least the other file manager is. Mods you can delete this thread.
Maybe most people know about do this, but I wanna share for some people how don't know to do this.
1. Your phone must have unlocked bootloader and have twrp so you can root your phone and also install busybox. (Many tutorial in xda, just follow that. If u still can't, you can ask in comment)
2.
*If you root with superuser phh's, so go to twrp recovery mode and flash ViPER4Android_2.5.0.5_guitardedhero.zip (you can searching with Google and download)
*If you root with magisk, so you can go to magisk manager, choice menu-download- find ViPER4Android_FX_Legacy-v4.3 module and install.
Reboot your phone and you have Viper4Android v2.5.0.5 in your device. Open Viper4Android app, grant
superuser permission, and now there should has driver installed.
3. Open root explorer or other app like that go to dev/system/priv-app/ViPER4AndroidFX, find ViPER4AndroidFX.apk, delete it and paste ViPER4AndroidFX v2.7.1.0.apk here. ( You can searching with Google and download the ViPER4AndroidFX v2.7.1.0.apk file)
4. Reboot your phone and enjoy Viper4Android v2.7.1.0 in your phone.
Just install Viper4Android v2.5.0.5 for first. You can't just install Viper4Android v2.7.1.0 directly. If you use magisk, don't install Viper4Android v2.7.1.0 module and of course don't delete your Viper4Android v2.5.0.5 module. Viper4Android v2.7.1.0 is using driver v2.5.0.5. I think is more about interface update. Maybe...:laugh:
Sorry I don't know how to attach file here, but I'm sure is not difficult to find the file you needed.
Do with you own risk!
If you not clear please ask first!
Understanding all procedure before you do it.
I think if you phone is Moto E4 Plus Mediatek Variants, that's should be work.
Don't forget to backup before do this.!