It's not currently on the play store but it is here: http://xdaforums.com/showthread.php?t=2524485Download selinux mode changer from play store .. Change selinux to permissive ..reboot
Tapatalked that shiznit.
It's not currently on the play store but it is here: http://xdaforums.com/showthread.php?t=2524485Download 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:
Code:[COLOR="Green"]# audio_policy.conf edits for V4A compatibility[/COLOR] sed -i '/deep_buffer {/,/}/s/^/#/' /system/etc/audio_policy.conf
Once the script finishes what it needs to do, the deep_buffer lines will look like so:
Code:# 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 # }
And what I have in my addon.d script (also placed under the post-restore section) to add to build.prop
Code:[COLOR="Green"]# build.prop edits for V4A functionality[/COLOR] 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;
Hopefully these will be of use to some who also create their own addon.d scripts.
I added the policy to my test zips. Can you take a peak at the add.on script I use in my zips and see if this looks correct? I've attached it below.
BTW I find that with the deep buffer edits the build prop changes are not needed. Or at least no one has come back into my thread saying Viper stopped for them. Dozens of users from different devices are using my zips.
Sure enough it works as intended and in the right place
Here on my Nexus 5 running CM12.1 Nightly (CAF Version) I've had a few moments where V4A would not kick in after a while even with AudioFX removed completely. For example: it'll work fine before I get to class, but when I get out 2 hours later and continue playing my music, it wasn't processing until I rebooted. For me the commenting out of deep buffer seemed to have fixed it for me on CM CAF, unless it's the stupid memory leak in Lollipop causing it.
Sent from my Nexus 5 using Tapatalk
I did install it and run it and the Notification says it did it. Weird result otherwise though! But B4 that, it keeps running at Startup, setting it to Permissive. Is it supposed to do that? I mean, does it need to? Or once set, it stays set and I can take it out of Startup?
Have you uninstalled/freezed Samsung Music player and disabled SoundAlive as discribed in in the OP?
You're more than welcome to add it. It's at least something I can give back to the community.Awesome man. If you don't mind I'd like to add that to the zip and remove the edited .conf file. I had seen myfluxi's commits earlier this week about him editing the audio_policy.conf file for hammerhead and was wondering how that would come into play since so many ROMs use CM as their base. Your method works much cleaner.
I know that you'll probably think this a stupid question, but I ran this utility and it appeared to work fine. But it runs every time my phones boots up and my question is; Does it need to run and set to "Permissive Mode" every time my phone starts up? Or is it a "run once and it's done" utility and I don't need it any more?It's not currently on the play store but it is here: http://xdaforums.com/showthread.php?t=2524485
Tapatalked that shiznit.
My apologies Moderator, for my part in any arguments here in your thread. It won't happen again.I just cleaned several pages of crap from this thread. Please stick to the topic at hand. If you cannot do this without arguing & bickering then perhaps XDA is not the place for you.
Thanks
Magnum_Enforcer
FSM
I don't use xHiFi with v4afx anymore but I remember it always said Not Enabled in Driver Status unless music was actually playing.I did install it and run it and the Notification says it did it. Weird result otherwise though! But B4 that, it keeps running at Startup, setting it to Permissive. Is it supposed to do that? I mean, does it need to? Or once set, it stays set and I can take it out of Startup?
Anyway, after running this utility, I was able to get my phone to see it as a System App (Yaaay!).
However, when I went to run the XHiFi app (after setting my phone to it), my screen went black and stayed black. I could flip it to the background though. I tried rebooting, same result. I then went to Kill the process, which didn't work, but after 3 tries, XHiFi prompted for SU access. Weird, huh?
Anyway, after that and rebooting, the app did come up fine. I installed the sriver, Enabled XHiFi in the apps' settings and rebooted.
When it came up, I opened the XHiFi app and checked "Driver Status", but it is not Enabled. Tried Uninstall/Reinstal and a couple of other things, but no luck.
I'll have to figure out what's going on, but I thought you might find this bit interesting.
Thank you for the app though! I got farther in a couple of minutes, than I have for the last 3 days! And that, contrary to popular belief, that was indeed including lots of reading.
Thanks again!!!
It isn't his thread since he didn't create it but he is one of the moderators in charge of this forum.I know that you'll probably think this a stupid question, but I ran this utility and it appeared to work fine. But it runs every time my phones boots up and my question is; Does it need to run and set to "Permissive Mode" every time my phone starts up? Or is it a "run once and it's done" utility and I don't need it any more?
I appreciate your time. Thank you in advance for your patience with me.
---------- Post added at 09:21 PM ---------- Previous post was at 09:19 PM ----------
My apologies Moderator, for my part in any arguments here in your thread. It won't happen again.
I use this and SuperSU on my tablet, when my device is powered on, I just get a toast message saying it's been granted super user permissions and when I check in settings it's permissive right from the start. If you're having something different, maybe ask on the thread I linked?I know that you'll probably think this a stupid question, but I ran this utility and it appeared to work fine. But it runs every time my phones boots up and my question is; Does it need to run and set to "Permissive Mode" every time my phone starts up? Or is it a "run once and it's done" utility and I don't need it any more?
I appreciate your time. Thank you in advance for your patience with me.
---------- Post added at 09:21 PM ---------- Previous post was at 09:19 PM ----------
My apologies Moderator, for my part in any arguments here in your thread. It won't happen again.
I know that you'll probably think this a stupid question, but I ran this utility and it appeared to work fine. But it runs every time my phones boots up and my question is; Does it need to run and set to "Permissive Mode" every time my phone starts up? Or is it a "run once and it's done" utility and I don't need it any more?
I appreciate your time. Thank you in advance for your patience with me.
---------- Post added at 09:21 PM ---------- Previous post was at 09:19 PM ----------
My apologies Moderator, for my part in any arguments here in your thread. It won't happen again.
I think you may be thinking of the one that says; "Processing". The "Enabled" one should say "Yes" if the driver is working.I don't use xHiFi with v4afx anymore but I remember it always said Not Enabled in Driver Status unless music was actually playing.
I'm extremely familiar with v4afx and v4axhifi, when using both on my devices v4afx will always say enabled with no music playing, however, xhifi always showed not enabled with no music playing. Play some music and xhifi is suddenly enabled and processing. I don't post much but when I do it's with plenty of confidence, otherwise I'll let someone else post the necessary/requested information.I think you may be thinking of the one that says; "Processing". The "Enabled" one should say "Yes" if the driver is working.
I was thinking of FX, no doubt. And based on your word, I set it all for XHiFi and rebooted. Then I loaded the music player I usually use (Music Folder Player Full, by ZorillaSoft), started playing a song, flipped back and checked out XHiFi and sure enough, it said; "Enabled"! You were right!I'm extremely familiar with v4afx and v4axhifi, when using both on my devices v4afx will always say enabled with no music playing, however, xhifi always showed not enabled with no music playing. Play some music and xhifi is suddenly enabled and processing. I don't post much but when I do it's with plenty of confidence, otherwise I'll let someone else post the necessary/requested information.
I would not use xhifi alone as I depend on the covolver function in v4afx, v4afx will always be mandatory for me. Also mandatory for me is ExtremeBeats 4.1, also found in this forum section. V4afx and ExtremeBeats 4.1 has been the best combo I've ever tried with other combinations of mods. I used xhifi along with v4a fx and ExtremeBeats for a long time but I definitely noticed an improvement disabling xhifi. In my setup, I noticed that xhifi simply added too much " noise" to the overall audio.I was thinking of FX, no doubt. And based on your word, I set it all for XHiFi and rebooted. Then I loaded the music player I usually use (Music Folder Player Full, by ZorillaSoft), started playing a song, flipped back and checked out XHiFi and sure enough, it said; "Enabled"! You were right!
So apparently, I've actually had it working since running the "SELinux2" Apk and just didn't know it! <lol>
I want to say a sincere and very big; "Thank You!". I really appreciate your help! I really do! Without your knowledge of this fact, I'd still be pulling my hair out, probably for some time to come et!
May I ask you just one question, please? If I am using XHiFi, do I need to even have FX on my device? Thank You!
v4a_fx {
path /system/lib/soundfx/libv4a_fx_xxx.so
}
#NECESSARY FOR XHIFI
v4a_xhifi {
path /system/lib/soundfx/libv4a_xhifi_xxx.so
}
v4a_standard_fx {
library v4a_fx
uuid 41d3c987-e6cf-11e3-a88a-11aba5d5c51b
}
#NECESSARY FOR XHIFI
v4a_standard_xhifi {
library v4a_xhifi
uuid d92c3a90-3e26-11e2-a25f-0800200c9a66
}