yashsingh1/xdaforums huggingface dataset:
[Android Software Development] repey6:
Many variants. The main thing that Dolby install successfully. Then select Viper.
[Android Software Development] guitardedhero:
In regards to your inquiry requesting uninstallation procedure(s).
[Android Software Development] linx1287:
Thank you bro for such a detailed explanation. One final thing i want to know before i go in is that do you have Boomsound Dolby working alongside Atmos? Or does it break Boomsound? Thanks in advance. Great work [MENTION=4445176]guitardedhero[/MENTION] knew the problems would sort out
[Android Software Development] repey6:
I understood , this is hardly. Suitable build not one. Their many. Backup restore simply.:)
[Android Software Development] guitardedhero:
I apologise, I assumed you were asking for the uninstallation procedure for a SuperSU system-less /su installation. I have none as I do not even know if that installation scenario works lol.

I used to have a system-less /su installation method right around the time Magisk made an appearance. It worked wonderfully back then, I just am unsure of the necessary directory tree for /su lol. Currently, the script will install Dolby Atmos in /su/system (which symlinks to /system), but I am now suspecting that the /su folder is what symlinks to /system.

The aspect I really like about this system-less installation method is that it is essentially no different than what occurs when writing to /system. What I mean by that, is that if you try to install content that is already there, it is simply overwritten as there are no module folders.

Magisk's greatest weakness is ironically one of its greatest strengths - the ease and convenience of removing content on a modular level as nearly everything provided is a bundle of content within a relevantly named folder. The massive inconvenience arises when more than one file is fighting for the symlinking role.

This scenario is precisely why you have individuals exhausting enormous effort to find a solution that overcomes this Magisk nuance, like AML and Unity, obviously. :good:
[Android Software Development] repey6:
It's like that. Some users simply prefer supersu than magisk for his stable work. For example on my Samsung Tab on LOS 14.1 magisk v.14+ give bootloop yet.:D
[Android Software Development] jack allen:
I keeo getting a error in recovery it just aborts all the time im on oreo and have galaxy S8+
[Android Software Development] Mar-cel:
Select viper where?? Which viper version?
[Android Software Development] linx1287:
Sorry mate. My bad luck it seems as it doesnt work on mine. The same breaking Boomsound, Dolby Fc, affair. Even with the audioserver kill method. Will try Leedroid's latest R128 and see if it makes a difference. I am on R125
[Android Software Development] repey6:
Magisk manader have three versions. In this thread can find and [MENTION=4445176]guitardedhero[/MENTION] publish his builds on XDA and AFH , ARISE and etc.
[Android Software Development] Zackptg5:
Some big changes with unity build. Sepolicy patches have been redone thanks to some intel from [MENTION=4667597]Didgeridoohan[/MENTION] so they'll now actually finish running for everyone so all weird issues from that should be gone. Also some misc fixes
[Android Software Development] kamilmirza:
bootloop

please find the attachments

OnePlus 3T | Liquid Remix (LOS) | Magisk 15.3 | Busybox 1.27 (Magisk)
[Android Software Development] KPOCAB4EG:
I have Samsung Galaxy S8. I've been following this mod since its appearance. Tried to install on different firmware Oreo (Beta) and the final version (G950FXXUCRAP :D ). Does not work. Will there be support for the Oreo firmware Samsung Samsung S8?
[Android Software Development] jack allen:
Can someone help please every thing i click on sends me to youtube i just want atmos on my S8+ running oreo please
[Android Software Development] guitardedhero:
Downloads

:

Android File Host (gh)

Standard:

Latest: 20180213[*]MD5: 937fdeec804ea575611572f4c25fa2c4

Android File Host (Zackptg5)

Unity:

Latest: 20180212-2[*]MD5: c5dae00911df70ba44ebb5a101deb8ec

Changelog

:

[B]20180213 -[/B]

- Extensive reworking of boot scripts
aimed at device boot success and
debloat.
[Android Software Development] guitardedhero:
No doubt about it, which is why there has never been a limitation/restriction on Magisk or SuperSU once I began supporting the Magisk root solution.

I was merely trying to explain the relevance for providing a system-less SuperSU installation - something nearly not found anywhere else.

Unfortunately, I believe my recent suspicion is correct, meaning that such a result is not possible currently, as I need to edit the /su module function to treat the /su directory as /system and not treat it as / (rootfs) as it still does.

I will ensure the next update includes this adjustment for those interested in testing this installation. :good:
[Android Software Development] AquaBytez:
Bootloop. What do you need in order to debug this? An ADB log during boot isn't an option (I tried, it seems like it only works in certain phones)
[Android Software Development] guitardedhero:
What root solution and is the installation manipulated by one or more parameters in /sdcard/arise_parameters.prop?

