yashsingh1/xdaforums huggingface dataset:
[Android Software Development] Dark Fear:
yeah it says success .. but the problem is after flashing the module, dolby app doesn't open when i press it .. although i tried sony dolby recently , it opens

but power toggle doesnt work and i cant change equalizer (it says dolby is off)
[Android Software Development] g3v0:
Can you attach the output of "su -c dumpsys media.audio_flinger" and a logcat of launching/crashing the app?

I'm copy-pasting the bug report notes from the Telegram channel below:
[Android Software Development] noskojv:
Dolby works but why is the interface empty at the bottom ?

P.S. Android 10 AOSP rom (Xiaomi Redmi Note 5).
[Android Software Development] CapnShitzhu:
Flashed LazyKernel and Evrything seems to work. Thanks for the assist

However I noticed the sound turns off for like for a millisecond on high decibal parts of songs. I'd have to decrease volume by 1 or 2 step to limit that
[Android Software Development] pbergonzi:
Congrats on having fixed it.

If you don't have an ACDB flashed, that might help. I know ACDB is only for if you have other sound mods, but guitardedhero recommended it anyway.

You might try other Dolby versions also to see if it helps. Good luck.
[Android Software Development] noskojv:
After a conversation on the phone, Dolby ATMOS processing disappears.

Android 10 AOSP rom (Xiaomi Redmi Note 5)
[Android Software Development] pbergonzi:
Any other sound mods? ACDB Installed?
[Android Software Development] noskojv:
There are no other sound mods. ACDB Installed.
[Android Software Development] pbergonzi:
Custom Kernel?

Try selinux switcher Magisk mod?

Try other versions of Dolby?
[Android Software Development] noskojv:
SELinux Permissive.

Tried all versions, after talking on the phone (if the call was taken while playing music on Bluetooth) processing is disabled and no longer enabled, only after restarting it works again.
[Android Software Development] pbergonzi:
I'm glad you are so persistent.

How about in your settings->developer options, trying different bluetooth codecs?

Or maybe some other bt settings might have something to do with it.

It' be a shame if you can't use Dolby. I love it, but there are other great audio mods around. I tried that Motorola mod I think it was, where you have to allow the equalizer tile in the quick settings. It was exceptionally good and simple too.
[Android Software Development] noskojv:
On 10 Android ViPER4Android behaves the same way, processing sometimes disappears.

Need to fix the Dolby service in the system so that other processes can't stop it.

I do not know how to do this, the author may be able to do it using a script or additional Dolby system files, or increase the priority of the Dolby application by editing the APK.

In General, there are a lot of options.
[Android Software Development] pbergonzi:
I'm sorry you can't get anything going well. What kind of phone you got?

Might I suggest a different phone? If you really want sound mods, that might be a solution.
[Android Software Development] noskojv:
Android 10 AOSP rom Havoc-OS-v3.7 (Xiaomi Redmi Note 5).
[Android Software Development] pbergonzi:
Sorry I've run out of ideas.

I hope someone can help out.
[Android Software Development] JakunTech1010:
SoundSpace Dolby Atmos profile for RC1/RC4

Version: 6c

For Dolby Atmos RC1/RC4 only.

Download here: https://drive.google.com/file/d/10Y3irINO0o-aXu9PptmGpfoSyciVhUBQ/view?usp=drivesdk

Main folder: https://drive.google.com/folderview?id=1QZlkTe8Mt_ZJ7e0tUXthJ5a0hhvpZN7a

Installation:

- Ensure that the file are in: /sdcard/Download/

- Execute the following command: su -c cp -f /sdcard/Download/SSv6c.xml /vendor/etc/dolby/dap-default.xml

- Run restartdms.sh script

- Done

Changelog: up untill now all my SSxmls had used angles > 90 for surround v.speaker , cus there they should be in the 2d plane that's the soundstage. Default values are < 90 and I should have thought about it before that they are already have 90° shift in the value ?. Compared to old SSxmls this time I've also opted for height filter mode 1 which would bring the stage more to eyes-level instead of forehead-level

