Related
Hi folks,
Did anyone get viper4android (XHiFi or FX) working on the G4? I tried the normal lollipop version but it screws up the camera; video recording fails within 1 second, probably due to some ALSA config or whatever (I'm no expert). I did see some closed thread (audio-engine-absolute-sound-project-t3015180"]http://forum.xda-developers.com/android/software/audio-engine-absolute-sound-project-t3015180[/URL]) on TASP where @ahrion did his best to make an all-in-one package for install on newer devices. I will see how that goes, but I'm more hoping on someone chiming in to tell me how to do it instead of reinventing the wheel so to speak...
- update -
Just tried the TASP package found elsewehere on the internet (13b version) and that seems to work, except for the permissive mode which doesn't stick to permissive. I'm running v10b (or 10c depending how you look at it) and it seems the adb su 0 setenforce 0 command doesn't work like it did on 10a?
So last step, I'm stuck on is setting SELinux to permissive... Iet's google some more
Don't you need to be rooted for viper to work? That's 1 of the main reasons I want root
Sent from my VS986 using Tapatalk
Yes and I have root. It's definitely SELinux, setenforce 0 does the trick until reboot...
https://www.dropbox.com/s/vri6pb4vb38bhsu/viper_v2.3.4.0_-_remove_fx_build_fix.zip?dl=0
Gesendet von meinem LG-H815 mit Tapatalk
Thanks, interesting... but, what exactly am I flashing with this? Looks like a modified viper installer, but does it also take care of SELinux?
Who made this ? I want to see if there is any updates,working good for me !
I thought you couldn't permanently change SELinux to permissive on Android 5 unless you were using a custom firmware like AOSP.
leijonasisu said:
I thought you couldn't permanently change SELinux to permissive on Android 5 unless you were using a custom firmware like AOSP.
Click to expand...
Click to collapse
You thought right.
There's an app on Fdroid called "SeLinux Mode Changer" that'll set the SeLinux state to permissive on every boot. But Google doesn't like the app, so it randomly remembers you to remove the app.
About gave up for months, then it clicked in my mind when i saw a post mention to make sure all other audio apps redirect eq to viper, and if not, change them. Even if you dont use a certain audio player app, change it too.
Problem is, i could not get the lg music app (which i never use) to change the equalizer to viper, it just had it's own default settings, so i ignored it. So i decided to revisit the lg app, and froze the app with link2sd, i also froze the lg video app too, just in case. Rebooted and now viper sees NEON and i can even run without compatibility mode (which did not work consistantly for me) .
I tried all steps to get this to work, not sure what other things are needed for everyone else, but i tried moving viper to system, installed selinuxmodechanger, maybe this can be uninstalled now, i have no idea. I have no plans to fix what isnt broken and find out myself, so just try freezing lg music app for starters.
Hope it works for you, if so, let the community know what steps you had to do!
involver said:
Hi folks,
Did anyone get viper4android (XHiFi or FX) working on the G4? I tried the normal lollipop version but it screws up the camera; video recording fails within 1 second, probably due to some ALSA config or whatever (I'm no expert). I did see some closed thread (audio-engine-absolute-sound-project-t3015180"]http://forum.xda-developers.com/android/software/audio-engine-absolute-sound-project-t3015180[/URL]) on TASP where @ahrion did his best to make an all-in-one package for install on newer devices. I will see how that goes, but I'm more hoping on someone chiming in to tell me how to do it instead of reinventing the wheel so to speak...
- update -
Just tried the TASP package found elsewehere on the internet (13b version) and that seems to work, except for the permissive mode which doesn't stick to permissive. I'm running v10b (or 10c depending how you look at it) and it seems the adb su 0 setenforce 0 command doesn't work like it did on 10a?
So last step, I'm stuck on is setting SELinux to permissive... Iet's google some more
Click to expand...
Click to collapse
Any chance you have a link to download TASP 13B? I absolutely cannot find it on the official dev page. Maybe I am blind.
I've sent you a PM with the link
involver said:
Yes and I have root. It's definitely SELinux, setenforce 0 does the trick until reboot...
Click to expand...
Click to collapse
Enable Init.d on your rom and put a script with the following lines in it in the /etc/init.d folder.
#!/system/bin/sh
setenforce 0;
That should set SELinux to permissive at runtime.
Hi - thanks for your tip, but I've moved on to the V10 and then to the OP3 since then
Hey guys. I'm trying to get viper4android working on my Nexus 5x running the most recent stable version of Dirty Unicorns.
I tried just normally installing the apk. Changing selinux to permissive. I have the newest version of su and BusyBox installed and yet the driver refuses to install. Every time I restart my phone it says I need to install the driver.
I've been looking around online and I can't seem to find a good answer for what exactly I need to do to get it working.
The popular thread in the Nexus 6 section has way to much info and I just can't follow it to install it properly. I basically want viper4android so I can use pulse with Spotify.
Any help would be appreciated. Thank you!
Flash either of these ViperAudio or ViperAtmos (if you want Dolby Atmos too) in TWRP. It works even with systemless root and enforcing SELinux.
przemcio510 said:
Flash either of these ViperAudio or ViperAtmos (if you want Dolby Atmos too) in TWRP. It works even with systemless root and enforcing SELinux.
Click to expand...
Click to collapse
Worked great! Thank you very much for the help!
Hi y'all, first off I have the G920P, just recently upgraded to Nougat QC7 stock ROM, modified and running the SkyHigh kernel v5.01 with Magisk v12. Everything runs pretty smooth, even got Liveboot working successfully (there's a reason I mention Liveboot.) Now I decided to try to get Viper4Android to work. Of course, installing the standard apk fails when it comes to installing the driver. So I tried the V4A Magisk module and it installed fine, however on reboot, my Liveboot no longer works and when opening the V4A app it asks to install the driver, I hit yes and it says it successfully installed and to please reboot. I reboot and of course Liveboot still doesn't show, but otherwise it boots fine. Once I re-open the V4A app it is asking me to install the driver yet again, and the whole system at times seems a bit unstable until I disable the V4A module in Magisk Manager. Does anyone have any ideas, or has anyone gotten this to successfully work? If so I'd love a suggestion lol. I really would like to keep my Liveboot working, but I'd kinda like to get Viper working too. Thanks in advance for any help, suggestions, ideas, etc.
Chuck
I could not get the V4A module to install under Magisk 12; however, it works just fine with Magisk 13.
This is the version that I used: https://www.androidfilehost.com/?fid=745425885120735287
Magisk Uninstaller (should not be needed, but if you want it) is here: https://www.androidfilehost.com/?fid=745425885120735289
NOTE: You are, I believe using the @tdhite kernel, which is based in Magisk 12. Not sure what the impact of installing Magisk 13 will be.
The kernel is fine with Magisk v13 (beta, to be sure is all that is released there). Magisk v13 beta still has problems, so beware. The SkyHigh kernel and module are v13 compatible as much as v12, just so you know. The reason v12 is packaged in is v12 is the only stable Magisk version at this point.
The bigger issue is Magisk v13 beta working stably and reliably, but if you are willing to debug its failures, it's ok. There should be no need to uninstall to upgrade if you want to play. Reloading the kernel flash will cleanly load up v12 if all goes badly.
Sent from my iPad using Tapatalk
@koop1955 Thank you for that information! I will bookmark those so I can get back to them once v13 is reliable and stable enough for my kernel
@tdhite Thanks bud as Well! I think I will just stay where I am until the kernel and v13 play nicely. Just got this thing as perfect as I can for now, well other than ram use creeping up, but that's only every now and then, and for another topic. I *might* get my nandroid current and play a little if I get bored and want to tinker. I guess I can safely assume then the reason Liveboot stops working with the V4A module installed is because of Magisk v12...?
Thank you to both of you guys for the help and advice. At least now I know it's not some dumb issue with my device lol.
Chuck
@digitalchaos1980 and @tdhite, I have had a good experience with one particular version of Magisk 13, which is why I added it to my AFH. Other and newer versions...not so much. To be expected with a work in progress.
At some point, Magisk 13 will be final and we can move forward.
koop1955 said:
@digitalchaos1980 and @tdhite, I have had a good experience with one particular version of Magisk 13, which is why I added it to my AFH. Other and newer versions...not so much. To be expected with a work in progress.
At some point, Magisk 13 will be final and we can move forward.
Click to expand...
Click to collapse
No doubt! Version 13 gives me something to look forward to for sure
Chuck
digitalchaos1980 said:
Hi y'all, first off I have the G920P, just recently upgraded to Nougat QC7 stock ROM, modified and running the SkyHigh kernel v5.01 with Magisk v12. Everything runs pretty smooth, even got Liveboot working successfully (there's a reason I mention Liveboot.) Now I decided to try to get Viper4Android to work. Of course, installing the standard apk fails when it comes to installing the driver. So I tried the V4A Magisk module and it installed fine, however on reboot, my Liveboot no longer works and when opening the V4A app it asks to install the driver, I hit yes and it says it successfully installed and to please reboot. I reboot and of course Liveboot still doesn't show, but otherwise it boots fine. Once I re-open the V4A app it is asking me to install the driver yet again, and the whole system at times seems a bit unstable until I disable the V4A module in Magisk Manager. Does anyone have any ideas, or has anyone gotten this to successfully work? If so I'd love a suggestion lol. I really would like to keep my Liveboot working, but I'd kinda like to get Viper working too. Thanks in advance for any help, suggestions, ideas, etc.
Chuck
Click to expand...
Click to collapse
if you kindly Tell me the process how did you end up using Live boot in magisk , It would be very helpful . I have tried various method but failed
Saafir said:
Place a copy of audio effects.conf in vendor/etc. Should get you working. Be sure to set permissions as well.
Click to expand...
Click to collapse
Just to be sure, folks realize there is full equalizer support in my SkyHigh kernel and the bands are all adjustable, even per channel if desired, in Synapse, right? Just noting in case that's all you need, because it is a no-CPU-load way of getting it done.
Sent from my iPad using Tapatalk
I have successfully put together a method to get Dolby Digital Plus and Viper4Android running on Redmi Note 8 Pro. Firstly I am rooted on 11.0.6 Global and using LR-TWRP as recovery. On another note I have tried nearly every recovery on this Forum but the only one that doesn't give me a black screen the LR-TWRP.
1. First you need to get the Android running in Permissive mode. For me the Magisk module DID NOT work. To get permissive I found a file on another forum that someone was using on other Redmi devices. It works perfectly with no flaws. Boot into TWRP flash Permissiver_v4_2.zip. And boot back into the device.
***Note.. If you upgrade rom using TWRP as I did from 11.0.2 to 11.0.6. You will have to reflash this file to get everything running properly.
2. Open Magisk and flash ViPER4Android_FX-v2.7.1.0(2710).zip. Reboot device and the open V4A. You should be prompted to install driver. Do so and reboot if prompted to, I don't remember for sure if it makes you or not.
3. Open Magisk and flash 2.1Audio_Modification_Library-v2.4.zip and then reboot.
***NOTE.. Only this version of Audio Modification I have had luck with getting this to run. I updated this file after having everything completely setup and working and it broke V4A and Dolby. Had to uninstall and reinstall this version..
4. Boot into TWRP, NOT Magisk and flash Dolby_Digital_Plus_v.6.5.zip
5. On reboot confirm everything is working. For me it is working flawlessly. Below is a link to the files you will need.
DOWNLOAD
Gonna try this now because the previous tutorial about v4a does work but the moment I plug in my earphones, the status changes to "abnormal"
djgilquirino said:
Gonna try this now because the previous tutorial about v4a does work but the moment I plug in my earphones, the status changes to "abnormal"
Click to expand...
Click to collapse
That is likely due to your phone not being in permissive mode. I've seen that guide as well. I took my past knowledge of getting Viper + Dolby to work and came up with this solution. Being in permissive mode is required for both apps to function
I just found out the reason why my V4A doesn't work when I plug in my headset/earphones. To all those who use poweramp and set your output to "Hi-Res Output", make sure your sample rate is set to 48khz. Setting it to 96khz and up changes the status on V4A to abormal and won't work.
Thanks bro. It is working for me as well you made my day..
rraghava10 said:
Thanks bro. It is working for me as well you made my day..
Click to expand...
Click to collapse
Awesome my dude!! Glad I could help. I'm new to writing guides but love this device and would like to encourage its development as much as I can.
When I flash V4A it functions properly however my SIM card is no longer recognize. When I uninstall V4A my sim is restored. What's up with that?
chugs said:
When I flash V4A it functions properly however my SIM card is no longer recognize. When I uninstall V4A my sim is restored. What's up with that?
Click to expand...
Click to collapse
That is extremely weird. Never heard of anything like that before. Just a couple thoughts but do you have BusyBox installed through Magisk and have your phone set to permissive already?? Also what MIUI version are you running. I have tested this successfully on 11.0.2 and 11.0.6 Global.
I'm still down on 10.4. I haven't been convinced to move to 11
Worked perfectly from EEU (EU) rom moved to 11.0.6 (Global)!
Thank you very much!
alejandromujica.rsm said:
Worked perfectly from EEU (EU) rom moved to 11.0.6 (Global)!
Thank you very much!
Click to expand...
Click to collapse
Your welcome and that's awesome.. Glad I could help bro!
https://ibb.co/YLt7r7s result miui global 11.0.2 err
anasfanani said:
https://ibb.co/YLt7r7s result miui global 11.0.2 err
Click to expand...
Click to collapse
You are not permissive. That is the exact error I got before I found the file I reference to flash to get 'permissive'. To check your status go to terminal and first 'su' to get root. Then type 'getenforce'. Make sure your device is showing permissive. If this is notthe problem I would be surprised. Let me know and I will help you work the problem..
bpawnz said:
You are not permissive. That is the exact error I got before I found the file I reference to flash to get 'permissive'. To check your status go to terminal and first 'su' to get root. Then type 'getenforce'. Make sure your device is showing permissive. If this is notthe problem I would be surprised. Let me know and I will help you work the problem..
Click to expand...
Click to collapse
Thanks. The problem is in selinux magisk module. I uninstalled and install other selinux app from https://github.com/MrBIMC/SELinuxModeChanger and its works
anasfanani said:
Thanks. The problem is in selinux magisk module. I uninstalled and install other selinux app from https://github.com/MrBIMC/SELinuxModeChanger and its works
Click to expand...
Click to collapse
Awesome. The file I reference will change se status from boot. That app I think you have to set it after every reboot if I remember correctly. Regardless I'm glad you got it working. FYI.. Dolby won't show up as an installed app if your not running permissive as well. I know that from trial and error. Glad you got it working!
Steps work. Will confirm if this is any better than standalone V4A
[Update]
Yup. Definitely way better sound quality comparing to the previous methods i used. Also thanks for sharing permissiver.. The previous way i used to change SELinux was a massive pain in my neck. (Global phone on 11.0.2 Global ROM) Looking to see how v4a will fare in upcoming custom ROMs.
Do we have any dual speaker audio sound mod for our note 8 pro global?
+1 to dual speaker mod!
bpawnz said:
Awesome. The file I reference will change se status from boot. That app I think you have to set it after every reboot if I remember correctly. Regardless I'm glad you got it working. FYI.. Dolby won't show up as an installed app if your not running permissive as well. I know that from trial and error. Glad you got it working!
Click to expand...
Click to collapse
Dolby digital is not working after android 10 update... need the version update
Dear all, please note and be aware, this mod will not work on android 10 because
1. dolby digital version is not supported as i stated earlier..
2. when we change SE linux to permissive, phone becomes laggy and many secured application will not work... i have personally tried that may be because of high security of android 10.. i think we will need a custom rom
Has anyone gotten Viper 4 Android to work with the pixel 6 pro yet? If not, are there alternatives? Any guides to doing this would be appreciated! I searched but didn't find much.
Android 12 (Viper4Android)
Has anyone managed to get Viper4Android working on the latest beta of Android 12? The usual methods don't work (makes sense, since its a new OS). Just curious. I like Android 12 so far, but might roll back to 11 if I can't get Viper going...
forum.xda-developers.com
Followed the guide in that thread and got it installed and seems to be working, any recommendations on the profiles for the speakers or the pixel buds a?
FabricatorGeneral said:
Seguí la guía en ese hilo y lo instalé y parece estar funcionando, ¿alguna recomendación sobre los perfiles para los altavoces o los botones de píxeles?
Click to expand...
Click to collapse
norteDon't put much Bass on the speakers because they over time deteriorateBass on the speakers because they over time deteriorate
For those that don't want to change their kernel to permissive due to security reasons, I used this method and is working fine for me. Legacy mode needs to be toggled on.
Viper4Android
Anyone get this working yet?
forum.xda-developers.com
Lughnasadh said:
For those that don't want to change their kernel to permissive due to security reasons, I used this method and is working fine for me. Legacy mode needs to be toggled on.
Viper4Android
Anyone get this working yet?
forum.xda-developers.com
Click to expand...
Click to collapse
i didnt have to change to permissive. the 2nd. file is a Android 12 fix, i believe if you use the fix you do not have to change to permissive....
AndroidAddict420 said:
i didnt have to change to permissive. the 2nd. file is a Android 12 fix, i believe if you use the fix you do not have to change to permissive....
Click to expand...
Click to collapse
I was referring to the method linked in Post #2 where they said they changed their kernel to permissive. The Android 12 fix file is from another thread which you started and posted the file it. You might want to add a link to your post so people know what "fix" file you are talking about since it's not in this thread, lest people might get confused about what you are talking about.
Or maybe I'll just link it here...
Interested in a Working Formula to get Viper4Android Working? (ROOT)
Viper4Android for Google Pixel 6/6 Pro and most other devices on Android 12... It the time of testing this Method, it worked in November 2021 and December 2021 builds for my Google Pixel 6.... 1) Make sure your BL is unlocked and you are...
forum.xda-developers.com
I installed by using the method I had to do for OP8T. Install Audio_Modification_Library Magisk Module (DO NOT REBOOT) -> Install Viper Magisk Module (DO NOT REBOOT) -> Open Viper App (this forces a reboot) -> Remove Audio_Modification_Library. It works great for me in apps like AIMP, but in apps like YouTubeVanced have never worked for me.
card13 said:
I installed by using the method I had to do for OP8T. Install Audio_Modification_Library Magisk Module (DO NOT REBOOT) -> Install Viper Magisk Module (DO NOT REBOOT) -> Open Viper App (this forces a reboot) -> Remove Audio_Modification_Library. It works great for me in apps like AIMP, but in apps like YouTubeVanced have never worked for me.
Click to expand...
Click to collapse
Strange it doesn't process with YouTubeVanced for you. It should. Have you tried giving this mod a shot?
EDIT: Actually I think the version located at John Fawkes site is newer than the XDA one, so adding that link.
Audio Compatibility Patch (Formerly Universal deep_buffer Remover) [MMTEx]
This fixes music and streaming apps (Spotify, Pandora, etc) that aren't processing audio effects for various equalizer applications through the modification of audio policy. Starting with v1.6 USB_policy patcher (upp) and Notification_helper...
forum.xda-developers.com
John Fawkes Playground
@Lughnasadh I'm not currently using the Compatibility Patch. It's mainly because last time I did on the OnePlus phones, my Bluetooth audio would get fubar'd and require a Factory Reset to fix.
Thanks to the community, the Viper4android works for me on Pixe6 PRO, BUT I am unable to activate any VIPER-DDC , Headset correction profiles loading takes no effect, tried a few I see them active but no change in sound. Previously my OnePlus 8Pro worked fine with the same version (Android 12). Does anyone experience similar issue ? Can you please try and let me know.
ansher said:
Thanks to the community, the Viper4android works for me on Pixe6 PRO, BUT I am unable to activate any VIPER-DDC , Headset correction profiles loading takes no effect, tried a few I see them active but no change in sound. Previously my OnePlus 8Pro worked fine with the same version (Android 12). Does anyone experience similar issue ? Can you please try and let me know.
Click to expand...
Click to collapse
I don't have answer for your question, perhaps go to their Telegram group to ask for help as you may have more chance there.
I do have something for your consideration. I used V4A for longer than I can remember but it must be over 10 years. However, seems the developer has already quitted the project for quite sometime, the driver has never been updated in the past 7-8 years, we are lucky that it is still working with A12. But everything has an end, I tried it on A13 Beta and it doesn't work with it. If you search the web, you properly going to find that so far no one is able to make it work with A13. The A13 is already in beta 4 and official release could be sometime in next month, unless you are going to give up to update to A13, you better start to find something to replace V4A, my choice is JamesDSP but you may find something better suit your needs.
I prefer presets because I don't know what I'm doing. I ended up moving to PowerAmp and am usually pleased with the sound. If only the developer would enable roor features, man that would be cool.
Thanks acwcanada for the suggestion. I looked at the thread and so far may stick with Android 12 (those crazy audiophiles ) because I could not find 2 key features available in Viper4Android.
1. Headphone frequency response correction (VIPER-DDC or AutoEQ in Wavelet). This feature does not even work for me in Pixel 6 pro A12L , workaround: install wavelet and use its AutoEQ feature.
2. Dynamic System feature of Viper4Android creates bass subharmonics using reference frequencies and algorithm (selectable by choosing headphone type), so it can inject them in the music making it feel much richer and restores lack of low frequencies without "booming" effect created by other bass boosters. So far nothing in this word can beat this Viper4Andoid's feature.
Some good news folks: Viper4Android and Wavelet can be stacked and work in tandem .
Perhaps going to write James to consider the above, unless I missed it.
Cheers and thanks Team !