yashsingh1/xdaforums huggingface dataset:
[Android Software Development] Essentrix:
Dolby Atmos Add-On for Deuteronomy updated in November.
[Android Software Development] greenza:
Don't suppose you have a AFH link for this zip?
[Android Software Development] Kyrillos:
Guys sorry for a dummy question, but i couldn't find the answer in so many posts here. I would like to try the latesr alpha 8-8. There are posts to copy the atmos_yes.prop to system. I have two questions on that:

1. The prop is in the user triggered folder. Do I have to copy it to system of the phone or include in a folder and rezip the installation file.

2. Do you suggest to include the other prop files included in the user triggered folder as well?

Thanks in advance
[Android Software Development] Essentrix:
Here you go:

https://www.androidfilehost.com/?fid=312978532265371208
[Android Software Development] wayneywoo:
1. copy the file into /system exactly, nothing else.

2. No unless you need to...
[Android Software Development] crackerjack1957:
You think maybe systemless root could be causing a no processing in viper & dolby.

It can be fixed by a simple reboot but when going from headphones to speaker & back it happens again.
[Android Software Development] vjendra:
Thanks :)
[Android Software Development] hunting_:
plz help me which line i delete & how to delete

because not v4a not work 2.4.8.8 Dolby work fine
[Android Software Development] FinickyMan:
No need to freeze ice, just remove the icepower_algo effect entry. Dolby, besides permissive kernel, needs full focus to process. Found out this, on cm.14-1, 7.1.1 because of using Force activities to be resizable in developer options (multi windowing). When Dolby window stretched out on tapping the full screen symbol at the top right corner of the window, Dolby lights up.

Screen shots
[Android Software Development] Phrodini:
Thanks. I was thinking exactly which out of the two actually resolved the problem. Since I deleted the entry I will unfreeze ice.. Did you have the same issues as I did with both not processing?
[Android Software Development] nericollin:
My apologies, I didn't see that Poweramp and Neutron were able to play the FLAC files successfully.

This makes sense though. Some players are not able to play lossless audio formats (WAV, FLAC, ALAC, etc).

A lot of players have trouble playing lossless audio that's in the form of one singular audio file for an entire album utilizing a .Cue to determine what time markers signal the beginning and end of each track.

These can cause problems in programs that aren't Poweramp and Neutron. I know that other apps can play them though: USB Audio Player, Black player, etc

---------- Post added at 05:58 PM ---------- Previous post was at 05:54 PM ----------

You're welcome! Just did another clean flash this morning on SAOSP, December 11 build, with opengapps (pico) from the same date. No issues at all.

After repeating the same method several times, I'm almost certain that this will get things to work without any problems consistently.

This is just on a Nexus 6p though. the one factor that could make this method not "fool proof" , so to speak, is the device people are using. If users are running AOSP Roms though , I don't see why it wouldn't work.

---------- Post added at 06:02 PM ---------- Previous post was at 05:58 PM ----------

I'd recommend configuring the .Zip to install Dolby, not flashing a separate Dolby .Zip file.

---------- Post added at 06:05 PM ---------- Previous post was at 06:02 PM ----------

The easiest way to do this would be extracting the alpha 8-8 .Zip, going into the Deuteronomy subfolder in the extracted .Zip and rename the props you want installed (Dolby, AM3D, Deep Buffer, etc) by adding a "_YES" to it. Example Something.prop turns into Something_YES.prop

When finished go back to root of extracted .Zip, select all the subfolders and compress them into a .Zip file. Use this one to flash and it will now install all those components you enabled with _YES earlier

---------- Post added at 06:07 PM ---------- Previous post was at 06:05 PM ----------

I posted a method that utilizes SuperSU version 2.76 because of the issues that systemless root has.

This will fix the issues with no processing and possibly force closes.
[Android Software Development] docnok63:
Are you saying you've tried other media players or things like YouTube and streaming music apps (Pandora, etc) don't work? If it's streaming apps, that's what deep_buffer_YES.prop is for.

See above answer.

We have at least three people with OP3 in the dev/testing team. All of them are on 8-8 without issue.

Have you verified that it's Atmos or Viper? Use the attached file to find out when the problem occurs. Play the file with both Viper and Atmos powered up. Then just Viper powered and then just Atmos. This will tell you which app is causing the issue for you.

Are you saying Atmos doesn't affect your BT output at all or the Surround Virtualizer in the app does nothing over BT for you?

No, it's not systemless root as many are using SR5 without issue. This is a known issue with the Alphas and we're trying to pin down why it occurs.

