yashsingh1/xdaforums huggingface dataset:
[Android Software Development] ShadoV90:
I have that error too in logcat but i think it's ok because script sets selinux to permissive.

Even with that atmos is working like a charm on my device.
[Android Software Development] Skittles9823:
If you have more than just Atmos and one other Unity/MMT-Ex audio mods you'd flash everything, then AML, then reboot and flash Lennon's zips. You may need to manually remove audio effects from the Atmos module dir though.

Although a new AML update should be coming out or it might already be out that uses diff to see the differences in modules audio effects files so if that's already out then you could just flash aml last.
[Android Software Development] Mervingio:
What is this zip?

---------- Post added at 02:44 AM ---------- Previous post was at 02:31 AM ----------

So guys what I need to flash to work on A10 OP6T???
[Android Software Development] Skittles9823:
Any zips made by [MENTION=4445176]guitardedhero[/MENTION]
[Android Software Development] konsolite:
Thanks a lot. I turn off Volume Leveler in dax-default.xml, because it was too loud on my OnePlus 6 at minimum level. If I have much time I will try to compile and use another Dolby with libs and xml.

This ports works for me better than Oreo ports. In my opinion the best was classic Nougat Dolby. It was clear, solid and stable.
[Android Software Development] guitardedhero:
Script changes.
[Android Software Development] anttaz:
What is the Viper Atmos Redux ?
[Android Software Development] guitardedhero:
An update to the ViPER|Atmos™ series from 2016.
[Android Software Development] ckanth12:
I still cant get the app running.

It still force closes.

Crash log : "msg: java.lang.RuntimeException: DolbyAudioEffect: set/get parameter error

stacktrace: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.dolby.atmos/com.dolby.atmos.MainActivity}: java.lang.RuntimeException: DolbyAudioEffect: set/get parameter error	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3271)"

What do I do?
[Android Software Development] guitardedhero:
What do I do now?
[Android Software Development] anttaz:
The Viper FX is self explanatory. Will this work withe redux as well as Dolby Atmos or not?
[Android Software Development] NE0HP:
Nice and Improved.
[Android Software Development] ramrastus:
Da working great & now I have two viper what I am do now?
[Android Software Development] anttaz:
Atmos working but viper will not install driver at all many attempts and reboots done. OP3T OOS 9.0.6 Pie
[Android Software Development] Skyllery:
Flashed latest Atmos (0.8x) and previous (0.7x) on mi9tpro with EvoX Android 10

The app start the sound is processing fine on audio but notification sound is cracking.

Tried notification helper remover without any change with and without aml

Tried to delete lib in the same module no change

Libs are present in vendor lib and lib64

Edit : authorizations in Dolby app is grey
[Android Software Development] Abdul hadi202:
Will it work on Floyd rom for S6 Edge running android pie 9.0????
[Android Software Development] anttaz:
0.8.1 just keeps FC on OOS 9.0 .6 Pie OP3T rolling back to previous version
[Android Software Development] guitardedhero:
Inspect /vendor/etc/vintf/manifest.xml for the Dolby service registration as the first entry.

Same or different vipers??

Try installing the v4a zip again. The Atmos module is likely symlinking the audio effects configuration to /vendor/etc/ and doesn't have the v4a entries.

Right now, it is likely that installing both zips will require the first zip to be flashed after the second zip:

Dolby, v4a, Dolby - or - v4a, Dolby, v4a

I'm still experimenting with the effects configuration operations.

Atmos only? Have you tried various adjustments to any improvement?

The odds are in your favor.

0.83

Added the detailed Quick Settings Dolby Atmos™ tile suggested by tester, D e a d p o o l.
[Android Software Development] ckanth12:
code :

<hal format="hidl">

<name>vendor.dolby.hardware.dms</name>

<transport>hwbinder</transport>

<version>1.0</version>

<interface>

<name>IDms</name>

<instance>default</instance>

</interface>

<fqname>@1.0::IDms/default</fqname>

</hal>

The above code is present in my manifest xml file.
[Android Software Development] ramrastus:
[MENTION=4445176]guitardedhero[/MENTION] different version bro..

---------- Post added at 02:57 PM ---------- Previous post was at 02:47 PM ----------

[MENTION=4445176]guitardedhero[/MENTION] bro I really liked your v4a but I've already xdalab v4a 2.7.. Now I flashed your v4a afterthat it shows 2 v4a now what I've to do??? And no driver installation
[Android Software Development] NE0HP:
Thank you. It is getting better and better.
[Android Software Development] Mervingio:
My God it's work!!!!!! THANK YOU!!!!!!!

