Viper4android and Dolby Atmos are not working - Galaxy Note 4 Q&A, Help & Troubleshooting

I'm running Ditto Note 7 ROM on 6.0.1 on my N910C
I already have Busybox and SELINUX set to permissive.

Someone please help

Ok I managed to fix it, I followed this guy's workaround.
slit said:
Thanks, but the ViPER4Android-supolicy zip took care of selinux
Also, if anyone's interested I've finally managed to make it work permanently. You need to remove the deep buffer stuff from audio_policy.conf (placed at system/etc) with a root explorer, AND remove/uninstall/disable SoundAlive in system apps.
Click to expand...
Click to collapse

Related

[GUIDE]How to get Viper4Android to work on 6.0 Beta.

I'm a HUGE fan of V4A, so I finally got it to work, and today I'll share with You how to get to work.
Make sure that You have root and TWRP or Phillz installed
Download V4A from PlayStore
Download BusyBox(Stericson) and install it to System/xbin(Su/bin directory probably would work too)
Install V4A drivers.
Rename SoundAlive_31_M folder in System/Priv-App to something else or cut and paste it somewhere else.
Flash this file Click here!
In V4A change mode to compatibility.
Done!
Thanks to MaximumEntropy for his file.
Additional info:
6.0 beta
SuperSu 2.66 beta
V4A 2.3.4.0
i have given this a go as per your guide but is still not working on 6.0.1?
It's just acting like it did before v4a installed audio effects don't make a difference any help anyone?
thanks
iNeoTom
Likewise here, in driver status it says it is supported and that neon is enabled but it is not processing or enabled overall. I've tried changing to compatibility mode and normal mode without any change.
Thanks a lot, works flawlessly on 6.0.1!
To get it working I had to replace the audio_effects.conf in system/etc with the one arter97 posted here http://www.arter97.com/browse/S6/M/ViPER/ set the right permissions and reboot. Got a system FC at first but then seems to work flawlessly. Good luck! :good:
This worked! S6 noble ROM 6.0 Thanks!!
delete

Viper4android

is there someone who succes in the installation of this app?
when i open it,it ask if i want to install the drivers and stuck and after few seconds it crash
someone can help me with this ?
Many guys use this and there already was enough discussions, there are even seperate threads created with tutorials, use search for once[emoji14]
I managed to get Viper4Android working this way:
First off, I use stock with systemless root and xposed so the many security features included in stock made it a bit tricky. If you use a custom rom with a custom kernel, it's likely a bit easier.
I flashed my stock image from the google website
I flashed a custom kernel and then Supersu and then the lolliviper zip from this thread: http://forum.xda-developers.com/google-nexus-5/themes-apps/discussion-viper4android-t2543796
I installed busybox from the play store, opened the busybox app and let it install.
I disabled selinux enforcing using the app from this thread:
http://forum.xda-developers.com/showthread.php?t=2524485
Then I ran viper4audio and installed the driver from the app
Then I rebooted into twrp and used the terminal to delete /system/etc/audioeffects.conf and rebooted.
Voila, working Viper4android.
exad said:
I managed to get Viper4Android working this way:
First off, I use stock with systemless root and xposed so the many security features included in stock made it a bit tricky. If you use a custom rom with a custom kernel, it's likely a bit easier.
I flashed my stock image from the google website
I flashed a custom kernel and then Supersu and then the lolliviper zip from this thread: http://forum.xda-developers.com/google-nexus-5/themes-apps/discussion-viper4android-t2543796
I installed busybox from the play store, opened the busybox app and let it install.
I disabled selinux enforcing using the app from this thread:
http://forum.xda-developers.com/showthread.php?t=2524485
Then I ran viper4audio and installed the driver from the app
Then I rebooted into twrp and used the terminal to delete /system/etc/audioeffects.conf and rebooted.
Voila, working Viper4android.
Click to expand...
Click to collapse
By the way, you can run a supolicy script for media server instead of disabling selinux because that would increase security risks and don't you mean audio_effects.conf in vendor? IMO better to add v4a entries than delete it, it's there for a reason I would think
hinxnz said:
By the way, you can run a supolicy script for media server instead of disabling selinux because that would increase security risks and don't you mean audio_effects.conf in vendor? IMO better to add v4a entries than delete it, it's there for a reason I would think
Click to expand...
Click to collapse
Yes! Thanks for the corrections! I haven't done it in a while! ?

[GUIDE] [NOUGAT] Viper4Android

