yashsingh1/xdaforums huggingface dataset:
[Android Software Development] gokart2:
I removed the arise Atmos via the arise_customize.prop. Rebooted. Then booted to rec.

Flashed the OnePlus zip a few back. Went to the garage, rebooted. Definitely sounds better.

Since the app has no UI, pressing does nothing. I assume the app is only being used for preset sounds and no UI? Regardless, longtime audiophile, sounds better than before.

Best part of the whole thing....on the installer UI......:good:.....

:laugh::good:

*I do have the magnum opus base, and DAP Qualcomm effect previously flashed still.
[Android Software Development] ShadoV90:
After reboot i get this

I don't know. I remember when i was on oreo, everything was normal.

I checked dumpsys audio flinger aaand... Dolby audio effect is loaded, but logcat shows that, and ofc app can't launch...

But i see one positive. Device is functioning normally and don't do any derpfest anymore.

EDIT: I appreciate your work guitardedhero. You are great dude. You don't know it but thanks to you i was able to learn anything i know about how android audio works...

Btw. Trick with killall audioserver i discovered when i saw much earlier icesound mod. Their script had option to do killall audioserver in order to reload all audioeffects. I had remember that. When i installed magisk module and any audio mod wasnt able to load, i tried use that, because why not. And voila, it worked :D but this challenge is... More... Challenging? :D
[Android Software Development] guitardedhero:
A Dolby Atmos icon should be in your app launcher and will give you total control of the adjustable parameters available.

Additionally, there is an available Quick Settings tile named Dolby Atmos that can be added via the Quick Settings Edit feature. Tapping this tile toggles Dolby Atmos On and Off while long-pressing the tile launches the app.

I have also found the Dolby Atmos effect to be so persistent that adjustments or switching presets will oftentimes require toggling Dolby Atmos Off and On either via the app's power button or the Quick Settings tile. Changes in sound can then be noticed ONLY when making an adjustment, as the previous settings and profile are persistent.

I hope that wasn't too confusing lol.

Let me know what you find. :good:

Thank you for the kind words, man. It certainly motivates me to keep doing everything the same way.

While preparing this port's installation mechanics for the smoothest experience for you guys I was blasted with everything from "It won't work", "You'll have to patch ramdisk", "compatibility impossible", "You copied my/his work", "No one cares about Dolby except for you (and one other person)", and "I gave you a zip" - all this was after the port was already functioning lol. But I had only a single tester for Pie at that point and my news of my first successful test other than myself was not met with the positivity I had expected from a group of "friends/devs".

I took over a year off from any and all Android tinkering whatsoever and didn't return to TG or XDA until after I had produced a functional Android Pie Dolby Atmos port, which took a month or less.

The point is, is that sometimes being your only cheerleader is enough. It's with confidence and determination that goals are achieved.

Interesting detail regarding killing audioserver. I'll certainly experiment to observe the behavior.

Unfortunately, I didn't fully understand your current situation with the port lol. Is the service finally registered? Does the Dolby effect-chain exist in audioflinger's dumpsys output?

Edit*

I didn't see your attached pics. I will prepare something for you to try next here in a bit. I gotta drive home first - preparing this entire post before taking off has me already behind lol. :good:
[Android Software Development] ShadoV90:
There was one entry which i didn't see. After (another) reboot i took fresh logcat and besides that what you saw in picture, i got one error with this message

"01-16 00:58:12.871 639 639 E SELinux : avc: denied { find } for interface=vendor.dolby.hardware.dms::IDms sid=u:r:untrusted_app:s0:c12,c257,c512,c768 pid=3604 scontext=u:r:untrusted_app:s0:c12,c257,c512,c768 tcontext=u:object_r:default_android_hwservice:s0 tclass=hwservice_manager permissive=1"

And take your time. Don't rush. I don't demand immediate help. My device is very complicated from development side and i know that :) LG did very well (unfortunately for me) in order to protect their device from modifications :D

On the other side it's challenging, and challenges are good for skill raising and polishing.

I noticed something. After reboot dolby effect is loaded in dumpsys media audio flinger, but now killing audioserver destroys audio completely. Kinda weird behavior. :P
[Android Software Development] guitardedhero:
[MENTION=8116982]ShadoV90[/MENTION]

Round 2.

