It would appear that Samsung locked the SELinux to Enforcing but I was curious if anyone was able to get V4A working. I have been unsuccessful.
unsuccessful here too.It would appear that Samsung locked the SELinux to Enforcing but I was curious if anyone was able to get V4A working. I have been unsuccessful.
Thanks for linking to this. I may give it a shot.There is a version of v4a made for lollipop on the nexus 5 called lolliviper. Its a zip that needs to be flashed, so we should be able to flash this using fireflash.
I didnt make a backup before I flashed 5.0 so I'm hesitant try it. Maybe someone is brave enough to try for us and report back?
http://forum.xda-developers.com/google-nexus-5/themes-apps/discussion-viper4android-t2543796
I installed a variation of the zip that i got from the OPO forums, it added some libs and changed a couple files and also added the viperaudio apk to priv-app, like it says in the thread, but i believe it was on older version, regardless it said the driver installed, and the option changed to uninstall driver implying it was, but i didn't notice much difference(didn't have much time to test though, bricked shortly after, unrelated) you can give it a shot though, it should work fine just do the first zip attatched, maybe the second, it says in the thread though that you NEED a permissive kernel so it working is doubtful.There is a version of v4a made for lollipop on the nexus 5 called lolliviper. Its a zip that needs to be flashed, so we should be able to flash this using fireflash.
I didnt make a backup before I flashed 5.0 so I'm hesitant try it. Maybe someone is brave enough to try for us and report back?
http://forum.xda-developers.com/google-nexus-5/themes-apps/discussion-viper4android-t2543796
You are correct. I read the thread and regardless of how V4A is installed, the end result is the same. We need SELinux to be permissive which appears to be currently impossible with our stock kernel.I installed a variation of the zip that i got from the OPO forums, it added some libs and changed a couple files and also added the viperaudio apk to priv-app, like it says in the thread, but i believe it was on older version, regardless it said the driver installed, and the option changed to uninstall driver implying it was, but i didn't notice much difference(didn't have much time to test though, bricked shortly after, unrelated) you can give it a shot though, it should work fine just do the first zip attatched, maybe the second, it says in the thread though that you NEED a permissive kernel so it working is doubtful.
multisystem for android ( found here http://forum.xda-developers.com/att-galaxy-s5/help/qa-multisystem-android-t3101217 ) says it supports selinux permissive mode, so perhaps we can use this to flash a rom to a secondary slot, enable permissive mode with selinux mode changed apk, and then follow the lolliviper instuctions to get viper back.You are correct. I read the thread and regardless of how V4A is installed, the end result is the same. We need SELinux to be permissive which appears to be currently impossible with our stock kernel.
I tried it, didnt work, seems it needs more tha just selinux set to permissive.multisystem for android ( found here http://forum.xda-developers.com/att-galaxy-s5/help/qa-multisystem-android-t3101217 ) says it supports selinux permissive mode, so perhaps we can use this to flash a rom to a secondary slot, enable permissive mode with selinux mode changed apk, and then follow the lolliviper instuctions to get viper back.
Ton of work for little reward but I really miss having viper.
I will try this method if and when I ever get a day off
Requires a custom kernel set to permissive which we don't have.
You have a custom rom with a permissive kernel and it still doesn't work? That's interesting.![]()
Sent from my Twi5ted SM-G900A using Tapatalk
Rom has nothing to do with it, im on stock kernel, multisystem sets you to permissive, did you read at all?You have a custom rom with a permissive kernel and it still doesn't work? That's interesting.
Rom has nothing to do with it, im on stock kernel, multisystem sets you to permissive, did you read at all?
Sent from my Twi5ted SM-G900A using Tapatalk
It COULD work, just have patience, i'm sure someone will get it working.The bottom line is that it's not gonna work. Doesn't matter which path we take the destination is the same.