yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL Guides, News, & Discussion] Felosis:
Awesome, thanks bro! I'll give this a shot and report back.

---------- Post added at 01:53 PM ---------- Previous post was at 01:38 PM ----------

Yep, that was it! The latest Magisk v4a module 1.0 does not work with Dolby. If you check the Downloads under your Magisk, it will probably prompt you to update your v4a to 1.0. Don't do it! lol

Thanks again for your help!
[Google Pixel 2 XL Guides, News, & Discussion] Trupen:
Which version of viper works well with Dolby azon

Dolby azon latest version gives FC is viper 1.0 reason behind FC of dolby
[Google Pixel 2 XL Guides, News, & Discussion] Felosis:
The 2.8 version [MENTION=3730810]Badger50[/MENTION] posted above is working perfect. Remove any v4a modules you currently have installed, reboot, install the ZIP posted above (chose new driver and materialized version) reboot and everything should be good. I just used it on the way home from work with BT in my car. :)

2.9 should work too, but I've not tested it with Feb update. Both 2.8 and 2.9 will auto install the AML 2.8 or 2.9 depending on version you install as well.
[Google Pixel 2 XL Guides, News, & Discussion] otonieru:
I think thats not really the case. Am on V4A 1.0 Materialized Magisk Module, and my Dolby work normally.

Am on February patch btw. I even have my selinux on enforcing
[Google Pixel 2 XL Guides, News, & Discussion] Felosis:
Weird? Not sure then. It's working for both of us, which is what matters. I couldn't get v4a 1.0 materialized to work for the life of me. I mean v4a worked, but Dolby just FCs unless I use an old version. Oh well, thanks for sharing. I kind of want to try the new version again lol.
[Google Pixel 2 XL Guides, News, & Discussion] otonieru:
You might want to reflash dolby instead.

I remember well my problem in early days, when dolby keep FCing on me, until i flash it in permanent TWRP and suddenly the issue is gone
[Google Pixel 2 XL Guides, News, & Discussion] Felosis:
That was actually the first thing I tried. I actually tried flashing Dolby a few times in perm TWRP at different times to be sure. I'll probably try again later for grines to see how it goes. :)
[Google Pixel 2 XL Guides, News, & Discussion] otonieru:
Honestly, this also fazed me,

Since as far as i know, to use multiple sound mod together (ex V4A & Dolby) we gonna need AML installed,

You might want to try that as well (installing AML) and see whether dolby still crashing or not.

I dont have AML module installed right now, but i used to have it n maybe the file still reside, thus i got it working
[Google Pixel 2 XL Guides, News, & Discussion] Felosis:
That was my understanding too, but v4a 1.0 won't work either with AML 1.0 installed. Lol, as soon as I removed AML 1.0 then v4a starts working. V4a 1.0 doesn't even install AML automatically anymore. Not sure.

Would you mind trying v4a 1.0 with AML 1.0 modules and see if Dolby still works or even v4a? :confused:
[Google Pixel 2 XL Guides, News, & Discussion] Goog1e Phone:
This is strange...I used your exact guide (thank you for that btw) and everything worked.

I was on the Jan patch. Followed your guide to update to Feb patch and everything works for me.

Uninstalled magisk using magisk uninstaller

Removed -w and flashed img

Reinstalled twrp and magisk

And loaded viper and Dolby

Everything worked before like it did on the Jan update.

Only thing I notice differently on your set up and mines is that I use the stock kernel

Made a 1 min video to show.

[youtube]MxcGrJYLfto[/youtube]
[Google Pixel 2 XL Guides, News, & Discussion] CyberpodS2:
Not sure if this helps, but I dirty flashed the Feb update and all is still good to go...
[Google Pixel 2 XL Guides, News, & Discussion] otonieru:
V4A 2.9 has no problem,

You might want to try to install the 1.0 (i know, their versioning is weird, back to 1 after 2.9)update from magisk manager, and see whether dolby still working or not,

