I haven't faced any problems in installation of the zip. I installed thru twrp. The module is present on the modules tab on magisk as well as the app in the app drawer. But one there was no effect on the sound output. I have a Lenovo Vibe K5 Plus and using PixelExperience ROM. Also, I don't have any sound mods installed aside from this dolby port.
You have my word that if such an avenue becomes available I will be all over it. It was difficult to describe my philosophy without appearing to be dismissal at the same time and this philosophy is completely absent of any familiarity with the stock experience outside of the audio feature set as well so I certainly understand your preference to avoid it if at all possible.
Your assessment of LineageOS has me intriqued, though. I will see what I can find regarding its utilization of any vendor audio components. I, perhaps irresponsibly, just assumed it was typical CM audio service AudioFX fare. :good:
Did you try powering the app On and Off while adjusting any of the parameters below during audio playback?
Would you be able to provide the audio effects configuration(s) symlinked to the normal locations in /system after boot for me to examine? :good:
I updated my post with an editand no, it is beta. It is too buggy and based on Chinese firmware so there are mistranslations and Chinese words everywhere
Understood. :good:
Yes indeed. ZTE worked with the LOS developers to get audio working like stock and even gave them the Oreo blobs to build lineageOS 15 but cannot release it until ZTE releases their official Oreo release. The DAC and stereo speaker was working as well as a port of the nougat Dolby Atmos version. So most of us had near or equal to stock audio on custom ROMs ranging from lineageOS to resurrection remix to unofficial builds of dirty Unicorn
Sorry of this takes time away from more important things like making this compatible wirh many devices as possible and fixing bugs and errors. I suggest making the axon 7 a low priority. We just can't wait until April if any release is coming. That was only for global, not even for the US variant. But who wouldn't wait either?
if this works for us, then this will work for every 8.1 custom ROM in the duture. Thanks for your help!Still bootlooping on Pixel 2 XL. I looked at the logcat and noticed it kept repeating about waiting on the audio. I attached a logcat of the part where it just started repeating.
Two lines stick out to me:
After disabling the module and rebooting, I looked through the logcat again and saw the "Unsupported target" line again (only once or twice), but the process name for it was blank, whereas it had the fullname "/vendor/bin/hw/android.hardware.audio@2.0-service" when it was looping. It also never gave the "AudioPolicyService not published" warning.
Not sure if either point is important or I'm just chasing after red herrings
Two lines stick out to me:
Code:
01-26 20:01:05.490 2427 2427 E hardware_info: hw_info_init: Unsupported target msm8998-tavil-taimen-snd-card:: /vendor/bin/hw/android.hardware.audio@2.0-service
01-26 20:01:05.964 1243 1557 W AudioSystem: AudioPolicyService not published, waiting...: system_serverAfter disabling the module and rebooting, I looked through the logcat again and saw the "Unsupported target" line again (only once or twice), but the process name for it was blank, whereas it had the fullname "/vendor/bin/hw/android.hardware.audio@2.0-service" when it was looping. It also never gave the "AudioPolicyService not published" warning.
Not sure if either point is important or I'm just chasing after red herrings
Changelog:
Code:[B]20180126-5 -[/B] - Boot scripts restructuring and enhancements targeting successful device boot and additional functionality.
Very interesting report I just observed in a separate thread informing those device owners of this port:
https://xdaforums.com/showpost.php?p=75341915&postcount=50
This log contains the series of events during the installation of 20180126-4, the version immediately before changes addressing bootloop issues and functionality issues.
However, the log shows nothing that would make one conclude a successful device boot would not result.
Nonetheless, please try again with 20180126-6. :good:
You know, you just reminded me of something...
Ever since upgrading to Oreo, and possibly even before that, I have found it not too uncommon to experience a bootloop at times that was immediately resolved by a press of the power button until a forced reboot began, at which time the device would almost always successfully boot immediately. This literally happened mere hours ago as well.
This may be unique to OnePlus 5, but either way...
If experiencing a bootloop...
DO NOT GIVE UP!!
Hold down the device Power button until a reboot is initiated... and then give up if a successful boot fails to occur lol. :good:
Last edited:
I find that procedure only occurs on magisk and only fixes it when stuck on the bootloader for me.
Sent from my LG Nexus 5X using XDA Labs
wow...it was actually , i tested with -4 and the latest -6, and yes uninstalling busybox made the dolby effects work
here's few things thoguh, 1st from v4 from last night, the compatibility issue with other modules is now seems fixed on v6 , and while testing on v4 it seemed to me that it had a mind of it's own, it wasn't a spicific module , it was just sometime the app showed and the files were placed and sometime they weren't.
also the prop file on v4 still doesn't affect the flashing it just flashes the magisk module if it detects magisk, but i noticed that (that's only tested on v4) if i set install to system to true, the module worked every time (given all other modules were disabled) , if prop file is not there at all or without value, sometime files were placed other times it didn't
as you said the power button doesn't seem to be working visually, but it does when pressed turn on/off dolby... that said, it did visually work for me , here's how, press the turn off button and then close the dolby app window, then open it again ...it will be off and will be turned on when pressed.
lastly about the boot loop, you're right, some of(most of) were fixed by just shutting down the device and turning it on again, but the loop on v6 seems strange (when it happened) at 1st the screen kept turning off (the lights went off) and then on again ...also the 2nd time after i shut the device down, it went all the way to the home screen and after 5 sec or so it rebooted ...it didn't occur again though, so far on v6 all seems to be working fine as a Magisk Module,
The one Module it had issues with for sure on v4 was the iytbp module (modded youtube) , that was the only module that if it was enabled dolby didn't show up...but on v6 this seems to be fixed ...
sorry for the long post, and thank you for the great work.
Edit/ if you need any file or log please let me know.
Last edited:
Dear developer, would be glad to test Your work. Im on Axon 7 Oreo (8.1) PNW. When i trie to add the zip as module in Magisk it always says: No magisk modul, no other hint. In Recovery (trwp) installing starts, says Installing..., then nothing happens. Why does magisk Your zip-file not recognize as magisk-modul? Would be so glad, if it would be installable. In the prop-file i set magisk systemm install an aditional lybrary as true. Help would be kind. And thanks for investing time an brain for our welfare.
Hansjörg
Copying zip to temp directory
! This zip is not a Magisk Module
Last edited:
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.
