yashsingh1/xdaforums huggingface dataset:
[Android Software Development] eqagunn:
Did that already. Didn't help.

Not sure what else can be causing it as phone was booting fine before flashing DA through Magisk.

Flashed DA through TWRP this time. Bootloop still.

Flashed again to uninstall it. Cleared Dalvik/ART+cache. Bootloop still.

Maybe uninstallation through mm didn't restore the default audioserver. :/

P.S. RR is Treble, TWRP is MultiROM, SELinux is enforcing, system is encrypted.
[Android Software Development] panicker666:
Dirty flash the rom or uninstall magisk. It will restore boot img
[Android Software Development] eqagunn:
Restoring multirom-twrp backup of all partitions didn't fix the bootloop. Now I'm clueless.
[Android Software Development] panicker666:
Try to uninstall magisk with the uninstaller zip.

If it still doesn't boot then dirty flash the rom file and gapps.
[Android Software Development] omkolte17:
Did you restored "Boot" from TWRP backup?
[Android Software Development] d3vyarth:
1-)Go to /data/adb find magisk.img and delete it.

Or, extract default boot.img from your rom zip and flash it(if first option don't work) in the boot partition.
[Android Software Development] yyz71:
Do any of these work with Android p?
[Android Software Development] andy9872:
[MENTION=6037748]Zackptg5[/MENTION] can you tell me why is this happening and what can I do to fix this? Above are the details as you requested.
[Android Software Development] Pathania08:
It can only be fixed with dirty flashing the ROM. Same thing happened on my MI 5X.
[Android Software Development] eqagunn:
Indeed. Phone boots fine after dirty flash.

I'll try to sum up my testing...

Environment:

RN5 Pro Global

System is encrypted

MultiRom-TWRP-3.2.1-vasishath

Treble-RR-6.1.0.20180706

Magisk 16.0 Stable

Dolby-Atmos-Axon7-Oreo_7.17.18.zip

1. Flashed latest DA through Magisk. Splash bootloop afterwards. Uninstalled DA through Recovery MM (module by VR25). Splash bootloop still.

2. Restored Boot. Splash bootloop. Restored Data. Splash bootloop. Restored SystemImage. Splash bootloop. Dirty flashed RR. Phone boots fine. Restored same partitions again. Phone boots fine.

3. Flashed DA through TWRP. Splash bootloop afterwards. Unistalled DA by re-flashing it through TWRP. Phone boots fine.

4. Updated Magisk to 16.7 Beta. Flashed DA through Magisk. Splash bootloop. Unistalled DA by re-flashing it through TWRP. Splash bootloop. Dirty flashed RR. Phone boots fine.

Some thoughts...

DA installed through Magisk doesn't get uninstalled properly through TWRP.

Whatever gets modified during DA installation is outside System+Data+Boot.

Maybe someone finds this info useful.
[Android Software Development] andy9872:
[MENTION=6037748]Zackptg5[/MENTION] need help please. Can you tell me what should I do to make it work?
[Android Software Development] Zackptg5:
For v4a, follow the troubleshooting guide on the op of the v4a unity thread and then post the listed logs there if none of the solutions there works along with the recovery.log immediately after flashing the mod
[Android Software Development] andy9872:
But v4a was working fine. Previously you told that none of the sepolicies were executed and then asked for the root solution i was using.

Edit: about the recovery log, should i reboot the device to system or immediately after flashing copy recovery log without rebooting?

PS. Should I provide log without flashin v4a and aml mod or this mods should be installed before?
[Android Software Development] Zackptg5:
Oh, I forgot about that. Can you send your magisk.log? Also, if v4a is your only audio mod then you don't need aml (I'm also assuming your on the latest v4a and aml)
[Android Software Development] andy9872:
Yeah I was on latest v4a and aml, and for the magisk.log i'll need to flash v4a, aml and dolby again. My phone became unresponsive so i removed them. Do I need to flash all these modules again? If so, then please tell me the sequence.

Edit: Nice website by the way. I saw it today under your signature. :good:
[Android Software Development] Zackptg5:
This Dolby doesn't work with much of any other audio mods so I wouldn't even bother. Pick either it or v4a (probably v4a since it sounds like Dolby wasn't compatible with your phone)
[Android Software Development] andy9872:
It means I can choose either Dolby or v4a? then I'll try dolby once more without using any more audio mods (just dolby), if not successful then i'll stick with v4a.
[Android Software Development] glurak888:
Bootloop here, newest lineago nightly, magisk, and twrp.
[Android Software Development] andy9872:
I am facing the same problem (Dolby Atmos FC issue.) I also have attached all my logs including recovery log, magisk log, bugreport, logcat (taken using aLogcat.). Hope it helps, I really wanna try your dolby module.
[Android Software Development] docnok63:
[MENTION=4445176]guitardedhero[/MENTION] - After a bit of sleep, I just did a lotta flashing. Here's what I discovered...no matter what version you install on 8.1, Atmos install will fail to boot if you have V4A installed either through either Magisk Manager or ARISE. I did get 1-31-1 to install, boot, and function without V4A. As others have stated in here, the problem probably lies in the AML Just for testing purposes, I tried installing ARISE on Magisk without the compatibility module. It didn't boot either (always stuck on boot animation....not bootlooped.) The three logs below are:

1) 0114-4 (last 100% working version for me) installed with V4A on SuperSU. I only see a .sh error. Failed to boot

2) 0131-1 with V4A on SuperSU. A few errors and failed to boot.

3) 0131-1 without V4A on SuperSU. A few errors, but it booted and functioned 100%. Screen provided below.

Lastly, just my opinion, a functioning ARISE without Atmos sounds better than a functioning Atmos without Viper. People need to test for themselves. On the fast OP5, restoring a stock system is less than two minutes.

[MENTION=5704037]repey6[/MENTION] - It's very rude to promote your work in another person's thread especially when your work is based off of their work. That being said, I did try it and it also go stuck on boot animation.
[Android Software Development] mohand06:
Good job although not for me as still on nougat
[Android Software Development] docnok63:
[MENTION=4445176]guitardedhero[/MENTION] - This is quite vital. I was going to test just flashing V4A through the Magisk module. To my surprise, 8.1 wouldn't boot with just Magisk 15.3. I downloaded Magisk 14.0 and it also got stuck on the boot animation. It doesn't have anything to do with ahrion's module at all.

For all of you having issues with 8.1 and Magisk, I highly recommend you use SuperSU and the latest ARISE.
[Android Software Development] g3v0:
Yeah I've noticed the post-fs script for this module breaks Magisk weirdly enough.

The real question I have is what the DolbyAtmos.apk needs to run without FC. Even with copying the libs and audioserver, modifying the audio_effect conf/xml, and executing the post-fs script manually, DolbyAtmos still crashes on launch.
[Android Software Development] guitardedhero:
Changelog

:

[B]20180201 -[/B]

- Boot scripts completely
rewritten.

- Bundled Magisk's 1531 binary in
an attempt to access its functions
during the recovery session instead
of the existing binary for certain
Magisk-specific operations.

- Various corrections and refinements.
[Android Software Development] guitardedhero:
Again, I apologise for continued frustration and the time it has taken for me to offer something hopeful.

I have spent most of the day examining everything, much of which while in recovery.

It wasn't immediately obvious, but I eventually found a serious flaw:

The Magisk binary was not available in any of the numerous attempts to utilize it.

This binary is solely responsible for various functions including image size control utilities, mount/loop utilities, SELinux context and policy handling, init services, etc...

Even though I intentionally avoid relying on what would certainly provide convenience and predictable results if a binary flawlessly handles the various scenarios, I do rely on it for image volume tasks and also included its mounting functions for a couple of builds (around 20180129 or so) for testing purposes.

I have no clue when this "unavailability" within recovery began, although, it certainly is not from a recent Magisk update. It's possible the custom recovery is at fault as this has changed more frequently and more recently than Magisk's latest build which has remained unchanged during the entire development of this port, I believe.

It's difficult to suspect firmware updates as culprits due to this "unavailability" being limited to recovery, as the binary is certainly "available" and executing as expected outside of recovery.

I haven't tested today's zip so I do not know if this provides the binary access that I was missing when preparing the update. It could certainly suffer the same results, as I was testing file management tasks with the installed binary to gain access to it while in recovery before concluding with what is now in this installation archive.

At any rate, we'll see if any progress is made regarding module installations. I have focused on unsuccessful device boots primarily, interrupted briefly by the recovery binary event I discovered, and am really hopeful that the new boot script(s) make significant gains for many of you yet to achieve a successful installation and still trying. :good:
[Android Software Development] guitardedhero:
If not too inconvenient, please provide the audio effects configurations as they exist after the installation of a zip that causes this file management need.

It is directly related to the music output_session_processing effect configuration, which is performed on any audio effects configuration found during the installation. I want to see if this particular configuration is different between your configurations. :good:
[Android Software Development] tropical cactus:
6p 8.1

