[APP][ALL ROOT SOLUTIONS][6.0+]ViPER4Android FX 2.7

[MAVEI21CK]

Does viper work on Android 10?

Sent from my beryllium using XDA Labs

 

[xdausernext]

Yes

Sent from my MI 9 using Tapatalk

 

[hoorinek]

Yes

Sent from my MI 9 using Tapatalk

How can I install V4A on A10 - MIUI 11, please? Didn't work for me.

 

[niko60]

Try this if you want http://bit.ly/2P4gSH7 ,

http://bit.ly/335HgUB can't be 100% it will theme v4a but swift installer themes it on my Nokia 6.1

Tried them, but they don't work properly.

 

[grandpajiver]

If anyone has got this working for OOS 10 (Android 10), more specifically OP7T/Pro, I'd appreciate if you reached out.
Used this mod before and it was awesome, hopefully there's a way to make it work for me.

Bootloops for me... and cuz we don't have TWRP, there isn't a way to easily disable the module, which blows.

 

[DorianX]

Bootloops for me... and cuz we don't have TWRP, there isn't a way to easily disable the module, which blows.

Same here, Nexus 7 (2013), LineageOS 17, fortunately we have TWRP to disable the module. This issue is because SAR (maybe?)

Enviado desde mi Nexus 7 mediante Tapatalk

 

[DiamondJohn]

can't seem to figure it out for the life of me on how to get viper4android to still process even when Google is speaking the next turn direction via voice. Has anyone ran into this issue? Anyone managed to fix this?

A few years back, I had what sounds (no pun intended) like the exact same issue you describe. I use my phone for both navigation and also plugged into my stereo for music. Whenever Google maps gave a verbal direction, viper would stop processing.

I do not know if it is still the same, as I now run v2.7 (previously it was 2.5), and probably more significantly I use different apps for navigation, so would not know either way. I use Waze (as it includes traffic and is more accurate at determining times) or Here (only as a backup under emergencies). I know its not a real solution, but if this is your only issue, maybe consider using another navigation app.

 

[bestgio]

A few years back, I had what sounds (no pun intended) like the exact same issue you describe. I use my phone for both navigation and also plugged into my stereo for music. Whenever Google maps gave a verbal direction, viper would stop processing.

I do not know if it is still the same, as I now run v2.7 (previously it was 2.5), and probably more significantly I use different apps for navigation, so would not know either way. I use Waze (as it includes traffic and is more accurate at determining times) or Here (only as a backup under emergencies). I know its not a real solution, but if this is your only issue, maybe consider using another navigation app.

I've tried doing more searching around the thread and found that this general issue applies to voice navigation with both Google Maps and Waze alike (for people who did report the issue). So you're saying other navigation apps like Waze and Here doesn't have this issue for you at all? The funny thing is that I'm coming from an OG Pixel XL, and with just the installation of Audio Compatibility Patch, I was able to get viper to process everything just fine including google maps.

I will try installing Waze and see if the issue still occurs and report back.

Not sure if this may be a factor but, I play music via Bluetooth and I also tried testing it on the phone speakers itself too and the issue seems to be happening regardless of the output device.

 

[DiamondJohn]

I've tried doing more searching around the thread and found that this general issue applies to voice navigation with both Google Maps and Waze alike (for people who did report the issue). So you're saying other navigation apps like Waze and Here doesn't have this issue for you at all? The funny thing is that I'm coming from an OG Pixel XL, and with just the installation of Audio Compatibility Patch, I was able to get viper to process everything just fine including google maps.

I will try installing Waze and see if the issue still occurs and report back.

Not sure if this may be a factor but, I play music via Bluetooth and I also tried testing it on the phone speakers itself too and the issue seems to be happening regardless of the output device.

I did not explicitly monitor when it stopped happening, and it has been a long time since I remember noting that it occurs. All i can say is that a few years back, while running Viper v2.5, google maps voice navigation instructions would switch Viper processing off, and then it would come back on. I noticed i as I also had my phone plugged in as the music player in my car.

Today I am running a different device, different ROM and different Viper, and it never cuts out when Waze gives a voice direction. I have not used Google maps for navigation for a long time, so do not know if it still does it now. Possibly the newer ROM and device has fixed it for both. I have a vague memory that when it was occurring for Google maps, it wasn't occurring for Here navigation.

 

[xdausernext]

How can I install V4A on A10 - MIUI 11, please? Didn't work for me.

You need to root with magisk 20.0 + module for viper.

Sent from my MI 9 using Tapatalk

 

[fil3s]

Tried them, but they don't work properly.

Optionally u can type this in terminal

Su

settings put secure ui_night_mode 2

