[APP] [8.0+] Dolby Atmos™ Axon 7 Oreo port 20180125

[docnok63]

So you didn't do anything special to get V4A to work?

Any ideas?

This is an old V4A trick that I found works with this situation:

1) Hit V4A's Master Power
2) Use the 3 dot menu in the top right to exit V4A.
3) Use your recents and swipe right to completely wipe V4A from memory
4) Launch V4A and hit the Master Power. Profit.

 

[docnok63]

Thank you for the confidence-boost of booting with all my data intact after updating to the official OP5 firmware, unfortunately, the ViPER4Android behavior remains unchanged

Inability to process Bluetooth audio output

I wonder if headset output is different and is your testing environment.

I'm glad the update went smoothly. Try the above?

 

[Trupen]

Was very excited to flash the zip but it's stuck in twrp just dolby logo and loading

---------- Post added at 09:09 PM ---------- Previous post was at 09:01 PM ----------

Was very excited to flash the zip but it's stuck in twrp just dolby logo and loading

Any suggestions would be helpfull

 

[guitardedhero]

Changelog:

• 
  

  [B]20180119 -[/B]
  
  - Extensive adjustments to systemless
  module creation and boot script.
  
  - Removed build properties.
  
  - Default installations intended to
  accommodate HTC devices.

 

[guitardedhero]

Changelog:

• 
  

  [B]20180119-1 -[/B]
  
  - Correction to boot script.

NOTE:
Both of today's updates are focused on resolving device boot issues. :good:

HEAD'S UP:
Updated 20180119-1
Confirm MD5: 983d49e2fcf49e87afb31164610d803f
68407cc6b86a7adfa96cd4d2baf73a1f before installing 20180119-1!

 

[nhatlong1231]

Working fine on my kenzo, just a stupid question, can i dirty flash the update? or need reflash rom first?

 

[guitardedhero]

Really sorry guys...

Changelog:

• 
  

  [B]20180119-2 -[/B]
  
  - Yet another correction to boot script.

 

[guitardedhero]

Working fine on my kenzo, just a stupid question, can i dirty flash the update? or need reflash rom first?

Updating procedure is no different than installation procedure unless specified otherwise.

:good:

 

[yyz71]

Any special instructions as to install on pixel 2. Or am I S.O.L :crying:

Sent from my Google Pixel 2 using XDA Labs

 

[guitardedhero]

Any special instructions as to install on pixel 2. Or am I S.O.L :crying:

Sent from my Google Pixel 2 using XDA Labs

Report on 20180119-2. :good:

 

[jandia7381]

Report on 20180119-2. :good:

Will try new update asap n report to u later. Really enjoying it dev, thnx again n again for ur hard work ?

 

[guitardedhero]

This is an old V4A trick that I found works with this situation:

1) Hit V4A's Master Power
2) Use the 3 dot menu in the top right to exit V4A.
3) Use your recents and swipe right to completely wipe V4A from memory
4) Launch V4A and hit the Master Power. Profit.

:highfive:

 

[guitardedhero]

Dolby Atmos™
for
Android Oreo​

​

Description:

• Dolby Atmos™ Digital Signal Processer with effects and Graphic User Interface ported from the latest ZTE™ Axon 7 Android Oreo firmware.
  
• Dolby Atmos™ sound effects applied to media audio output supporting various media players.
  
• MiFavor Music Player from the same firmware included only because of its Settings option to directly launch Dolby Atmos™ for testing purposes such as the possibility of additional features and/or other unique functionality.
  
• Flexible custom recovery installation archive supporting Magisk and SuperSU installations including the options to install directly to /system for Magisk users and to install to /su for SuperSU¹ users. ¹ Experimental

Details:

• A minimum of SDK 26 (Android 8.0) is required for installation to begin, else Exit 1 will abort the recovery installation activity.
  
• Magisk users are provided the option of installing directly to /system instead of creating a Magisk module using the included arise_parameters.prop.
  