Magisk 15.3

Flashed viper and Atmos zip from here: https://xdaforums.com/showpost.php?p=70502885&postcount=2

Last build flashed on top of this 0129

All working.

Thanks.
[Android Software Development] mashaty:
Installation was failing from the beginning of the release, but the installation was completed for 20180201 for the first time.

· OnePlus 5 (liquid_remix)

· Oreo 8.1

· Magisk 15.3

Working Very fine.

Thank you
[Android Software Development] Trupen:
Latest 1-2 zip not working stuck in recovery

For me only 29 and 30 build is working
[Android Software Development] psychoela:
Finally:victory: Thanks [MENTION=4445176]guitardedhero[/MENTION]:svetius:
[Android Software Development] repey6:
I try to do this. The difficulty is that I do not know much English and I do not understand everything correctly.:D
[Android Software Development] guitardedhero:
I sense some progress lol! :highfive:

Your success is surely dependent on the binary's mounting function I was testing that I mentioned in my previous post.

This will be reimplemented immediately. :good:
[Android Software Development] repey6:
You not right understood me. I am not promote my work . I only want to help [MENTION=4445176]guitardedhero[/MENTION] as you find right solve with this Dolby. I will wery happy if i gave the correct clue.
[Android Software Development] tropical cactus:
Thanks for your work. If not, couldn't have got viper and Atmos to work together.:)
[Android Software Development] repey6:
Success and patience in your hard job!:good:
[Android Software Development] Hacker@1995:
Dolby Atmos app doesn't open on aex 5.1
[Android Software Development] namlai000:
i got everything working with 2-1 build (only dolby atmos, not using viper)

im on OmniRom 26-1

Red Wolf Recovery

the only issue is the UI not update when i turn on and off but it works
[Android Software Development] PinoF75:
I installed the zip file but fc. How can I solve this problem?
[Android Software Development] guitardedhero:
Jeff, thank you so much for all the feedback, logs, and information. It really helps me as well as everyone else. Somehow, some text got shifted in the effects configuration function for /system installations, something I never would have spotted unless I was looking for such an error. :highfive:
[Android Software Development] andy9872:
[MENTION=4666122]glurak888[/MENTION] please provide logs so that the devs will know exactly what problem are you facing.
[Android Software Development] Zackptg5:
Can you post your service.sh script in the dolby magisk module directory? Like with v4a, sepolicies aren't being set. It's making me thing that it's an issue with your magisk install since it happens across multiple mods. I'd recommend trying the latest 16.7 but in the mean time. You can try putting this script into /sbin/.core/img/.core/post-fs-data and then set it's permissions to 0755. It'll set selinux to permissive

Also, this is guitardedhero's module, not mine :)

I just package it into the unity installer
[Android Software Development] glurak888:
I tried fixing it already, wiped system, wiped cache, wiped dalvik, reinstalled ROM, Reinstalled Gapps and it boots.

Then I install Magisk and the ****ing thing bootloops again. What did that do to my system and how can I get rid of it?
[Android Software Development] andy9872:
Magisk v16.7 is currently in beta, so that won't cause any problems, right? And if I don't change the selinux to permissive and update to magisk v16.7 will it work?

ok, got it.

---------- Post added at 02:36 PM ---------- Previous post was at 02:25 PM ----------