Don't forget to reboot.

 

[hoorinek]

You need to root with magisk 20.0 + module for viper.View attachment 4859471

Sent from my MI 9 using Tapatalk

For me, didn´t work. After installation V4A driver - reboot to fastboot. Bootloap.

 

[Steve Punter]

I have a strange issue with TuneIn Radio. This app works with v4a when I'm on Bluetooth (Processing: Yes). However, if I try to listen through the internal speaker or through the headset jack, it doesn't (Processing: No). This appears to be the only app I've found that behaves this way, as everything else seems to work fine.

I've installed the Audio Compatibility Patch from Magisk, but this hasn't helped. And yes, the Master Limiter switch is turned on in Headset and Speaker modes.

Does anyone have in insight to this, or has seen a similar issue.

 

[PoochyX]

I have a strange issue with TuneIn Radio. This app works with v4a when I'm on Bluetooth (Processing: Yes). However, if I try to listen through the internal speaker or through the headset jack, it doesn't (Processing: No). This appears to be the only app I've found that behaves this way, as everything else seems to work fine.



I've installed the Audio Compatibility Patch from Magisk, but this hasn't helped. And yes, the Master Limiter switch is turned on in Headset and Speaker modes.



Does anyone have in insight to this, or has seen a similar issue.

TuneIn works for me all around

([emoji3590]09-09-18[emoji3590])

 

[Smoke99]

Hi, i have installed viper4android fx through magisk manager.
Now every time i boot the tablet it open the app of viper4android... why?

 

[bestgio]

I did not explicitly monitor when it stopped happening, and it has been a long time since I remember noting that it occurs. All i can say is that a few years back, while running Viper v2.5, google maps voice navigation instructions would switch Viper processing off, and then it would come back on. I noticed i as I also had my phone plugged in as the music player in my car.

Today I am running a different device, different ROM and different Viper, and it never cuts out when Waze gives a voice direction. I have not used Google maps for navigation for a long time, so do not know if it still does it now. Possibly the newer ROM and device has fixed it for both. I have a vague memory that when it was occurring for Google maps, it wasn't occurring for Here navigation.

This is interesting, I installed Waze and tried using navigation with Waze and Viper doesn't cut out when Waze speaks?!

I suspect this is definitely a per device/Android version/Google maps version that's causing variability between everyone's experience with Viper. After playing with every possible combination of settings in Audio Compatibility Patch, everything works except Google Maps audio. At this point I would say it's definitely got to be with the Maps app itself, and with the Pixel 4 XL specifically since my OG Pixel XL never had this issue to begin with (using the legacy viper with Android N, O, P, and the new viper here with Android 10).

I'm just personally used to using Google Maps everything but a little workaround is to change the navigation audio to "softer" in Maps settings to help with the extreme audio transitions when viper stops processing when the next turn direction is being played and then starts processing right after. Not really a full solution, but still not the end of the world.

Hopefully future versions of viper and audio compatibility patch would get this ironed out, but as of now this is better than nothing!

 

[Joe199799]

Really stupid question no chance viper could process audio casted to a Google home mini right? Since I'm guessing you're not really playing music from your phone to it, you're just telling it to play music right?

 

[NeoMember]

can't install V4A 2.7.1.0 on my OnePlus 3T running Nitrogen 10, whenever I install the drivers and it reboots, I get stuck in the fastboot menu. tried the Audio Modification library method but it didn't work either. any ideas on how to get around that?

 

[morfances]

can't install V4A 2.7.1.0 on my OnePlus 3T running Nitrogen 10, whenever I install the drivers and it reboots, I get stuck in the fastboot menu. tried the Audio Modification library method but it didn't work either. any ideas on how to get around that?

Here is the solution that I found: let me know if it works for you too

FLASHING TUTORIAL:

1)First flash this File via twrp:

V4aFx_Rootless (https://www.pling.com/p/1330699/sta...p&file_type=application/zip&file_size=3964619)

2)Second flash this file via twrp:

AUDIO MODIFICATIONS (https://www.pling.com/p/1330699/sta...zip&file_type=application/zip&file_size=17510)

And Reboot then

3) FLASH THIS FILE VIA MAGISK ONLY

V4aFx (https://www.pling.com/p/1330699/sta...p&file_type=application/zip&file_size=3625438)

Reboot and enjoy!!

 

[MatBru]

Spectrum analyzer with FIR equalizer

I find it quite difficult to tune the FIR equalizer for a great sound.
It would help a lot if it could be overlayed on top of a spectrum analyzer, like the one in the LOS lock screen.
You could then "see" the spectrum peaks and adjust the equaliser accordingly.
Devs, what do you think?