• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[Release Candidate] Dolby Atmos™

Search This thread

guitardedhero

Senior Member
Jan 17, 2012
7,941
24,087
40
Little Rock
Ok. Here's files you wanted guitardedhero :)

media.audio_flinger is #195 in your list.

You might try:
Code:
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:
 

Attachments

  • ShadoV90.zip
    6.9 KB · Views: 41

ShadoV90

Senior Member
Mar 5, 2017
228
85
Legnica
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"
 

Attachments

  • Log_2020-01-15_20-14-59.txt
    18.3 KB · Views: 3
Last edited:

Logan

Retired Forum Moderator
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:
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
 
  • Like
Reactions: shantam3108

guitardedhero

Senior Member
Jan 17, 2012
7,941
24,087
40
Little Rock
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"

Provide the following file for me:
Code:
/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.

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

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:
 
Last edited:
  • Like
Reactions: Bogdans29

ShadoV90

Senior Member
Mar 5, 2017
228
85
Legnica
Provide the following file for me:
Code:
/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 look forward to learning your results. :good:

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
 

Attachments

  • manifest.xml
    44.6 KB · Views: 6
  • Like
Reactions: guitardedhero

guitardedhero

Senior Member
Jan 17, 2012
7,941
24,087
40
Little Rock
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

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:
Code:
/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?
 
Last edited:

guitardedhero

Senior Member
Jan 17, 2012
7,941
24,087
40
Little Rock
Here are all xml i found through search option. Every file corresponding with it's original location.

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:
 

Attachments

  • patched-registers.zip
    6.5 KB · Views: 47

gokart2

Senior Member
Sep 21, 2011
1,443
611
Detroit
Moto Z2 Force
Google Pixel 6
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"*
 
  • Like
Reactions: guitardedhero

guitardedhero

Senior Member
Jan 17, 2012
7,941
24,087
40
Little Rock
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"*

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:
 
Last edited:

gokart2

Senior Member
Sep 21, 2011
1,443
611
Detroit
Moto Z2 Force
Google Pixel 6
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:

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.
 

ShadoV90

Senior Member
Mar 5, 2017
228
85
Legnica
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
 

Attachments

  • Screenshot_20200115-232615.jpg
    Screenshot_20200115-232615.jpg
    280.3 KB · Views: 568
  • Screenshot_20200115-233046.jpg
    Screenshot_20200115-233046.jpg
    297.7 KB · Views: 572
Last edited:

guitardedhero

