yashsingh1/xdaforums huggingface dataset:
[Android Software Development] guitardedhero:
This update amounts to nearly nothing for you guys so please do not get too excited as an identical installation as yesterday's zips will yield the same result if unsuccessful.

Officially, and unofficially, Dolby systems are composed of two Dolby apk's, at least one sound effect library, at least one system library, at least one XML profile configuration, and a very specific audio effects configuration for its effect universal unique identifier (UUID).

Removing any one of these components renders a functional implementation non-functional.

The way I prepare all Dolby ports is to result with a single Dolby .apk containing all necessary components and information to manually construct a fully functional and complete Dolby installation even if nothing else from the installation zip is available.

My highest priority, even long before starting the ARISE project, has always been to eliminate as much potential frustration possible a user may face when encountering something prepared by me - even if the user has no clue who I am or what XDA is.

My second priority is transparency, which is why my postings are almost excessive in information, details, and word-count. I do not see success in maintaining an understanding beyond others, success is equalizing that understanding and a humility to learn from others and share it further.

The reality is that much of what we see here at XDA is shared elsewhere - often times stripped, incomplete, and without any information regarding authorship or resources for seeking assistance.

I have no interest whatsoever in curtailing this reality, think of Lars Ulrich vs. Napster but without the piracy aspect, just the crusade. Let's not get distracted with "But, I made that!" nonsense, that is not what any of this is about.

The end-user is everything, even if that user has never visited this forum.

If these Dolby zips are downloaded, stripped of everything except for the single Dolby apk and shared elsewhere online with no information or resources whatsoever, the inquisitive user taking a peek inside the Dolby apk (an apk is simply an archive, after all) will find that everything needed to achieve a complete installation is provided easily if extracted.

But yeah, the damn UUID in that included information was incorrect, nothing more lol. :good:

EDIT:

Inadvertently uploaded wrong zip. The upload now has the change mentioned above. I apologise. :good:
[Android Software Development] yyz71:
Getting same results with opening Dolby. Permissive is set.. Google Pixel 2 8.1
[Android Software Development] guitardedhero:
Correct. Anything other than identical results would be very suspect.

However, a user reached out to me today with an offer of 2-3 week usage of a Google 2 XL destined for Return Merchandise Authorization to address Android 8.1 compatibility.

Access to official Android 8.1 firmware is certainly what I am lacking in order to resolve compatibility issues, no doubt.

This is one of many examples why all of you are the reason the ARISE project and community is what it is today.

This is no exclusive club, this is your project as much as it is "ours". :good:
[Android Software Development] yyz71:
Yes there's quite a bit of sound mods not working correctly with 8.1? I just managed to get viper working! But I do sure miss my Dolby.. Nonetheless we'll get this sucker figured out. Thanks for the reply ?
[Android Software Development] mac796:
Thanks for trying ?
[Android Software Development] matt1313:
Pm sent. I'll send tomorrow
[Android Software Development] darkstar73:
ARISE is working properly except for Dolby on my Nexus 6 running Nitrogen 8.1. If I can help diagnose the compatibility issues, let me what you need.
[Android Software Development] ainurrofiq:
This thread is so warm n fun, so much of humanity
[Android Software Development] iBART:
normal, v4a's problem with magisk is that everything is working but it couldn't process the sound.
[Android Software Development] mohand06:
Just out of curiosity why is that ds that I manually installed fc even though audio_effects.conf was correctly set and now works just fine after flashing your 2nd posted zip but audio_effects.conf (/vendor symlinked) this time being devoid of any ds reference ?

Flashed Dolby_SDK_17-27.zip on Sonophilos themed release V4A am3d Arkamys

For me the best dolby so far. Thanks [MENTION=4445176]guitardedhero[/MENTION]
[Android Software Development] jack allen:
Is magnum opus working on samsung devices running android 8.0 beta can some one point me to right place as well the op is all over the place
[Android Software Development] gk1984:
Been out of this thread for several months and tried to search but didn't find anything useful. Has this or regular Viper4Android been updated to support phones missing a headphone jack?

I tried this and Viper4Android a month or 2 ago on my Essential PH-1 and the problem was that although it worked fine via Bluetooth, it wouldn't process over the wired headphones using the USB adapter. I did manage to get it working by turning on the processing for Phone Speaker, but the options available there are limited.

