yashsingh1/xdaforums huggingface dataset:
[Android Software Development] Mr.Demous:
Latest Unity build working great on my Nexus 6 running Nitrogen 8.1

Thanks [MENTION=4445176]guitardedhero[/MENTION] [MENTION=6037748]Zackptg5[/MENTION]
[Android Software Development] docnok63:
Sorry Zach, I got a busy yesterday and couldn't help until waking up early this morning. I'm pretty sure you guys are going to like this post...

For everyone having bootloop problems, GH has been correct all along in assuming that the issue is with the audioserver. How do I know this? Thanks to this post, I was able to obtain a logcat on boot and can see exactly the line that stops the device from booting. Right after initializing with multiple errors above it, it fails to boot with:

02-10 04:59:39.809 1551 2669 I imsrcsd : Successful Initialization
02-10 04:59:39.809 1551 2669 I imsrcsd : Starting Service for First Time
02-10 04:59:40.113 1715 1715 I ServiceManager: Waiting for service media.sound_trigger_hw...
02-10 04:59:40.367 1818 1818 W /system/bin/audioserver: Waited one second for

As GH said from the get go, I believe that his audioserver database is going to be key in getting this working for all. If you fail to boot after an install, don't just wipe everything and post that your phone won't boot with the latest build here, as GH previously instructed in this thread....

1) Boot into recovery and hit the 'Mount' button and mount system.

2) Hit the 'Advanced' button and select 'File Manager'

3) Use the file manager to navigate to system/bin and copy both audioserver.original and audioserver to another directory

4) Now you can wipe and restore your system

5) Once back in Android, rename the two files with a .txt at the end so they will upload to XDA (audioserver.original.txt and audioserver.txt) and upload them here with your device, ROM. and build date.

Let me start:

OP5 Dirty Unicorns 12.0 20180122-2058-RC

[MENTION=4445176]guitardedhero[/MENTION] and Zach, I've also attached a zip with my full logcat, recovery.log, and a text comparison between the two files

EDIT: It would also be cool for people that have Atmos properly working (especially with V4A (the ultimate goal)) to post their files so that those that fail to boot can try another audioserver. NOTE: ONLY use an audioserver from your device. Example: I'm on OP5 DU. I can try OP5 Omni ROM audioserver which I think I've seen in this thread is booting. We can make this a community thing helping each other.
[Android Software Development] repey6:
Thanks. Supersu roms installed and started without issues.:good:
[Android Software Development] KryptonKal-El:
I installed the latest build today 20180210 dolby atmos:

Device - Nexus 6

ROM - S.I.X. 8.0

Root: SuperSu

It works as expected but with minor glitches. When I go into the app and press the power button to disable DA it still shows the power button light is on instead of off. It does actually turn off DA as you can hear the music effects drop but the GUI looks like it's delayed or stuck. I have to close out the app and go back into it again then it will show the power button off. Same thing happens when you reset the equalizer by tapping on the circular arrow it doesn't reset to defaults right away until you close out the app and go back into it again.
[Android Software Development] laugeek57:
20180210 - works fine on mi A1 :D
[Android Software Development] Rehan Sheikh:
Not working on Redmi Note 4 running pixel experience 8.1.0 Logs attatched
[Android Software Development] Albert Poon:
After I cleared cache/dalvik it works now! Just have the graphical glitches mentioned by another user above.

Great work man!
[Android Software Development] genuine55:
[MENTION=4445176]guitardedhero[/MENTION] what's the unity version for ? Thanks and I got a error 1 error when flashing the viper zip and idea ?
[Android Software Development] onliner:
1- Dolby/Viper + AML

2- Logs.
[Android Software Development] genuine55:
Ok thanks what do I use to get logs and how do I do it if u don't mind helping ?
[Android Software Development] onliner:
Flash zip > error > go to Mount, check "system", go to Advanced/File Manager/cache/recovery/last_log
[Android Software Development] OldMid:
After trying again, system doesn't finish booting after successfully flashing on RR op5t, works on other toms though, [MENTION=4445176]guitardedhero[/MENTION] if you don't mind me asking, what device do you use for testing?
[Android Software Development] Jonizz:
What happened?[IMG="What the..."]http://i.imgur.com/WxUJwUO.jpg[/IMG]
[Android Software Development] OldMid:
What ROM and device do you have? You've got no init.d support on your ROM, which is required during boot
[Android Software Development] Jonizz:
OxygenOS OB31 with magisk on OnePlus 3.
[Android Software Development] OldMid:
Strange. Reflash, then go to the advanced menu of twrp and save the recovery log, then upload here
[Android Software Development] Jonizz:
When i flash IT through twrp, i get bootloop so i won't do that.
[Android Software Development] OldMid:
No, after flashing, don't reboot, just press home and go to advanced

