yashsingh1/xdaforums huggingface dataset:
[Android Software Development] Wolfcity:
Please use the search function. It has been asked very very often and the answer is no.

There's a WIP by [MENTION=4445176]guitardedhero[/MENTION] for Atmos on Pie.
[Android Software Development] AIP.me:
I tried on J3 2017 stock OREO Unity old and new versions and standard versions and repey6 all bootlop.

I tried to clean install and reboot the second time it failed too.

i tried dolby digital repey6 all versions from 2.5 - 6.5 Permissive kernel Dolby force close.

Now i am back to nougat dolby atmos axon 7 nougat :(

is there a solution for oreo ?

I do not understand how to viper4android so it is nice to listen to.

dolby is very simple
[Android Software Development] voske15:
Qualcomm only
[Android Software Development] guitardedhero:
This is not true.

A bootloop results from an incompatibility with the necessary /system/bin/audioserver.

Nothing in this port contains Qualcomm elements.
[Android Software Development] AIP.me:
Yep right, I have tried to delete the audioserver in twrp data / adb / module boot successful, but force close.

Sorry my english so bad.
[Android Software Development] ban.codrut:
Any news on the port release ?

I would love to test if you want...

Nokia 7 Plus running Pie here , Android 10 update release soon
[Android Software Development] milesian:
Same here. Can't hardly wait to test and see if it works on Android Auto car head units. I'm running OP5 on Pie, same as dev.
[Android Software Development] louis-JYG4t:
Great! Finally someone who succeeded!

How would you rate the odds that it will be working on MIUI 11 android 10? With Xiaomi doing a lot of things a bit different concerning software...

Also, do the atmos effects also affect android auto?

Good work man :)
[Android Software Development] Bogdans29:
How you do it?
[Android Software Development] R3demax:
Hello,great work man,any news to release ? Can't wait to test :(
[Android Software Development] guitardedhero:
The recent Magisk updates have been disruptive, unfortunately. I'm still working on returning to the level of success achieved when using Magisk 18.x.

