Related
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
So I've been getting lots of different questions about how to get this and that on android 7.0 nougat so to make it easier for everyone to find ill create this thread.
1. TWRP
Is twrp available for N? If so where can I find it?
http://forum.xda-developers.com/p9/how-to/twrp-3-0-2-0-n-t3506947
2. ROOT
Oh cool now I have twrp. So how can I root?
Download phh r275 version and flash
Download and install Material phh apk: Release post
Now you should be good to go. If any issues feel free to ask here or in phh official thread.
3. BUSYBOX
User friendly zip flash this and the below steps isn't needed!
Flashable zip (1.25.1) : https://mega.nz/#!zlRm3S4B!9rAtfi0wI8oFu6xjJITgF0dRwV21UPsxvZQZzMo6VXk
This one is a bit tricky. If you run root. But
Download jrummy's busybox on Gplay.
Select installation folder to /system/xbin or if u don't want to touch system folder use /sbin if available. U can replace jrummy''s busybox with stericsson version if you like it better. But you must have installed jrummys version first if you're booted into android. Else stericsson busybox might have issues installing. Or u can use zips which contains busybox Google busybox flashable.
4. VIPER
More user friendly if using this zip the below steps should only need se Linux mode changer!
Flashable zip: https://mega.nz/#!f8wlzIrB!vVCAv-xqWB8lOrcQTgIyFL0WS7MFsE9iFb08E1YKV2Y
Is quite a mess to get working. You need se Linux mode set to permissive. Flash guitarheroes version of v4a (2.5.0.5) once flashed you need to replace the audio effects in /vendor/etc/audio_effects else you'll get I/O driver installation failed. Copy the .so files to /system/lib and /system/lib64 and set correct permission. If you have wrong busybox message. Try different versions of busybox but I use latest from stericsson and it works great. Hope u get it working.
Oh and don't forget to allow sd storage access or you'll get driver I/O error as well. And se Linux changed to permissive use se Linux mode changer for it. It works great with phh!
5. MAGISK
As it seems to be now. Magisk won't work due to loop issues on boot. And mount seems to have losetup fail 1 on mounting a .img while booted.
6. Xposed
Not yet available. Be patient rovo needs time we can wait for him
7. comes soon.
More stuff.
Sent from my FRD-L09 using Tapatalk
how does your audio_effects.conf look like? i used one for aosp from "ARISE+Sound+Systems+Deuteronomy+2.3.3.zip" and got it working but don`t know if this is the right one for our device (huawei phones).
paratox said:
how does your audio_effects.conf look like? i used one for aosp from "ARISE+Sound+Systems+Deuteronomy+2.3.3.zip" and got it working but don`t know if this is the right one for our device (huawei phones).
Click to expand...
Click to collapse
It doesn't matter if it's aosp. Since it is for v4a it will work. As long as the audio effects works it doesn't matter.
Also I just finished my hopefully new nougat viper4android zip (i made my own for M with material designed version for my s5 neo) which worked fine until now.
Now it extract all files to its locations even to /vendor partition which all zips I used previously never had. I'll also update busybox zip which previous available is 1.24.2 which I'll bump up to 1.25.1.
I'll also going to upload my stuff to android file host. But that will be later
New files can be found https://mega.nz/#F!HlpzlaZL!wGNoJinVPZL0YiBcdbLlKA
Tapatalk is messing with the link
Sent from my FRD-L09 using Tapatalk
Updated op with latest busybox by stericsson. More user friendly now
Sent from my FRD-L09 using Tapatalk
LastStandingDroid said:
Updated op with latest busybox by stericsson. More user friendly now
Click to expand...
Click to collapse
Nice job mate!
dodgedroid said:
Nice job mate!
Click to expand...
Click to collapse
Easy to do when you got a zip for it just update the busybox executable and replace old one
Sent from my FRD-L09 using Tapatalk
Installation of ARISE
paratox said:
how does your audio_effects.conf look like? i used one for aosp from "ARISE+Sound+Systems+Deuteronomy+2.3.3.zip" and got it working but don`t know if this is the right one for our device (huawei phones).
Click to expand...
Click to collapse
How did you installed ARISE in Nougat?
I've been trying all day and I'll always end with an I/O or Busybox error. I tried a lot of things, like changing /vendor/etc/audio_effect.conf to audio_effect.conf.bak or installing Busybox into system/bin, but none of them seems to work for me.
I'm on B361 btw. And sorry for answering an old post
LastStandingDroid said:
Also I just finished my hopefully new nougat viper4android zip (i made my own for M with material designed version for my s5 neo) which worked fine until now.
Now it extract all files to its locations even to /vendor partition which all zips I used previously never had...
New files can be found https://mega.nz/#F!HlpzlaZL!wGNoJinVPZL0YiBcdbLlKA
Click to expand...
Click to collapse
Do you know, is your Viper4Android installer compatible with the following rooting/Busybox configuration:
- L09 c432/b378
- TWRP 3.1.0-0
- SuperSU-v2.79-201612051815-EMUI5.0.zip
- Rummy"s BusyBox (installed to /system/xbin)
as described by @hakaz and @Atarii in the post #102 and follow-ups:
https://forum.xda-developers.com/showpost.php?p=71588837&postcount=102
Also, should SELinux really be switched to Permissive mode for V4A to work on P9 with Nougat?
Thanks
zgfg said:
Do you know, is your Viper4Android installer compatible with the following rooting/Busybox configuration:
- L09 c432/b378
- TWRP 3.1.0-0
- SuperSU-v2.79-201612051815-EMUI5.0.zip
- Rummy"s BusyBox (installed to /system/xbin)
as described by @hakaz and @Atarii in the post #102 and follow-ups:
https://forum.xda-developers.com/showpost.php?p=71588837&postcount=102
Also, should SELinux really be switched to Permissive mode for V4A to work on P9 with Nougat?
Thanks
Click to expand...
Click to collapse
Yes it should be compatible and yes u need to switch to permissive mode else it'll be asking you to install over again, or simply not start to work
Sent from my CUBOT_MANITO using Tapatalk
LastStandingDroid said:
Yes it should be compatible and yes u need to switch to permissive mode else it'll be asking you to install over again, or simply not start to work
Click to expand...
Click to collapse
Yes, thanks, I have flashed your Viper.zip through TWRP and installed vViPERFX_v2.5.0.5.apk
I have also installed SELinuxModeChanger and set SELinux mode to stay Permissive over rebooting
Viper4Android works fine - thanks
LastStandingDroid said:
5. MAGISK
As it seems to be now. Magisk won't work due to loop issues on boot. And mount seems to have losetup fail 1 on mounting a .img while booted.
Click to expand...
Click to collapse
in my p9 lite emui 5.0 magisk is successfully installed !
it worked by flashing the modded boot.img by @HassanMirza01 and by setting selinux to permissive !!
big thanks to @Paolo83 who found this method
simo255 said:
in my p9 lite emui 5.0 magisk is successfully installed !
it worked by flashing the modded boot.img by @HassanMirza01 and by setting selinux to permissive !!
big thanks to @Paolo83 who found this method
Click to expand...
Click to collapse
Having Magisk, can you now also install Xposed?
PS: Please provide links to your resources and threads.
Btw, you have P9 Lite - does the method for Magisk apply also to (regular) P9 (single SIM)?
zgfg said:
Having Magisk, can you now also install Xposed?
PS: Please provide links to your resources and threads.
Btw, you have P9 Lite - does the method for Magisk apply also to (regular) P9 (single SIM)?
Click to expand...
Click to collapse
it workes because we have a modded boot.img created by @HassanMirza01, ask him what he did so as to he will do the same for p9 boot.img(or anyone else)
install selinux and set it to permissive, after that install magisk app via playstore and click on autoinstall
no xposed isnt working because there is no xposed for Nougat.
simo255 said:
it workes because we have a modded boot.img created by @HassanMirza01, ask him what he did so as to he will do the same for p9 boot.img(or anyone else)
install selinux and set it to permissive, after that install magisk app via playstore and click on autoinstall
no xposed isnt working because there is no xposed for Nougat.
Click to expand...
Click to collapse
Can you post the link to install his kernel?
Danymat said:
Can you post the link to install his kernel?
Click to expand...
Click to collapse
it won't work because it's a boot.img of p9 lite not for p9
simo255 said:
it won't work because it's a boot.img of p9 lite not for p9
Click to expand...
Click to collapse
So for p9 we don't have any solutions to install magisk?
Danymat said:
So for p9 we don't have any solutions to install magisk?
Click to expand...
Click to collapse
try to install the pre rooted boot.img (phh one) via this link https://forum.xda-developers.com/p9/development/root-pre-rooted-boot-img-p9-nougat-b378-t3574548
and follow the steps that i wrote above
simo255 said:
in my p9 lite emui 5.0 magisk is successfully installed !
it worked by flashing the modded boot.img by @HassanMirza01 and by setting selinux to permissive !!
big thanks to @Paolo83 who found this method
Click to expand...
Click to collapse
Is this using a Magisk.img in /data folder?
As said magisk can be made working since we had supersu working by chain I still doubt it uses a loop
Sent from my CUBOT_MANITO using Tapatalk
LastStandingDroid said:
Is this using a Magisk.img in /data folder?
As said magisk can be made working since we had supersu working by chain I still doubt it uses a loop
Click to expand...
Click to collapse
no there is no magisk.img folder, but there is a magisk folder which include those files (look at the screenshot
simo255 said:
no there is no magisk.img folder, but there is a magisk folder which include those files (look at the screenshot
Click to expand...
Click to collapse
Yes this is how Magisk is being made working
Sent from my CUBOT_MANITO using Tapatalk
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
Hi guys,
My Pixel are systemlessly rooted with Magisk since many months now, but for some reasons I'm tired by the method of Magisk: I want to touch at the /system partition, move or delete or edit system files and apps, and with Magisk I can't do it.
Okay, Magisk was pretty useful for keeping Safetynet pass, but with Xposed this ability becomes useless for me. Only things I'm still using is Magisk Hide for using Netflix or NFC paiment app, and Sony Framework module for using PS4 Remote Play.
Before I'm using Magisk and his systemless mode I was using SuperSU, and with it I had no problem with the system partition or with différents things like flashing Viper4android (didn't works whatever the way I use, magisk module or old system mode, it says the drivers need to be reinstalled), mouting partition/making file partition in Linux Deploy, stop background app, modifying the booting apps...
So I'm here now: are they exist a method for having system mode root and still using magisk modules ? Or maybe I've using the wrong way with Magisk and I've missed something for properly having root access ?
Thanks for your help ?
billiepreks said:
So I'm here now: are they exist a method for having system mode root and still using magisk modules ? Or maybe I've using the wrong way with Magisk and I've missed something for properly having root access ?
Thanks for your help ?
Click to expand...
Click to collapse
the whole point of magisk is to systemless modifications. I'm not sure that I follow all of the modifications that you want to make to the system partition?? or rather the specific apps that you want to use... but I can tell you that your /system partition (and others) are just mirrored with magisk and are tmpfs file systems...
I think the real /system lives in /dev/magisk/mirror/system, unless I'm mistaken....
question though; if you prefer SuperSU and only use magisk for safetynet, then why not just use a custom kernel that passes safetynet + SuperSU + suhide?. ... and then use that xposed or whatever....
anyhoo, you definitely have root access. but the intention with magisk and it's modules is to modify the system without actually modifying it directly....
nine7nine said:
the whole point of magisk is to systemless modifications. I'm not sure that I follow all of the modifications that you want to make to the system partition?? or rather the specific apps that you want to use... but I can tell you that your /system partition (and others) are just mirrored with magisk and are tmpfs file systems...
I think the real /system lives in /dev/magisk/mirror/system, unless I'm mistaken....
question though; if you prefer SuperSU and only use magisk for safetynet, then why not just use a custom kernel that passes safetynet + SuperSU + suhide?. ... and then use that xposed or whatever....
anyhoo, you definitely have root access. but the intention with magisk and it's modules is to modify the system without actually modifying it directly....
Click to expand...
Click to collapse
Thanks for your help ?
If Magisk create a mirror of /system as your said, this explain many things that I didn't knew since now.
This night I've made a clean installation of my Pixel, on stock 7.1.2 NJH47F with ElementalX 1.15 for hiding the unlocked bootloader, then I've flashed SuperSU 2.82 SR5. On xda I've seen that suhide 0.55 are discontinued since one year, and suhide-lite 1.09 who works with SuperSU 2.89 are uncompatible with Xposed, so I didn't flash it. There is a way to hide SuperSU with Xposed ?
For my needs with the /system partition, I'll try to explain better myself, I give you some examples:
- Uninstalling system app in ES Explorer or TiBu, it works but after reboot those apps are still here.
- Editing files like build.prop, unable to save the edited file or to replace original file by a modified one
- installing Viper4android drivers, it says "drivers needs to be reinstalled" everytime I launch it
- Linux Deploy, an app for running GNU/Linux distrib on your device, works the first time I launch it, but after reboot he said he didn't get root permission or found busybox, it's very strange.
Many things who worked before with SuperSU 2.79.
Edit : and what about SuperSU and CCMT ?
billiepreks said:
If Magisk create a mirror of /system as your said, this explain many things that I didn't knew since now.
This night I've made a clean installation of my Pixel, on stock 7.1.2 NJH47F with ElementalX 1.15 for hiding the unlocked bootloader, then I've flashed SuperSU 2.82 SR5. On xda I've seen that suhide 0.55 are discontinued since one year, and suhide-lite 1.09 who works with SuperSU 2.89 are uncompatible with Xposed, so I didn't flash it. There is a way to hide SuperSU with Xposed ?
Click to expand...
Click to collapse
You should look in Magisk's log to get a better idea of how it changes your system. trting to modify /system is pointless since it is a tmpfs mount (temperary)...
unfortunately, i can't help much with xposed. i don't use it. after it didn't work with Nougat, i ported a couple of it's modules to my rom (at the time) and then i got the pixel and i run Oreo + my own custom kernel + magisk...
xposed isn't providing any 'suhide' tyype functionality?
billiepreks said:
For my needs with the /system partition, I'll try to explain better myself, I give you some examples:
- Uninstalling system app in ES Explorer or TiBu, it works but after reboot those apps are still here.
- Editing files like build.prop, unable to save the edited file or to replace original file by a modified one
Click to expand...
Click to collapse
again, no point in editing your /system partition, it's a tmpfs mount, of course - any modifications will disappear on reboot.... you probably need to edit the real /system partition to make any change stick.
as far as the other apps, they obviously are trying to modify your aystem partition, which is why they don't work.... i think that you could install soumd mods via magisk modules?
i would recommend.consulting relevant forum threads on specific topics/apps though. u are bound to get better solutions&.
@billiepreks
Did you find the solution?
I'm in the same situation.
Did you try using TWRP's filemanager? I think it has true system access. You just need to mount the partition.
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)