Collective Dolby Atmos® Nougat Port Thread [Unity][Deprecated]

[Zackptg5]

This is the Dolby Atmos ported from BQ Aquaris X5 and Lenovo K6 stock Nougat ROMs. Like with @guitardedhero's ZTE Axon 7 Dolby Atmos Oreo port, it requires the stock audioserver from the roms. This greatly limits it's compatibility and likely won't work on devices/roms with a lot of audio customization. However it should work on most
Huge thanks to @ahrion who taught me everything I know about app porting

These installers utilize my Unity installer that will install the mod to magisk or system depending on the device setup and will prepare it for any root solution (for anything other than magisk, supersu, and phh superuser, you will need init.d support)

Troubleshooting:

Audio Mod Troubleshooting Guide

Installation/Upgrade:
Flash the zip and your done! If your flashing a newer version of this mod, the installer will detect the old one and perform an upgrade

Uninstallation:
Just flash the zip again and it'll detect the current install and uninstall it. Pretty easy huh?

Magisk Version Compatibility:
v15.3 - v18.1

DOWNLOAD

Credits of Originality:
- Dolby
- BQ
- Lenovo

XDA:DevDB Information
Collective Dolby Atmos® Nougat Port Thread [Unity], App for the Android General

Contributors
Zackptg5

Version Information
Status: Stable
Current Stable Version: v1.8
Stable Release Date: 2019-01-16

Created 2019-01-24
Last Updated 2020-01-01

 

[The Tox]

Great work , the new UI is awesome , and the dynamic mode is a very good addition to the old modes

Thanks ?

Sent from my X5 Plus using XDA Labs

 

[guitardedhero]

:highfive:

 

[repey6]

Sorry but not work on my Redmi 4x RR 5.8.5 7.1OS. FC.

 

[Zackptg5]

Sorry but not work on my Redmi 4x RR 5.8.5 7.1OS. FC.

Can you go over the troubleshooting section of the op?

 

[repey6]

Can you go over the troubleshooting section of the op?

Sorry.Not other mod . Clear installation. Log maybe later. And can't unistall it.

 

[mohand06]

@Zackptg5, flashed this Dolby-BQ-X5-v1.0.zip in twrp_3.0.2-1_sm-a310 (Samsung exynos SM-A310F) on clean stock nougat 7.0, no boot even when restoring original audioserver. Only exit is restoring system. Recovery.log and system space screenshot attached.

 

[Zackptg5]

@Zackptg5, flashed this Dolby-BQ-X5-v1.0.zip in twrp_3.0.2-1_sm-a310 (Samsung exynos SM-A310F) on clean stock nougat 7.0, no boot even when restoring original audioserver. Only exit is restoring system. Recovery.log and system space screenshot attached.

The recovery log outlines the problem: you have no space left in your system partition. The tricky thing with audioserver is that it requires proper permissions and chcon set or you won't be able to boot. When you flash this mod again to uninstall it, it restores stock audioserver and sets those permissions but since the install itself never finished, there's no telling what would happen. I recommend switching to magisk as it stores all of its mods on your /data partition which would avoid this problem

 

[mohand06]

The recovery log outlines the problem: you have no space left in your system partition. The tricky thing with audioserver is that it requires proper permissions and chcon set or you won't be able to boot. When you flash this mod again to uninstall it, it restores stock audioserver and sets those permissions but since the install itself never finished, there's no telling what would happen. I recommend switching to magisk as it stores all of its mods on your /data partition which would avoid this problem

The attached screenshot of system partition shows that there's 206.08Mb space available. Restored audioserver with 0755 permissions. Thus the issue is elsewhere. Fyi, I used to flash each of gh's Dolby Atmos™ for Oreo test builds and I always manage to get out of the no boot issue by the audio server restoring trick.

As for using magisk, which I tried and have sometimes the issue of no apps in drawer though modules present in magisk, I still feel more comfortable with supersu. Thanks for your reply.

 

[Zackptg5]

The attached screenshot of system partition shows that there's 206.08Mb space available. Restored audioserver with 0755 permissions. Thus the issue is elsewhere. Fyi, I used to flash each of gh's Dolby Atmos™ for Oreo test builds and I always manage to get out of the no boot issue by the audio server restoring trick.

As for using magisk, which I tried and have sometimes the issue of no apps in drawer though modules present in magisk, I still feel more comfortable with supersu. Thanks for your reply.

That's not enough. You need to do this:

chown 0:2000 /system/bin/audioserver
chmod 0755 /system/bin/audioserver
chcon u:object_r:audioserver_exec:s0 /system/bin/audioserver

The no space error actually referred to the /system/vendor folder so I'm not sure how you're partition layout is. The only time modules won't show up in magisk is when there's a bad post-fs-data script that errors out and/or takes too long to finish. Magisk is easier because you can just delete the module folder and be done with it

 

[Nightdemon1999]

Perfectly work with redmi note 4(mido) on official miui beta rom with magisk..The Ui is fantastic...but i wonder what demo actually do..i just see the slideshow but none of any sound.. @.@ ..nah but i dont care much about it as long the mod work . 1 more things is when i install it alongside with ainur sauron...the dolby atmos will crash.... But without ainur it works like charm.

 

[mohand06]

That's not enough. You need to do this:

chown 0:2000 /system/bin/audioserver
chmod 0755 /system/bin/audioserver
chcon u:object_r:audioserver_exec:s0 /system/bin/audioserver

The no space error actually referred to the /system/vendor folder so I'm not sure how you're partition layout is. The only time modules won't show up in magisk is when there's a bad post-fs-data script that errors out and/or takes too long to finish. Magisk is easier because you can just delete the module folder and be done with it

OK that's fine, I understand that I can't install the new dolby on my system by flashing the zip in recovery as I don't intend to switch to magisk for now.
I used to manually install v4a, what about manually installing dolby? Would you direct me what to install and where. I know for the permissions. Thanks

 

[Zackptg5]

Perfectly work with redmi note 4(mido) on official miui beta rom with magisk..The Ui is fantastic...but i wonder what demo actually do..i just see the slideshow but none of any sound.. @.@ ..nah but i dont care much about it as long the mod work . 1 more things is when i install it alongside with ainur sauron...the dolby atmos will crash.... But without ainur it works like charm.

Sound doesn't work? Works for me. In order to use multiple audio mods like sauron and dolby together with magisk, you need to flash audio modification library (it's also on magisk repo)

OK that's fine, I understand that I can't install the new dolby on my system by flashing the zip in recovery as I don't intend to switch to magisk for now.
I used to manually install v4a, what about manually installing dolby? Would you direct me what to install and where. I know for the permissions. Thanks

If you unzip the installer, all of the files are in the path they would be normally installed into (system folder) so just copy that layout. Although unless you cleared up some space, it won't work. In which case if you do clear some space, you're better off just flashing the zip. It also installed boot scripts and addon.d script which are generated by the installer depending on your device setup so an alternative to the scripts would be setting selinux to permissive

 

[Nightdemon1999]

Sound doesn't work? Works for me. In order to use multiple audio mods like sauron and dolby together with magisk, you need to flash audio modification library (it's also on magisk repo)

Okay after im tried again it did not work..after first reboot..but after second time reboot both ainur and dolby working ..tq for u help :good:

 

[Tung Lam]

Help, please! My phone samsung J710FN can't boot stuck at samsung logo after install via Magisk.

 

[Zackptg5]

Help, please! My phone samsung J710FN can't boot stuck at samsung logo after install via Magisk.

Are you on stock samsung? Not surprised this doesn't work. Audioserver keeps crashing due to it not containing some stuff needed for some other libraries present on your device. There's not much I can do about it so it's just not compatible with your device unfortunately. You can flash the zip again and it'll uninstall it

 

[Tung Lam]

Are you on stock samsung? Not surprised this doesn't work. Audioserver keeps crashing due to it not containing some stuff needed for some other libraries present on your device. There's not much I can do about it so it's just not compatible with your device unfortunately. You can flash the zip again and it'll uninstall it

I'm on a custom touchwiz ROM.

 

[laugeek57]

Hello,Zackptg5

Is there a solution for this sound module to work on my Nexus 7 2012 aosp rom 7.1.2
The installation runs without worries but I have got force close by opening the application Dolby Atmos...
Thanks for help...

 

[Zackptg5]

Hello,Zackptg5

Is there a solution for this sound module to work on my Nexus 7 2012 aosp rom 7.1.2
The installation runs without worries but I have got force close by opening the application Dolby Atmos...
Thanks for help...

Can you run through the troubleshooting guide and see if any of the listed solutions solves it? Try setting selinux to permissive too

 

[laugeek57]

Can you run through the troubleshooting guide and see if any of the listed solutions solves it? Try setting selinux to permissive too

Selinux to permissive again force close any solutution ?