Reminder guys, this is a unique fileset prepared for a single user instance. Usage of these files can only do nothing at all in the best possible scenario. Unless you have the very same device... with the very same firmware... and trying to get this port to work... :good:
[Android Software Development] ShadoV90:
After reboot it's still the same. Not registered.

LG 2:0 Humans :D

Is there a possibility to check which manifest or matrix files are used when device boot up? Just out of curiosity :)
[Android Software Development] guitardedhero:
I imagine there is.
[Android Software Development] mrrocketdog:
apologies if i misunderstand , but like a boot log?

i337M powered by audit13
[Android Software Development] lkp171:
I just tried the zip for a10 on my oneplus 6 on beta4 and it works?thanks dev

But i noticed that aml crashes it. Maybe you can look into it when the time is right
[Android Software Development] ShadoV90:
Thank you mrrocketdog, you gave me an idea.

I know that i said earlier that i can't do logcat during boot, but i made a mistake.

I tried some time ago but nothing wasn't work...

I learned 5 minutes ago how to do it and wow... i have a text file with full logcat from boot.

Maybe that will help?

There are LOTS of informations, but i believe some of them will be valuable.
[Android Software Development] guitardedhero:
:good:

Try without AML. :good:

In the meantime here is every file you provided me in patched form lol. :good:
[Android Software Development] guitardedhero:
You've been placing these in the module folder, haven't you?
[Android Software Development] lkp171:
Yeah doing that, was just saying maybe you'll add support sometimes:good:
[Android Software Development] ShadoV90:
Yes. I will try to replace them directly without module but there are two scenarios:

1) system will not allow me to do that

2) if something went wrong then bootloop will force me to reflash whole system xD

But i like some risk so i will do it... Wish me luck

Sorry i thought that placing it in module folder will do the job, and with fail factory reset will fix bootloop.
[Android Software Development] guitardedhero:
Requiring you guys to install something extra for a zip of mine to work is unacceptable to me and can be accommodated in this zip.

The configuring of effects is still evolving and will be aggressive.
[Android Software Development] guitardedhero:
This port will not function without the Dolby service existing directly in /vendor/etc/vintf/manifest.xml with Magisk's current state.

This is the only reason a backup is made for this file.
[Android Software Development] mrrocketdog:
yeah , good for that. i was going to say chainfire makes an app called "live boot" that shows logs .......... while booting. lol

i337M powered by audit13
[Android Software Development] ShadoV90:
Mrrocketdog yep, it shows but not write :D

I replaced files [MENTION=4445176]guitardedhero[/MENTION] and it's registered.

But i am getting errors in logcat and app don't launch.

Anyway, we're closer and closer. :)
[Android Software Development] Skittles9823:
It does actually have an option to save logs in it FYI.
[Android Software Development] ShadoV90:
Oh. I didn't know that.
[Android Software Development] scaschera:
Hi ,

installed zip a10 from top of page 368. But with bluetooth earpiece the sound Out from loudspeaker..

Can you help me please, i'm on Pixel experience pie on A5 2017.

Thx
[Android Software Development] immarcel:
hi, anyone managed to get the module from page 368 to work on oxygen os 10? im on magisk 20.3 but can't get it to work
[Android Software Development] Bogdans29:
its not point to download module 368

point is that you need to download lastest module and provide logs.. i think...?
[Android Software Development] immarcel:
oh, thank you! the amount of posts got me a little bit confused, thanks for enlightening me:)
[Android Software Development] gokart2:
Not at all. So...I found an odd one last night. I went to edit quick settings to put the Dolby button in range to try and see if I could at least cycle it on/off that way since GUI isn't working. Oh boy, that little tile.

Tapped it to have it fly to the active tile area. Soon as it took off flying.... It threw a prompt of shutting down similar to when you run out of battery. Batt showed ~40%. So was confused. It didn't shut down though, went to recovery? Rebooted, boots up for ~5 sec, then repeats the shutdown to recovery.

This morning I started over and only had this Dolby flashed. No problems at all until I tried the tile again. Same thing. Was able to remove the time within 5 sec on the reboot and has been fin since.

I'll try to get a boot log later after the job. Anything else you want to see? I know a lot people are throwing logs at ya. I'll sift through and see what I can find.

