yashsingh1/xdaforums huggingface dataset:
[Android Software Development] lcsd:
One Plus 3T 64GB A3010

OOS 5.0.1 (Oreo v8.0.0)

Magisk Install => boot loop after 2 reboots

Magisk+SuperSU_RecoveryManagement ok

Logs attached

DiskInfo

--------------------------

Armazenamento Interno

--------------------------

* /persist [/persist] (/persist) [ext4]

Used: 1,1 MB, Free: 26,4 MB, Total space: 27,5 MB

* /dsp [/dsp] (/dsp) [ext4]

Used: 4,5 MB, Free: 7,3 MB, Total space: 11,7 MB

* Cache [/cache] (/cache) [ext4]

Used: 14,2 MB, Free: 233 MB, Total space: 247 MB

* /dev/usb-ffs/adb [/dev/usb-ffs/adb] (/dev/usb-ffs/adb) [functionfs]

Total space: unknown

* /sys/fs/pstore [/sys/fs/pstore] (/sys/fs/pstore) [pstore]

Used: 0 B, Free: 0 B, Total space: 0 B

* /sys/kernel/debug/tracing [/sys/kernel/debug/tracing] (/sys/kernel/debug/tracing) [tracefs]

Used: 0 B, Free: 0 B, Total space: 0 B

* /firmware [/firmware] (/firmware) [vfat]

Used: 84 MB, Free: 11 MB, Total space: 95 MB

* /config [/config] (/config) [configfs]

Used: 0 B, Free: 0 B, Total space: 0 B

* /bt_firmware [/bt_firmware] (/bt_firmware) [vfat]

Used: 128 KB, Free: 1023 MB, Total space: 1023 MB

* /mnt/runtime/default/emulated [/mnt/runtime/default/emulated] (/mnt/runtime/default/emulated, /mnt/runtime/read/emulated, /mnt/runtime/write/emulated, /storage/emulated) [sdcardfs]

Used: 49,7 GB, Free: 3,9 GB, Total space: 53,5 GB

* /system/etc/sysconfig/google.xml [/system/etc/sysconfig/google.xml] (/system/xbin/busybox, /system/priv-app/Greenify, /system/etc/sysconfig/google.xml, /system/etc/hosts, /sbin/.core/img) [ext4]

Used: 54,9 MB, Free: 35,6 MB, Total space: 90,5 MB

* Data [/sbin/.core/mirror/bin] (/data, /sbin/.core/mirror/bin, /data/user_de/0/com.topjohnwu.magisk/databases/su.db) [f2fs]

Used: 49,7 GB, Free: 3,9 GB, Total space: 53,6 GB

* System [/system/priv-app/ConfigUpdater] (/system, /system/xbin/antradio_app, /system/xbin/box, /system/xbin/nfc_trasmit_start.sh, ... /system/priv-app/qcrilmsgtunnel, /sbin/.core/mirror/system) [ext4]

Used: 2,6 GB, Free: 168 MB, Total space: 2,8 GB

--------------------------

Memória

--------------------------

* RAM

Used: 3,7 GB, Free: 1,9 GB, Total space: 5,6 GB
[Android Software Development] afcaajax:
Bootloop after installing the mod successfully. When i turn off the module in magisk manager recovery no bootloop anymore. Mod is visible in magisk manager but when i turn it on and reboot.... Again bootloop
[Android Software Development] g3v0:
For some reason the installer doesn't expand Magisk's size automatically. This was resulting in a bunch of 0kb files in the module folder, causing a bootloop. Rather than manually replacing the files after every flash, I flash this Magisk IMG Resizer tool before flashing the dolby installer in TWRP. Now it boots up fine, but the app itself still crashes.

Digging through the lib files, I've noticed that my device needs the extra libradio and libradioservice to boot, but bootloops when including libaudioflinger. The bootloops keep mentioning waiting on audiopolicy, maybe it requires an extra lib file?

