yashsingh1/xdaforums huggingface dataset:
[Magisk] justjr:
The mod works fine in my Moto G, but not in my LG Fino L (both Lineage 7.1.1). I think I figured out why, but wasn't able to fix it.

Moto G has the /etc/vendor and /vendor folders add a config file in magisk on Moto G, that does not appear on the Fino L, what you guys think?

I created the folder (creating 1 create both, so I assume they are only 1 folder linked), rebooted and magisk still does not link the config files.

edit: well, I think I talked too early. It seems to work on Moto G, but Viper is not processing and Dolby is not showing effects and tweaking both changes nothing.

On Fino L, without the /vendor folder, Viper driver is not installer, Dolby is the same, but it worked the other day (don't know why, how, I tried make it work again, nothing).
[Magisk] pbergonzi:
Having a little trouble.

Uninstalled the Viper4Arise module in Magisk so as to have no modules besides Dolby Atmos.

Rebooted system, and installed Dolby Atmos r6.5-b.zip through Magisk and rebooted system.

Rebooted to TWRP recovery, and installed Dolby Atmos r6.5-a.zip, and rebooted system.

Can't find Dolby Atmos in my App Drawer.
[Magisk] kend0g:
Anyone have this working on HTC 10 with Lineage?
[Magisk] freaks211:
Thanks

I just installed this on my phone yesterday It worked flawlessly Thanks for this great Magisk Module :D
[Magisk] Hadookie:
Which phone? Seems like a hit or miss depending on which phone is used..
[Magisk] freaks211:
My 27

Its a my phone my 27 Android 5.1 only in the philippines
[Magisk] pbergonzi:
After installing the Magisk module and the apk per the OP, I can't find the Dolby app?
[Magisk] :
From the bottom of my soul, a BIG THANK YOU to you for this!!
[Magisk] Gungrave223:
Quick question....have this been update with the fix for nougat?
[Magisk] Yash98:
No, i will update it when i get time
[Magisk] g0d0fmischief:
Looks like this still isn't working for stock 7.1.1 ROM

Device: Nexus 5x

ROM: Stock 7.1.1 (Security Patch Level FEB 2017)

Rooted via phh's superuser and running magisk manager 4.2.6 (updated to this from the play store after my initial flash)
[Magisk] Gungrave223:
lol see above question and answer bro ham
[Magisk] Meowdib:
Did not work for me.
[Magisk] Aldideos:
Hi,

Thanks for your module, it works very well (I like systemless things). I'm running your module onto Oxygen OS 4.0.3 (7.0) and it works even if it is nougat, the only add that I had to do is delete the audio_effects.conf in /system/vendor. So I'd like to know if there is a way to cancel it via magisk (I don't know how to cancel a file via magisk, only replace) and not in system so that we can have a real systemless module.

Thanks
[Magisk] lhayati:
Looking forward to the nougat update :)
[Magisk] schrickz:
working great on Moto G running RR N.

thanks for the mod.
[Magisk] laggardkernel:
Sorry, my fault. The problem is that I used multirom to test these modules but Magisk v10 and v11 aren't compatible with multirom anymore.
[Magisk] Schrotty35:
I have install but dont hear any difference whene on/off. For me not work. Use Oneplus 3T on latest Aosip Rom with latest Magisk.
[Magisk] Shemploo:
Has anyone found steps to remove this module via file browser in recovery? I'm unable to boot after install either.
[Magisk] Didgeridoohan:
Get the Mount Magisk script from here:

https://xdaforums.com/apps/magisk/collection-magisk-modules-v2-t3575758

Flash that in recovery and it'll mount Magisk to /data/magisk.
[Magisk] kartikb:
Hi, this module works on my Nexus 6P stock room, 7.1.1 March update with Bluetooth only but not on phone speaker. Is that normal?

Also, funnily it doesn't work on my OnePlus 3T..
[Magisk] ahrion:
Flash my deep buffer remover in the magisk forum.
[Magisk] kartikb:
Thanks, it all finally works on my Nexus 6P. Now to try on my OnePlus 3.. :svetius:
[Magisk] ahrion:
Works on OP3 because that's my daily driver.
[Magisk] Mar-cel:
Any chance to get the latesr Arise dark Dolby Atmos as module ?
[Magisk] opts:
working fine on my device,thanks:)
[Magisk] ahrion:
That's not arise. That's mine.

