yashsingh1/xdaforums huggingface dataset:
[Android Software Development] OldMid:
This seems almost 100% correct based on what I've tested
[Android Software Development] exodius48:
From the link and from your screenshot, v4a that you've installed is not magisk module, right? If so, it will install inside system instead of /magisk partition.
[Android Software Development] diculess:
Using the standard version would be okay for my Pixel 1 worked fine after uninstalling the unity version, except for the delay of UI elements that both the power button and the reset button reveal their actual status only after relaunch the app.:laugh:

It seems that the author has found out the error and fixed it. (See page 72 #713)
[Android Software Development] nithin1999:
Anybody give me the download link for the latest version
[Android Software Development] 127cwho:
Lmao, see op

https://androidfilehost.com/?fid=673956719939818767
[Android Software Development] nithin1999:
I clicked it but it takes me to YouTube page
[Android Software Development] 127cwho:
Well, you must press on the something wrong

Here than

https://androidfilehost.com/?fid=673956719939818767
[Android Software Development] nnmanobala:
Viper4Arise FCs upon opening it. How to resolve it? Running 8.1 AEX on Mido with Magisk 15.3
[Android Software Development] Zackptg5:
Well something is going wrong then cause they have the same audioserver file in the installers. I'll look into it further, thanks!
[Android Software Development] shivam kapoor:
Great work bro [MENTION=230538]guitar[/MENTION]dedhero
[Android Software Development] crackerjack1957:
Got an issue on Pixel with breaking Magisk root after a period of time after installation. Have had stock 8.1 for 2 weeks with no issues until installation of latest Dolby Atmos Oreo with GH version of Viper4Android (only one that I could get to process along side DA). Going back to DA only without V4A to see exactly what is breaking root.

Anyone else have this issue?
[Android Software Development] AquaBytez:
The magisk scripts time out, that's why you lose root. Try rebooting multiple times, and you'll see that some things work and others don't depending on what times out
[Android Software Development] Flounderist:
Dolby Atmos for Oreo 20180210 Standard - Black 'n Cheese Edition

Hi [MENTION=8383546]sonophilos[/MENTION] and [MENTION=4445176]guitardedhero[/MENTION], I tried to install this mod on my xperia Z running unofficial LOS 15.1 and Magisk 15.3 and I had bootloop.

Once restored, device won't be boot up, it hang on Sony logo.

I had to dirty flash ROM again to get device fully working.

Any suggestion?

An older build is working good on device, but it is too loud and I get some distortion on highest volume.

I will try standard 20180210 build later on for a comparison.

EDIT: I extracted arise_parameters.prop from zip in download folder, then i dirt flashed ROM and Dolby. It installed and it is working, but as a system app.

I deleted arise_parameters.prop, then i dirt flashed ROM and flashed zip, but it gave me a bootloop again.

Is there any workaround to install mod as a Magisk module without performing a clean flash?
[Android Software Development] veetoe:
Here you go. This is with the 9-2 update and the required libs copied to vendor from system in order for atmos to open but doesn't process sound.
[Android Software Development] g3v0:
Try this, it works on my Pixel 2 XL. Only issue is that viper doesn't process bluetooth while atmos is working
[Android Software Development] veetoe:
Can confirm this works on my pixel 2 xl man, awesome! Atmos is processing the sound. Thanks! So it looks like it needed the postprocess entries added to the audio_effects.xml file. Are you using the viper from this thread? Also do you get the UI not refreshing bug in atmos?
[Android Software Development] yyz71:
What's the difference with the pixel 2 Xl and the pixel 2 when it comes to installing this?
[Android Software Development] veetoe:
What step do you get to? Atmos installs and FC or atmos installs, opens and doesnt process?
[Android Software Development] yyz71:
FC
[Android Software Development] guitardedhero:
Very interesting. I had irresponsibly assumed all audio_effects.xml configurations included a postprocess section and I am surprised it took this long for me to become aware of this mistaken assumption.

Thank you for providing that file and I will accommodate this scenario in the very next update. I have been busy with my son's basketball tournament games this weekend (he's a baller, man) so just bear with me or make the necessary manual adjustments until an automated solution is available. :good:
[Android Software Development] veetoe:
I had to copy/paste a bunch of libs from system to vendor in order to get atmos to open successfully. This wasn't getting done during the twrp installation for me. Might be your problem.
[Android Software Development] OldMid:
Gonna leave these here in case they help
[Android Software Development] guitardedhero:
Downloads

:

Android File Host (gh)

Standard:

Latest: 20180211[*]MD5: 4bc47f4604bd2a2c90fd922f37d1d9fb