Note: This was not made by me

Also, new restartdms.sh script that will now automatically restart Viper or JamesDSP.
[Android Software Development] noskojv:
Dolby processing stops working after a call
[Android Software Development] Bogdans29:
Is there any similar Dolby for A7
[Android Software Development] pbergonzi:
Got this by thread search for "A7":

https://xdaforums.com/showpost.php?p=78141891&postcount=3252

You can determine if you want to try it, or try different things.
[Android Software Development] Bogdans29:
I was thinking on Android 7.1.1 ?
[Android Software Development] pbergonzi:
Good luck whatever you do.

Backup first!
[Android Software Development] Wolfcity:
Dolby for Nougat:

https://xdaforums.com/android/apps-games/soundmod-axon-7-dolby-atmos-t3412342
[Android Software Development] JakunTech1010:
New Dolby Atmos build

RC1 Debug2

Changelog:

+ Refactoring of register_service

+ Enabling the check for empty manifest file (edge-case, GSI?), in such case fallback to vendor

+ Better debug messages regarding manifest.xml.bak creation

+ Checking whether bak file can be created, otherwise fallback to vendor, otherwise throw a warning message.

Quick note: those are just small improvements upon existing installer. Overall the installer is the same.

Always save install log when installation finishes

I did not take credit for any of the soundmod

This one was made by Codrut on Telegram

Link: https://drive.google.com/folderview?id=1e_x69ZWFforhkA-WSCJY4KDFDhBCTwDk
[Android Software Development] noskojv:
After updating the custom firmware via recovery , Dolby does not work , you have to delete the module and install it again.

log - https://del.dog/mesustibif.txt
[Android Software Development] Essentrix:
Hi all. Haven't used this forum for some time since Dolby had been baked into my ROM.

Have Samsung 520F on Android 9 Stock modified Korean ROM.

Flashed latest Dolby and works if I toggle it off and back on. Then keeps working until I go away from the Dolby screen or the screen turns off then stops. Have to go back and switch it off and on again.

Any thoughts?

BTW great to see you still at it all these years later guitaredhero! You and the guys have brought a lot of pleasure to many ears... [emoji106]
[Android Software Development] JakunTech1010:
Of course

The Dolby file will patch a file directly to your system

After a ROM update, that file will be overridden
[Android Software Development] noskojv:
Other audio modules for example Viper Android after updating the firmware work the same way they did.
[Android Software Development] JakunTech1010:
Dolby Atmos needed to patch a few file to /system make it not systemlessly
[Android Software Development] noskojv:
How to do it?
[Android Software Development] JakunTech1010:
The Dolby installer

So yeah, when you update, downgrade your system, make sure to reflash Dolby
[Android Software Development] noskojv:
Can't you fix the module somehow ?

Other audio modules do not need to be reinstalled after the firmware update.
[Android Software Development] repey6:
Dev need to change your installer to magisk installer.
[Android Software Development] noskojv:
Can you do it?
[Android Software Development] repey6:
No i can't.
[Android Software Development] Essentrix:
Hi mate. Didn't realise you were still at it all these years later after the good old ARISE days. You built a great team around you and have to say the app completely changed my appreciation of music on Android.

Things are looking pretty crazy there health wise the US. Trust you and yours have been keeping safe.

Been quite different here in Oz - life almost back to a slightly modified normal...

Quick question and not sure if you have any answers but thought I'd ask.

Haven't needed to install a sound system for years except magisk viper on top of the Dolby already baked into my ROMs - been decent sound.

Recently installed Android 9 Stock modified Korean ROM on a Samsung SM-520F. Clean ROM close to stock.

Installed magisk V4A which works well then flashed latest RC Dolby from this site and works if after boot I toggle Dolby off and back on. Then keeps working so long as I stay on the Dolby screen. If I leave the Dolby screen or the screen turns off then Dolby stops. Have to go back and switch it off and on again.