I apologise for the delay, guys. After posting the progress report, I updated Magisk for obvious reasons and it has been quite stubborn with services, intents, broadcast receivers, etc...
[Android Software Development] zgfg:
Would it work also on Huawei with Oreo or Pie (so far AFAIK it didn't, due to the needed permissive mode)
[Android Software Development] R3demax:
Unfortunately this happens, but we are ready to wait for such work - I think I'm not the only one :) Therefore, we expect, thanks again for the work done
[Android Software Development] guitardedhero:
Those interested that meet the following two prerequisites:

Android 9 firmware

Legacy Magisk (/data/adb/magisk.img exists)

Please provide the following library renamed to your XDA handle:

/system/lib/libhidltransport.so -> guitardedhero
[Android Software Development] Skittles9823:
https://github.com/topjohnwu/Magisk/releases/download/v18.1/Magisk-v18.1.zip

Is the last stable version that has magisk.img btw ??

(I can't find any canaries back that far.)
[Android Software Development] JakunTech1010:
Can I install this on an x86_64 bit processor ?
[Android Software Development] Wolfcity:
x86 or x64 ? You can't have both as far as I know, at least it's very uncommon.

32bit or 64 bit? Or do you use an android emulator?

However, you can install it on both.
[Android Software Development] guitardedhero:
Doubtful, but the only way for me to know is to inspect the /system/lib/libhidltransport.so library.

Actually, there might be over a hundred libraries from which I could tell, but I chose libhidltransport.so for consistency, if that makes sense.

If you could provide me that library I will be able to provide an answer.

Intel 64bit device.
[Android Software Development] JakunTech1010:
OK so here it's the link for /system/lib/libhidltransport.so that you asked for: https://drive.google.com/file/d/1Gl3XaY7hARa-Hu3ZqRH7kttMN0hby6aj/view?usp=sharing

Also I have a question: Are you still working on Dolby Atmos Pie port? :)
[Android Software Development] guitardedhero:
Thank you.

Yes, and it appears your device may very well be compatible.

Can you link me to your device/rom information?
[Android Software Development] ShadoV90:
Will this mod be compatible with 24 bit (or 24 bit packed) audio processing?
[Android Software Development] guitardedhero:
Yes. Essentially, this supports the capabilities of the device. I'm listening to 32bit LDAC processing right now on my device.
[Android Software Development] ShadoV90:
Wow. That sounds awesome.

I hope LG G7 will be compatible. But for now i'm using newest magisk so i will wait.

Unfortunately rollback magisk isn't easy on my device, because i need to flash magisk boot patched file. And TWRP isn't persistent and able to decrypt data. Stubborn device.
[Android Software Development] JakunTech1010:
Yeah OK

Well it's pretty weird but what I'm using is not a rom but rather an OS: Android x86. Homepage: https://www.android-x86.org/

So yeah!
[Android Software Development] Prince153:
will it be compatible on Android 9.0 (Lineage OS 16) with Magisk 20.3 with SELinux Enforcing ?????
[Android Software Development] Adamk102:
dolby Atmos will work on Miui 11 Android 9? if your mod will be available I will gladly test it

Wysłane z mojego MI 6 przy użyciu Tapatalka
[Android Software Development] guitardedhero:
No, Magisk 20.3 is causing the service apk to fail and a solution has yet to be found.

It works great on Magisk 18.1 and below, even better than the Oreo port did in its best installation scenario.

Hit me up on Telegram [MENTION=4445176]guitardedhero[/MENTION].

:good:
[Android Software Development] Prince153:
can i use standard version with Lineage OS Root ?
[Android Software Development] guitardedhero:
Success on Magisk 20.3 finally achieved! :highfive:

Massive thanks and a shout-out to [MENTION=6806219]anvesh583[/MENTION] for testing the entire way through. :highfive:

I will need to include support for LineageOS root assuming boot scripts are supported by the root solution.
[Android Software Development] Prince153:
can you please provide the link for this latest dolby which supports magisk 20.3 [emoji7]
[Android Software Development] zgfg:
Search for XDA Magisk Canary (another thread)
[Android Software Development] yyz71:
You da man :good: Hopefully one day we can get this working with the pixel 4 ?
[Android Software Development] ShadoV90:
https://drive.google.com/file/d/1-XvXKa_lFYvq5LmCiCW1qPBf4K-niOq9/view?usp=drivesdk

This is LG G7 Europe libhidltransport.so

Will it be compatible? If yes, then i will gladly test dolby atmos with magisk 20.3
[Android Software Development] guitardedhero:
Access request sent. :good:
[Android Software Development] ShadoV90:
Access granted... I think xD
[Android Software Development] guitardedhero:
Compatible. :good:
[Android Software Development] ShadoV90:
Yay! Thank you for quick answer :)

And when right time will come, i will gladly test Atmos :)
[Android Software Development] guitardedhero:
Okay.
[Android Software Development] Bogdans29:
Hey i installed and shows app but can't launch it..

Im using Los16 kernel32bit Magisk 20.4

Here is some logs if helps..
[Android Software Development] guitardedhero:
This is almost always due to the effect configuration not being found. Sometimes, it's hit or miss right now, unfortunately. Flashing again seems to resolve this quite often, though. This will be corrected, however.

You can confirm the absence of the effect configuration by inspecting the dumpsys output of audioflinger for the presence of Dolby and its necessary effect-chain.

In terminal:

su -c dumpsys media.audio_flinger

Also, check version number in the name of the zip. The attached zip has evolved a few times.
[Android Software Development] NE0HP:
Is it worth testing on 10? Little curious!!!!
[Android Software Development] Skittles9823:
It won't work in Q
[Android Software Development] guitardedhero:
Forcing an installation will require changing the value of the following build property to 28.

ro.build.version.sdk=

I must insist some form of escape route is in place before proceeding with such a maneuver and suggest reverting the build property value in the event that no device restoration is necessary.

I doubt that the compatibility check will be satisfied and there's no way to circumvent this compatibility check without altering customize.sh inside the zip.

I cannot recommend doing this, of course.
[Android Software Development] Bogdans29:
Tryed to install again its same zip version is 0.63

and here is what i get from that code line
[Android Software Development] guitardedhero:
And the app fails to launch?
[Android Software Development] Bogdans29:
yes (to be clear?) app fails to launch.. just this time won't let me play any video on yt

every video with same error that i tryed.. Error is displayed like some of youtube line format..

So i just uninstalled it..And yt again works
[Android Software Development] ShadoV90:
Oops, LG G7 can't boot after flash.

It booted without Magisk enabled. (swapped boot.img to stock).