1) Use the search function on this thread where I post about icepower algo

2) Use a text editor to remove the three lines of code. Reboot and profit

EDIT: I forgot to attach file...
[Android Software Development] wayneywoo:
Thanks for the reply.

I mean in Atmos, there is an On/Off switch for Surround which makes a difference (Headphones/Speaker but Bluetooth, the switch won't respond or turn on/off. Atmos still responding as the equalizer and the other two switches work...
[Android Software Development] docnok63:
Since your post last night, I've had three people, including two on the test team, test this method. It didn't work for any of them. All of them were on CM-based ROMs, so that's a big difference.
[Android Software Development] nericollin:
Thank you for the feedback! That confirms my suspicion then that it wouldn't work on CM Roms. I'm wondering why that is though
[Android Software Development] hunting_:
i search but not success to find post
[Android Software Development] Phrodini:
Screenshotted
[Android Software Development] Joloxx9:
Is deuteronomy working on oneplus 3t and how is it comparing to leviticus?

Wysłane z mojego ONEPLUS A3003 przy użyciu Tapatalka
[Android Software Development] Phrodini:
I quoted his post..Look above..View his original post to see the screenshot
[Android Software Development] raylogic:
I have Samsung S5 CM14.1 8-8 plus Atmos working here.

R.
[Android Software Development] NexusLush:
I read through two pages of your comments going back a week and didn't find it. Can you please point it out to me?
[Android Software Development] FinickyMan:
True
[Android Software Development] Phrodini:
Saved for DDC joints

---------- Post added at 08:27 PM ---------- Previous post was at 08:19 PM ----------

Check my quote of his post above, it has the links
[Android Software Development] shindiggity:
Can't wait for the Pixel to become part of the family, great work guys!
[Android Software Development] sm4tik:
Was there ever a solution or a workaround for this? I skimmed through the rest of the thread but nothing caught my eye. Happens here with alpha 8-8, n6p running SAOSP 7.1.1 build.
[Android Software Development] FinickyMan:
I'm on CM 14-1, 7.1.1, permissive. I don't use SuperSU to get deut. 2.4 alpha 8-8 fully functional V4A and Dolby on any sound source.
[Android Software Development] docnok63:
Right. I just had to verify that we were talking about the same thing. I've asked in the test team (most aren't Atmos users) and only one reported that this also happens with AM3D. Perhaps this is BT standard issue? Perhaps others reading this can chime in?

EDIT: Just confirmed by another member. This is intentionally disabled with BT connectivity.

1) Yes. 2) Each book has its own flavor but many like Deut the best. "Best" is always going to be what's best to your ears.

I'm posting right now to say that a MAJOR breakthrough has been made in just the last hour. More testing/packaging needs to be done, but there may be more news on this.......shortly....no ETA.... :good:

This is one of the bugs we're working on to take 2.4 out of Alpha phase and into stable.
[Android Software Development] Joloxx9:
Thx I will try deut, can I flash it over levictus?

Wysłane z mojego ONEPLUS A3003 przy użyciu Tapatalka
[Android Software Development] metrohackz:
Flashed latest alpha along with proaqistica all is good here icesound function perfect good work
[Android Software Development] docnok63:
No. Make a Nandroid backup and dirty flash your ROM. If using 2.2.3 or 2.3.3, make sure that you use the patched version.
[Android Software Development] lynnux:
Flashed 2.4 alpha 8-8 on N5 running CM14.1caf, and it's working great right out of the box. Sounds great, too. Didn't install Dolby, not finding it necessary.
[Android Software Development] pogi1100:
Yea, I just downgraded to the stable 2.3.3 version, works flawlessly on my 6P on 7.1.1. Dont really see a difference between this and the alpha anyways. Alpha bugs should be expected I guess.
[Android Software Development] c_/\/\_k:
how to install in x86 zenfone 2..?
[Android Software Development] vsot13:
Its all good with Spotify. Nexus 6
[Android Software Development] Godlydevils:
[IMG="1"]https://i.imgsafe.org/0a938eebbb.png[/IMG]

[IMG="2"]https://i.imgsafe.org/0a93934dad.png[/IMG]

second image:

https://i.imgsafe.org/0a93934dad.png

Any fix to this?

Using Sony XPeria m c1904 with cm14.1 installed, device is rooted by default, can use root on other apps

Have flashed 2.3.3 with dolby atmos

is fresh install of whole rom and just this
[Android Software Development] JBNex:
Yes I posted about it several times, guitardedhero has suggested this solution:

