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

[gfrank227]

Is this particular version for all root solutions? Like to be used by everybody that's rooted?

Cuz I tried about half dozen Viper FX installs not one of them would work.
I'll give this one a shot but if anybody knows that I'm doing something wrong speak up, and I'll follow your direction.

Thank you, @SouthOkanagan

V4A FX should automatically detect the correct driver to install.

Several suggestions - have you used Audio Modifications Library? First, install AML, restart and V4A, and install the V4A drivers. Then disable AML, restart, go into V4A again, and install drivers again.

Then, make sure that either Selinux is set to permissive, or that you make the changes to the setup file in the root that is discussed above.

See if this helps.

 

[DiamondJohn]

Is this particular version for all root solutions? Like to be used by everybody that's rooted?
...snip...

which "particular solution" are you speaking about?

It wold be best if you let people know your Device, ROM & android version.

 

[ProjectAlly]

Ran a search in the thread, but was curious if anyone with a (Pixel 5) running the latest Android 12 beta, has had any success in flashing v4a. Thinking specifically of Ichigo Kywrosaki's v2716.
I've just upgraded and learned that while I can get reliable root through Magisk, v4a closes upon opening. Thanks for any input!

 

[DiamondJohn]

Ran a search in the thread, but was curious if anyone with a (Pixel 5) running the latest Android 12 beta, has had any success in flashing v4a. Thinking specifically of Ichigo Kywrosaki's v2716.
I've just upgraded and learned that while I can get reliable root through Magisk, v4a closes upon opening. Thanks for any input!

Logcat.

 

[ProjectAlly]

Logcat.

Here's my logcat: Pixel 5 V4A 2716 Android 12 Beta 3 Log

Hopefully it shows what is going on. I'm suspecting the driver isn't properly installing or isn't loading correctly.

The version I mentioned before I've been using since Android 10. I imagine that Android 12 does things differently.

I should also mention that I've used both the original Ichigo permissive build, and the enforcing zip that was posted a page or two back. Same issue either way.

The app will load, stay open for a few seconds then crash before I can mess with settings. This is also on a newly wiped and fresh Android 12 Beta 3 flash. When flashing the OS I disabled verity and verification as per a post for my device, in order to successfully obtain root with Magisk Canary.

Also within Magisk, V4A is the only module installed, since running this particular zip over two other Android OS versions, I've had no need for AML, ACP, etc, because they weren't necessary to run Viper without issue.

 

[DiamondJohn]

Ran a search in the thread, but was curious if anyone with a (Pixel 5) running the latest Android 12 beta, has had any success in flashing v4a. Thinking specifically of Ichigo Kywrosaki's v2716.
I've just upgraded and learned that while I can get reliable root through Magisk, v4a closes upon opening. Thanks for any input!

I am assuming you are using the same zip I linked to above.

Here's my logcat: Pixel 5 V4A 2716 Android 12 Beta 3 Log

Hopefully it shows what is going on. I'm suspecting the driver isn't properly installing or isn't loading correctly.

The version I mentioned before I've been using since Android 10. I imagine that Android 12 does things differently.

I should also mention that I've used both the original Ichigo permissive build, and the enforcing zip that was posted a page or two back. Same issue either way.

The app will load, stay open for a few seconds then crash before I can mess with settings. This is also on a newly wiped and fresh Android 12 Beta 3 flash. When flashing the OS I disabled verity and verification as per a post for my device, in order to successfully obtain root with Magisk Canary.

Also within Magisk, V4A is the only module installed, since running this particular zip over two other Android OS versions, I've had no need for AML, ACP, etc, because they weren't necessary to run Viper without issue.

Your error is:

[07-18 01:01:38.208 27084:27084 E/AndroidRuntime]
FATAL EXCEPTION: main
Process: process.ViPER4Android, PID: 27084
android.app.ForegroundServiceDidNotStartInTimeException: Context.startForegroundService() did not then call Service.startForeground(): ServiceRecord{263590a u0 com.pittvandewitt.viperfx/.service.ViPER4AndroidService}
    at android.app.ActivityThread.throwRemoteServiceException(ActivityThread.java:1915)
    at android.app.ActivityThread.access$2500(ActivityThread.java:250)
    at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2140)
    at android.os.Handler.dispatchMessage(Handler.java:106)
    at android.os.Looper.loopOnce(Looper.java:201)
    at android.os.Looper.loop(Looper.java:288)
    at android.app.ActivityThread.main(ActivityThread.java:7829)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:982)