https://xdaforums.com/android/software/soundmod-axon-7-dolby-atmos-t3412342
[Magisk] sayash5:
Flashed this and at the next boot, it deactivated xposed. Seems like the script conflicted with xposed.
[Magisk] g0d0fmischief:
You don't have xposed running with magisk do you?
[Magisk] ahrion:
Why was I quoted?
[Magisk] g0d0fmischief:
copy paste error didn't notice it was the wrong comment just delete
[Magisk] Bebi_v24:
I installed via Magisk and seemingly it all went well but when I clicked on driver status I got the message in the screenshot. Should I just change the FX Compatibility mode to Compatible instead of Normal?

Edit: After changing to Permissive instead of Enforcing all the only thing that says No, is Processing
[Magisk] ForgottenDude:
Why does this module not show up anymore on Magisk 11.6?
[Magisk] Didgeridoohan:
It's not about the Magisk version, but the Manager. It no longer shows modules that hasn't been updated to one of the newest module templates. This module hasn't been updated...
[Magisk] ForgottenDude:
Thanks. That's what I thought.
[Magisk] Choobilsky:
Should switch to yes as soon as you play an audio file. If not, check your audio players equalizer settings. Should be off.
[Magisk] pbergonzi:
Working now. In any event, I flashed "b" through Magisk, and "a" through TWRP.

Starting Dolby from the app drawer resulted in fc, however I opened Magisk and deleted my other sound modules--Viper and Arise, rebooted, and my precious Dolby is back.

Maybe it wasn't necessary to delete Viper, but I'll survive.
[Magisk] Yash98:
Please test the latest version on magisk manager

Report if working!
[Magisk] Yash98:
It was already working as per screenshot ?

Just play audio and try if processing changes to yes.
[Magisk] Yash98:
Link?
[Magisk] Yash98:
Check again.
[Magisk] pbergonzi:
Yes--Dolby Atmos r6.5-c was available as update in Magisk Manager.

Installed it, rebooted as Magisk Manager offered, and working perfectly.

Dolby effortlessly on my part brings my movies and music to life, and probably doubles the output volume of my OnePlus One.

Thank you.
[Magisk] tejaskadaskar:
Got boot loop while installing the zip through magisk as well as twrp. Stays on OnePlus logo.

Device: OnePlus One
[Magisk] Yash98:
Are you running systemless xposed? This module seems to conflict with that module. :(

What you could do is, flash system xposed and then use dolby with magisk
[Magisk] tejaskadaskar:
Nope I am running nougat 7.1.1 infact I experienced the same thing in previous version. IDK whats happening.I unistalled v4a as its mentioned in op to remove sound mods.But still no success.
[Magisk] MoHuToP:
Hello there. i9300 with latest Los 7.1.2 Dolby just report force close. Can I get any suggestions? :)
[Magisk] alem972:
Really good port, thanks a lot devs, flawlessly working on my Oneplus one, but I found a small bug: every time I reboot (or power on) mods works but the convolver on V4A didn't work until I switch it off and on. Latest build of LOS 14.1
[Magisk] s8m:
Is there any way to fix the module to work with systemless xposed?
[Magisk] lenin1928:
HTC 10 latest viper rom

Causing black screen when booting up. Updated from 6.5b. Xposed not installed.

Downloaded and installed magisk mount and magisk folder mount 0.8.5. Cannot access /magisk from recovery.

Please advise.

Edit

Mount magisk does work. Don't reboot after installing, go straight to explorer.