//Thank you all for 30k+ Views. You're amazing guys//
You want Android 8 with Viper4android to?
Thread created check my profile...
Hi,
at first im not responsible for anything that happens to your phone OK?
Fine Let's Start.
If you are on cm skip all until the cm section
Supported kernel list and known errors/bugs see second post
Step 1
- Flash full Factory Images.
- Install TWRP, remember you have to be decrypted.
Step 2
- Install Android 7 ROM by tupac4u / or any other rom / or leave stock
- Reboot //if nessesairy
Step 3
- Flash ElementalX's N Kernel.
- Flash Viper5.0_Stock.zip in Recovery / or any other viper
- Reboot.
Step 4
- Install driver.
- Open File Explorer and delete /system/vendor/etc/audio_effects.conf
- Reboot.
Step 5
- Set enforcing to permissive (You have to do it at every Reboot!).
- In Viper open Menu->FX-CompatibleMode->yes // you can try without, it may work
- Enjoy Viper.
CM Section
1. Flash arise sound mod ( link down below )
2. And IMPORTANT flash super su
3. Disable audio fx and reboot
SPOTIFY FIX
1. Download that file
https://drive.google.com/file/d/0BxyY1q0qeeeEeUFGT3JHeDZLZkE/view
2. Place it under /system/etc
3. Reboot
PURE NEXUS ONLY WORKS WITH BUILD 10/25!!!
If it worked leave a reply.
Alternative Download link for ARISE Viper here:
http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
Unsupported Rom/Kernel
Kernel:
- Stock
- Jolla
ROM:
F.A.Q.
Q: Spotify isn't working with that
A: Force enable Viper4Android and turn FX Mode to compatible. Then restart both applications.
Q: Why ElementalX Kernel?
A: That's the only Kernel who works with Viper except Stock kernel. Elite Kernel may also work but it hasent been updated since the Dev Previews.
Q: Is that also working with the stock rom?
A: Yup. Also works with (nearly) any stock based ROM.
Is there a definite way of checking if it's working? Not by sound?
Yes, just check driver status in viper when something is playing in the background. If it says 'processing', then it's working.
Btw, why would I need custom kernel for viper?
Sent from my Nexus 5X using Tapatalk
how to set permissive mode permanently?
Nightshadow931 said:
Yes, just check driver status in viper when something is playing in the background. If it says 'processing', then it's working.
Btw, why would I need custom kernel for viper?
Click to expand...
Click to collapse
I found that it isn't working on jolla Kernel and Stock.
Did you enable viper in app itself?
Not sure, but maybe you need to enable it on order to see 'processing'..
Did the installation of driver went well?
Sent from my Nexus 5X using Tapatalk
enzippo said:
how to set permissive mode permanently?
Click to expand...
Click to collapse
use a file exlorer with root privileges like es or root explorer and go to /etc/init.d directory, create a file and named "08setperm" (without quotes) and add the below lines in the file and save it..
#!/system/sh
setenforce 0
And give full permission (rwxrwxrwx)
reboot and you should be good. if for some reason your init.d script doesn't launch then download and install universal init.d tool and enable it.
Nice that someone is trying to get Viper4Android to work on Nexus 5x with Android 7.0 (Nougat). Sadly it does not work, tried your way but it does not enable me to get Viper4Android to work in Spotify.
Selinux is in permissive, your viber4android package is in place, audio_effects.conf removed, Android 7 by tupac4u installed and complete factory image installation before all this. No go..
Viper4android driver status does not complain but processing is always "no".
Try some other app like play music, v4a won't work on all apps if they have their own equalizer.
Sent from my Nexus 5X using Tapatalk
Blinkiz said:
Nice that someone is trying to get Viper4Android to work on Nexus 5x with Android 7.0 (Nougat). Sadly it does not work, tried your way but it does not enable me to get Viper4Android to work in Spotify.
Selinux is in permissive, your viber4android package is in place, audio_effects.conf removed, Android 7 by tupac4u installed and complete factory image installation before all this. No go..
Viper4android driver status does not complain but processing is always "no".
Click to expand...
Click to collapse
For those who want to use Viper4android with Spotify change fx compatible Mode to compatible in Viper settings. Then Open Spotify and go to Settings->Equalizer that should bring up Viper. Select Force enable and close Viper and Spotify. Open up both again and Boom Viper is there.
How find Android 7 by tupac4u ??
EDIT.
I found him already
Did someone get it working with stock rooted ROM?
noidea24 said:
use a file exlorer with root privileges like es or root explorer and go to /etc/init.d directory, create a file and named "08setperm" (without quotes) and add the below lines in the file and save it..
#!/system/sh
setenforce 0
And give full permission (rwxrwxrwx)
reboot and you should be good. if for some reason your init.d script doesn't launch then download and install universal init.d tool and enable it.
Click to expand...
Click to collapse
Idk if this will work on the new version, but this zip I've attached here sets the previous ElementalX-N5x-1.17 kernel permissive permanently. I'm not on nougat yet, waiting for Xposed.
trhacker01 said:
Idk if this will work on the new version, but this zip I've attached here sets the previous ElementalX-N5x-1.17 kernel permissive permanently. I'm not on nougat yet, waiting for Xposed.
Click to expand...
Click to collapse
In gonna give it a try
Nightshadow931 said:
Did someone get it working with stock rooted ROM?
Click to expand...
Click to collapse
Me not
Thargorsson said:
In gonna give it a try
Click to expand...
Click to collapse
Nope it don't works
Thargorsson said:
Nope it don't works
Click to expand...
Click to collapse
thats how im running right now, just checked. only with the universal init.d though
noidea24 said:
thats how im running right now, just checked. only with the universal init.d though
Click to expand...
Click to collapse
Ur saying that permissive zip works with the universal init.d?
trhacker01 said:
Ur saying that permissive zip works with the universal init.d?
Click to expand...
Click to collapse
As long as the zip creates/places a file in the init.d to change selinux then i guess it should work