Then use unity installer to uninstall and reboot
[Android Software Development] repey6:
Thanks a lot for your wonderfull build! It start stable with any root.:good:
[Android Software Development] onliner:
Flash in twrp.
[Android Software Development] AquaBytez:
I have tried this mod with pretty much every OnePlus 3 rom. Out of all of them, only NitrogenOS boots, which is odd, because one would think that OxygenOS would also boot. Having osm0sis' Busybox magisk module doesn't seem to be a factor whatsoever on whether the device will bootloop or not, so that assumption isn't true, at least for this device.

Anyways, I have attached both, the recovery log and magisk's log. (found under /cache/magisk.log). Additionally, I attached audio_policy and audio_effects (mine is a .conf file, I didn't find an XML version of it anywhere. I also had to add .txt in order to be able to attach it) As a final note, since all logs are identical, I attached the ones from my current ROM (ResurrectionRemix v6.0.0[android-8.1.0_r11]).
[Android Software Development] lacsinasonny:
I haven't faced any problems in installation of the zip. I installed thru twrp. The module is present on the modules tab on magisk as well as the app in the app drawer. But one there was no effect on the sound output. I have a Lenovo Vibe K5 Plus and using PixelExperience ROM. Also, I don't have any sound mods installed aside from this dolby port.
[Android Software Development] guitardedhero:
You have my word that if such an avenue becomes available I will be all over it. It was difficult to describe my philosophy without appearing to be dismissal at the same time and this philosophy is completely absent of any familiarity with the stock experience outside of the audio feature set as well so I certainly understand your preference to avoid it if at all possible.

Your assessment of LineageOS has me intriqued, though. I will see what I can find regarding its utilization of any vendor audio components. I, perhaps irresponsibly, just assumed it was typical CM audio service AudioFX fare. :good:
[Android Software Development] guitardedhero:
Did you try powering the app On and Off while adjusting any of the parameters below during audio playback?

Would you be able to provide the audio effects configuration(s) symlinked to the normal locations in /system after boot for me to examine? :good:
[Android Software Development] guitardedhero:
Understood. :good:
[Android Software Development] Teet1:
Yes indeed. ZTE worked with the LOS developers to get audio working like stock and even gave them the Oreo blobs to build lineageOS 15 but cannot release it until ZTE releases their official Oreo release. The DAC and stereo speaker was working as well as a port of the nougat Dolby Atmos version. So most of us had near or equal to stock audio on custom ROMs ranging from lineageOS to resurrection remix to unofficial builds of dirty Unicorn
[Android Software Development] guitardedhero:
Ah, indeed. This is very familiar now thanks to your reminder! :good:
[Android Software Development] Teet1:
Sorry of this takes time away from more important things like making this compatible wirh many devices as possible and fixing bugs and errors. I suggest making the axon 7 a low priority. We just can't wait until April if any release is coming. That was only for global, not even for the US variant. But who wouldn't wait either? :D if this works for us, then this will work for every 8.1 custom ROM in the duture. Thanks for your help!
[Android Software Development] g3v0:
Still bootlooping on Pixel 2 XL. I looked at the logcat and noticed it kept repeating about waiting on the audio. I attached a logcat of the part where it just started repeating.

Two lines stick out to me:

01-26 20:01:05.490 2427 2427 E hardware_info: hw_info_init: Unsupported target msm8998-tavil-taimen-snd-card:: /vendor/bin/hw/android.hardware.audio@2.0-service

01-26 20:01:05.964 1243 1557 W AudioSystem: AudioPolicyService not published, waiting...: system_server

After disabling the module and rebooting, I looked through the logcat again and saw the "Unsupported target" line again (only once or twice), but the process name for it was blank, whereas it had the fullname "/vendor/bin/hw/android.hardware.audio@2.0-service" when it was looping. It also never gave the "AudioPolicyService not published" warning.