Deleted mod but black screen persists.
[Magisk] EddoWagt:
I get force closes on my S7e running 7.1.2 Resurrection remix as well :/
[Magisk] s8m:
This module is awesome - works great. Just an idea - it would be great in a future version to include the better Atmos version. The one included is the "classic" version as opposed to the one included in the Le Pro 3 version also found on Magisk repo. (This mod works better for me than the ahrion version.)
[Magisk] Lightracer:
It should work with AudioFX right? (I'm on LOS)
[Magisk] Spikestrip:
Installing this causes Bluetooth Share to crash constantly and makes Bluetooth unusable. I don't know if it's conflicting with something else I've installed, but installing V4A by itself from the repo works just fine.

Nexus 6p, 6.0.1, second to last security update (MTC20F) because I'm using a deodexed rom that is otherwise stock and I never found one for MTC20L. Xposed installed through Magisk. No other audio mods installed.
[Magisk] SkilletDesire:
The Dolby Atmos module in magisk sets of SafteyNet.
[Magisk] yochananmarqos:
How do you know?
[Magisk] SkilletDesire:
Tested and verified myself on S8+ I only installed one module at a time and rebooted each time.
[Magisk] yochananmarqos:
Strange. I can't reproduce it.
[Magisk] dahawthorne:
I'm sure I'm being very stupid, since I see that a number of people are happy, but I don't understand the instructions in the OP. I installed the module through Magisk, but if I understand correctly I need an app/apk to tweak it. So...

"This module now includes ViPER4Android, after installing module install this APK to use it."

https://www.androidfilehost.com/?fid=673368273298930509

"To use ViPER4Android, install APK from here."

https://www.androidfilehost.com/?fid=312978532265364193

And, as noted above, they point to entirely different apks.

Could [MENTION=4794403]Yash98[/MENTION] please clarify this and update/correct the OP as appropriate? Thank you...
[Magisk] Didgeridoohan:
Yeah... Something went wrong with the copy-pasta I think. :D The first link is an old version of the module itself. It's the second link you want. :good:
[Magisk] dahawthorne:
[MENTION=4667597]Didgeridoohan[/MENTION]

Thanks - do you never sleep...? :)
[Magisk] MrNataan:
I get force close on my CM13
[Magisk] shadavis08:
Ok I installed viper and Dolby through NAFT with magisk. the viper opens but nothing works and Dolby just force closes when I try to open it . Any ideas what I need to do to fix this!
[Magisk] sebastian1978:
solved
[Magisk] acwcanada:
Same here
[Magisk] shadavis08:
I reflashed adding in Dolby and Viper with NATF and everything works now.

LG V20 - NATF 5.0 - Magisk 13
[Magisk] otonieru:
Installing this module using Magiskv13 giving trouble to magisk hide, thus tripping safetynet [MENTION=4794403]Yash98[/MENTION]

tried few times. Magiskhide always stopping if the module installed.
[Magisk] shadavis08:
Can anyone explain the difference between adding these in with the ROM I installed and adding the module in through magisk?

LG V20 - NATF 5.0 - Magisk 13
[Magisk] AravindhStanley:
same issue for me. trips safety net. other modules don't seem to cause this issue
[Magisk] cantenna:
that's interesting, installing as system instead passes safteynet?
[Magisk] otonieru:
I Havent tried installing as system. Have you ?
[Magisk] cantenna:
Sorry should have been more specific, instaling ARISE+Deuteronomy+2.94+Modular+AROMA+Installer.zip

via twrp to system i have tried and still passes saftey net.

recommend installing with jedi knight otion and select deep buffer script and dolby digital plus.
[Magisk] otonieru:
Can you send me some link to thread or download ? Hahahaha
[Magisk] cantenna:
Here;

https://www.androidfilehost.com/?fid=457095661767141554
[Magisk] otonieru:
Wow, this is weird indeed ! Installing to system directly can pass safety net, lol

Thx !
[Magisk] cantenna:
(this must mean google secretly loves viper4android)
[Magisk] Didgeridoohan:
Modifying /system doesn't trigger SafetyNet.
[Magisk] otonieru:
I used to simply rename logd to logd.bak, and that trip safetynet right away, weird.
[Magisk] Didgeridoohan:
It of course depends on what kind of modification you do, but just the process of modifying /system should not trigger SafetyNet.
[Magisk] cantenna:
That's a relief.
[Magisk] eeeelinen:
Using Laos 14(Android 7.1.2) LG d620r

Installed model from magisk...