This does not work for me, I found another workaround, which is to reinstall v4a apk in the v4a folder in /system/priv-app. After it installed, press Open and it should process. Make sure Master Power is on before reinstalling.

---------- Post added at 11:22 PM ---------- Previous post was at 11:15 PM ----------

To deal with difficulties copying/accessing DDC/convolvers, it has to deal with bad folder permissions of the ViPER4Android folder in /sdcard/. What worked for me was going to /data/media/0/ and deleting that folder (I was unable to delete it when in /sdcard/). Then go back to /sdcard/ and re-create the ViPER4Android folder, and the respective folders DDC, Kernel, Profile, and copy your profiles, IRS, DDC, etc.
[Android Software Development] Lughnasadh:
Neither of the 2 solutions for the headphone=not processing bug above have worked for me on Hammerhead, but it was posted earlier today that the team is working on it.
[Android Software Development] JBNex:
Oh, that's strange, I don't think my workaround worked for anyone but myself :p Someone with the same device (angler) and also on 7.1.1 didn't work either. Glad to hear they are working on it though!
[Android Software Development] vjendra:
[MENTION=4967345]docnok63[/MENTION]

Thanks :)
[Android Software Development] Omega Kaos:
I finally managed to get it working on my Pixel XL

All I have done is edit the updater-binary in the zip to successfully install

only issues im having is am3d does not work and atmos works fine until I plug in the headset

Viper is processing and working as expected
[Android Software Development] ViTAMiNCHEG:
For a very long time I couldn't get Dolby lemax working. fc all the time. I tried different arise versions. Until yesterday.

I wiped data/system/cache/dalvik and flashed the latest RR 7.1.1 rom on my Mi 4s and then latest ARISE alpha 8-8. Boom... And it's working. No fc's, viper and ice both processing. Finally I can enjoy the beauty of sound.

Thank you the developers. This is truly the best sound mod on xda. And I'm very happy that it finally worked for me.
[Android Software Development] docnok63:
The Zenfones were only recently added to the sources in the Alpha versions (see screen below.) Download and flash Deut 8-8 in recovery.

Flash SuperSU in recovery instead of using CM's superuser.
[Android Software Development] docnok63:
I was leery when I saw my current ROM was going from 7.1 to 7.1.1. I read multiple reports in this thread how 7.1.1 didn't play nice with the Alphas. Well, I'm happy to report not only is ARISE working with the 8-8, but EVERYTHING!!! AM3D! Atmos! DTS! Arkamys! ICE sound! 100%!!! (Even the elusive Spotify!)

Thanks [MENTION=4351374]shaggyskunk[/MENTION] for sharing the flashing experience/joy over Telegram! ARISE UP!!!
[Android Software Development] str8str:
Sorry if this is a stupid question but can the Dolby add on be used with numbers…?

Sect From Me, Is That You?
[Android Software Development] docnok63:
Sure. We even built one special for Numbers: https://www.androidfilehost.com/?w=files&flid=106151
[Android Software Development] greenza:
As mentioned a few pages back 2.4 alpha 8.8 breaks streaming music apps on my HTC 10 running Leedroid Nouguat.

It was suggested that use the deep_buffer_YES.prop which i tried (flashed ROM, copied prop file to \system and then flashed 2.4 alpha 8.8) but it still didn't work.

Also when I did a nandroid recovery streaming audio was still broken, so reflashed my ROM, still broken, so had to format Data and reinstall ROM to get things working again. I think I'll give 8.8 a miss for now as it's too much hassle trying to figure why it's not working.
[Android Software Development] hawknest:
Alright, I just might be having a moment. But for the life of me I can't get Deuteronomy to work. So far I have viper4arise app installed with installed drivers.

Running Leedroids M9 sense 8 rom, Carrier is Verizon running Elemental 4.05. Firmware is up to date and everything.

I flash the Deuteronomy sound system zip in TWRP while the flash goes OK without error upon reboot I'm getting bootloops at the HTC Splash screen. Is there something I should be doing with the zip before flashing. The OP says extract files and examine contents

Thanks in advance for any help on what I can do to get this going

I'm set to permissive and boomsound is disabled
[Android Software Development] amh10:
I am having a similar problem with ArkamysAudio - where I have a constant FC on this and the contents of the folder in data/data/[app name] are empty. If this is due to a lack of write access - how can I fix this?
[Android Software Development] marianoasis:
Hello. Im on rr nougat 7.1 with a Titan ... and i cant make ir work arise (viper4android) help please.
[Android Software Development] Papdya:
From where to get the latest alpha? Can someone plz provide the link? Its hard to browse each folder on android file host on the phone.....
[Android Software Development] shaggyskunk:
https://www.androidfilehost.com/?fid=601307472480698515

