yashsingh1/xdaforums huggingface dataset:
[Android Software Development] guitardedhero:
From where was audio_effects.xml taken when shared in your post?

Your xml and dumpsys output indicate that the Dolby entries are not in the xml and that /vendor/lib/soundfx/libjamesdsp.so does not exist - addressing the null at the top of dumpsys.
[Android Software Development] guitardedhero:
If you pass the compatibility check at the beginning of the installation it will work as long as the installation targets and patches the necessary files appropriately.

Only one way to find out, though. :good:

If anything further is needed to accommodate both at the same time, I'll make it happen.
[Android Software Development] NE0HP:
It does work for me as stated here https://xdaforums.com/android/software/app-dolby-atmos-axon-7-oreo-port-t3740508/post81506677 but dunno I experienced few apps fc such as YouTube, VLC, chrome etc.. system ui also freezes especially when tapping on notification under apps and notification.... and if I remove the module then everything works fine...can anyone here who got success on 10 is facing such issue or it is just me or is it rom related issue?
[Android Software Development] guitardedhero:
It is the port causing these issues if they were not issues prior to installing the port.

Delete /data/adb/modules/dolbyatmos/system/lib(64)/libstagefright_omx.so
[Android Software Development] btb55:
Thank you, impressive work. Installed 20180202 on OP3T with OS 5.02 and Magisk 15.3, flashed in recovery (blu_spark 861). Audio is being processed, various profiles seem to be as expected, very good :)

Selinux is Enforcing.

One question, should I keep or disable the stock Dirac apps?
[Android Software Development] LabLab...28:
Kind of noob here. Anyways this is my first time using this mod, i just flashed the 02/02 build but twrp says error 1. Im using cosmic OS 8.1. Am i missing something before flashing? Should i edit the prop file first like arise? Any one can explain in layman's term. Thanks in advance:)
[Android Software Development] Curiousn00b:
I get the same error as well, just going to wait for the next release.
[Android Software Development] LabLab...28:
Do i need to edit first the prop file inside the zip before flashing bro? Or any extra steps first before flashing the zip?
[Android Software Development] Curiousn00b:
Yes. The prop, you should input true for either Magisk or SuperSU, depending on which you are using.
[Android Software Development] Golv:
[MENTION=4445176]guitardedhero[/MENTION] THX for your great work!

I got ERROR: 1 too.

HTC U11 (Oreo), Magisk 15.3, Dolby Atmos™ ZTE™ Axon 7 Oreo 20180202 (DolbyAtmos_Axon7_Oreo_20180120-1.zip working fine fo me)

# /sdcard/arise_parameters.prop

magisk.system.install=true

install.add.libraries=true

Recovery log attached.
[Android Software Development] Trupen:
Earlier zip which used to work is now giving boot loop 29 build

---------- Post added at 10:36 AM ---------- Previous post was at 09:41 AM ----------

[MENTION=4445176]guitardedhero[/MENTION]
[Android Software Development] arifqur:
Was getting error 2 in twrp then moved the zip file to the root of the sd card and am now getting error 1.

What is going on here?

Can't think of anything else to try
[Android Software Development] sille:
Hey [MENTION=4445176]guitardedhero[/MENTION]

im using the OP5T with Codename Phoenix (8.1) decrypted. I only got one Revision of your Port that is working for me.

Preconditions:

Using Magisk 15.3, letting the .prop as it as (no change to true etc etc) and flashing the 17.01 build. -> Working

If i try to use any other Version, the Device is getting in a Bootloop.

If i try to edit the .prop to magiskinstall true and / or true to additional files, it bootloops.

Also i thought that if i set magiskinstall to true it installs the Atmos Port to System but in my case its always installed in /magisk.
[Android Software Development] Ethan140310:
Installed and running but no processing I believe, changing the EQ gives no effects...

Will try again in newer builds, hope it can be fixed.
[Android Software Development] Mr.Demous:
Still can't get it to work properly, Magisk disappears no matter what install option I use.

I'm also getting ERROR 1 on 0202 when I try to install it as Magisk system install.
[Android Software Development] arifqur:
The new version installs but goes into a bootloop no matter what options I choose in the prop file
[Android Software Development] shamsul007:
Tried this. Magisk modules came back and so Dolby showed up.

Unfortunately it's not processing any audio at all. Turned off V4A and messed around with Atmos and found no difference.
[Android Software Development] :
Installed the latest version. Phone went into a bootloop. Somehow revived the phone. All magisk modules had disappeared. Got them back too. Safetynet failed. Revived it too. Dolby app is shown as installed. Trying to open it force stops it. Tried flashing it for three times. Same things happened for three times. Have SELinux permissive v1.2
[Android Software Development] Trupen:
[MENTION=4445176]guitardedhero[/MENTION] pls find the attachment for log