on Dolby Plus the EQ bars is moving but not Atmos not sure if it's ok but change music and movies and the sound change!!!!✌️

Let me Know guys
[Android Software Development] anttaz:
Dolby 0.81 and 0.83 will not open just FC on OOS 9.0.6 Pie OP3T. Even after removal of V4A and AML 3.0?

What logs or files do you require to look into?
[Android Software Development] Adamk102:
Dolby Atmos has been installed. Does not turn on. I tried to copy the file described in your post. But I don't have the vendor / etc folder anywhere. I'm doing something wrong?

Wysłane z mojego MI 6 przy użyciu Tapatalka
[Android Software Development] ramrastus:
[MENTION=4445176]guitardedhero[/MENTION]
[Android Software Development] ckanth12:
I can make version 0.64 work without crashing.

Sticking to it for now.

Can you implement the code of 0.64 that is missing in latest versions?

I think it is something related to SELinux.
[Android Software Development] exodius48:
Sound processing works on PE 10 Official. But Quick Settings tile does not appear on Quick Tile status bar.
[Android Software Development] JakunTech1010:
OK so I removed DolbyAtmos 0.7292 because I realized that Viper|Atmos Redux zip has already contained Dolby Atmos. But Viper still not work. So I removed it and only install Dolby 0.7292. Well there are some issues I still encounter:

- Dolby will stop working after I turn off Dolby. Of course I turned it back on but there were no longer any audio difference between with or without Dolby

- Sometime the audio will got disorted at some section if I turn the volume to loud. Turning Dolby off solved the issue. This issue only occur if I use my phone's speaker. Headphones did not have this issue.

Beside all of that, I hope that you (guitardedhero:o) can solve these issues and add the surround virtualizer and other buttons and support for working with Viper. THIS WILL BE THE BEST AUDIO EXPERIENCE EVER.
[Android Software Development] avaie:
This is somewhat of a unique issue and pertains to the V35 and V40 LG variant. This is not found in the V30 (even though it works phenomenal to a limited degree on the V30 - somewhat digital). Every sound but playback is processed through Dolby but music playback isn't. I have attached the dumpsys files.
[Android Software Development] Skyllery:
Yes only Atmos installed. It's an issue well knowned on mi9tpro sound is always buggy with sound mods. Atmos, Dolby Plus, Viper4Android. Sound processing work well but not notifications.

Regards
[Android Software Development] Bogdans29:
dont report without logs.. its not possible to know from here what heppens on your phone..
[Android Software Development] Skyllery:
V0.83 is working fine for notification sound on mi9tpro there's still a bit of "noise" in background don't know how to say this in English but it's way better.

Thanks for you work I'll follow futures updates.

Regards
[Android Software Development] alok932:
It wasn't but now i decided to give another try. I went back to MIUI 11 A9 and had to do clean install few times And IT WORKED :)

Mostly all functionality of app is working properly but it seems to effects stops randomly or gets killed. It's not a big deal i can manage it.

Thank you very much for such a wonderful port.
[Android Software Development] ckanth12:
Clean install rom or Dolby?

if not rom, how did you clean install dolby?
[Android Software Development] alok932:
Clean install rom. Removed all magisk module and used magisk uninstaller and then clean install rom.
[Android Software Development] ckanth12:
ohh man.

That is a lot of time and work. kudos.

Even I clean flashed evox yesterday and moved back to havoc today.

only dolby 0.64 is working now in havoc.

all other versions 0.7x and 0.8x are force closing and if dolby quick tile is enabled, device is restarting just after powering on.
[Android Software Development] Adamk102:
Ok no problemView attachment magisk_log.zip

Wysłane z mojego MI 6 przy użyciu Tapatalka
[Android Software Development] alok932:
I switched to pixel experience rom and it working properly here as well. The latest version is showing audio mode in tiles properly.
[Android Software Development] gokart2:
Been away a little bit, just caught up reading. But confused on the Viper4dolby Zip's. It seemed to me it's only for 10(Q)? Or is it supposed to be good for Pie as well?
[Android Software Development] acuicultor:
Yes, it is also for pie
[Android Software Development] EstherTakumi:
Can't seem to work for me, the Dolby keep shutting down my phone and restart straight to TWRP.
[Android Software Development] gokart2:
Thank you!
[Android Software Development] ckanth12:
It is due to dolby quicksetting tile being enabled in previous version.

I installed 0.64 and used quicksetting tile and later uninstalled 0.64 and installed 0.8x, from then dolby force closes and due to tile being enabled it goes into TWRP.