Not sure if either point is important or I'm just chasing after red herrings :(
[Android Software Development] guitardedhero:
Changelog

:

[B]20180126-5 -[/B]

- Boot scripts restructuring and
enhancements targeting successful
device boot and additional
functionality.
[Android Software Development] guitardedhero:
Sorry guys...

Changelog

:

[B]20180126-6 -[/B]

- Slight adjustment to scripts.
[Android Software Development] Rickyloc:
Bootloop

Wouldn't boot waited 20 minutes. Here is a log. I'm sure there is something super simple I am missing.
[Android Software Development] guitardedhero:
Very interesting report I just observed in a separate thread informing those device owners of this port:

https://xdaforums.com/showpost.php?p=75341915&postcount=50
[Android Software Development] guitardedhero:
This log contains the series of events during the installation of 20180126-4, the version immediately before changes addressing bootloop issues and functionality issues.

However, the log shows nothing that would make one conclude a successful device boot would not result.

Nonetheless, please try again with 20180126-6. :good:
[Android Software Development] Rickyloc:
Totally forgot to mention what I was running.

OnePlus 5

Pixelexperience rom 8.1

Fk kernel

No other sound mods

Gonna flash again thanks pal.
[Android Software Development] Sukeshj26:
Hi bro

Is this mod working

Iam on Oreo 8.1 OnePlus 3 (custom ROM )

Before I flashed this Mod it caused bootloop
[Android Software Development] guitardedhero:
You know, you just reminded me of something...

Ever since upgrading to Oreo, and possibly even before that, I have found it not too uncommon to experience a bootloop at times that was immediately resolved by a press of the power button until a forced reboot began, at which time the device would almost always successfully boot immediately. This literally happened mere hours ago as well.

This may be unique to OnePlus 5, but either way...

If experiencing a bootloop...

DO NOT GIVE UP!!

​

Hold down the device Power button until a reboot is initiated... and then give up if a successful boot fails to occur lol. :good:
[Android Software Development] Skittles9823:
I find that procedure only occurs on magisk and only fixes it when stuck on the bootloader for me.
[Android Software Development] MikeW14:
i'm having trouble with this. i'm running abc rom on my nexus 6p. the dolby-oreo zip you provided weeks ago works for me, but when i tried to install this axon 7 oreo, the app force closes every time i try to use it. am i missing something?
[Android Software Development] theduke7:
wow...it was actually , i tested with -4 and the latest -6, and yes uninstalling busybox made the dolby effects work

here's few things thoguh, 1st from v4 from last night, the compatibility issue with other modules is now seems fixed on v6 , and while testing on v4 it seemed to me that it had a mind of it's own, it wasn't a spicific module , it was just sometime the app showed and the files were placed and sometime they weren't.

also the prop file on v4 still doesn't affect the flashing it just flashes the magisk module if it detects magisk, but i noticed that (that's only tested on v4) if i set install to system to true, the module worked every time (given all other modules were disabled) , if prop file is not there at all or without value, sometime files were placed other times it didn't

as you said the power button doesn't seem to be working visually, but it does when pressed turn on/off dolby... that said, it did visually work for me , here's how, press the turn off button and then close the dolby app window, then open it again ...it will be off and will be turned on when pressed.

lastly about the boot loop, you're right, some of(most of) were fixed by just shutting down the device and turning it on again, but the loop on v6 seems strange (when it happened) at 1st the screen kept turning off (the lights went off) and then on again ...also the 2nd time after i shut the device down, it went all the way to the home screen and after 5 sec or so it rebooted ...it didn't occur again though, so far on v6 all seems to be working fine as a Magisk Module,

The one Module it had issues with for sure on v4 was the iytbp module (modded youtube) , that was the only module that if it was enabled dolby didn't show up...but on v6 this seems to be fixed ...

sorry for the long post, and thank you for the great work.

Edit/ if you need any file or log please let me know.
[Android Software Development] oehajo:
Dear developer, would be glad to test Your work. Im on Axon 7 Oreo (8.1) PNW. When i trie to add the zip as module in Magisk it always says: No magisk modul, no other hint. In Recovery (trwp) installing starts, says Installing..., then nothing happens. Why does magisk Your zip-file not recognize as magisk-modul? Would be so glad, if it would be installable. In the prop-file i set magisk systemm install an aditional lybrary as true. Help would be kind. And thanks for investing time an brain for our welfare.