I asked about this at the time (month or 2 ago) in the Viper4Android thread and the only response I got was same experience with a Le Eco phone that also has no headphone jack.

I've seen people making comments regarding this working on the Pixel 2, which prompted my question. Unsure how it's working via wired headphones. For all I know, it's working via Bluetooth. (And yes, I've seen it isn't working on 8.1 and there's difficulty on 8.0).
[Android Software Development] tropical cactus:
Thanks so much for this. Uninstalled digital plus and flashed the zip. Working on my 6p developer preview one 8.1. Amazing difference in sound between Atmos and digital. Only surround virtualizer is greyed out.

Edit: wrongly assumed it was Atmos because of the huge improvement over digital plus included in opus magnum. But excellent work though. Thanks.
[Android Software Development] Trupen:
Zip is not getting flash from twrp it's just showing Dolby logo and loading screen waited for 5 min nothing happened
[Android Software Development] Lughnasadh:
Surround virtualizer is for headphones so when you plug in the headphones it should become "ungreyed" out.
[Android Software Development] snsone:
Such rich sound on 8.1 (Nexus 6P)

Fantastic work
[Android Software Development] guitardedhero:
In v4a:

Tap the "hamburger" menu button located at the top left corner.

Settings > Lock Effect Mode > Headset (or Bluetooth). :good:

"Dolby™" and not "www.dolby.com", correct?

What device and firmware?

I am assuming you are required to perform a hardware power button to escape, correct?
[Android Software Development] pawelekdabek:
I have Mi 6. I have installed Stable Magnum Opus and Magisk v14 compatibility module and I have no LDAC connectivity. What have I done wrong?
[Android Software Development] guitardedhero:
Does your stock device firmware natively provide/support LDAC and now LDAC does not function?

Or were you expecting LDAC support by the presence of the LDAC libraries included in Magnum Opus?
[Android Software Development] yyz71:
Now the Dolby zip you uploaded Oreo. It seems to be working. With My Google Pixel 2 ? It seems that the Material viper isn't sticking ? So when I remove Dolby and reinstall Viper it works..
[Android Software Development] guitardedhero:
Magisk or SuperSU?

Is the Material Viper zip installing to /system or creating a Viper Magisk module if using Magisk?

"isn't sticking" describes the app appearing to not be installed, I am assuming. If so, this is certainly the most frustrating bug for me while using Magisk since 13.0.

I prepare Magisk modules on my device manually nearly all the time, performing recovery installations only to test the zip before sharing, therefore, I accept the fault - attributing the module "failure to start" issue to 0% of Magisk Module Template being used. Instead, I use/resource the latest Magisk installation util_functions.sh for my functions and installation scripts relevant to Magisk (This will change if found to be inadequate).

If everything still applies to you at this point, is this a common bug for you (since Magisk 14, possibly the previous build)? Or is it an occurrence when my zips (ARISE zips do not apply) are installed (as Magisk modules)?

I may be completely off-base, but I will just end with my "work-around" for these scenarios when installed modules with the auto_mount file do not link or mount to /system when booted:

Install the Magisk installation zip in recovery

If this is traced to my script(s), I obviously need to address this. :good:
[Android Software Development] yyz71:
I'm using magisk 14.5 it seems to install. It creates a magisk folder where it sits.. But that being said I'm not sure if they conflict ?
[Android Software Development] guitardedhero:
Gotcha. I am using the official ViPER4Android 2.5.0.5 along with this Dolby port, there should be no conflict with the two apps, unless it is something with the Material apk, though doubtful. Currently, I have both installed to /system, but that is only because I earlier tested an optional override parameter ("system.install=true" inside: /sdcard/arise_parameters.prop will instruct the installation script to install to /system when Magisk is installed) that will be possible with the next build I share.

The primary reason for this installation option (besides providing an option users may desire) was to test /system installs against those same installations as Magisk modules. I highly suspected stability to dramatically improve, which seems to be the case thus far.

However, as I described previously, this possibly is an annoyance/bug of my own doing.