Now, you uninstall magisk using uninstaller and reinstall magisk, should be fine. Install only working version of dolby atmos and remove quicksetting tile before trying new versions, otherwise it will reboot to TWRP after 5-10 seconds of every boot.
[Android Software Development] guitardedhero:
What Magisk version?
[Android Software Development] ckanth12:
Magisk : 20.4
[Android Software Development] laugeek57:
V0.83 works fine on N5x :good:

Just remove v0.64 before... ;)
[Android Software Development] guitardedhero:
I haven't tried 20.4, but others have.

Your experience, as well as the other user's, sounds precisely like what I experienced upon updating to 20.1 or 20.2 from 18.3 - my working port suddenly became a bootloop sentence.

It took me over a month to finally realize the Magisk update borked the port and not something I did - which certainly happens lol.

You might try 20.3.

I choose to remain on stable/current Magisk and stable/current firmware to best replicate the likely users trying things out - OnePlus 5, in my case.

That's why everything blew up in my face immediately after making the announcement that I was preparing to begin testing for Android Pie, I then updated everything on my phone as I was on an old Magisk build and one firmware update behind.

In fact, oddly enough, my very first tester that bootlooped was the one that got me very excited and told him that it was likely a successful and working port installation (I spent 1.5 months boootlooping, I know...) and that booting up meant something wasn't right and it wouldn't work at all.

Soon after, a Magisk update finally allowed testers to boot up to a functional port.

Something to consider, anyway. :good:
[Android Software Development] EstherTakumi:
Im still using Magisk v20.3

My phone also had fresh clean install before I'm adding this module.

Maybe I should try the older version, will test it out later.
[Android Software Development] Bravin Joshua:
0.72 works fine with havoc q on z2 plus! Great work btw
[Android Software Development] Adamk102:
anyone run android 9 on Miui 11? please help

Wysłane z mojego MI 6 przy użyciu Tapatalka
[Android Software Development] gokart2:
V4A .15 didn't work, but .18 does! Thank you!

Although, Atmos .83 still doesn't open. And the installer is missing a critical piece..... :good:

---------- Post added at 04:52 PM ---------- Previous post was at 04:46 PM ----------

Had the same quicksetting tile issue. YOU CAN PUT THE TILE BACK TO THE UNUSED AREA WITHIN THE AMOUNT OF TIME ITS BOOTED. Then you'll be fine, won't loop anymore. If it flys to the unused area, but then bootloops again, then next reboot you'll be fine. I tested multiple times. Loop-dee-loop!
[Android Software Development] AndrzejDwo:
Hi!

I've tried to flash this Viper on my Samsung SM-G975F running HadesRom OneUi2.0 and latest magisk Canary. Installation succeed but Viper still doesn't show up in app drawer. Log attached.

Cheers
[Android Software Development] guitardedhero:
Are you freaking kidding me?!
[Android Software Development] Skyllery:
After an other check when go back at home the last version broke sound over Bluetooth on mi9tpro.

Regards
[Android Software Development] gokart2:
About the tile thing or the installer script error?:D
[Android Software Development] guitardedhero:
The tile lol. What error did you find?
[Android Software Development] AndrzejDwo:
Hi again, this time I tried my luck with DolbyAtmos-0.81. Installation succeed, Dolby app and tile showed up but the app itself still crashes. Zip attached contains Magisk installation log, Dolby crash log, terminal output from dumpsys "media.audio_flinger" command and manifest.xml from /vendor/etc/vintf.

Cheers
[Android Software Development] gokart2:
Tile things for real, just rechecked it. Still happens:laugh:. I actually got some good logs I posted some pages back. :good:
[Android Software Development] guitardedhero:
Very nice job providing the goods. :good:

Everything looks great except for the absence of the Dolby effect-chain and that certainly corresponds with the logs provided.

It looks like the SoundBooster effect-chain might be conflicting as it's the only chain anywhere.

I hate to say it, but Sammy may need a little more effort to get EVERYTHING compatible lol.

If you're able to disable it turn off the "SoundBooster" feature/effect, I would wager you find it working after a reboot. :good:
[Android Software Development] guitardedhero:
What error were you referencing earlier? I need to make sure it's fixed if it is still there.
[Android Software Development] guitardedhero:
Fixed error introduced with notification_helper disabling. Smdh
[Android Software Development] ramrastus:
DA working great.. When will you add the volume leveler switch for DA bro?
[Android Software Development] shantam3108:
Dolby 0.842 not opening. Just getting black screen.
[Android Software Development] ckanth12:
Downgrading Magisk to 20.3 solved everything.