Hansjörg

Copying zip to temp directory

! This zip is not a Magisk Module
[Android Software Development] AquaBytez:
--This is a duplicate of the previous post--
[Android Software Development] kamilmirza:
bootloop on both

find the attachments
[Android Software Development] CatoBass:
Error : 2, when flashing in TWRP.

Sony xz, Duality ROM, Oreo 8.0. Magisk V14 (not updated Magisk manager)

XDA won't let med attach recovery.log...
[Android Software Development] Albert Poon:
Move the recovery.log from sdcard to internal storage before posting it.
[Android Software Development] veetoe:
Pixel 2 xl. Atmos installed with no FC and the effects get loaded, but no sound processing.
[Android Software Development] stargzrr11:
Same on Pixel (1) XL
[Android Software Development] CatoBass:
Error : 2, when flashing in TWRP.

Sony xz, Duality ROM, Oreo 8.0. Magisk V14 (not updated Magisk manager)
[Android Software Development] sonophilos:
Presenting...

Dolby Atmos for Oreo 20180210 Standard - Black 'n Cheese Edition

Changes:

Updated base to 20180210

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

Changes:

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

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

Check sonophilos_README.md inside for information on getting the full intended effect out of my profiles.
[Android Software Development] Zackptg5:
Good to know. You said you boot with the unity installer right? Can you send a logcat with the unity build?
[Android Software Development] AquaBytez:
Ok, as [MENTION=4967345]docnok63[/MENTION] suggested. I attached both the original audio server and the modified one (grabbed them after mounting magisk.img to /magisk/)

OP3 ResurrectionRemix v6.0.0[android-8.1.0_r11]

Both of the files appear to be identical. So perhaps, that's why it RR doesn't boot.
[Android Software Development] RalphMalph:
I tried to find but cannot find it.

What is the difference between Standard and Unity release?
[Android Software Development] onliner:
Bootloop
[Android Software Development] konsolite:
Let me join to this question. Please explain difference between Standard and Unity. Is there any GUI/funcitonal changes?

I've installed Unity and it works on Redmi Note 4 with LiquidRemix.
[Android Software Development] carlosorta:
Test with Xiaomi Mi A1

I've got an error at run DolbyAtmos.apk, it says "Dolby Atmos Stopped", the module is installed in magisk and everthing in the installation is fine, but when boot up the Mi A1, dont appear the Dolby Atmos APK and when I run post-fs-data.sh I get the message "/system_root" is read only, I changed the file and I change this:

odm=/odm #$root

audio1=/system_root/system/vendor/etc/audio #$root

etc0=/system_root/system/etc #$root

etc1=/system_root/system/vendor/etc #$root

and at the end of the file before "exit 0" I put this

setenforce 0

When I reboot the device I install the apk contained with the zip file and Dolby Atmos work's like charm.

I tried the installation of DolbyAtmos_for_Oreo_20180209-1.zip with TWRP (I boot the TWRP image, I install the Mi A1 TWRP and then I boot the TWRP installed and I install the mod, then I restored the boot.img patched by Magisk to "preserve" the OTA)
[Android Software Development] exodius48:
Could i run both in one device?

---------- Post added at 10:23 AM ---------- Previous post was at 10:18 AM ----------

Does dolby in your device works with sound processing?

I have Mi A1 Also, but no sound processing. Test with standar version, unity version give me bootloop.
[Android Software Development] JIJIN JOSE:
installed and booted successfully...no app fc.....but audio is not processed....any help?

i installed Unity_2.9.18.zip through magisk
[Android Software Development] dead0:
just to add, for OP3, nitrogen os and z unleashed seem to be working fine with the dolby audioserver file. others stuck in bootloop. for example with aospextended 5.1, ive also tried adding audio libs from nitrogenos to try to make it work but to no avail. one thing i havent tried is replacing the android.hardware.audio@2.0-service in vendor/bin/hw from NOS

edit: that doesnt work either