Any thoughts?

Hear from you when you get a moment mate.
[Android Software Development] pbergonzi:
Guitardedhero has been preoccupied as of late, and not frequently around. If you traipse back through the thread, you will understand.

The solution for you might be to try some different versions of Dolby, as the newest might not be the best for you. Also, even though it may not be essential, installing an ACDB to go with your particular Dolby version.

A custom kernel is a prerequisite to all of this.
[Android Software Development] Essentrix:
Thanks for the feedback mate... Didn't realise where things are at for him. I'll take a look at the options and see how we go. Enjoy your weekend. Cheers
[Android Software Development] noskojv:
This module solves this problem.
[Android Software Development] Essentrix:
Hi once again mate. Quick follow up on your advice - installed earlier version with ACDB and sure enough working a treat! Much appreciated. [emoji106][emoji120]
[Android Software Development] pakpenyo:
Clean install Paranoid Android Q4 (Android 10), ph-1 devices. No soundFX or any soundmod, latest Magisk.

DA is works fine (RC1 + ACBD). But my phone call doesn't work after install DA. There is no sound at all. Install this RSPP module just make DA won't open.

Any suggestion? Thanks.
[Android Software Development] Gonime:
Noob question:

Can i install by flashing with Orange Fox? I don't want to use Magisk.

Also i'm on Lineage 17 on a Redmi Note 7 which version should i install?
[Android Software Development] KeinePanik:
If you read the troubleshooting guide - link therefore is in the OP - you will see that you can flash the actual versions with magisk only.
[Android Software Development] Gonime:
Well shame... guess i'm stuck with only AudioFX then
[Android Software Development] JakunTech1010:
New DolbyAtmos RC1 Debug

Version 2.1

Changelog:

First attempt at GSI

+ Detection of Phh / Erfan GSI, in which case enforce vendor manifest patching

+ Added missing $etc and $vetc assignments, otherwise audio_effects couldn't be patched without AML/ACDB

+ Added check for AML (imported from maxxaudio)

Note: might still not work on Xiaomi and Motorola with GSI.

Always save install log when installation finishes

Restartdms script v030

Changelog:

+ Reworked effects restarting as a function

+ Added restart for maxxaudio

+ Now handling even original dax-naming (but not removing dax db)

Remeber to delete old script file first before re-downloading if you use the command below.

Run from a root shell:

sh /sdcard/Download/restartdms.sh

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

New DolbyAtmos RC1 Debug

Version 2.1

Changelog:

First attempt at GSI

+ Detection of Phh / Erfan GSI, in which case enforce vendor manifest patching

+ Added missing $etc and $vetc assignments, otherwise audio_effects couldn't be patched without AML/ACDB

+ Added check for AML (imported from maxxaudio)

Note: might still not work on Xiaomi and Motorola with GSI.

Always save install log when installation finishes

Restartdms script v030

Changelog:

+ Reworked effects restarting as a function

+ Added restart for maxxaudio

+ Now handling even original dax-naming (but not removing dax db)

Remeber to delete old script file first before re-downloading if you use the command below.

Run from a root shell:

sh /sdcard/Download/restartdms.sh

Download folder: https://drive.google.com/folderview?id=1QZlkTe8Mt_ZJ7e0tUXthJ5a0hhvpZN7a
[Android Software Development] noskojv:
So you don't need AML/ACDB right now ?
[Android Software Development] pbergonzi:
You can always try it without and see. Easy enough to install later if need be.
[Android Software Development] gk1984:
Sorry to be late to this comment. I use same phone too. I found every audio mod breaks phone calls with Paranoid Android. Viper4Android, JamesDSP, this, and others I've tried. Only option I used well has been the app Wavelet. Its not as good as these mods but pretty close if you tune the EQ and don't get too crazy with the other options.
[Android Software Development] JakunTech1010:
New Dolby Atmos RC1 Debug 2.2b