Now working fine. Using version 0.842 without issues.

Thank you.
[Android Software Development] guitardedhero:
Porting a different system with the Volume Leveler switch will likely happen before adding it to this port will.

The function of that switch and other elements is compiled in the libraries for those Atmos systems.

The apk's in many different Atmos systems are interchangeable, but not the library base. These libraries interact deeply enough that bringing in a foreign library will very often break everything.

The difficulty porting this system isn't the apk's, it is the providing or the preparation of a sufficient "Dolby environment" for the service and libraries to give the apk its "power", if you will.

Don't worry, there will be more after this one. Currently, I think the best course of action is to learn and understand as much as I can about the many nuances of this port by the time we see version 1.0. Anything I can gain will help as the difficulty of porting varies quite a bit.

Here's what to do. :good:

:highfive:
[Android Software Development] immi:
hello [MENTION=4445176]guitardedhero[/MENTION] will there be a 32bit port?

P.S NOT asking for an eta ;)
[Android Software Development] guitardedhero:
Indeed. 32-bit will be the primary focus next. :good:
[Android Software Development] shantam3108:
Sorry for being a noob but what to do after running

Su dumpsys media.audio_flinger?

Till now only Dolby atmos 0.7292 version has worked on my op5
[Android Software Development] shantam3108:
Here is the file
[Android Software Development] AndrzejDwo:
Thx for the hint but i can't find anything regarding "SoundBooster" feature/effect anywhere. I've searched through all my apps/services but no luck... If you have any ideas, please let me know.

Cheers
[Android Software Development] aarkee:
I tried several zips. Alll the apps are crashing. I'm just a noob to this.. if its possible give me a solution.
[Android Software Development] ckanth12:
Which Magisk version are you using?

Try using stable Magisk 20.3.
[Android Software Development] Lord Sithek:
Hello everybody :) I was thrilled to see Dolby available for Android 10. I understand of course that it's still in testing phase. I flashed latest 0.842 version and I am able to open the app without a problem, but can't make it process the sound. Can I do something to make it possible? Forgive me if this was discussed before, I was searching some info, but this is lot of pages to read... The Dolby entries in manifest file are present. I'm attaching this file along with Magisk log and logcat. I'm on Xiaomi Redmi Note 4X, DerpFest 10 ROM, Magisk stable 20.3. Should I provide any other information? Thanks in advance
[Android Software Development] aarkee:
I'm already using magisk 20.3. I tried to edit manifest but upon restart its going back to default again. My device is op6 oos 10.3.0
[Android Software Development] laugeek57:
On Rom stock it would be necessary to desactivate Dolby Atmos stock ...

On OP7 with Havoc OS 3.1 Unofficial there is the option to do so ... :good:
[Android Software Development] JakunTech1010:
OK so I'm switched to LineageOS 17 on my A70. And I know that this Dolby Atmos mod have AndroidQ support. But just a quick question: How to use it with Viper?

Now you may say: That question is already answered. Then please forgive for my stupidity cuz I have no idea where it was and please post the link to that post.

Thanks
[Android Software Development] Mervingio:
After update to latest A10 on OP6T Dolby Atmos FC with Redux zip but Viper work any fix for this?