Edit: Also noticed this app doesn't show as an EQ option in say...Spotify EQ in settings. I flashed old Atmos and Dolby Digital, both show as an available EQ option, but FC upon selecting. This doesn't show period.
[Android Software Development] ShadoV90:
[MENTION=4445176]guitardedhero[/MENTION] I MADE IT!

I removed libaudioflinger.so from module and voila :victory:

I don'tknow if it's fully working because im in my job right now, and can't check properly, but after work i will.
[Android Software Development] Bogdans29:
if worked pls provide zip to try out..
[Android Software Development] gokart2:
Various logs. If interested.

:eek:
[Android Software Development] Bogdans29:
What i think that myb its not problem in liber.. or patces.. It can be about apk it self..

I think that on kost davices app won't launch but effects still work.. myb it have some conflicts with lib.. but myb can it be problem in apk itself?
[Android Software Development] gokart2:
It could very well be code in the app not chiving with your phone. Seen it before and it sucks trying to fix.
[Android Software Development] lkp171:
Does your Bluetooth still work properly?
[Android Software Development] Qwerty182:
Is this work on permissive selinux status?
[Android Software Development] gokart2:
Looks to require Permissive.
[Android Software Development] Bogdans29:
ohhh my selinux status is enforcing
[Android Software Development] ShadoV90:
Post.fs.sh in dolby module sets permissive selinux.

So it's permissive at system start.
[Android Software Development] Qwerty182:
It's not work on my phone with permissive selinux status on android 10. Any solution?
[Android Software Development] gokart2:
I was already permissive.

It work on phone if permissive only. Make phone permissive only solution.
[Android Software Development] Qwerty182:
Which module u used?
[Android Software Development] louis-JYG4t:
Hell yeah! It's woking on Mi8 Miui 11 android 10 (xiaomi.eu 11.0.6)!

Flashing version 0.67 from #367 resulted in failing with error "incompatible". Flasing the 0.64 posted by _Bl@ckOut (sory, can't type the special characters) from #368 however went through.

First notices and experiences:

1) There's literally NO "quiet" anymore for my loudspeaker ? minimum volume is already quite loud; haven't tested out max volume yet as I'm in a hotelroom and respect my neighbours :angel:

2) The new atmos version is letting you have less control compared to the earlier version (no sliders for "volume leveler", "dialogue enhancer",...). Are these features that will be added later on? Or is it just missing for me in the app? I've seen images on google with what seems to be the same dolby atmos design where these sliders are present.

3) The equalizer bars aren't moving with the music anymore. Is it suposed to be like this in this version?

4) At the moment the configuration I like the most is activating Mi sound enhancer because that just sound SO MUCH better (I feel like they decrease music quality on purpose when you disable it...) + Xiaomi equalizer flat + Dolby Atmos on "dynamic" mode for the wider soundstage and more detail + bass turned up just a little bit in Dolby Atmos equalizer (I guess my earphones lack that).

[MENTION=4445176]guitardedhero[/MENTION] is the soundprocessing also something you're still working on (more detail and surround)? Or is this something you will leave as it is now? I feel like the surround effect was stronger in the Oreo version.

Tomorrow I'll test if Dolby also affects android auto :)

Thank's for your work guitaredhero!
[Android Software Development] ShadoV90:
Everything you can manually set in /vendor/etc/dolby/dax-default.xml

This is configuration file for dolby

[MENTION=4445176]guitardedhero[/MENTION] i added additionally killall audioserver to post-fs-data.sh after setting selinux to permissive.

It raised compatibility with my modded mixer_paths_tavil.xml, audio_output_policy.xml and audio_policy_configuration.xml

Normally my device is processing 16 bit deep buffer but with higher analog audio gain (in phone i have ESS Sabre 9218p DAC) i have hisses, so i forced 24 bit audio and hisses gone. Without killall audioserver dolby is working but device was at 16 bit processing (standard).

With killall audioserver doing in terminal i have 24 bit processing, but dolby effect is gone idk why. When i set that command in post-fs-data.sh in that place, everything is working perfectly.
[Android Software Development] Qwerty182:
My selinux status is permissive, but i can't open the app. Help me please
[Android Software Development] NE0HP:
Removed API check compatibility in customize.sh in this version and flashed it on my device (Mi A2) running custom rom AOSiP 10 and it works perfectly fine alongside V4A. Thank you.
[Android Software Development] gyuuuu:
how method remove api check?
[Android Software Development] guitardedhero:
I apologise for just now getting back to you guys. I finally updated my firmware and Magisk version so that I can flash the port for the first time to hopefully not waste anymore of your time than I already have lol.

