yashsingh1/xdaforums huggingface dataset:
[Android Software Development] Teet1:
It seems the only way to get it to flash in TWRP on the Axon 7 (on the Oreo 8.1 AOSP custom ROM named Project New World) is to do something that someone suggested in the original thread. Go to the /data partition in TWRP, and rename the adb folder (there are magisk files inside) to adb.bck and then flash the zip.

While flashing, it warns that there isn't a root solution, and dolby atmos stuff won't work until supersu is flashed but continues installation. I go back to the /data partition and rename adb.bck back to just adb.

Once that's done and booting to Android, issues occur that I explain in your other thread here. tl;dr: NO audio plays, but anything that tries to play audio creates an intense lag on the phone and the dolby app crashes when it tries to load the UI. I posted the logcat there, things to do with audioserver.

Now what I'm wondering, is this the dolby functionality that is turned off due to it not detecting a root? Audio not working and Dolby crashing? What if I do these exact steps, except before renaming adb.bck to adb again, I flash supersu instead, then will Dolby work completely?

edit: oh...actually this is interesting. So restored my system partition so my Android works but forgot to rename adb.bck back to adb. As a result, it generated a new adb folder for magisk. However, all of my apps started asking for root again and my magisk modules are gone. I rebooted back to TWRP and flashed the Dolby zip, only to find it that it successfully flashes. Unfortunately I am now met with a bootloop instead upon rebooting the device after flashing.

So yes, for me, as a result of renaming the adb folder and the zip not detecting a root solution, dolby functionality becomes limited and doesn't work. But it seems from this experience, if I had a fresh install of magisk with no modules, the dolby zip flashes like normal but I am met with the bootloop some face. With or without the added libraries in the arise_parameters.prop.

edit again: as per reading above that was ninja'd by my post there may be a module conflict that causes it to become frozen during flashing. Further testing for the Axon 7 continues.....
[Android Software Development] bkkzak:
Pixel Xl BenzoRom 8.1 Magisk 15.3

Installed as magisk module thru TWRP, Dolby app shows up in app drawer but force closes, and some magisk modules didn't load (v4a and YouTube did load, but Sony music disappeared).
[Android Software Development] Miustone:
Thanks for pointing that out and sharing Your Expierence! I will give it another try and hope i can finally test it without issues... Thanks again [MENTION=4445176]guitardedhero[/MENTION]! Very busy right now but i really have to PM You the next Days :angel:

BR
[Android Software Development] caxwan:
Have u try my post below, I have same problem before.

That happen due conflict and all module removed or not load.

https://xdaforums.com/showpost.php?p=75345538&postcount=51
[Android Software Development] guitardedhero:
No, BusyBox is perfectly fine.

And the demo is without audio for some reason, although, there has been no confirmation that the demo has audio on the native device and firmware so until such evidence suggests otherwise, this particular aspect is not considered a bug at this time.

Another instance without any confirmation of native behavior is the Power "button" icon at the top right of the Dolby Atmos™ window, so a functional Dolby Atmos™ installation is the only way to determine whether the DSP is powered On or powered Off since the icon does not change in appearance. Obviously, audible changes when adjusting parameters within the DSP window will indicate a powered On state, so you can likely see why a functional installation is required to even have the ability to make an assessment of the powered state.

Your dumpsys output is peculiar though, showing nearly nothing properly configured except for the two effects provided by this Dolby Atmos port, but this does not imply that Dolby Atmos should be functional, either.

One critical component that is still unavailable for me to assess with the dumpsys utility is the configuration of the music output_session_processing effect, which still requires examination of the audio effects configuration(s) symlinked to /system/etc, /system/vendor/etc, /vendor/etc...

Your scenario of crippled device usability and responsiveness is absolutely due to the native Axon 7 Oreo /bin/audioserver which is crucial to the functionality of this and all Nougat Dolby Atmos™ systems.

This is an incredibly difficult obstacle to overcome for the native device, albeit, with different/custom firmware, but this port's purpose is certainly to provide functionality native to your device to all other devices.

Personally, if I had an Axon 7 device in my possession, it would be on the firmware from which this port is sourced, effectively making this particular port absolutely unnecessary.

I assure you this is not an excuse to dismiss your scenario as irrelevant, but this is my philosophy regarding your and other similar device features:

If I purchased an Axon 7 (for my very own reasons), it would be explicitly because of the native audio enhancement solutions provided by the vendor, ZTE™. The last thing I would do with the device is to install custom firmware that effectively removes everything that compelled me to purchase the device in the first place. Enjoying that feature set outside of the vendor firmware is not exactly within the realm of reality unless I am mistaken. Is there custom firmware not based on the stock firmware that provides the stock feature set of the device?

How much space shows to be available in the Magisk image when you navigate to /magisk with your file manager? It seems the resizing option may not be appropriate during the installation while in recovery.

Absolutely, friend! But, as you likely already read above, I wouldn't even waste your time with your Axon 7, instead, use one of your other devices!

Of course, I would love to be proven wrong in this instance! :good:
[Android Software Development] Teet1:
Unfortunately not as if yet, a representative said the Oreo update would be released at the end of December only to be disappointed by the sudden silence of ZTE and no update. Only thing we have is the leaked Oreo rom.

I agree with you about custom ROMs and I indeed purchased it for the audio and other things. But with how ZTE has been helping with audio functionality in custom ROMs like lineage, I had faith in ZTE releasing an Oreo update soon and their word about having speedy major updates and involved in the development community which is now lacking on their part, because we need THEIR source files and THEIR help to have the custom Dolby audio on custom ROMs, as per their promise. So I expected the same amazing audio we had on stock and lineageOS on more custom ROMs and updates. But they haven't participated lately

Personally I hate how stock ROM is, though it is near stock, I prefer custom ROMs on any device. and I had hope ZTE would help us with that. I was just hoping this port would work for us. I'm sure it could with a lot of tinkering. But I know you don't have the time or don't want to spend the time making a different version for one device natively on a custom ROM. I'm sure it can be done

And no the audio being laggy and not working wasn't a result of Dolby not working for us. It was just not functioning. When it flashed successfully the second try, I was met with a bootloop instead, something others have experienced in the past which I'm sure can be fixed. I am determined as much as you are to get this working on this device. It is surely necessary to have this Oreo updated port for custom ROMs since we all want it
[Android Software Development] guitardedhero:
Yeah, reports were suggesting as late as April before an official release would be made available. Is the leaked Oreo build from which this Dolby Atmos™ port is sourced not a viable firmware solution compared to the custom Oreo rom's currently available?
[Android Software Development] Teet1:
I updated my post with an edit :) and no, it is beta. It is too buggy and based on Chinese firmware so there are mistranslations and Chinese words everywhere
[Android Software Development] Unnamedia:
I do know that, but how do i revert that?, I mean, now Magisk woulf/should work..?
[Android Software Development] CatoBass:
Tried to flash DolbyAtmos_Axon7_Oreo_20180126-6.zip in TWRP. No progress. Halt at the Dolby Atmos tekst... Needed to reboot.

I'm on Duality ROM Oreo 8.0 (Sony xz). Any suggestions?

---------- Post added at 05:14 PM ---------- Previous post was at 05:12 PM ----------

I'm not sure what's left in /system. I think aml and other audio mods are uninstalled..
[Android Software Development] NagaPujith:
Can anyone tell which works on AEX v5.1 lenovo vibe k5 plus and mention the version that works
[Android Software Development] yyz71:
DolbyAtmos_for_Oreo_20180208-3.zip working nicely on my girlfriend's Pixel Xl :good:
[Android Software Development] Zackptg5:
[MENTION=4445176]guitardedhero[/MENTION]

Updated unity installer. Fixed and improved output_session_processing which should fix the dolby not processing sound problem:

Dolby Unity

Edit: reuploaded, found issues with the spacing (yes it actually does matter in this case -_-)
[Android Software Development] xxxreyxxx:
still not processing...

currently flash it with sauron + v4a fx+ aml
[Android Software Development] Zackptg5:
aml is the problem. It has the same output_session_processing issue. Just pushed a fix now (should be up in magisk repo)
[Android Software Development] twcobra:
On 2018208-3

Running latest Validus on my OP5.

Its not completing boot.

I was able to grab a logcat.

https://www.androidfilehost.com/?fid=890129502657581803
[Android Software Development] Trupen:
Latest 1.3 installed

But now viper and dolby both not working
[Android Software Development] Zackptg5:
Can you remove them all, then install them and send the recovery log? Also, can you send /magisk aml folder after rebooting?
[Android Software Development] Trupen:
[MENTION=4445176]guitardedhero[/MENTION]