[/COLOR [MENTION=6037748]Zackptg5[/MENTION] there is no .core directory inside my sbin folder.

---------- Post added at 03:00 PM ---------- Previous post was at 02:36 PM ----------

[MENTION=6037748]Zackptg5[/MENTION] I have attached the service.sh and updating magisk to v16.7 didn't work. Is the module not working due to my enforcing selinux?
[Android Software Development] Zackptg5:
The sepolicies are what allow it to work in enforcing. Otherwise, you'd need permissive. This looks like the script from the zip. Is this the one in your magisk image? I need that one
[Android Software Development] Rryann22:
Installed 7.17.18 via Magisk (16.7) and now my phone doesn't boot. I get stuck at SAMSUNG logo. If I wipe cache and dalvik cache it boots up to the point where it says Android is starting - Optimizing app x of y. When it reaches the last app, that's it. It's stuck there.

S7 Edge (G935FD) - 8.0
[Android Software Development] d3vyarth:
Here is the log file, flashes well without error, but doesn't boot.

AEX 5.7 Oreo Treble on Z2Plus.
[Android Software Development] Aquib1999:
Thanks buddy it's working in OnePlus 5 , I made a tutorial video

Thank you so much

Working in OnePlus 5 Oreo 8.1

Stock oos .. 5.1.3

This is my video link

https://youtu.be/l7L21w8W_XE
[Android Software Development] forcecorn2001:
Can I install it on Note 7 (OLD Note 7) ?
[Android Software Development] yashkush:
Fingerprint unlock is disabled

After installing zip from magisk manager and rebooting

Fingerprint sensor is disabled. Add fingerprint option in settings is also disappeared.

I am using Moto g4 plus (Athene),RR 6.1.0(OREO)

Please help

Edit:Working flawlessly after reinstalling.??
[Android Software Development] andy9872:
How can I get that script? Can you explain please.

Edit: and there's no .core directory in my sbin folder to paste the permissive script. So where can I paste the script to change my selinux to permissive?
[Android Software Development] tnmsrkr:
NEED DOLBY ATMOS FOR Treble RR

NEED DOLBY ATMOS FOR Treble RR rom support..
[Android Software Development] Graschuk:
When is someone going to figure out the whole audioserver problem that is screwing it up for Samsung users (like myself, SM-G930W8, *sigh*)... Is anybody working on that whole situation? it seems dead in the water...
[Android Software Development] jcmm11:
Make sure that 'show hidden' is enabled in whatever file manager you're using. If you're using Magisk as a root solution then you definitely have a .core directory.
[Android Software Development] SankyEI:
Working standard version on my mobile,using msm extended from,thanks
[Android Software Development] Popke523:
Not working with treble magisk. It says this zip is not a magisk module. latest lineage 15.1
[Android Software Development] omkolte17:
Can you tell which might be the best root browser?

I currently use SE File Explorer Pro.
[Android Software Development] andy9872:
The SELinux is changed to permissive but still the same problem (Dolby Atmos FC) and no sound on device (not even ringtone). I have attached the service.sh file from my magisk dolbyatmos directory.
[Android Software Development] jcmm11:
This is really off topic for this thread but there's a few good options out there. The best is probably https://xdaforums.com/showthread.php?t=1523691 (not found in play store). Others include (non-exclusive list) X-plore, Total Commander, Ghost Commander, FX, Solid.
[Android Software Development] m0han:
does not work for me in android-p beta

just wanna inform: i tried the latest release referred to here in the new android-p beta rom. the device was stuck in bootanimation and did not boot even after clearing cache & dalvik cache. uninstalled by flashing the same .zip again and things are fine. any way to get it working on android-p beta?
[Android Software Development] SankyEI:
It worked yesterday,but now I can't open the app,any help
[Android Software Development] Zackptg5:
Okay, that looks fine. My guess is that your device/rom might not be compatible then
[Android Software Development] ecompton59:
viper v2.5.0.4 working great on Moto z2 force I'm about to add Dolby only issue I had was unzip and find apk I installed let viper update driver no issues great work I used magisk to install all zips
[Android Software Development] Talwinder8872:
Install successful but can't see it in app drawer nor titanium backup can find it,
[Android Software Development] ecompton59:
i dont think that Dolby works with device i uninstalled kept viper that works the Dolby magisk mod for one+x works maybe it does somewhat for me.on arise page i found First, ensure you have SELinux set to Permissive; Dolby Atmos only works properly on Permissive setups. Then, if the issue persists, check /vendor/etc for audio_effects.conf and remove it if it is present there - if this is your issue it's most likely a 0b empty file. hope that helps
[Android Software Development] andy9872:
My device is OnePlus X running unofficial LOS 15.1 by YumeMichi. Currently I am using the Dolby Atmos mod from Magisk repo but wanted to try yours too.
[Android Software Development] natanrosenfeld:
Guys, I installed this using Magisk and there were no problems, except when I open the app, it doesn't process the equalizer. Doesn't work with any music app, I tried switching modes but nothing works. Cleared data and cache of the app and it still doesn't work. Honor 8 Lite running official Resurrection Remix. Any help?
[Android Software Development] rinaldi14:
Need help friends..how to disable audiofx mate..thanks..
[Android Software Development] Graschuk:
Use Titanium Backup Pro.
[Android Software Development] rinaldi14:
Okay..then how to do that use titanium back up
[Android Software Development] ecompton59:
depending on phone spotify in settings will load most audio equalizers or shortcut master lite load apps not codes
[Android Software Development] Pathania08:
I can't find any audio FX app on my phone, there's only Equalizer app...should I disable it before installing Dolby?
[Android Software Development] jandia7381:
Yes, better disable/uninstall it
[Android Software Development] derkleinebroicher:
You can freeze audiofx using titanium backup
[Android Software Development] Lownita:
Anyone tested this on OnePlus 6?
[Android Software Development] sh0w 0f:
getting stuck on Huawei Logo

Huawei Y6 2018 (ATU-L22)
[Android Software Development] TomDeW:
Has anyone been able to get this working on op5t >ob11? Mod keeps making gcam crash.
[Android Software Development] rinaldi14:
Thanks mate..but audio fx not showing on my tb maybe i dont have..

Could I ask you..now I'm using Viper4android mod from magisk..but I wan't to try this version so which version works on oreo..thanks
[Android Software Development] derkleinebroicher:
You can always the latest version from this link:

https://androidfilehost.com/?w=files&flid=247761

Works fine for me on Oreo
[Android Software Development] yyz71:
Has anyone tried this on android p?
[Android Software Development] zeusseuz:
nice app
[Android Software Development] rinaldi14:
Thanks mate..anw what's the difference with bnc version?
[Android Software Development] derkleinebroicher:
bnc means black 'n cheese version. the surface is slightly different - other colors.
[Android Software Development] rinaldi14:
I try to installed this port on my s7 edge s9 port rom but I got bootloop..unlucky..:(
[Android Software Development] harris123424:
Pls support dolby for magisk 16.7. I flash last version 30.7.2018 and i dont see dolby app.
[Android Software Development] dm00389731:
I am a noob....i am using oxygen os 5.0.4( oreo).i am using magisk v16 and latest magisk manager . Please please tell me the procedure of flashing dolby atmos. I tried many times through twrp and magisk also but fails to install
[Android Software Development] Infy_AsiX:
There's an old Nougat Dolby that still works with Viper4A on 8.1. It originally had an old Pixel XL2 8.1 guide that was found to work on Axon 7 8.1 recently too. I created thread in depth about usage and preferred benefits over the Oreo Dolby version too. See here https://xdaforums.com/axon-7/themes/info-n-dolby-port-v4a-setup-custom-8-1-t3824475
[Android Software Development] Ớt xanh:
Thank bro
[Android Software Development] breacherman:
I tried to read through a lot of this thread (269 pages so far)but that left me even more confused, i don't understand half of what's being discussed.

LG V30 Magisk 16.0 / flashed DolbyAtmos_Axon7_Oreo_Unity_2.20.18.zip

Phone won't boot, just sits at LG logo. Tried this twice, second after clean wipe.

I also have a botched install (crash/force close) of the standard (DolbyAtmos_for_Oreo_20180219.zip) version, is there anyway to remove these without wiping the rom?
[Android Software Development] konsolite:
I'm also using this mod, because Viper processing with it via bluetooth.

New Dolby requires workaround to start processing Viper, but if music is stopped Viper needs to be re-enabled so it is very annoying. Is there any chance to fix that?
[Android Software Development] Miamori86:
Tested on redmi 3x, pixel experience update 22.05.18, magisk treble 16.4..im using latest dolby atmos build 30.7.18

Reading through all the comments i was affraid im gonna hav bootloop too,which i really prefer not to since i just got out of it yesterday for another problem...but now im happy, everything works great execept for gcam (i feel your frustration land users :laugh:) still need a workaround to get it work..

Anyway, i know this is out of topic but if you are on pixel experience the only working solution for me to get gcam to work is to disable screen lock then reboot your phone..once ur gcam working u can set the screen lock back again..but remeber next time you reboot your phone with the screen lock still on your gcam will stop working again and u hav to redo the steps mention above all over again..
[Android Software Development] 12Fully:
Has anyone tried running on official Android P yet?
[Android Software Development] nspacedust:
Yes I tried. Doesn't work
[Android Software Development] clyde13:
is this working on any device running oreo?
[Android Software Development] crackerjack1957:
Not working with Magisk 16.7 or pie.

Works on Pixel XL with Magisk 16.3 on stock rom
[Android Software Development] panicker666:
Oreo is mentioned on the first post. It's working on my z2_plus AOSiP treble/oreo 8.1/magisk v16.7
[Android Software Development] berrytaylor56:
I recently came across your blog and have been reading along. I thought I would leave my first comment. I don't know what to say except that I have enjoyed reading. Nice blog. I will keep visiting.
[Android Software Development] d3vyarth:
Probably AOSiP is the only treble oreo ROM that supports Dolby on Z2Plus.