Android File Host (Zackptg5)

Unity:

Latest: 20180209[*]MD5: 87762df810231060f1caf5762c89f7b8

Changelog

:

[B]20180211 -[/B]

- Accommodation for audio_effects.xml
configurations lacking
<postprocess></postprocess> section.

- Adjustments to boot scripts focused
on device boot success.
[Android Software Development] guitardedhero:
There is no installation operation moving existing libraries from /system/lib to /vendor/lib, what libraries have proved to be necessary in /vendor/lib that originate in /system/lib? :good:
[Android Software Development] veetoe:
With a pixel 2 xl. I ended up copying these libs from system/lib to magisk/dolbyatmos/vendor/lib. I didn't mess with lib64, not sure if it matters, as dolby is opening now. Dolby wouldn't open prior to having these in vendor/lib. Not sure if it matters but the permissions on them all are 0666.

Edit: Just changed them all to 0644 permissions and seems to be fine.

libaudioclient.so

libaudioflinger.so

libaudiomanager.so

libcamera_client.so

libdlbdapstorage.so

libdlbsservice.so

libdlbmemoryservice.so

libdlbnativeservice.so

libicui18n.so

libicuuc.so

libmedia.so

libmediadrm.so

libmediametrics.so

libmediautils.so

libmemunreachable.so

libnbaio.so

libradio.so

libradioservice.so

libserviceutility.so

libsonivox.so

libstagefright_soft_ddpdec.so
[Android Software Development] AquaBytez:
Bootloop. Maybe its because my ROM doesn't have an audio_effects.xml, but rather an audio_effects.conf
[Android Software Development] exodius48:
I don't know, i do not use viper4arise
[Android Software Development] yyz71:
I could confirm this works on my Pixel 2 :good:
[Android Software Development] guitardedhero:
I can assure the reason for your failed boot is something other than audio effects preparation.

Have you previously obtained a successful device boot after installing a previous version of this port?

Is this audio effects configuration content with or without an existing installation of this port, and if so, where is the precise location of the audio effects configuration from which this content was copied?
[Android Software Development] AquaBytez:
Yes, all versions of this port work on the NitrogenOS ROM (only the builds after 09 process if installed alongside Viper however). I recently switched back to ResurrectionRemix and not a single build of the mod has worked. I'm clueless as to what the problem is.

This audio effects config file is without an existing install of the mod, the file, however, doesn't seem to be touched by the Dolby installation at all.

Edit: The audio_effects.conf file is both under /system/etc/ and /vendor/etc/. The files are identical.

Another odd thing is that if I don't mount /magisk/ before installing the standard edition, the installer will think that a magisk install isn't present, this obviously not being the case.
[Android Software Development] onliner:
Finally booted, thanks for you amazing work!

:highfive:
[Android Software Development] Adamk102:
Is this mod work on xiaomi mi 6 miui 9?

Wysłane z mojego MI 6 przy użyciu Tapatalka
[Android Software Development] guitardedhero:
Before performing operations on the final locations for this many native files, I want to ensure that at least one of you has previously tried moving/copying only the Dolby files in this port to /vendor/lib or /magisk/dolbyatmos/system/vendor/lib without the success reported for the full list you guys have provided and confirmed. :good:
[Android Software Development] g3v0:
To be honest, I never got Viper working with Atmos. Occasionally after messing with some settings I could get both to work on the internal speaker, but when I connect to bluetooth, if Atmos is processing, Viper doesn't, and if Atmos isn't working/loaded, then Viper does. I'm not too worried about it though. I use a slightly tweaked version of sonopholis's dax_default settings, and Atmos sounds better than anything I could muster with Viper convolvers/settings.

And yeah, I think the UI not refreshing bug is pretty standard. Gotta back out and reopen it to show changes :/

Thanks for the list! :good:

Until now I was just copying the entire lib folders lol

---------- Post added at 06:29 PM ---------- Previous post was at 06:25 PM ----------

Can confirm, first thing I did was copying lib files (except audioflinger + nbaio) in this port so they're all in both vendor/lib and system/lib. Would still FC. I believe libatmos looks for these libraries in vendor/lib whereas our phones have them in system/lib, so copying them (or perhaps some sort of symlink) is necessary
[Android Software Development] guitardedhero:
Downloads

:

Android File Host (gh)

Standard:

Latest: 20180211-1[*]MD5: 2a960bb66a6af3696115ea2166308b54

Android File Host (Zackptg5)

Unity:

Latest: 20180209[*]MD5: 87762df810231060f1caf5762c89f7b8

Changelog

:

[B]20180211-1 -[/B]