Sent From My SM-N910W8 ??
[Android Software Development] Papdya:
Thanks!
[Android Software Development] Papdya:
It doesn't work on 7.1.1? Or do I have to copy some file somewhere for it to work? Cause I flashed it just now on 7.1.1 Resserruction Remix and my device is moto e . but the drivers are not enabled
[Android Software Development] Godlydevils:
that bricks my phone

and supersu didn't worked the last I flashed
[Android Software Development] abhimanyu.singh:
Hey Guys,

Can anyone help me create Viper4Arise Profile. I need good(Best) Bass and nice Surround (Like Microsoft headphone virtualization or better). Please help me setup this kind of Profile. or send me if you can.

Thanks a lot.﻿
[Android Software Development] Papdya:
I got it working by flashing SuperSU but it broke my RIL so no sim signal.. Any workaround to flashing SuperSU? I tried downloading from play store and installing binaries. but it gave errors every time....
[Android Software Development] shaggyskunk:
Which version of SuperSU did you Flash? Downloading from the store is a pain I find.

Sent From My SM-N910W8 ??
[Android Software Development] Papdya:
The systemless one linked a few posts back..
[Android Software Development] shaggyskunk:
Yeah there's a few versions - which one v2.78 Stable? - v2.78 SR5?

You could try this version

https://www.dropbox.com/s/orxtgjrn8n6wkih/UPDATE-SuperSU-v2.65-20151226141550.zip?dl=0

It's not systemless

Sent From My SM-N910W8 ðŸ‡¨ðŸ‡¦
[Android Software Development] Papdya:
This one

UPDATE-SuperSU-v2.78-20160905010000.zip
[Android Software Development] shaggyskunk:
Did you try SuperSU that I posted above v2.65 and as I said it's not systemless

Sent From My SM-N910W8 ??
[Android Software Development] Papdya:
I will try.. Can I flash over this SuperSU?
[Android Software Development] shaggyskunk:
You should be able to.

Sent From My SM-N910W8 ðŸ‡¨ðŸ‡¦
[Android Software Development] docnok63:
You said streaming music app(s). Which ones did you try? deep_buffer_YES was a good recommendation for your situation. Alpha 9 is......errr.....baking.....and may or may not be public.

Very ironic that you and [MENTION=6518008]greenza[/MENTION] post one after another with ARISE troubles on the same ROM. This tells me that this is another case of ROM incompatibility with ARISE. Please try another ROM. Good luck!

Ark crashes are, unfortunately, one of the issues that's keeping 2.4 from progressing from Alpha phase to stable. Please find my post a few pages back to troubleshoot this.

Please give the ARISE version you're trying to install, what problem you're having, what you've done to fix the problem, and if you've had a previous version of ARISE working.

Under driver status, there's two different words. Enabled and Processing. To fix Enabled, hit the master power button and play some music. V4A should now be processing.

If not processing, again, see find my previous post to troubleshoot.

If the driver won't install, manually delete system/lib/soundfx/libv4a_fx_ics.so and reboot. When back in Android, start ARiSE again. It will ask you to install driver. Do this and reboot. You should be fixed.

SuperSU doesn't usually brick a phone. Please state the exact problems that happened after you flashed it.
[Android Software Development] JBNex:
Is your V4A driver installed? I fixed it by disabling Arkamys I'm Settings -> Apps (need fast fingers), rebooting, launching V4A, installing the driver. Then Re-enable Arkamys, reboot.
[Android Software Development] Papdya:
I got V4A working but RIL is broken. It didnt recognise CM root so i flashed SuperSU. which broke the RIL . This is happening on all of CM 14.1 Roms.
[Android Software Development] shaggyskunk:
Not ALL 14.1 Roms - SuperSU v2.78 Stable and v2.78 SR5 work perfectly on my device and Rom.

I've heard of some people having issues with SuperSU and WiFi but that's about it.

