yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL Guides, News, & Discussion] vibrantliker:
My current rom won't allow Dolby to work for some reason. Rather than switch roms, I'm using the Viper4Android XHiFi magisk module (along side V4A) and setting eq on Bass boost preset.

May not be for everybody but sounds good on my phone (OP6).
[Google Pixel 2 XL Guides, News, & Discussion] madscribblerz:
Thanks for the tip. Setup XHiFi and it does sound better. I'm also using the convolvers badger linked earlier in the thread (beats/Harmon Kardon) and it pretty much rivals Dolby. What I liked about Dolby is the dynamic shaping of the bass though. It always shifted bass into my subwoofers sweet spot in my car.

Hopefully someone figures it out...maybe I'll give it a go if I find time.

I heard pie was going to bring viper like functionality at one point. Anyone know what's up with that?
[Google Pixel 2 XL Guides, News, & Discussion] madscribblerz:
Dunno if this will motivate anyone, but I'll offer a $200 bounty for a working Dolby with pie on pixel 2 xl.

https://xdaforums.com/pixel-2-xl/themes/bounty-pixel-2-2-xl-dolby-pie-t3839900
[Google Pixel 2 XL Guides, News, & Discussion] matt1313:
Man where were you in December of 2017.... I'm working on it more today fyi, not giving up so easily
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
I'll be one of your testers so that you may take his money! ???
[Google Pixel 2 XL Guides, News, & Discussion] madscribblerz:
Hehe, installed Dolby for the first time off your distro, fell in love with it. Like a drug right? First one's free, but if you like it, the rest ain't.

I'm addicted.

Seriously, I want to show my appreciation for your efforts. I've fought with viper since my nexus and have a layman's understanding of the audio stack - and know it isn't easy standing this up. So thank you. I appreciate what you're doing. :)
[Google Pixel 2 XL Guides, News, & Discussion] matt1313:
I think we need to wait for a system dump of Dolby from a phone running Pie. Audioserver is the issue
[Google Pixel 2 XL Guides, News, & Discussion] madscribblerz:
OK, bounty still stands. When we can, we can.
[Google Pixel 2 XL Guides, News, & Discussion] ossito2012:
Has anyone tried using this command. After you have Dolby installed and it FCs run this in terminal.

su -c killall audioserver

or in adb

adb shell killall audioserver

Read more about it... https://xdaforums.com/showpost.php?p=75542271&postcount=891

More info about audio mapping and audioserver https://source.android.com/devices/audio/aaudio I don't quite understand it but maybe it might trigger brainstorming session.

I am still on Oreo so I can not try.
[Google Pixel 2 XL Guides, News, & Discussion] matt1313:
I will try this weekend and report back unless someone trys first.
[Google Pixel 2 XL Guides, News, & Discussion] ossito2012:
Oh No, please know that I was not meaning to put on your plate, appreciate all you have done sir, it was more of a general idea for all of us, I am going to upgrade from Oreo to Pie this weekend, so I can tinker too.
[Google Pixel 2 XL Guides, News, & Discussion] matt1313:
Lol no worries man, this is a community for sharing and helping each other, at least that's how I look at it. The more people helping, supporting positively and encouraging the better in my eyes.

Good find and thought behind your post. I hope it works as audio server is the issue from what I see.
[Google Pixel 2 XL Guides, News, & Discussion] Dragostini:
https://www.reddit.com/r/androidroot/comments/95yoiu/viper4android/

Already works on Pie.

Can confirm, running stock rom, pixel XL 2, rooted using P2XL AIO Toolkit, Magisk 16.7.

No Dolby, but doesn't matter to me, I just wanted Viper.
[Google Pixel 2 XL Guides, News, & Discussion] Reechings:
Viper working on Pie isn't what's being worked on but I agree that it's nice to have.
[Google Pixel 2 XL Guides, News, & Discussion] epm90:
Using su - c killall audioserver let's Dolby open on Pie but it kills all sound as soon as you toggle it for spotify and YouTube. I will try pulling a log for you later
[Google Pixel 2 XL Guides, News, & Discussion] hp13:
Will this work on Google Pixel 8.1? I couldn't get other mods to work unfortunately. I'm curious to try this.
[Google Pixel 2 XL Guides, News, & Discussion] matt1313:
Yes
[Google Pixel 2 XL Guides, News, & Discussion] ossito2012:
I read this article where Google was limiting even more apps having access to processes, namely cameraserver, mediaserver, and audioserver. Audioserver is what we our interested in since it deals with audio drivers. I think in Oreo they clamped down on cameraserver and now in Pie they have clamped down on Audioserver. I am sure if someone can find a way to access permissions to audioserver processes Dolby will work again.

---------- Post added at 06:37 AM ---------- Previous post was at 06:29 AM ----------

Found this post https://xdaforums.com/showpost.php?p=75460774&postcount=376

[MENTION=4445176]guitardedhero[/MENTION] I figured out how I got it to work and what may be causing bootloops for some devices. At least on the zip I tried which is 20180129-1, I set install.add.libraries to true in arise_parameters.prop and flashes fine in TWRP (unlike more recent and past versions) but then met with a bootloop. I deleted the audioserver file in /system/bin in TWRP with file manager, and then took out the audioserver file from the zip and moved it to my micro sd card, and used these commands in Terminal to move it to /system/bin.

cd external_sd

cp audioserver /system/bin && chmod 655 audioserver

once that is done, I rebooted, and it worked. I just tried this exact same thing with my brother's Axon 7. Flashing is fine, but met with bootloop. Doing the above makes Dolby Atmos work 100%

I think something happens when your zip tries to move the audioserver file. At least maybe on certain devices.
[Google Pixel 2 XL Guides, News, & Discussion] guitardedhero:
I appreciate the effort trying to get Oreo's Atmos working on Pie. :good:

Your commands seem to achieve something entirely different than your intent, however.

I haven't tested your commands as I am currently running some audio stuff other than Atmos on Pie at the moment, but this is what I see happening with your commands presented - assuming /external_sd/audioserver exists:

cd external_sd ( change directory from / to /external_sd )

cp audioserver /system/bin ( copy /external_sd/audioserver as /system/bin - audioserver file named "bin" next to the folder also in /system )

&& chmod 655 audioserver ( once the copy operation from earlier completes, change permissions of /external_sd/audioserver to 0655 )

The last command is impossible due to Android storage attribute restrictions and the result of your "present working directory" pwd being /external_sd.

To properly test your scenario, I suggest the following commands - assuming /external_sd/audioserver exists:

[B]su[/B]

[B]mount -o rw,remount /system[/B]

[B]mv -f /system/bin/audioserver /system/bin/audioserver.original && chmod 0644 /system/bin/audioserver.original[/B]

[B]cp -f /external_sd/audioserver /system/bin/audioserver[/B]

[B]chmod 0655 /system/bin/audioserver[/B]

[B]chown 0.2000 /system/bin/audioserver[/B]

[B]chcon u:object_r:audioserver_exec:s0 /system/bin/audioserver[/B]

[B]umount /system && reboot[/B]

This is the full audioserver installation, but with your specific chmod value.

A bootloop will likely result, in which case, /system/bin/audioserver.original can simply be renamed to /system/bin/audioserver once the bootloop-causing audioserver had been deleted, then simply chmod 0755 /system/bin/audioserver.

I do not doubt your reported success, it is just a result of something other than what is being claimed - essentially, the existing /system/bin/audioserver is untouched while the audioserver of interest is a file named /system/bin right above /system/build.prop.

With this insight, see what you can find that is responsible for your success. :good:
[Google Pixel 2 XL Guides, News, & Discussion] ossito2012:
Oh dang, sorry I did not mean to message you, I did not notice the @ sign in front of your name. I was posting some general info you reached with another device so that "others" could see.

I appreciate your input on the matter.
[Google Pixel 2 XL Guides, News, & Discussion] matt1313:
[MENTION=4445176]guitardedhero[/MENTION] thank you for this!!!

I originally tried this exact process on pie and got boot loop. If anyone does get it working with this let us know.

As I have mentioned before we need a working STOCK Dolby on Pie or as guitardedhero mentioned need to get the permissions worked out in the audioserver.

I feel confident we will get there.
[Google Pixel 2 XL Guides, News, & Discussion] hp13:
yes finally worked!! great work mate :)

I followed exact same steps. I haven't installed the Audio Competibility Mod yet. I am not sure if thats necessary. I did see the driver settings changed to processing when playing music through spotify. I will hold on to it for now.

[MENTION=2988397]matt1313[/MENTION] is there a way to get Dolby Atmos? Have you had any luck?

Thanks again Dev.
[Google Pixel 2 XL Guides, News, & Discussion] sinha02:
Hope we will have luck with Dolby very soon, thanks dev
[Google Pixel 2 XL Guides, News, & Discussion] matt1313:
Once there is an official Dolby Pie release we will do our best to Port it.
[Google Pixel 2 XL Guides, News, & Discussion] heindrix:
Hi guys,

Sorry for bring up old things,

But doesn't it the context for audioserver should be 0755?

So :

[B]su[/B]

[B]mount -o rw,remount /system[/B]

[B]mv -f /system/bin/audioserver /system/bin/audioserver.original && chmod 0644 /system/bin/audioserver.original[/B]

[B]cp -f /external_sd/audioserver /system/bin/audioserver[/B]

[B]chmod [COLOR="Red"]0755[/COLOR] /system/bin/audioserver[/B]

[B]chown 0.2000 /system/bin/audioserver[/B]

[B]chcon u:object_r:audioserver_exec:s0 /system/bin/audioserver[/B]

[B]umount /system && reboot[/B]

well anyway, just clarified little things there.

still nothing's worked through.

should wait for first pie stock rom with dolby.
[Google Pixel 2 XL Guides, News, & Discussion] DevALT:
Anyone tried with magisk 18.0?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
https://xdaforums.com/pixel-2-xl/themes/bounty-pixel-2-2-xl-dolby-pie-t3839900/post78392845. :cool:
[Google Pixel 2 XL Guides, News, & Discussion] Joloxx9:
I w never used bootable twrp to flash add ona. Anyway after 3th flash it worked
[Google Pixel 2 XL Guides, News, & Discussion] Ajmal Bma:
Install twrp or magisk

Tell me
[Google Pixel 2 XL Guides, News, & Discussion] matt1313:
Both
[Google Pixel 2 XL Guides, News, & Discussion] mikepopo99:
You dont have to install twrp you can just boot to twrp then flash everything.
[Google Pixel 2 XL Guides, News, & Discussion] otonieru:
That will cause a problem with dolby force closing later

Happened to me,

Fixed by installing TWRP
[Google Pixel 2 XL Guides, News, & Discussion] Ajmal Bma:
What both

I already installed twrp and magisk

Dolby Atmos install method

Tell me

Twrp or magisk
[Google Pixel 2 XL Guides, News, & Discussion] matt1313:
Mis understood your question.

Install Dolby through twrp as stated in op.
[Google Pixel 2 XL Guides, News, & Discussion] sharpz811:
A please and thank you wouldn't been nice.

Why would you even help this dude he's not even asking he's demanding
[Google Pixel 2 XL Guides, News, & Discussion] kburtonjr04:
Having same issue
[Google Pixel 2 XL Guides, News, & Discussion] Trupen:
Can I get link of Dolby zip which you have flashed it is there showing as module in your magisk

I have flashed a Dolby zip but it's not showing as a module in magisk
[Google Pixel 2 XL Guides, News, & Discussion] matt1313:
This is the one I use

https://xdaforums.com/android/software/r-s-e-sound-systems-auditory-research-t3379709/post74901736
[Google Pixel 2 XL Guides, News, & Discussion] Golf c:
It's in the OP
[Google Pixel 2 XL Guides, News, & Discussion] Trupen:
Flashed the zip but it keeps loading
[Google Pixel 2 XL Guides, News, & Discussion] matt1313:
Try putting it in /sdcard only

Did you follow op?
[Google Pixel 2 XL Guides, News, & Discussion] damngood98:
OP states it should be downloaded from a PC in case you missed that
[Google Pixel 2 XL Guides, News, & Discussion] Haz3:
Or you can select desktop site in chrome and it's works the same?
[Google Pixel 2 XL Guides, News, & Discussion] Trupen:
Flashed from phone itself working great apk is also there working with viper, but still it's not showing any module loaded in magisk

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

Now as uall suggested to download from pc then flash so the apk which is installed currently how to uninstall it is there any uninstaller zip for Dolby or dirty flashing the rom
[Google Pixel 2 XL Guides, News, & Discussion] Trupen:
Downloaded from pc then flashed still facing same issue never ending loading screen
[Google Pixel 2 XL Guides, News, & Discussion] Trupen:
What this means
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Looks like you need root to me.
[Google Pixel 2 XL Guides, News, & Discussion] Felosis:
Dolby FCs

I think I figured out why some folks are getting FCs upon launching Dolby. I spent some time ruling out different things and came to the conclusion that you have to have dtbo patched for it to work properly. When I upgraded to the latest Magisk, which of course does not patch dtbo anymore and preserves avb2.0, I started getting FCs. I tried a few different things at first and then it hit me... Patch the dtbo and boom Dolby working perfect.

I'll quote what I've read many times, and I agree... I patch dtbo and wear my badge! :)

Honestly at the end of the day, I unlock and root for a reason so... I unlock boot/critical, patch dtbo (NOT preserving force encryption or avb), disable Play Protect and even run SELinux permissive. lol, if I get malware or corrupt something, it's my fault and I'll just start clean if I mess up. With this, I never have any problems with everything just always working, including my bank apps and Android Pay.
[Google Pixel 2 XL Guides, News, & Discussion] CyberpodS2:
January update, no error message on boot and Dolby is working as best I can tell without error. Not sure what night be different...
[Google Pixel 2 XL Guides, News, & Discussion] Felosis:
Hmm, weird, I have no idea then. What version of the MagiskManager do you have installed?
[Google Pixel 2 XL Guides, News, & Discussion] CyberpodS2:
5.5.4
[Google Pixel 2 XL Guides, News, & Discussion] Golf c:
Dolby is working fine for me without patching Dtbo because I am permissive SElinux. It's either one or the other or both. On Magisk 15.2 I was SElinux enforcing and AVB verity disabled. Dolby worked fine.
[Google Pixel 2 XL Guides, News, & Discussion] Felosis:
Interesting, thanks for the replies. Mine quit working after I upgraded to MM 5.5.4 and once I patch dtbo without preserving either, it starting working. I even tried twice by reflashing Flash 2.09 and Magisk 15.3 again in TWRP (3.2.1-0) and it FC again until dtbo patch.

lol, oh well, I'm glad it works for you guys without! :) I'm not worried as I don't mind patching my dtbo as the message doesn't bother me. At least if someone else is having FCs like me, this might be worth a try.

Thanks!
[Google Pixel 2 XL Guides, News, & Discussion] CyberpodS2:
I too am permissive, maybe that's the ticket...
[Google Pixel 2 XL Guides, News, & Discussion] Golf c:
Either one or both
[Google Pixel 2 XL Guides, News, & Discussion] sharpz811:
Thanks so much for this I missed Viper so much and yes audiophile x profile is blessed my car speakers sound so much better via Bluetooth!
[Google Pixel 2 XL Guides, News, & Discussion] Felosis:
Still interesting, I too am permissive. To add more, the new Magisk 5.5.5 was released yesterday so I went through the process twice again and still same result, FC on Dolby unless I patched my dtbo. I did a clean flash of Flash 2.09 and Magisk in TWRP as well, preserving both encryption and avb, had FC then patched dtbo and boom works. haha, oh well, maybe something else I'm doing or have installed makes the difference, but I don't mind patching dtbo and clicking ok on startup as I don't reboot my phone really ever. :)

Thanks again for sharing your setups. :)
[Google Pixel 2 XL Guides, News, & Discussion] Golf c:
Strange, I ran without patching dtbo for awhile. I'm patched and permissive at the moment.
[Google Pixel 2 XL Guides, News, & Discussion] vibrantliker:
getting error 2 trying to flash Dolby
[Google Pixel 2 XL Guides, News, & Discussion] otonieru:
Redownload the zip using PC or using download manager app from phone
[Google Pixel 2 XL Guides, News, & Discussion] vibrantliker:
The version I flashed was downloaded to my pc first then copied to phone. I did try flashing twice.
[Google Pixel 2 XL Guides, News, & Discussion] stalls:
Make sure it's at the base of your SD card... /sdcard
[Google Pixel 2 XL Guides, News, & Discussion] Kdx10:
Flashed v4afx 2.9 and its working perfect. Im in 8.1rom and rooted via magisk 15.3 upto that point everything was ok and awesome. But, when i try to flash dolby oreo zip(installed successfully in twrp without errors) the problem is both v4a fx and dolby apps are missing. But when i check on magisk modules v4a fx, audmod lib, and dolby are checked. What is going on. Lol. Any one tell me how to succeed on this process. Thank in advance
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
You could just extract the apk's from the zip files and install the apps that way :good:
[Google Pixel 2 XL Guides, News, & Discussion] vibrantliker:
Thanks! That was the problem.
[Google Pixel 2 XL Guides, News, & Discussion] Trupen:
You mean place Dolby zip in root directory
[Google Pixel 2 XL Guides, News, & Discussion] vibrantliker:
Anyone know of any other mods working, i.e., AM3D, etc?

I tried the Magisk version of AM3D and it doesn't work on my end.
[Google Pixel 2 XL Guides, News, & Discussion] Kdx10:
Thanks for the hint sir. Will gonna try this later
[Google Pixel 2 XL Guides, News, & Discussion] Juzman:
So I flashed this on my P2XL / Oreo 8.1.

Using 2.5.0.5 driver and all working well, however when watching YouTube videos, the audio is a millisecond or two out, anyone notice this?

I'm using Audiophile X profile, soon as I turn convolver off it is in sync. No matter what profile I choose in convolver, it is out of sync.
[Google Pixel 2 XL Guides, News, & Discussion] matt1313:
I tried turning on/off and no change as you described.
[Google Pixel 2 XL Guides, News, & Discussion] Juzman:
Hmm, strange. Must just be me then.
[Google Pixel 2 XL Guides, News, & Discussion] matt1313:
I also have iYTBP installed. Don't know if that changes anything as you described.

Maybe a clean install of everything
[Google Pixel 2 XL Guides, News, & Discussion] Juzman:
It's a fresh install of stock 8.1 January. Also using iYTBP.
[Google Pixel 2 XL Guides, News, & Discussion] matt1313:
Stock kernel??

I'm using elemental
[Google Pixel 2 XL Guides, News, & Discussion] Juzman:
I'm running Flash Kernel. :) It's okay, I can live with convolver off.
[Google Pixel 2 XL Guides, News, & Discussion] Youngbloodx:
My TWRP doesn't seem to be working properly. After flashing into TWRP using "fastboot boot twrp.img" the root folders seem to look okay, but when i go into the sd card folder all the files/folders in there looked like gibberish. They were all named in a weird format so i couldn't even flash the dolby zip.

I would sideload the zip using adb but after reading the posts, apparently it must be flashed using twrp.
[Google Pixel 2 XL Guides, News, & Discussion] CyberpodS2:
The only time I've seen that is of the storage is not decrypted by TWRP.
[Google Pixel 2 XL Guides, News, & Discussion] Youngbloodx:
Nevermind, solved that problem (i wasn't entering my pin code when prompted lol). Now I have to find out why my Dolby force closes and why i get the "Driver install failed:I/O error, please reboot and try again" message when prompted to install the V4A driver. The module i have installed on magisk is ViperFX 2.5.0.5.

When attempting to install what I think might be the correct module "Viper4A FX v 2.9" I get the "Installation failed" message in the log.
[Google Pixel 2 XL Guides, News, & Discussion] matt1313:
Are you flashing arise or magisk
[Google Pixel 2 XL Guides, News, & Discussion] Youngbloodx:
I'm in magisk trying to install the viper module. It then gives the "installation failed" message on the log
[Google Pixel 2 XL Guides, News, & Discussion] Youngbloodx:
Okay I resolved it. Instead of installing the module through magisk, I just flashed the v4afx zip through twrp. When I booted my phone and opened the viper app, I was no longer prompted to update the driver. Viper works and so does Dolby :)

Nowwww I just gotta find a sound profile that I like.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Here's a bunch of them for you to try out. WETA and smeejayt are my 2 favorites. Enjoy ?

https://drive.google.com/file/d/1XEfXDSP8pqQ4L3V6K3x0Q8lEh5f06svk/view?usp=drivesdk
[Google Pixel 2 XL Guides, News, & Discussion] Felosis:
Hey everyone, seems that ViPER and Dolby are not working on the Feb update anymore. Just ViPER alone, I'm getting the driver is not installed message again. I've tried several different things from SELinux permissive to patching DTBO, nothing works anymore. :/

Anybody else have luck?

EDIT: So I was able to get ViPER working. The modules were updated and ViPER doesn't need or even work with the Audio Modification Library anymore. After removing AML, ViPER started working again. As for Dolby, I can't get it to work still. Just crashing on startup.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Viper 2.8 + DD working ok on my P2XL. No permissive scrip used as well.
[Google Pixel 2 XL Guides, News, & Discussion] Felosis:
Nice! Thanks for confirmation it still works. What did you do to get it working, if you don't mind me asking?

I installed the ViPER module in Magisk, choosing the new driver and materialized version. Reboot and confirmed ViPER working (just edited my initial post about ViPER not working either). Flashed Dolby.zip in TWRP with success, but it just crashes on launch. I've had this in the past when I upgraded to the Jan security update, but patching DTBO fixed it for me (I can care less about the error on bootup, lol I wear my badge!). I've also tried with and without SELinux set to permissive for grines. Any ideas?

Oh, I'm also on Nathan's latest Flash Kernel 2.16.1.

EDIT: You know, I see you mentioned ViPER 2.8, but Magisk lists ViPER as version 1.0 now as "initial release" from 2.5.2018? Did you just manually flash the old module you had downloaded from before?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
I really didn't do anything special. Everything was already working on January build. I just dirty flashed the February factory image, installed twrp, flash kernel, and magisk. I booted it up and everything is working as it was before I started.
[Google Pixel 2 XL Guides, News, & Discussion] Felosis:
I figured that's what you did. :)

I got in the habit of running the Magisk Uninstaller script, along with the rest of my pre steps lol, prior to dirty flashing updates cause of an issue I had in the past. I guess I just need that old version 2.8 back as I know it works with Dolby. Do you mind sharing it with me? You should still have it in your /sdcard/Magisk Manager folder from the initial install. :)

Thanks!

EDIT: Ah crap, I forgot... If you could, I'd also need the Audio Modification Library and Universal deep_buffer Remover ZIPs from your /sdcard/Magisk Manager folder too if you have them. I'm sorry, it's a pain, but I'm sure that's my issue. lol
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
https://drive.google.com/file/d/1cJeP4MdYxtakzukkoC4yktyK5Hl4qvOJ/view?usp=drivesdk

The audio mod library will install when you flash the 2.8 zip in twrp. I don't use the deep buffer remover.