I've also noticed that the installer incorrectly puts a copy of audio_effects.conf into the vendor/etc folder, where that needs to be the XML. So I ran the bash code from the installer against the XML and noticed it produced xml errors in the <postprocess> section (note the ^ and bad tags around the music stream tag):

<postprocess>
^ <stream type="music">
<apply effect="dap"/>
</stream>
<apply effect="music_helper"/>
</stream>
<stream type="ring">
<apply effect="ring_helper"/>
</stream>
<stream type="alarm">
<apply effect="alarm_helper"/>
</stream>
<stream type="voice_call">
<apply effect="voice_helper"/>
</stream>
<stream type="notification">
<apply effect="notification_helper"/>
</stream>
</postprocess>

I'm assuming the ^ is an extra error from the sed command, and that the effect should be "atmos" instead of "dap". Not sure if the music_helper should be included in the tags or be removed entirely (I removed them myself).

In regards to the app crash itself, the logcat doesn't have much to say, mostly the killed/restarted activity chatter but also:

com.dolby.dax2appUI W AudioTrack: Use of stream types is deprecated for operations other than volume control
com.dolby.dax2appUI W AudioTrack: See the documentation of AudioTrack() for what to use instead with android.media.AudioAttributes to qualify your playback use case
com.dolby.dax2appUI E AudioEffect: set(): AudioFlinger could not create effect 46d279d9-9be7-453d-9d7c-ef937f675587 / ec7178ec-e5e1-4432-a3f4-4657e6795210, status: -22
com.dolby.dax2appUI E AudioEffects-JNI: AudioEffect initCheck failed -3
com.dolby.dax2appUI E AudioEffect-JAVA: Error code -3 when initializing AudioEffect.

Googling those effect strings, I noticed the first was referring to the Dolby type (which makes sense), while the second one is a null uuid string according to this page.

I wonder if a few extra libs might help? Such as libaudioeffect_jni.so (given the above error), or maybe the libaudiopolicy libs (if libaudioflinger is a requirement).

Edit: Also, service.sh still messes with Magisk
[Android Software Development] repey6:
Hi [MENTION=4445176]guitardedhero[/MENTION]. I did DA build based on Dolby Atmos™ ZTE™ Axon 7 Oreo -20180126-6 with self additions. I checked it on 8.1 roms with magisk and supersu root on my Redmi 4x. Busybox installed. No bootloop, all work. Dear [MENTION=4445176]guitardedhero[/MENTION] i ask you check my build and if it will have right idea correct and rebuild it by modern installation. I not have enough knowledges. Kind regards.

Link https://androidfilehost.com/?w=files&flid=245731 *updatable*.
[Android Software Development] repey6:
[/COLOR]

It need to be show in magisk modules
[Android Software Development] exodius48:
Read my comment carefully
[Android Software Development] Ceejay343:
I just flashed it so not as a magisk module, and I don't use xposed. It plays nice with the standard equaliser though, next I might try viper4android magisk module
[Android Software Development] Ramakrishnan ?:
29-1 build dolby force closing

---------- Post added at 12:36 PM ---------- Previous post was at 12:04 PM ----------

And my previous comment i said dolby not proceessing sorry for that dolby processing perfectly no problem
[Android Software Development] DrazzEn:
los 15.1 piko gaaps, magisk 15.3 with no modules

bootloop on 29-1

on your build stuck on Installing DAO
[Android Software Development] repey6:
Can't be. Need little wait (less 30sec).Check your recovery. DAO=DolbyAtmos by guitardedhero without any changes.
[Android Software Development] DrazzEn:
26-6 build also was stuck on Dolby AtmosTM screen, Have waited more than 5 minutes and nothing

