Viper keeps either crashing or not loading at all. To make it work i have to reboot my device and even then it doesnt work 100%. Any fixes?
Weird. Seems to be working for me although gives me worse feeling then on Oreo with the same audio profile...[emoji24]
Wysłane z mojego ONEPLUS A6003 przy użyciu Tapatalka
Sometimes the driver doesnt even start and im left with default driver.
xBastek said:
Sometimes the driver doesnt even start and im left with default driver.
Click to expand...
Click to collapse
There's a Magisk module, flash it. It works fine on stock and custom roms.
The Marionette said:
There's a Magisk module, flash it. It works fine on stock and custom roms.
Click to expand...
Click to collapse
I installed magisk add-on " viper4android FX materialized" v.1.7.4 (2.5.0.5) and it's constantly off. I hid the 3 dots menu hit exit, start the app again and the driver is active for around an hour. Next time I listen to music it's off again. That not stable for me.
I'm currently on the latest stock rom but rooted with magisk.
h0LLe said:
I installed magisk add-on " viper4android FX materialized" v.1.7.4 (2.5.0.5) and it's constantly off. I hid the 3 dots menu hit exit, start the app again and the driver is active for around an hour. Next time I listen to music it's off again. That not stable for me.
I'm currently on the latest stock rom but rooted with magisk.
Click to expand...
Click to collapse
Remove the APK from system, reboot and install the one from XDA Labs. Works fine for me.
The Marionette said:
Remove the APK from system, reboot and install the one from XDA Labs. Works fine for me.
Click to expand...
Click to collapse
That indeed worked as promised. Once done today in the morning I tried it several times and always the driver was running during the playback. Thank you a lot!
I was happy and did not know. It was perfect my viper4fx there magisk suggested an update to version 1.7.5 unfortunately I lost the equalizer, it did not work anymore. I installed busybox, drivers, dozens of times, backed up the versions, nothing. Damn update, I think I'll have to format. I'm sad.
Related
Hey,
I've got a rooted Nexus which won't start anymore. It has been rooted for months and everything worked fine so far. I've installed a lot of root apps like the Xposed Framework, Titanium Backup and App Ops. The last Rom I had on it was the Stock Android 4.4.3. After running without any problems and me making no modifications, suddenly it stopped working. First, the System UI kept crashing after max. 1 second of running. Now, it won't even get past the boot screen. I think, it is a problem with a Xposed Framework module of which I have a lot installed (I remember XBlast, GravityBox and Wanam but there were more (propably around 10). Is there a way to disable the Xposed modules? Another problem is, that I don't know, if I accidently updated to KitKat 4.4.4 what could've caused those problems.
I hope, you can help me.
Stefan
Stefan Baumann said:
Hey,
I've got a rooted Nexus which won't start anymore. It has been rooted for months and everything worked fine so far. I've installed a lot of root apps like the Xposed Framework, Titanium Backup and App Ops. The last Rom I had on it was the Stock Android 4.4.3. After running without any problems and me making no modifications, suddenly it stopped working. First, the System UI kept crashing after max. 1 second of running. Now, it won't even get past the boot screen. I think, it is a problem with a Xposed Framework module of which I have a lot installed (I remember XBlast, GravityBox and Wanam but there were more (propably around 10). Is there a way to disable the Xposed modules? Another problem is, that I don't know, if I accidently updated to KitKat 4.4.4 what could've caused those problems.
I hope, you can help me.
Stefan
Click to expand...
Click to collapse
I think it's xblast.
Just flash the disabler zip via recovery. Its attached in the Xposed thread:
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053
rootSU said:
I think it's xblast.
Just flash the disabler zip via recovery. Its attached in the Xposed thread:
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053
Click to expand...
Click to collapse
You can repetitively press the volume keys during boot and eventually it'll vibrate every time you do. What it does is add a folder "disabled" in Xposed's data and disables it. No need to push and flash lol. Was implemented a while ago as an easier alternative
Lethargy said:
You can repetitively press the volume keys during boot and eventually it'll vibrate every time you do. What it does is add a folder "disabled" in Xposed's data and disables it. No need to push and flash lol. Was implemented a while ago as an easier alternative
Click to expand...
Click to collapse
Cool. I haven't seen this anywhere
rootSU said:
Cool. I haven't seen this anywhere
Click to expand...
Click to collapse
I think it was in the Q&A thread for Xposed lol
Since nobody knows how to use adb to push
Lethargy said:
You can repetitively press the volume keys during boot and eventually it'll vibrate every time you do. What it does is add a folder "disabled" in Xposed's data and disables it. No need to push and flash lol. Was implemented a while ago as an easier alternative
Click to expand...
Click to collapse
I tried that several times now and it doesn't seem to work. During boot, i repetitively pressed the volume keys as you told me until it vibrated a bit. Then, the boot took a lot longer than usual but it didn't change anything - the com.android.systemui process is still crashing.
Stefan Baumann said:
I tried that several times now and it doesn't seem to work. During boot, i repetitively pressed the volume keys as you told me until it vibrated a bit. Then, the boot took a lot longer than usual but it didn't change anything - the com.android.systemui process is still crashing.
Click to expand...
Click to collapse
Try what @rootSU said then. If that doesn't work either then its not because of Xposed.
Lethargy said:
Try what @rootSU said then. If that doesn't work either then its not because of Xposed.
Click to expand...
Click to collapse
Ok, it seems I did the button pressing the wrong way. After looking at the thread posted by rootSU and especially at this post I was able to do it (I pressed both volume buttons repetitively instead of just one). So, now I was able to boot the Nexus - what next?
Disable all your modules and re-enable Xposed with the instructions of that post. Reboot to see if its Xposed itself causing the issue. If it boots up then enable them one by one and reboot each time. One will be the culprit.
Lethargy said:
Disable all your modules and re-enable Xposed with the instructions of that post. Reboot to see if its Xposed itself causing the issue. If it boots up then enable them one by one and reboot each time. One will be the culprit.
Click to expand...
Click to collapse
Ok, I disabled all of them and it booted now . I saw, that there are a lot of updates for my available (xposed installer, app settings, burnt toast, customshare, gravitybox, holo themer, wanam, xblast, xposed additions and youtube adaway). Should I install those before reactivating the modules?
Up to you
Lethargy said:
Up to you
Click to expand...
Click to collapse
Ok, I updated all the modules, enabled them one by one (with a restart after every one) and now, everything is working again. Thank you very much for your help :good:.
Does it occur only for me???
EDIT:
Actually, using any 3rd party equalizer in stock Sony Nougat roms results in high battery drain!! (by Music app & system wavelocks / audiosever)
You can use any soundmod (made of audio libs, such as Diva soundmod) without draining as long as you use the native Sony equalizer (soundenhancement).
So, sadly, v4a is now a no go for me...
It seems that the culprit is v4a...
It was not draining so much with MM
I could not get any v4a version working in nougat, as they all get installed fine but no sound when its processing. Can you share me the working version you are using ?
Thanks
GryTEcHoG said:
I could not get any v4a version working in nougat, as they all get installed fine but no sound when its processing. Can you share me the working version you are using ?
Thanks
Click to expand...
Click to collapse
It works fine with the Magisk module ViperFX
nreuge said:
It works fine with the Magisk module ViperFX
Click to expand...
Click to collapse
nreuge said:
It works fine with the Magisk module ViperFX
Click to expand...
Click to collapse
Thanks. Will try.
Off topic: I have some problems with camera app options as I no longer can see 20Mp option in Superior mode and like so few more options are missing in other modes. I dont know what happened, and I tried to clear cache/data but problem persists. Only way I can get it is flash firmware, but after few days then its gone. Do you have any idea ?
Thanks
GryTEcHoG said:
Thanks. Will try.
Off topic: I have some problems with camera app options as I no longer can see 20Mp option in Superior mode and like so few more options are missing in other modes. I dont know what happened, and I tried to clear cache/data but problem persists. Only way I can get it is flash firmware, but after few days then its gone. Do you have any idea ?
Thanks
Click to expand...
Click to collapse
No idea...
Draining issue origin solved: see 1st post
I've had no problem installing just the V4A apk manually (without deleting any libs!). If you delete libs sound will pop all the time or cause bootloop. Don't forget to turn on compatibility mode.
Hello all. I'll try to explain my issue with as much detail and hopefully somebody can help me.
Anyways I picked this phone up on sale on amazon and I have already unlocked the bootloader and am successfully rooted. Now I want to use Xposed. I have been trying to get it to work for 2 days now and I am fed up.
I downloaded the correct Xposed installer(SDK 24 v88.2) and it will somewhat work but then after a reboot It says it's installed but not active and it tells me to check the logs of which are blank. I am rooted the supersu way and have twrp installed.
I've read about some script I can put in the init.d folder or something like that but I cannot seem to get it to work.
I am on emui 5.0 with android 7.0.
Can someone please for the life of me help me get this to work?
I'm simply trying to use a module for my Snapchat called snaptools.
I know it's a lot to ask but can someone please help with a tutorial or a fix/instructions?
Unluckily I'm facing the same issue on my phone without having found a solution yet, both by official or systemless Xposed versions, the result is always the same as yours; Xposed framework looks installed but deactivated after some reboots, and it stays like that until i completely remove it and reinstall it again. Then, after other 2 reboots or something like that, it gets deactivated again and again. I already tried to look for a fix on official systemless Xposed thread as you can see here from an old post of mine https://forum.xda-developers.com/showpost.php?p=74439953&postcount=5740 but even trying other Xposed Installer versions (official, topjohnwu's, dvdandroid's one...) or without using Greenify4Magisk module, the issue persists. I thought I was the only one facing this lol. I'm rooted with Magisk, so the issue must be something else than the SU manager used. Can i ask you if you have Greenify installed on your device? I have to tighten the circle of possible causes of this, because it's getting me mad.
RedSkull23 said:
Unluckily I'm facing the same issue on my phone without having found a solution yet, both by official or systemless Xposed versions, the result is always the same as yours; Xposed framework looks installed but deactivated after some reboots, and it stays like that until i completely remove it and reinstall it again. Then, after other 2 reboots or something like that, it gets deactivated again and again. I already tried to look for a fix on official systemless Xposed thread as you can see here from an old post of mine https://forum.xda-developers.com/showpost.php?p=74439953&postcount=5740 but even trying other Xposed Installer versions (official, topjohnwu's, dvdandroid's one...) or without using Greenify4Magisk module, the issue persists. I thought I was the only one facing this lol. I'm rooted with Magisk, so the issue must be something else than the SU manager used. Can i ask you if you have Greenify installed on your device? I have to tighten the circle of possible causes of this, because it's getting me mad.
Click to expand...
Click to collapse
I do not have greenify installed unfortunately. I literally got this phone 2 days ago and I've never had this issue before.
I just uninstalled the SuperSU version and Installed the magisk version for root and then installed Xposed through the magisk manager and installed the modified Xposed installer apk that can see the systemless install. Xposed has survived a couple reboots and my modules are working but I fear that it will stop working as you stated before randomly. Have you tried it my way?
Flash magisk v14 through TWRP and then install Xposed SDK 24 systemless through the magisk manager. And then installed the modified APK for Xposed installer. It's at least made it further than the normal Xposed install.
Edit: Since I've posted this I have survived 2 more restarts. I feel like I'm playing Russian roulette Everytime I restart it but so far so good.
patrick8996 said:
Flash magisk v14 through TWRP and then install Xposed SDK 24 systemless through the magisk manager. And then installed the modified APK for Xposed installer. It's at least made it further than the normal Xposed install.
Edit: Since I've posted this I have survived 2 more restarts. I feel like I'm playing Russian roulette Everytime I restart it but so far so good.
Click to expand...
Click to collapse
Ok so greenify isn't a cause of this issue... yes i tried it already, read my post above... Both by official by rovo89, and systemless by topjohnwu (with related installer obviously) the issue persists. It works, like the other one, but after some reboots (i reboot my phone once a day, at least) i find it deactivated. Yeah you said well, it's a Russian roulette ahahah i tried every version of Xposed practically...
RedSkull23 said:
Ok so greenify isn't a cause of this issue... yes i tried it already, read my post above... Both by official by rovo89, and systemless by topjohnwu (with related installer obviously) the issue persists. It works, like the other one, but after some reboots (i reboot my phone once a day, at least) i find it deactivated. Yeah you said well, it's a Russian roulette ahahah i tried every version of Xposed practically...
Click to expand...
Click to collapse
Hmm I'm still active but I haven't restarted since I posted. I'm wondering why there isn't a more detailed thread regarding this as it seems a lot of people use this phone.
Maybe you can try fresh with magisk and the modified Xposed installer for straight systemless. I've had a hell of a lot more luck this way than I have through the regular install. It's survived 5 reboots so far. Have you tried just a soft reboot inside the Xposed installer? I mean I know it's not a full restart but it may maintain Xposed and keep it active.
Maybe because only a limited set of people are facing this. And maybe only some devices suffer this. I tried both, fresh installations of normal Xposed / systemless Xposed, both didn't survived after 2 or 3 normal reboots. Yes I always rebooted by Xposed Installer when it was installed, even because i can preserve on/off button the longest i can this way, but sometimes a soft reboot isn't sufficient to apply some modifications, so i rarely used them. I daily rebooted with normal reboots. I'll try when new versions will be available at this point, i tried actual builds for 2 weeks encountering always this error so I'm not motivated on trying them again
Hey @patrick8996 did you tried latest systemless Xposed, V89? It surely works much better than previous one, V88.2, it has already survived 5 reboots while activating various modules compatibility is definitely increased with this update, I hope the issue won't represent in future
RedSkull23 said:
Hey @patrick8996 did you tried latest systemless Xposed, V89? It surely works much better than previous one, V88.2, it has already survived 5 reboots while activating various modules compatibility is definitely increased with this update, I hope the issue won't represent in future
Click to expand...
Click to collapse
I just installed it last night and so far so good.
My lasts posts regarding v88.2 were proved incorrect because once I rebooted one more time it went back to not working. But this new update to v89 seems to be working. Hopefully all goes well.
patrick8996 said:
I just installed it last night and so far so good.
My lasts posts regarding v88.2 were proved incorrect because once I rebooted one more time it went back to not working. But this new update to v89 seems to be working. Hopefully all goes well.
Click to expand...
Click to collapse
Yeah this build survives always reboots, even after recovery boots... I'd declare this issue solved :victory:
RedSkull23 said:
Yeah this build survives always reboots, even after recovery boots... I'd declare this issue solved :victory:
Click to expand...
Click to collapse
I've had a weird issue that my module's randomly stopped working. I had to disable them all in the Xposed app and restart and then enable them and restart again. Not sure if you've had this issue. But it's not that big of an issue because as long as Xposed stays active after a reboot it's a simple fix.
patrick8996 said:
I've had a weird issue that my module's randomly stopped working. I had to disable them all in the Xposed app and restart and then enable them and restart again. Not sure if you've had this issue. But it's not that big of an issue because as long as Xposed stays active after a reboot it's a simple fix.
Click to expand...
Click to collapse
Never faced this. The framework keeps staying active actually
RedSkull23 said:
Never faced this. The framework keeps staying active actually
Click to expand...
Click to collapse
My Xposed stays active it's just my modules randomly stop working inside Xposed. So I have to disable all my modules reboot and then reenable them and reboot again.
I had issues last night with updating magisk. When I updated to v15 it took all my sound away on my device. I had to uninstall it and reflash v14 and everything went back to normal.
patrick8996 said:
My Xposed stays active it's just my modules randomly stop working inside Xposed. So I have to disable all my modules reboot and then reenable them and reboot again.
I had issues last night with updating magisk. When I updated to v15 it took all my sound away on my device. I had to uninstall it and reflash v14 and everything went back to normal.
Click to expand...
Click to collapse
V15.1 should fix everything. V15.0 was messing up thousands of phones
RedSkull23 said:
V15.1 should fix everything. V15.0 was messing up thousands of phones
Click to expand...
Click to collapse
Ya I installed 15.1 and no longer have any issues. I'm happy all has been working for this long
Sent from my BLN-L24 using Tapatalk
Hey all,
Sorry if this has been covered elsewhere - I've searched a fair bit but found no definitive explanation..
Anyways I've installed viper4android 2.5.0.5 via magisk and it works initially. But soon enough it stops (processing=no)
I think I may need to flash it via twrp but I'm not sure ?
Has anyone got viper4android working on OP6 OOS 5.1.8? If so how?
Thanks!
Viper4Android works very good for me. Sometimes I have to reestablish a Bluetooth connection again as at the first connection no processing is active but in general viper works good.
I use the original Magisk module in the current version 1.6.9 and in addition "Audio Compatibility Patch"-Module in version 1.4.4.
I think this is all you need.
Just reboot.
hurray said:
Viper4Android works very good for me. Sometimes I have to reestablish a Bluetooth connection again as at the first connection no processing is active but in general viper works good.
I use the original Magisk module in the current version 1.6.9 and in addition "Audio Compatibility Patch"-Module in version 1.4.4.
I think this is all you need.
Click to expand...
Click to collapse
Thanks! I've installed this module and reinstalled viper4android afterwards. It's working again, but it always does after reinstalling. Hopefully it continues too. I'll update you guys!
I think the order of installation is important:
first viper and afterwards the audio compatibility module.
If your flash viper two times in a row it deinstalls itself (if I remember it correctly).
But I think you get it.
hurray said:
I think the order of installation is important:
first viper and afterwards the audio compatibility module.
If your flash viper two times in a row it deinstalls itself (if I remember it correctly).
But I think you get it.
Click to expand...
Click to collapse
Viper (as magisk module) works flawlessly also without the audio compatibility module for me; on spotify, soundcloud, power amp. Don´t know exactly, what the module is needed for. If "processing" says "no", clearing app data (and maybe reboot) helps - in worst case reinstalling the viper module.
Flying Fox said:
Viper (as magisk module) works flawlessly also without the audio compatibility module for me; on spotify, soundcloud, power amp. Don´t know exactly, what the module is needed for. If "processing" says "no", clearing app data (and maybe reboot) helps - in worst case reinstalling the viper module.
Click to expand...
Click to collapse
Which viper version and options are you using in magisk?
I've tried audio compatibility module but no help there. I turned on fx compatible mode in viper and that gets it to work and stay working!
However it silences my alarms. Which isn't ideal ?
debatingrooster said:
Thanks! I've installed this module and reinstalled viper4android afterwards. It's working again, but it always does after reinstalling. Hopefully it continues too. I'll update you guys!
Click to expand...
Click to collapse
Glad it worked for you if you find any issues in future please try it by turning off the Audio Tuner in Sounds & Vibration setting.
KrabKoyal said:
Glad it worked for you if you find any issues in future please try it by turning off the Audio Tuner in Sounds & Vibration setting.
Click to expand...
Click to collapse
It's stopped working again unfortunately. I might try flashing it in TWRP instead and see if that fixes it...
I am on 5.1.8 with viper I am running the no limits rom patch. No problems with viper on speaker and Bluetooth m
bassbounce said:
I am on 5.1.8 with viper I am running the no limits rom patch. No problems with viper on speaker and Bluetooth m
Click to expand...
Click to collapse
I suppose a custom rom is one way to solve it. I'd prefer OOS but...
Can anyone who's managed to get it working on stock OOS share with me the steps they took?
Hey man - I have it going on stock 5.1.8, I had problems with one of the modules in magisk, am using this one now after removing the old one - works well.
I am on OOS5.18 and used the version "Viper4Android FC Magisk V15", and I flashed it via TWRP.
But the "Proccesing" mode switches to "Off" after a while (5-10 min.). It is not consistent, you have to reboot, which makes no sense for me to reboot 10 times per day. There must be a different way to install it.....?????!!!!
Vivasanti said:
Hey man - I have it going on stock 5.1.8, I had problems with one of the modules in magisk, am using this one now after removing the old one - works well.
Click to expand...
Click to collapse
Thanks for the suggestion - still same problem as @mlara.particular unfortunately
mlara.particular said:
... the "Proccesing" mode switches to "Off" after a while (5-10 min.). It is not consistent...
Click to expand...
Click to collapse
This is weird... I don't understand why it would work for some people and not others...
I've been using the v4a material version from magisk, and it works great. I had to install the audio compatibility patch along with the audio modification library in order to get certain streaming apps to work correctly. You need to install the audio modification library if you install v4a and the audio compatibility patch.
debatingrooster said:
I suppose a custom rom is one way to solve it. I'd prefer OOS but...
Can anyone who's managed to get it working on stock OOS share with me the steps they took?
Click to expand...
Click to collapse
XXX no limits is no custom rom .. just a module in magisk and viper works great.
sakerhetz said:
XXX no limits is no custom rom .. just a module in magisk and viper works great.
Click to expand...
Click to collapse
I've xXx installed too and viper won't work for me. Starts ok but stopped processing and won't start again.
Sent from my ONEPLUS A6003 using Tapatalk
mossief1965 said:
I've xXx installed too and viper won't work for me. Starts ok but stopped processing and won't start again.
Click to expand...
Click to collapse
Experiencing the exact same issues here. Feel like I've tried everything, and now it wont even work after reboot :crying:
@Siggi and mossief.... you have installed magisk ???
sakerhetz said:
@Siggi and mossief.... you have installed magisk ???
Click to expand...
Click to collapse
Yes, of course.
Sent from my ONEPLUS A6003 using Tapatalk
going insane with this. finally got the new Q beta booting. when i install magisk after booting i get immediate system ui crashes and i'm not sure why. normally i would try clearing data but it seems like you can't do this in Q twrp? not sure what the best thing to do is. any ideas?
Are you using 19.3 or 19.4?
coach0512 said:
Are you using 19.3 or 19.4?
Click to expand...
Click to collapse
figured it out, needed 19.4 and to uninstall swift. doesn't seem like swift installer works and if it gets launched everything gets screwed up.
ok google and youtube vanced not working either. damn