Not processing of viper is directly related with aml
[Android Software Development] guitardedhero:
I know the two available builds cause confusion and likely a sense that the Standard version is NOT capable for what AML/Unity are purposed, but ALL of my zips in the last six months are prepared to accommodate existing Magisk and /system audio mod installations in a manner that avoids "breaking" existing and future audio mod installations.

It may be necessary for me to prepare a ViPER4Android installation supporting Oreo, but you should be in fine shape with a combo of the Standard Dolby Atmos zip and a simple ViPER4Android zip supporting Oreo. :good:
[Android Software Development] sonophilos:
Presenting...

Dolby Atmos for Oreo 20180208-3 Standard - Black 'n Cheese Edition

Changes:

Updated base to 20180208-3.

Custom "Black 'n Cheese Edition" theme for Dolby Atmos apk, inspired by Swift Black.

Custom "Lover of Sound" dax_default.xml for Dolby Atmos - Music profile is preferred for intended effect but all profiles are configured differently to Dolby defaults. You can see the changes in this Google Sheet.

NOTE: If it seemed like the installation was successful, you have Dolby Atmos in the Magisk modules list and it appears in your app drawer, but it FCs, you may be able to get it working by killing the audioserver once (you may have to do this once on every boot). Enter this in a terminal emulator of your choice:

su -c killall audioserver

Once audio recovers (it will drop out temporarily when you do this) you should hear Dolby start processing before you even open it if this was successful, and it should open and respond to changes if this was successful.

As ever, I sincerely hope this helps and that the community enjoys the efforts Lennon and I have put into this project.

ADDED BONUS: For those of you who already have working ViPER4Android / ViPER4Arise 2.5.0.5 installs, you may replace your apk where it is installed with this one for a Black 'n Cheese theme for ViPER that exactly matches the conventions of the theme used for Dolby. Based on ViPER4Android FX Materialized Reconfigured and inspired by Swift Black.
[Android Software Development] DrazzEn:
pixel xl, flash,wipe cache boot fine but DA crush
[Android Software Development] Trupen:
Flashed older version of aml v1.1

Dolby and viper working fine now
[Android Software Development] yyz71:
Same here. Flashed on Pixel 2 but Dolby FC and killall audioserver didn't work either ?
[Android Software Development] guitardedhero:
Whipped up a ViPER4Android installation with the same flexibility and versatility as the Standard Dolby Atmos™ installation zip for testing. :good:
[Android Software Development] :
Thanks man. About to try it on my shamu, nitrogen 8.1.
[Android Software Development] zen2fans:
In my redmi note 4 installation

1. Install arise latest black n cheese edition : only core n magisk

2. Install v4a via magisk module

3 install Dolby latest standard version

I'm install arise only core n magisk module because v4a error I/o driver

so installed v4a from magisk and success, but after view reboot v4a asking for reinstall driver n error

Dolby installation success in twrp n booted but fc
[Android Software Development] juv3nal:
This has worked for me too :svetius:

However the latest build from this post hasn't, it kept crashing.

Thank you all for sharing.

Note: I have a Mi5 running Pixel Experience (Oreo)
[Android Software Development] :
Successful install on nitrogen with nexus 6 shamu

Weird processing... But works more or less.

Due to kernel

&

Successful install and processing stellar on screw'd Oreo for nexus 6

Works amazing on this one.

Nicely done, and thank you. Been trying to get some sounds on my shamu since going to Oreo.
[Android Software Development] guitardedhero:
You're most welcome!

I strongly suggest you download the updated zip on place of the previous one in the same post.

I had mistakenly targeted a script not included in the archive resulting with no boot script for the installation, making its functionality dependent on an existing audio mod installation providing an adequate boot script. :good:
[Android Software Development] Adamk102:
Hello I have a question. How to install on my xiaomi mi 6 android 8.0? It is possible?

Wysłane z mojego MI 6 przy użyciu Tapatalka
[Android Software Development] zen2fans:
I got this
[Android Software Development] guitardedhero:
Which zip exactly?
[Android Software Development] zen2fans:
Your latest v4a for testing in previous page

My device redmi note 4 nitrogenOS Feb patch enforcing
[Android Software Development] shantam3108:
First version that didn't bootloop for me on Kenzo. And successfully installed it. I feel the sound difference but the ui is broken i cannot see any eq changes or even on off changes in the app

But pressing on off button does in fact changes the sound quality
[Android Software Development] guitardedhero:
Please copy /magisk/viperfx to /sdcard/, zip it up, and attach it to a reply for me to examine the prepared module. :good:
[Android Software Development] zen2fans:
Ok this is for u sir ?

Can't say much my English not good :rolleyes:
[Android Software Development] FighterBoyZ:
Standard version put me in a bootloop. Luckily I had installed magisk recovery manager beforehand. I just disabled the module thru recovery. Took me a while to figure out how to work it though. What's the difference between the standard and the unity version?

Edit: nvm. I got it. It's just the installation by unity installer. It doesn't work for me. Even if I remove my other sound mod.

OnePlus 5 OOS 5.0.2 Oreo 8.0 , magisk 15.3.
[Android Software Development] xxxreyxxx:
still the same, not processing
[Android Software Development] Zackptg5:
That log is printing out a bunch of lines that aml shouldn't print out. Are you using the build from the magisk repo?

Edit: you're definitely using an older debug build. Grab the latest from the repo or aml thread
[Android Software Development] xxxreyxxx:
yes,using aml 1.3

here my install order: ainur-v4a fx- dolby atmos- aml
[Android Software Development] Zackptg5:
Uninstall them all and try again with aml here: https://xdaforums.com/apps/magisk/mod-audio-modification-library-t3745466
[Android Software Development] guitardedhero:
Standard:

Latest: 20180208-4[*]MD5: dbfe9ef75b7dbd35172498f35f844cc5

Changelog:

[B]20180208-4 -[/B]

- Minor adjustments and improvements.
[Android Software Development] guitardedhero:
Finally resolved the inefficiencies preventing this from functioning independently in Enforcing SELinux mode. :good:
[Android Software Development] ainurrofiq:
Awesome. I tried latest viper zip from arise tèlègram group, and it works, now will try this
[Android Software Development] xxxreyxxx:
Still not processing
[Android Software Development] repey6:
I checked this build now on my Redmi 4x NOS 8.1, magisk and supersu. Installation was correct with magisk, error1 in TWRP with supersu. But Dolby FC in magisk rom. Because different roms and devices have different content of etc and vendor/etc folders. Some roms have audio_effects.conf in vendor/etc , another only audio_effects.xml . Audio_effects.conf have difference between same files in etc and vendor/etc. This all create conflict audioprocessing. Need create same conditions for all roms if it possible. I did screenshots of this content. And after rename audio_effects.xml to audio_effects.xml.bak Dolby works.
[Android Software Development] Albert Poon:
Sadly, bootloop on HTC U11 stock rom with magisk 15.3. No other mods are installed. Since bootloop I cannot get a logcat, what should I do?
[Android Software Development] guitardedhero:
Please provide the entire audio_effects.xml for me to personally examine as this configuration is intended to be prepared appropriately during installation. :good:
[Android Software Development] madkiran:
[MENTION=4445176]guitardedhero[/MENTION]

Got bootloop.. using redmi note 3 (Firehound (android 8.1))

logs attached..

please make it compatible with redmi note 3

thanks for the port.. btw

edit : I installed standard package..

should I try with "unity" one?
[Android Software Development] guitardedhero:
Your particular device is intended to automatically receive the optional additional system libraries from the native Dolby Atmos firmware in order to achieve a successful device boot as well as a functional Dolby Atmos installation.

If not too inconvenient, download the Recovery Management zip tool provided in the OP's attachment section if you have not already done so.

Repeat the process you reported as preventing a successful device boot, confirm successful device boot will not result, boot to recovery using the appropriate hardware button combination for your device, and flash the Recovery Management zip tool.

Once informed that /magisk is mounted and accessable via TWRP's File Manager, do the following:

Hit Home to return to TWRP's main menu

Advanced > File Manager

Navigate to /magisk/dolbyatmos/system/lib

Produce a screenshot using the same hardware button combination that produces a screenshot while booted in Android.

Navigate to /magisk/dolbyatmos/system/lib64 and produce a screenshot of this directory's contents as well.

Navigate to /magisk

Tap dolbyatmos > folder action icon > Delete

Flash the Recovery Management zip tool once more to properly unmount the magisk.img from /magisk.

Reboot to a fully booted and functioning state and attach both screenshots to a reply for me to observe. :good:
[Android Software Development] guitardedhero:
Unfortunately, neither log contains any evidence of the port being present on the device in any form.
[Android Software Development] madkiran:
sorry, My bad

I think I produced those logs after I deleting the Dolby magisk folder . . .

I will send again, trying with unity zip..

thanks for the reply..