29-1 installed successfully and then bootloop :(
[Android Software Development] repey6:
Strange. I install my zip via TWRP. Success. Then install v4A via magisk . Success too.
[Android Software Development] OldMidnight:
Your build gives me an I/o error when trying to install driver for v4a
[Android Software Development] repey6:
You can try from here , but my v4A is not magisk module.
[Android Software Development] OldMidnight:
Yeah I tried the standalone one and the DA+V4A combo, still getting the I/o error
[Android Software Development] laugeek57:
You do not see it in magisk modules?

Use the root explorer app and delete dolby atmos files manually
[Android Software Development] repey6:
Different devices, roms - different result
[Android Software Development] yyz71:
Pixel 2 bootloop it has something to do with the audioserver! I deleted that file and it booted up. But no Dolby app..
[Android Software Development] mohand06:
That's 0644 for file (rwxr-xr-x/755 for folder)
[Android Software Development] ShadoV90:
Jesus! You're right! OK i am going to edit it :) Thanks.
[Android Software Development] svnhvn:
Do i need to flash AML again after updating?
[Android Software Development] Zackptg5:
Nope
[Android Software Development] ShadoV90:
After some investigation about static noise/hissing sounds when i am listening music (especially on low volume or on quiet parts) i figured out that new Atmos can be guilty.

When i bring back original HTC10 dolby (boomsound), sound was clear, without any static. Is there a solution for that? For now i will try to mess with dax-default.xml

My second thought is that maybe new audioflinger? Audioserver? or maybe other libs can cause that? (htc devices are treated as "must have" for additional libraries.

I don't know... But i know that Viper, Noozxide, and some other sound mods are causing that hiss/static noise in that phone. JamesDSP even cause very loud distortion. [MENTION=8383546]sonophilos[/MENTION], [MENTION=5736502]Kyuubi10[/MENTION] do you have the same sh*t with your HTC10?
[Android Software Development] Kyuubi10:
While i havent jumped ship to Atmos for Oreo quite yet, I remember this being an issue with Atmos on Nougat.

The problem is Atmos' intelligent gain boost.

To combat it just use a custom kernel which allows you to manually reduce digital gain.

Most for HTC 10 should allow nowadays, I'm on ElementalX.
[Android Software Development] CygnusHyoga:
I still can't hear any different.

Already tried U'r latest mod

Kenzo, running NOS 8.1
[Android Software Development] varun94:
[MENTION=4445176]guitardedhero[/MENTION] after installing after booting my screen is staying on black screen all the time.What should i do?
[Android Software Development] GBPackerFanForLife:
How come Dolby version from 2-12-1 only seems to work on the pixel 2 xl..Well its the only one I can get to work..
[Android Software Development] silvertrain78:
cool story bruh
[Android Software Development] yyz71:
Flash away and let me know your results :rolleyes:
[Android Software Development] Raz0rU:
RR-O

After installing DolbyAtmos Axon7 Oreo Unity 4.9.2018 the Wi-Fi module doesn't work (it is not available in settings), in case I use the original vendor\manifest.xml с android.hardware.broadcastradio, so that I get bootloop. Can I use Dolby Atmos with the working Wi-Fi? Firmware: Official RR-O v6.0.0 20180408 (OnePlus 3)
[Android Software Development] Darktron13:
Bootloop le max 2 crDroid 4.1 magisk

---------- Post added at 06:24 AM ---------- Previous post was at 05:57 AM ----------

Got it working x820

DolbyAtmos_Axon7_Oreo_Unity_4.9.2018

With Audio modification library
[Android Software Development] Zackptg5:
Updated unity dolby build to unity v1.5!

https://www.androidfilehost.com/?fid=746010030569968448
[Android Software Development] FRNKSTN:
Very nice. Congrats! :)
[Android Software Development] Adamk102:
Xiaomi mi 6 miui 9 android oreo 8.0 not work [emoji25]

Wysłane z mojego MI 6 przy użyciu Tapatalka
[Android Software Development] Zackptg5:
Updated again to unity v1.5.1 -_-

https://www.androidfilehost.com/?fid=818070582850507404
[Android Software Development] rwxr-xr-xis:
Deleted
[Android Software Development] Darktron13:
Working on Le Max 2

But when dolby is installed v4a disables the driver. Aml and acp installed all up to date.
[Android Software Development] Zackptg5:
That's a known issue. Dolby oreo doesn't play nicely with other system eqs like v4a. It's pretty much a hit or miss :(
[Android Software Development] Darktron13:
Thanks for the info im a bit new to this sound mods I've used older ones in the past.

So yeah just wanted to point out its working on x820
[Android Software Development] Zackptg5:
Updated dolby unity one more time. Fixed an old bug with audio file patching and fixed the issue where manifest.xml wouldn't be modified if in bootmode

https://www.androidfilehost.com/?fid=673956719939834406
[Android Software Development] preference:
Flashed the latest from twrp and it works (on its own). I have it installed alongside sauron and Viper but haven't tried v4a yet. I was just so damn excited. The boot locked up at first, but upon force rebooting Dolby had successfully installed. It's processing sound just fine. Gonna **** with Viper but Dolby + sauron is plenty for me, just worried I'm gonna break something in aml.

Installation: sauron, Viper, aml already installed. Flashrd Dolby from twrp and it froze boot. Force rebooted and now Dolby is processing sound.

Oneplus 5t, Oreo liquid remix latest build

---------- Post added at 03:07 AM ---------- Previous post was at 03:03 AM ----------

V4a doesn't work but honestly don't need it when Dolby / sauron are doing their thing
[Android Software Development] Ferpen:
---------- Post added at 06:24 AM ---------- Previous post was at 05:57 AM ----------

Got it working x820

DolbyAtmos_Axon7_Oreo_Unity_4.9.2018

With Audio modification library[/QUOTE]

WiFi module doesn't work after installing. I flashed the kernel again and it still doesn't work

Firmware version aosip and unity 040918 :crying:
[Android Software Development] jcmm11:
Wrong thread. This is the Dolby thread. Read the special instructions in the OP of the V4A thread.
[Android Software Development] mr.thiem:
Hi you . I can run on samsung s8. oreo Thank you
[Android Software Development] silvertrain78:
I find it really hard to believe that any Pixel 2 XL user running Magisk-rooted stock 8.1 has successfully installed this mod. I've tried every configuration tip I can find, and always get stuck at the white Google splash screen on initial reboot. Would be nice if someone who can claim success would share thoughtful, detailed instructions as to how it was done. I've seen a couple folks make claims and provide tips in a flippant manner ("do this, and if it don't work you must be a dummy" kinda stuff), but who does that help?
[Android Software Development] Destiny97:
Working in Mi 6 Global Rom 9.5.3.0 without problem. Thanks :)
[Android Software Development] mrsover:
I am have oneplus 5t oos 8.1 open beta 6 and after flash dolby l has bootloop.:(

Was also installed last version ainur viperfx and aml...

Force rebooting also was bootlop...
[Android Software Development] preference:
This is what I did

-Install sauron

-Install AML

-Reboot to recovery

-flash latest Dolby zip in TWRP

-Reboot - your phone will get stuck at boot logo

-Force reboot by pressing the power button

-This time your phone will not get stuck, Dolby should be in your app drawer

---------- Post added at 09:51 PM ---------- Previous post was at 09:48 PM ----------

Have you tried force rebooting when stuck on boot logo? Also there's a specific release that pixel 2 xl users keep posting. Find that zip and flash it fromm recovery. Look at my previous post to see how I did it
[Android Software Development] veetoe:
I've had it working on my 2 XL for a while now and I'm using stock rom with magisk, Xposed, flash kernel, and selinux enforcing. Use the 2-12-1 version, I was having issues with later builds. Flash in twrp and have the Dolby zip in the /sdcard directory, not any deeper. Also even with this version, it has a tendency to get stuck during boot for me. Some timing issue. Sometimes I'll have to force reboot literally 5 times or so by holding the power button down while it's stuck, but eventually it will boot up. There's 2 spots it can get stuck at, one at the initial Google logo screen and the other after the animation while the loading bar is underneath, if the animation doesn't appear after 10 seconds, you're probably stuck, and I'd give the loading bar 15-20 seconds, but I think Xposed delays my boot time anyways. Start clean with no other audio mods, you can worry about them after getting Dolby working first. It should boot. You can pm me if you need more help.
[Android Software Development] yyz71:
2-12-1 is the only one I find that works with the Pixel phones!
[Android Software Development] tsongming:
I use the LeEco X727 and I am currently using this version. Works extremely well, and has the built developer mode, which allow changing to permissive mode, built into the app! Amazing!
[Android Software Development] silvertrain78:
Thank you! This is exactly what I needed to hear. I searched the thread and didn't come across a zip for the 2-12-1 build. On AFH all I see is 2-12-2. Will that work?
[Android Software Development] StRomeo612:
Sauron>aml>viper>(twrp)dolby. All working very well but I can't turn on my wifi.

<<EDIT:Clear flashing from scratch>>

Wipe dalvik>system>cache>data; flashing rom>gapps>magisk>reboot

Viper>(twrp)dolby>sauron>aml

Reboot after installing one by one and when stuck in bootlogo force reboot

I have all working in LEX720 AICP 13.1 Magisk 16.0... at last.
[Android Software Development] Adamk102:
Dolby atmos the last standard version of the application work on my xiaomi mi 6 miui 9. Thanks guitardedhero !!!!!!!!!!

Wysłane z mojego MI 6 przy użyciu Tapatalka
[Android Software Development] sjamie:
I did all of the above and my device still gets stuck at the boot animation.

If I uninstall Dolby, device boots as normal. :confused:

OnePlus 5, xXx NoLimits OOS ROM, V4A 1.62
[Android Software Development] psychoela:
Have u try change selinux?
[Android Software Development] morgoth6:
It seems we both have almost the same setup (OP5, xXx 8.1) and myself always ends up in a bootloop after DA Axion/Unity installation.

I was able to get working DA by using non unity version DolbyAtmos_for_Oreo_20180219.zip and removing mentioned lines from manifest(s).xml by hand.

Some observation. Normally when system boots the /vendor is an symlink to /system/vendor, but in recovery I can see /vendor as directory/mountpoint (?) with different contents (maybe some leftovers) than /system/vendor and with separate manifest.xml.
[Android Software Development] mrsover:
I am flash all components in twrp.

The same order of install..

Force reboot by power button not solve problem...
[Android Software Development] sjamie:
If you are talking about manually removing these lines that worked to get Dolby installed and partially working (EQ bars don't move to match selected presets) but now V4A is not working. I think I would prefer to have V4A working over Dolby. :D

EDIT: I've rebooted numerous times, toggled V4A on and off and tried loading different profiles which all ended with the same result... Processing: NO

EDIT 2: Uninstalling Dolby allows V4A to properly process music again.
[Android Software Development] HC4Life:
I have the same problem, always stuck on boot with Unity version, but i will try your method.

Thx.
[Android Software Development] n1Bb135:
Anyone here experience this bug where the buttons don't refresh (kinda like you press the "reset" button to reset the equaliser but it doesn't reset until you reload the app)

Mi 6 with LineageOS 15.1
[Android Software Development] sjamie:
Unfortunately, that method did not work for me on my OP5 running xXxNoLimits. I hope you find a total solution! I'm still seeking and searching...

No, I have not tried that yet. Thanks.
[Android Software Development] Pete02:
If you click on the first AFH link in the download section of the OP and scroll down you'll see the 2-12-1 Atmos file.
[Android Software Development] silvertrain78:
I had been looking in the "Unity" section. The build Pixel 2 XL users want is 2-12-1 "Standard."
[Android Software Development] Zackptg5:
Can you post your magiskvdolbyatmos folder with that build installed so I can see the difference between it and the newest unity build?
[Android Software Development] HC4Life:
No way. It doesn't work. Unity version doesn't work on OxygenOS Android 8.1.
[Android Software Development] sjamie:
Neither does the Standard version work on my OP5. I can get it to install by deleting the lines previously mentioned from the manifest.xml but then V4A refuses to process any music from any source. I also have Sauron and AML installed.
[Android Software Development] HC4Life:
Ok, i successfuly install the last Dolby standard version, removing the famous lines from the manifest.xml, install also Sauron and AML via Magisk and flash via recovery the Dolby Atmos 20180219 version.
[Android Software Development] kowallis.r@gmail.com:
+1 on that us eq profiles won't change.
[Android Software Development] sjamie:
Does V4A process now? It doesn't work for me so I've had to uninstall Dolby.
[Android Software Development] konsolite:
I have installed with your description on Beta 6 in One Plus 5T and V4A process correctly.
[Android Software Development] sjamie:
WoW! Guess I need to trade my OP5 for a 5T. :confused:
[Android Software Development] konsolite:
Maybe reinstall V4A and AML after installing Dolby?

I need zip file for TWRP to prepare manifest file. Is anybody can help? Thanks.
[Android Software Development] sjamie:
Truthfully, I have tried every possible installation combination with no luck. Do you hear a dramatic Improvement using Dolby w/ V4A instead of just using V4A on your 5T?
[Android Software Development] konsolite:
This a bit difference, but not dramatic. If I have to choose, I will remove Dolby and left Viper.
[Android Software Development] sjamie:
Thanks for the confirmation. :D

Also, please detail the exact installation steps you used to achieve success with both Dolby and V4A. Maybe I missed something....
[Android Software Development] HC4Life:
Do you install V4A from xXx aroma installer or from XDA Labs app?
[Android Software Development] konsolite:
I have installed Sauron, V4A and AML.

My steps:

1. Modify xml manifest file.

2. Reboot into TWRP.

3. Install Dolby Atmos Standard.

4. Reboot.

After that Dolby is visible in Magisk. Later I have updated V4A and AML, because there is newer version.
[Android Software Development] sjamie:
No, I'm using the newest 1.6.3 version of V4A.

---------- Post added at 12:48 PM ---------- Previous post was at 12:45 PM ----------

Thank you. Did you have to forcefully reboot after installing Dolby? Is Dolby fully functional or do some features appear not to work?
[Android Software Development] HC4Life:
I'm using V4A 2.6.0.3 version.

My steps:

1-Install V4A apk.

2-Remove the lines form manifest.xml

3-Install Sauron and AML from Magisk

4-Flash Dolby Atmos from recovery
[Android Software Development] sjamie:
Thank you. After flashing Dolby, were you stuck at the boot animation until you manually powered off the device?

Did you flash Dolby standard (Feb 19th) or Unity (Feb 20th) version?

Please post a link to the version of V4A you're using.
[Android Software Development] konsolite:
No, don't have to force reboot. It booted first time. It seems to work everything except animated equalizer.

I had the similar issue with Dolby as you with my previous phone - Redmi Note 4X. Dolby was installed successfully, but Viper not proccessing.

For me help this:

1. Install Dolby via TWRP.

2. Reboot.

3. Install Viper via Magisk or TWRP.

4. Install AML as above.
[Android Software Development] HC4Life:
I'm using Standard.

https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
[Android Software Development] sjamie:
Are these the lines you removed from manifest.XML?
[Android Software Development] HC4Life:
Yes.
[Android Software Development] Ferbee:
I know this seems practically impossible from my screenshot, but would we be able to edit the audioserver ourselves into adding the code it needs?
[Android Software Development] Suku1509:
Turn on compitable mode on then restart it will work
[Android Software Development] GBPackerFanForLife:
Alright I'm on a Pixel 2 XL using Nathan kernel on Nitrogen ROM.What exact steps will work or should to install Viper an Dolby an what versions work..I have tried so many different ways starting to drive me nuts..
[Android Software Development] sjamie:
Turn on compatibility mode in Dolby or Viper?
[Android Software Development] IThinkALot:
Hi! Can someone help me? So I install viper4android fx unity first using magisk and it's working fine but I want viper4android + Dolby Atmos combination and so I install Dolby Atmos unity but when I reboot after, I can't see Dolby Atmos at my app drawer and it says "module will be updated at next reboot" in magisk and so I reboot but nothing happens, I install audio modification library on magisk, but again, nothing happens.