Sent From My SM-N910W8 ??
[Android Software Development] Papdya:
I dont know maybe its device specific cause many ppl in my device forum have this problem after flashing SuperSU.
[Android Software Development] mohand06:
Permissive 14.1, 7.1.1 roms don't need at all SuperSU to get alpha 8-8 fully processing (V4A and Dolby), only superuser.
[Android Software Development] Alex Tian8800:
No,if you flash it as zip. But if you install it from Play Store and install su manually from app, after reboot you get bootloop!
[Android Software Development] docnok63:
The ARISE team is always talking about/messing with Android sound behind the scenes into the early hours of the day and, after a brief nap, I woke up to find that the man himself, [MENTION=4445176]guitardedhero[/MENTION], had chimed in on the subject. The man knows literally every sound mod there is for Android. So, he thought of one mod that was a possibility and one that he knew for sure worked. It's called Dolby Digital Plus (DDP.) I did a quick Google search and found this thread. After examining the .zip, I knew it was going to break my perfect ARISE install, but now my curiosity was peeked and decided to flash it anyway. Sure enough, Ark started crashing like crazy (had to freeze to fix) and because the zip changes the audio_effects.conf, my effects chain was broken except for V4A. I fired up DDP and it worked like a charm. So I dug up my BT headphones out of the closet and paired them with my fresh 7.1.1 install. Naturally, GH is 100% correct and DDP sent sound to my cans with Surround Virtualizer still enabled!

I'll be pulling apart this the DDP zip today (after another nap (or two)) and see if I can't properly integrate it with ARISE's effect chain and make a flashable .zip. It may have to be a manual install. I'll keep ya posted.
[Android Software Development] docnok63:
Yes, this is the major progress I posted about earlier. We're currently integrating our updater-binary with the rest of the mod and testing it. It will have to be it's own Deut version, so it might not coincide with Alpha 9's release.
[Android Software Development] ModelCitizen:
What exactly did you edit? Mind sharing it? I have the regular Pixel
[Android Software Development] shaggyskunk:
Great to hear this news from a Team Member! ðŸ‘ðŸ˜‰

Sent From My SM-N910W8 ðŸ‡¨ðŸ‡¦
[Android Software Development] marianoasis:
im trying ARISE Sound Systems Deuteronomy 2.3.3
[Android Software Development] Omega Kaos:
http://cloud.tapatalk.com/s/5851487d35fad/update-binary.txt

This is the only file I edited, just delete the .txt extension and replace the one in the zip with this

Hope this helps
[Android Software Development] Omega Kaos:
Well I am still playing with the updater-binary and looking to create an if else statement so one script will work across all boards.

I don't know how the dev team are doing this but if I can get it to work I'll drop a mention

Quick question though do all 7.1.1 ROMs use the same partitioning scheme as the Pixel or is it just going to be the new phones?
[Android Software Development] docnok63:
I had this happening on a ROM that I was using before my current one. After a couple weeks of flashing almost every version of SuperSU and Superuser I could get my hands on, I figured out that I had to use phh's Superuser. Since you said that ARISE doesn't work with the ROM's pre-installed superuser, I suggest you follow the directions I posted and then disable the built-in superuser. You'll have a proper root + RIL!

Errrr....so why would you use the Play Store method if flashing zip works?

This is usually correct with the permissive script built into the mod, but [MENTION=5923481]Papdya[/MENTION] stated it wasn't working for him. Apparently, just like the ROM I was using before, the built-in superuser was not properly/completely installed by the dev.

Go to sleep bud! :silly: (I at least took a brief nap...) I still have irs and profiles to give you. Hit me up on TG later....
[Android Software Development] ModelCitizen:
Do you mind PM'ing me the zip? I couldn't get it to work after replacing the file.
[Android Software Development] Omega Kaos:
As soon as it's uploaded to GDrive I will post the link here for everyone ?
[Android Software Development] wayneywoo:
Awesome, thanks!

I thought I'd give AM3D a go so copied the relevant _YES props file to system then flashed the zip.

AM3D was there and was processing but V4A wasn't processing nor Atmos. Grumble...

So made the relevant change to audio_effects file, reboot and still V4A/Atmos not processing. Hmm....

Ended up commenting out the AM3D lines in audio_effects, reboot and voila, V4A and Atmos working again.

I suppose my question might be, with V4A 2.5.0.5, is Atmos/AM3D necessary? Yes, it's a personal choice as to the sound you want and I've not had the "whole audio system work" but technically, what can they do that V4A can't do on its own? Maybe add on top to the limits of V4A? Kinda like V4A is the cake, nice and good enough on its own, Atmos/AM3D might be the icing? Not necessary but can make it better?
[Android Software Development] Omega Kaos:
Here's the zip file for marlin/sailfish

https://drive.google.com/file/d/0B9em77LaJfYmZWdVMjhLNmVfckE/view?usp=drivesdk