Related
Hi all,
I rooted my S4, installed Beats Audio using the "Beats Audio Installer". I didn't like the sound, but had no backup, so I downloaded a stock ROM (5.0.1) und flashed my mobile using ODIN. Odin finished with "PASS". Mobile rebooted an to my suprise it came up with all apps and data still on it. When I plugged in my headphones, the beats notification appeared. I rebooted in recovery mode and wiped all data. The mobile looks like new now. Now my question:
Can I be sure beats audio is gone? Can I check that somehow using a root browser or somehow else?
Thanks for your effort helping me!
Regards,
Rumpelhund
Wiping is usually done before flashing a ROM.
If you really want to be 100% sure Beats is gone, dope a complete wipe before flashing the ROM.
Thank you very much. I hoped, there would be another way. I already reinstalled and configured my mobile again, but well, that was my mistake not yours
rumpelhund said:
Thank you very much. I hoped, there would be another way. I already reinstalled and configured my mobile again, but well, that was my mistake not yours
Click to expand...
Click to collapse
These sound mods usually also have an uninstaller, why didn't you use that?
It has an uninstaller, that merly deletes the notification app of beats audio. It does not remove the sound drivers. Therefore I did the ROM flash.
I'm Posting this because of all the confusion I see on the different forums on how to get this working. This WILL WORK as I've personally tested on three different versions of Android on the Nexus 6p, Samsung S3 and HP Touchpad.
The underlined steps are the gist of the process....
How to Install Viper4Android 2.5.0.5 on 6.x 7.0, 7.1
Download ViPER4Android_2.5.0.5_guitardedhero.zip
here's a personal google drive link
DOWNLOAD IT HERE https://drive.google.com/file/d/0B3qV-scfklSkZEg0MDdZY3J4ZXM/view?usp=sharing
Boot into TWRP recovery and install/flash the ViPER4Android_2.5.0.5_guitardedhero.zip from recovery.
Reboot phone.
Use a file explorer with root access (Root explorer)
Go to the /vendor/etc/ directory on the device and rename audio_effects.conf to audio_effects.conf.bak (IF THE FILE EXISTS)
Open ViPER4Android FX
You may get a notification to install V4A driver. Select YES.
It may take some time to install V4A driver, it's doing its job and will finish soon. If Android gives an error that the app has stuck/stopped, select the wait option, don't force close it.
Make SURE that you've given Viper4Android Storage permissions
or you won't be able to load or save profiles
Check under Driver Status (in Viper4Android) to make sure it's enabled and processing. Like this: https://drive.google.com/file/d/0B3qV-scfklSkbGJMb0JkOWdwX0E/view?usp=sharing
Once the Driver installed message shows on screen, reboot.
CREDIT TO guitardedhero and androiding.how for making it simple and me for being pissed at the confusion to get this simple mod working for folks.
Most of this guide's steps were modified/originated from http://androiding.how/install-viper4android-nougat/
I attempted to simplify the steps because of all the confusion I see on forums, and make the instructions less wordy and more precise.
This works for you please just give me a thanks I've been on here for too many damn years to not have more than 17 thanks. Good luck everybody enjoy Android it's awesome
Can I get a copy of your audio.effect file? I don't have one I deleted it by mistake trying to edit it. Thanks
troyd28 said:
Can I get a copy of your audio.effect file? I don't have one I deleted it by mistake trying to edit it. Thanks
Click to expand...
Click to collapse
Never needed to do anything with that file other than rename it before installing the Viper4android driver. If it's a fresh flash you should be good to go. Or you could just reflash the rom on top to fix any weird stuff you might have done trying to get it to work. It's really not that difficult to get this mod installed/set up.
My current ROM doesn't even have that file in vendor/etc if that helps.
lmt1979 said:
Never needed to do anything with that file. If it's a fresh flash you should be good to go. Or you could just reflash the rom on top to fix any weird stuff you might have done trying to get it to work. It's really not that difficult to get this mod installed/set up.
My current ROM doesn't even have that file in vendor/etc if that helps.
Click to expand...
Click to collapse
Yea I tried reflash on top but the file is completely gone it doesn't come back I just need it to edit it to .bak or I don't need that file at all?
troyd28 said:
Yea I tried reflash on top but the file is completely gone it doesn't come back I just need it to edit it to .bak or I don't need that file at all?
Click to expand...
Click to collapse
I don't think you need it at all. But always do backups before messing with things.
lmt1979 said:
Never needed to do anything with that file other than rename it before installing the Viper4android driver. If it's a fresh flash you should be good to go. Or you could just reflash the rom on top to fix any weird stuff you might have done trying to get it to work. It's really not that difficult to get this mod installed/set up.
My current ROM doesn't even have that file in vendor/etc if that helps.
Click to expand...
Click to collapse
lmt1979 said:
I don't think you need it at all. But always do backups before messing with things.
Click to expand...
Click to collapse
Yea I kinda screwed up on that part but I'll try to see if it works now without that file that you said to edit.
troyd28 said:
Yea I kinda screwed up on that part but I'll try to see if it works now without that file that you said to edit.
Click to expand...
Click to collapse
It should, if not do a backup of your Rom, your apps and a backup with your launcher's backup utility and there's no worries. Then do a clean flash of the rom.
I just switched to Nova launcher from Apex and it will basically restore your widget locations even..it really makes it easy to clean flash. I'll dirty flash sometimes but if there's any funny business, back up and get a good clean rom flash going..
You should provide a download link. Had to search a bit to find it.
Sent from my iPad using Tapatalk Pro
Sonel Prabhakaran said:
You should provide a download link. Had to search a bit to find it.
Sent from my iPad using Tapatalk Pro
Click to expand...
Click to collapse
Which download link? The first one? It should be available/shared with anyone.
Just tested it with Internet Explorer and it brought it up fine.
lmt1979 said:
Which download link? The first one? It should be available/shared with anyone.
Click to expand...
Click to collapse
Oops! Speed read this thread. Misread that.
What is different about this and just installing deuteronomy zip https://www.androidfilehost.com/?fid=529152257862677226
I got it also working by doing the same as you describe here?!
jochem86 said:
What is different about this and just installing deuteronomy zip https://www.androidfilehost.com/?fid=529152257862677226
I got it also working by doing the same as you describe here?!
Click to expand...
Click to collapse
The package I use is much simpler. It was provided by guitaredhero and doesn't include all of the other config files. I've not had luck with those nor tested those. The ARISE ZIPS simply haven't worked for me. If those work for you by all means use them. The smaller package has worked for me on numerous devices and android builds.
Simpler is better in my opinion. The old viper zips didn't require 20 + files to function.
Good luck!
Nougat 7.1.1 latest build nmf26f
Supersu and twrp(no kernel or rom)
Rooted just for adaway and v4a ,your method works,but for me it didnt install driver said i had no root,had to reboot once after changing the filename to audio effects.conf.bak and then it was installed own ,didnt ask to install when i opened the app
gobblegobbler said:
Nougat 7.1.1 latest build nmf26f
Supersu and twrp(no kernel or rom)
Rooted just for adaway and v4a ,your method works,but for me it didnt install driver said i had no root,had to reboot once after changing the filename to audio effects.conf.bak and then it was installed own ,didnt ask to install when i opened the app
Click to expand...
Click to collapse
Hi, just sharing. Installing viper mod has been slightly tricky for me since nougat. I like Leviticus 1.3 and have it running with nmf26f. I always install viper after setting everything up and doing a back up since it's near impossible to get rid of the files once installed.
1. Install busy box stericson. Reboot.
2. Rename audio effects.con.bak Reboot.
3. Finally install 1.3.
4. Install black player from play, insert headphones and press play.
5. Open viper app and hooray, no drivers not installed message.
If I do not reboot after every step, it's almost guaranteed.
When enable for first time, music will disappear for a sec before hearing a slight difference. Adjust to your liking from there. I noticed if the music doesn't mute for that sec, Dolby atmos will just be lifeless when enabled or when switching to speaker mode and back to headset, no processing after.
Really weird.
Also, if developer options not enabled before installation, drivers won't install.
Learned from plenty of wipes and restoration.
Alternatively, there is a way to do this the systemless mode using Magisk.
Just install the Viper4Android module thats on the Magisk Manager app,
then I made a module that changes the "audio_policy_configuration.xml" file for the one I modded, using this reference http://forum.xda-developers.com/showpost.php?p=68859212&postcount=23811
It works for all except on soundlcloud.
I have 2 diferent modules for 7.0 and 7.1.1 stock images if you need them
Papote3 said:
Alternatively, there is a way to do this the systemless mode using Magisk.
Just install the Viper4Android module thats on the Magisk Manager app,
then I made a module that changes the "audio_policy_configuration.xml" file for the one I modded, using this reference http://forum.xda-developers.com/showpost.php?p=68859212&postcount=23811
It works for all except on soundlcloud.
I have 2 diferent modules for 7.0 and 7.1.1 stock images if you need them
Click to expand...
Click to collapse
Hi, does this make the mod system wide except sound cloud? If so, could you share the 7.1.1? Thanks.
tropical cactus said:
Hi, does this make the mod system wide except sound cloud? If so, could you share the 7.1.1? Thanks.
Click to expand...
Click to collapse
It works on all the apps I've tried.
Here's the magisk module, install using the magisk manager
http://cloud.tapatalk.com/s/584aa591ae861/v4a_fix_v2_7.1.1.zip
Papote3 said:
It works on all the apps I've tried.
Here's the magisk module, install using the magisk manager
http://cloud.tapatalk.com/s/584aa591ae861/v4a_fix_v2_7.1.1.zip
Click to expand...
Click to collapse
Err, not sure what magisk is. Never used it before. Can't find it as an app in play. Would appreciate some help. Thanks.
tropical cactus said:
Err, not sure what magisk is. Never used it before. Can't find it as an app in play. Would appreciate some help. Thanks.
Click to expand...
Click to collapse
Start here:
http://forum.xda-developers.com/showthread.php?t=3473445
Basically magisk is similar to Xposed in that it can add mods to your ROM without having to flash entire Roms.
Magisk does not touch system, so magisk modules are systemless. Read the forum to find out
You basically flash magisk.zip and Magisk PHH Superuser in recovery,
Then install PHH Superuser app from play store
Then magisk manager apk from XDA
But please read first
Papote3 said:
Start here:
http://forum.xda-developers.com/showthread.php?t=3473445
Basically magisk is similar to Xposed in that it can add mods to your ROM without having to flash entire Roms.
Magisk does not touch system, so magisk modules are systemless. Read the forum to find out
You basically flash magisk.zip and Magisk PHH Superuser in recovery,
Then install PHH Superuser app from play store
Then magisk manager apk from XDA
But please read first
Click to expand...
Click to collapse
Thanks. I flashed superSU to root via twrp earlier on. Don't know what it means to flash it systemless. If I flash PHH superuser, will I be able to continue to use chainfire's flash fire to install official ROMs later? Been using it to upgrade since 7.0. I've used xposed mods a lot previously, so this magisk manager is like xposed app where you can download modules and install and enable them?
UPDATE 2: if you are on the November update already I recommend following this guide that's a lot better than my own and does not rely on TWRP. To get snokes kernel going to use with that guide (you must be on the November update and non-verizon), download this kernel that was posted in this thread by @123SIT.
After gaining root, come back here for the Viper portion.
Hey all. This took me a bit to get up and running on my own phone, but with some help from the XDA community I've now got Magisk/Root, Snoke Kernel, and Viper4Android all working. Since I know other members have to be struggling with the same things, I've decided to post a semi-noob friendly guide.
This worked for my device, I make no guarantees for your own. This guide assumes you have an unlocked bootloader already and therefore are not using a Verizon device. I have not tested this on 8.1, so I can say that this, for now, is only applicable to 8.0. Before starting, please ensure that you have the latest version of adb/fastboot. This is extremely important.
Install the MagiskManager-v5.4.1.apk to your device
Open Magisk Manager on your phone and click install (Not 100% sure if this step is necessary)
Download TWRP alpha here.
Download the Magisk version that @bryantjopplin posted in this thread.
Download the Taimen version of the Snoke.R10.zip kernel found in this thread.
Rename twrp file to twrp.img and open a command prompt/adb window where all of the downloaded files are located.
Rename the Magisk-v14.4.1.zip file to magisk.zip for simplicity
Type the following command in the adb window to reboot to bootloader: adb reboot-bootloader
After it reboots, type the following command to boot into TWRP. Swipe to allow system mods: fastboot boot twrp.img
When TWRP loads, go to Advanced and choose ADB Sideload, swipe to confirm, then type the following command:adb sideload Snoke.R10.zip
After that completes, you'll have to select ADB Sideload again, then type the following command: adb sideload magisk.zip
Reboot. When you go to Magisk Manager, you should see that you now have root.
Go to normal android settings -> Apps & notifications -> See all apps -> Three dot menu button -> show system -> find MusicFx in the list and click it -> Click force stop -> Click disable -> Go to storage -> Clear Data.
Reboot
Download version 2.2 (latest) of viper4Android from this thread. Other members have reported that this module version can now be found in the magisk manager downloads section!
In magisk manager, click menu and go to modules. Click the add button, and select the viper4Android zip you downloaded in the previous step.
After installation completes, reboot.
Open the newly installed Viper4Android app on your phone
Enable master power where you'd like it.
Play some music. Viper4Android should now be working. It could require an additional reboot, song change, or master power toggle in viper to get things processing.
Thanks to @bryantjopplin and @g3v0 for the assistance.
Thanks for the write up. Instead of snokes kernel I used stock and just installed selinux mode changer and set permissive and every step you wrote worked for me. Just thought I would let you know for people who wanted to keep stock.
Good post.
Are Snoke and Viper4Android to fix the audio clicks on some models?
I got root without TWRP. Should I install or or just wait for a more polished version?
But this is not valid for anyone who took the Nov update because TWRP is incompatible, correct?
Sent from my Pixel 2 XL using Tapatalk
idkwhothatis123 said:
But this is not valid for anyone who took the Nov update because TWRP is incompatible, correct?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I believe that is correct, yes.
shizat63 said:
Good post.
Are Snoke and Viper4Android to fix the audio clicks on some models?
I got root without TWRP. Should I install or or just wait for a more polished version?
Click to expand...
Click to collapse
Viper will make any audio coming out of your phone sound amazing if tuned properly. For TWRP, yes, I'd definitely wait until a full beta or stable release to do a real flash.
idkwhothatis123 said:
But this is not valid for anyone who took the Nov update because TWRP is incompatible, correct?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Root/Magisk, Viper and Snoke's kernel still work fine. Refer to my previous post:
g3v0 said:
My general steps to update were:
Fastboot flash boot, system, vendor imgs from stock factory image.
Reboot and do OTA update.
Download the new factory image from Google, extract boot.img and replace the zImage with the one from R10.
Flashed the modified boot.img (not sure if necessary).
Reboot and patch boot image in MagiskManager.
Now for some reason, the newly created patched_boot.img file is not visible when I connect my phone to my PC (it showed and transferred the old one when I tried). I used a file manager app to copy and paste /sdcard/MagiskManager/patched_boot.img into /sdcard, where it was visible, and transferred it to my computer.
Fastboot flash the patched_boot.img
Reboot with Magisk/root and Snoke's R10 permissive
Click to expand...
Click to collapse
If your phone's build number in Settings -> About Phone is "OPD1.170816.025" (ends in .025), you can use the attached boot.img file, which includes Snoke's R10, and skip the first 3 lines. You will still need to patch it in Magisk and reflash it though.
Was too big too attach, get here: https://drive.google.com/open?id=1_2vXBn5zGCGVq_b5PIKQszpqQa1xHS1f
I love you zachman175.
I've tried the steps in the OP and Viper will work for a little bit, but then after a couple minutes it stops working or when I switch the master power on and off a few times then it stops working, it's odd.
KHANrad_SIN said:
I've tried the steps in the OP and Viper will work for a little bit, but then after a couple minutes it stops working or when I switch the master power on and off a few times then it stops working, it's odd.
Click to expand...
Click to collapse
Afaik that is a typically issue with viper and magisk. A few months ago when I used viper with super su there wasnt any issues. But I am not 100% sure, just a hint.
for me it works for speaker output but not processing for bluetooth. Anyone else?
Taebom said:
for me it works for speaker output but not processing for bluetooth. Anyone else?
Click to expand...
Click to collapse
I was having the same issue and got it working by installing the Magisk Module called 'Universal deep_buffer Remover' by ahrion, zackptg5 that can be found within the downloads section of magisk manager. After installation, I disabled master power on bluetooth in Viper, rebooted, and then turned master power back on. I then opened spotify and it started processing. I'll update the main thread with this information.
zachman1750 said:
I was having the same issue and got it working by installing the Magisk Module called 'Universal deep_buffer Remover' by ahrion, zackptg5 that can be found within the downloads section of magisk manager. After installation, I disabled master power on bluetooth in Viper, rebooted, and then turned master power back on. I then opened spotify and it started processing. I'll update the main thread with this information.
Click to expand...
Click to collapse
hmm I'm having the same issue as well and I tried the deep buffer module but bluetooth master power is still not working for me, gonna try to uninstall and redo it all
KHANrad_SIN said:
hmm I'm having the same issue as well and I tried the deep buffer module but bluetooth master power is still not working for me, gonna try to uninstall and redo it all
Click to expand...
Click to collapse
Maybe before reinstalling all of it you could try clearing your Viper app data and then reboot. I took that step as well. I've had success streaming Spotify over bluetooth with these steps, but it definitely seems a bit finicky.
zachman1750 said:
Maybe before reinstalling all of it you could try clearing your Viper app data and then reboot. I took that step as well. I've had success streaming Spotify over bluetooth with these steps, but it definitely seems a bit finicky.
Click to expand...
Click to collapse
I actually ended up doing both reinstalling everything and clearing vipers data then rebooting but its still not working. Maybe it could be that i'm using google play music to play local music instead of streaming on spotify. Under driver status, does yours say "Processing: Yes"? Mine says "Processing: No". Or it could be the bluetooth headphones I'm using, I'm using one of those truly wireless earbuds with no wire in between.
KHANrad_SIN said:
I actually ended up doing both reinstalling everything and clearing vipers data then rebooting but its still not working. Maybe it could be that i'm using google play music to play local music instead of streaming on spotify. Under driver status, does yours say "Processing: Yes"? Mine says "Processing: No". Or it could be the bluetooth headphones I'm using, I'm using one of those truly wireless earbuds with no wire in between.
Click to expand...
Click to collapse
Mine says processing: no as well, but that could be because I'm not presently streaming audio. Are you sure you're using the permissive version of the kernel? The non-se version that is.
zachman1750 said:
Mine says processing: no as well, but that could be because I'm not presently streaming audio. Are you sure you're using the permissive version of the kernel? The non-se version that is.
Click to expand...
Click to collapse
Mine says processing: no when i start playing music with bluetooth headphones. I used the patched boot image with R10 incorporated that you provided in post #7.
KHANrad_SIN said:
Mine says processing: no when i start playing music with bluetooth headphones. I used the patched boot image with R10 incorporated that you provided in post #7.
Click to expand...
Click to collapse
Keep in mind that was another member who posted that and I am speaking from a pre-november update perspective.
zachman1750 said:
Keep in mind that was another member who posted that and I am speaking from a pre-november update perspective.
Click to expand...
Click to collapse
ohhhhhhh you're on the september update? I guess that may be it, I'm on the november update
KHANrad_SIN said:
ohhhhhhh you're on the september update? I guess that may be it, I'm on the november update
Click to expand...
Click to collapse
Bluetooth viper does not work for me either, and i'm on Sep. Speaker works fine tho. Tried the deep buffer mod too.
Has anyone had any success getting either to work? I've tried the ones in magisk and they don't work, thanks for any help
shooterlgk said:
Has anyone had any success getting either to work? I've tried the ones in magisk and they don't work, thanks for any help
Click to expand...
Click to collapse
Same boat as you my friend!
shooterlgk said:
Has anyone had any success getting either to work? I've tried the ones in magisk and they don't work, thanks for any help
Click to expand...
Click to collapse
Whenever I try to flash the viper file I used on my 6P in TWRP it gives me an error says system cannot mount...I have no idea why....I need my Viper4Android lol
Kochoa940 said:
Whenever I try to flash the viper file I used on my 6P in TWRP it gives me an error says system cannot mount...I have no idea why....I need my Viper4Android lol
Click to expand...
Click to collapse
I feel ya
I actually have both V4a and Atmos running concurrently on NMJ32F with Magisk 14.3 (14.5 gets caught in a loop and burns battery like mad)
What worked for me is to install V4A (w AML 2.2) from repo, then reboot....Magisk will choke and die, but just reboot again until magisk starts working again. Once it picks back up, it should stay golden.
If you want Dolby also, install that in a similar manner...but from my experience, Atmos must go in AFTER v4a, as installing viper will break dolby but dolby does not break viper. Either way, if Magisk appears to break do not change anything and just reboot again.
YMMV, but thats my experience after a week of fighting with it.
Tardeaux said:
I actually have both V4a and Atmos running concurrently on NMJ32F with Magisk 14.3 (14.5 gets caught in a loop and burns battery like mad)
What worked for me is to install V4A (w AML 2.2) from repo, then reboot....Magisk will choke and die, but just reboot again until magisk starts working again. Once it picks back up, it should stay golden.
If you want Dolby also, install that in a similar manner...but from my experience, Atmos must go in AFTER v4a, as installing viper will break dolby but dolby does not break viper. Either way, if Magisk appears to break do not change anything and just reboot again.
YMMV, but thats my experience after a week of fighting with it.
Click to expand...
Click to collapse
Are they working through bluetooth?
nrage23 said:
Are they working through bluetooth?
Click to expand...
Click to collapse
As traumatic as it might be to those in adjacent cars, yes.
Tardeaux said:
I actually have both V4a and Atmos running concurrently on NMJ32F with Magisk 14.3 (14.5 gets caught in a loop and burns battery like mad)
What worked for me is to install V4A (w AML 2.2) from repo, then reboot....Magisk will choke and die, but just reboot again until magisk starts working again. Once it picks back up, it should stay golden.
If you want Dolby also, install that in a similar manner...but from my experience, Atmos must go in AFTER v4a, as installing viper will break dolby but dolby does not break viper. Either way, if Magisk appears to break do not change anything and just reboot again.
YMMV, but thats my experience after a week of fighting with it.
Click to expand...
Click to collapse
Anyway you could share the link to the v4a you used? Thanks so much brother!
Kochoa940 said:
Anyway you could share the link to the v4a you used? Thanks so much brother!
Click to expand...
Click to collapse
In the Magisk Manager download section, look up ViPER4Android FX by ahrion & zackptg5. This will also install the Audio Modification Library automatically. From my experience, Magisk will screw up after the first reboot so just reboot again and it should come back to life and now show the V4a app in launcher. I didn't have to do anything else to make this version work (unlike one of the others that needed conf files moved around).
Once you have V4a going, search the repo for Dolby Atmos (LeEco Le Pro 3) by same authors. At this point my Magisk blew up again and needed a second reboot....but after that I have both Viper and Atmos working side by side.
Only real caveat is that all my Magisk apps completely dump their settings anytime the magisk core craps the bed (so basically any time I add/remove a module). Everything comes back after 2nd reboot, but settings are cleared. I've given up on it and chalked it up to 14.3 being "beta"...Titanium Backup makes quick work of restoring all app settings when it happens.
Thanks Tardeaux, I got it working with your instructions... Mostly.
Does anyone know how to fix the viper seeing headphones through USB as the phone speaker? If I could get that working this phone would be 100%
BreakingStrata said:
Thanks Tardeaux, I got it working with your instructions... Mostly.
Does anyone know how to fix the viper seeing headphones through USB as the phone speaker? If I could get that working this phone would be 100%
Click to expand...
Click to collapse
No fix for this that I've seen. I asked in the official Viper4Android thread and it seems it's a common problem with Viper in general -- it can't see USB-C audio adapters for some reason (I'm baffled since Viper has a USB audio output tab).
Yeah I've come to the same conclusion from googling. Hopefully someone will update the app soon, until then it looks like I'll be getting a Bluetooth headphone adapter.
BreakingStrata said:
Thanks Tardeaux, I got it working with your instructions... Mostly.
Does anyone know how to fix the viper seeing headphones through USB as the phone speaker? If I could get that working this phone would be 100%
Click to expand...
Click to collapse
I flashed it thru the magisk app but after a reboot I don't see the viper app. Do I have to install that seperate?
Reboot your phone a second time and the app should be there.
Tardeaux said:
In the Magisk Manager download section, look up ViPER4Android FX by ahrion & zackptg5. This will also install the Audio Modification Library automatically. From my experience, Magisk will screw up after the first reboot so just reboot again and it should come back to life and now show the V4a app in launcher. I didn't have to do anything else to make this version work (unlike one of the others that needed conf files moved around).
Once you have V4a going, search the repo for Dolby Atmos (LeEco Le Pro 3) by same authors. At this point my Magisk blew up again and needed a second reboot....but after that I have both Viper and Atmos working side by side.
Only real caveat is that all my Magisk apps completely dump their settings anytime the magisk core craps the bed (so basically any time I add/remove a module). Everything comes back after 2nd reboot, but settings are cleared. I've given up on it and chalked it up to 14.3 being "beta"...Titanium Backup makes quick work of restoring all app settings when it happens.
Click to expand...
Click to collapse
Ugghh, followed what ya'll have done here but no love. I had the driver working and processing according to the app but no settings had any effect at all. So I removed all Magisk modules and cleared cache and data from Magisk. Installed Busbybox. Rebooted. Installed Viper, rebooted twice. Now my driver status is greyed out.
Any suggestion appreciated. About ready to give up and go with a paid app. Funny thing, the 2nd time I installed Viper I did NOT get the other module allowing multiple audio mods.
Not working on Oreo beta
chiadrum said:
Ugghh, followed what ya'll have done here but no love. I had the driver working and processing according to the app but no settings had any effect at all. So I removed all Magisk modules and cleared cache and data from Magisk. Installed Busbybox. Rebooted. Installed Viper, rebooted twice. Now my driver status is greyed out.
Any suggestion appreciated. About ready to give up and go with a paid app. Funny thing, the 2nd time I installed Viper I did NOT get the other module allowing multiple audio mods.
Click to expand...
Click to collapse
I'm having the same issues now. I was able to do it before but now the modules don't pop up. Only one works, if I have multiple it won't work
dear friends
https://drive.google.com/file/d/1-86d....
this works
thanks for the original up loader.
after installation if it freeze clear the cache in storage.
magiks canary needed for ROOT and VIPER
ayurmouli said:
dear friends
https://drive.google.com/file/d/1-86d....
this works
thanks for the original up loader.
after installation if it freeze clear the cache in storage.
magiks canary needed for ROOT and VIPER
Click to expand...
Click to collapse
Link is broken, file does not exist
Plese use this attachment
Safe?
ayurmouli said:
Plese use this attachment
Click to expand...
Click to collapse
Can anyone confirm that this file is safe?
State.of.mind said:
Can anyone confirm that this file is safe?
Click to expand...
Click to collapse
I can confirm the #3 Attached Files , work well at H2OS 11.IN11 (the first stable build android 11 , should be same with O2OS)
with magisk v21.0 , magisk manager v8.0.2 , install it as a module at MAGISK , do not need any audio midification libiary moudle
yes it works. its safe.
u can flash it safely.
dont flash any audio modification libraries.
thank u
Can confirm this works on android 11 op8 pro!
Thanks dude was looking for this:good:
Also working here. Kudo's
Did you guys flash this with Magisk?
Sent from my IN2025 using Tapatalk
Mine is not processing any tips how to make it work? I just flashed with magisk.
That's weird, that's the one I flashed yesterday bc it's sitting on my download folder. After flashing, both of my SIM couldn't be detected, phone number and all were gone. I don't think my FS partition were corrupted. Had to wipe the phone down with recovery. Just downloaded the version posted here and it's the same in my download folder. Didn't work for me.
Sent from my IN2025 using Tapatalk
same here.
reboot phone - sims both ok
Just want to share some thoughts and ask some questions.
Both SIMs sometimes not being detected is true, just reboot the phone, sometimes rebooting doesn't help, after I shutdown the phone and little later start again the SIMs are being detected properly again.
I would like to ask something else, after some random Bluetooth device reconnects or after certain time, V4a stops working with Processing: No. A simple ForceStop of V4a and OPEN again solves the problem but it's just annoying because this happens to me almost every half an hour and with every BT (headset) reconnect.
On previous "pittvandewitt" official V4A Magisk module we were greeted with something like "VOL-Down: Use alternative method, only use this when having issues!"
After selecting this alternative method I recall that it kept processing for days long in the past.. how could we be able to achieve this on Android 11???
hii
all the issues are due to android 11. no option we have to wait until we get all these bugs fixed. i am using dolby now. not viper. in that also sim issue is there unfortunately. thanks
It works. Thank you
Hii all
In magiks viper is available.install it .but don't install drivers. Install viper and reboot. Don't touch it.now come once again to magiks install audio modification library. Reboot. Then go to viper install drivers.reboot it.check driver status.it should have been installed.
Thanks
ayurmouli said:
Hii all
In magiks viper is available.install it .but don't install drivers. Install viper and reboot. Don't touch it.now come once again to magiks install audio modification library. Reboot. Then go to viper install drivers.reboot it.check driver status.it should have been installed.
Thanks
Click to expand...
Click to collapse
Didn't work for me. Seems we have to wait for an updated version.
Is it because the OP8 update? Anyone have a version that works?
So anyone found a fix to SIM Card not being detected on boot? And that I need to reboot multiple times for it to work.
The Viper mod in the magisk manager works fine on Android 11 if you switch SELinux to permissive.