What device/rom/SDK?

Have you attempted a forced second reboot via the device's Power button to confirm successful device boot is unable to complete?

Did you complete the last step of the installation instructions by copying the recovery.log to /sdcard?
[Android Software Development] AquaBytez:
Magisk 15.3, OnePlus 3, ResurrectionRemix v6.0.0[android-8.1.0_r11].

I haven't touched the arise_parameters.prop file at all.

And yes, I have tried to force a reboot, and it gets stuck in the boot animation, early enough during boot for adb to not be available.
[Android Software Development] guitardedhero:
You can perform three simple tests after initiating the bootloop with the installation:

Download and confirm the location of the Recovery Management zip tool attached in the OP.

Boot to recovery using the appropriate hardware button combination for the device that boots to fast boot mode and selecting the Recovery option from its menu.

Flash the Recovery Management zip tool and navigate to /magisk/dolbyatmos when informed that the Magisk image has been successfully mounted to /magisk.

First, let's test audioserver as the culprit by navigating to /dolbyatmos/system/bin, tapping audioserver, selecting the Delete action, and swiping to perform the action.

Flash the Recovery Management zip tool once more to unmount the Magisk I'm going from /magisk and reboot the device to test for successful device boot.

If device boot is unsuccessful, boot to recovery, flash the Dolby Atmos zip to restore its audioserver, and reboot just to confirm that you are still facing a bootloop.

Repeat the same steps performed to delete audioserver, but remain in /dolbyatmos, as we will now test /dolbyatmos/service.sh as the culprit.

If a successful device boot still has not been achieved, the third file to test as the culprit is /magisk/dolbyatmos/post-fs-data.sh.

Let me know what you find. :good:
[Android Software Development] Heins:
I have installed both DA unity (standard caused bootloop) and Viper in my RN3 from this threat, DA working properly, Viper will working only when toggle the master power button to "off" then force closed and then toggle to "on" after apk is opened again. Heared audio is processed. This treack repeadly done every boot and load efect profiles.
[Android Software Development] AquaBytez:
First try. Deleting /magisk/dolbyatmos/system/bin/audioserver allows the device to boot.

I can't test to see if Dolby processes since it just FCs. Do you need a log now?
[Android Software Development] yyz71:
Ya that's the bummer about that! But I just finally got DA on my Pixel 2 with moving some flies. And I'm using standard:good: installation.
[Android Software Development] king3opobn:
Pure v4a is working from magisk downloads
[Android Software Development] Heins:
Yes right,as I had tried before, but it cant work together with DA. Viper must be untick on magisk if will use DA.

Viper from this threat can be used together despite use toggle trick:confused::confused:
[Android Software Development] king3opobn:
No sweat, it's just to early, eventually, you'll be able to just edit prop amd flash arise
[Android Software Development] guitardedhero:
Post #3 :good:
[Android Software Development] satriahitam:
bootloop on asus zenfone Z00T . Aex 5.2 (Oreo 8.1), magisk 15.3.

forced boot by pressing power button still bootloop.

flash recovery zip manage to boot

attached recovery log
[Android Software Development] guitardedhero:
Downloads

:

Android File Host (gh)

Standard:

Latest: 20180213-1[*]MD5: c0d99a9ca3a8b31d5db5d9dfb11bc2de

Android File Host (Zackptg5)

Unity:

Latest: 20180212-2[*]MD5: c5dae00911df70ba44ebb5a101deb8ec

Changelog

:

[B]20180213-1 -[/B]

- Completed the incomplete service.sh
script mistakenly thought as completed.
[Android Software Development] AquaBytez:
Done. Anything else?

How does that database help anyways? :confused:
[Android Software Development] satriahitam:
Z00T, aex 5.2

using latest unity, install success, booting, but dolby atmos forced closed, then phone random reboot
[Android Software Development] guitardedhero:
It provides me with study material. :good:
[Android Software Development] -Rhoby|™-Bugs:
what is the difference from the version Standar & Unity?

Thanks.
[Android Software Development] akdrhmz:
xiaomi mi5 lineageos 15.1 supported?
[Android Software Development] Albert Poon:
[MENTION=4445176]guitardedhero[/MENTION]

I wanna report that standard-20180210 works fine but then any later versions resulted in FC. Let me know what to do, tho I will be traveling for a week's time.
[Android Software Development] adefxda:
standard, apply only via TWRP

Unity, you can apply over TWRP or over MAGISK..