- Testing new library migration
function.
[Android Software Development] AquaBytez:
I get Error 2 in TWRP with 20180211-1
[Android Software Development] GBPackerFanForLife:
Hi installed the Dolby Oreo Unity an it installs thru Twrp but when phone starta up there in no Dolby icon I go into Magisk its not in their either ..Any ideas I'm on a Pixel 2 XL..
[Android Software Development] g3v0:
Viper doesn't process with Atmos rn on the Pixel 2 XL. Disable your other audio mods and install the latest standard version of atmos posted above - I believe the latest one already has the fix needed for us Pixel owners baked in
[Android Software Development] GBPackerFanForLife:
The Standard version doesn't install Error 2..The Unity one does tho but doesn't show anywhere on my phone..
[Android Software Development] Jobin@123:
How to instal this on redmi note 4 pixel experince rom
[Android Software Development] lmentor:
can't flash it, it's error 2 in twrp.
[Android Software Development] onliner:
I don't know if it's a bug or it's intentional, but latest version isn't a Magisk module, I mean, it's installed directly in /system without me having configured it in arise.prop

Screenshots of arise.prop and /Magisk (Show my installed modules), and recovery log.
[Android Software Development] MiltonF:
I get error 2 en twrp, and with unity still getting bootlop, I have tried all versions and always getting bootloop.

I hope this log help

