yashsingh1/xdaforums huggingface dataset:
[Android Software Development] Zackptg5:
Can you try removing everything and doing it though magisk manager? There's a ton of errors in there that leads me to believe that your recovery doesn't have a fully working BusyBox
[Android Software Development] Albert Poon:
There are some progress. First of all, standard-0209 install failed, but unity-0208-2 install suceeded and can booted into system (no bootloop), however it is not processing. In Dolby app the power button is not responding. The HTC U11's default boomsound kicks in instead. (This happened during Nougat with Ahrion's DolbyAtmos too, however, his LePro3 works flawlessly while Axon7 resulted in no processing)

Let me know what to do.
[Android Software Development] Albert Poon:
Attached the recovery.log
[Android Software Development] ZidanBlaster:
Dolby installed correctly using unity version but the app is fc

when i install using standard version with arise magnum opus the install is failed

here's the log
[Android Software Development] mohsinreadymoney:
I have flashed the latest the non unity installer one and v4a has I/O errors and does not work :good:

---------- Post added at 06:26 PM ---------- Previous post was at 06:24 PM ----------

No :( v4a does not work have I/O errors and I installed the latest version.
[Android Software Development] zen2fans:
Yeah same me too, currently in nitrogenOS
[Android Software Development] Kuljeet Singh:
Bootloop on OnePlus 3 running Oxygen OS 8.0.0. Attached recovery.log
[Android Software Development] Trupen:
Working fine thanks again
[Android Software Development] exodius48:
[MENTION=4445176]guitardedhero[/MENTION] v20180209 no sound processing on my device Xiaomi Mi A1. Log attached
[Android Software Development] Trupen:
But I have installed aml older version V1.1
[Android Software Development] zen2fans:
Success installing unity version but not processing

Here some log
[Android Software Development] xxxreyxxx:
I dont know if i'm do some mistake but its still not processing even flash though magisk manager
[Android Software Development] exodius48:
[MENTION=4445176]guitardedhero[/MENTION] Unity version 20180208-2 make my all magisk module gone after install it via twrp. Why too many error in dolby oreo? :(
[Android Software Development] veetoe:
Latest 2-9 build installs successfully on pixel 2 xl but dolby does nothing when trying to open it. Tried killall audioserver. In dumpsys it shows the dolby libraries as not loaded. Noticed in vendor/etc/audio_effects.xml that there is 6 of the exact same vlldp library entries.
[Android Software Development] guitardedhero:
Lol, I need to take a look at this. :good:
[Android Software Development] laugeek57:
20180209 -1 Standard works fine on mi A1 :D
[Android Software Development] veetoe:
So after removing the atmos module and rebooting, the atmos library entry along with those 6 vlldp library entries are still in the audio_effects.xml file. Weird. Are they written to the file permanently? There's also an audio_effects.xml.bak which looks all stock.
[Android Software Development] guitardedhero:
Standard:

Latest: 20180209-1[*]MD5: fa47c3043d91a850bcc247ee9adb6758

Changelog:

[B]20180209-1 -[/B]

- Correction to audio_effects.xml
manipulation.
[Android Software Development] guitardedhero:
The physical /system or /vendor configuration copy is only modified in /system installations and will be available in stock form as audio_effects.xml.original. :good:
[Android Software Development] jkdrinkard:
Can confirm this working 100% on my Nexus 6 running Nitrogen OS 8.1. Latest Dolby caused boot loop. Is selinux permissive required for Dolby installation/processing?

Glad to have v4a on Oreo 8.1! Keep up the awesome work!
[Android Software Development] guitardedhero:
Enforcing SELinux mode is fully supported with both Magisk and SuperSU root solutions. :good:
[Android Software Development] jkdrinkard:
I'm trying to read through everything to see what I did wrong. Is any prep required prior to flashing the Dolby zip for magisk module option on enforcing?
[Android Software Development] guitardedhero:
None. That is the default installation for Magisk users. Try using the latest zip. :good:
[Android Software Development] yyz71:
I don't know what I'm doing wrong here. But each time I install this. It FC on me. I've removed every mod installed I have. The only Dolby that works is Dolby Oreo you posted awhile back. I'm getting really frustrated with this Google Pixel 2. Don't get wrong I love this phone but hmm! I appreciate the work your doing with this port :good:
[Android Software Development] guitardedhero:
Hell, I was certain you had achieved a successful installation at this point?!!

Anything of interest when performing the auditing procedures outlined in the OP?

What does /vendor/etc/audio_effects.xml look like after installing 20180209-1?
[Android Software Development] yyz71:
The installation isn't the problem. It's the FC I encounter I will flash again and I have a look at the file :good:
[Android Software Development] Zackptg5:
New unity build is up. Added removal of sa3d for samsung device support (got afh dev approval so all unity builds will be here from now on): https://www.androidfilehost.com/?w=files&flid=247761
[Android Software Development] LKc丶:
which previous one works for you ? I'm facing FC too.The standard version keeps FC and the Unity one doesn't FC but not process either.
[Android Software Development] yyz71:
They all FC on me! The installation isn't the problem it's getting it to open is the problem..
[Android Software Development] Zackptg5:
Can you flash latest unity, then post full logcat and your audio effect files in the magisk Dolby folder?
[Android Software Development] yyz71:
Here you go the file you ask for
[Android Software Development] Zackptg5:
Well the file looks good. Can you post a full logcat and magisk log?
[Android Software Development] docnok63:
I've been following along but not posting much and flashing occasionally. I tried the 2/9 build and got stuck on bootloop with both V4A already installed and just trying it by itself. I then tried the 2/9-1 file and things got ugly quickly (Error 1.) I'll try the Unity build in a sec...
[Android Software Development] shivangswain:
I've always been able to solve problems I face with each day's build with some simple steps. Firstly, I have been installing Dolby via the Magisk Manager since the Unity builds have dropped. Secondly, This is for Dolby + Viper4Android, it may or may not work for only Dolby.

Steps:

1. Uninstall all previous versions of this mod and Viper by flashing the same version zips once again in the manager app and uninstalling AML.

2. REBOOT.

3. Wait and let all the start-up processes end. This is usually the Kernel Settings getting applied and my boot app's starting (GSam & Cornerfly).

^ I've noticed problems if you don't let this happen. ^

4. Install in this order-

Dolby (with its older build of AML/Unity) will be installed first from the Manager app.

Then install the latest AML build from Zack.

Finally, install the latest Viper4Android zip from ahrion (I am using the new driver and materialized app, so can't tell about the older driver and app).

5. REBOOT.

6. Repeat Step 3 (only).

7. Open Viper4Android first and see if the driver is installed and then open Dolby.

If for some reason Viper shows a driver installation issue or the Dolby app FCs, try reinstalling but with the recovery and flash the newer AML right after Dolby in the recovery itself (I recommend getting a log at this time just for good measure and to help guitardedhero, ofc) before booting into the system and installing Viper from the Manager app.

Event after all of this, if you still don't get something/anything working, uninstall by reflashing the zip(s) or using the Magisk Recovery zip in the OP. Also, while you are at it, post the installation recovery logs here and look if there is a new & updated zip available here.
[Android Software Development] prathu30:
Plz ignore if already reported but the app doesn't show any change in ui (the effect works) unless app is closed and reopened. Using the latest 09 build on redmi-note-4
[Android Software Development] yyz71:
Will do :good:
[Android Software Development] yyz71:
here you go
[Android Software Development] Zackptg5:
I see your using aml :)

Can you uninstall Dolby, install latest unity Dolby build ( I put it up a few posts back) and make sure you're on today's aml release?
[Android Software Development] docnok63:
I followed your steps and still wasn't able to boot. [MENTION=688191]zachp[/MENTION]tg5 , I've attached the logs
[Android Software Development] repey6:
You may to try this variant:D
[Android Software Development] sonophilos:
Presenting...

Dolby Atmos for Oreo 20180209-1 Standard - Black 'n Cheese Edition

Changes:

Updated base to 20180209-1

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.

--

Also presenting...

ViPER FX 2.5.0.5 20180209 Black 'n Cheese Edition

Changes:

Custom "Black 'n Cheese Edition" theme for ViPER4Android apk, inspired by Swift Black.
[Android Software Development] Kuljeet Singh:
Bootloop on Oneplus 3 running Oxygen OS 8 0.0. Attached recovery.log and module from /magisk folder, also i have removed dolby.apk to reduce the zip size.
[Android Software Development] Zackptg5:
Magisk log looks good but the other log had nothing in it. Can you send a full logcat?
[Android Software Development] Sandrittu:
Hi guys, I have xiaomi redmi note 4 with rom pixel experience 8.1 aosp, root magisk e busy box installed. I tried to flash the zip with twrp but it does not work. Help, thanks in advance
[Android Software Development] guitardedhero:
Downloads

:

Android File Host (gh)

Standard:

Latest: 20180209-2[*]MD5: 2309be6b275d929a8f22b1fc36b12034

Android File Host (Zackptg5)

Unity:

Latest: 20180209[*]MD5: 87762df810231060f1caf5762c89f7b8

Changelog

:

[B]20180209-2 -[/B]

- Corrections and adjustments to
/system installations.

- Automatic audioserver restoration
during all system-less installations.
[Android Software Development] yyz71:
Ok so I did a clean installation completely wiped my phone back up to my computer, wanna make sure there's was nothing leftover.

Unity doesn't work, standard boots and FC :confused: I'm uploading logs and screenshot to what's installed. Like I said earlier the only Dolby that works for this device is the one you posted awhile back. I don't know what's going on with flashing this phone with your Dolby Atmos port! I'm flashing like crazy to get this going. And your doing an awesome job with these frequent updates :good: I feel a little defeated with this :eek: But

I will keep trying and provide more logs as needed:good:
[Android Software Development] yyz71:
These work well together :good: That's your first Oreo Dolby Port ..
[Android Software Development] sonophilos:
Standard FCs for me too when I first boot, and it has for several builds in a row. However, this can be resolved for me by entering the following in a terminal emulator:

su -c killall audioserver

Audio will drop out briefly, and when it comes back in processing may already be working before you even open Dolby.

This can fix ViPER 'install driver' issues with the ViPER FX installation too (the driver is installed, we promise, it's just ViPER can't 'see' it).

Hope this helps.
[Android Software Development] Kuljeet Singh:
[MENTION=4445176]guitardedhero[/MENTION] yes your previous mod is working good, only please take a look to magisk of that mod as after install dolby doesn't come in app drawer installed with viper4android in magisk 15 sometimes, but in magisk 14 it works fine. Please ?
[Android Software Development] g3v0:
After you flash atmos and it's FCing, can you run

su -c dumpsys media.audio_flinger > /sdcard/dumpsys.txt

and upload the generated dumpsys.txt from your sdcard
[Android Software Development] yyz71:
Ok give me sec

---------- Post added at 12:27 AM ---------- Previous post was at 12:26 AM ----------
[Android Software Development] yyz71:
Here it is :good:
[Android Software Development] sonophilos:
Presenting...

Dolby Atmos for Oreo 20180209-2 Standard - Black 'n Cheese Edition

Changes:

Updated base to 20180209-2

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.

--

Also presenting...

ViPER FX 2.5.0.5 20180209-1 Black 'n Cheese Edition

Changes:

Updated base to 20180209-1 (gh's and my profiles should automatically install to /sdcard/ViPER4Android/Profile/ now)

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

Check sonophilos_README.md inside for information on getting the full intended effect out of my profiles.
[Android Software Development] yyz71:
From the dumpsys.txt it looks like the libraries are not loading :confused:
[Android Software Development] guitardedhero:
It's possible the TYPE UUID of the ds effect is conflicting with the Dolby Atmos libraries.
[Android Software Development] yyz71:
I think you might be right:good: cause installation going through. But libraries are not loading. I thought maybe I had too many conflicting mods installed. But that's not the case here.
[Android Software Development] Golv:
Success installing standart version but not processing.

I mounted Magisk and checked files htc_audio_effects.conf in /dolbyatmos/system/vendor/etc/ and audio_effects.conf in /dolbyatmos/system/etc/ and found errors at the end of these files:

\noutput_session_processing {\n music {\n atmos {\n }\n }\n}\n

I fixed them to

output_session_processing {
music {
atmos {
}
}
}

saved files and rebooted. After that, everything works as it should be.

Please check functions file in META-INF and change it in several lines from

echo "\noutput_session_processing {\n music {\n atmos {\n }\n }\n}\n" >> $cfg

to

echo "output_session_processing {
music {
atmos {
}
}
}
" >> $cfg

THX dev!
[Android Software Development] PinoF75:
Tried to install it, but it stuck on boot..

You find the log file.

Hope you find the solution
[Android Software Development] g3v0:
Disable the other dolby mod (or all other audio mods in general). Flash the latest atmos that was booting for you, then flash the attached zip. The first boot after, it might bootloop, hold the power button and restart if this is the case.

If it boots and the app doesn't FC but it's not having any effect, post your latest audio_effects.xml and dumpsys as described before

If it boots and the app does FC, enable USB debugging (Settings -> System -> About Phone, tap Build Version (last one) 7 times; then Settings -> System -> Developer Options -> USB debugging). Hook your phone up to your computer, open command prompt, and type

adb reboot && adb logcat > logcat.txt

After your phone finishes rebooting, hit Control+C at the command prompt to write the logcat to disk (it'll save it to whatever folder the command prompt is in). Upload that logcat.txt, in addition to the latest audio_effects.xml and dumpsys

If it continues to bootloop, I will be sad. Recover as described before.

NOTE: The attached zip has been tested on a grand total of one device (Pixel 2 XL) so it's dubious if it'll work on any other device (except Pixel 2). Also, this is more of a hack to get it to work rather than a real fix. Desperate times call for desperate measures.
[Android Software Development] caxwan:
Thank you [MENTION=4445176]guitardedhero[/MENTION] works perfectly..

I use unity build 2.9.18 from [MENTION=6037748]Zackptg5[/MENTION] on afh..

:good::good::good:
[Android Software Development] yyz71:
Temp zip won't flash unable to mount system error when flashing. It's just not my day today:eek:
[Android Software Development] g3v0:
That's weird. Try Mount -> System in Twrp before flashing it
[Android Software Development] yyz71:
Tried that my friend. I don't understand why it won't flash.
[Android Software Development] guitardedhero:
Lol, damnit! I just couldn't resist changing something without any need for any change lol.

Will fix right away. :good:
[Android Software Development] yyz71:
Screenshot
[Android Software Development] guitardedhero:
Downloads

:

Android File Host (gh)

Standard:

Latest: 20180209-3[*]MD5: f66638135870d25926fc1d7930a642ba

Android File Host (Zackptg5)

Unity:

Latest: 20180209[*]MD5: 87762df810231060f1caf5762c89f7b8

Changelog

:

[B]20180209-3 -[/B]

- Don't be helpful, be harmless.
[Android Software Development] LKc丶:
Here you go :)
[Android Software Development] ZidanBlaster:
Are you also install viper too
[Android Software Development] Kuljeet Singh:
[MENTION=4445176]guitardedhero[/MENTION] anything else you need to resolve the bootloop? Last working mod was DolbyAtmos_Axon7_Oreo_20180202.zip after that all bootloops.
[Android Software Development] g3v0:
Try this
[Android Software Development] yyz71:
Thank you
[Android Software Development] caxwan:
I dont use Viper.

But previous install + Ainur made bootloop, then try use with AML and reboot to recovery for wipe dalvik & cache..
[Android Software Development] yyz71:
Nope still no go.
[Android Software Development] Nikhil Thadani:
Is it available on OnePlus 3T oos 5.0.2

I am using some modules working perfectly but I can't able to Install Dolby Atmos from magisk.

Please help
[Android Software Development] g3v0:
Can you post one more logcat while it's booting up? The current one has very little (just magisk mounts which aren't too important in this case)
[Android Software Development] t0per666:
whats the difference between standard and unity? standard boots fine on Mi A1. unity cause bootloop.
[Android Software Development] kecodoc:
i can't find viper4 from magisk how to remover all file viper4 use explorer.

open viper4 message install driver I/0 error

Mỹ devices usr magisk
[Android Software Development] Teet1:
Latest Unity worked 100% on flash wihtout needing to mess with anything on a newly flashed ROM.

Funny thing is, it uninstalled my Magisk root, but the Dolby app was still installed and still worked perfectly. It's working perfectly, good job :good: all that's next is to fix the equalizer bars jumping to the music and showing the status of Dolby processing!
[Android Software Development] repey6:
[MENTION=4445176]guitardedhero[/MENTION] hi. Why all last builds(2/29+) SE have error1 in recovery on supersu roms? Please fix it.
[Android Software Development] ZidanBlaster:
Using standard latest version i got problem error 1 on recovery

I'm forgot to tell my phone was Redmi Note 3 Pro

Here's the log
[Android Software Development] arifqur:
On my 3T running Nitrogen OS, the regular version bootlooped the first time and after hard resetting it booted into the rom but no Dolby app in the drawer. Then I booted into recovery and flashed the magisk mount zip and in the magisk folder there was no Dolby folder.

After this I flashed the Unity build which booted straight into the rom without any bootloops and all is working just fine.

Thanks guys
[Android Software Development] exodius48:
[MENTION=4445176]guitardedhero[/MENTION] v20180209-3 still no sound processing here on Xiaomi Mi A1. Why? Pls respond to me. :(
[Android Software Development] spaxon:
+1 works fine

Sent from my Redmi Note 4x
[Android Software Development] Jobe1105:
Is the audio processing?
[Android Software Development] guitardedhero:
I have yet to receive a single recovery log for this particular scenario.
[Android Software Development] repey6:
Please

Sorry fix it soon
[MENTION=4445176]guitardedhero[/MENTION] ready
[Android Software Development] arifqur:
Yeah, working great
[Android Software Development] Kuljeet Singh:
[MENTION=4445176]guitardedhero[/MENTION] ??
[Android Software Development] Jobe1105:
Flashed it myself on an OP3 with NOS. You're right everything is working great :D
[Android Software Development] guitardedhero:
Downloads

:

Android File Host (gh)

Standard:

Latest: 20180210[*]MD5: 4d107f6e22019050d4dd10b2caaecf29

Android File Host (Zackptg5)

Unity:

Latest: 20180209[*]MD5: 87762df810231060f1caf5762c89f7b8

Changelog

:

[B]20180210 -[/B]

- Resolved accidental omission of
libstagefright_soft_ddpdec.so.
[Android Software Development] xN00Bx:
[MENTION=4445176]guitardedhero[/MENTION]

Dolby is not installing on my phone :(

Device: Redmi Note 3 SD

ROM: RR Oreo Android 8.1.0

Root: Magisk
[Android Software Development] guitardedhero:
Try 20180210 linked above.

If error 2 persists, provide /cache/recovery/last_log :good:
[Android Software Development] arifqur:
Try placing the zip in the root of the internal storage
[Android Software Development] ivanliao:
Redmi3 with AICP 13.1(Android 8.1),with standard bootloop, unity works perfectly.Thanks for your work.
[Android Software Development] LabLab...28:
I flashed unity successfully, no fc in app drawer i can toggle switch to turn it on. But i cant distinguish difference when it is off or on. Same audio output i think no difference at all
[Android Software Development] xN00Bx:
Tried today's update, still the same :'(

last_log

https://www.dropbox.com/s/5wqh6odzp4ted50/last_log?dl=0

Not yet working, same result.
[Android Software Development] Mike Foxtrot:
Anyone has any idea about which magisk module should i install..... Im running oreo NOS on kenzo(redmi note 3) with agni kernel
[Android Software Development] guitardedhero:
Flash again and do the following before booting out of recovery:

Advanced > Copy Log

Reboot and provide /sdcard/recovery.log.

Your log above shows no recovery activity. :good:
[Android Software Development] Kuljeet Singh:
Bootloop again :(
[Android Software Development] xN00Bx:
Here it is ~

https://www.dropbox.com/s/x6e5j1gl8utose1/recovery.log?dl=0
[Android Software Development] veetoe:
FINALLY got the dolby app to open on a pixel 2 xl. Had to move 18 different libraries into vendor/lib before the app would open. Now it opens and can see the UI and change settings but nothing affects sound output. Dumpsys shows both vlldp and cpdp effects created.
[Android Software Development] guitardedhero:
Does /data/adb/magisk/util_functions.sh exist?
[Android Software Development] xN00Bx:
YES it's there!

https://www.dropbox.com/s/ldd09srvdgg9lnm/util_functions.sh?dl=0
[Android Software Development] ikunalgautam:
wtf bootloop
[Android Software Development] OldMid:
Just finished testing all available versions on my op5t running RR, none fully bootup, any specific logs you wanna look at?
[Android Software Development] Dedojyoti:
How to please explained. On 3t nitrogen os
[Android Software Development] Jobe1105:
I don't see what needs to be explained. Just download the unity zip, flash, done.
[Android Software Development] Albert Poon:
Tried standard 0210, installed and booted successfully and no FC, but still not processing.

Attached the recovery.log