CMIIW
[Android Software Development] Minions007:
Unity version with magisk module works fine on my kenzo's crdroid rom , no bootloops thanxs op
[Android Software Development] -Rhoby|™-Bugs:
Nice... thanks you
[Android Software Development] Mar-cel:
My phone bootloops after installing one of them V4A modules
[Android Software Development] repey6:
Maybe this was temporary bootloop? You did hard reset? Strange. If Dolby work viper can give different issues but not bootloop.
[Android Software Development] kamilmirza:
[MENTION=6037748]Zackptg5[/MENTION] [MENTION=4445176]guitardedhero[/MENTION]

bootloop experiences

please find the attachments

OnePlus 3T | Liquid Remix 8.1 (LOS) | Magisk 15.3 | Busybox 1.27 (Magisk)
[Android Software Development] kamilmirza:
just saw this post

going to try it and report back
[Android Software Development] MrJones2k:
Also just tried the unity installer on latest magisk Januaray Oreo Mi A1 and was stuck on android one logo.

EDIT:// Tried one more time with no other Magisk module installed. Still stuck at Android One logo, waited 10 minutes now.I guess we still have to wait a bit for a working port as Magisk only module without TWRP.
[Android Software Development] -Rhoby|™-Bugs:
Thanks bro,

nice information for our device.
[Android Software Development] kamilmirza:
i have uploaded my device folder along with other things in Oreo Database
[Android Software Development] exodius48:
[MENTION=6037748]Zackptg5[/MENTION] [MENTION=4445176]guitardedhero[/MENTION] Latest unity installer still give me bootloop, standar version works.Tested on Xiaomi Mi A1
[Android Software Development] laugeek57:
20180213-1 Standard works fine on mi A1 :D
[Android Software Development] -Rhoby|™-Bugs:
With twrp temp you flash?
[Android Software Development] laugeek57:
with 3.2.1.1 ;)
[Android Software Development] Zackptg5:
Can you post your magisk/dolbyatmos folder (except the apk. Remove that and then the attachment will be small enough to be uploadable to xda)
[Android Software Development] shivam kapoor:
The sound is not coming in demo video why?
[Android Software Development] exodius48:
Here it's https://sendit.cloud/qzqq86nb31pg
[Android Software Development] maosilva:
Does it work on any device?
[Android Software Development] truelies1:
It's not easy to install ViPER4Android on oero. Better if you can combine to one installation or put a step by step detail.
[Android Software Development] laugeek57:
Why do you want to try it on your curling iron ?? :laugh:
[Android Software Development] maosilva:
Thanks for using part of your time, which seems to be as helpful as your response! ;):laugh:
[Android Software Development] laugeek57:
Seriously what phone model do you use?
[Android Software Development] docnok63:
[MENTION=4445176]guitardedhero[/MENTION] [MENTION=6037748]Zackptg5[/MENTION] - Bootloop with 13-1, audioserver dies

02-13 11:01:57.641 1110 1492 E AudioService: Audioserver died.
02-13 11:01:57.648 865 2430 E android.hardware.usb@1.0-service: uevent received SUBSYSTEM=dual_role_usb
02-13 11:01:57.648 865 2430 I android.hardware.usb@1.0-service: otg_default
02-13 11:01:57.649 865 2430 I android.hardware.usb@1.0-service: canChangeMode: 0 canChagedata: 0 canChangePower:0
02-13 11:01:57.727 1110 1110 I ServiceManager: Waiting for service media.sound_trigger_hw...

This is now looks similar to Unity fail.
[Android Software Development] guitardedhero:
I'd like to examine DU's audioserver. :good:
[Android Software Development] marquelito:
Neither of them worked on my s7 edge in Oreo. Got fc and random vibrations. Last one happens too with any sound mod.
[Android Software Development] docnok63:
I think that would be in either of the zips as audioserver.original? If not, I'll post it renamed below
[Android Software Development] guitardedhero:
Lol, my bad. I had downloaded the zip and never even went to it. :good:
[Android Software Development] guitardedhero:
Magisk or SuperSU installation?

Still installed?
[Android Software Development] guitardedhero:
Downloads

:

Android File Host (gh)

Standard:

Latest: 20180213-2[*]MD5: 0caa747a1b5b18a5b17e93a9c7b042f2

Android File Host (Zackptg5)

Unity:

Latest: 20180212-2[*]MD5: c5dae00911df70ba44ebb5a101deb8ec

Changelog

:

[B]20180213-1 -[/B]