Have you experienced this senario before, especially without anything installed originating from myself?
[Android Software Development] yyz71:
No I haven't this is first time this has happened.. It's frustrating. I won't give up though thanks for the reply and help ?
[Android Software Development] guitardedhero:
The next build will include the Magisk Module Template script for Magisk operations to test for appropriate behavior of the installations.

The ViPER4Android screenshot is unexpected though, that seems to portray an incomplete installation as the driver is appropriately installed during the initial ViPER4Android installation, unless this is the first launch after installing the zip.

Edit:

I am assuming the Dolby screenshot is portraying behavior during expected Dolby processing. Both screenshots (of various failure) appear to suggest an incomplete audio effects configuration.
[Android Software Development] yyz71:
This is the first launch after installation..
[Android Software Development] guitardedhero:
That makes more sense.

Is ViPER4Android installed as a data/user application as well?

Is audio_effects.conf identical in the following two locations?

/sbin/.core/mirror/(system/vendor|vendor)/etc

/(system/vendor)/etc
[Android Software Development] yyz71:
No my friend neither lines are there and viper isn't in data user app either.
[Android Software Development] Skittles9823:
Which viper installer have you used? I'm going to assume you've used Ahrion and Zacks most recent viper installer since you are using the material version. Unless you've used a system installer and just replaced the apk?
[Android Software Development] johnholley123:
[MENTION=4445176]guitardedhero[/MENTION] I have tried both of your Dolby Oreo zips that weren't marked SDK27, but I got error 2 in TWRP for both as shown in my screenshot. I am using a OnePlus 3T on OxygenOS Open Beta 19 (Android 8.0) with blu_spark kernel. Anything else you need? I would appreciate any help you could give to get this working on my phone.
[Android Software Development] yyz71:
I'm using the newest viper v4afx-v2.5.zip material
[Android Software Development] Skittles9823:
Yea that's Ahrions. That's why. The modules are conflicting. Guitardeds module I assume doesn't use AML, therefore whichever module loads last will work and the other won't work. However. If guitardeds module currently has the system override method then if you install that first you'll be able to install AML modules afterwards with no issues.
[Android Software Development] yyz71:
Ah I see thank you very much for that detailed information.? I'll give that shot on my next round! Getting kinda late here in Edmonton ?
[Android Software Development] Skittles9823:
No worries. Just noticed the dilemma and thought I'd give my 2c.
[Android Software Development] yyz71:
Ya things been headache for me.
[Android Software Development] veetoe:
Same problem with a pixel 2 xl on 8.1. Here is the twrp log:

Installing zip file '/sdcard/custom stuff/Dolby-Oreo.zip'

Checking for Digest file...

Skipping Digest check: no Digest file found

I:Update binary zip

Verifying package compatibility...

Package doesn't contain compatibility.zip entry

I:Zip does not contain SELinux file_contexts file in its root.

I:Legacy property environment not used in updater.

unzip: can't open /sdcard/custom[.zip]

mount: can't find /cache in /etc/fstab

linker: error reading config file "/system/etc/ld.config.txt" for "/sbin/busybox" (will use default configuration): error reading file "/system/etc/ld.config.txt": Too many symbolic links encountered

linker: error reading config file "/system/etc/ld.config.txt" for "/sbin/busybox" (will use default configuration): error reading file "/system/etc/ld.config.txt": Too many symbolic links encountered

WARNING: linker: WARNING: linker: error reading config file "error reading config file "/system/etc/ld.config.txt/system/etc/ld.config.txt" for "" for "/sbin/busybox/sbin/busybox" (will use default configuration): " (will use default configuration): error reading file "/system/etc/ld.config.txt": Too many symbolic links encounterederror reading file "/system/etc/ld.config.txt": Too many symbolic links encountered

/tmp/updater: source: line 49: can't open '/dev/tmp/META-INF/functions'

Updater process ended with ERROR: 2

I:Install took 0 second(s).

Error installing zip file '/sdcard/custom stuff/Dolby-Oreo.zip'

Updating partition details...
[Android Software Development] iamrahul10:
I am using this [screenshot attached] version of Viper. Is there any huge difference between that and Arise?
[Android Software Development] Skittles9823:
That's the original Viper4AndroidFX. The exact same viper in the stock edition of A.R.I.S.E.
[Android Software Development] snsone:
I had the same error, download through chrome on a windows pc and it works
[Android Software Development] jcarter3729:
Wait?...you have a Motorola Z2 Force that's ROOTED?...HOW?
[Android Software Development] veetoe:
This didn't work for me, still getting the same error code 2 in twrp when trying to flash the latest dolby-oreo.zip.
[Android Software Development] shantam3108:
Download using chrome and remove md5 check while flashing in twrp
[Android Software Development] veetoe:
I just tried and didn't see any md5 option, there was zip verification but it wasn't checked.
[Android Software Development] johnholley123:
+1
[Android Software Development] whiplash1:
The Dolby-oreo.zip doesn't start the flash. It's stuck at Dolby™. Running 8.0 on OnePlus One (Unofficial LOS 15)
[Android Software Development] jack allen:
Anyone?? No fix for oreo beta
[Android Software Development] guitardedhero:
Thank you very much, a log is the only possible way to effectively address these errors during recovery. :highfive:

Before rebooting from TWRP:

Advanced > Copy Log > Swipe

If forgetting to do the above before booting into Android:

/cache/recovery/last_log

Your error is triggered by the unzip operation failing, causing no content to exist.

I've seen this before with my installation scripts, especially Kenzo devices it seems.

At any rate, I have just finished some heavy and aggressive editing to the script's operations focusing on removing inconsistent information and file gathering and tidiness.

I then built upon this focusing on arise_parameters.xml customization file that will copy to internal storage if not already there. I've also updated the stand-alone viper zip as well as adding the 2.3.4.0 version as an option. broke them (lol).

4 2 zips in all as I have yet to install either enhanced zip (enhanced=longer file name) and I do recommend users to test the non-enhanced zips first, unless uninterested in debugging or there is no need to debug. :good:

Try the Dolby-Oreo.zip attached below. :good:
[Android Software Development] Fdraco10:
I´m still asking me, for when the ROUND 2?? :crying:
[Android Software Development] Vincent_40:
Hi all,

I'm Completly lost :)

When i'm on 7.1.2 or 8.0 custom rom, i flash just ONE zip like ARISE_Sound_Systems_Deuteronomy_2.4 and it's working fine.

But now, when i flash 8.1 custom rom this file doesn't work.

Can you decribe step by step what i need to do, to have Viper arise who works on 8.1. I think it 'll be help lot of users.

Thx in advance
[Android Software Development] sm3691:
V4a 2.5.0.5 installed

Magisk module installed

Enabled=yes

Processing=no

What can i do ??

V4a has very temporary activation

Sometimes with next track it got deactived
[Android Software Development] veetoe:
So I tried flashing again with the new Oreo zip and same results. It failed in twrp. Then I rebooted and tried flashing a font zip which worked...so I tried Dolby-oreo again in the same twrp session and it worked? Lol. So right now Dolby is installed and I verified it processes. I even have ahrions viper installed from magisk and it processes as well. They both seem to be working. I ran dumpsys media.audio_flinger in terminal and it shows Dolby and vipers effects loaded.
[Android Software Development] johnholley123:
I have tried this new zip and I have the same error. Here is the TWRP log.
[Android Software Development] guitardedhero:
Same issue:

Failure to unzip the archive.

I'll try something else, thank you for the log. :good:
[Android Software Development] johnholley123:
Ok, thanks for the quick feedback. Should I try downloading on my PC like somebody suggested earlier or just wait for your fix?
[Android Software Development] guitardedhero:
Are you able to retrieve the MD5 for the archive?

The MD5 for the four attached archives are as follows in the same order as the attachments appear:

Dolby-Oreo.zip

MD5: a2015a012c0213ef670b2a6a52669d07

ViperFX-2.5.0.5_Audiophile-20171219-gh.zip

MD5: 9fb69e62e5328f982856e7dcdbfc0341

Dolby_SDK17-27.zip

MD5: 809e05d50923920122c66f67b2481d18

ViperFX-2.5.0.5_ViPER4Android-2.3.4.0_Audiophile-X-20171219-gh.zip