Viper4Android Discussion

Overall I love the Pixel XL, but with all of my previous Android phones having Root access, I have always run Viper4Android, and in my opinion the sound quality output of the stock Pixel is awful by comparison. So, my primary reason to use the awesome work done by those who brought us bootloader unlock and Root, is to be able to use Viper4Android.
With the changes to Pixel partitions and overall structure, as well as the method of Root, so far I have not been able to get Viper4Android working. This thread will be a place for us to discuss what we have tried, learned, and hopefully figure out a solution! I do think that what ever needs to be done to get it working will be the same for both the Google version of the Pixel (XL) and the Verizon version, as the method of Root is the same for both as well as the overall structure for the partitions and images.
So far, after unlocking bootloader, and then using the Root method, I have not gotten Viper4Android to even detect root. This was with stock kernel, and no other changes to any audio files or other settings. I did install a couple of apps (Titanium Backup, Solid Explorer) to validate Root was working. I also tried installing BusyBox, which seemed to install just fine, but no change to Viper.
I am not very up to speed yet on how systemless root may be a factor in this, the Pixel XL is the first device I have had with it. Anyway, I will keep plugging away at some things and post what I learn.
once there is a custom recovery, it will be very easy to flash packages that will make viper work..
search XDA for the Arise Sound mods
What error are you getting? I'm getting a bad BusyBox error. I fixed the I/O error by renaming audio_effects.conf.
Sent from my Pixel XL using Tapatalk
sionicion said:
What error are you getting? I'm getting a bad BusyBox error. I fixed the I/O error by renaming audio_effects.conf.
Click to expand...
Click to collapse
Viper4Android cannot detect root. See screenshot.
mrhds said:
Viper4Android cannot detect root. See screenshot.
Click to expand...
Click to collapse
I got that error when viper was in priv-app, make sure you set the kernel to permissive. I do it by going into the terminal app and entering the commands su, to gain root, setenforce 0, to switch to permissive, getenforce, to make sure it's permissive.
Sent from my Pixel XL using Tapatalk
To make viper work we have to use the same trick that is used for adaway but with all the files needed by viper which is:
- Move the files to /su
- Make copies of the files viper needs to change, make the changes and copy the modified ones to /su
- Create a /su/su.d/60viper with mount binds on all the files
Or have a modified version of Viper that could read from /su or /system_root instead.
exadeci said:
To make viper work we have to use the same trick that is used for adaway but with all the files needed by viper which is:
- Move the files to /su
- Make copies of the files viper needs to change, make the changes and copy the modified ones to /su
- Create a /su/su.d/60viper with mount binds on all the files
Or have a modified version of Viper that could read from /su or /system_root instead.
Click to expand...
Click to collapse
That's nothing I can figure out but it does confirm my thoughts that viper is having trouble because there is no /system and instead a /system_root. I guess we'll have to wait it out until someone patches viper. Or someone figures out that trick and posts a guide for it.
Sent from my Pixel XL using Tapatalk
I did it! I can't believe it! Viper is working!
So I was googling manual installs of Viper and came across Arise, somebody said you just have to paste the contents to system if you can't flash. That's what I've been doing kinda but it wasn't working before. Anyway I got Arise and went into the zip and into the Leviticus folder and pasted the contents where I believed they belonged. I got some errors so I had to use FX and ES File Explorer together, to rename files, copy files over, etc. I copied over the files to the folders underneath /system_root/system/, except su and su.d. su is just /su in my file apps. Although I think the permissive script is in the wrong spot since I still had to manually run the setenforce 0 command.
Doing it manually this way avoids Viper wanting to install a driver, it's just ready to be powered on, avoiding I/O and busybox errors. Leviticus 1.3 is what I used from the Arise website since I couldn't find any other download and it was on the header of the website.
Now if I could just figure out how to increase sound output. The mixer_paths.xml is different slightly, the digital volumes are like digital mix volumes, and changing their values doesn't seem to have an effect. I still have to play around with that, I might just wait for someone else to discover what values alter the headphone sound output. But at least I made progress! Hope this helps some people out.
Sent from my Pixel XL using Tapatalk
Viper is working!!
@Mentalmuso posted his work on a script that takes care of permissive, busybox issues, etc.! Thanks a ton! I downloaded the zip package, ran the script and it works! Here is the link:
http://forum.xda-developers.com/pixel-xl/themes/mod-weta-audio-t3491179
@sionicion: I was about to test out your route as it looked promising, but then noticed the other post
quick question... (this may be stupid)
If you root - get viper working
can you then unroot and be good as far as safetynet and stuff?
Or does viper ALWAYS need root?
I'm trying to warm up to the idea of not rooting this phone and maybe doing android pay.
So much stuff that I used to use root for isn't needed anymore (culminating with the "autotools" addon for tasker)
But I just don't know if I can live without viper, it makes such a huge difference.
Thanks,
I've learned to live without it. It's tough as Viper is really good but I really grew tired of coming up with workarounds for an app that isn't even maintained anymore. Fiddled around with the stock eq in Play Music for awhile before I was satisfied.
Yea, I really miss Viper too but not sure if I want to root anymore. The only reason I use Viper is for the volume boost for my BT earbuds when watching mkv files in MX Player. For some, all mkv files play at a pretty low volume. Viper is able to increase it substantially. I sitll haven't found a non-root substitute for this problem yet. If anyone can advise on an app that does volume boost for BT headsets, that would be greatly appreciated.