• SuperSU users with the systemless root solution are provided the option of creating a SU module instead of installing directly to /system. This is similar to Magisk module installations and is a great alternative for those with insufficient /system space to accommodate a /system installation among other benefits Magisk users enjoy.
  
  • arise_parameters.prop may be extracted from the installation archive, placed directly into root of internal storage (e.g. /sdcard/arise_parameters.prop), and edited (details and instructions inside prop file) before installing the archive in recovery.
    
  • arise_parameters.prop (with no options active) will be automatically placed in the root of internal storage if not already present during the installation in recovery.
• SuperSU users and Magisk users instructing a /system installation via a prepared /sdcard/arise_parameters.prop are encouraged to confirm a minimum of 100MB of /system space is available before beginning installation in recovery.
  
• Magisk users performing the default Magisk module installation and SuperSU users performing the optional systemless installation will require 100MB more than the minimum available /data space acceptable (usually 500MB, 500MB + 100MB = 600MB).
  
• Permissive SELinux Mode is currently required and will be set automatically each device boot. Do not install archive if this is not acceptable.

• Third party audio effects and DSP's such as https://xdaforums.com/showpost.php?p=75262097&postcount=201 ViPER4Android (<--
  link to @docnok63's solution :highfive may require some extra effort to allow processing due to Dolby Atmos' necessity for its output_session_processing music effect.

Instructions:

• Performing a backup of the /system partition in recovery is encouraged for users other than Magisk users receiving the default installation in recovery:
  
  • 
    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:

• 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/Magisk /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 application's include Terminal Emulator for Android and Termux.
      
    • In Android Terminal:
      

      su
      dumpsys media.audio_flinger

      OR
      

      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 compatibility with other audio effects, functionality in Enforcing SELinux Mode, 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.
  • Audio Modification Library (ver: ? - 2.9):
    • Scenarios: The AML 2.9 Magisk module has been found to remove a necessary audio effects configuration entry upon every device boot, if found by AML's detection mechanics targeting content to eradicate. This vulnerability for the Dolby Atmos™ system exists in every installation method if AML 2.9 is installed.
    • Solutions: Until this vulnerability is no longer exploited by the AML 2.9 Magisk module, the appropriate AML uninstallation procedure must be performed to restore Dolby Atmos ™ functionality. Fortunately, this vulnerability can be addressed quickly due to the active development of AML in addition to existing and active communication with AML authors.is currently being accommodated by the AML authors and should no longer present an issue with the next AML update. Props to the AML guys for focusing on securing a complimentary experience with this single package. :good:

Downloads:

• Android File Host
  • Latest: 20180119-2[*]MD5: d4b822bccf2e56e218ac1da548421b65

Changelog:

• 
  

  [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]20180112 -[/B]
  - Updated Magisk module.prop to 1530
  
  
  
  [B]Initial Release -[/B]
  -

Thanks you, @docnok63! :highfive:

 

[docnok63]

Thanks you, @docnok63! :highfive'

Glad it worked for ya! :highfive: but, to be honest, this was either @ahrion 's or @wrongway213 's solution to what we called the headphone bug in ARISE.

 

[jilx]

anyone knows ... working on mido???

 

[guitardedhero]

Glad it worked for ya! :highfive: but, to be honest, this was either @ahrion 's or @wrongway213 's solution to what we called the headphone bug in ARISE.

It dates back even further only without the Power Off (and then On) step(s), which is what I was lacking this entire time when performing those other steps lol. :good:

 

[jandia7381]

Reporting - latest update (magisk) working great on my Kate(reno3SE) running latest Nos official 8.1 along with viper(take from fx manager, shadow kernel) + shox + ainur sauron = its making my sound really2 BOOM!!! Enjoy it so much dev, thnx again n again
*been follow u since Arise Up!

 

[dioooi]

Hi I am on the latest 20180119-2 file and able to boot but the Dolby atmos app still fc.
Viper4a is working fine.
Any clues?

Thank you.

 

[guitardedhero]

Hi I am on the latest 20180119-2 file and able to boot but the Dolby atmos app still fc.
Viper4a is working fine.
Any clues?

Thank you.

Magisk module installation or Magisk/SuperSU /system installation?

 

[dioooi]

Magisk module installation or Magisk/SuperSU /system installation?

I installed by the zip file.
The magisk module has the Dolby atmos like the screen shot.