neither of which works on axon7. thinking about going back to the last edl package that everything worked on. maximum api is either 21 or 24, and i'm on 27. this is ridiculous trying to get one very necessary app to work.
neither of which works on axon7. thinking about going back to the last edl package that everything worked on. maximum api is either 21 or 24, and i'm on 27. this is ridiculous trying to get one very necessary app to work.
Can't we make a software with backward compatibilty or increase the sdk of old version softwares and compile them in magisk modules.
Wolfcity
Recognized Contributor
I think you underestimate the procedure to make all the libaries work on devices they aren't made for.
Each device has unique audiolibaries and works with a special audioserver. There were 4 mods for Nougat (where only 1 or 2 were proceeding on one device) and there is only one for Oreo, made by @guitardedhero. As he is a bit out of business atm it seems there aren't so many devs with the ability to make such a mod work on several devices (that you have to own to troubleshoot).
But you're free to try it on your own. I did and it exceeded my possibilities by far.
Last edited:
It's one of those Your Mileage May Vary things. Dolby is installed and working just fine (along with Viper) on this Axon 7 and AospExtended Oreo. API 27 ofc. Used the UNITY installer.
All of that was quite awhile back but still working. Not using Magisk, btw. SU kinda guy. [emoji16]
IMO I don't see Dolby as a very necessary app (nice to have luxury item) so I haven't messed with trying to install it on other devices running Oreo (plus they don't have the nice speakers like the Axon).
ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HellsGate Kernel, Multiboot, XDA Legacy
Hi! Can someone guide me to download the version that works with Magisk? 
( I went through the description but it does not make any sense. Some words used in the description are not that simple to understand. IDK. It maybe a my problem. )
( I went through the description but it does not make any sense. Some words used in the description are not that simple to understand. IDK. It maybe a my problem. )
Last edited:
Hi! Can someone guide me to download the version that works with Magisk?
The OP is more than outdated. You can get the latest release under this link:
https://androidfilehost.com/?fid=11410963190603907670
this one ended up working for me
https://xdaforums.com/android/software/mm-p-dolby-digital-plus-arise-20181115-t3868192
Hi guitardedhero,
Thanks for quoting docnok63's trick to solve V4A not processing in the OP of your Dolby Atmos Oreo sound port.
As I thanked docnok63 separately for this, I have been searching for a solution to the problem of making Dolby Atmos and V4A work at the same time for about a month but no success. (I am using Magisk version 18 with zackptg5's AML). The only issue with this trick is, V4A processing is lost after playing a song. It would be great if the V4A processing is retained for a session if not for ever before one has to repeat this trick to make it work again. Looking for a solution to that issue as well.
Thanks once again.
[*] 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.
[/LIST]
Thanks for quoting docnok63's trick to solve V4A not processing in the OP of your Dolby Atmos Oreo sound port.
As I thanked docnok63 separately for this, I have been searching for a solution to the problem of making Dolby Atmos and V4A work at the same time for about a month but no success. (I am using Magisk version 18 with zackptg5's AML). The only issue with this trick is, V4A processing is lost after playing a song. It would be great if the V4A processing is retained for a session if not for ever before one has to repeat this trick to make it work again. Looking for a solution to that issue as well.
Thanks once again.
[*] 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.[/LIST]
Hi docnok63,
Thanks for this (URL="https://xdaforums.com/showpost.php?p=75262097&postcount=201") excellent trick to make V4A and Dolby Atmos work together in Oreo rom.
This worked for me when I tried it after coming across your post thru' guitardedhero's OP for Dolby Atmos Oreo sound port. In fact, I have been trying to get both Dolby Atmos and V4A working together for about a month. I searched a lot on this issue and I learnt that the success varied from ROMs, Kernels and individual devices. So, it was a kind of a hit and miss. I even had it processing for about 10 seconds and suddenly losing it though I have a permissive kernel. But your solution proved to be a success to overcome V4A failing to process when Dolby Atmos was working alright.
BTW, I did notice that this trick works only for one track at a time and when I have to play the next track of a song album, I have to follow these steps all over again. Not a big problem though. But thought of checking with you if the V4A effects could be retained for a session if not until I reboot, say if I am listening to few songs at a stretch after making V4A to process using your trick. But there is no problem with Dolby Atmos though as it can be simply switched on and off whenever I need it. Thanks once again for your fantastic trick.
[*] 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.
[/LIST]
Thanks for this (URL="https://xdaforums.com/showpost.php?p=75262097&postcount=201") excellent trick to make V4A and Dolby Atmos work together in Oreo rom.
This worked for me when I tried it after coming across your post thru' guitardedhero's OP for Dolby Atmos Oreo sound port. In fact, I have been trying to get both Dolby Atmos and V4A working together for about a month. I searched a lot on this issue and I learnt that the success varied from ROMs, Kernels and individual devices. So, it was a kind of a hit and miss. I even had it processing for about 10 seconds and suddenly losing it though I have a permissive kernel. But your solution proved to be a success to overcome V4A failing to process when Dolby Atmos was working alright.
BTW, I did notice that this trick works only for one track at a time and when I have to play the next track of a song album, I have to follow these steps all over again. Not a big problem though. But thought of checking with you if the V4A effects could be retained for a session if not until I reboot, say if I am listening to few songs at a stretch after making V4A to process using your trick. But there is no problem with Dolby Atmos though as it can be simply switched on and off whenever I need it. Thanks once again for your fantastic trick.
[*] 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.[/LIST]
Wolfcity
Recognized Contributor
Really? Are you serious?
Searching/reading seems to be overrated....
Questions been asked multiple times which is why he said search
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
231Release 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
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.
- Instruct an installation directly to /system if a Magisk user prefers a /system installation over the Magisk module installation.
- 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:
- 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.
- Active accommodation of existing and future Magisk modules relevant to audio modification.
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:
Downloads:
- Android File Host (gh)
- Standard:
- Latest: 20180219[*]MD5: eb56b15a2f35bd87e7627652620a98ac
- Standard:
- Android File Host (Zackptg5)
- Unity:
- Latest: 20180220[*]MD5: 16d3397c43bc8ac20fb12f1b637a16cb
- Latest: 20180220[*]MD5: 16d3397c43bc8ac20fb12f1b637a16cb
- Unity:
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.
Credits:
45Release 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.434141Android 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.
- Introduced with Android Nougat, audioserver appears as its own binary after years of being a component of /system/bin/mediaserver in all Android firmware.
:good: - 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.
