Related
I have been using V4A for some time on my Android devices... Now finally when the Z3C could be rooted without loosing the DRM keys I went for it... Everything works just fine after the root, but I am totally unavailable to get V4A to work for some reason. Anyone that have this working with a rooted Z3C and locked boot loader? If you have, how did you manage to do it?
reguser said:
I have been using V4A for some time on my Android devices... Now finally when the Z3C could be rooted without loosing the DRM keys I went for it... Everything works just fine after the root, but I am totally unavailable to get V4A to work for some reason. Anyone that have this working with a rooted Z3C and locked boot loader? If you have, how did you manage to do it?
Click to expand...
Click to collapse
On my Xperia Z it worked just fine with a locked BL, I don't see why it would require an unlocked BL. My BL on the Z3C is unlocked so I can't say anything about that.
What problems are you having?
Sent from my D5803
Thanks for your answer Dsteppa... Well, I have this rooted Z3C and downloaded the latest V4A together with BusyBox. The driver and BusyBox installs just fine and I'm able to change V4A under sound settings... But I can't get the V4A to work. Whatever changes I make to it there's no change in sound. E.g. on my S3 everything was working just fine.
reguser said:
Thanks for your answer Dsteppa... Well, I have this rooted Z3C and downloaded the latest V4A together with BusyBox. The driver and BusyBox installs just fine and I'm able to change V4A under sound settings... But I can't get the V4A to work. Whatever changes I make to it there's no change in sound. E.g. on my S3 everything was working just fine.
Click to expand...
Click to collapse
im on locked BL too and rootted and it works great , hop you have installed the drivers
pw1nce said:
im on locked BL too and rootted and it works great , hop you have installed the drivers
Click to expand...
Click to collapse
OK... I must be missing some fundamental configuration then... Did you only install BusyBox and then the V4A driver for it to work?
What ap are you using to listen to music? Don't forget to change V4A to your default MusicFX (Settings > Sound)
Dsteppa said:
What ap are you using to listen to music? Don't forget to change V4A to your default MusicFX (Settings > Sound)
Click to expand...
Click to collapse
Hi... I have changed settings and using BubbleUPnP. Also tried the Walkman app but no difference in sound
reguser said:
Hi... I have changed settings and using BubbleUPnP. Also tried the Walkman app but no difference in sound
Click to expand...
Click to collapse
Can you confirm that @ Settings > Sound > Music Effects V4A is default?
And did you enable V4A @ Headset/Phone Speaker/Bluetooth etc..
I have V4A installed, can confirm it works with bubbleUPNP and power amp. When you download the zip and extract it, make sure you install the largest file, then open and install the drivers. Then follow what Dsteppa said... It should work
Cheers ?
Dsteppa said:
Can you confirm that @ Settings > Sound > Music Effects V4A is default?
And did you enable V4A @ Headset/Phone Speaker/Bluetooth etc..
Click to expand...
Click to collapse
Hi and thanks once again for your concern... Yes, I have tried both the V4A FX and XHIFI and enabled them in Sound/M Effects and also enabled V4A for e.g. Headset. I've installed and used V4A on nearly 10 Android devices prior to this one without any issues at all. The strange thing is that I can see that the driver is active but not producing any change in sound... I also tried to reset the phone, also did the root process once more but the same result... Really strange as I see it.
reguser said:
Hi and thanks once again for your concern... Yes, I have tried both the V4A FX and XHIFI and enabled them in Sound/M Effects and also enabled V4A for e.g. Headset. I've installed and used V4A on nearly 10 Android devices prior to this one without any issues at all. The strange thing is that I can see that the driver is active but not producing any change in sound... I also tried to reset the phone, also did the root process once more but the same result... Really strange as I see it.
Click to expand...
Click to collapse
Hmm then the only thing I can think of is you asking in the V4A topic, they should be able to help you there. Because it should work without a problem.
I have the exact same problem, viper4android installed on my D5803, rooted with locked BL, but not working. After spending some time trying to figure it out i found out that it doesn't work with the Walkman app, with google play music it's working fine. Hope that helps. I'm curious if you guys got it working with the walkman app?
mykep said:
I have the exact same problem, viper4android installed on my D5803, rooted with locked BL, but not working. After spending some time trying to figure it out i found out that it doesn't work with the Walkman app, with google play music it's working fine. Hope that helps. I'm curious if you guys got it working with the walkman app?
Click to expand...
Click to collapse
Mine worked fine with Walkman, but I prefer PowerAmp (So I use that)
Thank you for your answer, after more digging around i found out that it's working with Walkman app too, but only on the phone speakers, it does not work with the headset. If you go to driver status (on headset) it says processing no, and it does nothing, you can't feel any difference, i have to mention that i use a pair of Sennheiser momentum in ear, and have not tested with anything else. On the phone speakers it says, processing yes, and it's working...
I bought the XPERIA Z3C for its native support of High Resolution Audio (HRA). This is the problem why it's not working for me... I found out that when playing a 24 bit FLAC file the V4A driver just won't process?! It worked fine on my Galaxy S3 (i9300) but not on this. 16 bits FLAC files play just fine, but when I play HRA files the sound processing just wont happen. I don't know if it's related to that it's a separeta DAC (Wolfson 1811) in the S3 and the Z3C uses the Qualcomm 801 with embedded DAC.
I'm having problems too.
Rooted my z3c especially for this and it's not working.
I've installed the drivers and then the app asks me to reboot, after the reboot I've entered the app and again, it asks me to install drivers like I never did.
Any idea on how to fix this?
Put V4A in compability mode and it will work probably
Roye_V said:
I'm having problems too.
Rooted my z3c especially for this and it's not working.
I've installed the drivers and then the app asks me to reboot, after the reboot I've entered the app and again, it asks me to install drivers like I never did.
Any idea on how to fix this?
Click to expand...
Click to collapse
it's because of your busybox, it's either not installed or not properly installed, had the same issue.
Hi can yous confirm if this increases ringtone volume?
It's because of your duel recovery and rooting method, if you install busy box it might most likely erase your recovery on xperia z3. It happened to me actually but Viper android fx will work, if you prefer Viper android fx and no recovery go 4 it and install busy box from Google play you do a backup then reinstall your recovery via computer then restore your data from the backup
If you have duel recovery on xperia z3 or z3c it most likely has a different busy box compatible with that recovery
---------- Post added at 04:46 PM ---------- Previous post was at 04:29 PM ----------
T_money_third said:
It's because of your duel recovery and rooting method, if you install busy box it might most likely erase your recovery on xperia z3. It happened to me actually but Viper android fx will work, if you prefer Viper android fx and no recovery go 4 it and install busy box from Google play you do a backup then reinstall your recovery via computer then restore your data from the backup
If you have duel recovery on xperia z3 or z3c it most likely has a different busy box compatible with that recovery
Click to expand...
Click to collapse
I solved Viper android fx not working with duel recovery on xperia z3 XD all I did was set selinux mode to permissive and it didn't ask me to install drivers again and again it works now
Is your WiFi Calling staying connected after updating to 10n? Mine was working fine on 10h, but on 10n it disconnects after 5-10 minutes with a REG99: Unable to connect error and won't reconnect until I reboot the phone.
I did all the troubleshooting steps with T-Force: factory reset, got a new SIM card, got an update sent to the SIM card twice, factory reset again, and no dice.
Is anyone else experiencing this on 10n? I'm on stock rooted 10n (odex).
EDIT: It's XPosed. As long as the XPosed Framework is installed (even with no modules), WiFi Calling is completely broken.
I was getting the same error on 10N. I called and was transferred to Tech Support. They updated my E-911 info and was back up in running in less than 5 minutes
siraltus said:
Is your WiFi Calling staying connected after updating to 10n? Mine was working fine on 10h, but on 10n it disconnects after 5-10 minutes with a REG99: Unable to connect error and won't reconnect until I reboot the phone.
I did all the troubleshooting steps with T-Force: factory reset, got a new SIM card, got an update sent to the SIM card twice, factory reset again, and no dice.
Is anyone else experiencing this on 10n?
Click to expand...
Click to collapse
Are you using xposed? I am experiencing same while xposed is installed and it works perfect without...
jamesd1085 said:
Are you using xposed? I am experiencing same while xposed is installed and it works perfect without...
Click to expand...
Click to collapse
I'm using xposed and it works great (wi-fi calling).
gerald410 said:
I'm using xposed and it works great (wi-fi calling).
Click to expand...
Click to collapse
Not the case for me and others are trickling in with the same issue
So I rooted my phone a little more than a week ago and then flashed MicroMod777's rooted stock 10n ROM a few days later. Up until this point, WiFi calling was working. I then flashed the Xposed framework v72, downloaded some modules, and installed them. I realized that WiFi calling was no longer available and would give me the classic REG99 error, unable to connect. Another user on MicroMod777's 10n stock ROM thread (http://forum.xda-developers.com/tmo...m-g4-h811-10n-stock-rooted-rom-t3188858/page9) had the same problem, though another user responded that Wifi calling was working fine with the 10 ROM and Xposed v72.
I uninstalled Xposed and I could immediately access WiFi calling, so it seems that Xposed is conflicting with the 10n stock ROM's WiFi calling. Same results with v73. Users who are getting WiFi calling to work on Xposed, did you get the official 10n update OTA or flash a rooted ROM? And what version of Xposed are you running?
Synchronicities said:
So I rooted my phone a little more than a week ago and then flashed MicroMod777's rooted stock 10n ROM a few days later. Up until this point, WiFi calling was working. I then flashed the Xposed framework v72, downloaded some modules, and installed them. I realized that WiFi calling was no longer available and would give me the classic REG99 error, unable to connect. Another user on MicroMod777's 10n stock ROM thread (http://forum.xda-developers.com/tmo...m-g4-h811-10n-stock-rooted-rom-t3188858/page9) had the same problem, though another user responded that Wifi calling was working fine with the 10 ROM and Xposed v72.
I uninstalled Xposed and I could immediately access WiFi calling, so it seems that Xposed is conflicting with the 10n stock ROM's WiFi calling. Same results with v73. Users who are getting WiFi calling to work on Xposed, did you get the official 10n update OTA or flash a rooted ROM? And what version of Xposed are you running?
Click to expand...
Click to collapse
Stocked rooted rom and v72 I believe (how to confirm?).
gerald410 said:
Stocked rooted rom and v72 I believe (how to confirm?).
Click to expand...
Click to collapse
Open the XPosed Installer app and look in the Framework section.
jamesd1085 said:
Are you using xposed? I am experiencing same while xposed is installed and it works perfect without...
Click to expand...
Click to collapse
I was having the issue on a totally stock, factory-reset phone with nothing installed.
T-Force opened a ticket with network engineering, supposed to be resolved by tomorrow.
siraltus said:
Not XPosed's fault at all. I was having the issue on a totally stock, factory-reset phone with nothing installed.
Click to expand...
Click to collapse
Just asking as i have same issue but only with xposed...as are some others
jamesd1085 said:
Just asking as i have same issue but only with xposed...as are some others
Click to expand...
Click to collapse
Interesting.... I wonder why. I have Xposed installed on my Note 4 also and WiFi Calling works perfectly fine there. Might be a specific module causing it.
Come to think of it, when I factory-reset the phone, Xposed was still installed into the system partition, since it's not an app, but a modification to system files.
I will have to re-test after explicitly uninstalling Xposed. It would be a total bummer if Xposed is the problem. And if it is, I hope it's just a specific module that I can disable. I'd hate to lose YouTube AdAway and a few others.
siraltus said:
Interesting.... I wonder why. I have Xposed installed on my Note 4 also and WiFi Calling works perfectly fine there. Might be a specific module causing it.
Come to think of it, when I factory-reset the phone, Xposed was still installed into the system partition, since it's not an app, but a modification to system files.
I will have to re-test after explicitly uninstalling Xposed. It would be a total bummer if Xposed is the problem. And if it is, I hope it's just a specific module that I can disable. I'd hate to lose YouTube AdAway and a few others.
Click to expand...
Click to collapse
Mine is broken without even adding modules...fixes instantly after flashing xposed uninstaller
jamesd1085 said:
Mine is broken without even adding modules...fixes instantly after flashing xposed uninstaller
Click to expand...
Click to collapse
Well that just sucks. I just uninstalled Xposed and WiFi Calling is staying connected now. This is not good.
siraltus said:
Well that just sucks. I just uninstalled Xposed and WiFi Calling is staying connected now. This is not good.
Click to expand...
Click to collapse
Looks like we need to try and get some logs for rovo and hopefully he can easily fix it...
Scrap that! Download SELinux mode changer and change to permissive...instantly popped up and stayed connected! Great news
jamesd1085 said:
Looks like we need to try and get some logs for rovo and hopefully he can easily fix it...
Scrap that! Download SELinux mode changer and change to permissive...instantly popped up and stayed connected! Great news
Click to expand...
Click to collapse
O RLY... is that an Xposed module?
siraltus said:
O RLY... is that an Xposed module?
Click to expand...
Click to collapse
Try ticking disable resource hooks in exposed installer app...and You can google SELinux mode changer its an app it coonects after boot...takes longer than it used to but its working on my end
siraltus said:
Open the XPosed Installer app and look in the Framework section.
Click to expand...
Click to collapse
I'm running v71 thx.
jamesd1085 said:
Try ticking disable resource hooks in exposed installer app...and You can google SELinux mode changer its an app it coonects after boot...takes longer than it used to but its working on my end
Click to expand...
Click to collapse
Nope, neither works. WiFi Calling is still busted while Xposed is installed.
siraltus said:
Nope, neither works. WiFi Calling is still busted while Xposed is installed.
Click to expand...
Click to collapse
Try unticking disable hooks...it's working fine without that...try a couple reboots...mine has settled in and works fine...also did you opeen the app and grant root and press permissive?
jamesd1085 said:
Try unticking disable hooks...it's working fine without that...try a couple reboots...mine has settled in and works fine...also did you opeen the app and grant root and press permissive?
Click to expand...
Click to collapse
Of course I granted root and pressed Permissive, I know what SELinux is. I also unticked that checkbox and rebooted like 5 times. It either never connects or connects and disconnects after 2-3 minutes.
Hi guys,
So I have the latest version of Android Messages but i still have the old design. I've been trying to uninstall and reinstall it but still not working. I've also tried to reboot my phone and everything but it still stuck on old design.
If anyone can help me I really appreciate it.
Thanks.
It's probably a server side push. I tried the version that first had dark mode but then Google pulled it
Can you tell which version you got?
I had the update, dark mode completely flips and app doesn't open. Switched off the dark mode and all fine. (On pixel experience treble ROM)
Ayfred said:
Hi guys,
So I have the latest version of Android Messages but i still have the old design. I've been trying to uninstall and reinstall it but still not working. I've also tried to reboot my phone and everything but it still stuck on old design.
If anyone can help me I really appreciate it.
Thanks.
Click to expand...
Click to collapse
Works fine for me. No crashing.
Currently on 152
dladz said:
Works fine for me. No crashing.
Currently on 152
Click to expand...
Click to collapse
You're clearly using emui. Probably caused by the treble ROM, although I've read reviews on Google play saying the same (most likely unrooted phones)
dladz said:
Works fine for me. No crashing.
Currently on 152
Click to expand...
Click to collapse
I am on same version of Android Messages and CLT-L29 8.1.0.152 (C636) with no issues. except not able to set custom notification sms sounds for each person like I could before.
Pretty sure after I installed the updated version I force stopped the app then reopened and its been running fine
nibs777 said:
Pretty sure after I installed the updated version I force stopped the app then reopened and its been running fine
Click to expand...
Click to collapse
I've tried this but nope still old design.
josdehaes said:
You're clearly using emui. Probably caused by the treble ROM, although I've read reviews on Google play saying the same (most likely unrooted phones)
Click to expand...
Click to collapse
Why wouldn't I be using emui? There is no mention of what ROM is in use in this thread??
Also I am rooted.
Magisk 16.4
PS: There is a tweak that can be done but this was reverted back afterwards, can't remember it exactly but just Google it.
After the most recent update the dark settings were listed and I've had no issues
you need to enable dark mode, force close the app, clear cache.
then it should work.
mrengineer said:
you need to enable dark mode, force close the app, clear cache.
then it should work.
Click to expand...
Click to collapse
Everytime i did that it still shows me the old design
I haven't had any issues using Magisk until today.
I upgraded from Android 7.0 to 8.1 (I wanted to be able to use Swift Installer), now that it's been released for my device.
After flashing Magisk, the phone isn't detecting my SIM, and there's a constant error message that pops up, but it's so fast that I never have the chance to see what it actually says.
Is there a fix for this?
Samsung Galaxy J3 (SM-J327U).
17.3 was working perfectly fine on the phone running 7.0. It's broken with 8.1.
I doubt that it is a Magisk error. It is either your SIM card going bad or an issue your system.
Sent from my SM-G900V using Tapatalk
Kaliaila said:
I doubt that it is a Magisk error. It is either your SIM card going bad or an issue your system.
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
It's not a system issue nor a SIM issue. It's ONLY after flashing Magisk on 8.1. It doesn't occur on 7.0, it doesn't occur on 7.0 with Magisk flashed, and it doesn't occur on 8.1 without Magisk flashed. It's the combination of Magisk and 8.1.
Everything works fine using any other combination with Magisk, or just stock ROMs alone.
The IMEI, etc, is showing UNKNOWN after I flash Magisk on 8.1.
Are you using stock or a different rom?
Sent from my SM-G900V using Tapatalk
Kaliaila said:
Are you using stock or a different rom?
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
I'm using stock both with and without Magisk flashed. I don't use custom ROMs.
I source my firmware from Updato.
Well, just know that on other phones and different Roms that have had that exact problem, it would occur sporadically with and without Magisk being installed. In most cases it was a bug in the rom and not Magisk.
I personally do not know how it could be caused by Magisk.
Sent from my SM-G900V using Tapatalk
Kaliaila said:
Well, just know that on other phones and different Roms that have had that exact problem, it would occur sporadically with and without Magisk being installed. In most cases it was a bug in the rom and not Magisk.
I personally do not know how it could be caused by Magisk.
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
It's not possible to revert to 7.0 without a backup is it?
I would wait and see if anyone else replies first, but I think there are ways but they are not necessarily simple.
You would probably be better off asking that in a forum for your specific phone.
Sent from my SM-G900V using Tapatalk
Had the same issue, no Magisk installed. I dropped my phone a few times. Noticed sim card warning a few boot ups later. So I opened up the back and took out card and put it in again. No problem.
Same issue here. After flash Magisk 17.1 or 17.3, system doesn't detect SIM card. Android 7.1.2, MTK6580 soc. Works relatively well with the Magisk 16, however there is always the message "emergency call only" and I must manually change radio frequency. So yes, Magisk affects radio operation on some devices.
In another device with Snapdragon, no issues related.
Hi,
Now they fixed the fingerprint in the ç27 update. I rooted my x2pro again with Magisk 20.4 So far so good.
Now I really wanted my viper4android Android back, but I get a bootloop when activating the driver.
I tried the aml patch but no luck so far.
Anybody tried this with success?
Luckily it's easy to undo the install in TWRP.
Just run the zip file and it would uninstall v4a.
Hellsblade said:
Hi,
Now they fixed the fingerprint in the ç27 update. I rooted my x2pro again with Magisk 20.4 So far so good.
Now I really wanted my viper4android Android back, but I get a bootloop when activating the driver.
I tried the aml patch but no luck so far.
Anybody tried this with success?
Luckily it's easy to undo the install in TWRP.
Just run the zip file and it would uninstall v4a.
Click to expand...
Click to collapse
I managed to get v4a working again after hours trying different methods
Install magisk
Get the aml and v4a rootless zip version here https://zackptg5.com/android.php not from magisk repo
First install AML through magisk install complete don't reboot now got recovery install v4a rootless zip when install complete reboot
After that install v4a apk xda labs version https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
Now you have working v4a c 27 update
Wow great.
It works again. I'm what they call a happy camper ?
NB: My setup picture for my Sony WF1000 in ears. I use an old studer.irs for convolver. 2 ms deferential sound. Balance a little to left for compensation and viper clarity natural...
Thanks for helping me out.
Good evening, you can tell me how I update my realme x2pro to c27 and the rooted, I'm on the c11 rooted version and twrp installed, I did not want to update it to Android 10 not to lose the fingerprint, but now that they are fixed the problem on c27 I would like to update it. If there's someone who can help me and give me a link to a tutorial, I haven't found here on xda a tutorial that explains the root and installation of twrp. Thank you
---------- Post added at 01:45 AM ---------- Previous post was at 01:44 AM ----------
Hellsblade said:
Hi,
Now they fixed the fingerprint in the ç27 update. I rooted my x2pro again with Magisk 20.4 So far so good.
Now I really wanted my viper4android Android back, but I get a bootloop when activating the driver.
I tried the aml patch but no luck so far.
Anybody tried this with success?
Luckily it's easy to undo the install in TWRP.
Just run the zip file and it would uninstall v4a.
Click to expand...
Click to collapse
Good evening, you can tell me how I update my realme x2pro to c27 and the rooted, I'm on the c11 rooted version and twrp installed, I did not want to update it to Android 10 not to lose the fingerprint, but now that they are fixed the problem on c27 I would like to update it. If there's someone who can help me and give me a link to a tutorial, I haven't found here on xda a tutorial that explains the root and installation of twrp. Thank you
Aze0077 said:
I managed to get v4a working again after hours trying different methods
Install magisk
Get the aml and v4a rootless zip version here https://zackptg5.com/android.php not from magisk repo
First install AML through magisk install complete don't reboot now got recovery install v4a rootless zip when install complete reboot
After that install v4a apk xda labs version https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
Now you have working v4a c 27 update
Click to expand...
Click to collapse
This should not disable stock dolby atmos options right?
adsubzero said:
This should not disable stock dolby atmos options right?
Click to expand...
Click to collapse
No it doesn't, but I turn it off anyway because it's adding a bit too much for my liking.
Hellsblade said:
No it doesn't, but I turn it off anyway because it's adding a bit too much for my liking.
Click to expand...
Click to collapse
Ah yeah I mean I like to use the movie preset when playing though speakers, so that's great.
Do you guys have any issues with system sounds and ringtone? If I'm not using a convolver it's fine, but with convolver active there are unusual sound glitches and audio pops.
adsubzero said:
Do you guys have any issues with system sounds and ringtone? If I'm not using a convolver it's fine, but with convolver active there are unusual sound glitches and audio pops.
Click to expand...
Click to collapse
No problems with system sounds here.
I'm using convolver with studer -1db irs.And output gain on minus 6.
Hellsblade said:
No problems with system sounds here.
I'm using convolver with studer -1db irs.And output gain on minus 6.
Click to expand...
Click to collapse
Could you please go into sound settings and then change the media volume slider so it plays that short sound? Nothing weird happens for you?
adsubzero said:
Could you please go into sound settings and then change the media volume slider so it plays that short sound? Nothing weird happens for you?
Click to expand...
Click to collapse
Yep there is always a bit of lag before the driver kick's in when playing media audio. Also when you start playing music. I don't think there's a solution for that.
I think I just got used ?
Hellsblade said:
Yep there is always a bit of lag before the driver kick's in when playing media audio. Also when you start playing music. I don't think there's a solution for that.
I think I just got used ?
Click to expand...
Click to collapse
Ah yes that's the thing, but the problem is when receiving notifications from different apps.
For instance I get a notification from Viber and there's a slight pop, but then I receive a notification from Facebook and first it plays the remaining sound from Viber then from FB and it sounds really messed up.
It's sad if there's no solution, but I guess I'll keep investigating.
Though I don't think there's no solution, since this always worked fine for me, previously on Nexus 6P, LG V30 and HTC 10.
Btw, my suggestion for the SRS_1_1_Normal_stereo.irs convolver.
Edit the EQ to something like -2dB for the bass freq and -4dB for 4KHz, the rest is up to you.
It gives incredible deep bass and better bass response to the speakers.
Edit: the partial solution for the mentioned issue is to enable attach audio effects option in V4A. I'm not sure if it works for every audio player, but it works with Poweramp. What it does is it disables V4A processing for everything but the music player. The drawback to this is when I'm listening to something in Poweramp and want to play something eg. on YouTube, there is no sound at first. It works okay when I stop/close poweramp. For my usage this is kind of fine I guess, so I thought I would share.
hello everyone and thanks for the explanation everything works correctly now
I don't know if it only happens to me or if it is normal, when I close the multitasking v4a application it stops working, I tried turning it into a system application but the same thing happens, can you help me with that question?
Aze0077 said:
I managed to get v4a working again after hours trying different methods
Install magisk
Get the aml and v4a rootless zip version here https://zackptg5.com/android.php not from magisk repo
First install AML through magisk install complete don't reboot now got recovery install v4a rootless zip when install complete reboot
After that install v4a apk xda labs version https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
Now you have working v4a c 27 update
Click to expand...
Click to collapse
why i cant find xda version apk anywhere ? other versions doesnt work
peymanbeyraghi said:
why i cant find xda version apk anywhere ? other versions doesnt work
Click to expand...
Click to collapse
https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
thanks , i have fixed it , i forget to install selinux on magisk . after that all versions works fine .
Aze0077 said:
I managed to get v4a working again after hours trying different methods
Install magisk
Get the aml and v4a rootless zip version here https://zackptg5.com/android.php not from magisk repo
First install AML through magisk install complete don't reboot now got recovery install v4a rootless zip when install complete reboot
After that install v4a apk xda labs version https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
Now you have working v4a c 27 update
Click to expand...
Click to collapse
Hey, I have used this method previously to install V4A, but I can't get it working anymore. After trying out custom ROMs, I've gone back to clean RUI 1.0 C38, and following the same steps the V4A doesn't work. Has anyone found a reliable way to install V4A?