And Dolby Atmos force closes when I start it.
[Magisk] eeeelinen:
Also in settings it appears odly
[Magisk] rheckr:
After installing this module safety net fails even on Magisk v13.0 (96f8efc)
[Magisk] whiplash1:
Safety net fails on magisk v13 beta. Works good with magisk v12 though.
[Magisk] alem972:
now that magisk v13.1 is released this module did't work, dolby work only if you open it every reboot, viper did't find his driver so it doesn't work.

Los 14.1 10/7 build, Oneplus one
[Magisk] danivatsal15:
Unable to use Dolby Atmos post v 13.1 update

Dolby Atmos app force closes itself after v 13.1 update. Doesn't work with repeated reboots as well. I'm on RR 7.1.2. any fix available for this?
[Magisk] kresnadetea:
working so far

keep it up
[Magisk] Potato997:
Hello, I am currently using Paranoid Android with Magisk. I installed Dolby Atmos module but it doesn't work: the app is installed and I can open it without problems but when I play music Dolby doesn't work and the sound remains the same. I checked that there aren't any equalizer, I tried with Shuttle, Phonograph and YouTube but none of them works.

Any suggestion would be very apprecciated.
[Magisk] yochananmarqos:
[MENTION=4794403]Yash98[/MENTION]: There is no processing with Magisk 13.2. It was working with 13.1 and older.

I took a logcat as well, but XDA Labs won't let me upload it. I'll add it later after work.

EDIT: After a reboot, it's processing again. We'll see how it goes.
[Magisk] TahirZX:
Dolby and V4a both working even after magisk 13.2 update.

Plz note that I had module installed even since I was on magisk 12
[Magisk] Rom:
@Yash98

Hello :)

With the next Magisk version (13.3 i suppose) all previous outdated Magisk modules will not continue to work.

So could u update your module please ?
[Magisk] yochananmarqos:
That's not true. Topjohnwu stated modules without the v4 template would be blocked from the module repository, not that they wouldn't work. He's only delaying blocking them to give module developers some time to update them before he actually has time to accept new submissions.
[Magisk] Immortalis:
With Magisk 13.2, Dolby Atmos works for me, but V4A not, status shows as abnormal.

I tried to change that "sepolicy-inject" line and set 755 permissions on audiomodlib scripts, but it doesn't work, it's still the same.

Reverted to Magisk 12, because I would rather have working audio mods than passing SafetyNet.

I assume we have to wait for an update?
[Magisk] 6hexanexz:
+ViPER not working with magisk 13.1 and 13.2 . (12magisk working​)

Status abnomal. Audio format unsupported .

And it's working do this after

Go settings . Enter the developer mode . Disabale SELinux . Start working.

Dolby Atmos always working.

Also this thing install after working

https://xdaforums.com/apps/magisk/module-magisk-selinux-permissive-script-t3577549

but phone getting some time stuck and reboot . Also without reason randomly reboot. I fixed this uninstall magisk and reinstall . Now I use disabale SELinux to work +VIPER
[Magisk] Arju01:
Hello guys, I have oneplus 3t with Twrp Rom Stock (7.1.1) kernel EX. I installed Magisk13,2 and root pernissions are ok, SafetyNet ok, but I also installed the Dolby Atmos + viper4android Fx module, and unfortunately these do not work, viper drivers are not enabled, dolby atmos does not work, what can it depend on?

Inviato dal mio ONEPLUS A3003 utilizzando Tapatalk
[Magisk] vijaykanth:
Use Magisk 12 for now, with UniversalSafetyNet module in case you want to have Android Pay as well. ;)