Senior Member
Jan 17, 2012
7,941
24,087
40
Little Rock
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.

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:

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

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:
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 229
    Release Candidates for 9.0+ begin on page 458 and on Telegram.

    The troubleshooting guide for Release Candidates is in this post.

    updated 20200206



    YouTube™ Link!
    "Listen to the Dolby Atmos™ Difference!"




    Dolby Atmos™
    for
    Android Oreo

    LExesia.jpg


    Description:
    • Dolby Atmos™ Digital Signal Processer with effects and Graphic User Interface ported from the latest ZTE™ Axon 7 Android Oreo firmware intended for all Android devices on Android Oreo.

    • Dolby Atmos™ sound effects applied to media audio output supporting various media players.

    • Flexible custom recovery installation archive supporting Magisk and SuperSU installations as well as existing audio mod installations - fully supporting Enforcing SELinux Mode:

      • Multiple installation scenarios available using the included arise_parameters.prop that is automatically copied to /sdcard if not already there. When edited by the user in this /sdcard location, arise_parameters.prop can:

        • Instruct an installation directly to /system if a Magisk user prefers a /system installation over the Magisk module installation.

        • Instruct a system-less module installation using /su if a SuperSU user with the system-less SuperSU installation prefers a module installation for a variety of reasons such as insufficient /system space to accommodate a /system installation or the convenience of a persistent installation unaffected by rom updates.

    • An independent build maintained by @[B]Zackptg5[/B] fully integrated with Unity:

      • Active accommodation of existing and future Magisk modules relevant to audio modification.

      • Flashing the installation archive over a current installation results with an uninstallation of the Dolby Atmos™ Magisk module.

      • @[B]Zackptg5[/B] explains the nuances a bit further here.


    Details:
    • A minimum of SDK 26 (Android 8.0) is required for installation to begin, else Exit 1 will abort the recovery installation activity.

    • A root solution or a capable kernel is required in order to automate the execution of scripts during boot to allow the appropriate sepolicy rules necessary for Dolby Atmos™ functionality while in Enforcing SELinux mode.

    • Third party audio effects and DSP's such as ViPER4Android (<--
      link to @[B]docnok63[/B]'s solution :highfive:) may require some extra effort to allow processing due to Dolby Atmos' dependency on its output_session_processing music effect.


    Instructions:
    • Performing a backup of the /system partition in recovery is encouraged for users receiving a /system installation:


      • TWRP > Backup > Check System > Edit name, if desired > Swipe to perform backup operation

    • Confirm device requirements are met and installation results are acceptable.

    • Confirm an escape route is available in the event of unsuccessful device boot or unsatisfactory experience.

    • Confirm successful download and location of downloaded archive(s).

    • Boot to recovery > Install > *.zip > Swipe to perform installation operation > Advanced > Copy Log > Reboot

    • Updating procedure is no different unless specified otherwise.


    Additional Information:


    • Unsuccessful device boot:

      • If experiencing a bootloop...

        ! ! DO NOT GIVE UP ! !

      • Wait until at least 60 seconds have passed, hold down the device's Power button until a reboot is initiated... and then give up if a successful boot fails to occur.


    • Escape routes for unsuccessful/unsatisfactory installations:

      • Magisk Module Installation:

        • If booted, navigate to /magisk using a capable file manager application and delete /dolbyatmos before rebooting the device. If experiencing an unsuccessful device boot, boot to recovery using the appropriate hardware button combination for the device, install the Magisk Recovery Management archive attached below, and follow the given instructions to delete the Magisk module (/magisk/dolbyatmos).

      • SuperSU /system installations:

        • Restore Backup in recovery if available: TWRP > Restore > appropriate backup folder > Check System > Swipe to perform Restore operation

        • Install the currently installed rom zip in recovery without any partition wipes or install a different rom zip according to the rom developer's installation instructions.


    • Reporting bugs/failures:

      • An acceptable report will include the /sdcard/recovery.log received after the installation session before booting from recovery even if the recovery session appeared to be free from any error. An acceptable report will include relevant information/details to equip me to efficiently address the report.


    • Auditing:

      • Assessing the installation is encouraged for all users and is especially helpful when the collected information is included in reports of less than perfect experiences.

      • Dumpsys:

        • The dumpsys utility in Android can be a very valuable troubleshooting tool, especially audio output processing related issues, when targeting the audioflinger service. Recommended terminal applications include Terminal Emulator for Android and Termux.

        • In Android Terminal:
          Code:
          su
          dumpsys media.audio_flinger
          or
          Code:
          su -c dumpsys media.audio_flinger

        • The output generated upon tapping the Enter key is the information of interest and can be copied from the Terminal and pasted with a report, if necessary.

        • This output includes the list of successfully configured audio sound effect libraries and any successfully created effect-chains from one or more of those libraries when combined with the successful installation of an appropriate apk, Dolby Atmos being one of many examples.

      • Logging:

        • The log utility in Android is another valuable tool for many various purposes, including troubleshooting. This utility is most convenient when used with a logging application such as Matlog in order to utilize features such as word filtering and syntax highlighting among others.

        • Using the logging application's search feature, the user can filter the displayed log output using words or characters relevant to this Dolby Atmos™ port such as: dolby, dax, dlb, dseffect and include that relevant log output with reports, if necessary.


    • Testing:

      • The possibility of my experience being different from others' experiences is always present!

      • Those meeting the installation requirements may certainly test against various aspects stated as facts within this OP such as incompatibility with other audio effects, requirement of Permissive SELinux Mode :highfive:, etc.


    • Vulnerabilities:

      • The installation, as with any device content, is not immune to impact from existing and future installations of custom content. This custom content may remove or modify necessary content, or introduce conflicting content preventing Dolby Atmos™ from functioning as intended by this mod's installation. Security measures can block these scenarios from occuring but will typically be implemented only after the discovery of such cases of "breaking" Dolby Atmos™ functionality, in which case, the relevant vulnerability will be omitted from this particular section.

      • Vulnerability: --

        • Scenario: --


    Downloads:


    Changelog:

    • Code:
      [B]Standard 20180219 -[/B]
      
      - Expiration met for the Dolby Atmos
      Demo Video component after confirmation
      of its lack for volume support indicated a
      native "bug" and not a porting shortcoming.
      
      - A reduction of 67MB, uncompressed, now
      totaling 15.49MB uncompressed, without
      the Dolby Atmos Demo Video component.
      
      - Abandonment of the recently introduced
      libsurround_proc.so library (suspect of recent
      audio unpleasantness) from the Nokia
      6 Official Oreo build that was paired with
      that same firmware's Dolby Surround Sound
      Settings' menu as an additional apk that is
      currently still included and still in its trial
      period.
      
      - SUBSTANTIAL adjustments, additions, and
      improvements to every script - installation
      and boot scripts, the most comprehensive
      update for this shell component thus far.
      
      
      
      
      [B]Unity 20180220 -[/B]
      
      - Added the debloated apk.

      Code:
      [B]Standard 20180218 -[/B]
      
      - Updated installation script and
      functions with Magisk (1540).
      
      - Adjustments to boot scripts.
      
      - Added surround processing library
      from the native CustDolbySettings.apk
      firmware (Nokia 6 Official Oreo).
      
      - Temporary icon change for
      CustDolbySettings.apk.
      
      
      
      [B]Unity 20180218 -[/B]
      
      - Reworked bootmode support for devices
      with separate vendor partitions, added
      dolby surround app.
      
      
      
      [B]Standard 20180216 -[/B]
      
      - Fixed a critical error in libswvlldp.so's
      effect configuration in the XML
      configuration.
      
      - Several adjustments to boot scripts.
      
      
      
      [B]Unity 20180216 -[/B]
      
      - Fix issues users with devices that use
      audio_effect.xml were having. Thanks to
      [user=7073442]@manhong2112[/user] for the patience
      and troubleshooting.
      
      
      
      [B]Standard 20180215 -[/B]
      
      - Added new CustDolbySettings.apk
      from the latest Nokia 6 official Oreo
      firmware (untested/experimental).
      
      - Slight change in post-fs-data.sh
      boot script.
      
      
      
      [B]Standard 20180214 -[/B]
      
      - Correction to Pixel 2/2 XL detection.
      
      
      
      [B]Unity 20180214 -[/B]
      
      - Adjustments to unique audio effects
      configuration preparation.
      
      
      
      [B]20180214 -[/B]
      
      - Minor corrections and enhancements.
      
      
      
      [B]20180213-2 -[/B]
      
      - Adjustment to SuperSU /su
      module installation.
      
      
      
      [B]20180213-1 -[/B]
      
      - Completed the incomplete service.sh
      script mistakenly thought as completed.
      
      
      
      [B]20180213 -[/B]
      
      - Extensive reworking of boot scripts
      aimed at device boot success and
      debloat.
      
      
      
      [B]20180212-1 -[/B]
      
      - Samsung compatibility attempt
      via the disabling of the SoundAlive
      music output_session_processing
      effect.
      
      
      
      [B]20180212 -[/B]
      
      - Corrected library_migration function.
      
      
      
      [B]20180211-1 -[/B]
      
      - Testing new library migration
      function.
      
      
      
      [B]20180211 -[/B]
      
      - Accommodation for audio_effects.xml
      configurations lacking
      <postprocess></postprocess> section.
      
      - Adjustments to boot scripts focused
      on device boot success.
      
      
      
      [B]20180210 -[/B]
      
      - Resolved accidental omission of
      libstagefright_soft_ddpdec.so.
      
      
      
      [B]20180209-3 -[/B]
      
      - Don't be helpful, be harmless.
      
      
      
      [B]20180209-2 -[/B]
      
      - Corrections and adjustments to
      /system installations.
      
      - Automatic audioserver restoration
      during all system-less installations.
      
      
      
      [B]20180209-1 -[/B]
      
      - Correction to audio_effects.xml
      manipulation.
      
      
      
      [B]20180209 -[/B]
      
      - Correction to typo preventing
      audio_effects.xml manipulation.
      
      
      
      [B]20180208-4 -[/B]
      
      - Minor adjustments and improvements.
      
      
      
      [B]20180208-3 -[/B]
      
      - ...
      
      
      
      [B]20180208-2 -[/B]
      
      - meh.
      
      
      
      [B]20180208-1 -[/B]
      
      - More than enough changes to
      likely introduce new errors.
      
      
      
      [B]20180208 -[/B]
      
      - Script corrections and enhancements.
      
      
      
      [B]20180207-2 -[/B]
      
      - Does it even matter at this.point??
      
      
      
      [B]20180207-1 -[/B]
      
      - Like it even makes a difference...
      
      
      
      [B]20180207 -[/B]
      
      - Various corrections and adjustments.
      
      
      
      [B]20180206-2 -[/B]
      
      - Redundant changelog is redundant.
      
      
      
      [B]20180206-1 -[/B]
      
      - Further error corrections.
      
      
      
      [B]20180206 -[/B]
      
      - Various error corrections.
      
      
      
      [B]20180205-1 -[/B]
      
      - Various error corrections.
      
      
      
      [B]20180205 -[/B]
      
      - Initial release integrating Unity
      installation and scripts courtesy
      of @ahrion and @Zackptg5.
      
      
      
      [B]20180202 -[/B]
      
      - Corrected a critical error recently
      introduced by "reckless thumbing"
      to the audio effects configuration
      operation for /system installations.
      
      - The Magisk binary's --mountimg
      function is once again used for
      mounting the Magisk image volume
      if the standard mount attempt is
      unsuccessful.
      
      - Various enhancements.
      
      
      
      [B]20180201 -[/B]
      
      - Boot scripts completely
      rewritten.
      
      - Bundled Magisk's 1531 binary in
      an attempt to access its functions
      during the recovery session instead
      of the existing binary for certain
      Magisk-specific operations.
      
      - Various corrections and refinements.
      
      
      
      [B]20180131-1 -[/B]
      
      - Minor adjustments.
      
      
      
      [B]20180131 -[/B]
      
      - Numerous corrections and refinements.
      
      - Enforcing SELinux Mode fully supported.
      
      - No longer affects SELinux mode in any way.
      
      
      
      [B]20180129-1 -[/B]
      
      - Minor corrections.
      
      
      
      [B]20180129 -[/B]
      
      - Numerous changes/improvements
      to all scripts.
      
      
      
      [B]20180127 -[/B]
      
      - Numerous changes/improvements
      across the entire archive.
      
      
      
      [B]20180126-6 -[/B]
      
      - Slight adjustment to scripts.
      
      
      
      [B]20180126-5 -[/B]
      
      - Boot scripts restructuring and
      enhancements targeting successful
      device boot and additional
      functionality.[
      
      
      
      [B]20180126-4 -[/B]
      
      - Does it even matter at this point??
      
      
      
      [B]20180126-3 -[/B]
      
      - Reverted the recent option
      introducing unsuccessful results.
      
      
      
      [B]20180126-2 -[/B]
      
      - Redundant changelog is
      redundant...
      
      
      
      [B]20180126-1 -[/B]
      
      - Corrected, yet another, error
      introduced with the latest
      /sdcard/arise_parameters.prop
      option that would only affect those
      installations utilizing this option.
      
      
      
      [B]20180126 -[/B]
      
      - Various corrections of errors
      introduced with the changes to
      accommodate the recently added
      /sdcard/arise_parameters.prop
      option.
      
      
      
      [B]20180125-3 -[/B]
      
      - Corrected duplicate
      output_session_processing entry
      for module installations.
      
      
      
      [B]20180125-2 -[/B]
      
      - Added option to install custom
      dolbyserver instead of native
      audioserver for those unable to
      successfully boot with the native Axon 7
      Oreo /bin/audioserver. (Refer to
      arise_parameters.prop for full details)
      
      - Updated arise_parameters.prop.
      
      
      
      [B]20180125-1 -[/B]
      
      - Updated apk internal filesystem
      and information (Does NOT affect
      installation success-rate).
      
      
      
      [B]20180125 -[/B]
      
      - Adjustment to Xposed detection.
      
      
      
      [B]20180124-1 -[/B]
      
      - Unique atmos library and effect
      UUID to accommodate native Dolby
      effects.
      
      
      
      [B]20180124 -[/B]
      
      - Adjustment to Magisk variables with
      existing audio effects configurations.
      
      
      
      [B]20180122-2 -[/B]
      
      - Mount magisk.img with Magisk's
      util_functions.sh if initial mount
      attempt was unsuccessful.
      
      
      
      [B]20180122-1 -[/B]
      
      - Correction to audio effects
      configuration manipulation.
      
      
      
      [B]20180122 -[/B]
      
      - Correction of introduced errors.
      
      
      
      [B]20180121 -[/B]
      
      - Extensive adjustments to installation script.
      
      - Addressed Pixel, Samsung, /su module, and
      general installations.
      
      - Removed previously bundled music player.
      
      - Beginning of DolbyAtmos.apk customization
      and experimentation.
      
      
      
      [B]20180120-1 -[/B]
      
      - Conservative shift of boot scripts.
      
      
      
      [B]20180120 -[/B]
      
      - Various and discriminate installation
      and boot script adjustments.
      
      
      
      [B]20180119-3 -[/B]
      
      - Third time's the charm??
      
      
      
      [B]20180119-2 -[/B]
      
      - Yet another correction to boot script.
      
      
      
      [B]20180119-1 -[/B]
      
      - Correction to boot script.
      
      
      
      [B]20180119 -[/B]
      
      - Extensive adjustments to systemless
      module creation and boot script.
      
      - Removed build properties.
      
      - Default installations intended to
      accommodate HTC devices.
      
      
      
      [B]20180117-1 -[/B]
      
      - Correction to
      /odm/etc/audio_policy_configuration.xml
      symlink.
      
      
      
      [B]20180117 -[/B]
      
      - Various script corrections.
      
      - Recovery Management zip now supports
      SuperSU's /data/su.img and is now included
      in the Dolby Atmos zip for convenient access.
      
      
      
      [B]20180114-4 -[/B]
      
      - More script corrections.
      
      
      
      [B]20180114-3 -[/B]
      
      - Script error correction.
      
      
      
      [B]20180114-2 -[/B]
      
      - Further script changes.
      
      
      
      [B]20180114-1 -[/B]
      
      - Adjustment to supported .prop detection.
      
      - Removed experimental /*_contexts patches.
      
      - Various script changes.
      
      
      
      [B]20180114 -[/B]
      
      - Corrected Magisk module installation.
      
      - Added systemless installation option
      for SuperSU users (/su/dolbyatmos).
      
      - Updated /sdcard/arise_parameters.prop
      (will overwrite the no longer supported .prop).
      
      - Various script changes.
      
      
      
      [B]20180112-2 -[/B]
      
      - Added missing setprop section
      to script in /system installations.
      
      
      
      [B]20180112-1 -[/B]
      
      - Added two library dependencies
      to accommodate devices without
      either library. (@Zackptg5)
      
      - Adjustment to vendor partition
      audio effects configuration
      detection. (@Zackptg5)
      
      - Added Xposed alert describing
      potential conflict and potential resolution
      of Dolby Atmos functionality. (@MMWolverine)
      
      - Added /system free space detection,
      resolution methods, and installation exit
      for /system installations destined to fail due
      to insufficient space to accommodate the
      Dolby Atmos system.
      
      Massive shout out to the many users
      responsible for the current success rate
      enjoyed by this Dolby Atmos Oreo solution!
      
      :highfive:
      
      
      
      [B]20180112 -[/B]
      
      - Updated Magisk module.prop to 1530
      
      
      
      [B]Initial Release -[/B]
      -


    Credits:
    45
    Release Candidate 1:
    • 32-bit and 64-bit installations from a single zip.

    • Axon 9 Pro apk and effect library used in both 32-bit and 64-bit installations to provide the most consistent experience for all users.

    • This allows 32-bit users to avoid the 3dB GEQ boost limit as well as any license check by Lenovo.

    • Removed much of the verbose messaging during the installation.

    • Refinements and minor corrections to every single script.

    Procedure:
    • Install ACDB 0.45 if not already installed.

    • Uninstall any existing Dolby Atmos™ installation and reboot.

    • Install RC1 in Magisk Manager or in custom recovery.

    • Save installation log before rebooting.

    • Apply your best effort to find a failure or force a failure of functionality by any reasonable means - deleting/overwriting something will not count, obviously.
    43
    God, I miss him...
    40
    Android Oreo Database

    /system/bin/audioserver <-- Drive link


    • Purpose and Contribution:

      • Introduced with Android Nougat, audioserver appears as its own binary after years of being a component of /system/bin/mediaserver in all Android firmware.
      • Introduced with Android Nougat, vendor provided Dolby Atmos™ software audio solutions appear with a new media.dolby_memoryservice that is compiled into /system/bin/audioserver as well as a unique system library typically appearing as /system/vendor/lib/libdlbmemoryservice.so.
      • These new components are crucial to a functional Dolby Atmos software solution and there is currently no known way of achieving any amount of success without them.
      • While porting the very first Nougat Dolby Atmos system available, courtesy of ZTE™ Axon 7’s initial Nougat firmware image, I discovered this implementation and a functional port was finally available.
      • However, using a Nexus 6 at the time, I was able to evade nearly all bootloop scenarios with much of what would cause a bootloop scenario for others.
      • It took no time to determine that this new media.dolby_memoryservice component was going to be a challenge in achieving a viable Dolby Atmos Nougat port.
      • To begin, results were determined: Successful device boot or Unsuccessful device boot.
      • Stock firmware seemed to fare much better than custom firmware, even for just a single device.
      • A pattern began to emerge for me when focusing only on the audioserver binary: Stock firmware had an audioserver file size range (21.50KB-21.53KB) and Custom firmware had an audioserver file size range of its own (21.58KB-21.60KB).
      • Not a significant difference, unless you were looking for a difference.
      • This assessment presented an effective predictibility of an installation scenario's success and failure with nearly 100% accuracy (nearly only because every possible scenario is not documented).
      • This audioserver database is intended for those that have determined a single scenario as successful or as unsuccessful due to the native audioserver binary in their device’s rom being overwritten or symlinked over with the audioserver native to the ZTE™ Axon 7 Oreo firmware AND NOT A RESULT OF ANY OTHER FILE OR SCRIPT OPERATION!!
      • Simply, those with success have the easier path requiring nearly no effort other than uploading the native audioserver from their firmware along with the firmware build.prop to the WIN audioserver folder.
      • Those contributing to the FAIL audioserver folder with the native audioserver along with the firmware build.prop will only be able to do so after some personal testing to ensure the audioserver switching is the exclusive cause of an unsuccessful device boot after flashing the Dolby Atmos installation archive in recovery.

    :good: