yashsingh1/xdaforums huggingface dataset:
[Android Software Development] Zackptg5:
;)

Dolby Unity has been updated to unity v1.7! See unity op for changelog (full compatibility with magisk 17 and stuff)

Same link as always: zackptg5.com/android.php#dolby
[Android Software Development] Wolfcity:
Sadly Dolby still doesn't work, it isn't visible and Viper disappears also from the launcher.

They both still appear in the Magisk Manager but other modules like Terminal Debloater or App Systemizer are also shown there but doesn't work anymore.

Strange enough, if I uninstall Dolby all modules start working again. Viper has to be uninstalled/reinstalled once because it produces the driver error but after that it's ok too.

If I can help you with some logs just tell me what you need.
[Android Software Development] Zackptg5:
Are you using aml? I just updated aml now to new magisk template so maybe that will help.
[Android Software Development] Wolfcity:
Yes I do. Will give it a second try.
[Android Software Development] Wolfcity:
Same result. Tried flashing the mod through TWRP and MM.
[Android Software Development] mdimarucot:
The latest update works fine and the icons show on the app drawer on my device with magisk 17.1.
[Android Software Development] FireFenix76:
Same here :/
[Android Software Development] the show stopper:
New update doesn't work either with 17.1 :/ and if i try to go back to 16 i get error saying magisk not installed ????
[Android Software Development] RKRN3@1997:
You first uninstalled both Dolby and AML and then flashed them in same order?
[Android Software Development] mdimarucot:
Uninstalled dolby, reboot, after bootup, dolby is gone then I installed the latest. I'm not using AML.
[Android Software Development] RKRN3@1997:
Did the same now and it works. Thanks.
[Android Software Development] MMWolverine:
I am getting a bootloop with the latest version. My config OP5 OOS 5.1.5, Magisk 17.1, installed ViPER4AndroidFX working fine so do other Magisk modules. I tried different combinations: flashed in MM and TWRP followed by AML. Recovery log attached, Magisk log showed that arise_parameters.prop cannot be written - read-only file system.
[Android Software Development] AlexCmb:
I have try Dolby Atmos on OOS Beta, bootloop for me too. Next, I make a clean install with all wipe and reinstall dolby Atmos and it's ok.
[Android Software Development] MMWolverine:
Yeah, maybe I messed up sth when updating Magisk. But since I did a full wipe not long ago, it's just too much of a hassle restoring my config and all the apps. V4A + Eqfy app is enough of an audio quality boost. :D
[Android Software Development] Flounderist:
It's working on Sony xPeria Z (yuga) running LOS 15.1.

It is normal I get 2 app in drawer? One is for audio mode (music or theatre) and one for Dolby itself.
[Android Software Development] Aremeyr:
My dolby stop working once the screen is lock Any idea why? I have to connect disconnect my headphone jack and start Spotify again to make dolby works..
[Android Software Development] mervluk:
Magisk 17.1 with AEX 5.8 Oreo rom seems to have some incompatibility with this modified Dolby. V4A, Dolby and AML all install normally in that order, with nothing untoward in logs, but neither Dolby nor V4A appear in the app list, although shown as active in Magisk.

However, disable Dolby and V4A reappears and works normally, including the driver without the need to reinstall. Unlucky, I suppose. I'm OK with V4A or Dolby though would prefer the latter's sound volume, getting a bit hard of hearing with age. Just Dolby without V4A doesn't work either.

By the way how do you tell you've the latest dolby from the download link, as they all come out as the same February version?

PS I did use the "new" link a few pages back, too.
[Android Software Development] tcat007:
The link I pulled says Dolby-Atmos-Axon7-Oreo_09.02.2018.

I don't think the link in the OP is updated, I went with the link a few posts back. Hardly matters since it doesn't work on my 5t either. I'm happy with v4a alone. Plenty of volume and great sound.
[Android Software Development] Wolfcity:
That's almost the same what happens to me. Also magisk 17.1 and AEX 5.8. As there are several users having module problems with 17.1 my first thought was that it's a magisk issue. But as you are running the same ROM it may be worth trying another one. All in all it's really a strange bug.
[Android Software Development] mervluk:
I use legacy phones as music players so have no alternative Oreo ROM. But with Magisk 17.1 on LOS 14.1 (same V4A, different Dolby) the same issues don't occur.
[Android Software Development] tsongming:
You must root or you can't have Dolby. Use magisk 17.1
[Android Software Development] ycyIOU:
use magisk17.1 On MIUI10 The version of 09.02 has no icon display use The version of 5.7.18 An icon is displayed and opened successfully, but it does not take effect

Is there any way to solve this? The version of 09.02 Cannot be used in MIUI10.
[Android Software Development] ikepo:
use magisk17.1 The version of 09.02 has no icon display on MIUI10
[Android Software Development] tsongming:
I used the Leeco pro 3 version from Magisk 17.1 downloads in Miui 10 without any issues.
[Android Software Development] Wolfcity:
Maybe it's the combination of the Oreo port and magisk 17.1. For me the Nougat Dolbys were always more stable than the Oreo one. I will try some different ROMs to check that out.

Edit: I found a Dolby module that was originally made for Nougat and Axon device (I'm using it on a Moto G Titan) but is working on Oreo too, at least if I flash it through TWRP or MM it's available and other modules like Viper are still visible and working. I haven't tested it completely, it doesn't seem to work too well with Bluetooth (Audio Compatibility Patch may help) but everything else is fine. Here's the thread I found it:

https://xdaforums.com/axon-7/development/unofficial-lineageos-15-1-zte-axon-7-t3800214/post77155571

I post this primarily because it may help [MENTION=6037748]Zackptg5[/MENTION] and [MENTION=4445176]guitardedhero[/MENTION] in future development.
[Android Software Development] mervluk:
Yep, the old Dolby Digital Plus and latest V4A, with Magisk 17.1 and AML 1 8.1 all seem to be working together too on my old moto g running AEX Oreo. Now just to try and optimize the audio, again.
[Android Software Development] gokart2:
[MENTION=4445176]guitardedhero[/MENTION] Hey dude, been awhile. Broke the one phone, had to rock an unrooted G4 until I could afford a new one. Grabbed a Moto Z2 Force for cheap. Anyway, been figuring out this whole new a/b partition and boot.img/recovery crap for the last two days. Believe I'm up to speed. Then took a bit to get a working v4a. So i currently have latest ARISE offering, a working v4a, and permissive selinux. Flashed this wonderful Atmos concoction you mixed up here and am getting FC's. Went through the logs but can't make sense of any of it. Any help is greatly appreciated. :good:
[Android Software Development] gokart2:
Figured it out. Vendor libs never got installed.

Edit: [MENTION=4445176]guitardedhero[/MENTION] So going from that G4 with no audio mods to now.... Day and night difference through my car system. You are ****ing amazing dude! Thank you once again for all of your hard work, it is GREATLY appreciated.

As for the missing libs, I'm sure more may have been missed. Going to go through it either later today or tomorrow.
[Android Software Development] King Zlakh:
here is a way around and it's simple

a way around

when i flashed a new rom and installed the latest magisk i found that the dolby icons not shown in the app drawer

so first i went to recovery and wiped everything , and re flashed the oreo 8.1 aosb extended rom after the rom started

i downgraded magisk zip to the (1600) version 16.0

and the magisk manager to v5.8.0

Magisk older ZIP from here : https://www.androidinfotech.com/2017/07/magisk-versions-download.html

Magisk manager older version from here : https://magisk-manager.en.uptodown.com/android/old

then flash the permissive module

and last thing is flash the dolby atmos module from magisk

then reboot and u good to go , the icon will appear in the app drawer once again

then if u upgraded the magisk managaer or flashed the latest magisk ZIP, the icons will not disappear

i just ignored upgrading it's not necessary for me :D

thanks
[Android Software Development] gokart2:
Swear I'm probably the only one still rocking SuperSU.....lol.
[Android Software Development] mdimarucot:
I just noticed that the Dolby app has data usage around 300+mb since it was installed without any permissions. Is this normal or just an error from the device?
[Android Software Development] nikola87:
On my p10 lite after installing dolby in recovery now goes into bootloop or better remains on the huawei screen indefinitely, is there a possibility to restart it without erasing everything?
[Android Software Development] bananaci:
I ve got bootlop to.Installed this with magisk.

So how can i uninstall this with twrp 3.2.30.

My phone is Redminote5 pro with LineageOS 15.1
[Android Software Development] Flounderist:
Just reflash the same file on twrp
[Android Software Development] bananaci:
1-First I re-installed my OS not chancing bootlop continue.

2-Second I tried my luck with this Tool Magisk Manager for Recovery Mode (mm) [2018.8.1]

from here:

https://xdaforums.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165

So I could delete this module and I am lucky now.
[Android Software Development] arpanbag1996:
Anyone got any working Dolby on Android 9.0 Pie?
[Android Software Development] matt1313:
I have noticed when installed it crashes audio.server on pie
[Android Software Development] Rhaegar85:
Only on Pixel XL so far. Dolby crashes on Syberia rom atm. Only Viper is working. Waiting patiently for Dolby Devs, it will come soon enough. :)
[Android Software Development] dt0807:
Whoa. Success with the latest build 20180201. I'm on the latest DU v12.0 RC build for the OnePlus 3T, with Magisk v15.3 and ARISE Magnum Opus 20180105 (core and V4A only) installed

No bootloops. Dolby Atmos finally appears in the app drawer. No FCs. And it works simultaneously with V4A. I have the SELinux mode is set to permissive, because this is required for V4A to process in Oreo. This does not seem to conflict with any of my other Magisk modules. Nicely done :highfive:
[Android Software Development] guitardedhero:
Changelog

:

[B]20180202 -[/B]

- Corrected a critical error recently
introduced by "reckless thumbing"
to the audio effects configuration
operation for /system installations.

- The Magisk binary's --mountimg
function is once again used for
mounting the Magisk image volume
if the standard mount attempt is
unsuccessful.

- Various enhancements.
[Android Software Development] Trupen:
Still 29 and 30 build is only working latest 2-2 is not working stuck in recovery
[Android Software Development] guitardedhero:
Damn, what am I missing??
[Android Software Development] sirioo:
wow WORK..... Module Ainur Sauron + AML 2.3 + Viper4 2.3 + Dolby Atmos 2.5 . With Magisk 15.3 + Oreo 8.0 (LeeDrOiD U)
[Android Software Development] repey6:
How you it? What firstly , then etc. As you wrote? Please.
[Android Software Development] sirioo:
1)Module Ainur Sauron

2)Reboot

3)install from twrp Viper4 2.3 (driver 2.3)

4)Reboot

5)install from twrp Dolby Atmos 2.5 (20180202)
[Android Software Development] droidphile:
Anybody got Viper and Atmos working together on S8/S8+ running oreo beta and magisk (selinux enforcing)
[Android Software Development] Trupen:
Pls make the build similar like 29 and 30 they are working good but your latest zips are getting stuck in recovery
[Android Software Development] ShadoV90:
On my HTC10 System booted successfully but... Unfortunately atmos don't want to cooperate. I catch log from matlog. I don't know how much it's helpful. But take a look please.
[Android Software Development] agungh:
yes, work for my device. thanks bro.
[Android Software Development] jandia7381:
Y i got this dev? Never happen before, updating from build 01.02
[Android Software Development] Awais Bhatti:
01022018 pass the recovery but bootloop occur
[Android Software Development] RogerF81:
"Listen to the Dolby Atmos™ Difference!" and then a parody of Ed Sheeran? :D
[Android Software Development] Awais Bhatti:
Same happened

Build 02022018
[Android Software Development] bruceutut:
I use op2. and before 0202 build, I can flash in as magisk module, but fail to boot up

as for 0202 build, I cannot flash in. Stucked at "Dolby Atmos"

Where i can find installation log?
[Android Software Development] lcsd:
Magisk Install fully working! Great job.

All troubles seems to be related to magisk not working in recovery.
[Android Software Development] lcsd:
Dumpsys log attached. All libs loaded ok now.
[Android Software Development] Spaceboy60:
Seemed to install OK, no error messages and it shows under magisk modules, but apk hasn't been installed. Tried extracting the apk but it won't install ("app not installed" error).
[Android Software Development] Rhaegar85:
I'm able to install properly and it worked briefly on sGSI but on Sybeia it installed correctly but never opens, always crashes. Would it help if I debloat music fx first and then install Dolby? Last when I flashed AML after Dolby it's not patching anymore
[Android Software Development] Spaceboy60:
Ok, here is install log for what is worth.
[Android Software Development] Knuxyl:
Ironically does not work on Axon 7 8.1 . Seems as though latest Magisk has caused problems with it.

I am on A2017U AOSP Extended 5.7 Oreo 8.1 with Magisk 17.1.

This used to work, doesn't now.

It will install right after installing a rom and magisk (before booting), but crashes when trying to load it (both apps).

If I do a clean rom install, boot it, restart to TWRP, and try to flash it, it comes back with an error about not able to mount magisk img after sitting on "Dolby Atmos" text for like 5 minutes.

I cannot install the standard version from Magisk Manager, it does not recognize it as a Magisk module.

Flashing and installing through Magisk Manager the Unity version has no problems, however the apps do not install, even though Magisk shows it in installed modules.

Any advice?
[Android Software Development] Spaceboy60:
Running exactly same ROM version and Magisk version as you. Only tried installing the unity version and as you say seems to install without issue except the fact the apps don't get nstalled.