just another thought, on the roms that work with the audioserver file, could they possibly be using audioserver thats based on oreo 8.0 rather than 8.1?
[Android Software Development] jandia7381:
Just reporting - unity build 02.09 working great on my Kate running latest Nos Magenta 8.1. TQSM dev and all teams :svetius:
[Android Software Development] exodius48:
Can you tell me which magisk module you've installed? and which v4a version? I tried almost v4a alongside dolby by gh, but none of them worked, all show me abnormal driver status.

------------------------------------EDIT--------------------------------------------------

Oh wow, after i see your screenshot, your rom selinux is permissive, so i install Magisk selinux permissive module to get v4a work alongside dolby and voiiila, it working good.

Btw [MENTION=8383546]sonophilos[/MENTION] i can install both, v4a driver is normal and dolby working and there is dolby sound processing. But when i disable master power in v4a no sound processing, its normal, then the issue is when i enable it again, there is no sound processing in v4a, any clue or fix for it???
[Android Software Development] AquaBytez:
The pattern seems to be that roms based entirely on AOSP work just fine, and those based on LOS will bootloop. As a side note, in NitrogenOS, I have to flash ARISE with the magisk compatibility module and the audio effects configuration of either ASUS or Huawei in order to get Viper and Dolby to play nice with each other.

Installing AML on NitrogenOS will make ALL audio mods disappear from the drawer and FC every few seconds.
[Android Software Development] docnok63:
No, I've never been able to boot with DU ROM. I was functional early in the previous thread on stock OOS 5.0.0. I just tried the latest Unity build and it bootlooped with basically the same errors, but yours added that audioserver had died:

02-10 23:57:55.707 1192 1541 E AudioService: Audioserver died.
02-10 23:57:56.208 1192 1541 E AudioService: Audioserver died.
02-10 23:57:56.305 1192 1192 I ServiceManager: Waiting for service media.sound_trigger_hw...
02-10 23:57:56.452 2187 2187 W /system/bin/audioserver: Waited one second for android.hardware.broadcastradio@1.0::IBroadcastRadioFactory/default. Waiting another...
02-10 23:57:56.708 1192 1541 E AudioService: Audioserver died.

This is because your audioserver is different than the one produced from the Standard installation. Also, your installation doesn't make an audioserver.original to fall back on to boot.

I've attached a zip with the full logcat, both the Standard and Unity audioservers, and a hex comparison of the two in html format (they're quite different.)
[Android Software Development] exodius48:
Woaaah...too advanced for noob like me.

As i know "SETENFORCE 0" is same as permissive mode selinux, so install magisk permissive selinux module solve the problem. CMIIW :D
[Android Software Development] jandia7381:
I'm using viper from fx manager by dev who made shadow kernel, u should try it
[Android Software Development] diculess:
No change

Successfully installed the latest version without any error but didn't take effect even if busybox checker reported busybox not found.

I was once installed and used Dolby-Oreo.zip but it suddenly crashed after a reboot, then return error 2 every time I flashed it.

Pixel on 8.1
[Android Software Development] Albert Poon:
[MENTION=4445176]guitardedhero[/MENTION] [MENTION=6037748]Zackptg5[/MENTION],

I have done some further tests, the standard-20180210 installs, boots, app starts and works fine, while unity-20180209 installs, boots, app starts but not processing. I tried to look for those \n lines but seemed not the case this time.

Let me know which logs are needed.

---------- Post added at 10:02 AM ---------- Previous post was at 09:51 AM ----------

My bad. When I tried the unity version I forget to install the AML. After installed AML it works fine now. This is also to confirm that both version work fine for HTC U11 stock Oreo.

Many thanks!
[Android Software Development] g3v0:
Can you guys upload your audio_effects.xml and audio_policy_configuration.xml (should be in vendor/etc)
[Android Software Development] exodius48:
Any link for it?
[Android Software Development] Bordo_Bereli51:
When I install the standard version, I get bootloop on Huawei Mate 10 Pro. I read the logs and it says : [ERR] chcon: too few arguments

Look at picture
[Android Software Development] mohsinreadymoney:
how to use with Viper4Android, V4A showing I/O error
[Android Software Development] jandia7381:
Here u go https://xdaforums.com/redmi-note-3/themes/app-viper4android-fx-installer-t3703575/page6

Just trying with aml+sauron and all just fine :cool:
[Android Software Development] repey6:
You can to try from here:D