Related
Hey guys, I have a rooted US998 with magisk running on oreo. I was able to successfully install the latest viper4android, version 2.5.0.4, and driver installation went well. I rebooted, and when I check driver status, it says "enabled: yes status: normal". So you would think everything would be working fine. However, when I enable V4A, I hear no difference in the sound. I have an eq and several other changes, so I should definitely hear a difference in SQ when I enable V4A. I have tried both in neutron and poweramp. In poweramp, I turned off DVC (direct volume control), as the app suggest.
Any suggestions? To me, it seems that something on the phone is "overriding" the V4A output settings.
Thanks!
i can also confirm that turning the quad dac on or off makes no difference. Viper still doesn't do anything.
[/ATTACH]Working fine here
I've installed it with magisk
It's version 2.5.05
ricohz said:
Working fine here
I've installed it with magisk
Click to expand...
Click to collapse
you are using an earlier version than I am. I am going to uninstall the version I have now, and try to install through magisk modules the version you have and see if it works.
The version I installed was an apk downloaded from the official xda app thread.
son of a gun, that did it! I just installed the earlier version of v4a in the official thread and flashed the zip in twrp, rebooted, and all was good. Upon closer look, it seems that version that I used that was an apk install is actually an unofficial version of the app (despite being fully recognized as a magisk module). Too bad, I liked the UI much better . But glad to see it's now working. So anyone having issues w/ v4a, install the zip via recovery using the official app, not the unofficial apk.
Hisma said:
son of a gun, that did it! I just installed the earlier version of v4a in the official thread and flashed the zip in twrp, rebooted, and all was good. Upon closer look, it seems that version that I used that was an apk install is actually an unofficial version of the app (despite being fully recognized as a magisk module). Too bad, I liked the UI much better . But glad to see it's now working. So anyone having issues w/ v4a, install the zip via recovery using the official app, not the unofficial apk.
Click to expand...
Click to collapse
You can edit your thread topic to say SOLVED.
Sent via open market LG US998 V30/V30+
Hisma said:
son of a gun, that did it! I just installed the earlier version of v4a in the official thread and flashed the zip in twrp, rebooted, and all was good. Upon closer look, it seems that version that I used that was an apk install is actually an unofficial version of the app (despite being fully recognized as a magisk module). Too bad, I liked the UI much better . But glad to see it's now working. So anyone having issues w/ v4a, install the zip via recovery using the official app, not the unofficial apk.
Click to expand...
Click to collapse
If you like the material design that much, you can get the material look back. Reflash that same Viper4Android. Just pay close attention to the installation log in Magisk Manager and press Up on the Volume when it says "Test mode". Then you can select the "Material" design instead of Original before selecting which sound driver version you'd like.
I would like to know what you are saying about the sound with DAC in connection with Viper4Android. Is there now Rome, where you can turn on the DAC, but not the default settings of LG has? because I found that faked the sound with Viper. Would be glad about feedbacks. I'd love to use only viper, but with the built in DAC together it sounds better again. but just without the stupid sound profiles of LG.
Hisma said:
son of a gun, that did it! I just installed the earlier version of v4a in the official thread and flashed the zip in twrp, rebooted, and all was good. Upon closer look, it seems that version that I used that was an apk install is actually an unofficial version of the app (despite being fully recognized as a magisk module). Too bad, I liked the UI much better . But glad to see it's now working. So anyone having issues w/ v4a, install the zip via recovery using the official app, not the unofficial apk.
Click to expand...
Click to collapse
So are you saying you chose the older version in the magisk module?
Nothing I do seems to work.
Sent from my LG-H932 using XDA Labs
Install the fallowing Magisk Modules ViPER4Android FX, Audio Compatibility Patch, Audio Modification Library and Selinux Permissive reboot and you should be good to go.
So one of the reason why I rooted my phone 2 days ago was because of font style and Dolby Atmos. I waited so long and it's still not coming. I decided to root. I unlocked bootloader, installed TWRP, installed MAGISK, basically everything you need to do to install Pixel Experience. I went to an article about how to install Dolby Atmos on rooted device. I downloaded the zip and flashed it using TWRP. The app was there, but when I opened it, it just crashed. I ended up recovering my device to a state right before I installed that Dolby. Any clue?
Hi If I'm not mistaken, Dolby in Pocophone only works on Oreo systems ... I installed Dolby in all my root phones, but it was impossible in Pocophone, I guess due to lack of development, So I gave up on installing it.
You can download flash zip her https://forum.xda-developers.com/android/software/mm-p-dolby-digital-plus-arise-20181115-t3868192
For work you need set se Linux to permissive.
If you let se Linux to enforcing, the app is force closing many times and unstable for usage
AndreSkywalker said:
You can download flash zip her https://forum.xda-developers.com/android/software/mm-p-dolby-digital-plus-arise-20181115-t3868192
For work you need set se Linux to permissive.
If you let se Linux to enforcing, the app is force closing many times and unstable for usage
Click to expand...
Click to collapse
Uh, what is se Linux? Sorry, I am completely new to rooting. Just literally rooted my phone about 2 days ago...
I just checked the article you posted. Apparently there are many people complaining about it being not working. Guess I'll wait until someone actually manage to make a compatible one. Also that one was Dolby Digital though, not Dolby Atmos..
nazagato said:
Hi If I'm not mistaken, Dolby in Pocophone only works on Oreo systems ... I installed Dolby in all my root phones, but it was impossible in Pocophone, I guess due to lack of development, So I gave up on installing it.
Click to expand...
Click to collapse
So a more modern android version won't work? That's a huge bummer to be honest.
Maybe try to get Dirac like in HavocOS cause it seems realy good
Triparadox said:
Uh, what is se Linux? Sorry, I am completely new to rooting. Just literally rooted my phone about 2 days ago...
I just checked the article you posted. Apparently there are many people complaining about it being not working. Guess I'll wait until someone actually manage to make a compatible one. Also that one was Dolby Digital though, not Dolby Atmos..
Click to expand...
Click to collapse
Se Linux is a configuration in kernel. I have many audio mods in pocophone (like a dolby atmos, viper4android and ainur sauron). For make this mods work, you need a custom kernel with support for se Linux permissive.
After installing a custom kernel (Franco Kernel for example) you can mark Se Linux permissive in several ways. I use a simple application that set up Se Linux to permissive on boot of the phone. The application name is if "The SeLinux switch" . That done dolby atmos will work without problems.
AndreSkywalker said:
Se Linux is a configuration in kernel. I have many audio mods in pocophone (like a dolby atmos, viper4android and ainur sauron). For make this mods work, you need a custom kernel with support for se Linux permissive.
After installing a custom kernel (Franco Kernel for example) you can mark Se Linux permissive in several ways. I use a simple application that set up Se Linux to permissive on boot of the phone. The application name is if "The SeLinux switch" . That done dolby atmos will work without problems.
Click to expand...
Click to collapse
Wait wait.. I'm lost.. You mentioned a bit about custom kernel. What is that? All I have done is unlock bootloader, install twrp, install magisk, install custom rom pixel experience. What is kernel? What is custom kernel? What's the function of it? How do we change it? What should I do? Do I just flash several zip or apks to make it work? If possible, please explain in non technical terms.. Some articles I found are just too complicated or use too many technical terms that I don't know..
Triparadox said:
Wait wait.. I'm lost.. You mentioned a bit about custom kernel. What is that? All I have done is unlock bootloader, install twrp, install magisk, install custom rom pixel experience. What is kernel? What is custom kernel? What's the function of it? How do we change it? What should I do? Do I just flash several zip or apks to make it work? If possible, please explain in non technical terms.. Some articles I found are just too complicated or use too many technical terms that I don't know..
Click to expand...
Click to collapse
It may seem complicated to those unfamiliar with roms mods, but over time you will get used to it. Basically to customize a cellphone there are three steps.
1) unlock bootloader and install custom recovery (TWRP)
2) Install a custom rom and root (magisk)
3) Install a custom kernel
You stopped at step 2, you do not need to do step 3, but if you want to further customize you should install a custom kernel (modify sound quality, CPU usage, GPU, battery). The kernel is the basic configuration between the hardware (physical part of the phone) and the software (android).
Anyway to install a kernel is very easy, just flash the kernel zip, just as you did the rom. download this kernel for example https://forum.xda-developers.com/poco-f1/development/kernel-canting-0-1-t3907883.
After flashing the kernel just install the application I passed previously, open the application and choose the option if linux to permissive, after that dolby atmos will work without problems
Triparadox said:
So one of the reason why I rooted my phone 2 days ago was because of font style and Dolby Atmos. I waited so long and it's still not coming. I decided to root. I unlocked bootloader, installed TWRP, installed MAGISK, basically everything you need to do to install Pixel Experience. I went to an article about how to install Dolby Atmos on rooted device. I downloaded the zip and flashed it using TWRP. The app was there, but when I opened it, it just crashed. I ended up recovering my device to a state right before I installed that Dolby. Any clue?
Click to expand...
Click to collapse
Happened same to me yesterday.I tried dolby and it crashed.So now I'm using Viper4Android, it works great.I can send you settings for headset:
Headset
Master Power: ON
PlaybackAGC: ON
Effect Strength: Moderate
Firequalizer: ON
Preset: R&B
Headphone Surround: ON
Effect Level: 2
Viper Bass: ON
Bass Boost: 3.5dB
Viper Clarity: ON
Clarity: 3.5dB
Cure Tech+: ON
Binaural Level: Extreme
Cheers
AndreSkywalker said:
It may seem complicated to those unfamiliar with roms mods, but over time you will get used to it. Basically to customize a cellphone there are three steps.
1) unlock bootloader and install custom recovery (TWRP)
2) Install a custom rom and root (magisk)
3) Install a custom kernel
You stopped at step 2, you do not need to do step 3, but if you want to further customize you should install a custom kernel (modify sound quality, CPU usage, GPU, battery). The kernel is the basic configuration between the hardware (physical part of the phone) and the software (android).
Anyway to install a kernel is very easy, just flash the kernel zip, just as you did the rom. download this kernel for example https://forum.xda-developers.com/poco-f1/development/kernel-canting-0-1-t3907883.
After flashing the kernel just install the application I passed previously, open the application and choose the option if linux to permissive, after that dolby atmos will work without problems
Click to expand...
Click to collapse
Ah ok. Thanks. At least I know where I am at and what step is doing the kernel is. So all I have to do is to download the custom kernel and flash it to the system using TWRP, then I flash the dolby atmos like I did previously but it should not work because I have custom kernel. One quick question, after/before flashing the custom kernel, is there anything I need to wipe? I believe I remember I wiped the cache and DAVIX previously otherwise it wouldn't work.
Triparadox said:
Ah ok. Thanks. At least I know where I am at and what step is doing the kernel is. So all I have to do is to download the custom kernel and flash it to the system using TWRP, then I flash the dolby atmos like I did previously but it should not work because I have custom kernel. One quick question, after/before flashing the custom kernel, is there anything I need to wipe? I believe I remember I wiped the cache and DAVIX previously otherwise it wouldn't work.
Click to expand...
Click to collapse
No wipes. Just flash kernel via TWRP. After this flash dolby atmos and reboot. Open app and set se Linux to permissive Mode. Dolby atmos work it
AndreSkywalker said:
No wipes. Just flash kernel via TWRP. After this flash dolby atmos and reboot. Open app and set se Linux to permissive Mode. Dolby atmos work it
Click to expand...
Click to collapse
I just did what you told me. I flashed the kernel via TWRP and then flashed the Dolby zip. Then I reboot to the system. Next I installed the apk for SELinux. Opened that app and granted it superuser for 10 mins to change from enforcing to permissive. Opening Dolby seems to still be forced closing.
Triparadox said:
I just did what you told me. I flashed the kernel via TWRP and then flashed the Dolby zip. Then I reboot to the system. Next I installed the apk for SELinux. Opened that app and granted it superuser for 10 mins to change from enforcing to permissive. Opening Dolby seems to still be forced closing.
Click to expand...
Click to collapse
Are you using version 6.5 of Dolby Atmos? Check the list of modules installed on your magisk. I will take a screenshot of my pocophone.
AndreSkywalker said:
Are you using version 6.5 of Dolby Atmos? Check the list of modules installed on your magisk. I will take a screenshot of my pocophone.
Click to expand...
Click to collapse
i don't see any module.
Triparadox said:
i don't see any module.
Click to expand...
Click to collapse
Where did you download dolby atmos? Download the latest version from this link below, only this version works on Android pie. After downloading it, tweet the Dolby Atmos 6.5 flash you downloaded. After rebooting dolby should appear in the magisk module list
https://forum.xda-developers.com/android/software/mm-p-dolby-digital-plus-arise-20181115-t3868192
AndreSkywalker said:
Where did you download dolby atmos? Download the latest version from this link below, only this version works on Android pie. After downloading it, tweet the Dolby Atmos 6.5 flash you downloaded. After rebooting dolby should appear in the magisk module list
https://forum.xda-developers.com/android/software/mm-p-dolby-digital-plus-arise-20181115-t3868192
Click to expand...
Click to collapse
Yeah, thanks for that. I downloaded the top one because I thought that was the newest version. It works fine now. Also is it also happening to you that you can't really change the setting for custom and the movie profile and music profiled doesn't seem to have any difference? Game one does make it louder tho.
Triparadox said:
Yeah, thanks for that. I downloaded the top one because I thought that was the newest version. It works fine now. Also is it also happening to you that you can't really change the setting for custom and the movie profile and music profiled doesn't seem to have any difference? Game one does make it louder tho.
Click to expand...
Click to collapse
I use dolby atmos with viper4android. Dolby atmos is effective with the headset, without the headset it doesn't work very loudly, while viper4android works both ways.
Anyone got V4A working on mojito? i tried installing and using compatibility mode but it wont hook onto the audio. i used JamesDSP and it works fine. But I'm more used to V4A.
It's been done before. I tried it and it worked. Necessary installation sequence with reboots. I only have a link to the image.
inn000 said:
Anyone got V4A working on mojito? i tried installing and using compatibility mode but it wont hook onto the audio. i used JamesDSP and it works fine. But I'm more used to V4A.
Click to expand...
Click to collapse
i got it working on my mojito , im using global eea rom instead of global . you need to add something , here is the guide guide on viper4android
Hey,
Yesterday I've rooted my phone with this method: https://forum.xda-developers.com/t/tutorial-twrp-and-root-nord-2.4340477/
Worked as it should, thanks.
Now I try to install viper4android on the device (main reason I've rooted it ), but I can't get it work.
Everytime I install it, then install the driver and reboot, it detects no driver, so again install driver etc...
I've tried audi modification library, v4a fx legacy, flashed the drivers in TWRP, and so many things. The weird thing is that, magisk can't install the apk, I have to do it manually. Even tried to set SELinux permissive, but I couldn't change it.
Anyone can help me? Tinkering phone was easier back in the day
Thanks!
szmoki42 said:
Hey,
Yesterday I've rooted my phone with this method: https://forum.xda-developers.com/t/tutorial-twrp-and-root-nord-2.4340477/
Worked as it should, thanks.
Now I try to install viper4android on the device (main reason I've rooted it ), but I can't get it work.
Everytime I install it, then install the driver and reboot, it detects no driver, so again install driver etc...
I've tried audi modification library, v4a fx legacy, flashed the drivers in TWRP, and so many things. The weird thing is that, magisk can't install the apk, I have to do it manually. Even tried to set SELinux permissive, but I couldn't change it.
Anyone can help me? Tinkering phone was easier back in the day
Thanks!
Click to expand...
Click to collapse
Hi,
Unfortunately, it doesn't work for me either and there is currently no solution to the problem
Man that just s#cks.
If anyone knows something, please don't hold it
Hi guys I am trying to load v4a2.7.2.1 with magisk version 23, on android 7.0 on An lg v530 gpad x2 8.0 plus. I have checked and I have root. I also have busybox installed via magisk and I installed selinux switch and used it to switch to permissive mode. V4a just keeps trying to install the driver and reboot every time I load it up. Can anyone guide me as to how to make v4a work? I've spent days on xda trying to find a way to make this work. Way to confusing with all the old versions of v4a like 2.5.*.* and using it with newer Android versions with and without magisk. So far nothing I've found works obviously or I wouldnt be posting. Any help would be appreciated.
polygaryd said:
Hi guys I am trying to load v4a2.7.2.1 with magisk version 23, on android 7.0 on An lg v530 glad x2 8.0 plus. I have checked and I have root. I also have busybox installed via magisk and I installed selinux switch and used it to switch to permissive mode. V4a just keeps trying to install the driver and reboot every time I load it up. Can anyone guide me as to how to make v4a work? I've spent days on xda trying to find a way to make this work. Way to confusing with all the old versions of v4a like 2.5.*.* and using it with newer Android versions with and without magisk. So far nothing I've found works obviously or I wouldnt be posting. Any help would be appreciated.
Click to expand...
Click to collapse
Oh and there is no twrp version for this device for me to try to install the rootless driver which I did download to try to install manually.
Anyone with knowledge about this out there that can help?
I too have the same issue so can we put our heads together and fix it? Im using mtk 6753t octa core agptek t06s mp4 player I patched my recovery.img with universal mtk twrp patcher but no dice booting to recovery. By the way I'm rooted and tried everything.
I'm reading this... https://www.apkmirror.com/apk/team-dewitt/viper4android-fx/viper4android-fx-2-7-2-1-release/