Flashed Dolby successfully but boot loop

Pls help us find the solution
[Android Software Development] Teet1:
[MENTION=4445176]guitardedhero[/MENTION] I figured out how I got it to work and what may be causing bootloops for some devices. At least on the zip I tried which is 20180129-1, I set install.add.libraries to true in arise_parameters.prop and flashes fine in TWRP (unlike more recent and past versions) but then met with a bootloop. I deleted the audioserver file in /system/bin in TWRP with file manager, and then took out the audioserver file from the zip and moved it to my micro sd card, and used these commands in Terminal to move it to /system/bin

cd external_sd

cp audioserver /system/bin && chmod 655 audioserver

once that is done, I rebooted, and it worked. I just tried this exact same thing with my brother's Axon 7. Flashing is fine, but met with bootloop. Doing the above makes Dolby Atmos work 100%

I think something happens when your zip tries to move the audioserver file. At least maybe on certain devices.
[Android Software Development] guitardedhero:
Changelog

:

[B]20180205 -[/B]

- Initial release integrating Unity
installation and scripts courtesy
of @ahrion and @Zackptg5.
[Android Software Development] guitardedhero:
Massive shout out to [MENTION=6037748]Zackptg5[/MENTION] for making today's update possible. :highfive:
[Android Software Development] saiamrock:
Using latest unity, but when music play it not processing
[Android Software Development] guitardedhero:
Did you tap the Power button during audio playback to see if it was not On, since there is currently no visual confirmation at this time?
[Android Software Development] gokart2:
Believe my manifest.XML wasn't updated correctly? I also posted logs on page 420
[Android Software Development] guitardedhero:
Indeed, it wasn't patched at all.

What is the specific location of this file starting from /sbin/.magisk/mirror/?

Are you normally able to write to system or vendor while booted?

What device/rom?
[Android Software Development] NE0HP:
Deleted, rebooted device but no luck.
[Android Software Development] guitardedhero:
Delete /data/adb/modules/dolbyatmos/system/vendor/etc/mefia_codecs_*_audio.xml and reboot.
[Android Software Development] gokart2:
/sbin/.magisk/mirror/vendor/etc/vintf

For sure system. BUT...found my partition minting is weird, unlike I remember. You have to mount via

mount -o remount,rw /

not /system or partition name like /Z2FFO. And it boots not mounted, need to script mount when I make a change.

I'm not sure about vendor though, will try.

Moto Z2 Force, LOS 16

Edit: I can mount vendor and alter files.
[Android Software Development] NE0HP:
Sorry..still no luck. :rolleyes:
[Android Software Development] guitardedhero:
Delete /data/adb/modules/dolbyatmos/system/vendor/lib(64)/libstagefrightdolby.so & libstagefright_soft_ddpdec.so
[Android Software Development] guitardedhero:
Added [MENTION=4267845]gokart2[/MENTION]'s rootfs mounting suggestion to the installation script. Thank you, buddy. :good:
[Android Software Development] gokart2:
Anytime homie! I'd be so much more depressed if my music wasn't crystal clear and bumping hard. Its crazy to think about it, but you've made my life better by taking care of my anal-ness for audio perfection! OK, enough brown nosing. :laugh:

I didn't see anything about an uninstaller in the zips or thread? I assume I can just flash over .71?
[Android Software Development] gokart2:
[MENTION=4445176]guitardedhero[/MENTION]

.72 fails to flash via magisk. Would attach the log, but there's not much, just

Copying zip to temp directory
! Installation failed

No other logs show anything, cache ones...which I assumed.

Here's .071's log.
[Android Software Development] avaie:
Is there anything I'm missing. Dolby processes everything but music through the music player. There is almost no difference in processing. The device is LG V40. It processes notifications, clicks and other system sounds but music playback isn't.

So far, there is no audio server. Perhaps it is renamed.
[Android Software Development] NE0HP:
This doesn't work as well.. but just wanted to update you, if I install v64 from here https://xdaforums.com/android/software/app-dolby-atmos-axon-7-oreo-port-t3740508/post81491919 then It works fine and I don't face any app/ui freezes as mentioned earlier..
[Android Software Development] laugeek57:
DolbyAtmos-axon9-A10-0.64

Works fine on One plus 7 Havoc OS 3.1

just disabled Dolby Atmos stock ;)

Magisk v20.3

Thanks !!! Guitardedhero the legend of Dolby Atmos port :D
[Android Software Development] Alejndrox097:
The app won't work. Los 16 S7 Edge.

There's no file called audio_effect, but one called audio_policy.conf

Edit:

Ver 0.72 > installation failed.
[Android Software Development] guitardedhero:
Indeed, uninstallation will never perform no matter how many times you install the zip.

Magisk Manager has a dedicated Disable/Uninstall feature for each installed module in its Modules tab that allows you to manage a module however you wish.

Installing an update over an existing module will update the module, never uninstall the module.
[Android Software Development] gokart2:
Not sure exactly about .72.? Tried reflashing .71 and fail. Tried flashing other known good modules, all fail. Found I wasn't mounted anymore and BusyBox missing? Lol. Will try a clean flash after I get home.
[Android Software Development] guitardedhero:
Sorry, a "fi" must have run away...
[Android Software Development] scaschera:
Hi,

The bluetooth earphone sound issue is fixed on this Newer version ?

Thx for your works
[Android Software Development] guitardedhero:
Is this issue only present when using the app or persistent even with DolbyAtmos turned off?

If only while using the app, you might try changing Bluetooth codecs in Settings > Developer Options.
[Android Software Development] scaschera:
The issue is persistent with on and off, and After uninstall module aswell, i must rollback with a twrp backup before installing module

Edit : last version not work on A5 2017 PE 9, app not open , and tile is greyed
[Android Software Development] avaie:
Can you share the file?
[Android Software Development] guitardedhero:
I want to apologise for the various media issues introduced by the flashing of these zips.

The installation does not use Magisk module template scripts or anything else found anywhere and I failed to notice I had not included a command to delete the entire dolbyatmos module folder before

the installation begins.

This has seemed to cause the media codec xml copied to the module to be patched each consecutive flashing of any of these zips.

Apparently, multiple instances of identical decoder elements collapses the entire xml, although, the intention all along has been to ensure any patching of a file occurs only once.

:good:
[Android Software Development] guitardedhero:
Please provide /sbin/.magisk/mirror/vendor/etc/vintf/manifest.xml
[Android Software Development] scaschera:
Uninstalled 7.2.1 and install 7.2.2 make Bad think

No app in drawer
[Android Software Development] scaschera:
And i have this in magisk
[Android Software Development] guitardedhero:
Does the following file exist:

/data/adb/modules/dolbyatmos/module.prop

If so, what are its contents?
[Android Software Development] guitardedhero:
Does the following file exist?

/data/adb/modules/dolbyatmos/system/app/DolbyAtmos/DolbyAtmos.apk

If not, does the following folder even exist?

/data/adb/modules/dolbyatmos
[Android Software Development] laugeek57:
https://xdaforums.com/showpost.php?p=81491919&postcount=3671
[Android Software Development] gokart2:
[MENTION=4445176]guitardedhero[/MENTION]

So, I started with 100% clean LOS 16. Flashed .722

Got log of pressing app, but no GUI opening. I moved a few things around in the log so its quicker to view.

Also got a log of the chaos that happens when I press the add Dolby tile.

And a dumpsys. Install log ADDED

:good::good:
[Android Software Development] guitardedhero:
I know you guys are tired of me apologising, so I'm not lol.

I just now spotted a vendor variable error breaking or misdirecting several functions. I don't know how many versions this has been included, but certainly a few, at least.

The corrected version is attached below.
[Android Software Development] ramrastus:
This version works on android 10 oos ?
[Android Software Development] stxyec:
This version works on android 9 oos.
[Android Software Development] guitardedhero:
Yes, I omitted "PIE" from the zip's name so that it would no longer be confused as being limited to Android 9 since more than enough Android 10 testers have confirmed the port to be functioning - even with my many, many mistakes lol.
[Android Software Development] guitardedhero:
All is working okay for you now?
[Android Software Development] guitardedhero:
Just so you guys know, all zips from 0.7 to 0.722 have borked variables and should not be flashed.

0.723 has the fix (which ends up fixing many others) and is the only zip to flash, unless a version before 0.7 (when new variables were introduced) works great for you.

I have removed all attachments I could find and if any others are found attached or shared elsewhere, it would be a very kind gesture to point out the issue so that it can be removed or replaced with version 0.723 or higher.
[Android Software Development] _BГ@ckθut:
Lol i still using 0.64 :)) it work well but some of my people gor Bluetooth issues that won't turn on some how...and yeah they are on OOS 10 :(( but yeah good work!
[Android Software Development] Alejndrox097:
Same with los 16, Broken.☹️
[Android Software Development] stxyec:
Yes,thank you.
[Android Software Development] Bogdans29:
Wow.. Can you just make that zip for me without compactabilty check to try it out.. Myb will work?
[Android Software Development] anvesh583:
Flashed this zip on a10. System UI isn't responding error popping up like in the case of Sony port . SS , volume buttons borked etc. Strangely effects seem to be working .
[Android Software Development] Soumy1234:
I've tried installing this on my OP7Pro running OOS 10.3.0 but it keeps crashing. Please let me know if I need to provide more information.
[Android Software Development] NE0HP:
I have tried almost all version posted by OP including the latest v723 and in all version, system boots and port works fine but facing certain apps/UI freezing but surprisingly not in the one that you posted (v64) so I stick with v64 for now.
[Android Software Development] avaie:
Thanks.
[Android Software Development] bobdeepith:
Hey bluetooth is not switch turning on my device poco F1 Oxygen OS Q port rom (android 10) please check log below attached
[Android Software Development] Kuljeet Singh:
+1 [MENTION=4445176]guitardedhero[/MENTION] OOS OP6T Android 10