xposed framework for huawei p10 lite?

Recently it has come out xposed framework by rovo89 for android N:
https://forum.xda-developers.com/showthread.php?t=3034811
Has anyone tried it on the p10 lite, with rom stock + recovery + root? or in some other device huawei with rom stock and emui 6?
Thanks in advance.
I've tried it and it works fine, but since I rooted my p10 and installed xposed my battery started to drain noticeably faster, so I went back to stock.
I use xposed with magisk v14 and no battery drain(I think)
Testing and work fine.
Some times, after reboot, xposed in disabled. Need run this attached script on init, in /su/su.d
mpiero11 said:
Testing and work fine.
Some times, after reboot, xposed in disabled. Need run this attached script on init, in /su/du.d
Click to expand...
Click to collapse
I get this too, but to fix I just untick all enabled modules in xposed, reboot, enable modules again and reboot again.
hayabusa2yk said:
I use xposed with magisk v14 and no battery drain(I think)
Click to expand...
Click to collapse
How did you install magisk?
plerohero said:
How did you install magisk?
Click to expand...
Click to collapse
Just flash in TWRP
sorry for my bad English
mpiero11 said:
Testing and work fine.
Some times, after reboot, xposed in disabled. Need run this attached script on init, in /su/su.d
Click to expand...
Click to collapse
I am facing the same problem and when I tried to use your solution its not working either.
I somehow able to found out the error (by using init.d scripts app):
Path is not correct for
/data/user_de/0/de.robv.android.xposed.installer/conf/enabled.modules.list
/data/user_de/0/de.robv.android.xposed.installer/conf/modules.list
On checking the path appears to be correct. Then whats the issue here? Please guide.
My P10-Lite is rooted. So I can see the path actually exists in my phone's root folder.
Thanks
mzeeshan2 said:
I am facing the same problem and when I tried to use your solution its not working either.
I somehow able to found out the error (by using init.d scripts app):
Path is not correct for
/data/user_de/0/de.robv.android.xposed.installer/conf/enabled.modules.list
/data/user_de/0/de.robv.android.xposed.installer/conf/modules.list
On checking the path appears to be correct. Then whats the issue here? Please guide.
My P10-Lite is rooted. So I can see the path actually exists in my phone's root folder.
Thanks
Click to expand...
Click to collapse
Change permisions for .sh file, chmod 777 to script, reboot and enjoy.
No problems for my.

Categories

Resources