MD5: 745999164dec07e4663bdc411135cda5
[Android Software Development] johnholley123:
Yes, I got md5 = a2015a012c0213ef670b2a6a52669d07, which matches the value you gave, and the sha1 = d10a6361c4509931e9a7f3af077cf6f3be052c2a.
[Android Software Development] whiplash1:
Still doesn't start flashing. Now the Dolby™ text isn't shown either.
[Android Software Development] guitardedhero:
No need to suspect the download in that case. I'll try to get something to you soon. :good:

---------- Post added at 11:32 PM ---------- Previous post was at 11:29 PM ----------

Lol, at least we are not running in place!

/cache/recovery/last_log will be a good place to start inspecting. :good:
[Android Software Development] sandyss18:
Guys could anyone send m the link to telegram group
[Android Software Development] whiplash1:
Here it is.

Edit: I flashed a different TWRP and the first zip flashed successfully but it doesn't process any audio and the options are greyed out. The 2nd zip gave me error 2.
[Android Software Development] whiplash1:
After successful flash with another TWRP. Also attached the log for the error 2 in the 2nd zip.
[Android Software Development] iamrahul10:
I was using this [Viper4AndroidFX] on my Xiaomi Redmi 3S and it was working fine. Now I switched to Redmi Note 4. And started using this, but this time the quality is different. In full volume, I am getting some scratchy sound along the bass.

So thought of switching to ARISE. Is there any great difference between both Vipers?

I am a huge fan of bass and the profile which I currently use is bass oriented. Will I get good profiles on ARISE?

So, if I want to flash ARISE, how can I remove the Viper4AndroidFX which is currently in my phone?
[Android Software Development] Skittles9823:
Okay so switching the viper installer won't change much sound wise. It's your profile that doesn't suite the device well. Every device is different and can require small tuning with viper profiles. I'd have to say I'm quite lucky that from the feedback I've gotten that my profile seems to be quite universal xD
[Android Software Development] iamrahul10:
From where can I get your profile?
[Android Software Development] Skittles9823:
Right here. Make sure to read the readme for install instructions and where to find the convolver.
[Android Software Development] iamrahul10:
Thanks a lot.
[Android Software Development] Skittles9823:
No worries.
[Android Software Development] iamrahul10:
There are two IRS'

Razor Surround ((48k Z-Edition)) 4.Stereo +50 Bass

Razor Surround ((44k Z-Edition)) 4.Stereo +50 Bass

Which one should I use?
[Android Software Development] Skittles9823:
Whichever one your viper processes at. But I've set the profile to use the 48K one since that's what mine process at. You can check in driver status in viper for which one to use.
[Android Software Development] iamrahul10:
I checked the driver status in my Viper and it shows 48K. So I will go wit that.

Once again thank you for all the details and files.
[Android Software Development] Skittles9823:
Sweet. In that case, once you move the profile folder and the irs files into the correct locations you can just load the profile twice and it'll automatically use the 48 K one
[Android Software Development] iamrahul10:
Done. :good:

Loaded twice and it works like a charm.
[Android Software Development] mimo.aridi:
Can u port am3d to oreo please. I really appreciate your work
[Android Software Development] Skittles9823:
I highly doubt this ever happening. It couldn't be ported to Nougat and Oreo messed up audio mods even further.
[Android Software Development] gopal pipil:
How did you flash it ? I'm getting error again and again
[Android Software Development] VincentJoshuaET:
Dolby-Oreo doesn't work on OP3T running Nitrogen OS 8.1 :( It installed successfully, but the app force closes.

---------- Post added at 03:49 PM ---------- Previous post was at 03:41 PM ----------

Tried the other Dolby zip, the app still force closes.
[Android Software Development] whiplash1:
I used a different newer TWRP version. Flashed successfully, but it's not processing any audio and everything is greyed out.
[Android Software Development] marstonpear:
The mod works fine on my 3 yo Z3 Compact on Carbon ROM (Nougat). But I'm getting very low in-call volume from the other party, also the mic sometimes doesn't work during calls. Has anyone else faced this problem? If so, how did you solve it?
[Android Software Development] guitardedhero:
Axon 7's new Oreo Dolby Atmos.
[Android Software Development] yyz71:
Ooh that looks good ?
[Android Software Development] vibrantliker:
What os is it working on?
[Android Software Development] guitardedhero:
Open Beta 2.
[Android Software Development] vibrantliker:
Think it will work on other versions of 8,0-1?