Damn before all work flawless!!!!
[Android Software Development] escorpion_sw:
same here :(
[Android Software Development] Adamk102:
Dolby Atmos for Android Q??

Wysłane z mojego MI 6 przy użyciu Tapatalka
[Android Software Development] aarkee:
Doesn't have Atmos on op6 stock.
[Android Software Development] MitchiePitchie:
Hey, I'm back. Is there a work around for Viper4Android being disabled when notification pops up? System disables it temporarily and it irritates me.
[Android Software Development] aarkee:
I all the zips, but app getting crash with every zips. I tried to edit manifest.xml also, but upon reboot its going back to default file. Any suggestions?
[Android Software Development] guitardedhero:
When convenient, please provide me your /vendor/etc/audio_effects_sec.xml.

Are you editing the file beginning with path /sbin/.magisk/mirror/??
[Android Software Development] AndrzejDwo:
Here you are. As for me it looks like soundbooster comes from SoundAlive app.... Hopefully we can do something about it.

Cheers
[Android Software Development] guitardedhero:
Thank you. Please try this in the module folders where this file exists, or in /vendor/etc/ of any of the modules if not found in any module (/data/adb/modules/*/system/vendor/etc/).
[Android Software Development] mohand06:
Hi [MENTION=4445176]guitardedhero[/MENTION]! Nice seeing you back in the game.

I'm using Samsung A3 exynos lineageOS Android 9, rooted with Magisk 20.4, on which I first flashed in Twrp this zip: DolbyQplusV6.5 [MENTION=877164]irvan[/MENTION]15Maulana.zip. The app shows in drawer but when changing presets, it simply closes; the preset is applied and there's a little effect (I think). In dumpsys, the library isn't loaded but ds is present in lower part.

I flashed always in Twrp for the sake of testing the zip edited by _BГ@ckθut: DolbyAtmos-axon9-A10-0.64.zip while keeping the ds. This time the app, which shows in same blue-red Maulana UI, behaves normally and the presets are effectively applied -- game for one is louder than the others.

See attached files.

Thanks and best regards
[Android Software Development] mohand06:
Sorry didn't notice that sound leveler was already ON for games.
[Android Software Development] aarkee:
No, I just directly edited vendor/ect/vintf/manifest and I tried through sbin too. But same result
[Android Software Development] JakunTech1010:
So uhhhhhh have anyone tried out V4A with this Dolby Atmos? If yes and if success than please tell me how.

Thanks
[Android Software Development] aarkee:
Op6,, oos 10.3
[Android Software Development] JakunTech1010:
Hello so I have install Viper4Android 2.7.1.0 reboot then DolbyAtmos 0.83 and reboot. V4A worked but not DolbyAtmos: It just keep force stop.

So I run su -c dumpsys media.audio_flinger and it output are inside sysdumpoutput.text (I know I type it wrong but who care), I also post my

/vendor/etc/vintf/manifest.xml in here. Please take a look. Also, if you needed to see anything else, please tell me.

Thanks
[Android Software Development] _BГ@ckθut:
Has you figure out to make it work yet?...i just upgrade to 10.3.1 on my 6t and got similar issues but just got it work now! First you install Dolby version 0.7292...if it work then it good but if it still force close...just go to magisk and dirty flash the latest version which is 0.842 ...it work for me...jope it work for you too✓

Edit: the best part is that ainur Sauron work along with dolby too and if you need a UO lmk :)
[Android Software Development] guitardedhero:
Yes, and they make one awesome pair. :good:
[Android Software Development] guitardedhero:
OP6 OOS no longer allows changes to the partitions directly?

Manifest.xml either failed to get patched during installation or your device reverts changes to the partitions during device boot.
[Android Software Development] JakunTech1010:
OK but I decided to use ViperAtmos Redux 0.10 because I have no idea how to patch it.

Well DolbyAtmos work great without any issues at all (For now)

But Viper did not work at all: All it say is that it needed to install driver, I choose No and check driver status, it say driver version is 0.0.0.0. I know that something was wrong so I choose Install Driver but it says driver install failed I/O error.

So uhh did you have any solutions

I'm using LineageOS 17 from Grarak for A70 SM-A705F, latest build 20191230
[Android Software Development] ramrastus:
Can I would flash this over on DA 0.842 & v4a 2.7.1.0? Which was already working great..
[Android Software Development] repey6:
Simply need aml compatibility. Need unity build. IMHO.
[Android Software Development] aarkee:
Can you explain. I'm noob
[Android Software Development] guitardedhero:
ViPER|Atmos™ is a differently named module so it will not install over either module.

Yes, please explain how the lack of AML compatibility (is that even a thing?) and Unity is why edits to partitions are reverted when rebooted for some users.
[Android Software Development] AndrzejDwo:
Hi again!

Tried with replacing this file but it didn't work unfortunately. I've checked manifest.xml and it seems like it's modded properly. I've tried also to disable SoundAlive app but still no luck... Logs and manifest.xml attached

Cheers
[Android Software Development] guitardedhero:
Try this one.
[Android Software Development] AndrzejDwo:
Still same, app is crashing. Do you need any additional info after each replacement?
[Android Software Development] guitardedhero:
Not really. Just trying to get a Dolby effect-chain while still keeping SoundAlive.

Dumpsys output look any different now?
[Android Software Development] AndrzejDwo:
Better if you check it yourself ;)
[Android Software Development] niyonsv:
Great to see that the title of this thread now just says — Dolby Atmos ™ ?
[Android Software Development] Voenix:
Can you make it Android 10 compatible?

It says Pie only, but maybe it will work.
[Android Software Development] Adamk102:
On custom rom ,last version works on Q

Wysłane z mojego MI 6 przy użyciu Tapatalka