Also, you can update my Enable Doze for GMS module to v6 if you like to,

It has better support for oreo devices
[Google Pixel 2 XL Guides, News, & Discussion] yyz71:
Have you tried the Dolby Atmos port?
[Google Pixel 2 XL Guides, News, & Discussion] CyberpodS2:
To be honest, I've kept this same setup through dirty flashing both Jan and Feb updates as it just works. I'll be getting one of the custom roms soon so I'll try upsetting what I can and report back. In the short term, people that can't get scruff working might try the versions that work for me??
[Google Pixel 2 XL Guides, News, & Discussion] Felosis:
Out of curiosity... To completely remove Dolby in troubleshooting to start fresh, do I just delete it from system/priv-app? Is there anything else I would need to do? I guess I'm not sure if it adds or changes anything anywhere else. Thanks in advance! :)
[Google Pixel 2 XL Guides, News, & Discussion] Felosis:
Quick question... I've been flashing Dolby.zip from the OP in TWRP since it said to, but it's installing it in system/priv-app, so not systemless. Looking at your screenshots, I see you have a Dolby module in Magisk. Did you install the Dolby.zip from OP through Magisk so it's systemless or is that a different Dolby version from what OP posted? I'd love to get rid of Dolby from my System and go systemless! :)

Thanks!
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
I have the same, it's a priv-app and I installed it with TWRP. Have you tried moving the apk from priv-app to data app, and then rebooting? Maybe that'll work. ?
[Google Pixel 2 XL Guides, News, & Discussion] Felosis:
That thought crossed my mind as well, but I think I might try dirty flashing Feb again to "clean" my system then try flashing Dolby in Magisk to see if it will go systemless. I guess it doesn't really matter because it's working this way, but I'd rather take systemless if I have a choice. :)

If I get time today at work, I'll try and report back results. :good:
[Google Pixel 2 XL Guides, News, & Discussion] Felosis:
So, I did some testing and here's my results:

- The Dolby version attached in the OP must be flashed via TWRP and will not work in Magisk. No systemless on this one, unfortunately. It was worth a try. :)

- I did finally get V4A working on the latest version with Dolby. I noticed there were a few updates to V4A and AML over the last few days.

- The latest V4A 1.1 works with Dolby, but only without AML and UDBR. If I install one or both of AML or UDBR, Dolby will FC until removed.

- I also had to set SELinux to permissive to get Dolby to work without FC. The second I set to permissive, FC on Dolby goes away.

Steps taken after all testing:

- Not necessary, but did it for a clean start with Dolby... I dirty flashed Feb security update again to clean my system to ensure I got a clean start with Dolby. I also deleted the Arise config file from the root of my SD card.

- After dirty flash, did all the standard stuff; flash kernel, TWRP, Magisk, etc...

- Set SELinux permissive before any audio mods.

- Installed the V4A 1.1 Magisk Module, choosing new driver and Materialized, rebooted. Open V4A, settings, enable dev mode, disable SELinux, reboot again. Confirmed V4A working.

- Flashed Dolby.zip in TWRP, rebooted and verified both V4A and Dolby working. Testing in my car via BT as well for further verification.

I hope this is helpful. I know some have gotten this stuff to work with SELinux enforcing, but I couldn't no matter what. :good:
[Google Pixel 2 XL Guides, News, & Discussion] otonieru:
Even if it installed using magisk, if you check the file after boot, you will still see it in priv-app. Magisk made it like it was installed to system, while in fact it systemless. Thats why it so "magisk-cal" (sorry for the pun)

As for selinux, i think as long as your initial set up was done in permissive environtment, it will work upon update. But if you do initial flashing/setup in an enforcing. It wont work
[Google Pixel 2 XL Guides, News, & Discussion] Felosis:
That was my thought on the magisk part, but wanted to try anyway since I was messing around. :good:

That makes sense on the selinux part, I'm sure it was the way I setup originally. Oh well, I don't mind being permissive. I patch my dtbo too! lol
[Google Pixel 2 XL Guides, News, & Discussion] Felosis:
Hey guys! Would someone be kind enough to check their "/sdcard/MagiskManager" folder for a few older versions for me? Though I've got the latest version of V4A and Dolby working, I'd like to do some further testing/comparisons between the versions. I think I get better quality with V4A 2.8 over the rebirth 1.x version, but not sure if it's just me or not yet considering the driver version is the same, so I want to test 2.9 again too. lol

I've also noticed a couple annoyances with new 1.x version and want to rule out if it's indeed the new version or maybe something I did messing around after the Feb update. Mainly, randomly when I open the V4A app on 1.x, it complains the driver isn't installed, however, just backing out and reopening it it will automatically start processing and work again. I don't get this on 2.8.

I don't have the legacy 2.9 versions anymore as I started from scratch with Magisk when I upgraded to the Feb security patch, so if anybody still has the following and could share, it'd be greatly appreciated!

- ViPER4Android FX version 2.9 Magisk Module ZIP

- Audio Modification Library 2.9 Magisk Module ZIP (I know V4A installs automatically on this version, but I'll take it just in case if available) :)

- Universal deep_buffer Remover 2.9 Magisk Module ZIP

Thanks in advance! :good:

Edit: Got everything working. The audio quality wasn't a quality issue, rather I somehow had the wrong profile in Dolby selected so it sounded weird. User error!

As for the interminintent driver issue, a new V4A release 1.2 module was released and all good now! :good:
[Google Pixel 2 XL Guides, News, & Discussion] vibrantliker:
How are you all getting selinux to stick in permissive?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Maybe the selinux permissive magisk module??
[Google Pixel 2 XL Guides, News, & Discussion] vibrantliker:
I don't see that...
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Use mine ?

https://drive.google.com/file/d/1ptS5jCZ8ROQ_chCce2hMOFw4V6yuJjvj/view?usp=drivesdk
[Google Pixel 2 XL Guides, News, & Discussion] vibrantliker:
Hey Badger50, You have Dolby Oreo working also?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Yep. I use Dolby digital + V4A 2.8

It's an older version, but it works ?
[Google Pixel 2 XL Guides, News, & Discussion] vibrantliker:
How do you patch dtbo?

---------- Post added at 01:37 PM ---------- Previous post was at 01:36 PM ----------

You're on stock, right?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Nope. DU.
[Google Pixel 2 XL Guides, News, & Discussion] vibrantliker:
Pm'd you.
[Google Pixel 2 XL Guides, News, & Discussion] Felosis:
To patch dtbo, open MagiskManager, uncheck both "Preserve force encryption" and "Preserve AVB 2.0/dm-verity", tap "Install", "Install", then the direct option, reboot and profit. Keep in mind though, patching dtbo will give you the annoying error message on every reboot, but can be ignored, nothing is broken. :good:

If you're asking what ROM I'm using, I am stock, but use Flash kernel. I have upgraded to the latest V4A since this post as everything is working now. :)
[Google Pixel 2 XL Guides, News, & Discussion] vibrantliker:
Thanks, where is the "install", "install" option? (see screenshot)
[Google Pixel 2 XL Guides, News, & Discussion] otonieru:
After you update your magisk manager, that option will turned into "Install" button
[Google Pixel 2 XL Guides, News, & Discussion] vibrantliker:
Thanks, for some reason that new version fc's.

Edit: actually it installs ok.

---------- Post added at 03:06 PM ---------- Previous post was at 02:45 PM ----------

I did all this and it didn't change anything.

I also have no error message after booting.
[Google Pixel 2 XL Guides, News, & Discussion] Felosis:
I'm sorry, I probably should have asked before, but why are you trying to patch the dtbo? Are you trying to troubleshoot Dolby FCing? That's also weird you are not getting an error on boot up after patching dtbo. Are you sure you unchecked both boxes above the "Install" button before taping "Install"? After the system starts up, you should get a message saying "There's an internal problem with your device".
[Google Pixel 2 XL Guides, News, & Discussion] vibrantliker:
Yes, Dolby fc's. and I did uncheck both and followed instructions.
[Google Pixel 2 XL Guides, News, & Discussion] Felosis:
Can you please list out the Magisk Modules you have installed?
[Google Pixel 2 XL Guides, News, & Discussion] vibrantliker:
I have none at the moment. I'm starting over with flashing my rom.
[Google Pixel 2 XL Guides, News, & Discussion] Felosis:
Oh, gotcha... So a couple of things, if you're on a custom ROM, I don't think you'll get the error on boot up. You'll also need to install the V4A Magisk Module (choosing new driver and Materialized version during install) before Dolby will work. You don't need Audio Modification Library or Universal deep_buffer Remover anymore with the latest V4A for Dolby to work either. If Dolby still FCs after V4A module install, try setting your SELinux to permissive and reboot, then try again. :)
[Google Pixel 2 XL Guides, News, & Discussion] vibrantliker:
Thanks. got it working by starting from scratch.
[Google Pixel 2 XL Guides, News, & Discussion] Felosis:
Glad you got it working! :good:
[Google Pixel 2 XL Guides, News, & Discussion] State.of.mind:
Did anyone on the Pixel 2 Xl get the new one to work? https://xdaforums.com/android/software/app-dolby-atmos-axon-7-oreo-port-t3740508
[Google Pixel 2 XL Guides, News, & Discussion] MrBrady:
Haven't flashed anything yet, but to go back to stock, do I simply apply the latest OTA from Google? (Stock recovery, sideload OTA).

I'm always concerned about modifying the System with the Pixel 2 XL after reading it's getting more strict with security.
[Google Pixel 2 XL Guides, News, & Discussion] matt1313:
Just checking in. Using 8.1 February. Same setup with viper for magisk updated to 1.3.2

All running smoothly.
[Google Pixel 2 XL Guides, News, & Discussion] marbertshere:
Hi, do I have to install Audio Mod Lib or BusyBox or any other mods to get this working? I'm on the Feb update. Thanks.
[Google Pixel 2 XL Guides, News, & Discussion] matt1313:
Follow op
[Google Pixel 2 XL Guides, News, & Discussion] vibrantliker:
I didn't and it's working fine.
[Google Pixel 2 XL Guides, News, & Discussion] Goog1e Phone:
Delete
[Google Pixel 2 XL Guides, News, & Discussion] matt1515:
I'm on Pixel 2 Xl I want to do this but need to keep from safety net being tripped. Dolby just FCs and i don't want to set to permissive to get this working. I'm on latest 16.0 magisk is anyone have Dolby with safety net working?
[Google Pixel 2 XL Guides, News, & Discussion] alphamale:
I can't get this to work. Anyone got any suggestions?
[Google Pixel 2 XL Guides, News, & Discussion] alphamale:
Any my YouTube app keeps crashing since I installed all these mods
[Google Pixel 2 XL Guides, News, & Discussion] matt1313:
Have you played music? What player are you using?

YouTube no idea... do you have a theme installed?
[Google Pixel 2 XL Guides, News, & Discussion] alphamale:
Spotify. I have it working now. I uninstalled everything and installed BusyBox from play store and I used the latest magisk permissive script. No themes installed for YouTube it's still f/c and I get this message
[Google Pixel 2 XL Guides, News, & Discussion] alphamale:
Edit I disabled you tube ad away, and now it's working.
[Google Pixel 2 XL Guides, News, & Discussion] State.of.mind:
Does this work on the Dirty Unicorn rom
[Google Pixel 2 XL Guides, News, & Discussion] vibrantliker:
Yes, use the first Viper Magisk download. The Dolby for Oreo zip floating around works also.
[Google Pixel 2 XL Guides, News, & Discussion] holla420:
Would this work on Android P by any chance?
[Google Pixel 2 XL Guides, News, & Discussion] matt1313:
Try and let us know.
[Google Pixel 2 XL Guides, News, & Discussion] holla420:
Lol they all say that ?
[Google Pixel 2 XL Guides, News, & Discussion] boonthongw@gmail.com:
Try toutupe vanced edition, it work flawlessly without ads and can playing music in background.
[Google Pixel 2 XL Guides, News, & Discussion] alphamale:
Link
[Google Pixel 2 XL Guides, News, & Discussion] boonthongw@gmail.com:
Search
[Google Pixel 2 XL Guides, News, & Discussion] matt1313:
Just wanted to confirm working on April update
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Yep, that it is. I just fastbooted the April update with the -w removed, let it boot up once, then fastbooted twrp, then flashed the twrp.zip+kernel.zip+magisk.zip, booted up and V4A and all my other modules are fine :good:
[Google Pixel 2 XL Guides, News, & Discussion] sharpz811:
Hey Badger would you mind sharing exactly how you installed both Viper and Dolby? I'm using Dolby zip from the op but no matter what I do Dolby is constantly force closing I'm on stock+Flash kernel+magisk all latest builds I had this working perfectly fine on stock before then I went to try some ROMs then did a clean install of stock and for the life of me I can't get Dolby to stop force closing I've even tried changing selinux
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Well bruh, I do it in a bit of a round about way. I'll leave it up to you if you wish to try it. First, uninstall all V4A magisk modules and reboot. Then go into twrp and flash this older version of V4A...

https://drive.google.com/file/d/1cJeP4MdYxtakzukkoC4yktyK5Hl4qvOJ/view?usp=drivesdk

Then flash Dolby Oreo zip.....https://drive.google.com/file/d/1jIbneo2Nad2nz2Hi8POSRDqrHFOTImUH/view?usp=drivesdk

Then boot up, and you should be good. You can then go to MM to the download section and update the V4A and AML modules from within MM. I've used this same procedure on stock, DU, and AquariOS roms. Hope it works out for you :good:
[Google Pixel 2 XL Guides, News, & Discussion] sharpz811:
Fam you are a very very very good man! I'm test this method and report back. Thanks so much.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Thank my friend. Let me know how it works out :laugh:
[Google Pixel 2 XL Guides, News, & Discussion] sharpz811:
Sorry to bug you but one more question before I begin, do I need to install the AML module before I Flash your provider zips or will it install with the Viper zip?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
No need to install AML. The V4A zip will install an older version, which can then be updated within MM if you want to :good::cool:
[Google Pixel 2 XL Guides, News, & Discussion] sharpz811:
Ok so It still didn't work but I think I figured out why Dolby keeps force closing. A couple days ago after my clean install of stock I tried to install Viper via magisk and then Flash the Dolby zip in recovery but I also flashed the zip in my attachments like I usually did before I started flashing custom ROMs and ever since I flashed it out never goes away lol EVEN after a system restore from my recent backup (backup had no mods) it's still freaking there lingering somewhere in my system. That's the only thing I can think of that's messing with Dolby. So once again I'll have to do a clean install wiping the whole device so I can start from scratch thank God for Titanium backup lol. Dolby don't even show up in MM since I flashed that stupid audiophile zip
[Google Pixel 2 XL Guides, News, & Discussion] bkdodger:
I installed V4 in recovery and rebooted.. Then back to recovery for Dolby not to force close... I did them separate only way worked for me..

Pixel 2 XL
[Google Pixel 2 XL Guides, News, & Discussion] sharpz811:
I'm not sure if you've ever hard Dolby force close on you but if you did, did Dolby still show up in magisk manager? It doesn't for me so the only way I can uninstall Dolby is via system restore from my TWRP backup
[Google Pixel 2 XL Guides, News, & Discussion] bkdodger:
I think I saw it in Magisk and was able to delete it there ... I was getting the force closes...only way it worked after was to install older V4X in recovery and once up I opened V4.. Then flashed the Dolby zip in recovery.. Can you see Dolby in root explorer in System./priv-app? Maybe delete from there if so then reboot..

This is how I see it now

Pixel 2 XL
[Google Pixel 2 XL Guides, News, & Discussion] sharpz811:
That's exactly how I used to see it but haven't seen it at all lately and I've restored system and reflashed v4a and Dolby with the same results. I just deleted the Dolby APK from system/priv-app but I didn't do that before because I assumed that Dolby zip would've installed some other system files that I would not be able to find. But I'll try again this time flashing both zips separately lol. Thanks man
[Google Pixel 2 XL Guides, News, & Discussion] sharpz811:
This is my issue never works and never shows up in MM even tho I've followed both your instructions as well as the op. so I'm just gonna do a clean install and wipe everything and start from scratch. Thanks for the help guys.
[Google Pixel 2 XL Guides, News, & Discussion] bkdodger:
Hmmm weird.. Only difference I always flashed V4 2.3.4.0 older one not sure that would make a difference with Dolby.. But like you said should see it in Magisk

Pixel 2 XL
[Google Pixel 2 XL Guides, News, & Discussion] matt1313:
I just updated sons phone last night.

Follow OP. Clean flash rom or update to latest.

Setup/full boot

Flash magisk

Install v4a from MM, use material, new driver (vol+ 2times)

Flash Dolby in twrp

Profit
[Google Pixel 2 XL Guides, News, & Discussion] sharpz811:
Omg brah I'm about to give up on Dolby here's exactly what I did:

1. Flash April firmware

2. Let it boot, do minimal set up

3. Fastboot twrp

4. Adb sideload latest twrp, flash kernel, and magisk

5. Boot up system

6. Installed viper from magisk new, materialized

7. Reboot

8. Boot up and confirm viper working

9. Boot Beck into twrp

10. Flash Dolby-Oreo zip

11. Reboot

12. Open Dolby and once again FORECLOSE

and it still don't show up in magisk so I don't understand what I could possibly be doing wrong these were the exact steps I followed on Feb security update and also in DU rom
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Wow dude!...Dolby definitely doesn't like you! Go back to twrp and flash Dolby zip once or twice more just for the heck of it :good:
[Google Pixel 2 XL Guides, News, & Discussion] matt1313:
I had a issue with my son's using free root explorer to find Dolby. I switched to Es and tried and it worked.
[Google Pixel 2 XL Guides, News, & Discussion] sharpz811:
Yup I've been using es file Explorer for years now so it can't be that but I'll make another backup and then try again this will be my steps:

1. Make backup

2. Uninstall viper

3. Reboot

4. Install viper from magisk

4. Reboot then make sure viper works

5. Boot to twrp

6. Flash dolby-oreo

7. Reboot

8. Then watch the app force again lol

9. Then restore my backup:p
[Google Pixel 2 XL Guides, News, & Discussion] DevALT:
Will this work with magisk 16.3?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Does for me on the beta 16.3 :good:
[Google Pixel 2 XL Guides, News, & Discussion] DevALT:
Cool I'm flashing this right now ?

Since I use magisk for root I wasn't able to make work arises/DD or Viper :(

EDIT: I was able to make Viper work, but Dolby won't open it keeps crashing when I open the UI

Weird things is that when I disable Viper, start a music and open Dolby when it crash the sound is lowering, it looks like Dolby is working but I can't customize Dolby profile :( any suggestions?
[Google Pixel 2 XL Guides, News, & Discussion] matt1313:
Don't know what to say. It's working on 2 of my phone's using the steps mentioned before.