Gonna have to try standard version, see if I get same results as you.
[Android Software Development] Aremeyr:
My only problem is it stop working once i turn off my screen.. only occur if i uae headphones and not Bluetooth Device
[Android Software Development] NagaPujith:
Not only Dolby Atmos but other modules like YouTube also not working with latest magisk v17.1. I think it's the problem of magisk
[Android Software Development] Spaceboy60:
Get the following error trying to install the standard one :

tmp/updater: line 86: awk: not found

CANNOT LINK EXECUTABLE "/data/adb/magisk/magisk": "/system/lib64/libsqlite.so" is 64-bit instead of 32-bit

Aborted

CANNOT LINK EXECUTABLE "/data/adb/magisk/magisk": "/system/lib64/libsqlite.so" is 64-bit instead of 32-bit

Aborted

! /data/adb/magisk.img mount failed...

Updater process ended with ERROR: 1

Guess only works on 32 bit builds, although no idea why it can't mount /data/adb/magisk.img
[Android Software Development] lilbrat:
Sorry but that's a bit of a generalization, as I'm not having any issues, so to say it's an Magisk 17.1 without any logs or no general info about your phone setup is a waste of time..mini rant done.

Oh and my phone info.. Sony XZ, ExsitencZ Rom, latest Orea with Aug. update and well modded and debloated..
[Android Software Development] Wolfcity:
That's interesting. I have almost the same problem like others here, when Dolby is installed it's not visible in the launcher, it only shows up in Magisk Manager and so does Viper. Other modules like Terminal Debloater stop working too.

I realized that a lot of people with that problem are on AEX ROM so maybe it's something related to the combination of Dolby, Magisk 17.1 and ROM.

As written in an earlier post I found a Dolby mod made for nougat that is working with the combination of 17.1 and AEX so the Dolby Oreo port has something to do with that whole issue.
[Android Software Development] lilbrat:
Now I will say that I did try to install the latest Dolby before updating to 17.1 and it didn't show up anywhere or in manager or my app drawer.. So I deleted Dolby, AML completely did a direct install of 17.1 then installed the latest Dolby, AML module and all worked fine.. But my mini rant was more directed at folks who say something not working but not providing and basic info..
[Android Software Development] Toni Moon:
There are any developement for android Pie?
[Android Software Development] llmiller:
Good night

I'm having a similar issue with Dolby Atmos for Oreo not showing up in the app drawer as motioned above.

When ever I install Dolby viper app disappears also but everything shows up under modules.

I'm using magisk 17.1 with Samsung s7 aosp rom .

Any assistance will be appreciated.
[Android Software Development] mdimarucot:
Uninstall the module then reboot. The app should be gone in the app drawer then install the latest zip in magisk manager then reboot again. The app will show in the app drawer. This worked on my device with 17.1.
[Android Software Development] FireFenix76:
not finding any solution.

tried reinstalling magisk, reinstalling dolby, reinstalling everything, didn't work.

the only solution i've found is a factory reset + installing a previous version of magisk 17.0 (magisk 16.0 my choice)

after you install magisk 17.1 everything fails with the dolby atmos module. there has to be a file avoiding the module to work properly.

i'll be checking everyday this post until we can find a solution.

I'm using PixelExperience 8.1 for Moto G5s Plus (sanders)
[Android Software Development] Knuxyl:
I can confirm that Magisk 17.1 breaks a lot of compatibility with modules. The two I know do not work anymore are the Youtube Vanced and Dolby Atmos (from this thread) modules. Downgrading to 16.0 Magisk and using Manager 5.8.0 to install these modules will fix this issue, and then upgrading to Magisk 17.1 won't cause any problems afterwards (that I have noticed).

I checked the updater script and looking at the mount_magisk_img function it seems to be way over complicated. I'm not sure if this function is provided by Magisk or if the developer of this module wrote it, but this function is where the script fails installing from TWRP on Magisk 17.1. I'm betting it is provided by Magisk and they might've provided an updated function and developers haven't updated yet. I'm not sure, but a compatibility issue like this should been advertised more from Magisk developer because I've heard nothing about it.
[Android Software Development] Zackptg5:
Which zip are you talking about? The unity zip uses the img mount function from magisk install already on the device
[Android Software Development] lilbrat:
Folks, I said this once if you don't provide any info, rom you're using or stock,. logs, etc its just a wasted post as the devs to the best of my knowledge aren't mind readers.. But then again we can play bull**** and I'll call your bluff.. All working fine. ExzisrencZ rom, latest oreo on my Sony XZ, Aug. Security update.. latest updates for Dolby, Vance, AML and Magisk Manager and 17.1..
[Android Software Development] Prince Jhamat:
Will it be coming to android 9 ? It's the only reason i'm using oreo rom.
[Android Software Development] Zackptg5:
Pushed a minor update to dolby unity: Fixed an old bug in post-fs-data script that could break the mod on some devices