Still not perfect, but something for those to try that have yet to achieve a functional port to test.

This build is one I prepared after starting fresh while avoiding all possible distractions such as bug reports from others - this is simply what was needed for my scenario.

This zip will only execute in Magisk Manager, so don't waste a trip to recovery.

The installation screen includes a Save Log disk icon at the upper right just above the console. Tap this icon each and every time a module installation finishes so that these logs can later be retrieved from /sdcard/Download to probe the cause of an issue.

Also, auditing procedures described in the OP are still valid and still helpful. Soon, I will prepare a more comprehensive list of further procedures that were found to be helpful while porting this particular system, but I will include this one now:

Failure of the Dolby Atmos app to launch is nearly always the result of one or more of the following three scenarios:
[Android Software Development] gyuuuu:
The installation is complete, but the app is forced close

Also no sound from the device

Youtube won't play
[Android Software Development] guitardedhero:
Delete the media_codecs xml from /data/adb/modules/dolbyatmos/system/vendor/etc/ and reboot to test for corrected behavior.

This xml is a copy of your device xml with the Dolby ac3 media codec defined. It's possible an error in handling your file has occured or a failure to load the ac3 codec. Deleting this file from the module restores your media codecs xml which should resolve your issues.
[Android Software Development] guitardedhero:
Indeed, tuning is currently taking place at this time. :good:

If you want to experiment on your own, /data/adb/modules/dolbyatmos/system/vendor/etc/dolby/dax_default.xml is the tuning configuration. It's quite a bit of text, but if just stick with one line at a time it is pretty straightforward.
[Android Software Development] gyuuuu:
Media codec XML does not exist

audio_effects.xml does exist

Deleting audio_effects.xml still doesn't work
[Android Software Development] guitardedhero:
Delete /data/adb/modules/dolbyatmos/system/lib(64)/libstagefright_omx.so and reboot. :good:
[Android Software Development] gyuuuu:
libstagefright_omx.so does not exist

libstagefrightdobly.so exist

lib lib (64) Delete both?
[Android Software Development] guitardedhero:
Please zip /data/adb/modules/dolbyatmos and share with me so that I can assess your current module.
[Android Software Development] gyuuuu:
here
[Android Software Development] guitardedhero:
I would delete the /data/adb/modules/dolbyatmos folder, reboot, test video playback, and try again.

Deleting audio_effects.xml from within the module will guarantee the port to fail, of which, all side-effects are still not known.
[Android Software Development] gyuuuu:
It works fine after deleting
[Android Software Development] guitardedhero:
I forgot to mention that [MENTION=6841137]Logan[/MENTION] and I worked on maintaining Samsung's SoundAlive and all its native effects with this port yesterday and we're excited to inform all Samsung users that any zip beginning with version 0.7 from today will ensure that your Samsung device's native audio effects, including its very own Dolby Atmos implementation, will be in full working order in tandem with this port. :highfive:
[Android Software Development] guitardedhero:
/dolbyatmos/system/lib/libstagefright_omx.so

/dolbyatmos/system/lib64/libstagefright_omx.so
[Android Software Development] gyuuuu:
Sound is normal but the app still won't run

I am using Pixel3 stock
[Android Software Development] gyuuuu:
The absence of the DolbyManagerService hwservice registration or its failure to execute.

This is almost always a registration issue as executing the service has not been an issue but is certainly a possibility and one that would prevent the app from launching. Without being registered, a hardware service will simply be disallowed from executing if unregistered.

Registration for the DolbyManagerService takes place in /vendor/etc/vintf/manifest.xml and will be the very first service defined if the installation was successful in adding the element to the manifest.

Logcat can also be used to target specific errors for the service using a variety of different filters such as "dolby", "dms", daxService", and more.

Can you tell me more about the above syntax? I can not speak English very well
[Android Software Development] Qwerty182:
Sir, i have an issue the apps cannot be open
[Android Software Development] guitardedhero:
Audio effects configuration failed to copy to the module.

Does /vendor/etc/audio_effects.xml or similar exist?
[Android Software Development] Qwerty182:
Sorry sir, this is zip without delete any files
[Android Software Development] gyuuuu:
Dolby stuff is normally present in my audio_effects.xml