for confirmation..

I am taking logs from redwolf recovery (TWRP based).. are they usefull ?

edit : installation ended with ERROR 1 :(
[Android Software Development] Lopez Darren:
Are you using SuperSu or Magisk?:confused:
[Android Software Development] repey6:
Please
[Android Software Development] guitardedhero:
Standard:

Latest: 20180209[*]MD5: b0c2b668cb37e98f37d5d5de56e3daaa

Changelog:

[B]20180209 -[/B]

- Correction to typo preventing
audio_effects.xml manipulation.
[Android Software Development] guitardedhero:
/cache/recovery/last_log

:good:
[Android Software Development] repey6:
Wow! The first time Dolby earned without any dances on NOS 8.1 on Redmi 4x with magisk.:D:good:

But with supersu error1 again.:(
[Android Software Development] Adamk102:
Work on Android 8.0 xiaomi mi 6 miui 9?

Wysłane z mojego MI 6 przy użyciu Tapatalka
[Android Software Development] ashwini215:
I'm using Oneplus 5T with AICP 13.1.

Flashing the mods ( have tried most of them till the latest of today's), the screen gets stuck on boot logo.

Thanks to your recovery zip I'm able to recover every time :)

Please suggest what files would you need to hep us out.

I dont have audio_effects.xml in vendor/etc, rather I have audio_effects.conf.
[Android Software Development] guitardedhero:
Android Oreo audioserver Database

:good:
[Android Software Development] madkiran:
Unity build is working fine for me :laugh:

power button is not toggling though.. effect is working

sound is a bit low...

Thank you :o
[Android Software Development] DrazzEn:
09 works on pixel xl yeee thank you!)
[Android Software Development] repey6:
[MENTION=4445176]guitardedhero[/MENTION] some roms on Redmi 4x not have audio_effects.conf file in etc folder. In this case Dolby get FC. Solve?

I use on this roms my mod succesfully. Maybe it right solve?
[Android Software Development] ashwini215:
https://drive.google.com/open?id=1Y6GBmla95JIEDLAK3RRk2XPYfylION_t

native audioserver and firmware build.prop in FAIL audioserver folder.
[Android Software Development] mohsinreadymoney:
Flashed successfully and working fine on pixel experience ROM for redmi note 4 Snapdragon. :)
[Android Software Development] datsoy:
got bootloop on latest zip, files uploaded. :good:
[Android Software Development] guitardedhero:
The audio effects configuration preparation supports:

/system/etc/audio_effects.conf

/system/etc/audio_effects_sec.conf

/system/etc/audio_effects_vendor.conf

/system/etc/htc_audio_effects.conf

/system/vendor/etc/audio_effects.conf

/system/vendor/etc/audio_effects.xml

/system/vendor/etc/audio_offload_effects.conf

/system/vendor/etc/htc_audio_effects.conf

/vendor/etc/audio_effects.conf

/vendor/etc/audio_effects.xml

/vendor/etc/audio_offload_effects.conf

/vendor/etc/htc_audio_effects.conf

And anything else not yet known all with a single variable:

afx=*audio*effects*

If this is enough to accommodate your scenario, then this indicates an error as was recently found with audio_effects.xml thanks to your earlier report.

If so, the appropriate action would be to target and correct such an error in this case as well. :good:
[Android Software Development] repey6:
Thanks for reply. You right.:good:
[Android Software Development] bilshow:
Bootloop Samsung s8 rom rennovate ice oreo 0.5 :(
[Android Software Development] guitardedhero:
Thank you for your contribution! :highfive:

After examining your native audioserver, I have a suspicion that you may likely achieve a successful installation simply by adding the value of true to the install.add.libraries= property to /sdcard/arise_parameters.prop which should already be there waiting for you before attempting installation again. :good:
[Android Software Development] bilshow:
Bootloop Samsung s8 rom rennovate ice oreo 0.5
[Android Software Development] Hacker@1995:
Unity ver actually works on my lenovo k5 plus . logs attached
[Android Software Development] repey6:
Works with Dolby perfectly. First installed Dolby then Viper.:good:
[Android Software Development] datsoy:
sorry to tell but I still got bootloop.

please see the attached recovery log.
[Android Software Development] zen2fans:
What version u had installed?

And v4a works too?
[Android Software Development] PinoF75:
Hi to all,

I installed it on OP3 with z-unleashed rom but always stuck on boot logo.

Anyone can help me, please?