zackptg5.com/android.php#dolby
[Android Software Development] Willchi:
Just try it for my poco f1 and got bootlop :(

I'm use magisk 16.7 and try downgrade to 16.0 or upgrade to 17.1 still bootlop, change beetwen standard and unity still bootlop. Any advice for me?

Thank you anyway and sorry if my english is broken.
[Android Software Development] Soumy1234:
I installed Atmos and Viper (BnC editions), Audio Compatibility Patch and AML (Audio Mods were installed in TWRP and Patches were in Magisk) using Magisk 16. I installed each mod in that order with one reboot between each. After, I updated to magisk 17.1 and added this script to get Viper supported:(https://xdaforums.com/android/general/viper4android-dolbyatmos-android-t3815092).

Now, Dolby seems to work, but Viper still says "no process". Can anyone help?
[Android Software Development] Animouse31:
Can someone confirm if this Dolby Atmos for Oreo is working on Masik U Final or Masik X 1.0?

How you install it?

---------- Post added at 02:47 AM ---------- Previous post was at 02:47 AM ----------

What is YouTube module you mentioned?

This is interesting!
[Android Software Development] stibich:
Sorry, English, I'm using a translator.

I was able to install using this method.

1 - Installing the Magisk 16.

2 - Then the Dolby.

3 - Then you can upgrade the Magisk yourself.
[Android Software Development] NagaPujith:
YouTube repo
[Android Software Development] Verlaski:
works fine on Mi 5 with MIUI10 android 8.0

bootlooping on Mi 8 with MIUI10 android 8.1
[Android Software Development] Flounderist:
Latest build FC on Sony Xperia Z (yuga).

Is there any chance to get the [MENTION=8383546]sonophilos[/MENTION]' black'n'cheese edition working?
[Android Software Development] Wolfcity:
I think you're in the wrong thread for the sonophilos builds. Arise thread should be the place to ask for that because these builds are themed arise mods.
[Android Software Development] sonophilos:
You are incorrect, sir. I have been posting my Black 'n Cheese Edition builds of this Dolby Atmos for Oreo version in this Dolby Atmos for Oreo thread for some time. As soon as I have zackptg5's updates fully working on my own device, you may rest assured there will be an update for BnC Edition, and it will be posted here.

Hope this helps. :good:
[Android Software Development] Wolfcity:
Good to know. Sry, I don't wanted to misinform, I've been a long time on Magnum Opus and earlier Arise builds before I switched to Magisk modules and remembered your special builds from there. Will have a look for your update here. Keep your great work up.:good:
[Android Software Development] anttaz:
Thanks

Working fine on OP3T OOS OB 30 running in unity with V4A and DTS
[Android Software Development] Verlaski:
same issue with my device which is Oreo 8.1 as well.
[Android Software Development] JMaio:
Really love this port! Just wanted to mention that it doesn't seem compatible on higher versions of Magisk - it works on 16.0 and 16.3, however I could not get it to work on 16.7.

I thought it'd be worth mentioning because there's no obvious reason to me why that would be the case, and I don't recall any mention of this on the OP.

(OnePlus 3 - OOS 5.0.5 / Magisk 16.3)
[Android Software Development] Zackptg5:
Worked fine on 16.7 for me
[Android Software Development] JMaio:
When using 16.7, the application icon doesn't show up for me...

The only variable is Magisk so it may be specific to OP3 / OOS
[Android Software Development] Animouse31:
I need to think twice before installing this.

You just install it directly using TWRP or Magisk?

Without any other audio modules?
[Android Software Development] Wolfcity:
There are two versions in the op, one unity build and one normal build. Both are flashable through TWRP or Magisk Manager. The unity version is meant to work with other unity modules like Viper. If you install more than one audio mod you need to install audio modification library (also in the Magisk Manager download section) too. That one patches the other audio mods to be able to work together.

To uninstall a unity module just reflash it.

You can get the latest unity build of Dolby here:

https://zackptg5.com/android.php#dolby
[Android Software Development] Jbb3393:
Hey there! I have an HTC U11 and can't seem to get any of these to work. Flashed the latest from 09.07.2018. installs fine, I even I stalled aml after. Attached at a logcat, anyone please lemme know what I need to do to get Atmos working, I sure miss it. Thanks