I:Set page: 'install'
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
I:operation_start: 'Flashing'
Installing zip file '/sdcard/Download/DolbyAtmos_for_Oreo_20180211-1.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Update binary zip
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
Segmentation fault
Archive: /sdcard/Download/DolbyAtmos_for_Oreo_20180211-1-1.zip
inflating: META-INF/com/google/android/updater-script
inflating: META-INF/com/google/android/update-binary
inflating: META-INF/functions
inflating: arise_parameters.prop
inflating: source/source.txt
inflating: source/Axon7/build.prop
inflating: dolby/bin/audioserver
inflating: dolby/etc/permissions/privapp-permissions-com.dolby.dax2appUI.xml
inflating: dolby/etc/dolby/dax-default.xml
inflating: dolby/lib/libstagefright_soft_ddpdec.so
inflating: dolby/lib/soundfx/libatmos.so
inflating: dolby/lib/soundfx/libswvlldp.so
inflating: dolby/lib/libdlbdapstorage.so
inflating: dolby/lib/libdlbdsservice.so
inflating: dolby/lib/libdlbmemoryservice.so
inflating: dolby/lib/libdlbnativeservice.so
inflating: dolby/apk/DolbyAtmos/DolbyAtmos.apk
inflating: dolby/lib64/soundfx/libatmos.so
inflating: dolby/lib64/soundfx/libswvlldp.so
inflating: dolby/lib64/libdlbdapstorage.so
inflating: dolby/lib64/libdlbdsservice.so
inflating: dolby/lib64/libdlbmemoryservice.so
inflating: dolby/lib64/libdlbnativeservice.so
inflating: dolby/scripts/magisk/auto_mount
inflating: dolby/scripts/magisk/module.prop
inflating: dolby/scripts/magisk/post-fs-data.sh
inflating: dolby/scripts/magisk/service.sh
inflating: dolby/scripts/supersu/etc/init.d/dolby.sh
inflating: dolby/scripts/supersu/su.d/execute
inflating: dolby/framework/dolby_dax.jar
inflating: dolby/custom/lib/libradioservice.so
inflating: dolby/custom/lib/libnbaio.so
inflating: dolby/custom/lib/libradio.so
inflating: dolby/custom/lib/libaudioflinger.so
inflating: dolby/custom/lib64/libradioservice.so
inflating: dolby/custom/lib64/libaudioflinger.so
inflating: dolby/custom/lib64/libradio.so
inflating: dolby/custom/lib64/libnbaio.so
inflating: tools/RecovyManagement.txt
inflating: tools/Magisk+SuperSU_RecoveryManagement.zip
inflating: README.md
2+0 records in
2+0 records out
2 bytes (2B) copied, 0.007328 seconds, 272B/s
/tmp/updater: /dev/tmp/META-INF/functions: line 386: syntax error: unexpected "elif" (expecting "fi")
Updater process ended with ERROR: 2
I:Legacy property environment disabled.
I:Install took 2 second(s).
Error installing zip file '/sdcard/Download/DolbyAtmos_for_Oreo_20180211-1-1.zip'
Updating partition details...
[Android Software Development] repey6:
Error 2 on 11-1
[Android Software Development] nithin1999:
What's the difference between unity and standard
[Android Software Development] ShadoV90:
I looked out of curiosity in META-INF functions in 20180211-1 build (because it's causing error 2)

line 386 is exactly

elif [ -e /data/su.img ]; then

and whole block is like that:

library_migration() {
for libs in $lib/libaudioclient.so $lib/libaudioflinger.so $lib/libaudiomanager.so $lib/libcamera_client.so $lib/libicui18n.so $lib/libicuuc.so $lib/libmedia.so $lib/libmediadrm.so $lib/libmediametrics.so $lib/libmediautils.so $lib/libmemunreachable.so $lib/libnbaio.so $lib/libradio.so $lib/libradioservice.so $lib/libserviceutility.so $lib/libsonivox.so; do
if [ -e "$libs" ]; then
if [ -e "$MAGISKBIN" ]; then
if [ ! "$systeminstall" ]; then
cp -f $libs $vlibmodule/
else
cp -f $libs $vlib/
[U] elif [ -e /data/su.img ]; then[/U]
if [ "$sumodinstall" == "true" ]; then
cp -f $libs $vlibmodule/
else
cp -f $libs $vlib/
fi
else
cp -f $libs $vlib/
fi
fi
done
}

For me it looks like elif should be if and that if below should be elif.

And one fi is missing. (if i'm correctly)

I'm not sure (because i had programming about 5 years ago xD) but for me it should looks like that:

library_migration() {
for libs in $lib/libaudioclient.so $lib/libaudioflinger.so $lib/libaudiomanager.so $lib/libcamera_client.so $lib/libicui18n.so $lib/libicuuc.so $lib/libmedia.so $lib/libmediadrm.so $lib/libmediametrics.so $lib/libmediautils.so $lib/libmemunreachable.so $lib/libnbaio.so $lib/libradio.so $lib/libradioservice.so $lib/libserviceutility.so $lib/libsonivox.so; do
if [ -e "$libs" ]; then
if [ -e "$MAGISKBIN" ]; then
if [ ! "$systeminstall" ]; then
cp -f $libs $vlibmodule/
else
cp -f $libs $vlib/
fi
if [ -e /data/su.img ]; then
elif [ "$sumodinstall" == "true" ]; then
cp -f $libs $vlibmodule/
else
cp -f $libs $vlib/
fi
else
cp -f $libs $vlib/
fi
fi
done
}
[Android Software Development] guitardedhero:
Downloads

:

Android File Host (gh)

Standard:

Latest: 20180212[*]MD5: ed6e37ae8b2128b658fce1c502642db4

Android File Host (Zackptg5)

Unity:

Latest: 20180209[*]MD5: 87762df810231060f1caf5762c89f7b8

Changelog

:

[B]20180212 -[/B]

- Corrected library_migration function.
[Android Software Development] king3opobn:
Latest Viper4android, in telegram arise thats with dolby atmos for oreo, force closes on samsung 8.0 rom s7edge blackpearl(stock from leak)
[Android Software Development] guitardedhero:
Downloads

:

Android File Host (gh)

Standard:

Latest: 20180212-1[*]MD5: ced2553305bf4ff413e26d57403e5ee8

Android File Host (Zackptg5)

Unity:

Latest: 20180209[*]MD5: 87762df810231060f1caf5762c89f7b8

Changelog

:

[B]20180212-1 -[/B]

- Samsung compatibility attempt
via the disabling of the SoundAlive
music output_session_processing
effect.
[Android Software Development] kamilmirza:
bootloop on both files

OnePlus 3T | LiquidRemix 9.0.4 (LOS based) | Magisk 15.3 | Busybox 1.27.2 (Magisk)
[Android Software Development] guitardedhero:
Did you force a second reboot via the power button to ensure an irrecoverable bootloop was occurring?
[Android Software Development] lmentor:
bootloop on oneplus3t RR8.1, sorry no log for you
[Android Software Development] dead0:
the bootloop seems to be caused by the audioserver file that goes in or replaces system/bin/audioserver
[Android Software Development] Guido83:
bootloop as well on axon 7 with oreo after flashing 20180212-1 standard
[Android Software Development] kamilmirza:
yes
[Android Software Development] repey6:
[MENTION=4445176]guitardedhero[/MENTION] hi. Tell me how i can uninstall this modules(Dolby SE and Viper FX) on roms with supersu. Only backup?
[Android Software Development] deano121:
trying to install and all I am getting is where it says Dolby Atmos and doesn't install at all,
[Android Software Development] guitardedhero:
To clarify, you are asking how to uninstall a system-less SuperSU /su module installation, correct?
[Android Software Development] repey6:
Yes.
[Android Software Development] Curiousn00b:
Odd. Your version didn't work, but the Unity version worked fine on the first flash.

Tried doing the Magisk installation set to true, and without it. Both turned out to be a no go, along with trying the library option set to true, so on 4 different flashes, it failed to boot. I've also tried removing Xposed before doing so, so I know for sure there was nothing conflicting with it, but I'm just glad I got it working now. :p
[Android Software Development] guitardedhero:
It's been a long time since I've used SuperSU, but I believe /su/system is not a directory with a system-less SuperSU installation.

Have you confirmed this to be working?

I ask because I am now doubting myself, now suspecting that /su is supposed to act as the "/system" folder lol.
[Android Software Development] MiltonF:
Standard is flashable via recovery and the unity one is a magisk module.

I don't know if there is another difference besides that.
[Android Software Development] laugeek57:
20180212-1 - works fine on mi A1 :D
[Android Software Development] repey6:
Sorry but not nothing. "su" folder absent in system folder and root too.
[Android Software Development] guitardedhero:
SuperSU root solution, correct?

Does /data/su.img exist?

If not, does /system/xbin/su or /system/bin/su exist?

/sbin/su?
[Android Software Development] repey6:
All su files are in /sbin folder. But there not Dolby or Viper or other apk files.
[Android Software Development] MiltonF:
still getting boot loop, but can't upload full logs.

Is there an specific part of the log that I should look?

Is this working for someone on AICP 13.1 and a Le Pro 3 (LEX727) ?
[Android Software Development] GBPackerFanForLife:
Holy Fo Shizzle the newest standard installed on my Pixel 2 XL Finally ..An work perfect... Thanks for all the hard work Really appreciate it..
[Android Software Development] konsolite:
How fully remove/uninstall standard version?
[Android Software Development] MArtyChubbs:
Great work! Atmos and Viper playing nice with each other. GH is the man!

DolbyAtmos_for_Oreo_20180209-2 and V4A Materialized all Magisk modules
[Android Software Development] AquaBytez:
Latest build (20180212-1) still bootloops :confused:. Since I don't know what's causing it, I just uploaded my entire /magisk/dolbyatmos folder. Hopefully it helps locate the problem.
[Android Software Development] OldMid:
It'd be much more useful if you uploaded your audio policy config and audio effects XML files, along with details about what ROM you're running and what other sound mods you have applied (if any):good:
[Android Software Development] AquaBytez:
I already did. It is right here
[Android Software Development] linx1287:
Any success stories for the HTC 10 yet?
[Android Software Development] sonophilos:
Right here, buddy. I've been building and testing all my Black 'n Cheese Editions on HTC 10 with Oreo RUU, as states my signature. ViPER and Atmos are working side by side for me, they just require some prodding to get processing on boot:

If Atmos shows all signs of having installed correctly but it FCs, try entering this in a terminal emulator while music is playing:

su -c killall audioserver

You should hear audio drop out for a few seconds and when it drops back in Atmos may already be processing before you even open it. You may have to do this after every boot.

If ViPER shows the driver install prompt, try that audioserver kill for that as well. The driver is preinstalled with the ViPER FX installation, so the issue is that ViPER can't "see" it.

If ViPER isn't processing even though the other indicators in driver status suggest it should be, try the "jumpstart":

Turn off Master Power > 3dot menu > Exit > Clear from recents > Open > Turn on Master Power

It may take a couple of these before the power switch actually initiates the effect, but if you have music playing you should be able to hear it (audio drops out for a shorter duration than Dolby, then comes back in with effects)

Hope this helps. :good:
[Android Software Development] yyz71:
The viper trick worked both Dolby and viper processing :good:
[Android Software Development] Albert Poon:
From what I know its always working fine on HTC, 9/10, and recently U11.
[Android Software Development] sonophilos:
Presenting...

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

Changes:

Updated base to 20180212-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 20180210-1 Black 'n Cheese Edition rev1

Changes:

Updated base to 20180210-1 (gh's, Skittles' and my profiles should automatically install to /sdcard/ViPER4Android/Profile/ now) (rev1 is intended to fix profile installation but it doesn't appear to have worked, sorry. Profiles can still be extracted from /viperfx/arise/* inside the zip. I see also that my readme has become redundant now that it exists in /viper/arise/loverofsound)

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] guitardedhero:
Does the port appear to be installed?
[Android Software Development] repey6:
Specific or generaly?
[Android Software Development] Mar-cel:
How to get V4a working with that??
[Android Software Development] linx1287:
It wasnt. I was testing this when it came out and it either broke sound all together or the app FC''d like no tomorrow. But its super good news now that it seems to be working.