- Adjustment to SuperSU /su
module installation.
[Android Software Development] AquaBytez:
[MENTION=4445176]guitardedhero[/MENTION] If you don't mind me asking, how do you plan to fix audioserver hangs and crashes during boot?
[Android Software Development] g3v0:
Audioserver would crash for me like that too in the past. I fixed it moving some libraries around, try copying libradio.so and libradioservice.so from the dolby zip/custom folder into /magisk/dolbyatmos/system/vendor/lib + lib64, and copy libaudioflinger.so and libnbaio.so from /system/lib + lib64 into the same magisk folders.

My original installation didn't have any of the libs in dolby/custom. Without any of them, or with all of them, it would give me the audioserver crash. After doing the above, it would boot but app would FC. After copying a few more libs (which I think is included in the latest zips already), app worked fine without FC
[Android Software Development] marquelito:
Magisk, i tried both zips but it gets the same results. No, i've already uninstall it. But i can install it again. I get the same random vibrates when i open arise or viper. Its the same in every soundmod. Atmos just get fc never opened it
[Android Software Development] yyz71:
Hey bro what method are using to process? I'm Still using 21-2 standard. It opens but it doesn't processing.
[Android Software Development] xxxreyxxx:
latest standard build gave bootloop for me
[Android Software Development] hellboy180699:
Bootloop on S8+ Stable oreo (Magisk)
[Android Software Development] LeifAlbor:
So, I flashed this onto my Pixel 2 XL (8.1 Feb security patch, stock kernel, TWRP 3.2.1, Magisk 15.4, with V4A 1.3.2 by ahrion) and it wouldn't boot.

Any idea's where I've gone wrong here, or am I incompatible?
[Android Software Development] MikeW14:
anyone get this to work along with viper on nexus 6p??
[Android Software Development] shantam3108:
Yes using unity version with cr droid rom
[Android Software Development] g3v0:
The latest standard version gives bootloop to me as well. Replace the post-fs-data.sh with the attached previously working one to boot

I haven't gotten (or really tried) to get viper to process
[Android Software Development] g3v0:
This was the same error I was getting with the latest version. Replace post-fs-data with the one provided and it should work
[Android Software Development] theman480:
So with lastest unity version, you getting bootloop with mi A1? Did you try with the Magisk 15.4 beta?
[Android Software Development] MrJones2k:
I only tried latest stable version
[Android Software Development] adefxda:
work with Lineage OS 15.1. .. Thanks dev..

I'am usinf Unity version https://androidfilehost.com/?w=files&flid=247761

if Dolby app still not appear, try to exctract DAO.zip from files, then apply DAO.zip once via TWRP

fyi, font: 365 Fine Day
[Android Software Development] LabLab...28:
Pm sent :fingers-crossed:
[Android Software Development] laugeek57:
Standard:

20180214 works fine on mi A1 :D
[Android Software Development] exelinguy:
Got it working on my Nexus 6p with latest stock rom (OPM5.171019.015, Feb 2018) with Magisk. I first installed the Audio Mod Library on Magisk and then installed the Unity version. In the arise_parameters.prop, I edited:

install.add.libraries=true

Hope this helps someone! Cheers!
[Android Software Development] -Rhoby|™-Bugs:
What is change? Any new fiture?

Just replace from early version?

Installed 20180213-1.
[Android Software Development] laugeek57:
This improves the compatibility with the many devices turning on Oreo level rendering sound I do not think our friend Guitardedhero can do better ...:D
[Android Software Development] theman480:
Did you try with the Magisk version?
[Android Software Development] Ramakrishnan ?:
[MENTION=4445176]guitardedhero[/MENTION] . . i am tried ur 26jan-1 build on my redmi 4x . . first time installed with addlibs option and Dolby server option from aise.prop then the doby is force closing then installed without arise.prop dolby opened but not processing becausw when i connect headset dolby headset notification not showing automatically and when i open dolby headset notif showing then i click back button headset notif from doby gone ? . . i am attached ss and recovery.log and matlog while playing audio hope it will help u (rename matlog file to .txt format because txt format upload limit 500kb only) ?
[Android Software Development] guitardedhero:
This report is for a build five versions prior to what is the current version. Please try again with the current zip version linked in the OP as several changes have taken place targeting various issues. :good:
[Android Software Development] xxxreyxxx:
successful installed and the app is on app drawer but Audio effect not working,am i miss something?
[Android Software Development] bkkzak:
File manager shows 57.72mb of 585.08mb, also I used the Magisk manager for recovery module and it says 57.7mb of 186.0mb. Screenshots attached.
[Android Software Development] theduke7:
If you have BusyBox installed , uninstall it ...that was the issue in my case
[Android Software Development] raystef66:
First, nice works here and much appreciated! :good:

Second, I couldn’t agree more as written above. As much I would like to see and flash some custom rom on this Axon7 with and especially with that native build-in out-of-the-box amazing Dolby sound system, unfortunately there isn’t one available at the moment. It just would be an always “near” experience-sound-feeling created by third-party apps and imo a pity and waste having an A7 with those features not fully applied and working at their best ;)
[Android Software Development] xxxreyxxx:
i was never installed busybox before,but when i'm check with busybox checker, busybox still on system/xbin
[Android Software Development] Aniruddhlr:
Is demo in Dolby working?
[Android Software Development] Mao3K:
Hi,

When you install this mod, the audio recording from microphone not working. If you remove Dolby Atmos work again.
[Android Software Development] Ramakrishnan ?:
I think u missed dolby frameworks in port ?
[Android Software Development] escorpion_sw:
thanks buddy works great in my OP3 with NOS 8.1, just i had to reboot the first time by force close
[Android Software Development] andriana936:
It works on my Redmi 3S with Nitrogen OS (Android 8.1.0). First boot after it flashed it gave an FC, but after clear data of Dolby Atmos and then reboot the phone Dolby works.

But I'm back to V4A because after I extracted demo videos inside the Dolby Atmos's APK and then play it, somehow I feel the audio experience is better on V4A.

[MENTION=4445176]guitardedhero[/MENTION] Thank you for porting Dolby to Android 8.1.0. Keep up your good works Dev.
[Android Software Development] najjurocks619:
Is it only me or the sound is not louder than the Dolby-Oreo.zip even when i raise all lines to 12db is something missing i mean i enabled both volume leveler and bass? Any workaround?

Thanks in advance.
[Android Software Development] guitardedhero:
It's merged into the apk, but I may separate it like I did originally. :good:
[Android Software Development] laugeek57:
Hello,

I also observed a difference in tone but it is more detailed and the bass deeper ... the quality of headphones also contributes a lot :D
[Android Software Development] tropical cactus:
Agreed. It's about quality, not quantity. Now that viper 2.5 doesn't work with Atmos, there is a reduction in loudness. But the quality is definitely there. It used to be distortion with certain viper profiles. Volume slider didn't work coz it was already at max. Now at least I'm getting volume control back. And the sound quality... amazing. ?
[Android Software Development] repey6:
Look here
[Android Software Development] guitardedhero:
ViPER4Android is certainly working with this port better than previously and the combination is just... WOW!! The recent adjustments to the boot scripts have allowed ViPER4Android to process without fail after performing the initial "jumpstart" described in [MENTION=4967345]docnok63[/MENTION]'s post linked in the OP after each device boot.

Previously, this "jumpstart" procedure would be required with every track change, so much progress has been gained in just the past 24 hours alone. :good:
[Android Software Development] Trupen:
[MENTION=4445176]guitardedhero[/MENTION] renaming adb folder to adb.bak allows twrp to flash the zip successfully below is the list of modules installed
[Android Software Development] guitardedhero:
Changelog

:

[B]20180127 -[/B]

- Numerous changes/improvements
across the entire archive.

For effective testing, please refrain from any formed habits such as renaming /data/adb or edits to arise_parameters.prop that are performed simply to acquire an installation (unless these edits are desired, of course). :good:
[Android Software Development] laugeek57:
No, the standard version suits me perfectly :)
[Android Software Development] guitardedhero:
Downloads

:

Android File Host (gh)

Standard:

Latest: 20180214[*]MD5: fef62e5d1a3ef658cc841b1202f75d8e

Android File Host (Zackptg5)

Unity:

Latest: 20180212-2[*]MD5: c5dae00911df70ba44ebb5a101deb8ec

Changelog

:

[B]20180214 -[/B]

- Minor corrections and enhancements.
[Android Software Development] Trupen:
Viper not working

It works for sometime then stops working

---------- Post added at 04:38 PM ---------- Previous post was at 04:37 PM ----------

Enhancement ? Like what

---------- Post added at 04:39 PM ---------- Previous post was at 04:38 PM ----------

Viper not working is it still related to aml ?
[Android Software Development] guitardedhero:
Does /vendor/lib/libstdc++.so exist, physically or as a symlink?
[Android Software Development] theman480:
Anyone can try this version on mi a1 with Magisk?
[Android Software Development] laugeek57:
why do you absolutely want to flash this Dolby atmos with magisk :rolleyes: version with TWRP works perfectly ...
[Android Software Development] theman480:
I have no TWRP, I only booted on with to install Magisk.