Changelog:

+ Same GSI support as in debug2.1c

+ check for free vintf space pre-patching

+ /vendor mounting pre-patching

+ Permissive switching moved to later boot stage

+ Disable stock DaxService (RC1-only fix)

+ uninstall.sh : vintf mounting

+ uninstall.sh : DaxService re-enable (hopefully)

+ Fixed debug messages in TWRP

+ Fixed $sys and $ven in TWRP

Always save install_log and share it in case of issues.

Download link: https://drive.google.com/file/d/1-ZaZCQUC6G40lc56tmDhczHPRsDaIphp/view?usp=drivesdk
[Android Software Development] asripath:
Tried on k20 pro (evolutionx + immensity)

Issues:

On installation reboot screen brightness maxes out.

App fails to launch.

Attached install log & restartdms result.

SELinux is permissive

Dolby process is not started (ps -d | grep dolby)
[Android Software Development] repey6:
Me too
[Android Software Development] NagaPujith:
FC

Log and screenshots

Plz help
[Android Software Development] Golv:
Bootloop for me again.
[Android Software Development] guitardedhero:
Standard Edition

:

Latest: 20180207[*]MD5: 312324a14ab6644883b5828cc0bad132

- Various corrections and adjustments.
[Android Software Development] Trupen:
Stuck in recovery
[Android Software Development] giogio1:
After flashed the dolby zip from twrp I was stuck in the boot ... then I came back in TWRP and I flashed the rom zip without wipe .... then restarted the device and it restarted well ... in the drawer there is the dolby app and it works (with some small interface flaw).

Rom aicp_zl1_o-13.1-WEEKLY-20180207 for Leeco x720

TWRP twrp-3.2.1-0-20180108-codeworkx-zl1
[Android Software Development] laugeek57:
last edition standard 20180207

bootloop on mi A1 :crying:
[Android Software Development] Milkovit:
Сделайте ету версию для андроид 7
[Android Software Development] truelies1:
Need to install ViPER4Android first, then this one.
[Android Software Development] jandia7381:
+1

Same on my Kate :(
[Android Software Development] laugeek57:
Version 0202 works fine for me fortunately :D
[Android Software Development] lcsd:
Boot loop. Recovery attached, out of space?

Check diskinfo: free system 166MB, data 6.9G

Working here (op3t 64GB / oos 5.0.1 / magisk 15.3)

DolbyAtmos_Axon7_Oreo_20180202

DolbyAtmos_for_Oreo_(Unity)-20180206-1

Minor glitches

Doesn't enable Surround option

Doesn't refresh UI on/off

Doesn't show Dynamic equalization graphics
[Android Software Development] guitardedhero:
Changelog

:

[B]20180207-1 -[/B]

- Like it even makes a difference...
[Android Software Development] repey6:
I am feel success near.:D
[Android Software Development] Trupen:
Same result again stuck in recovery
[Android Software Development] laugeek57:
Originally Posted by Ni9e.

If after flashing this you are stuck on bootloop or boot screen then dont worry it happened with me aswell and here is the complete tutorial to successfully install this module. Follow step by step:

1. Reboot to recovery and flash Dolby file

2. Goto Reboot menu in recovery and select partition B

3. Now Reboot to recovery again

4. Flash Dolby file again

5. Goto Reboot menu and this time select partition A

6. Reboot system now and enjoy !!!

]20180207-1 Works on mi A1 after ,;:!! bootloop :p
[Android Software Development] jorgerolli:
Only in A1?? because in my twrp doesnt have option to reboot in A or B partition
[Android Software Development] laugeek57:
What phone do you have?
[Android Software Development] jorgerolli:
Leeco lepro3 x722
[Android Software Development] laugeek57:
rom stock 6.0 or aosp 8.1 ???
[Android Software Development] asripath:
2nd Attempt.

Removed all Audio mods.

Installed Viper4Android FX Legacy Materialized

