It worked
Many many many many many thanks @guitardedhero
---------- Post added at 02:45 PM ---------- Previous post was at 02:44 PM ----------
By the way what was the problem in previous builds
I mean what you did in this build as compared to previous builds
Hey dude this worked for me. On the first boot it bootlooped, then on force restart it booted right into the rom and voila it ali works. What magic was this?
Great stuff thanks man
Last edited:
I have sometimes after recovery one time bootloop. I do force restart too. I dont know why.
OMG!
You realize how long I've waited to see this particular post from you?!
Of course you do lol. :highfive:
Both Dolby and V4a can work simultaneously and its so awesome. But there is a catch, every time you have to start V4a first and make sure its processing than Dolby later.
Again, Dolby wouldn't show any changes at the first switch on button but all the GUI will come to alive only after you hit the home button and again open Dolby.
Hmm, are you using the latest unity dolby build? If so, can you remove the service.sh script in the magsik/dolby directory and see if that fixes the issue?
HTC U11, magisk 15.3
Installed successfully but not processing.
It works for me without any issue.
THX!
What other Magisk modules are installed? Please provide /vendor/etc/audio_effects.xml. :good:
In my case Dolby and Viper work without any conflict too. I run Viper first too. Becouse need give permission for it. But i use one audio_effects.conf file one for both.
Pls find attachments below
Attachments
bootloop on standard and unity build
also tried wiping cache before and after and with and without magisk.system.install=true
OnePlus 3T, LiquidRemix 8.1, Magisk 15.3
Sent from my OnePlus 3T using XDA Labs
The lastest zip installs :good: but Dolby forces closes.
Sent from my Google Pixel 2 using XDA Labs
Sent from my Google Pixel 2 using XDA Labs
Installation failed:
Bootloop
Rom aicp_zl1_o-13.1-WEEKLY-20180207 for Leeco X720
twrp-3.2.1-0-20180108-codeworkx-zl1
SELinux Enforcing
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.
