Bounty - Pixel 2/2 XL Dolby on Pie - Google Pixel 2 XL Themes, Apps, and Mods

Offering $200 for fully functional Dolby magisk module that runs with the magisk viper module and, if necessary, the audio modifications magisk module. Must be completely compatible with the Pixel 2 and Pixel 2 XL running 9.x.
I will pay bounty upon 5 users testing the module independently for a period of two weeks. If after the two weeks 5 users report success, I'll arrange payment with the mod's author.

---

I've completely gave up on getting Dolby running on mine. Oreo was a nightmare trying to get Atmos up and running with the exact same setup as my 6P. Just bootloops after bootloops. ?
Since we're on the topic of audio for the Pixel 2 XL... A question for those who use Viper+Audio Compatibility Patch.
Might be a little hard to explain, might upload a video of it, but do you guys get audio skipping when playing from 2 different sources? Let's say you're playing music and a video plays in the browser, instead of pausing your music and the video playing right away, you get this crazy skipping noise for a couple seconds, then the video plays and vice versa when going back to your music.
Unsure if any other Pixel 2 XL user experienced this.

---

@guitardedhero

---

Curiousn00b said:
I've completely gave up on getting Dolby running on mine. Oreo was a nightmare trying to get Atmos up and running with the exact same setup as my 6P. Just bootloops after bootloops. ?
Since we're on the topic of audio for the Pixel 2 XL... A question for those who use Viper+Audio Compatibility Patch.
Might be a little hard to explain, might upload a video of it, but do you guys get audio skipping when playing from 2 different sources? Let's say you're playing music and a video plays in the browser, instead of pausing your music and the video playing right away, you get this crazy skipping noise for a couple seconds, then the video plays and vice versa when going back to your music.
Unsure if any other Pixel 2 XL user experienced this.
Click to expand...
Click to collapse
Same thing

---

@Zackptg5

---