To be clear, I am NOT running A12, but A11 on a Pixel 4A, so all the below is a blind stab in the dark.

Its failing to start the viper service (from above log), before viper opens.

Try starting the service [com.pittvandewitt.viperfx/.service.ViPER4AndroidService] manually through a shell. Check if that works or gives you any different errors. (not sure if the below will work without modifying the APK manifest)
see: https://stackoverflow.com/questions/7415997/how-to-start-and-stop-android-service-from-a-adb-shell
am start-foreground-service com.pittvandewitt.viperfx/.service.ViPER4AndroidService;

 

[ProjectAlly]

@

DiamondJohn​

So I tried that command and interestingly it kind of helps the app stay open without immediately closing. It's also the same effect I get when quickly going to the options settings inside V4A and toggling the "compat mode" and "attach audio effects" settings.

Either way the app is now running, but just like with v2.7.2.1 on A11 and 12, I can't get V4A to enable or process audio at all. Would this be driver related or come down to editing the manifest file for V4A? Also when installing the Ichigo version 2.7.1.6 I've used all this time up until now, it usually has a persistent notification on in the notification area, but on Android 12 it won't let it run a persistent notification at all.

 

[Adevem]

Took a video last night and the recorded audio is a bit glitchy and "weaves" in and out. It's not totally clear. Almost like there's a limiter or noise gate on the mic during recording.

I have it in legacy mode with permissive mode on - I'm on the OP5T

Only have Master Limiter and Gain Control on, could those be the culprit?

Any ideas will be insightful - Thanks!

 

[gfrank227]

I am assuming you are using the same zip I linked to above.

Your error is:

[07-18 01:01:38.208 27084:27084 E/AndroidRuntime]
FATAL EXCEPTION: main
Process: process.ViPER4Android, PID: 27084
android.app.ForegroundServiceDidNotStartInTimeException: Context.startForegroundService() did not then call Service.startForeground(): ServiceRecord{263590a u0 com.pittvandewitt.viperfx/.service.ViPER4AndroidService}
    at android.app.ActivityThread.throwRemoteServiceException(ActivityThread.java:1915)
    at android.app.ActivityThread.access$2500(ActivityThread.java:250)
    at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2140)
    at android.os.Handler.dispatchMessage(Handler.java:106)
    at android.os.Looper.loopOnce(Looper.java:201)
    at android.os.Looper.loop(Looper.java:288)
    at android.app.ActivityThread.main(ActivityThread.java:7829)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:982)

To be clear, I am NOT running A12, but A11 on a Pixel 4A, so all the below is a blind stab in the dark.

Its failing to start the viper service (from above log), before viper opens.

Try starting the service [com.pittvandewitt.viperfx/.service.ViPER4AndroidService] manually through a shell. Check if that works or gives you any different errors. (not sure if the below will work without modifying the APK manifest)
see: https://stackoverflow.com/questions/7415997/how-to-start-and-stop-android-service-from-a-adb-shell
am start-foreground-service com.pittvandewitt.viperfx/.service.ViPER4AndroidService;

In Android 10 and 11, many people, including myself, needed to install AML, reboot, then install v4a drivers, then disable AML, reboot, and reinstall drivers. Not sure about 12, but you should try this first, if you haven't already.

 

[timofonic]

Excuse me.

Did V4A development stalled?

Are there an Open Source alternative?

If development stalled: Any hopes to Open Source it even by some kind of bounty?

 

[ProjectAlly]

Excuse me.

Did V4A development stalled?

Are there an Open Source alternative?

If development stalled: Any hopes to Open Source it even by some kind of bounty?

Curious about this as well. I know its probably a no-no to ask about these kinds of things, but is there anyone actively still developing this audio mod?

A lot of us have come to rely on it, it's really the only reason I root my phone at all. If there was a system wide EQ app that actually sounded great then I'm sure that would eliminate need of this.