but can't open app
[Android Software Development] guitardedhero:
I understand.

The module installation seeks audio effects configurations from /vendor/etc/ on the device to copy over to the module and then configure the atmos effect in its own copy.

Let's find the audio effects configuration files your device provides in /vendor/etc/, typically audio_effects.xml and/or audio_effects.conf, but variations of file names do exist for different vendors.

What device and rom?

This port has been prepared to not conflict with any single effect by inserting a unique effect UUID and library name.

The library name and the effect name are both configured as "dolbyatmos", so look for "dolbyatmos" instead of "dap" or "ds".
[Android Software Development] Qwerty182:
I used redmi note 4, rom havoc os 3.0 sir
[Android Software Development] gyuuuu:
my device provides in /vendor/etc/
[Android Software Development] Qwerty182:
This is the file sir
[Android Software Development] guitardedhero:
Do you guys know if HavocOS uses uniquely named audio effects configurations?

This includes my custom configuration so let us now perform a dumpsys on the audioflinger service to see what the final assortment of available effects is:

su -c dumpsys media.audii_flinger
[Android Software Development] Qwerty182:
This is the file sir, what should i do?
[Android Software Development] yyz71:
I get it installed with success. But the app doesn't open. Do you need anything from me? Pixel 4 stock
[Android Software Development] guitardedhero:
Was a previous zip installation working for you?

Let's certainly start with dumpsys auditing and then check /vendor/etc/vintf/manifest.xml for the service registration which will be at the top if patched.
[Android Software Development] yyz71:
No it wasn't working for me. 6.4 installs but didn't work.
[Android Software Development] guitardedhero:
The good news is we're not going backwards... yet...

Performing some auditing on the installation is the only way to move forward from here.
[Android Software Development] yyz71:
Just installed 71 gonna reboot now
[Android Software Development] ShadoV90:
I uninstalled 0.67 module, and installed newest.

It works. [MENTION=4445176]guitardedhero[/MENTION], i have patched registers in my backup too, so they are ready to use in case of... Something :D

Atmos is working great. Thank you very much for help.

But i have one question just out of curiosity. Do you have any idea why modded audio_output_policy.conf and audio/audio_policy_configuration.xml aren't applied from start in LG G7? Killall audioserver is a workaround to work, but i want understand.

When i was on oreo i didn't must to do that. After upgrade to pie it is like it is.
[Android Software Development] Qwerty182:
Sir? [MENTION=4445176]guitardedhero[/MENTION]
[Android Software Development] ShadoV90:
[MENTION=9040504]Qwerty182[/MENTION]

I think guitardedhero wanted output from

su -c dumpsys media.audio_flinger

To check if there is audio effect loaded i think.
[Android Software Development] Skittles9823:
Pixel 4 only has Android Q btw. So same situation as me. Honestly I'm surprised the pixel 4 passed the compatibility test if they didn't remove that part of the installer.
[Android Software Development] Qwerty182:
(deleted)
[Android Software Development] Qwerty182:
This is the true file from terminal emulator sir
[Android Software Development] ShadoV90:
[MENTION=9040504]Qwerty182[/MENTION]

I see that Dolby and JamesDSP isn't loaded.

In order to get James to work, you must get libstdc++.so workaround.

I needed paste it to system/lib and vendor/lib in jamesdsp module and jamesdsp started working.

Remember to set permissions to rw-r--r-- or 0644
[Android Software Development] Adamk102:
which version works on Miui 11?

Wysłane z mojego MI 6 przy użyciu Tapatalka
[Android Software Development] Ceejay343:
Deleted
[Android Software Development] guitardedhero:
Unfortunately, I do not. LG is a beast of firmware when trying to port anything. I hate to recommend custom firmware, but that is the only answer I can give you at this moment that will give you a chance to get further than where you are.

But compatibility with your phone/firmware is still a priority as are all others, so this will continue to be an objective.

The compatibility check merely checks the rom's firmware hardware libraries for compatibility with the port's libraries and service.

Other components to ensure a functional Atmos system still rely on the installation to target necessary components in the firmware for copying and patching and direct patching.
[Android Software Development] Soumy1234:
I see the latest Dolby is compatible with Samsung's Dolby, but will it work on the OnePlus 7 Pro or no?