(After Reboot everything works)

Installed AML (4.0)

Installed Ainur Narsil ( 15.09)

(After Reboot everything works)

Installed ACDB ( 0.48)

(After Reboot everything works)

Installed Dolby Atmos (RC1 -ACDB)

(After Reboot partial success)

What works?

Viper4Android works

Dolby Atmos works

So what are the issues?

1. Screen max brightness

2. Dolby Atmos works ONLY if the App is in focus

(Even after Removing battery optimization, Allowed background activity)

3. Double Tap to wake does not work anymore

(power button to turn ON screen)

4. Have to Power On/Off within Dolby Atmos App when switching modes ie Dynamic/Movie/Music otherwise it stops processing Audio.

Appreciate help to resolve the issues

Edit:

SeLinux status changes to permissive from enforcing

Edit 2:

Ran restartdms

Output:

Execute

STDOUT:

Found com.dolby.atmos + Atmos pid 7696 + Dms pid 1841

Killing Dolby Service 1841

Removing database Restarting Dolby Service + Successful 28707 Restarting com.dolby.atmos + Successful

28718

Found com.pittvandewitt viperfx Restarting 18960 + Successful 28756

+ Database dax successfully recreated

done v030

STDERR:

Edit 3:

Removed RC1 and flashed RC1 debug2_2b.

Same issues as above.

Issue 2 & 4 SOLVED by removing viper from running/cached processes and re-executing restartdms.

Enabled musicstream=true in acdb config for stream processing.

Issues 1 & 3 still present.
[Android Software Development] flash713:
[MENTION=10951315]asripath[/MENTION]

So what are the issues?

1. Screen max brightness

2. Dolby Atmos works ONLY if the App is in focus

(Even after Removing battery optimization, Allowed background activity)

3. Double Tap to wake does not work anymore

(power button to turn ON screen)

4. Have to Power On/Off within Dolby Atmos App when switching modes ie Dynamic/Movie/Music otherwise it stops processing Audio.

What device are you using? I have a OnePlus 6t and this screen brightness you're talking about in #1 , I assume you mean once you install Dolby Atmos and reboot your screen is set at max brightness and nothing will allow you to lower it...? That's not a bug with Atmos rather something that has to do with the vendor or at least that's what causes this issue on OnePlus 6/6t. If I use Pixen rom or stick OOS I don't have this brightness issue. And I always thought ACDB gets installed first then reboot system and proceed with whatever else you want to install. Pretty sure these issues you're talking about have to do with some way your phone is made and they can probably more than likely be fixed if you can either figure it out yourself or get a group together, maybe form a telegram group or something, to try and get to the bottom of why it happens exactly and can anything be done to make it not happen. Out of a the custom roms for OnePlus 6t only one has been altered made to not do this max screen brightness issue. I never got any more details about it but from what I gathered , at least on OnePlus 6t devices it had something to do with vendor.img and something that was causing it in the AOSP vendors but not stock Oxygen OS vendor. That's all I know about the brightness situation on OnePlus 6t.
[Android Software Development] milesian:
Would like to try out MaxxAudio's volume leveler on my Oreo phone but the APK's appear to target a later OS and do not install along with the Magisk flash. Please advise.
[Android Software Development] asripath:
Mentioned in my earlier post,

K20 Pro with custom ROM & Kernel (Evolution X + Immensity).

Issue 1 & 3 still persist.

Went thru this thread & telegram could not find a working solution for this mod with either stock/custom rom.
[Android Software Development] Rammit:
Try with AoSPA or extended...stable AF...u can use RC4 or RC1 debug 2.2b...flash after motoG8 mod
[Android Software Development] Lysiss:
Please HELP

MINE SAYS REGISTRATION FAILURE .. WHAT SHOULD I DO ..!! SOME ONE HELP ME PLEASE

..!! (Device :- Poco f1)

- Copying zip to temp directory