But I love V4A, just have no knowledge on app development, I'd love to maintain it if I did have this knowledge.

 

[Lord Sithek]

Curious about this as well. I know its probably a no-no to ask about these kinds of things, but is there anyone actively still developing this audio mod?

A lot of us have come to rely on it, it's really the only reason I root my phone at all. If there was a system wide EQ app that actually sounded great then I'm sure that would eliminate need of this.

But I love V4A, just have no knowledge on app development, I'd love to maintain it if I did have this knowledge.

The app itself is still in development, although not updated very frequently. But the driver has been always closed source and the original devs abandoned it long time ago

As an alternative you can try JamesDSP, although it's not that simple and straightforward to use as Viper

 

[gfrank227]

The app itself is still in development, although not updated very frequently. But the driver has been always closed source and the original devs abandoned it long time ago

As an alternative you can try JamesDSP, although it's not that simple and straightforward to use as Viper

James is good, but not as good.

I don't know anything about app development either. But I imagine if the project has been abandoned, someone must be able to extract the code somehow and work on it?

 

[Lord Sithek]

James is good, but not as good.

I don't know anything about app development either. But I imagine if the project has been abandoned, someone must be able to extract the code somehow and work on it?

I don't know nothing about extracting the code. The only thing I know is that the app was forked (hope this is the proper word?) by @Team_DeWitt and updated to work on newer Android versions

 

[DiamondJohn]

In Android 10 and 11, many people, including myself, needed to install AML, reboot, then install v4a drivers, then disable AML, reboot, and reinstall drivers. Not sure about 12, but you should try this first, if you haven't already.

I thihk you quoted the wrong person. I HAVE a working viper running on A11 using a single Magisk Zip, with no jumping through hoops installing extra components or the drivers as a seperate step, and rebooting multiple times and doing things in any special order. I simply flash a single Magisk Zip,. reboot, and it works. The post you quoted was me trying to assist someone else getting it to work in A12; that was not my error.

 

[DiamondJohn]

James is good, but not as good.

I don't know anything about app development either. But I imagine if the project has been abandoned, someone must be able to extract the code somehow and work on it?

You can decompile Java code to an extent, but what comes out is NOT pretty, and for a complex app such as this, it is not practical. Also, the magic would really be occurring in the driver, which I presume would not be written in java (ie not practicle to decompile).

And if it was as simplke as all that, someone would of already done it. Viper has been around for a long time.

 

[timofonic]

The app itself is still in development, although not updated very frequently. But the driver has been always closed source and the original devs abandoned it long time ago

As an alternative you can try JamesDSP, although it's not that simple and straightforward to use as Viper

Is JamesDSP still in development too?

GitHub - james34602/JamesDSPManager: Audio DSP effects build on Android system framework layer. This is a repository contains a pack of high quality DSP algorithms specialized for audio processing.

Audio DSP effects build on Android system framework layer. This is a repository contains a pack of high quality DSP algorithms specialized for audio processing. - james34602/JamesDSPManager

github.com

 

[timofonic]

I don't know nothing about extracting the code. The only thing I know is that the app was forked (hope this is the proper word?) by @Team_DeWitt and updated to work on newer Android versions

That team didn't post here since late 2020...

 

[Lord Sithek]

Is JamesDSP still in development too?

GitHub - james34602/JamesDSPManager: Audio DSP effects build on Android system framework layer. This is a repository contains a pack of high quality DSP algorithms specialized for audio processing.

Audio DSP effects build on Android system framework layer. This is a repository contains a pack of high quality DSP algorithms specialized for audio processing. - james34602/JamesDSPManager

github.com

I think yes. But you can reach devs mostly on Telegram these days: https://t.me/jDSP_V4A

 

[Lord Sithek]

That team didn't post here since late 2020...

True, they're not active here. I don't know if they follow this thread, but I know that the main dev appears from time to time on the official Viper Telegram group:

https://t.me/Viper4Android FX

(Looks like big part of the community moved to Telegram these days )

And from what I remember, the dev mentioned something about new release. But nobody knows when... As I said, the app seems to be still in development, but it's not rapid and if I understand correctly, it is al labout adjusting the app to the new Androids. And since the driver is closed source, the music quality and other features don't change