Remember to uninstall Magisk 13.2 using the Magisk-Uninstaller from the attachments of the release thread.
[Magisk] Arju01:
Thanks for the reply, I tried as you suggested, now in Viper drivers status Neon is enabled and also audio format is supported (with Magisk 13.2 was not supported and Neon disabled). But still nothing works, neither Dolby nor Viper4android Fx, I do not know why :(

Inviato dal mio ONEPLUS A3003 utilizzando Tapatalk
[Magisk] jhobc:
Your module is causing some unmounted errors on Magisk 13.2 (170716) because when I remove it no more errors appears.

SN still pass.

Log attached
[Magisk] kresnadetea:
can i push viper4android to the system app?
[Magisk] 6hexanexz:
I did magisk 12 with I use terminal app systemizer and it works.
[Magisk] safwan ck:
The video guide is here

mod edit - content removed
[Magisk] Rom:
For me too, but differently: the installaiton on the last 13.3 works but when i reboot my phone i get bootlop.

Certainly due to last policy updates of Magisk framework.
[Magisk] alem972:
[MENTION=4794403]Yash98[/MENTION] please update this beautiful module in order to make it works in the last 13.3 magisk
[Magisk] pengkoh1:
try install universal deep buffer remover . it work for me. dobly atmos and viper4android work. i am using magisk 13.3
[Magisk] whalesplaho:
Dolby doesnt work for me.. Viper4Android works!!

Using Android 7.1.1....
[Magisk] Arju01:
Hi my friend, I tried as you suggested and now the Dolby Atmos works (on my One Plus 3T Stock with Magisk 13.3)! Thank you! But Viper4android still nothing :(

At the beginning even the Dolby Atmos did not work, I opened the Viper4android app which asked me to install the drivers, so after Dolby worked .. but only if in the Viper4android the master button is active, otherwise it does not work

Inviato dal mio ONEPLUS A3003 utilizzando Tapatalk
[Magisk] pengkoh1:
Uninstall magisk 13.3. This will deinstall all modules install. Reinstall magisk13.3 through recovery. After magisk 13.3 is installed install dobly-atmos modules from download. Reboot. After that install the universal deep buffer from download in magisk 13.3 .reboot again. Hope this help.
[Magisk] Arju01:
I've already tried to do that, and it doesn't work. Maybe the problem depends on Rom? I have the OxigenOs 4.1.6 .. what is Rom you got?

Inviato dal mio ONEPLUS A3003 utilizzando Tapatalk
[Magisk] pengkoh1:
i am using Resurrection Remix version 5.8.3 on samsung note 3.
[Magisk] whalesplaho:
it didnt worked for me too... launched tha app- menu- help- play demo & it started working....

try that! yhu might be lucky like me..... dnt forget to install universal deep buffer removal!
[Magisk] yochananmarqos:
What menu? :confused:
[Magisk] whalesplaho:
there is a menu there.......
[Magisk] yochananmarqos:
You mean a legacy menu button on the nav bar? I don't have one. I'm on Android 7 1.2, maybe that's why. I also don't have the Help and Explore Dolby Atmos buttons at the bottom.
[Magisk] whalesplaho:
yeap, tha nav bar button.... tha help and explore aint buttons, its wen yhu clicked on tha menu nav bar dat it ll open tha help & explore menu!!!!
[Magisk] yochananmarqos:
I got the menu to work using Custom Navigation Bar, but the Play Demo button crashes the app.
[Magisk] Arju01:
I tried with the play demo but did not change anything, I think that will take time to make this module compatible with all the Rom

Inviato dal mio ONEPLUS A3003 utilizzando Tapatalk
[Magisk] whalesplaho:
Yeap and afterwards launch tha app again... It should work!!

---------- Post added at 10:02 PM ---------- Previous post was at 10:01 PM ----------

It worked for moi here.... Viper4Android and Dolby works together even while i didnt delete nor freeze my MusicFX app.
[Magisk] yochananmarqos:
Yeah, I noticed that. I was rebooting when I noticed it wasn't processing before. I'll see if I can come up with a script to automate restarting Atmos.
[Magisk] whalesplaho:
Dat ll be great.... Once i disconnect headset, i ll need redo tha process again!
[Magisk] 6hexanexz:
Yash98 please update:crying: module please :highfive:
[Magisk] yochananmarqos:
Yeah, Dolby would stop processing after a disconnect / reconnect of my AUX cable in my work vans. I didn't realize that's what did it until you mentioned it. Some of my work vans have BlueTooth, some don't.

I just started using ahrion's Lenovo A7000 [6.5] Atmos which is an updated version of this one. I've had no issues with it not processing using BlueTooth. I use BlueTooth headphones and can't find my wired headset. I'll see if the issue still occurs this week the next time I use a work van with an AUX connection. If it does, I've got a tentative shell script / Tasker task that should restart Atmos when it stops processing.
[Magisk] whalesplaho:
How ll tha script work? I wont mind having it too and for viper cos i always exit n relaunch after disconnect of headset or bluetooth. .
[Magisk] yochananmarqos:
I haven't gotten the script to work just yet. The headphone issue still occurs with ahrion's Atmos, but it's more reliable than this one. I noticed Atmos will only start processing again after tapping Play Demo if the option of Open app again is there. If it only says Close app, then it doesn't. I haven't figured out what exactly is different when that happens. My script basically restarts the Atmos service and app, which I thought would have been enough, but I guess not.
[Magisk] whalesplaho:
Okay brov... Dahs tha method im still using and noticed once i disconnect headset i ll need to do it again. And also doesnt work on speaker.
[Magisk] Im_Mattgame:
Hello, for some reason after installing the module, when I try to open the Dolby Atmosphere, the app opens and then closes again.... Strange
[Magisk] imna357:
same here, used to worked=(
[Xposed Framework Modules] aviraxp:
CHANGE LOG:

1.1.1:

- Fix an incremental bug which causes many false positives

- Add system apps protection

- Add shortcut block (all credits to apsun)

- Various Fixes

1.1:

- Add more builtin hosts

- Replace regular expression with Easylist rules to improve performance

- Tweak default preferences (Hiding is disabled and WebView Block is enabled)

- Introduce element whitelist

- Implement system framework apps protection

- Various fixes

1.0.2:

- Implement aggressive block toggle

- Add XDA link and PayPal donation

- Improve blocking effect by importing blacklist from AdScanner

- Address more false positives
[Xposed Framework Modules] u7Xz:
Works flawlessly. Had some issues with MinMinGuard. I am currently using AdAway+Adblocker Reborn. Everything is perfect.
[Xposed Framework Modules] aviraxp:
Version 1.0.2 has been updated. If you meet any issues feel free to contact me.
[Xposed Framework Modules] BytesReverser:
works perfect atm,thanks
[Xposed Framework Modules] matrixrio:
works as expected. great
[Xposed Framework Modules] IgorMarinho:
Thank you for your work. Could anyone confirm if this module impact (negatively) battery duration ?
[Xposed Framework Modules] aviraxp:
From my personal experience, it does not have any evident effect on battery. But to be honest, every exposed module will affect battery since the phone now has more work to do, which is implemented by the module. I will keep the battery consumption as low as possible.
[Xposed Framework Modules] pieceofphil:
Uhm what exactly is the reason I should use this. I just tested a website for adblock check, whereas adaway active lead to first pic.

Disable adblock and enable this tool and restart lead to the second one. So obviously the ad had not been blocked by this mod.

Is your mod for ads in games or how should i understand that?

Just a bit confused, sry
[Xposed Framework Modules] kamikaze702k:
Awesome module
[Xposed Framework Modules] JoeFCaputo113:
What can this xposed module/app do that THIS APP can't? Just curious, thanks!
[Xposed Framework Modules] 1droidmod:
[MENTION=7551742]aviraxp[/MENTION] thanks a ton!! Obviously does the trick especially when it comes to being redirected to a million other places then what I clicked on. In that sense, that is something that adway does not do no matter what host file/s I use as well as adguard and minminguard. There were a couple sites I just about swore off because it was impossible to do anything as far as a navigation goes but I can do as I like now thank you very much.
[Xposed Framework Modules] aviraxp:
I guess you are using Opera, right? Opera has its own proxy solution and unfortunately it does not use the system web view, thus I cannot get it work with the same reason as UnbelovedHosts. I am still searching for more stable hooking methods.
[Xposed Framework Modules] exodius48:
[MENTION=7551742]aviraxp[/MENTION] Does this continuation of "pl.cinek.adblocker" ?
[Xposed Framework Modules] aviraxp:
Generally, yes. But his code only covers about 10% of this app. You can think this is a new app too.
[Xposed Framework Modules] exodius48:
Nice.

Just a feature request, hope this app can block all miui ads. :angel: