[Oxygen OS] [V4A] [WIP] Making V4A work on OxygenOS - OnePlus 2 General

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Dear OnePlus Two Users (the Audiophiles of you)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Almost everyone in the android-geek-business has heard of v4a, a Audiomod which "magically" improves your audioquality. Many of you might have faced sadness when realizing that on OOS v4a rather decreases quality instead off improving it. So I made it my personal Project to find a way to make Viper work on OxygenOs.
The idea of this tread is to inform you on my progress and to request files and infos I might need to fix v4a for Oxygen. And also as a central point for collaboration and progress-sharing with others working on the same problem.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Schedule:
- Find the issue
- Find a fix for this issue
- Make a guide for noobs (and geeks too)
- We are there!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Thank you all
Deletescape
Banner source: Unknown... If there would be any copyright problems just contact me!

---

Where the issue isn't:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In build.prop <- but let's better take another look there
Due to something of Maxxaudio
In /system/lib/soundfx or /system/lib64/soundfx
Probably no libs at all [emoji52]
asound or aplay
Probably not in any of the following cofig files
audio_effects.conf
audio_policy.conf
audio_output_policy.conf
mixer_paths.xml
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Thanks to @sewer56lol for some of this infos

---

#Reserved
One more you never know

---

If you want then I looked a bit into it at one point, though for not overly long.
Here's a head start:
=> mm.enable.qcom_parser=3314291 once broke OOS audio for me. Did once, now it doesn't for some reason (it's the value in the CM builds). => However this is unrelated to V4A as for it is not the reason it is broken.
=> Fixing V4A has nothing to do with build.prop
=> V4A is not broken because of MaxxAudio
=> V4A isn't broken because of audio sound effect libraries in lib/soundfx or lib64/soundfx.
=> At least CyanogenMod AudioFX works .
From here on there are not many things to test, the issue might even possibly happen to stem from the kernel. If you want you can try going the unprofessional (kinda really only way since OOS is Closed Source) and that is editing audio system of OOS with CyanogenMod's since it works on CM on our device.
Also the thread title baited me.

---

Additional head start:
=> It is not aplay or asound.
I highly recommend giving it a shot at editing audio_policy.conf to see if that is the culprit (maybe missing frequency etc.?).
I'll be traveling so I'll be unable to do that later.
I feel that the culprit may have a possibility of residing there.
Go compare it with the CM one and make changes, do these changes work? If no make more changes, keep making changes until audio breaks, if it breaks fix it, go to next line and make more changes.
Sent from my ONE A2003 using Tapatalk

---

Thanks @sewer56lol really appreciate your help and yep I already thought of audio_policy.cond being the issue. Right now I am trying to replace some files (including this one) with their cm version just to see what happens
Sent from my ONE A2001 using Tapatalk

---

sewer56lol said:
Additional head start:
=> It is not aplay or asound.
I highly recommend giving it a shot at editing audio_policy.conf to see if that is the culprit (maybe missing frequency etc.?).
I'll be traveling so I'll be unable to do that later.
I feel that the culprit may have a possibility of residing there.
Go compare it with the CM one and make changes, do these changes work? If no make more changes, keep making changes until audio breaks, if it breaks fix it, go to next line and make more changes.
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
It doesn't seem to be audio_policy so far... The only thing I achieved by completly replacing it with the one from cm is a "Nightcore"-Effect, everything is sped up to double speed (could fix that but don't see any need for it). The distortion we get from v4a stay the same.
Will still gonna take another look on the audio_policy.conf file...
What I have been thinking now is: As far as i know dolby dap is integrated in background (according to audio_effects.conf) dunno if this might play a role here.
EDIT: Interesting... Now nightcore effect is away as long as I don't enable v4a... (Or occasionally in some random moments)
Sent from my ONE A2001 using Tapatalk

---

i tried replacing various .conf files in various places, i did not work.
i wonder, will flashing a cm kernel on an oos rom brick it? if not, it might be a good idea to try and see if v4a works.

---

dgershko said:
i tried replacing various .conf files in various places, i did not work.
i wonder, will flashing a cm kernel on an oos rom brick it? if not, it might be a good idea to try and see if v4a works.
Click to expand...
Click to collapse
Yeah I think I've tried almost any config I could think of nothing really worked... And well had a similar idea as you right now... But I thought of trying to replace some system aps with the CM pendants...
And bout the kernel, well It could soft brick the oos rom and make a cleanflash mandatory but it would be cool to try [emoji23]
Sent from my ONE A2001 using Tapatalk

---

deletescape said:
Yeah I think I've tried almost any config I could think of nothing really worked... And well had a similar idea as you right now... But I thought of trying to replace some system aps with the CM pendants...
And bout the kernel, well It could soft brick the oos rom and make a cleanflash mandatory but it would be cool to try [emoji23]
Sent from my ONE A2001 using Tapatalk
Click to expand...
Click to collapse
Maybe try replacing sound related libs with these ones used in CM

---

DJ_MuTeD said:
Maybe try replacing sound related libs with these ones used in CM
Click to expand...
Click to collapse
Good idea will try this later today
Edit: had postponed it due to other things I had to do but I will definetly try it in the next days... If anyone else is interested to try it, do it! And report back
Sent from my ONE A2001 using Tapatalk

---

I'll backup and then flash cm kernel in an hour or so, will report back.

---

Awesome keep going

---

dgershko said:
I'll backup and then flash cm kernel in an hour or so, will report back.
Click to expand...
Click to collapse
Ok thanks sounds like an interesting way to try it
Sent from my ONE A2001 using Tapatalk

---

Much appreciated work... Thanks for your time bud...

---

ya .. keep going.. crack it guys... i know you can do it.

---

I'll be getting a op2 tom. will help with this one.
Sent from my Nexus 6P using Tapatalk

---

Abaddon said:
I'll be getting a op2 tom. will help with this one.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Thanks! Any possible help is appreciated
Sent from my ONE A2001 using Tapatalk

---

Happy new year everybody! Thank you for your efforts on this.. In case u need testers or something, count me in. Cheers
Στάλθηκε από το ONE A2003 μου χρησιμοποιώντας Tapatalk

---

hey guys pls refrain from posting stuff irrelevant to v4a and OxygenOS. post here if you got something in mind to help out. cheers!