[APP] Official ViPER4Android Audio Effects (FX v2.5.0.5) - New Features & 7.0 Support

The OEM ROM simply means it's from (in my case) Samsung. I.e., it's not a Custom ROM. I was saying that I have never seen a Kernel put out by a developer to replace the Kernel that comes with a phone's OEM (Original Equipment Manufacturer) ROM. And I have searched a lot! There are things that a Custom Kernel would allow me to do, like OverClocking my CPU, while knocking the Voltage at each Frequency down, to keep the heat down while running faster, for one thing.

But hey, if you know where these Custom Kernels live, then please tell me, so I can go knock on their door. I'd be very grateful!

Can someone help?

I'm currently using Poweramp v2.0.10 Build 579, and I can't use V4A with it. I'm switching between Normal and Compatible Mode on V4A but still no success. Can some Poweramp users here tell me how to get it work?

Hey bud I'm not being mean scroll down do you see those arrows click on page 1 and read from top to when the creator of the forum stops writing it explains it

(Biting tounge) what service provider do you have sir/miss? (Not trying to be a wise guy don't know your sex by a screen name) and what kind of phone is it? I.e 'Sprint Samsung Galaxy S4 [sph-l720]

---------- Post added at 07:58 AM ---------- Previous post was at 07:55 AM ----------


Hey bud I'm not being mean scroll down do you see those arrows click on page 1 and read from top to when the creator of the forum stops writing it explains it

help unable to get to work on 5.1.1
driver installed but shows
status =abnormal
audio format = unsupported

It says "Disable their own sound effects". Already did that inside Poweramp, but still no V4A effects. Tried rebooting. Ugh...

Any Music Players you can suggest that has Media Utilities (for Zooper Widget use) support and can work with V4A? Cause I give up on Poweramp LOL...

It says "Disable their own sound effects". Already did that inside Poweramp, but still no V4A effects. Tried rebooting. Ugh...

Any Music Players you can suggest that has Media Utilities (for Zooper Widget use) support and can work with V4A? Cause I give up on Poweramp LOL...

Okay, I had no idea that a persons carrier made a difference when it came to the kernel they use. And not all phones belong to a specific carrier. Sprint uses a different format, so yes, their phone names start with "Sprint". But the name of my phone does not start with "MetroPCS", even though they are my carrier (now owned by T-Mobile).

FYI, if it helps, my info is in my signature below and yes, the Model # does tie back to MetroPCS, but that's only because they put their apps on it before selling it. Their name does not appear anywhere on the phone and it's a basic, Unlocked GSM phone (bought it from them that way), that I can use with any GSM Carrier.

I think maybe Sprint has tainted your view of phones. <lol>

Seriously, I understand why you might ask. And maybe different kernels are used for all I know. And if it helps, there it is. But also, in my sig, you'll see that I'm not using an OTA KK from MetroPCS. I got the ROM from Samsung and installed it using Odin. That would affect the Kernel too, no?

It says "Disable their own sound effects". Already did that inside Poweramp, but still no V4A effects. Tried rebooting. Ugh...

Any Music Players you can suggest that has Media Utilities (for Zooper Widget use) support and can work with V4A? Cause I give up on Poweramp LOL...

Download selinux mode changer from play store .. Change selinux to permissive ..reboot

Whoever is making the flashable zips that replace the entire audio_policy.conf file in ROMs, I found an alternative way which comments out the deep_buffer lines via sed command instead of replacing the file (as it may change in ROMs such as CM.) I have my own addon.d script that backs up what I would like it to, along with applying some changes for V4A functionality.

This is what I have in my addon.d script (placed under the post-restore section) to search and comment out the deep_buffer lines:

# audio_policy.conf edits for V4A compatibility
sed -i '/deep_buffer {/,/}/s/^/#/' /system/etc/audio_policy.conf

#      deep_buffer {
#        sampling_rates 8000|11025|12000|16000|22050|24000|32000|44100|48000
#        channel_masks AUDIO_CHANNEL_OUT_STEREO
#        formats AUDIO_FORMAT_PCM_16_BIT
#        devices AUDIO_DEVICE_OUT_EARPIECE|AUDIO_DEVICE_OUT_SPEAKER|AUDIO_DEVICE_OUT_WIRED_HEADSET|AUDIO_DEVICE_OUT_WIRED_HEADPHONE|AUDIO_DEVICE_OUT_ALL_SCO|AUDIO_DEVICE_OUT_AUX_DIGITAL|AUDIO_DEVICE_OUT_PROXY
#        flags AUDIO_OUTPUT_FLAG_DEEP_BUFFER
#      }

# build.prop edits for V4A functionality
echo "lpa.decode=false" >> /system/build.prop;
echo "lpa.releaselock=false" >> /system/build.prop;
echo "lpa.use-stagefright=false" >> /system/build.prop;
echo "tunnel.decode=false" >> /system/build.prop;

Go to post #4301 (page 431) of the official v4a thread