Edit: removed the module still Bluetooth not turning on :confused: I can confirm it worked before :(

Edit 2: dirty flashing rom made by bluetooth work again
[Android Software Development] laugeek57:
Same on my OP7 OOS 10.3.0 because not option for disabled Dolby Atmos stock...

Itested with Havoc OS 3.1 works fine :D
[Android Software Development] lkp171:
Same here, but i then istalled the same dolby zip again and everything works fine since then. Don't know why tough
[Android Software Development] Kuljeet Singh:
Bluetooth works? If it does work, try rebooting and see if it still works. Mine wasn't working when I rebooted.
[Android Software Development] lkp171:
Yes i rebooted several times after i flashed dolby. But as mentioned after my first flash my Bluetooth was broken and i needed to dirty flash my os, i can't really give more info, b3cause i work with (try - error - repair - retry) ?
[Android Software Development] Feardarks:
workıng great on Redmi 6 pro with OOS GSİ android pie
[Android Software Development] louis-JYG4t:
[MENTION=4445176]guitardedhero[/MENTION]

The "surround-boost-value" in the following coding, what's the range of the value? Is that in percentage?

Is a reboot required to make the changes go into effect?

<endpoint_type id="headphone">

<calibration-boost value="0"/>

<dialog-enhancer-enable value="true"/>

<dialog-enhancer-amount value="0"/>

<dialog-enhancer-ducking value="2"/>

<surround-decoder-enable value="true"/>

<surround-boost value="96"/>

<volmax-boost value="96"/>

<volume-leveler-enable value="false"/>

<volume-leveler-amount value="0"/>

<volume-leveler-in-target value="-320"/>

<volume-leveler-out-target value="-320"/>

<graphic-equalizer-enable value="true"/>

<virtualizer-enable value="false"/>

<bass-enhancer-enable value="false"/>

<virtual-bass-process-enable value="false"/>

</endpoint_type>
[Android Software Development] ShadoV90:
[MENTION=6535937]louis-JYG4t[/MENTION]

Surround boost value is not percentage.

Value 16 = +1dB

So value 96 is +6 decibel boost.

The same is in graphic equalizer etc etc.
[Android Software Development] louis-JYG4t:
Oh so it's like in the mixer_path.xml? I see, thanks!
[Android Software Development] guitardedhero:
I don't know the range, though that value is on the higher side, I believe 80 is a common value for that effect element, for example.

If you really want to dive into configuring this xml manually, I suggest diving into here first. :good:

Edit*

As far as avoiding a full reboot, the following is likely sufficient:

su -c killall zygote
[Android Software Development] ShadoV90:
Hmm interesting. After type su -c killall zygote and soft restart my phone got half second hiccups when i play songs.

Hiccups repeats every ~20-30 seconds. Weird... But it's LG. Nothing will surprise me with this phone
[Android Software Development] gokart2:
No clue.
[Android Software Development] ramrastus:
[MENTION=4445176]guitardedhero[/MENTION] bro i can't flash DA 0.723 zip..

Now I'm stick with DA 0.64
[Android Software Development] Jbb3393:
https://xdaforums.com/showthread.php?p=81507183
[Android Software Development] guitardedhero:
I'm sorry, at this time installation is limited to Magisk Manager in order to ensure the mounting and writing operations are successful and the installation is consistent and predictable.

Once that happens, the installation will be open to all other avenues.

This port requires a very minor and minimal "system installation" - if you will, so this isn't a cookie-cutter mod, zip, flashing. There are things necessary for this port to work that I have not seen anywhere else nor anyone do. So I am having to essentially recreate the necessary environment for the port to function on a variety of different devices, roms, Android versions, and partition/filesystem layouts.

I predicted to many on Telegram that this port would be compatible with many, many devices/setups and would most handily surpasses the Oreo Dolby Atmos port - compatibility-wise, before I even had my first tester. I'm sure those familiar with this thread from day one will agree that this is already a fact after only a week.

Porting the components is one thing, but manipulating those components to blend into a functioning port on the variety of devices/firmware this site sees each day is entirely another thing - this is the real work and effort now lol.

I'm just happy you have something that provides what you want from it. The objective is to provide a single zip that allows as many as possible to get your results with that zip. Unfortunately, the only real control and predictability available to me is to limit installations to Magisk Manager, but this is only temporary.
[Android Software Development] avaie:
Attached is a Magisk log. Sound from music players is too low (barely process). System sounds process.
[Android Software Development] Geetesh Sonwani:
It worked on poco F1 evo X A10 rom! Though a more deep testing is needed for bugs but for now it seems to be working well
[Android Software Development] Ceejay343:
Just confirming its working here too. I had Dolby Digital for pie on here (Xiaomi Redmi Note 7 with AOSiP Quiche Android 10) together with Viper4Android. Removed Everything, flashed 0.723 went right through with no errors. Dolby Atmos App starts and works.

Reinstalling Magisk module Viper4Android Legacy first didnt work, but after patching with Audio Compatibility Module 2.5 it did.

Happy times!

Lots of stuff I tried failed to work before i put Selinux on permissive. This might be a tip for people who cant get it going.

Thanks for coming back guitardedHERO!!! I had to walk around with 2 phones for a while because my old redmi note 2 still had your axon port on it and my new phone didnt! (no joke!) Thanks man you sure as heck made my day and then some!

Edit: I get consistently that after patching V4A with Audio Compatibility Patch the Dolby Atmos app will not open. This i can expect since you wanted a clean system to begin with. Atmos processing still works, as does Viper4Android. If you need a log let me know.
[Android Software Development] anttaz:
Working on OP3T OOS 9.0.6 Pie with no issues.

Shows in app tray but not in Magisk Manager. I'm on canary channel.

Thank you
[Android Software Development] avaie:
I cannot seem to figure it out. It works but it is barely noticeable. On the contrary, it processes properly system-wide. Only music playback.
[Android Software Development] guitardedhero:
Delete
[Android Software Development] MitchiePitchie:
On HadesRom Pie 1.5

Installation failed in magisk 726

But axon .68 Pie was installed successfully. Will see if it worked
[Android Software Development] MitchiePitchie:
On a5 2017 HadesRom Pie 1.5

Installation failed in magisk 726

But axon .68 Pie was installed successfully. Will see if it worked
[Android Software Development] guitardedhero:
Tweaked installation and variables.

Removed libstagefright_omx.so (at least temporarily)
[Android Software Development] MitchiePitchie:
It says here on terminux when entering the code needed when app does not launch (which is the prob right now). Or am i doing something wrong here. Im pretty new to this. Will try 727 right now.
[Android Software Development] guitardedhero:
This is due to Termux shell opening in:

[B]/data/data/com.termux/files/home/[/B]

Targeting vendor/bin/hw/*dolby* from Termux shell targets:

[B]/data/data/com.termux/files/home/vendor/bin/hw/*dolby*[/B]

Adding an initial "/" before the target would have targeted /vendor/bin/hw/*dolby*:

su -c [B]/vendor/bin/hw/*dolby*[/B]

Make sense?
[Android Software Development] MitchiePitchie:
Testing in 727, *problem* app wont launch

Was this right? Nothing happens. You guys have a telegram?

Found out dolby tile appears to be there and working but i still cant launch the app. I feel like im doing something wrong here
[Android Software Development] guitardedhero:
The terminal command is correct as well as the desired output - no error(s) regarding missing symbols.

This command isn't necessary and is only to check for errors and to see if the app will launch after running the command in order to see if the service, perhaps, did not start upon device reboot.

The app launch failure is due to either or both of the following:
[Android Software Development] MitchiePitchie:
Cant seem to find it here and also on su -c dumpsys media.audio_flinger

Does that mean we cant get it to work on my device?