V4A Neon Enabled:No,Enabled:NoStatus:abnormal - One (M8) Q&A, Help & Troubleshooting

Hey guys just installed V4a on my stock rooted Lollipop M8 S-ON
I installed V4a,downloaded from official website, installed drivers and disabled LPA and I cant notice any differences. When I check the driver status.
{
"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"
}
I tried changing compatibility and it doesn't work as well.
How do I know if its working or not?

MJ999 said:
Hey guys just installed V4a on my stock rooted Lollipop M8 S-ON
I installed V4a,downloaded from official website, installed drivers and disabled LPA and I cant notice any differences. When I check the driver status.
I tried changing compatibility and it doesn't work as well.
How do I know if its working or not?
Click to expand...
Click to collapse
Is selinux permissive?
The procedure I use is
1. Copy apk to system/priv-app/v4a/(make the folder)
2. Permissions (rwx, rwx, rwx)
3. Reboot, install driver (I haven't disabled lpa)
4. Reboot, and you've got it working!
My selinux is set permissive from the kernel I use (elementalx) if it makes a difference..

MJ999 said:
Hey guys just installed V4a on my stock rooted Lollipop M8 S-ON
I installed V4a,downloaded from official website, installed drivers and disabled LPA and I cant notice any differences. When I check the driver status.
I tried changing compatibility and it doesn't work as well.
How do I know if its working or not?
Click to expand...
Click to collapse
Hi... I got same problem here too... But I succeeded enabling the driver with magisk 14 + viper4android fx modules ( for magisk 14 ) after i'm installing busybox & se Linux changer. After installing viper4android fx modules ( via magisk manager), then I installed viper4android apk ( guitardehero version ) Viollaaa... The driver error is gone!!! even now can run flawlessly in my MINIX neo u1 too... Here the proved...

Related

Xposed Framework (LolliPop)

As I am well aware most of the regulars on these threads know xposed framework has fnally been implanted with ART. Unfortunely, as of right now it's not a simple install an APK, set SU access, go for gold. There have been a **** load of problems going on for a lot of people. Has anyone got xposed to work properly on their devices and how did you go about to doing it ? I already have SELinux set to permissive, but the log from xposed is reading something about modules.list.....
{
"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"
}
jxcorex28 said:
As I am well aware most of the regulars on these threads know xposed framework has fnally been implanted with ART. Unfortunely, as of right now it's not a simple install an APK, set SU access, go for gold. There have been a **** load of problems going on for a lot of people. Has anyone got xposed to work properly on their devices and how did you go about to doing it ? I already have SELinux set to permissive, but the log from xposed is reading something about modules.list.....
Click to expand...
Click to collapse
Working fine for me. I just followed the instructions they posted online. Flash the .zip, install the apk, and then install modules. I'm using a bootmanager, youtube adaway, and Pandora Patcher. I'm running BadBoyz latest Sprint Lollipop ROM.
henderjr said:
Working fine for me. I just followed the instructions they posted online. Flash the .zip, install the apk, and then install modules. I'm using a bootmanager, youtube adaway, and Pandora Patcher. I'm running BadBoyz latest Sprint Lollipop ROM.
Click to expand...
Click to collapse
Same thing here, no problems at all. Few modules don't work but thats because Lollipop.
henderjr said:
Working fine for me. I just followed the instructions they posted online. Flash the .zip, install the apk, and then install modules. I'm using a bootmanager, youtube adaway, and Pandora Patcher. I'm running BadBoyz latest Sprint Lollipop ROM.
Click to expand...
Click to collapse
Wat boot manager u using wen I install it loads then says I don't have closed installed and vloses but I do have installed, I'm using Pandora patcher and YouTube adaway fine
Just bootmanager. Click outside the not installed dialog. I read somewhere it works otherwise. I think it's working but really haven't messed with besides stopping a handful of apps.

Viper audio mod + lollipop

Has anyone been able to get this working? If so, how?
AOSP lollipop, download official V4A LP, flash it. Set kernel to permissive and install drivers.
On Touchwiz however v4a works via same method, but the devices memory killer always kills v4a even if you have it installed or notification turned on unless you somehow set v4a as high priority to not be killed.
I think found a solution for TW Lollipop V4A if someone wants to try the last thing I did to get it working.
Freeze SoundAlive with Titanium Backup. Couldn't find Settings/Sound/effects. After searching and trying everything, the last step nearly had me stumped.
If it makes any difference, I'm still on the stock OTA OB7.
{
"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"
}
If that doesn't do it, I had also installed viper to /system/priv-app in a folder with arm and lib sub folders with the .odex but didn't get a generated .odex.art file in arm folder so I get a quick "Android is updating... Starting apps" on each boot. I'm not sure that Odex is necessary. But since some are saying lollipop oom kills viper quickly, the deodexed version in /system/priv-app folder with lib sub folder may be necessary.
But I believe the permissive kernel is necessary: 3.10.40-N4-Sprint_AELKernel-v1-LP
root @friedrich420 #2
Sun Mar 15 21:34:07 EET 2015 Thanks; haven't got anything setup with it, just got viper going.
How did you get SELINUX into permissive mode? was it the new AEL kernel? I stopped Soundalive and have been using ExtremeBeats. Sounds pretty good. Not like a viper though.
ggee6688 said:
How did you get SELINUX into permissive mode? was it the new AEL kernel? I stopped Soundalive and have been using ExtremeBeats. Sounds pretty good. Not like a viper though.
Click to expand...
Click to collapse
Yes; AEL. I copied the kernel description but didn't post a link because of the requests not to. But there are links in the old/discontinued thread. That's where I got the kernel.
I saw a new AEL kernel out also. Ill have to give that a go when I get sat down. HOpe it works. I think itll fix my Cleanmaster in shutting down startup apps.
Definitely works with permissive set so selinux.
Sent from my SM-N910P using xda-developers.com, powered by appyet.com

Can't Install Viper4Android or Better Battery Stats into Z00AD After ROM Update

Info:
ZE551ML unlocked - WW 2.20.40.150? to WW 2.20.40.174
root - SuperSu Pro 2.67
busybox - v1.24.1 -Stericson
SELinux - set to permissive
As I usually do when there's an update, I edited the full ROM zip for 174 and then flashed with TWRP using @AL_IRAQI's guide here.
Flashed SuperSu afterwards, installed the same busybox I was using before and set my SELinux to permissive.
When I try to install Better Battery Stats as a system app, I get this error, "Failed, try recovery ZIP."
When I try to install the V4A driver, I get this error:
{
"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"
}
These errors lead me to believe that the system partition is set to read-only.
Am I correct in my guess, and if so, how do I set it back to r/w?
Otherwise, how would I go about fixing this?
Hi,
Disable Mount space separation in SuperSU and reboot. This should fix your issues with ViPER4Android and BetterBatteryStats.
Sent from my ASUS_Z00A using XDA Labs
I too faced similar issue. had to remove supersu and install again. Viper and BBS both worked afterwards.
krasCGQ said:
Hi,
Disable Mount space separation in SuperSU and reboot. This should fix your issues with ViPER4Android and BetterBatteryStats.
Sent from my ASUS_Z00A using XDA Labs
Click to expand...
Click to collapse
Thank you for this!
I've been struggling with the issue and it made me question whether I should factory reset my phone.
I don't even know how that option was enabled.
azthemansays said:
Thank you for this!
I've been struggling with the issue and it made me question whether I should factory reset my phone.
I don't even know how that option was enabled.
Click to expand...
Click to collapse
That option is enabled by default, but it's causing some issues with certain apps...
Sent from my ASUS_Z00A using XDA Labs

V4A Driver Won't Stick

I Flashed V4A_2.3.4.0_Enforcing_Lollipop.zip with TWRP on stock, rooted 6.0.1 nexus 5x, with Busybox installed, SuperSU mount namespace unchecked and selinux both permissive and enforcing and can't get driver to stick! I'm Prompted to install after every reboot. App storage perms are on. Any help most appreciated. Thx
I've posted my question in two other threads but none has answered
You need to delete the file "audio_effects.conf" in /root/vendor/etc/ Use a file explorer or something else you can get access to edit root files
Stop with the old stuff, so many things to do to get it working. Just flash latest version by guitardedhero or flash the new ARISE sound mod. Guitardedhero has worked so hard to make these mods super compatible.
Thanks to both of you. Pollie, I am unfamiliar with Guitardedhero. Can you please provide a link?
Hypemanisus, I did as you suggested, and while I am no longer prompted to update the driver upon opening V4A, and in fact the option in settings says ,"Uninstall Driver," driver status is still No, Unsupported an Abnormal across the board. Indeed I am not hearing any enhancement either as I certainly did hear with my Nexus 6 and Galaxy S4.
http://forum.xda-developers.com/android/software/viperaudio-viperatmos-3-8-sq-driver-t3289075 , isntall the universal version , should work .
Thanks Apyah. I will get around to this this weekend and advise
Flashed Dolby Atmos as directed. It is stopping upon opening. Perhaps there is conflict with previous version of V4A, which I removed using a root uninstaller. Advice?
Is there a flashable uninstall zip for the above V4A system app? Concerned some files might have been left behind which are conflicting with guitardedhero. Tried dr ketan fix too with v4a didn't allow driver install either
But then again I really have no idea. Quite frustrated. NEED MY VIPER compulsively!
what did you flash ? don't flash dolby atmos , just flash universal version , it has dolby and viper , just turn off dolby and use viper , don't delete anything .
Perhaps i'm crazy but there's no more link for the Viper|Audio. Only Viper|Atmos and DD.
{
"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"
}
Cannot find Guitarded Hero Universal Audio system app so I installed the latest V4A user app (V2.4.0.1). Removed "audio_effects.conf" from /root/vendor/etc/. Set SelLInux to permissive. Installed Driver. SOFT reboot and it now works. Still upset though because It's a pain to have to setenforce 0 then soft reboot and run phone in permissive every time. Coulda sworn i read somewhere a script to get this to run in enforcing...
no need permissive , i just flash the universal version on my 5X and G2 (5X hard brick now) viper work on both phone in enforcing SElinux .
Try reinstall your rom , clean wipe .
Thx Apayah. Where can I find this universal version you speak of please?
the one i gave to you , or to be simple http://forum.xda-developers.com/attachment.php?attachmentid=3701983&d=1459364213

Magisk problem with xiaomi.eu MIUI 8.5.2.0 Stable

Hi all.
I make clean install of stable 8.5.2.0 from xiaomi.eu and now I have problems with Magisk.
On weekly builds I installed Magisk v12 containing hide fix + xiaomi safetynet fix and everything works file. Root and SafetyNet. But right now, when I Install, Root don't work but safetyNet does.
When I flash Magisk v12 downloaded via Magisk Manager, root works, but safetynet don't.
Any solution?
So right now it looks like:
{
"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"
}
Used files you can find here:
Magisk-v12.0.zip
Magisk12.0_Hide_fixed.zip
MagiskManager-v4.3.3.apk
xiaomi-safetynet-fix-v1.9.1.zip
https://mega.nz/#F!PRAQDJwD!39Zd4yxHanX1lb_gD2YIew
dariusz666 said:
Hi all.
I make clean install of stable 8.5.2.0 from xiaomi.eu and now I have problems with Magisk.
On weekly builds I installed Magisk v12 containing hide fix + xiaomi safetynet fix and everything works file. Root and SafetyNet. But right now, when I Install, Root don't work but safetyNet does.
When I flash Magisk v12 downloaded via Magisk Manager, root works, but safetynet don't.
Any solution?
So right now it looks like:
Used files you can find here:
Magisk-v12.0.zip
Magisk12.0_Hide_fixed.zip
MagiskManager-v4.3.3.apk
xiaomi-safetynet-fix-v1.9.1.zip
https://mega.nz/#F!PRAQDJwD!39Zd4yxHanX1lb_gD2YIew
Click to expand...
Click to collapse
Are you using Xposed? If yes, try removing it.
alediniz said:
Are you using Xposed? If yes, try removing it.
Click to expand...
Click to collapse
No, ofc no. I use magisk on dev/beta releases before and I know I can't have Xposed or SuperSU.
I tried it for a week and safetynet test was always working.
The problem is that, even if locked and with no restriction on battery use, it was randomly loosing root.
I installed Magisk12.0_Hide_fixed and then xiaomi-safetynet-fix from TWRP.
Then I updated the manager from Play Store and reboot.
Any idea?
In the meanwhile I switched back to SuperSu.
BTW I also tried installing systemless SuperSu and then Magisk but root wasn't working at all.
I should try that again after the recent SuperSu updates.

Categories

Resources