I can't provide any logs for now, because adb don't recognize any device during that boot, of if there is any method to provide logs then tell me pls :)
[Android Software Development] Bogdans29:
take logs from Custom Recovery also they should support ADB..
[Android Software Development] ShadoV90:
For now i don't know any viable option to have TWRP and have stock system at once.

As one thread in LG G7 forum says:

"Warning: This TWRP Recovery is only useful for installing custom ROMs.

Currently there's no way to use this recovery on stock in any meaningful way without future addons

(Data partition cannot be read because of LG default encryption)

You cannot install or backup anything while you have LG Encryption enabled. "
[Android Software Development] Bogdans29:
to unlock bootloader i think you must to pay to Huawei for the key...
[Android Software Development] Skittles9823:
It's an LG phone, not Huawei.
[Android Software Development] ShadoV90:
My bootloader is unlocked.

Problem isn't with bootloader.

Problem is with twrp and LG data encryption.

I can flash modules through magisk, but if something went wrong i can't boot system. Only chance to boot is factory reset. But after that i'm unable to provide any logs, because i don't have any.

Some devices are able to create logs through adb during boot, but not mine. Adb don't recognize any device during boot of my LG G7.
[Android Software Development] mrrocketdog:
dont know if this would help or if i'm missing the entire boat [emoji16] but chainfire made an app called "live boot" that shows logs during boot. have to have either superSU or magisk.

https://www.google.com/amp/s/xdaforums.com/android/apps-games/liveboot-t2976189/amp/

can read about it here to see if it would help out. good luck :)

i337M powered by audit13
[Android Software Development] guitardedhero:
I neglected to mention this, but Magisk 20.3 or 20.4 are the recommended versions. Lower versions above 19 may leave you looking bald like me lol. :D

Took out everything that may cause unusual behavior outside of the mod itself.

*Edit

And added a smattering back in as more seemed to be needed in 0.64...
[Android Software Development] _BГ@ckθut:
Took out couple line to able flash on Android 10! Boot on OnePlus 6t Android 10 Dolby app open and sound work! Need test little more if there any problem! Thank you for update!
[Android Software Development] Bogdans29:
hmmm ? still same..
[Android Software Development] guitardedhero:
And another...
[Android Software Development] guitardedhero:
Were you able to pass the compatibility check or did that need to be disabled?
[Android Software Development] _BГ@ckθut:
Well umm I tryna flash this on top of narsil but Dolby force close...seem like aml can't detect Dolby or maybe haven't support yet anyway for it ? Thanks

---------- Post added at 03:38 PM ---------- Previous post was at 03:36 PM ----------

I took out the API check line in customize.sh and just flash it on magisk it just flash maybe did it wrong but it work :)
[Android Software Development] Bogdans29:
Can put zip here to test it..?
[Android Software Development] guitardedhero:
AML will not detect as a unique effect uuid is used in order to not conflict with stock/custom Dolby effects.

The objective is still to not rely on anything outside of what the zip accomplishes.

The dumpsys utility on the audioflinger service will provide output to assess whether this issue is a result of the effect not being available or if the service hasn't run in the case that the effect is loaded.

su -c dumpsys media.audio_flinger
[Android Software Development] Bogdans29:
funny i think that dolby works whan i listen video on yt but app wont launch 0.66tested to..
[Android Software Development] guitardedhero:
Yes, the effect is certainly persistent. To a point where even changing presets can require turning the app off and back on lol.
[Android Software Development] guitardedhero:
I have no problem at all with what you guys do with these zips. Have fun and consider other users if experimenting heavily. :good:
[Android Software Development] guitardedhero:
If the app fails to launch, yet the effect appears in the dumpsys output of audioflinger - do the following in terminal:

su -c /vendor/bin/hw/*dolby*

and attempt to launch the app again.
[Android Software Development] guitardedhero:
So compatibility passed, cool! :good:
[Android Software Development] _BГ@ckθut:
Apparently that version 0.64 with 6.28mb some how it show 0.65 on magisk is the only one work correctly on A10 .65 or .66 either app force close or audio won't play
[Android Software Development] Bogdans29:
This shows up
[Android Software Development] guitardedhero:
Included Android 10 to the API check. Compatibility check is still in place as it has yet to allow an incompatible installation.
[Android Software Development] _BГ@ckθut:
Here you go just test it idk if it work
[Android Software Development] guitardedhero:
What rom? It is certainly executable with at least 0700 permissions.
[Android Software Development] Bogdans29:
is LOS16 J5 2016 whan i have LOS15 and oreo version of Dolby its worked

i noticed that in terminal showed 64bit my rom/kernel is 32bit

---------- Post added at 04:06 PM ---------- Previous post was at 04:03 PM ----------

same

---------- Post added at 04:13 PM ---------- Previous post was at 04:06 PM ----------

Aboud 0700 permission a was send the message to developer of rom.. so whan he answers me i will tell you..

---------- Post added at 04:36 PM ---------- Previous post was at 04:13 PM ----------

he told me that we dont have vendor partition and 0700is supported also selinux is enforcing
[Android Software Development] _BГ@ckθut:
You mind if i post the edit zip on Oneplus 6T forums? Ill give a property credit! Just wanna share the new with people over there!? If not that fine :) thanks
[Android Software Development] guitardedhero:
You feeling up to the task of providing support and troubleshooting issues?

I don't mind. :good:
[Android Software Development] _BГ@ckθut:
Absolutely! Just trying my best lol
[Android Software Development] Bogdans29:
So is there any solution.. I used this Dolby oreo version with Oreo rom and worked..??
[Android Software Development] guitardedhero:
The first obvious question that should be asked is, "Is your device 64-bit?"

If so, I would try a different rom.
[Android Software Development] Bogdans29:
no its 32bit .. but im don't get it how its worked on Oreo32bit rom with your oreo Dolby version...

im using busybox too
[Android Software Development] guitardedhero:
/vendor/bin/hw/vendor.dolby hardware.dms@1.0-service

calls:

/vendor/lib64/vendor.dolby.hardware.dms@1.0.so

This is the reason this port will fail on 32-bit devices.

Once we get something more stable and predictable I will source some 32-bit Pie/10 Atmos systems and try to get you 32-bit guys accommodated, too. :good:
[Android Software Development] Bogdans29:
Thanks a lot for your support .. For my personal reason i dont pay with credit card but if you take donations by phone sms i will love to contribute..
[Android Software Development] Logan:
Do you need tester for samsung oneui? Or any specific files are needed i tried oreos version in previous Samsung experience but didnt get a result
[Android Software Development] ShadoV90:
Guys, i flashed via magisk DolbyAtmos-axon9-A10-0.64.zip

And device successfully booted up. In dumpsys effect is loaded, but app doesn't open.

I don't have access to computer right now, but i take full logcat.

I sent it as .zip because file size was 1,5 MB

Wait. I will try to flash 0.67... I didn't see this version was added earlier by GH

Ok. Flashed, device booted, but behavior is the same (almost, because i get "can't find service: media.audio_flinger.)

Took new logcat.
[Android Software Development] laugeek57:
DolbyAtmos-axon9-A10-0.64.zip

Thanks Bro tested on N5x Pixel Experience Rom Q10...

Flash with magisk v20.1 works fine :D
[Android Software Development] guitardedhero:
Please provide the following file:

/vendor/etc/vintf/manifest.xml
[Android Software Development] guitardedhero:
In terminal:

su -c service list

If you can provide the output, we can then examine it. :good:
[Android Software Development] guitardedhero:
Added an installation restriction for 32-bit devices and added a 3 second delay to service execution each device boot.
[Android Software Development] ShadoV90:
Ok. Here's files you wanted guitardedhero :)
[Android Software Development] guitardedhero:
No native Dolby Atmos?

I will never turn down a tester. If a scenario is incompatible enough, I will ensure the installation never begins. :good:
[Android Software Development] guitardedhero:
media.audio_flinger is #195 in your list.

You might try:

su
dumpsys media.audio_flinger

Somehow, the service was never added to manifest.xml, but you can go ahead and add these to /vendor/etc/vintf/ if that is where you retrieved it for me.

A backup of your original is included as well and I encourage you to copy it there as well.

Ensure 0644 permissions for each before rebooting and you should be all set. :good:
[Android Software Development] ShadoV90:
I did what you said, rebooted (after reboot ofc i needed to type in terminal su -c killall audioserver, because without that only default files are loaded, not modded. Because f*!#*! LG Idk how they did it) and dumpsys works, but still i can't open app.

I included logcat with keyword "dolby"
[Android Software Development] Logan:
Samsung have native dolby its 2 libs and some audio effect config lines its not comparable to axon's atmos power and quality ill test when i reach home in 2 hours
[Android Software Development] guitardedhero:
Provide the following file for me:

/vendor/etc/vintf/manifest.xml

I am interested in seeing if the file is being overwritten during boot or if LG sources a different file for registering hardware services.

I prepared this testing port to not conflict with existing stock/custom Dolby effects, just like the Oreo port, for scenarios such as this so your native Dolby and Samsung effects should be as effective as they usually are.

Hopefully, SoundAlive will not need to be disabled in your audio effects configuration for Atmos to be functional.

I look forward to learning your results. :good:
[Android Software Development] ShadoV90:
Ok this is file after boot without killall audioserver but with atmos installed

Weird this is that i have sound and everything before killall audioserver, after that... Nope

Killall works with audio mods for me, but not this time.

Oh and something else... I see files in vendor are modified, but not loaded... Only default files are loaded... Weird
[Android Software Development] guitardedhero:
The manifest was not overwritten, so it appears your device is sourcing a different file for registering hardware services.

When convenient for you, please provide all manifest and matrix xml's found in the following directories:

/system/
/system/etc/vintf/
/vendor/
/vendor/etc/vintf/

If not too much trouble, zipping them up with the same directory structure in which they are found will be very helpful. :good:

I am still perplexed how killing the audioserver service would ever be necessary. I have never done that personally and have never included such an operation in a zip. What is the source of this information?
[Android Software Development] Kuljeet Singh:
[MENTION=4445176]guitardedhero[/MENTION] DolbyAtmos-axon9-A10-0.64.zip works flawlessly on OnePlus 6T running OOS A10. Thank you for the work :svetius:
[Android Software Development] ShadoV90:
Here are all xml i found through search option. Every file corresponding with it's original location.
[Android Software Development] Bravin Joshua:
[MENTION=4445176]guitardedhero[/MENTION] beautiful work you have right here working on pixel experience pie plus on zuk z2 plus ?
[Android Software Development] guitardedhero:
Thank you very much.

Let's try this one file at a time starting with the likeliest, at least in my opinion lol.

Attached below is a zip containing one patched xml along with a backup of the original in the correct directory, /system in this case.

Place both files in /system with 0644 permissions before rebooting.

Check logcat for the Dolby service registering successfully or not found in manifest. :good:
[Android Software Development] gokart2:
Was going to send the below via pm, but your mailbox is full. Then seen this thread and got super excited. I'm down for being the LOS 16 tester. Below is what I've tried and where I'm at currently. I assume reflash arise Dolby remover, then flash the test you provided? Then audio patchy-ma-thing via magisk? Keeping the below just in case it's useful...

*"What's going on dude? Hope all is well.

It's been a little while since I've played with audio mods, finally got ARISE+Magnum+Opus+20180105+Stock+Edition working on my device running LOS 16. Typically I'm rocking stock ROM and have gotten Dolby going myself. LOS seems to be a different animal mod-wise.

Was wondering if you're still in the game and could POINT me in the right direction at this point. If not or not interested, busy, etc....I totally understand.

Attached are app specific logcats of As.apk and AsUI.apk from the already listed ARISE zip, although I don't remember which is what log....:eek:

Basically it loads the Dolby splash, the FC's without any prompt. Only other EQ I've gotten farther is the Sauron guy's "DTS EQ's". Those load, but show an error prompt/toast at every option toggle.

From what I see it looks like I need to decompile the APK and make a couple....java code changes? I prefer Dolby as my EQ, IMO has always been the best. But JamesDSP looks as the only working option I've found so far.

Again, any info/pointers are much appreciated!

https://drive.google.com/file/d/1-KuoC-SJWTKmmg9-i-Fm27x07KkceCG2/view?usp=drivesdk"*
[Android Software Development] guitardedhero:
Hey, man!

Flashing the single zip for a functional Pie Dolby Atmos system along with any other existing effects/mods is the objective so nothing else besides simply flashing the zip is necessary, hopefully lol.

If anyone finds they require anything additional to achieve success, please inform me so that such an additional action or step is eliminated. :good:

Edit*

By the way, mailbox has been trimmed so new messages should now arrive. :good:
[Android Software Development] ShadoV90:
I am getting Cannot find entry vendor.dolby.hardware.dms@1.0::IDms/default in either framework or device manifest.

and

Connect to Dolby Service failed.

More in attachment :(
[Android Software Development] Bogdans29:
tell me a phone name you trying to install.
[Android Software Development] guitardedhero:
Round 2