There's no stock pie firmwares with dolby yet that I'm aware of so I looked through several stock oreo firmwares other than zte axon 7 (current dolby oreo port). Here's what I found:
Razer - uses goofy boot img and vendor service stuff - would be a pain to port and would need to be installed to system due to dependency on rc files (so no magisk module for this). I tried porting this several months ago but couldn't get it working
Lg G6 - Dolby Vision app present but no sign of atmos (perhaps built into system settings or something), didn't look much further
Samsung Galaxy S9/9+ - built into settings app - not worth porting at this point
HTC U11/U12 - built into settings app and rebranded as BoomSound - same as S9/9+
Long story short, there's no dolby atmos for pie yet and I'm not seeing any other readily portable dolby atmos apps in any other stock firmware. It'd be cool if someone had the time to figure this out but I don't (and won't for a while). Sorry :/

---

madscribblerz said:
Offering $200 for fully functional Dolby Atmos magisk module that runs with the magisk viper module and, if necessary, the audio modifications magisk module. Must be completely compatible with the Pixel 2 and Pixel 2 XL running 9.x.
I will pay bounty upon 5 users testing the module independently for a period of two weeks. If after the two weeks 5 users report success, I'll arrange payment with the mod's author.
Click to expand...
Click to collapse
Deleted

---

madscribblerz said:
Offering $200 for fully functional Dolby Atmos magisk module that runs with the magisk viper module and, if necessary, the audio modifications magisk module. Must be completely compatible with the Pixel 2 and Pixel 2 XL running 9.x.
I will pay bounty upon 5 users testing the module independently for a period of two weeks. If after the two weeks 5 users report success, I'll arrange payment with the mod's author.
Click to expand...
Click to collapse
Sir, this is not mine, but i just want you to test, since it's working on my Mi Mix running Pie rom.
Download this Dolby Digital Plus : https://drive.google.com/file/d/1fp9rigCIxiC9QUFYAY0RUtHCaIJ6gOJY/view
Flash it in Magisk Manager, but don't reboot it yet.
After flash that file, immediately flash this : https://zackptg5.com/downloads/Audio-Modification-Library_v1.8.1.zip
And after that flash this : https://zackptg5.com/downloads/acp_v1.4.9.zip
And then exit the Magisk Manager and reboot.
Finger crossed..
For more information, my device is Mi Mix running LOS 16 (Pie) on Magisk 17.1.

---

heindrix said:
Sir, this is not mine, but i just want you to test, since it's working on my Mi Mix running Pie rom.
Download this Dolby Digital Plus : https://drive.google.com/file/d/1fp9rigCIxiC9QUFYAY0RUtHCaIJ6gOJY/view
Flash it in Magisk Manager, but don't reboot it yet.
After flash that file, immediately flash this : https://zackptg5.com/downloads/Audio-Modification-Library_v1.8.1.zip
And after that flash this : https://zackptg5.com/downloads/acp_v1.4.9.zip
And then exit the Magisk Manager and reboot.
Finger crossed..
For more information, my device is Mi Mix running LOS 16 (Pie) on Magisk 17.1.
Click to expand...
Click to collapse
All installs as you would expect but dolby app still FC's on launch.

---

madscribblerz said:
All installs as you would expect but dolby app still FC's on launch.
Click to expand...
Click to collapse
Hi there,
I'm not an expert, but there are several things to check :
* check "ds1-default.xml" file existing in /system/etc
* check "dolby.sh" file existing in /system/etc/init.d
* check "libstagefright_soft_ddpdec.so" file existing in /system/lib
* check "libdseffect.so" file existing in /system/lib/soundfx
* check "Dsplus.apk" file existing in /system/priv-app/Dsplus
* check in /system/etc/audio_effects.conf under "libraries {" line, for line :
ds {
path /system/lib/soundfx/libdseffect.so
}
* check in /system/etc/audio_effects.conf under "effects {" line, for line :
dsplus {
library ds
uuid 9d4921da-8225-4f29-aefa-39537a04bcaa
}
* check in /vendor/etc/audio_effects.xml under "<libraries>" line, for line :
<library name="ds" path="libdseffect.so"/>
* check in /vendor/etc/audio_effects.xml under "<effects>" line, for line :
<effect name="dsplus" library="ds" uuid="9d4921da-8225-4f29-aefa-39537a04bcaa"/>
* check if your init.d is activated or not, it should be activated

---

heindrix said:
Hi there,
I'm not an expert, but there are several things to check :
* check "ds1-default.xml" file existing in /system/etc
* check "dolby.sh" file existing in /system/etc/init.d
* check "libstagefright_soft_ddpdec.so" file existing in /system/lib
* check "libdseffect.so" file existing in /system/lib/soundfx
* check "Dsplus.apk" file existing in /system/priv-app/Dsplus
* check in /system/etc/audio_effects.conf under "libraries {" line, for line :
ds {
path /system/lib/soundfx/libdseffect.so
}
* check in /system/etc/audio_effects.conf under "effects {" line, for line :
dsplus {
library ds
uuid 9d4921da-8225-4f29-aefa-39537a04bcaa
}
* check in /vendor/etc/audio_effects.xml under "<libraries>" line, for line :
<library name="ds" path="libdseffect.so"/>
* check in /vendor/etc/audio_effects.xml under "<effects>" line, for line :
<effect name="dsplus" library="ds" uuid="9d4921da-8225-4f29-aefa-39537a04bcaa"/>
* check if your init.d is activated or not, it should be activated
Click to expand...
Click to collapse
I'm no expert either - but all that looks to be in order.
I tried it with and without magisk permissive, init.d, and compatibility modules.
Is there a log somewhere that might lend more insight?
Also - here is Dolby"s devoper documentation.
It will be funny if I win my own bounty.
https://developer.dolby.com/platforms/google/android/dolby-audio/overview/

---

madscribblerz said:
I'm no expert either - but all that looks to be in order.
I tried it with and without magisk permissive, init.d, and compatibility modules.
Is there a log somewhere that might lend more insight?
Click to expand...
Click to collapse
Okay, several things that i did and i know :
* about SELinux, this module can be running either in Permissive and Enforcing on my device
* on my device, i'm using Magisk 17.1
* for init.d, i use Kernel Adiutor https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor to activate it, there's a menu for activate it in that app
* Audio Compatibility Patch is just optional, i think it wouldn't make any difference if you flashed it
* but, Audio Modification Library is a must. there's a hint, if the Dolby flashed successfully, when you flash Audio Modification Library, you can see it detect Dolby in its install message, on my experience, if it doesn't not detect Dolby, i have to uninstall and reboot and reflash everything again (Dolby and Audio Modification Library) until Audio Modification Library detect Dolby
* keep in mind, i don't know why, in Pie, i have to flash Audio Modification Library immediately after i flash Dolby, not after reboot (or maybe that's the right order i don't know lol)
* maybe some logs can help you to identify what's wrong, i ussually use this : https://play.google.com/store/apps/details?id=com.pluscubed.matlog , it's quite good

---

heindrix said:
Okay, several things that i did and i know :
* about SELinux, this module can be running either in Permissive and Enforcing on my device
* on my device, i'm using Magisk 17.1
* for init.d, i use Kernel Adiutor https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor to activate it, there's a menu for activate it in that app
* Audio Compatibility Patch is just optional, i think it wouldn't make any difference if you flashed it
* but, Audio Modification Library is a must. there's a hint, if the Dolby flashed successfully, when you flash Audio Modification Library, you can see it detect Dolby in its install message, on my experience, if it doesn't not detect Dolby, i have to uninstall and reboot and reflash everything again (Dolby and Audio Modification Library) until Audio Modification Library detect Dolby
* keep in mind, i don't know why, in Pie, i have to flash Audio Modification Library immediately after i flash Dolby, not after reboot (or maybe that's the right order i don't know lol)
* maybe some logs can help you to identify what's wrong, i ussually use this : https://play.google.com/store/apps/details?id=com.pluscubed.matlog , it's quite good
Click to expand...
Click to collapse
So frustrating. Duplicated your setup, and know the init.d is running. Everything checks out.
I am getting an error in logcat starting up the effects though - there us a uuid that it references that I can't find in audio_conf in either system or vendor. I'll post the logs once I'm someplace where I can.
Also, to clarify, the bounty is not for atmos specifically - I didn't know about the Dolby flavors then. Dolby is fine, not specifically atmos.
Any other ideas?

---

madscribblerz said:
So frustrating. Duplicated your setup, and know the init.d is running. Everything checks out.
I am getting an error in logcat starting up the effects though - there us a uuid that it references that I can't find in audio_conf in either system or vendor. I'll post the logs once I'm someplace where I can.
Also, to clarify, the bounty is not for atmos specifically - I didn't know about the Dolby flavors then. Dolby is fine, not specifically atmos.
Any other ideas?
Click to expand...
Click to collapse
I'm not looking for the bounty, just want to help, besides, that Dolby isn't my works, i just happen to know a bit and wants to help.
It's specifically Dolby Digital Plus.
And yes, logs will help, either logcat and dmesg.

---

heindrix said:
I'm not looking for the bounty, just want to help, besides, that Dolby isn't my works, i just happen to know a bit and wants to help.
It's specifically Dolby Digital Plus.
And yes, logs will help, either logcat and dmesg.
Click to expand...
Click to collapse
I really appreciate the help. I'm pretty technical but don't know how this stuff is supposed to work so your help is very welcome. Even if you aren't after the bounty I put it up and I will pay it happily - so if it works out such, you can consider it a thank you gift.
Here are logs. Install log shows the audio mod module picking up Dolby, second is a warn/error log when launching the Dolby app.
Thoughts?
- Copying zip to temp directory - Installing Audio-Modification-Library_v1.8.1.zip cat: write error: Broken pipe cat: write error: Broken pipe cat: write error: Broken pipe - Current boot slot: _a - Mounting /system, /vendor Archive: /data/user/0/com.topjohnwu.magisk/cache/install.zip creating: common/ inflating: common/aml.sh inflating: common/AudioModificationLibrary.sh inflating: common/post-fs-data.sh inflating: common/service.sh inflating: common/system.prop creating: META-INF/ creating: META-INF/com/ creating: META-INF/com/google/ creating: META-INF/com/google/android/ inflating: META-INF/com/google/android/update-binary inflating: META-INF/com/google/android/updater-script creating: system/ inflating: system/placeholder inflating: config.sh inflating: module.prop inflating: README.md ******************************* Audio Modification Library (Zackptg5, Ahrion) ******************************* ****************************** Powered by Magisk (@topjohnwu) ****************************** - Found /data/adb/magisk_merge.img e2fsck 1.43.3 (04-Sep-2016) - Mount /data/adb/magisk_merge.img to /dev/tmp/magisk_img - Installing Audio Modification Library Searching for supported audio mods... Found V4AFX! Patching... Found Dolby Digital Plus! Patching... - Setting permissions - All done!

---

madscribblerz said:
I really appreciate the help. I'm pretty technical but don't know how this stuff is supposed to work so your help is very welcome. Even if you aren't after the bounty I put it up and I will pay it happily - so if it works out such, you can consider it a thank you gift.
Here are logs. Install log shows the audio mod module picking up Dolby, second is a warn/error log when launching the Dolby app.
Thoughts?
- Copying zip to temp directory - Installing Audio-Modification-Library_v1.8.1.zip cat: write error: Broken pipe cat: write error: Broken pipe cat: write error: Broken pipe - Current boot slot: _a - Mounting /system, /vendor Archive: /data/user/0/com.topjohnwu.magisk/cache/install.zip creating: common/ inflating: common/aml.sh inflating: common/AudioModificationLibrary.sh inflating: common/post-fs-data.sh inflating: common/service.sh inflating: common/system.prop creating: META-INF/ creating: META-INF/com/ creating: META-INF/com/google/ creating: META-INF/com/google/android/ inflating: META-INF/com/google/android/update-binary inflating: META-INF/com/google/android/updater-script creating: system/ inflating: system/placeholder inflating: config.sh inflating: module.prop inflating: README.md ******************************* Audio Modification Library (Zackptg5, Ahrion) ******************************* ****************************** Powered by Magisk (@topjohnwu) ****************************** - Found /data/adb/magisk_merge.img e2fsck 1.43.3 (04-Sep-2016) - Mount /data/adb/magisk_merge.img to /dev/tmp/magisk_img - Installing Audio Modification Library Searching for supported audio mods... Found V4AFX! Patching... Found Dolby Digital Plus! Patching... - Setting permissions - All done!
Click to expand...
Click to collapse
Okay, i got a little bit hint in that logs, but not too sure.
Could you share your audio_effects.conf/xml that located in both system/etc and vendor/etc?

---

Here ya go

---

madscribblerz said:
Here ya go
Click to expand...
Click to collapse
Hi there,
I will assume you are already expert in this things, so, several things to do and test :
* before doing this, please keep in mind this is high risk and might causing bootloop, please and please backup your data
* backup the original audio_effects.conf and audio_effects.xml
* download the file i attached, extract it, replace audio_effects.conf and audio_effects.xml in your device with that extract one, don't forget to set the permissions to 0644
* please check in /vendor/lib/soundfx if file libeffectproxy.so is persist
* please check in /vendor/lib/soundfx if file libvisualizer.so is persist
* please check in /vendor/lib/soundfx if file libqcomvisualizer.so is persist
* please check in /system/lib/soundfx if file libdseffect.so is persist
* please check in /vendor/lib/soundfx if file libv4a_fx_ics.so is persist
* reboot device
Because i haven't fully understand how Magisk Mount works, there's a chance that audio_effects files that you've replaced, might replaced by Magisk Mount, so the code i modify inside those two files might disappear. If that really happen, i'll figure out later after you give me feedback and logs if it's not working.
You can compare the two audio_effects files i modified with the original one to get to what i've done.
Finger crossed!

---

madscribblerz said:
I really appreciate the help. I'm pretty technical but don't know how this stuff is supposed to work so your help is very welcome. Even if you aren't after the bounty I put it up and I will pay it happily - so if it works out such, you can consider it a thank you gift.
Here are logs. Install log shows the audio mod module picking up Dolby, second is a warn/error log when launching the Dolby app.
Thoughts?
- Copying zip to temp directory - Installing Audio-Modification-Library_v1.8.1.zip cat: write error: Broken pipe cat: write error: Broken pipe cat: write error: Broken pipe - Current boot slot: _a - Mounting /system, /vendor Archive: /data/user/0/com.topjohnwu.magisk/cache/install.zip creating: common/ inflating: common/aml.sh inflating: common/AudioModificationLibrary.sh inflating: common/post-fs-data.sh inflating: common/service.sh inflating: common/system.prop creating: META-INF/ creating: META-INF/com/ creating: META-INF/com/google/ creating: META-INF/com/google/android/ inflating: META-INF/com/google/android/update-binary inflating: META-INF/com/google/android/updater-script creating: system/ inflating: system/placeholder inflating: config.sh inflating: module.prop inflating: README.md ******************************* Audio Modification Library (Zackptg5, Ahrion) ******************************* ****************************** Powered by Magisk (@topjohnwu) ****************************** - Found /data/adb/magisk_merge.img e2fsck 1.43.3 (04-Sep-2016) - Mount /data/adb/magisk_merge.img to /dev/tmp/magisk_img - Installing Audio Modification Library Searching for supported audio mods... Found V4AFX! Patching... Found Dolby Digital Plus! Patching... - Setting permissions - All done!
Click to expand...
Click to collapse
Try this module.
Same install method
Viper, reboot
Dolby, reboot
AML, reboot
try it out.
small changer in audio_effects.xml based on your log that may or may not work. I'm going back an forth from 8.1 to 9.0 to get this working just little time presently. Let us know. :fingers-crossed:

---

matt1313 said:
Try this module.
Same install method
Viper, reboot
Dolby, reboot
AML, reboot
try it out.
small changer in audio_effects.xml based on your log that may or may not work. I'm going back an forth from 8.1 to 9.0 to get this working just little time presently. Let us know. :fingers-crossed:
Click to expand...
Click to collapse
wow man.
the audio_effects.xml code looks same the one i posted above, so we both come to the same solution?