I cant figure out how to do it, I am rooted and I can't figure it out!
Brava27 said:
I cant figure out how to do it, I am rooted and I can't figure it out!
Click to expand...
Click to collapse
Need a SeLinux Permissive Kernel for S7Edge first. Have you found one?
Brava27 said:
I cant figure out how to do it, I am rooted and I can't figure it out!
Click to expand...
Click to collapse
Seems this guy has the answer on an enforcing kernel.
http://forum.xda-developers.com/s7-edge/review/audio-quality-t3336558
If you haven't seen this thread already, check it out. I successfully installed V4A on my 935F with it.
http://forum.xda-developers.com/showthread.php?t=3335007
And FYI... it sounds fantastic!
You DON'T need permissive kernel for v4a any more..after hundereds of trials and errors I just downloaded newest apk from original v4a thread, put it in private-apps folder then set correct permitions rw-r-r, restarted device and it works flowellesly ! I have stock enforced kernel.
tin2404 said:
You DON'T need permissive kernel for v4a any more..after hundereds of trials and errors I just downloaded newest apk from original v4a thread, put it in private-apps folder then set correct permitions rw-r-r, restarted device and it works flowellesly ! I have stock enforced kernel.
Click to expand...
Click to collapse
Does it work with Spotify as well?
Why don' you try? I don't use it.
tin2404 said:
You DON'T need permissive kernel for v4a any more..after hundereds of trials and errors I just downloaded newest apk from original v4a thread, put it in private-apps folder then set correct permitions rw-r-r, restarted device and it works flowellesly ! I have stock enforced kernel.
Click to expand...
Click to collapse
Tried hundered of ways here as well,
Mine just keeps asking to install the damn driver all the time mate, and even if installed, after reboot - it just asks again to install/update the driver again.
Tried with the su.policy zip flash as well. Still cant get it to work!
Tried with the MM compatible newest APK and placed it in Priv-app. Guess that's what you did too. Cant figure out what I'm missing here.
It happens to me also.That means you did NOT properly root device.Error with constant driver install is because busybox..I rerooted device ,wiped data for SU, and granted permission to busybox again.DO NOT use any other Viper app then original one from thread !
tin2404 said:
It happens to me also.That means you did NOT properly root device.Error with constant driver install is because busybox..I rerooted device ,wiped data for SU, and granted permission to busybox again.DO NOT use any other Viper app then original one from thread !
Click to expand...
Click to collapse
Youv'e been a lot helpful mate,
I think I'm getting somewhere, Could you please tell me which busybox did you use?
Is it the Stericsson version, or the Meefik ?
Stericsson one. I hac problems as you did and concluded the most simple one was the best..All that modded Viper apps doesn't do any use.Just use original one,give permissions in private-apps, restart device and that is it
which music players support this? cuz so far all i see is status normal processing no
tin2404 said:
Stericsson one. I hac problems as you did and concluded the most simple one was the best..All that modded Viper apps doesn't do any use.Just use original one,give permissions in private-apps, restart device and that is it
Click to expand...
Click to collapse
Men! You put so much hope in my heart. Please, could you be so nice and prepare step by step to do list? I personally would ask you about 'give permissionso in private-apps'. Could you explain? Do you copy v4a to priv-apps? Where from? What permissions? And about busy box: when I open it it shows me that it is installed in su/xbin... in what folder did you install busybox? And one about reroot: did you go to su and choose: full unroot before flashing su again? And what about mount namespaces: checked or unchecked in su? Have to tell you that I've tried so much different ways and still v4a doesn't work. I would love to try your way but please put some lights here. Thanks!
SM-G935F powered by Echoe
I've tried my best, in all possible variables and finally decided to give up after wasting 3 straight days of a perfect weekend.
My Driver just doesn't stick and I've tried all alternative installation methods. I've kept backups of system/*.* so all damages were reversed without any flashing. Root, Busybox everything runs perfectly and tested everything for integrity.
So far I've cornered the issue to Systemless Root, which seems to be the only entity having issues with v4a. Until a proper answer is digged up, I'm gonna stick with my Note 5 which has this working on System-Mode Root. (The driver didn't stick on the Note 5 when I tried to use it with System-less) Luckily the Note 5 is still on LP, with Su 2.64.
Good Luck to those who are trying, and thanks to all who helped!
OK...I made comprehesive tutorial here
http://forum.xda-developers.com/s7-edge/themes/viper4android-proper-installation-t3340525
JazonX said:
I've tried my best, in all possible variables and finally decided to give up after wasting 3 straight days of a perfect weekend.
My Driver just doesn't stick and I've tried all alternative installation methods. I've kept backups of system/*.* so all damages were reversed without any flashing. Root, Busybox everything runs perfectly and tested everything for integrity.
So far I've cornered the issue to Systemless Root, which seems to be the only entity having issues with v4a. Until a proper answer is digged up, I'm gonna stick with my Note 5 which has this working on System-Mode Root. (The driver didn't stick on the Note 5 when I tried to use it with System-less) Luckily the Note 5 is still on LP, with Su 2.64.
Good Luck to those who are trying, and thanks to all who helped!
Click to expand...
Click to collapse
FRM300 said:
Men! You put so much hope in my heart. Please, could you be so nice and prepare step by step to do list? I personally would ask you about 'give permissionso in private-apps'. Could you explain? Do you copy v4a to priv-apps? Where from? What permissions? And about busy box: when I open it it shows me that it is installed in su/xbin... in what folder did you install busybox? And one about reroot: did you go to su and choose: full unroot before flashing su again? And what about mount namespaces: checked or unchecked in su? Have to tell you that I've tried so much different ways and still v4a doesn't work. I would love to try your way but please put some lights here. Thanks!
SM-G935F powered by Echoe
Click to expand...
Click to collapse
Has anyone managed to get it working? I've tried every single method to install it and still nothing!
csr.rocha said:
Has anyone managed to get it working? I've tried every single method to install it and still nothing!
Click to expand...
Click to collapse
Yes. Actually there is a perfect package from @guitardedhero. You have to be rooted, busyboxed, twrp'ed. Flash this: http://forum.xda-developers.com/attachment.php?attachmentid=3701983&d=1459364213
It is Viper Atmos Sony Beats edition working beautifully on ny S7E. Three more step to do after flashing: 1. freeze SoundAlive and AdaptSound, reboot. 2. go to system preferences and check whether Viper has memory access granted. 3. go to SuperSu and DISABLE 'Mount namespace separation', reboot. Done!
Btw. If you want to play with Profiles inside Viper, go to your internal memory using root explorer and inside Viper folder create folder called 'Profiles'.
Btw2. 6.0.1new abowe destroy your conf files. Hope you have backup.
Better flash @guitardedhero mod on fresh rooted rom. hope you enjoy.
Btw3. Sound is AMAZING!
S7E powered by Echoe™ v5
Thanks for your reply!
Just after I asked for help here, i found a driverless package from @guitardedhero that worked! Glad to know you did it too, mate! :highfive:
Working but 10 second later turn normal mod
Why do you think's going on?
For example in youtube, 10 second viber4android active, later deactivate.
SM-G935F cihazımdan Tapatalk kullanılarak gönderildi
Related
Hello,
i finally got my Nexus 5 today and first thing I did was unlocking the bootloader, installed TWRP custom recovery, flashed CM11-nightly and Franco Kernel (r31).
Next thing I usually do is to uninstall some apps with Titanium Backup (Pro). But I can't uninstall any system apps (e. g. Browser.apk). Titanium says "successful" but after refreshing the application list, the app is still there.
Does anyone have an idea what is going wrong here? Is it a problem with CM11's superuser or with Titanium Backup?
Thanks.
Cloonix said:
Hello,
i finally got my Nexus 5 today and first thing I did was unlocking the bootloader, installed TWRP custom recovery, flashed CM11-nightly and Franco Kernel (r31).
Next thing I usually do is to uninstall some apps with Titanium Backup (Pro). But I can't uninstall any system apps (e. g. Browser.apk). Titanium says "successful" but after refreshing the application list, the app is still there.
Does anyone have an idea what is going wrong here? Is it a problem with CM11's superuser or with Titanium Backup?
Thanks.
Click to expand...
Click to collapse
What happens if you delete the file with a file manager and reboot?
Aerowinder said:
What happens if you delete the file with a file manager and reboot?
Click to expand...
Click to collapse
I used Solid Explorer as a file manager and tried to delete /system/app/Browser.apk. The root-confirmation (CM11 superuser) pops up, asks for superuser (i grant) and Solid Explorer deletes the file without error. But the file is still there (without reboot).
Issue with superuser?
Edit: Stop... I noticed /system is mounted as read-only.
I tried to analyze the problem... and the only conclusion is, that my superuser is not working. Also Super SU ist not working. I also flashed Omni ROM instead of CM11 with no success. I used an older version of TWRP without success. Does anybody has an idea?
Edit: Before with Stock ROM and Super SU it was working.
I don't know why I'm the only person with this issue... But I solved it with the following steps:
1. Flash CM11 (nightly)
2. Start the OS
3. Reboot to recovery and wipe cache/dalvik
4. Install "Super SU"
5. Start the OS
Titanium Backup is asking for root rights. Other apps also didn't get root in CM11. Whenever I install a new CM11 nightly root rights for TB are gone and I have to do the same steps again.
But why no one else has this problem? I googled like crazy. Is it CM11 or me?
Me to, cm11 for a850L build on crdroid nexus4
Cloonix said:
I don't know why I'm the only person with this issue... But I solved it with the following steps:
1. Flash CM11 (nightly)
2. Start the OS
3. Reboot to recovery and wipe cache/dalvik
4. Install "Super SU"
5. Start the OS
Titanium Backup is asking for root rights. Other apps also didn't get root in CM11. Whenever I install a new CM11 nightly root rights for TB are gone and I have to do the same steps again.
But why no one else has this problem? I googled like crazy. Is it CM11 or me?
Click to expand...
Click to collapse
Did you leave out Franco kernel this time?
This is the fix for your issue:
http://forum.xda-developers.com/showthread.php?t=2592456
es0tericcha0s said:
This is the fix for your issue:
http://forum.xda-developers.com/showthread.php?t=2592456
Click to expand...
Click to collapse
Thanks a lot!
Changing selinux to "permissive" did solve all my problems. I also had issues with other applications.
How can I change the selinux mode directly in the CM11-Zip? Under Redhat/CentOS is a configuration file unter /etc/selinux. In CM11 I can't find something similar.
And how it comes that this issue is not well-known? I think there are more 4.4 KK / CM11 users with problems.
Aerowinder said:
Did you leave out Franco kernel this time?
Click to expand...
Click to collapse
No I flashed Franco after CM.
Cloonix said:
Thanks a lot!
Changing selinux to "permissive" did solve all my problems. I also had issues with other applications.
How can I change the selinux mode directly in the CM11-Zip? Under Redhat/CentOS is a configuration file unter /etc/selinux. In CM11 I can't find something similar.
And how it comes that this issue is not well-known? I think there are more 4.4 KK / CM11 users with problems.
No I flashed Franco after CM.
Click to expand...
Click to collapse
No problem. I know that problem was starting to annoy me. Got the idea from playing with a new Note 3. The newer Samsung 4.3 roms are like that too. If you don't change to Permissive then Xposed and other mods won't work either.
I guess it's possible that it's just something strange with certain CM11 and Franco kernel combos?
es0tericcha0s said:
I guess it's possible that it's just something strange with certain CM11 and Franco kernel combos?
Click to expand...
Click to collapse
Even without Franco (which was my first guess) CM11 (my root) behaves that way.
I will look for a method to set selinux to permissive directly in the ZIP of CM11 and will update this post.
Cloonix said:
Even without Franco (which was my first guess) CM11 (my root) behaves that way.
I will look for a method to set selinux to permissive directly in the ZIP of CM11 and will update this post.
Click to expand...
Click to collapse
I'd imagine adding something like this in: http://forum.xda-developers.com/showpost.php?p=48006307&postcount=65 would do the trick, though I have not had that issue in awhile. I switch roms often.
es0tericcha0s said:
I'd imagine adding something like this in: http://forum.xda-developers.com/showpost.php?p=48006307&postcount=65 would do the trick, though I have not had that issue in awhile. I switch roms often.
Click to expand...
Click to collapse
I tried this. And it was successfully changing selinux to permissive with every reboot. But doing this I noticed that even permissive doesn't solve the problem. CM11 built-in superuser just don't work for me. Only "Super SU" by Chainfire works well. And permissive solves a few other problems besides TiBa.
Personally I've always eventually had issues with Superuser unmounting the system as rw causing issues with apps like Titanium. Had it happen many many times on my old phone as well as the Nexus 5 across multiple ROMs. I just stick with SuperSU now.
Haven't had too many issues with that part it seems, but glad you narrowed down the problems.
I find this issue sometimes on varous flashes of CM 11 on different devices.
I use ROM toolbox fo manage apps, and sometimes it just wont delete. The solution is strange: I install adaway - somehow, that "unlocks" something that lets you delete apps. You can uninstall adaway once you have run it!
Galaxy Nexus
I'm replying just to help out anyone who has this issue, but doesn't have a Nexus 5. I was trying to find a fix for me and my Galaxy Nexus running the latest Paranoid Android beta 4.4.2 because I kept having this same problem.. It wouldn't uninstall... and I would only keep getting directed to this specific post. So....
I tried the 'selinux' fix first, and that alone would not do a thing...
I then tried installing the 'Wanam Xposed' app and it worked perfectly.
Just change selinux to permissive and make sure both selinux and Wanam have SU access and then try to uninstall via Titanium... or whatever method you usually use.
Hope it's okay for me to post here. Thanks for the help, everyone!
es0tericcha0s said:
No problem. I know that problem was starting to annoy me. Got the idea from playing with a new Note 3. The newer Samsung 4.3 roms are like that too. If you don't change to Permissive then Xposed and other mods won't work either.
I guess it's possible that it's just something strange with certain CM11 and Franco kernel combos?
Click to expand...
Click to collapse
Hi,
unfortunately the SElinuxModeChanger seems not to work for me (Samsung Galaxy S2, CM 11 m6) and I do not really get how I should install Supersu (the first described solution). I guess I should not just install it from the play store - right? But were do I get an installable zip-file to install it from the CWM?
Or is there anything else that might be wrong in my system - so that I do not need to install supersu at all?
regards
Daniel
daniu said:
Hi,
unfortunately the SElinuxModeChanger seems not to work for me (Samsung Galaxy S2, CM 11 m6) and I do not really get how I should install Supersu (the first described solution). I guess I should not just install it from the play store - right? But were do I get an installable zip-file to install it from the CWM?
Or is there anything else that might be wrong in my system - so that I do not need to install supersu at all?
regards
Daniel
Click to expand...
Click to collapse
If you are already using CM11, then yes, you can install SuperSu from the Play Store. Once you do and open the app, it will prompt you to update the SuperUser binary. You should be able to do the "normal" method, and then once that updates, reboot, then try the SELinux app again and then everything should start to work like you would expect. If the normal method doesn't work, then you can let it download the newest zip for you if you choose the CWM/TWRP method, and then boot to recovery and install the zip it downloads for you.
SeEsAw12 said:
I'm replying just to help out anyone who has this issue, but doesn't have a Nexus 5. I was trying to find a fix for me and my Galaxy Nexus running the latest Paranoid Android beta 4.4.2 because I kept having this same problem.. It wouldn't uninstall... and I would only keep getting directed to this specific post. So....
I tried the 'selinux' fix first, and that alone would not do a thing...
I then tried installing the 'Wanam Xposed' app and it worked perfectly.
Just change selinux to permissive and make sure both selinux and Wanam have SU access and then try to uninstall via Titanium... or whatever method you usually use.
Hope it's okay for me to post here. Thanks for the help, everyone!
Click to expand...
Click to collapse
No clue why, but this worked for me. Permissive didn't do it (was already permissive using CM 11 for tf201) and AdAway didn't do it. Didn't matter that Wanam Xposed is for Samsung devices, once given root to this app, Titanium got its head out of its rump.
UPD: So, if i uninstall Wanam Xposed then TB sticks its head back up its rump. Whatever giving root to that app does, its fixing usage issues with TB.
As a few days frustration and zillion tries are behind me let me explain proper instalation of this sound engine. Just to notice that you DON'T need permissive kernel for that because I installed it on my stock German ROM and now works in French Orange ROM G935FXXU1APBF as well !
INSTALLATION PROCEDURE ON CLEAN STOCK ROM :
At first...
You need to DELETE not to freeze sound alive and adapt sound.
In build.prop find the lines or add them as follows ;
Ipa.decode=false
tunnel.decode=false
lpa.use-stagefright=false.
.
1.You need to root your SM-G935F device with newest SuperSU by ChainFire located here.So, download and flash TWRP recovery from here and flash SuperSU.Wipe dalvik,wipe cache, then Restart your device.
2.From Playstore download and install latest STERICSON BUSYBOX. Install busybox in default su/xbin and give root permission.Restart your device again.
3. Download from official page Viper4android version 2.4.0.1 from HERE
4. Using Root explorer copy Viper4Android in folder PRIV-APP and give it permission 0644 rw-r--r-- (see attached image)
5.Restart your device
6. Open V4A and install driver when it asks...don't exit app or DON'T TOUCH anything else, just Restart your device.
7. Open V4A and go to Settings - UI Setting - Expert Mode
8. In some occasions V4A will ask for new driver installation...Install again and restart device.
9. Use your V4A wisely !
IMPORTAINT NOTIFICATION !
If you previously messed up with V4A or rooting,I recommend fresh ROM installation from scratch.
If V4A constantly offers to install driver, it means you did not properly rooted your device !
VIPER4ANDROID IS NOT WORKING ON STOCK PLAYER !
That's all.If you didn't read post carefuly, there is no any support else, because it is not needed.
Followed your guide, didn't ask to install a new driver after step 8 and viper is not working any suggestions?
Bernard23 said:
Followed your guide, didn't ask to install a new driver after step 8 and viper is not working any suggestions?
Click to expand...
Click to collapse
In some cases it doesn't ask for another driver installation after entering expert mode.Did you try another player?
If you don't used it on clean rom then it could be anything.
I've not needed to do half of this.
riso123 said:
I've not needed to do half of this.
Click to expand...
Click to collapse
How come ?
BusyBox Location is Su/xbin or System/xbin ?
JazonX said:
BusyBox Location is Su/xbin or System/xbin ?
Click to expand...
Click to collapse
Did you read thread ? I mentioned above that busybox is in /su/xbin/
tin2404 said:
Did you read thread ? I mentioned above that busybox is in /su/xbin/
Click to expand...
Click to collapse
I read and hence the question, because usually since MM - Busybox is installed to System/xbin by default.
Nevermind, Gonna try that as well now. Thanks!
ViPER4Android_FX_A4_6.0.1_New.zip
set through TWRP checked S7 Edge 935FD
barbik said:
ViPER4Android_FX_A4_6.0.1_New.zip
set through TWRP checked S7 Edge 935FD
Click to expand...
Click to collapse
dude that's zip work flawlessly :good:
tin2404 said:
How come ?
Click to expand...
Click to collapse
Because I simply download the latest APK and install it as a normal app rather than copy across and setting permissions.
I then download and flash the ZIP from the below site:
http://androiding.how/how-to-fix-viper4android-selinux-policy-issues-on-lollipop/
After that I installed the driver, rebooted and all was good.
I was the first\one of the first, to flash v4a on our device.
I've already created a tutorial thread for this in the guide section. People might find it easier, no need to make adjustments to build.prop for example, it's automatic.
http://forum.xda-developers.com/s7-edge/how-to/guide-viper4android-enforcing-stock-t3337148
Beefheart said:
I've already created a tutorial thread for this in the guide section. People might find it easier, no need to make adjustments to build.prop for example, it's automatic.
http://forum.xda-developers.com/s7-edge/how-to/guide-viper4android-enforcing-stock-t3337148
Click to expand...
Click to collapse
Exactly what I was thinking...
Beefheart said:
I've already created a tutorial thread for this in the guide section. People might find it easier, no need to make adjustments to build.prop for example, it's automatic.
http://forum.xda-developers.com/s7-edge/how-to/guide-viper4android-enforcing-stock-t3337148
Click to expand...
Click to collapse
Amazing recommendation on the flat icons xposed module. Loving the custom status bar icons [emoji106]
Sent from my SM-G935W8 using Tapatalk
barbik said:
ViPER4Android_FX_A4_6.0.1_New.zip
set through TWRP checked S7 Edge 935FD
Click to expand...
Click to collapse
Thank you so much for this barbik!
I've literally spent the best part of a day trying to get this to work. Followed various guides posted here but only your link applied V4A system wide rather than just for GoneMAD.
If anyone else is having issues, uninstall the driver and the app, reboot into twrp and flash this zip instead.
Thanks again you saved me a few grey hairs!
SirBarnz said:
Thank you so much for this barbik!
I've literally spent the best part of a day trying to get this to work. Followed various guides posted here but only your link applied V4A system wide rather than just for GoneMAD.
If anyone else is having issues, uninstall the driver and the app, reboot into twrp and flash this zip instead.
Thanks again you saved me a few grey hairs!
Click to expand...
Click to collapse
I agree, that zip helped me as well after a few failed attempts Now it works perfectly and Spotify sound amazing!
barbik said:
ViPER4Android_FX_A4_6.0.1_New.zip
set through TWRP checked S7 Edge 935FD
Click to expand...
Click to collapse
Hi, flashed, works! Super! Thanks. One question: what is that clock??? app inside zip for? Is it necessary? That's strange surprise... It's located in system/app/com.cyanogenmod.lockclock-1, please explain. Thank you.
N4 powered by Echoe™
FRM300 said:
Hi, flashed, works! Super! Thanks. One question: what is that clock??? app inside zip for? Is it necessary? That's strange surprise... It's located in system/app/com.cyanogenmod.lockclock-1, please explain. Thank you.
N4 powered by Echoe™
Click to expand...
Click to collapse
+1
What's that Clock APK ?
JazonX said:
+1
What's that Clock APK ?
Click to expand...
Click to collapse
his is a clock widget ... they are not needed, they can be removed
Mine works perfectly fine with just freezing those two Samsung apps...
Sent from my SM-G935F using Tapatalk
I've got busybox installed properly, it's Stericson's, I've checked if it's working and it is, I have given root permission to V4A and I have plenty of space for the drivers to be installed. I'm on a rooted h959 15e image, I'm not really willing to revert back to previous software versions, and I'm stuck with this problem. The exact message I get is "Driver install failed: The busybox installation found on your device does not work. This usually means you installed a wrong or broken busybox. V4A needs Stericson's busybox to work. If you are sure you installed busybox properly, then please confirm your device has been completely rooted". But it is rooted, I can access all types of root-only things like xposed and root booster. SELinuxModeChanger is set to permissive, I have tried with both V4A apps from the DXA thread and from the (not the FX one) one in Google Play, and I have already tried uninstalling and installing everything, and I have also tried reflashing my rooted_system.img countless times. So root is working, busybox is working, SELinuxModeChanger is properly set up, why isn't it working? Also I noticed something, when I reboot my phone, SELinuxModeChanger changes the SELinux mode back to enforcing, but if I turn on the option to show a notification after the mode changes, the notification IS showed, so it must mean it's working, right? I have tried before without poweramp and dolby atmos, but as of now I'm using both. I don't even know if V4A will work with Atmos and Poweramp (Atmos and Poweramp do work together, though), but I just need to try it, even if it means uninstalling atmos. So I'm completely out of options. The only thing that I can think of is if there's a way to manually install the drivers (latest updated/updatable super audio quality ones), but I don't know if that's possible. So anyway, can anyone help me with this?
You should flash a zip from this site: http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137. I used this: http://forum.xda-developers.com/attachment.php?attachmentid=3667403&d=1456929089, and it works. Of course, flashfire v0.24 is required.
jst8 said:
You should flash a zip from this site: http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137. I used this: http://forum.xda-developers.com/attachment.php?attachmentid=3667403&d=1456929089, and it works. Of course, flashfire v0.24 is required.
Click to expand...
Click to collapse
I'm flashing the zip file viper|atmos 5.5 sony beats edition with flashfire 0.50, and nothing's happening. Again, SELinux mode is permissive and busybox is installed, but atmos app and viper app won't show up, and when installing the app from the playstore, it says the driver is not installed. Help, please?
Iron_Overheat said:
I'm flashing the zip file viper|atmos 5.5 sony beats edition with flashfire 0.50, and nothing's happening. Again, SELinux mode is permissive and busybox is installed, but atmos app and viper app won't show up, and when installing the app from the playstore, it says the driver is not installed. Help, please?
Click to expand...
Click to collapse
1. First, install ViPER4Android apk from the official site: http://forum.xda-developers.com/showthread.php?t=2191223. You can choose between the old (v2.3.4.0) and new (v2.4.0.1) version.
2. Then flash a zip from this site: http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137. I used "ViPERAudio 5.4 Stock.zip" (compatible with V4A v2.4.0.1). You can also choose "ViPERAudio 4.7.1 Stock.zip", if you have V4A v2.3.4.0 installed. I didn't try other mods (such as "viper|atmos 5.5 sony beats edition"), so I don't know if they work.
3. For flashing, you have to use FlashFire v0.24, other versions don't work with the device. Link: http://flashfireapk.com/flashfire-0.24.apk.
* Also, you don't have to change SELinux.
Thanks
jst8 said:
1. First, install ViPER4Android apk from the official site: http://forum.xda-developers.com/showthread.php?t=2191223. You can choose between the old (v2.3.4.0) and new (v2.4.0.1) version.
2. Then flash a zip from this site: http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137. I used "ViPERAudio 5.4 Stock.zip" (compatible with V4A v2.4.0.1). You can also choose "ViPERAudio 4.7.1 Stock.zip", if you have V4A v2.3.4.0 installed. I didn't try other mods (such as "viper|atmos 5.5 sony beats edition"), so I don't know if they work.
3. For flashing, you have to use FlashFire v0.24, other versions don't work with the device. Link: http://flashfireapk.com/flashfire-0.24.apk.
* Also, you don't have to change SELinux.
Click to expand...
Click to collapse
Thank you very much, friend, I'm gonna try your method right now. Just one question, why doesn't flashfire 0.50 work with the g flex 2? I flashed Xposed with it and it worked. Isn't 0.24 an older version?
How do you test the benefits?
Iron_Overheat said:
Thank you very much, friend, I'm gonna try your method right now. Just one question, why doesn't flashfire 0.50 work with the g flex 2? I flashed Xposed with it and it worked. Isn't 0.24 an older version?
Click to expand...
Click to collapse
Actually, I don't know. I've read somewhere that v0.24 is the only working version for our flex 2. I didn't want to brick my device, so I used v0.24. I've had no problems with it so far.
soosoolhastam said:
How do you test the benefits?
Click to expand...
Click to collapse
I'm just going to play my flacs and listen to them while tuning v4a to my liking.
jst8 said:
Actually, I don't know. I've read somewhere that v0.24 is the only working version for our flex 2. I didn't want to brick my device, so I used v0.24. I've had no problems with it so far.
Click to expand...
Click to collapse
I've tried with version 0.24 and it didn't work either. I'm gonna test the g flex 2 flash mod (the one with g4 tweaks and etc) with flashfire 0.24, since it says to use that version and it didn't work flashing it with 0.50, and if it still doesn't work for me, I'll revert back to 0.50, since it worked flashing dolby atmos (seperate from viper4audio, but the viper4audio-only zip file didn't flash). I fixed my problem of drivers not installing, so I'll just install atmos again and install the v4a drivers through the app. But thank you all for your help, really . If I menage to get all the mods I have working, I'll make a thread so that H959 rooted 15e image users can enjoy the best experience in their G flex 2.
maybe you never get viper4 to work in GF2...i did it many times with diferent methods and never never get it to work...even use the flashfire 0.24 (the only working to install zips on GF2) you never get a driver to work!
i recomend to you install Dolby Atmos see Apps section in this forum of GF2...the Dolby Atmos works like a charm and do the good job as Viper4.
(i am not sure but because of architeture of the SD810 Viper4 the latest version never will work on our device!)
That's strange... I'm on H955 v15c, V4A 2.4.0.1 with "ViPERAudio 5.4 Stock.zip" installed using FlashFire v0.24.
Everything works.
copy2050 said:
maybe you never get viper4 to work in GF2...i did it many times with diferent methods and never never get it to work...even use the flashfire 0.24 (the only working to install zips on GF2) you never get a driver to work!
i recomend to you install Dolby Atmos see Apps section in this forum of GF2...the Dolby Atmos works like a charm and do the good job as Viper4.
(i am not sure but because of architeture of the SD810 Viper4 the latest version never will work on our device!)
Click to expand...
Click to collapse
Everyone... I... I... I FINALLY GOT TO GET ALL THE MODS I WANTED TO WORK!! *dances frenetically* :laugh::laugh::laugh::victory: I'm gonna make a thread so that every user with a h959 G Flex2 can enjoy this tuned experience I achieved! Thank you all for your help! If you guys are interested in knowing what mods I managed to make work on the latest software version of the G Flex2 (that is, on the h959 ones), keep an eye on the thread I'm about to make! *celebrates into oblivion* (erm... this is embarassing... I'm a newbie here and... um... how exactly do I "close" or delete this thread? I mean, my problem is solved so... what do I do?
Install busybox from google play, set selinux to permissive and You guys have to uncheck an option on supersu app. Option named "namespace separation". After uncheck that option reboot phone and try to install viper driver again.
Hey guys,
I'm into the Android from the very beginning and I would love to get rid of a problem which is driving me crazy for some time
I was trying to flash the Viper driver to get the great sound quality again. I'm now on the latest nougat.
Already unlocked the bootloader, rooted it and flashed the TWRP. Saw an thread about how to install it properly on the Honor8 and I did everything correct in my opinion.
I have the 1.26.2-meefik busybox now installed in system/xbin path (which seems to be working correctly overall) and otherwise everything seems working good except that when I try to open the Viper it says that I don't have root OR that i have to install the driver, and after pressing yes my phone just reboots and does the very same thing as previously.
Am I missing something?
Feel free to ask something more if you need.
I had this same situation, just kept installing the driver, reboot, repeat, making no progress... I finally got mine to work thank goodness! Are you remembering to use a root file Explorer and go to /vendor/etc and rename the file named audio_effects.config to audio_effects.config.bak after flashing but before installing V4A? That was my main problem. And you have to be sure to do it on a clean setup, so if you've already installed V4A you need to clean out and start again. Also u need a kernel auditor to set selinux to permissive upon boot. These two steps are key...
Sent from my HUAWEI FRD-L04 using XDA Labs
Have same problem but this fix BigBrad75 gave didn't work.
Isn't that what I suggested? Not being a smarta**, but seriously wondering if I have got a step messed up or backwards or something...? Cause it gave me tons of trouble till I finally got lucky and it actually took
Sent from my HUAWEI FRD-L04 using XDA Labs
Rommco05 said:
I got same problem, solutions for my was:
1. install BusyBox by Meefik ( Google play)
2. install Kernel Adiutor ( https://github.com/yoinx/kernel_adiutor/raw/master/download/app/app-release.apk ) ( Kernel Adiutor from Google play dont work)
3. opem BusyBox tap Install
4. open Kernel Adiutor and go to Misc Controls, change Current SELinux Status: Permissive (after reboot SELinux stay premissive :good
5. flash Viper4 via TWRP
6. go to folder: root/vendor/etc and rename file from audio_effects.conf to audio_effects.conf.bak
7. open Viper4
8. Install driver (thats can take 1-3 min)
9. reboot - done
Click to expand...
Click to collapse
Hi Rommco05,
there are different versions of V4A floating around. Which Version of Viper4Android did you use? Download from where?
Greets....
Rommco05 said:
Hi, Honor 8/Theme,Apps,Modes/https://forum.xda-developers.com/honor-8/themes/viper4android-2-5-0-5-installation-t3468389
Click to expand...
Click to collapse
Thanks, worked for me just as you described. I'm on L09C432B389 BTW, if anybody is interested...
Thanks
Hey guys,
since i got my Oneplus 6, i couldnt get viper to work quite right. Most of the time its just shows "Processing: No" till i restart it and after like a hour or device switch it turns off.
I tried:
Copying the Audioeffects.conf from system/etc to vendor/etc
Using Magisk Audio Compability Module
Using Alternate Magisk V4A Module
Using a Magisk Rom with Build-In V4a (currently xXx 2.8)
Disabling Dirac and Services
but nothing worked
thanks for your help
i had the same but then i tried to use the other viper release from magisk and it worked. there is this one called hifi and fx
Try exiting the viper app with the 3 dots top right hand corner. That is what worked for me
dgunn said:
Try exiting the viper app with the 3 dots top right hand corner. That is what worked for me
Click to expand...
Click to collapse
that works for like 10 mins and then it gets killed
byReqz said:
that works for like 10 mins and then it gets killed
Click to expand...
Click to collapse
Sounds to me like you need to disable the battery optimizations for Viper. It's almost as if your phone is detecting High battery drain and shuts down the app
dgunn said:
Sounds to me like you need to disable the battery optimizations for Viper. It's almost as if your phone is detecting High battery drain and shuts down the app
Click to expand...
Click to collapse
yeah thats what i thought too, i zried whitelisting it and installing it as system app (+ magisk module) but it didnt seem to work.
I removed the one from my rom and tried the magisk repo version again and somehow its working till now
byReqz said:
yeah thats what i thought too, i zried whitelisting it and installing it as system app (+ magisk module) but it didnt seem to work.
I removed the one from my rom and tried the magisk repo version again and somehow its working till now
Click to expand...
Click to collapse
I was unaware that you were using the magisk module. I could not get that one to work either
dgunn said:
I was unaware that you were using the magisk module. I could not get that one to work either
Click to expand...
Click to collapse
the normal one doesnt work with viper doewsnt it?
Try just exiting the viper app then reopening it. I had this problem before and it just randomly went away.
TheNetwork said:
Try just exiting the viper app then reopening it. I had this problem before and it just randomly went away.
Click to expand...
Click to collapse
it only works for a few mins that way
I'm using the Android p beta and i don't have the problems with viper as i did with oxygen os 5. it's always processing for my headphones, either plugged in or Bluetooth. the only exception is sometimes after receiving a call while listening to music, after the call is over and my music resumes, viper is no longer processing. not every time though. i used the latest magisk and the viper module in the screenshot.
i also didn't make any changes to conf files, just installed through magisk download. rebooted, opened viper fx, gave it storage permissions and turned it on.
Had the same problem, but was able to resolve it by choosing the legacy (non-material) interface when installing the Magisk module. I still flashed the full module and selected the latest version, just not the material interface. It may have been something else, but I've updated my ROM (HavocOS) several times and even done a couple full fastboot stock resets and the issue is yet to resurface.
TuxRuffian said:
Had the same problem, but was able to resolve it by choosing the legacy (non-material) interface when installing the Magisk module. I still flashed the full module and selected the latest version, just not the material interface. It may have been something else, but I've updated my ROM (HavocOS) several times and even done a couple full fastboot stock resets and the issue is yet to resurface.
Click to expand...
Click to collapse
as i said, idk why but its working now.and im on material now
byReqz said:
Hey guys,
since i got my Oneplus 6, i couldnt get viper to work quite right. Most of the time its just shows "Processing: No" till i restart it and after like a hour or device switch it turns off.
I tried:
Copying the Audioeffects.conf from system/etc to vendor/etc
Using Magisk Audio Compability Module
Using Alternate Magisk V4A Module
Using a Magisk Rom with Build-In V4a (currently xXx 2.8)
Disabling Dirac and Services
but nothing worked
thanks for your help
Click to expand...
Click to collapse
I've had this problem on an Samsung S7 Edge, S8 Plus, and now, a Oneplus 6.
Everything appears to look good on Driver Status, except "Processing:No" and it's audibly not on.
What's worked for me in this specific situation is replacing the configuration file "audio_effects.conf" in /system/vendor/etc with another configuration file that I found in another XDA thread. So here's the concrete steps:
1. Install the viper4android FX module from Magisk manager that has four devs (v1.7 as i write this) and reboot. I don't know if this method will work with other v4a modules. Note that Processing will work temporarily, but likely won't survive a reboot.
2. Download this file (files_for_v4a.zip) from here:
https://forum.xda-developers.com/ga...laxy-s8-s8-t3596933/post72049061#post72049061
3. Unzip files_for_v4a.zip and make note where it extracted. (You'll need one of its contents, audio_effects.conf, later)
4. Using a file explorer with root capability, go to the following directory:
/system/vendor/etc
5. Copy the existing "audio_effects.conf" to another directory, for example /download, to use as a backup in case this goes badly
6. Copy the file "audio_effects.conf" that you unzipped earlier to /system/vendor/etc, overwriting the existing file.
7. Reboot and test v4a.
Good luck!
Note: The Pulse feature of a custom NavBar in custom ROMS based on LOS 15.1 will not work if you do the above.
Although I'm just a hack, I modded an "audio_effects.conf" file using commits from the above to work with Pulse. I've tested it on my device (despite my lack of know-how, it seems to work for me and others!), so be aware of this if you download the following file and use it (by renaming it audio_effects.conf and placing it in /system/vendor/etc):
reaper000 said:
I've had this problem on an Samsung S7 Edge, S8 Plus, and now, a Oneplus 6.
Everything appears to look good on Driver Status, except "Processing:No" and it's audibly not on.
What's worked for me in this specific situation is replacing the configuration file "audio_effects.conf" in /system/vendor/etc with another configuration file that I found in another XDA thread. So here's the concrete steps:
1. Install the viper4android FX module from Magisk manager that has four devs (v1.7 as i write this) and reboot. I don't know if this method will work with other v4a modules. Note that Processing will work temporarily, but likely won't survive a reboot.
2. Download this file (files_for_v4a.zip) from here:
https://forum.xda-developers.com/ga...laxy-s8-s8-t3596933/post72049061#post72049061
3. Unzip files_for_v4a.zip and make note where it extracted. (You'll need one of its contents, audio_effects.conf, later)
4. Using a file explorer with root capability, go to the following directory:
/system/vendor/etc
5. Copy the existing "audio_effects.conf" to another directory, for example /download, to use as a backup in case this goes badly
6. Copy the file "audio_effects.conf" that you unzipped earlier to /system/vendor/etc, overwriting the existing file.
7. Reboot and test v4a.
Good luck!
Note: The Pulse feature of a custom NavBar in custom ROMS based on LOS 15.1 will not work if you do the above.
Although I'm just a hack, I modded an "audio_effects.conf" file using commits from the above to work with Pulse. I've tested it on my device (despite my lack of know-how, it seems to work for me and others!), so be aware of this if you download the following file and use it (by renaming it audio_effects.conf and placing it in /system/vendor/etc):
Click to expand...
Click to collapse
Thanks for your long answer, will be trying the files if this module fails again.
Also im not on a LOS Based Rom, im on OOS and GravityBox
byReqz said:
Thanks for your long answer, will be trying the files if this module fails again.
Also im not on a LOS Based Rom, im on OOS and GravityBox
Click to expand...
Click to collapse
Just seeing if I can help! And I did the same sequence of steps on OOS as well ... But I haven't run gravity box in awhile. Hope it works out for you.
reaper000 said:
Just seeing if I can help! And I did the same sequence of steps on OOS as well ... But I haven't run gravity box in awhile. Hope it works out for you.
Click to expand...
Click to collapse
I tried everything but it still needs a restart to be working sometimes, do you know if i have to disable dirac or something?
byReqz said:
I tried everything but it still needs a restart to be working sometimes, do you know if i have to disable dirac or something?
Click to expand...
Click to collapse
I haven't messed with dirac at all, and v4a still works for me.
Some clarification, please:
Did you uninstall the v4a magisk module that came with xXx and reboot?
Then go to magisk manager and install v4a fx materialized1.7 and follow the rest of the steps outlined in my post?
reaper000 said:
I haven't messed with dirac at all, and v4a still works for me.
Some clarification, please:
Did you uninstall the v4a magisk module that came with xXx and reboot?
Then go to magisk manager and install v4a fx materialized1.7 and follow the rest of the steps outlined in my post?
Click to expand...
Click to collapse
yeah, its 1.7 from magisk repo, disabling dirac seems to help a bit but not everytime
byReqz said:
yeah, its 1.7 from magisk repo, disabling dirac seems to help a bit but not everytime
Click to expand...
Click to collapse
And you replaced the audio_effects.conf file in /system/vendor/etc with the one from the downloaded zip?
(Sorry to belabor the point, but it's not clear to me you tried all that)