Related
/////
THIS GUIDE WAS FROM THE NOVEMBER SECURITY PATCH ON NOUGAT!!! DO NOT DO THIS IF YOU ARE ON OREO CAUSE YOU WILL LOSE ALL SOUND!
IF YOU WOULD LIKE TO USE VIPER ON OREO/PIE DEVICES. PLEASE USE THE MAGISK MODULE AND/OR FIND A BETTER GUIDE WITH A COMPATIBLE ZIP
//////
Okay I have confirmed that sound mods work on the Moto z2 force with no issues whatsoever many probably know that
How to Install:
1.
make sure you have root and TWRP installed on your Moto Z2 force
2.
download this version of A.R.I.S.E.
https://androidfilehost.com/?fid=457095661767141554
3.
Place the zip file in the Internal storage of your device (so its easy to find)
4.
Boot into TWRP recovery and click install
5.
Find the file you put in your internal storage named;
ARISE+Deuteronomy+2.94+Modular+AROMA+Installer.zip
And then swipe to install
6
An install wizard should appear and assuming that you haven't used this before select easy mode on the wizard and make sure you have it set to "install core engine then modules" and spam the hell out of the next button besides those 2 things
7.
TWRP screen should appear and you should boot into your device like normal
8.
ENJOY
SOME NOTES:
A.R.I.S.E AM3D DOES NOT WORK BUT OTHER THAN THAT EVERYTHING ELSE IS FINE
Update: DO NOT ATTEMPT TO INSTALL MAGNUM OPUS IT WILL FAIL
!!!!DISCLAIMER!!!!!
-I AM NOT RESPONSIBLE FOR A INCREASE IN GAS PRICES GETTING CHEATED ON BY YOUR WIFE OR A BRICKED DEVICE
Man.. I was going to try ARISE, but with all the concerns that I couldn't restore a nandroid because of data partition encryption, I just said screw it and I installed the v4a 2.3.4 module right from Magisk, and it works great with both USB Type-C to 3.5mm and Bluetooth.
I don't know if anyone's noticed or not, but Oreo has an entire section on Bluetooth audio protocol under the development options. Things like sample rate, bit rate, etc etc. I do know that v4a works with all protocols (SBC, AAC, aptX, aptX HD and LDAC), but if you up the sample rate to 96khz, it will NOT process. I usually use 48khz and it sounds great.
I installed arise and lost all audio on device . I don't know if it's a setting or something in aroma I should not have added or if it's viper settings I messed with .
I need to uninstall this how do I
Or how do I get sound back this is weird
joesee said:
Man.. I was going to try ARISE, but with all the concerns that I couldn't restore a nandroid because of data partition encryption, I just said screw it and I installed the v4a 2.3.4 module right from Magisk, and it works great with both USB Type-C to 3.5mm and Bluetooth.
Are you on Oreo 8.0 running V4A? Thanks!
Click to expand...
Click to collapse
climbhigh77 said:
Are you on Oreo 8.0 running V4A? Thanks!
Click to expand...
Click to collapse
Yes sir, I am. Since I got it working, I haven't touched anything in fear that it'll stop working. I haven't even made a nandroid. Twrp isn't installed, I just booted in it from adb.
Right on! I was also advised not to install TWRP. I flashed it and it seems to be working so far. Having other issues though like my camera and flash (flashlight) don't work now since installing magisk or the v4a which one I'm not sure but I assume magisk.
3/12/18 Update: camera and Flash are working properly now after a wipe Dalvik, cache and reboot.
Is anyone else having issues with viper4android working intermittently on Oreo? Sometimes it works but mostly it doesn't and I have no way to control it, toggling the switches does nothing and it doesn't matter if I reboot or not. It does work sometimes so I know the drivers are installed, and I've tried a fresh install a few times using the 2.3.4 version and the newest 5.0 version which produces the same result.
Is there a setting in magisk or Viper that I need to apply to to get it working seamlessly? I have systemless hosts check-in magisk already for ad blocking. There's got to be something I'm missing here. Any help is greatly appreciated thanks!
I was having this situation, the I disabled the music FX and it's gone for now
Flashlight stops because of selinux
Dolby Atmos for oreo works fine without any problems. You just have to find the working version in the last few pages of the mod thread.
Was able to get the latest ARISE, plus V4A, and Dolby ATMOS Oreo from guitardedhero working. I'm using SuperSU as I'm not a fan of Magisk. Flashed the latest ARISE, including the V4A 2.5.0.5. Crap, I made sure V4A opened and checked that the drivers were installed. But I may have flashed the ViPER4Android_FX_v2505_A7.x_Nougat_IO_test_fix.apk over the ARISE loaded v4a apk....? Try to see if the loaded apk works first. If not, flash Nougat_IO_test_fix.apk over: ViPER4Android_FX_v2505.zip Anyway, use this to set permissive: The.SELinux.Switch.ver.6.0.3.build.603.apk. Reboot. ARISE libs will be there and V4A should work. Sometimes you have to turn off the main power button for the V4A mod, go up to the corner button and exit. Clear out anything in recents. Then open V4A back up, and enable the power button. If music is playing, you will hear the change.
Ok.....Dolby. Go HERE and download the normal zip. Thank the dude, he's done a lot for us audiophiles. Flash it. Reboot. Apps will be there, and will likely forceclose. You have to extract the dolby zip and copy the libs from the dolby/lib and dolby/lib/soundfx files and paste them in the related folders in root /system/vendor and system/vendor/soundfx. You need to set the permissions to rw-r-r (644). Now save/reboot. Apps should work. I'm betting other libs/files weren't installed either, but just those got Atmos working, working well. Still looking through things and will verify later what else wasn't placed.:good:
Quick Question, I have used ARISE and Viper before and really like them but this is a Software Mod. I would just like to clarify that this Software Mod works on the actual Hardware Mod and if it does, does this Software Mod work on the Hardware Mod using a Custom ROM or Kernal? Can anyone confirm that yet?
androidddaaron said:
I installed arise and lost all audio on device . I don't know if it's a setting or something in aroma I should not have added or if it's viper settings I messed with .
I need to uninstall this how do I
Or how do I get sound back this is weird
Click to expand...
Click to collapse
Sorry about this... You may have to back up your internal then flash back to stock. This guide was from when our device was still on nougat. For Oreo I need you to install the module from MAGISK or find the magnum opus zip
AUDIOPHILES GET IN HERE!
One of the many reasons why rooting is still Popular..
NOTE(Old):
Your phone's Dolby Atmos would not be functional (but its dual speakers still function well) in other words, the Dolby Atmos in the settings would be turned "Off" only.
Note(New): I had an error installing the driver but itndoesn cause any problems, I backed up the audio config file. Deleted, restarted and installed the driver from the app. It was successful. I tried bringing back a copy of audio conf. And jollah I made the built in dolby atmos system of Nokia 6 work with the Viper4Androi and I swear, the phone is like a mini stereo with awesome quality. Just a few tweaks and you're great.
For those who doesn't know what's ViPER4Android:
As we know that the vipe4android is one of the best android voice enhancer app. Not just voice/music enhancer but the best thing you can do by viper4android is, improve music quality. This app works on same principal and applicable to both kinds of music as well as video, and also works to games, almost every app on your phone!
How to Install ViPER4Android on Nougat
Make sure you’re rooted and have TWRP recovery installed on your device.
If not yet, follow Hikari Calyx's guide for rooting your Nokia 6 https://forum.xda-developers.com/nokia-6/how-to/guide-how-to-flash-custom-recovery-root-t3702354
Just tested it on my Nokia 6 TA-1021 (March 30 +8:00)
1. Download the ViPER4Android_2.5.0.5_guitardedhero.zip file from the download button above and transfer it your device’ internal storage.
2. Boot into TWRP recovery and install/flash the ViPER4Android_2.5.0.5_guitardedhero.zip file to your device.
Reboot phone. (If you can't go to recovery mode just like me, use "#Rashr" app from playstore it has a function that can reboot you to recovery mode)
3. Download/install a root file explorer app (we recommend ES File Explorer/Classic root browser).
└ On ES File Explorer, swipe-in from left and turn on Root explorer feature. And don’t forget to grant root access when asked.
4. Now using your root explorer app, go to /vendor/etc/ directory on the device and rename audio_effects.conf to audio_effects.conf.bak.
5. Open ViPER4Android FX app on your phone (it installed when you flashed the zip file in step 3 above).
You’ll get a notification to install V4A driver. Select YES.
It’ll take some time to install V4A driver, and while doing so it might even look like it’s stuck but you don’t worry. It’s doing its job and will finish soon.
└ If Android gives an error that the app has stuck/stopped. Be sure to select the wait option, don’t force close it.
Once you get the Driver installed message on screen, reboot your device.
http://downloadmirror.co/2zYA/ViPER4Android_2.5.0.5_guitardedhero.zip
Is there any audiophiles here?
I would like to know if anyone has safely installed Viper4android to Nokia6
And if it's causing any problems with its dolby atmos system..
I wanted to know because tbh, the HMD global didn't make efforts for a nokia music app and it comes without a preinstalled equalizer. While Samsung even has their SoundAssistant and SoundAlive equalizer options. 3rd party app sucks. So this is the best option I only see, the mother of all equalizers for music.
I use ARISE Sound mod with VIPER4ARISE and it is working great. Only Dolby Atmos will not work with that, if you install the arise Dolby you will get a bootloop.
Wait, I don't understand... What's the difference between Vioer4android and Viper4ARISE and Arise itself...
And which of those causes bootloop, which ones are safe to install through twrp?
frince9000 said:
Wait, I don't understand... What's the difference between Vioer4android and Viper4ARISE and Arise itself...
And which of those causes bootloop, which ones are safe to install through twrp?
Click to expand...
Click to collapse
Viper4android is the original audio mod you were asking about. Some guys from created a collection of different mods and apps and made them work as best as they can - this is ARISE. They included Viper4android and modified the configs so it fits into arise - this is VIPER4ARISE. The main difference for the Nougat user is that the installation is simpler. You just place a text file on the internal storage which tells this twrp zip what to do and Flash through twrp - done. This means that you can easily install a variety of sound software with only minimal problems.
If you install arise however, the pre-installed Dolby from Nokia breaks. If you install Dolby Atmos from arise, you will end up with a bootloop.
I hope this was understandable.
How do I install Viper4arise.. I can't seem to be able to find links in google. Also, the files :/ if it doesn't bother you that is...
Also, have you tried installing Viper4android? Does it also cause the dolby atmos (speakers) of nokia 6 to malfunction? Or any side effects it might cause? I want the dolby atmos speaker function to remain while having installed Viper4android.
frince9000 said:
Also, have you tried installing Viper4android? Does it also cause the dolby atmos (speakers) of nokia 6 to malfunction? Or any side effects it might cause? I want the dolby atmos speaker function to remain while having installed Viper4android.
Click to expand...
Click to collapse
The speakers remain perfectly functional. But DOLBY ATMOS WILL NOT WORK after installing viper through arise at least. I have never installed stock viper so I cannot provide information about this.
Updated thread*
I am an audiophile and I make it a point to use audio mods whenever possible. That being said, the audio mods that I've tried and worked amazingly well are Viper4Android and Ainur Sauron, but you will also need Audio Compatibility Patch and Audio Modification Library to make things work so seamlessly.
That being said, I get to see a lot of people complaining about Viper4Android being too buggy in that after every restart, it asks for the driver to be installed again, etc. Well, I have clean flashed/dirty flashed plenty of ROMs now so I can honestly say that my method works.
So, what is my method for installing all of the audio mods I mentioned earlier? Well here are the steps:
1. Install Busybox for Android (in Magisk Repo)
2. Install Audio Compatibility Patch. It now comes with a multi-option installer, so you want to Select NO to the first option then choose Vol + (Patch New Logic). Select NO to the second option and then use Vol - (remove Volume Listener Library). This is done so that your audio won't crackle. You can skip USB Dac if you're not using it and you should choose NO at the last option (library workaround).
3. After Installing ACP with the chosen options, proceed to install Ainur Sauron.
4. Once that is done, install Audio Modification Library. After AML, DO NOT REBOOT YET.
5. Download the Viper4Android 2.7.1 APK here: https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx . I find this to be the best iteration of the module since it is not buggy at all. Once that is installed, run the application and it will prompt you to install drivers for the first time, choose OK and then allow it to reboot. (Note: after installing this, a Magisk Module will be created automatically)
At this point, all of the audio mods should work in unison. Do not toggle anything else in Viper4Android but the main interface. This means that do not go to the settings and toggle anything. Just configure the audio options as per your liking.
6. Currently, the setup will bork BT audio which means that there is no sound that is going to come off of your BT speakers or headphones. What you need to do to fix this is as follows:
a. Rename "audio_policy_configuration.xml" in "/sbin/.magisk/img/aml/system/vendor/etc/audio" to "audio_policy_configuration.xml.bak".
b. Copy the audio policy configuration xml file from "/sbin/.magisk/img/aml/system/etc" to "/sbin/.magisk/img/aml/system/vendor/etc/audio".
c. Restart the device.
Additional Notes
a. When dirty flashing your custom ROM, allow the modules to recoup itself. In other words, do not touch anything until everything is back to normal (or after 5 minutes from dirty flashing).
b. If you happen to uninstall Ainur Sauron (or Narsil), I find that it usually uninstalls viper4android as well. If that is the case, uninstall Sauron and then click the viper4android app from the drawer and allow it to install drivers again.
c. In some devices, the BT workaround is no longer needed. However, I find that for the Pocophone, the workaround is still required. I guess you just have to test it for yourself if it works right off the bat or not.
d. Audio compatibility patch (remove patch logic) actually enhances the volume and the sound quality of the Poco F1. I cannot test this on other devices since I do not have another phone, but you can try and see if it works for you. (thanks to @Jonas G. Morsch for this).
e. If you are going to try Ainur Narsil, I suggest that you do not install viper4android anymore since it provides a great listening experience right off the bat. You can still install v4a, though if you really want it (The same procedure applies).
f. If you are using a custom ROM that has a built-in "AudioFX" app, you need to freeze it using Titanium Backup or similar apps for Viper4android to work. Thanks to @mikedavo for this tip.
g. If, after following all of the above instructions, and you still experience random driver issues or bugs, I suggest that you do a clean installation of your ROM and do the entire steps again. If it still presents the same error, I suggest that you hop on the Viper4android telegram channel to address your concern so that the dev can fix it.
h. Attached below is a profile converter, so if you're using the old version of Viper4android, you can use the attached file to convert all of your profiles to supported presets.
That's about it! If you have questions, feel free to drop them below. Happy listening!
man just what i needed. thank you very much. will try it later. :good:
Point 6 should be fixed. Possible a failure in Poco firmware or something. Use latest AML from Magisk repo. Also install all modules via magisk manager by now. Seems there is an issue and we are working in it.
Also I would replace Viper with JamesDSP.
JamesDSP future is bright and expect a tone of new **** in future. ?
Work as a charm in MIUI latest... But Bluetooth is working without step 6
Sent from my POCOPHONE F1 using Tapatalk
Hmm, I just make sure to disable and freeze any inbuilt audio equaliser or fx from custom roms before installing viper and have never had a problem with vipers drivers installing or instability in viper. I also, after installing viper, activate enhanced sound at the bottom of the sound menu in settings and choose my headphones in the dropdpwn, mine are mi inear pro. If I happen to forget to do this, I'll get the drivers need installing message from viper.
Use jamesDSP. Better ****. Has even 24-bit support. Viper just 16-bit. Also our viper guys teamed up with James. So expect some new **** soon.
it doesn't work for me at all, viper keeps asking to install driver and reboots the phone.. again and again
efakkawy98 said:
it doesn't work for me at all, viper keeps asking to install driver and reboots the phone.. again and again
Click to expand...
Click to collapse
Same here, i gave up after the tenth try
efakkawy98 said:
it doesn't work for me at all, viper keeps asking to install driver and reboots the phone.. again and again
Click to expand...
Click to collapse
Edit:- This worked perfectly for me even in the Secondary ROM with the following changes. V4A 2.7.0 instead of Latest 2.7.1 probably because I'm using Magisk 18.1 and V4A kept on asking to install driver even after reboot so I had renamed the MusicFX.apk in the System to MusicFX.apk.bak.
@BenParz Thank you very much for the guide.
This trick doesn't work with MultiROM for sure.
Will viper work with a bitrate of over 48k? My headphones us 96k which doesnt work with the buggy v4a i use, but its the only version of v4a that actually works at all for me (will try your way of installing later)
SVR said:
This trick doesn't work with MultiROM for sure.
Click to expand...
Click to collapse
I'm not using MultiROM. I'm on PE latest build
I've created a monster hehe. Ainur Sauron also installed
BenParz, i can't thank you enough for this! the choppy audio after installing Viper was making me crazy.
I'm running Lineage OS 05/18/2019 + nano gaaps
After mess around with this modules i got other way:
1 . Install Audio Compatibility Patch. It now comes with a multi-option installer, so you want to Select NO to the first option then choose Vol + (Patch New Logic). Select NO to the second option and then use Vol - (remove Volume Listener Library). This is done so that your audio won't crackle. You can skip USB Dac if you're not using it and you should choose NO at the last option (library workaround).
2. Download and install Viper4Android 2.7.1 Magisk Module here: https://zackptg5.com/downloads/v4afx_v2.7.1.0.zip .
More info : https://forum.xda-developers.com/android/apps-games/app-viper4android-fx-2-6-0-0-t3774651
3. Fix BT:
a. Rename "audio_policy_configuration.xml" in "/sbin/.magisk/img/acp/system/vendor/etc/audio" to "audio_policy_configuration.xml.bak".
b. Copy the audio policy configuration xml file from "/sbin/.magisk/img/acp/system/etc" to "/sbin/.magisk/img/acp/system/vendor/etc/audio".
4. Go to ViperFx and install drivers, Viper will auto Reboot!
I'm probably cutting some corners here, but i got no problems at all this far.
Jonas G. Morsch said:
BenParz, i can't thank you enough for this! the choppy audio after installing Viper was making me crazy.
I'm running Lineage OS 05/18/2019 + nano gaaps
After mess around with this modules i got other way:
1 . Install Audio Compatibility Patch. It now comes with a multi-option installer, so you want to Select NO to the first option then choose Vol + (Patch New Logic). Select NO to the second option and then use Vol - (remove Volume Listener Library). This is done so that your audio won't crackle. You can skip USB Dac if you're not using it and you should choose NO at the last option (library workaround).
2. Download and install Viper4Android 2.7.1 Magisk Module here: https://zackptg5.com/downloads/v4afx_v2.7.1.0.zip .
More info : https://forum.xda-developers.com/android/apps-games/app-viper4android-fx-2-6-0-0-t3774651
3. Fix BT:
a. Rename "audio_policy_configuration.xml" in "/sbin/.magisk/img/acp/system/vendor/etc/audio" to "audio_policy_configuration.xml.bak".
b. Copy the audio policy configuration xml file from "/sbin/.magisk/img/acp/system/etc" to "/sbin/.magisk/img/acp/system/vendor/etc/audio".
4. Go to ViperFx and install drivers, Viper will auto Reboot!
I'm probably cutting some corners here, but i got no problems at all this far.
Click to expand...
Click to collapse
Have you tried whatsapp voice notes?
Are they making crackling sound when app is minimized or screen is off while playing voice note?
Thanks a lot for such an easy guide.
hugolol said:
Will viper work with a bitrate of over 48k? My headphones us 96k which doesnt work with the buggy v4a i use, but its the only version of v4a that actually works at all for me (will try your way of installing later)
Click to expand...
Click to collapse
Well, you can actually change the Bluetooth bitrate setting in developer options. Doing that allows me to use V4a on my sony BT speaker (which uses LDAC).
slimshouki said:
Have you tried whatsapp voice notes?
Are they making crackling sound when app is minimized or screen is off while playing voice note?
Click to expand...
Click to collapse
Yeah, Whatsapp on Lineage crackles no matter what.
I'm dealing with this problem since my Zenfone 2 with Lineage 14 and no audio mod whatsoever, but never cared too much, because when i rarely listen Whatsapp audio files i do in foreground, and using the earpiece, . I also use telegram for 95+% off my conversations this days.
Hi Again!
After some time of testing, i think i got it how to use Audio Compatibility Patch (1.7.3+) with Lineage OS properly on our device:
Skip audio_policy patching?
- No
Patch flags or remove selections?
- Remove (old logic)
If patched the audio gets worse/lower on speaker/jack.
Would you like to skip notification helper?
- No
Remove notification helper effect or volume listener library?
- Remove volume listener library
Would you like to skip usb policy patching for usb dacs?
- Whatever
Use library workaround?
- No
If used causes bluetooth routing problems.
No Audio Modification Library needed.
After this sequence, my earphones,bluetooth and speaker worked fine with ViperFX 2.7.1, especially the jack, witch was really quieter and muffed before.
Can you guys try it out?
AudioModificationLibrary (AML) has been updated to 2.4. we've also updated unity modules. Everything should work now. Viper, James, Sauron and DTS.
At least on latest MIUI pie betas there should be no Bluetooth bug or anything.
There was a question regarding viper and above 48k.
Viper can just process up to 48. We've released yesterday the new module with DTSultra port. This is capable of up to 96k.
Nemuritor01 said:
AudioModificationLibrary (AML) has been updated to 2.4. we've also updated unity modules. Everything should work now. Viper, James, Sauron and DTS.
At least on latest MIUI pie betas there should be no Bluetooth bug or anything.
There was a question regarding viper and above 48k.
Viper can just process up to 48. We've released yesterday the new module with DTSultra port. This is capable of up to 96k.
Click to expand...
Click to collapse
What about bluetooth on PE and other custom ROMs?
While I know there are other threads regarding similar programs with this rather temperamental app, I didn't find any thread that fit my case exactly, nor one that really fixed my problem, so.. sorry if this is a duplicate.
Anyway, situation is this:
Viper4Android 2.5.0.5 (installed through magisk 20.0, MM 7.3.5) was working perfectly (or atleast somewhat) before recent update. Now that my phone is on Oxygen OS 10.0.1.GM21BA, the driver for Viper fails to install (it says "driver installed, please reboot etc.", but upon reboot it says "please reinstall driver, etc.", and the loop continues).
What I've tried so far:
>Reinstalling Viper - no difference
>Disabling SELinux (both through the Viper itself and through some outside app that might or might not work) - no difference
>Read that deleting audio.fx in vendor/etc/ could fix this problem - couldn't find the file
>Yelling at the phone - no difference
>Also read somewhere that an issue might be that Viper might be denied storage access permission, but the app don't seem to be requesting any permissions at all.
Anyone have any tips or pointers at what else I could check or try? Music just sounds kinda bleh without Viper.
Luxor144 said:
While I know there are other threads regarding similar programs with this rather temperamental app, I didn't find any thread that fit my case exactly, nor one that really fixed my problem, so.. sorry if this is a duplicate.
Anyway, situation is this:
Viper4Android 2.5.0.5 (installed through magisk 20.0, MM 7.3.5) was working perfectly (or atleast somewhat) before recent update. Now that my phone is on Oxygen OS 10.0.1.GM21BA, the driver for Viper fails to install (it says "driver installed, please reboot etc.", but upon reboot it says "please reinstall driver, etc.", and the loop continues).
What I've tried so far:
>Reinstalling Viper - no difference
>Disabling SELinux (both through the Viper itself and through some outside app that might or might not work) - no difference
>Read that deleting audio.fx in vendor/etc/ could fix this problem - couldn't find the file
>Yelling at the phone - no difference
>Also read somewhere that an issue might be that Viper might be denied storage access permission, but the app don't seem to be requesting any permissions at all.
Anyone have any tips or pointers at what else I could check or try? Music just sounds kinda bleh without Viper.
Click to expand...
Click to collapse
You need to install drivers twice.
Mhm, sure.
Though, to be honest, this was among the things I tried before. No difference.
Luxor144 said:
While I know there are other threads regarding similar programs with this rather temperamental app, I didn't find any thread that fit my case exactly, nor one that really fixed my problem, so.. sorry if this is a duplicate.
Anyway, situation is this:
Viper4Android 2.5.0.5 (installed through magisk 20.0, MM 7.3.5) was working perfectly (or atleast somewhat) before recent update. Now that my phone is on Oxygen OS 10.0.1.GM21BA, the driver for Viper fails to install (it says "driver installed, please reboot etc.", but upon reboot it says "please reinstall driver, etc.", and the loop continues).
What I've tried so far:
>Reinstalling Viper - no difference
>Disabling SELinux (both through the Viper itself and through some outside app that might or might not work) - no difference
>Read that deleting audio.fx in vendor/etc/ could fix this problem - couldn't find the file
>Yelling at the phone - no difference
>Also read somewhere that an issue might be that Viper might be denied storage access permission, but the app don't seem to be requesting any permissions at all.
Anyone have any tips or pointers at what else I could check or try? Music just sounds kinda bleh without Viper.
Click to expand...
Click to collapse
Uninstall your current Viper and reboot. Sideload Viper 2.7.1.0 apk or use the Magisk module. Install the driver and reboot. Once back in Android, install the driver again. Should work. If not, go into V4A settings and put in compatibility mode.
Hmm, installing drivers multiple times made no difference in 2.5.0.5, and yet in 2.7.1.0 that fixes everything. I actually thought Tropical Cactus was just taking the piss. Uehh, this Viper and its esoteric rituals.
Anyway, it works now. Thank you for your help.
To repeat my question from another thread, i have the same issue and 2.7 only works for me when the "attach audio effects" option is checked and that introduces quite significant audio lag when skipping tracks.
I also can't seem to get rid of the permanent notification without breaking vipers functionality.
Is there any fix for this? Or a way to properly install 2.5.0.5?
Luxor144 said:
Hmm, installing drivers multiple times made no difference in 2.5.0.5, and yet in 2.7.1.0 that fixes everything. I actually thought Tropical Cactus was just taking the piss. Uehh, this Viper and its esoteric rituals.
Anyway, it works now. Thank you for your help.
Click to expand...
Click to collapse
Lol. Forgot to suggest 2.7.1 and then install drivers twice.
Still an issue in 10.3.4
}{Alienz}{ said:
Still an issue in 10.3.4
Click to expand...
Click to collapse
I got it working after finding a guide that had to do with audio modification library too. Followed it perfectly and all works. I'll try to find it.
GeekMcLeod said:
I got it working after finding a guide that had to do with audio modification library too. Followed it perfectly and all works. I'll try to find it.
Click to expand...
Click to collapse
Tried to find that one again, too.
I ended up installing the Audio modification library magisk module, rebooting, deactivating (not uninstalling) that module and then installing the current Viper 2.7.1.6 module.
May have rebooted after that before installing drivers and therefore rebooting again, can't remember though.
But it does work perfectly and the guide did go something like this.
Also possible that a Viper update fixed the issue.
I'm not able to open the Android camera app anymore. WIth Edxposed disabled it works. So I'm wondering if anyone on Android 11 Nov update with Edxposed has camera working. If so, could you kindly tell me your setup (ie. Edxposed version, etc.)?
Edit: It looks like the Camera update from Nov 17 is what broke this. After uninstalling the update it works.
I have the same problem - how did you uninstall the update?
EDIT: Nevermind I figured it out ?
Uninstalling the update down to 7.3.021 is an okay fix... but is there any way to update it to something more recent without installing 8.1.011 from the Play Store which is definitely broken with EdXposed?
I tried the APK Mirror installer with a split APK, but get a "verification did not succeed" error. This is with USB/ADB verification disabled.
I tried an old 7.6 APK with MiXplorer trying to install with root and it also didn't work.
I don't think I use the camera enough to even know the difference between 7.x and 8.x... I guess I'm just curious.
Anyone found a solution for this? Only stock version is working.
Apparently if you clear the cache/data of Google Play Services, the APK Mirror Installer will have better luck installing other versions.
jljtgr said:
Uninstalling the update down to 7.3.021 is an okay fix... but is there any way to update it to something more recent without installing 8.1.011 from the Play Store which is definitely broken with EdXposed?
I tried the APK Mirror installer with a split APK, but get a "verification did not succeed" error. This is with USB/ADB verification disabled.
I tried an old 7.6 APK with MiXplorer trying to install with root and it also didn't work.
I don't think I use the camera enough to even know the difference between 7.x and 8.x... I guess I'm just curious.
Click to expand...
Click to collapse
For pass the dread "verification did not succeed" message, clear your Google Play framework data. You will need to resetting some personalization settings (you will know when it happens) but install of 8.x camera app will work.
I had the same issue with edxposed and google camera 8.1, but all of a sudden it started working today. Not really sure what I did that made it work.
I was playing around with edxposed back and forth. Originally had Riru v21.2 installed (where camera 8.1 didn't work), so I installed Riru v23 over it. Rebooted but camera still didn't work. Went back to v21.2 or v21.3 and then went back to v23. I may have done a few more uninstaling/reinstalling and now camera 8.1 opens without crashing.
With camera 8.1 working, I have the following installed: magisk manager 21101, riru v23, riru-edxposed v0.5.0.6 (sandhook), edxposed manager 4.5.7. But the odd thing is that I've had the same apps/modules installed when camera was not working.
What I noticed different this time is that Edxposed manager says "Edxposed Framework is not installed" whereas before it would say something like, "installed but not active." That made we think that edxposed wasn't installed or active, so i tested with 2 xposed modules (fingerface and disableflagsecure) and they both work... so I'm pretty sure edxposed is active.
I also cleared the cache and storage on the camera app but I don't think that did anything.
I have the same problem
neo_lithic3K said:
I had the same issue with edxposed and google camera 8.1, but all of a sudden it started working today. Not really sure what I did that made it work.
I was playing around with edxposed back and forth. Originally had Riru v21.2 installed (where camera 8.1 didn't work), so I installed Riru v23 over it. Rebooted but camera still didn't work. Went back to v21.2 or v21.3 and then went back to v23. I may have done a few more uninstaling/reinstalling and now camera 8.1 opens without crashing.
With camera 8.1 working, I have the following installed: magisk manager 21101, riru v23, riru-edxposed v0.5.0.6 (sandhook), edxposed manager 4.5.7. But the odd thing is that I've had the same apps/modules installed when camera was not working.
What I noticed different this time is that Edxposed manager says "Edxposed Framework is not installed" whereas before it would say something like, "installed but not active." That made we think that edxposed wasn't installed or active, so i tested with 2 xposed modules (fingerface and disableflagsecure) and they both work... so I'm pretty sure edxposed is active.
I also cleared the cache and storage on the camera app but I don't think that did anything.
Click to expand...
Click to collapse
I tried it but it didn't work, it only works with v 21.3 but the modules stopped working. Hopefully a solution comes out.
Add gcam to black list and reboot. Just tried and it works
peter_dk01 said:
Add gcam to black list and reboot. Just tried and it works
Click to expand...
Click to collapse
I tried updating Google Camera to 8.1, immediately didn't work as expected.
Added to Exposed blacklist, rebooted... still didn't work.
Added to Exposed Compat list, rebooted... still didn't work.
Downgraded to 7.1, works again.
Before installing 8.1, I added Camera to Exposed blacklist. Just for safe measure also added to magisk hide. Rebooted, installed 8.1 and it worked.
Don't know if all steps are necessary but not gonna tweak anything since I don't know how sensitive it is.
Added to Magisk Hide, Xposed Blacklist, Xposed Compat list, rebooted; installed 8.1.101.x... force closes immediately.
thx, it worked for me. I did it after I already installed 8.1
dortok said:
Before installing 8.1, I added Camera to Exposed blacklist. Just for safe measure also added to magisk hide. Rebooted, installed 8.1 and it worked.
Don't know if all steps are necessary but not gonna tweak anything since I don't know how sensitive it is.
Click to expand...
Click to collapse
dortok said:
Before installing 8.1, I added Camera to Exposed blacklist. Just for safe measure also added to magisk hide. Rebooted, installed 8.1 and it worked.
Don't know if all steps are necessary but not gonna tweak anything since I don't know how sensitive it is.
Click to expand...
Click to collapse
I did this except add to magiskhide and it worked.. uninstalled updates. Compatibility list camera app, rebooted then open it. After update back to 8.1. and opened camera..works great again
What fixed the problem for me was downloading the latest canary YAHFA build in exposed manager. And flashing it in Magisk. I already had configured the compatibility settings for the camera module.
peter_dk01 said:
Add gcam to black list and reboot. Just tried and it works
Click to expand...
Click to collapse
This is all I had to do on my Pixel 4a 5G also. Thanks!
For anyone wondering, in EdExposed, if I go to XHide and hide camera it works. Hope this helps!
Hide camera in black list.
Latest version of exposed, riru, and riruedxposed June 21 update stock rooted. Working flawlessly
LSPosed is a better choice
EdXposed has not been updated for too long
Anyone found a solution? I can't get it to work hiding gcam on xposed blacklist and magiskhide