- Installing DolbyAtmos-RC1_debug.zip

- Device is system-as-root

Archive: /data/user/0/com.topjohnwu.magisk/cache/flash/install.zip

inflating: module.prop

****************

Dolby Atmos™

****************

*******************

Powered by Magisk

*******************

Archive: /data/user/0/com.topjohnwu.magisk/cache/flash/install.zip

inflating: customize.sh

- Preparing environment...

mount: can't find /sbin/.magisk/mirror/system_root/system in /proc/mounts

ENV: /sbin/.magisk/mirror/system_root/system ; /sbin/.magisk/mirror/vendor

√ Ready

- Checking rom compatibility...

√ Compatibility detected

Using 64bit variant

- Registering Dolby service...

cp: write error: No space left on device

No /system/etc/vintf mount point:

Manifest found: /system/etc/vintf/manifest.xml

Backing up manifest.xml

Patching /system/etc/vintf/manifest.xml

X Registration failure

Dolby string not found.

- Configuring Dolby Atmos™ effect...

find: /data/adb/*/acdb: No such file or directory

! Install ACDB module for full ACDB support

- Patching all Magisk module audio effects configurations...

! Effect configuration without ACDB might not be persistent

- Finalizing module...

√ gh

- Done

PLEASE HELPPPPP !!!
[Android Software Development] rrusek:
Razer Phone 2 - Lineage 17.1 - Dolby Atmos stoping after 5 min

After installation and turning on Dolby Atmos you can play music for 3 to 5 minutes then Dolby Atmos stops working and music plays without the enhancement. You can toggle off then on the effect via the quick pull down icon.

Tried all different version same thing happens. I know that hardware supports it since on the stock ROM Dolby Atmos works without issue.

Thank you in advance,

RJR
[Android Software Development] pbergonzi:
Install ACDB?

Custom kernel?

That's all I can offer.
[Android Software Development] laugeek57:
This user is confused with the new version of Razer2 rebuilt by Rei Ryuki ...

To resolve this non-processing concern, you must remove the Battery optimization on the Dolby UI and Dolby Service apk ...
[Android Software Development] clarkgable:
Does anyone have this app working on Android 11 yet?
[Android Software Development] racerx002:
This version is supposed to work on 11. I personally have not tested on 11.

https://github.com/reiryuki/Dolby-Atmos-RC4-Ryuki-Mod
[Android Software Development] clarkgable:
Thank you, that seems to have worked.
[Android Software Development] FMAranda:
OMG, this version is great. It worked on my mido without any other module. Thanks!
[Android Software Development] laugeek57:
Hi,

You can change colors on RC4 with swift installer application...(Playstore)

:)
[Android Software Development] repey6:
Developer Rei Ryuki (rei ryuki) continuous and improves gh Dolby Atmos mods for 9,10 and 11 android . His works are here https://t.me/audioryukimods
[Android Software Development] ay i:
how to download it..i already go to his github..but the button download not there

nvm..i already download it
[Android Software Development] th4n0s.0xf:
I'm using RC4 in RN7Pro.. everything works alright.

Tidal Dolby Atmos still not working, is that supposed to work?
[Android Software Development] EstherTakumi:
It will never work if your device don't have Dolby Certificate.
[Android Software Development] ban.codrut:
Are you saying that Tidal is doing a per-device check ? And there is some list of "Dolby Certified" devices somewhere that it compares against ?

This would mean that changing device model or fingerprint inside build.prop on a certified device would break Dolby Atmos support in Tidal ... (and restoring defaults will work TBC ^^ )

Can someone confirm pretty pretty please ?
[Android Software Development] noskojv:
Does not support dynamic partitions.
[Android Software Development] ecompton59:
if done right it works im on android 11 working with viper4 if installed wrong you need to uninstall all magisk mods and sound apps start over it works
[Android Software Development] RalphMalph:
I downloaded the file by Ryuki but how to flash?

By Magisk? Need ACDB?

By recovery?