yashsingh1/xdaforums huggingface dataset:
[Android Software Development] mohand06:
Again, did you try dirty flashing 2.68 or 2.7 over 2.4 (what I did, say, as an update and to overcome that V4A driver update issue)
[Android Software Development] chikimonke:
No I have not, and as I understand it, if I did that, I'm not necessarily going to be running the fully intended system because the files would have changed.
[Android Software Development] 777.300:
Which .prop file do you mean?
[Android Software Development] darkstar73:
Has anyone with a Nexus 6 been able to get AM3D to work? If so, what steps did you take?
[Android Software Development] mohand06:
Try it and let your ears tell the difference or the change if any
[Android Software Development] ipmanwck:
After some testing on all the recent updates personally I still love 2.3.3. Amazing work guys. I went back to stock to compare and the difference from stock to 2.3.3 sound almost made my ears dance. It was quite amazing to hear the sound quality in this mod. Can't thank you enough.

I am currently running complete basic 2.3.3 with nothing apart from turning it on ? the sound mod is that good...

For anyone who has not installed it yet here is what I did on megapixel rom.

1. flash 2.3.3 in twrp

2. Reboot

3. Install selinuxmod

4. Change selinuxmod to permissive

5. Delete audio_effects.conf

6. Reboot

7. Open viper4arise and turn on master power and cry when you hear the amazing sound..

Warning - ears may bleed or dance depending on volume level ?

That has worked for me every time on megapixel rom but can't comment on any other. Peace.
[Android Software Development] gubacsek:
arise_addon.prop

The one that you find in the ARISE zip and put into the /sdcard folder. You can set some stuff there, like the "remove deep buffer" option.
[Android Software Development] guitardedhero:
Sorry to be so late addressing your issue. After installing, please save the log and confirm the existence of /system/etc/audio_effects.conf symlinked to /vendor/etc/audio_effects.conf. :good:
[Android Software Development] seabro01:
Got it working on 6P running DU by clean flashing latest DU Rc, Dynamic Gapps, 2/7 Flash kernel and SuperSU SR3 v2.79. Then I used the OLD Deut 2.7 modular Aroma installer zip. Only selected V4A 2.3.4, ICE 2, deep buffer, profiles and toolbox.
[Android Software Development] chikimonke:
Would that be while I'm still in TWRP? (I JUST rebooted and reflashed and am in the process of rebooting to system now) Or can I check that once I've booted up some how?
[Android Software Development] guitardedhero:
Which zip are you using?
[Android Software Development] chikimonke:
2.70 non-Aroma. I'm in the telegram support if you want to see everything we've tried so far. I've had the same results with 2.68 Aroma and non-Aroma too
[Android Software Development] sean222:
Nexus 6P and DU Rom.

2.70 made my night! Been tinkering with audio_effects.conf / vendor all week pulling my hair out.

Just tried 2.70 and Viper is processing right off the bat!! I'm a happy camper. Thanks guys!
[Android Software Development] VictorLapin:
To bullhead users experiencing the headphones bug:

Processing works fine here for the last couple of days. Recalling my latest actions that could fix it, I can think of the following:

1. I've deleted Viper4Android folder on /sdcard via TWRP file manager and let viper create it from scratch (didn't need all the profiles, just my own one).

2. I've switched off the convolver.

Try these, maybe it'll help you.

I use arise 2.68 with viper 2.5.0.5, no Dolby add-ons, ice sound excluded from installation and deep buffer removed.
[Android Software Development] radz_:
Is there a headphone bug?

After flashing 2.68 an test with phone speakers all seems to be working fine.. but once i plug in my headset everything is not working, dolby atmos, ddp, viper,.. breaks the sound sometimes, when I go and unplugged the headset speakers not working too now..

Note 4 device using ported Note7 ROM..
[Android Software Development] docnok63:
Acknowledged in the Troubleshooting Guide with possible fixes and another possible solution in the post above yours.
[Android Software Development] mehulchirania:
[HELP]

SELinux set to permissive. Busybox installed. Root permissions granted. Still not working. Getting the I/O driver issue.

Device: Kenzo [Redmi note 3]

ROM: Lineage 14.1 official latest weekly

Kernel: [Radon]

PS: The issue persisted before flashing Radon.

[/HELP]
[Android Software Development] guitardedhero:
I apologise, there was a typo in the symlinking of /system/etc/audio_effects.conf to /vendor/etc/audio_effects.conf causing the entire /system/etc directory to symlink to /vendor/etc/audio_effects.conf.

This has been corrected in the 2.71 version of non-AROMA, AROMA did not carry this typo. :good:
[Android Software Development] chikimonke:
Just an FYI, it seems the ice presets always install deepbass, no matter which one is called in the prop. This was on 2.70a.

Looking at the prop, I'm going to guess it's that the preset options aren't commented out, because deepbass is first in that list.
[Android Software Development] :
I'll upload a fixed one thanks for catching!!
[Android Software Development] xerxes1511:
Thank you man [emoji2]

It works
[Android Software Development] Kusoo:
Any way to stop the cracking sound? Always happens when I install Atmos GUI (and ON, ofc), the thing I do is select a higher CPU Min Freq (600Mhz doesn't crack at all) but I don't really like this solution, the other way is choosing ondemand, but that governor kills my battery, so is dicarted.

I have also tried setting a higher number on this line insde the tweak.prop, but stills crack when CPU Min Freq at its lowest :(

# Set this value higher in powers of 2 if you experience cracking, popping or skipping even with Ondemand gov.

audio.offload.buffer.size.kb=2048
[Android Software Development] JellyTooth:
Don't forget fixing the Dolby GUI s. Too cuz they dont install with aroma cuz they dont have a permission in the updater script
[Android Software Development] :
That's actually wrong, it's not that they don't have permission (you don't need permissions inside the zip?), it's that they're extracting /system and /vendor to /system so it's making basically a duplicate system inside of the system with only Dolby in it. I just fixed this. Uploading soon after I test it some more.
[Android Software Development] tcat007:
May just be my old ears, but I just don't care for GH or Sonophilos profiles, but find 9.5 superb. Here's my profile. Place "tcat001" in profile folder, and the two irs in kernel if you don't have them already. Sounds great on my s4i ear buds, and speaker profile adds some volume when just listening to phone.

https://www.dropbox.com/s/ncg5gslyzpg5sk7/tcat001.zip?dl=0
[Android Software Development] dingermtb:
Holy SoundWoW guitardedheroman...Just installed 9.5 with XPlay3S Preset and alternate Dolby On tweak.prop with my ZombieSin profile this morning, and I can't believe my ears. Utterly speechless. I absolutely LOVE this setup. As much as I love this setup though, will do more testing with Exodus Preset and other tweak.prop files?

Sent from Outside the 9 using my Zombiefied Exodus OnyX
[Android Software Development] FPSUsername:
Try SIO(plus), BFQ or FIOPS scheduler and put your read-ahead on 2048 (for 16GB or more), if 8GB use 1024
[Android Software Development] wrongway213:
I run a kernel that has a custon OnDemand based governor to solve this issue - on the Nexus 6 I run B14kb1rd Kernel, and it has both Nightmare and Darkness governors - Ondemand does not need to be used, the governor must simply be based on ondemand. Both of those work wonderfully and are MUCH more battery friendly than ondemand itself, which I myself cannot stand. If on a device with a kernel that has those governors available, I would check ino that. As for your min-freq solution, I know you don't wanna use this but I can tell you at least this - you are going higher than necessary. 422 absolutely stops the crackling at min freq and obv is a bit easier on battery than 600 - I would still recommend a custom ondemand governor if available to you, though.
[Android Software Development] mohand06:
Thanks [MENTION=4445176]guitardedhero[/MENTION], very good aroma installer, works fine in twrp 3.0.2-1. However, even though I choose to install both Dolby, there's none in the drawer and I find myself with 2 DTS DCC service: one in user app (I moved it there after fc in 0.9.5) the other as system app
[Android Software Development] Roi007leaf:
Looks like [MENTION=4445176]guitardedhero[/MENTION] fixed it already in his revised edition
[Android Software Development] :
I'm uploading one soon that will fix Dolby.

He didn't. If he did I wouldn't be fixing it :good:
[Android Software Development] Kusoo:
I installed Atmos GUI using the previos ARISE builds, where you can flash the Atmos GUI
[Android Software Development] xerxes1511:
One last question

Must I flash a preset zip after arise zip and before the tweak prop or can I flash arise zip and then the tweak prop zip?

Best regards ?
[Android Software Development] :
Simplest solution: don't use Atmos GUI. :good:
[Android Software Development] evilryry:
Just want to share my own profile I've tweaked with time of my use with viper over the last couple years. It's loud all around and bass heavy, probably best suited for loud music lovers bass lovers with good headphones/speakers that can support the bass and stuff. Might not be liked by some people, or those with lower end headphones. Just wanting to share. Any thoughts about it are welcome. I myself use V-Moda Crossfade Lp headphones and I feel for my likes, which is mainly rock and metal, it sounds good. Extract the folder to profiles folder in viper folder. https://www.dropbox.com/s/lmydqmss7fnfcoz/Evilryry.zip?dl=0
[Android Software Development] :
Thank you for your very well articulated criticism. I'm currently working on testing my tweak.prop I've updated to include guitardedhero's changes/updates, allowing the newer libs and their settings to be tweaked as well. The idea is absolutely that my prop be presented as an alternative which includes all the same default props for functionality as well as some extended/optional props I've been experimenting and testing with.

0.8.9-0.9.4 in particular brought to light several compatibility issues caused by tweak.prop and by my tweaks in particular, which I hadn't noticed because they're all operational on my device. This is why we have testing passes like this, and I'm grateful for the feedback I received which allowed me to create a more compatible tweak.prop by default and separate the potentially unstable tweaks into commented-out, optional settings for the users who take the time to follow every update, read every change, actually read the tweak.prop before flashing...etc.

I agree that a more condensed way of going about this is needed. I might suggest, given how similar guitardedhero's preferred prop is to my previous prop, that we do simply assimilate it into "guitardedhero / Default Edition" vs "sonophilos / Testing Edition" or some such. The separation of Dolby ON / Dolby OFF seems the least significant difference at this stage of development, but FWIW my setup still has these props included and set to "true", but commented out, requiring a user to consciously turn them on (and preventing users from flashing without reading and wondering why they have no headset volume).

Again, thank you for your detailed thought about this. I'll be in communication with [MENTION=4445176]guitardedhero[/MENTION] as we continue to work towards an official release about what we can do to make this simpler while still retaining all the benefit and functionality we're testing currently. I'll also be uploading an updated Testing Edition prop as soon as I've set up 0.9.5 and tested it myself. :silly:
[Android Software Development] Papeekruts:
we're on the same boat :)
[Android Software Development] :
Exodus 0.9.5 AROMA v2

Changelog

- Added tcat profiles

- Fixed Dolby installs

- Fixed TweakProp bug where it would install no matter what

- Fixed preset installs

- Added a couple more irs

Notes

- If you meet Dolby force close, delete /vendor/etc/audio_effecfs.conf and extract the zip and in Dolby system copy audio_effects.conf to /system/etc and overwrite the one there.

- I will try to add people's profiles as they are posted, please use the profiles thread though.

Link

https://www.androidfilehost.com/?fid=24562946973631083

Support me - login with social media here

https://www.anker.com/deals/tsh?ic=c5e5294b4a12c994293b
[Android Software Development] Kusoo:
Nope, that specific version (AROMA) will do all that for you
[Android Software Development] guitardedhero:
Thank you, I saw your report and looked into that as well but did not see anything amiss to cause that, unfortunately. It's possible that installing a preset that isn't part of an entire directory being symlinked unintentionally is key. :good:
[Android Software Development] chikimonke:
Check my edit above

Edit - Those typos you fixed now install properly, but I still get deepbass by default, even with commenting out the options.
[Android Software Development] guitardedhero:
I thought about that but the requirement for the DEEPBASS preset is the following:

use.ICEsound.preset=DEEPBASS

I was afraid that by commenting the list of presets, it might be confusing to users thinking # might be part of the preset value. If you imagine it from this perspective, however:

Contents in /vendor/etc will ALWAYS supercede those same contents in /system/etc

If DEEPBASS preset is EVER symlinked to /vendor/etc, no preset in /system/etc will ever have a chance.

The only way to allow a preset in /system/etc to have any effect in this scenario is to delete the symlink linking the entire /system/etc directory to /vendor/etc/audio_effects.conf.

Of course, it's easy to test your suspicion by commenting the entire list of presets in /sdcard/arise_customize.prop, but the information I outlined above is CRUCIAL to know given the impact that very small typo had in that version of the non-AROMA build. :good:
[Android Software Development] chikimonke:
So I did try to comment them out and it didn't make a difference with 2.71. That said, my initial issue with the driver not being installed is no long an issue, so that's fixed now.
[Android Software Development] guitardedhero:
Keep in mind, renaming a symlink will not break the symlink. Delete the renamed symlink inside /vendor/etc to be able to make any changes to /system/etc before the next time you flash your vendor image. :good:
[Android Software Development] chikimonke:
You've lost me, why would I need to do that?
[Android Software Development] 777.300:
Thanks for the tip, unfortunately that does not help. Unplugging and plugging my headphones in stops viper4android. Hmmmmm
[Android Software Development] guitardedhero:
Your initial installation after your last flashing of vendor image presented this scenario for you:

Contents written to and those previously existing in /system/etc were symlinked to /vendor/etc/audio_effects.conf.

If /system/etc/audio_effects.conf and /vendor/etc/audio_effects.conf both exist, ViPER4Android and similar apps will ignore /system/etc/audio_effects.conf in favor of /vendor/etc/audio_effects.conf.

In your case, /vendor/etc/audio_effects.conf was not an appropriate configuration file for audio effects. Rather, it was a symlink of a directory of over 70MB.

Renaming this symlink created a single instance of audio_effects.conf located in /system/etc, satisfying ViPER4Android.

However, the symlink still exists linking the initial contents of /system/etc, likely including the DEEPBASS preset.

Deleting the renamed symlink found in /vendor/etc should be sufficient to resolve your issue completely, allowing contents written to /system/etc to not conflict with anything in /vendor/etc, unless of course, files of the same name exist in /vendor/etc. :good:
[Android Software Development] Guidorio:
I'm on the last pure nexus and I got that V4A is not enabled, I was in stock earlier and everything was fine...any suggestions what can be? Thanks in advance
[Android Software Development] Roi007leaf:
Play some music?
[Android Software Development] Guidorio:
Yes I did but nothing changed
[Android Software Development] kyzn:
Enable it. I don't see the master power enabled in your screenshot.
[Android Software Development] Lycidias:
Can someone Please explain to Me what ICE Sound is? Thanks
[Android Software Development] raylogic:
What does removing deep buffer get us?
[Android Software Development] JaylanPHNX:
On some devices you need to remove deep buffer for viper to process on all apps.
[Android Software Development] mittalanmol22:
First i dirty flashed my rom to install 2.6.8 but when the rom booted, there was no V4A app....... Then i again dirty flashed my rom today and flashed 2.7 aroma and the same thing happened...... Why is this happening?

Am i doing something wrong in the process?
[Android Software Development] Guidorio:
Thanks for the help, I made a really newbie error ☺️ it works now!!
[Android Software Development] marcoly:
I would want to install Leviticus (I like it's sound) on Nougat (LineageOS 14.1), however it is working only in stock Music app, not in Spotify or YouTube (not processed by V4A/Dolby). Any suggestions?
[Android Software Development] guitardedhero:
It is critical to develop a habit of checking how much free, available /system space is provided after flashing a rom. I would confirm this value before looking anywhere else. :good:

---------- Post added at 05:18 AM ---------- Previous post was at 05:16 AM ----------

Remove deep_buffer from audio_policy. If you have downloaded our current AROMA zip, you could use it by skipping every step except for the deep_buffer step. :good:
[Android Software Development] psygarden:
2.68 & 2.70 are like alien level, kudos team.! But sadly each update robs me of something. 2.4 made me lose the better sounding Ahrion's Axon 7 Dolby Atmos. In 2.68 I lost DD+. And now 2.70 made me clean flash my ROM thrice just to make V4A work as it gave issues with Arkamys. Just reporting.

2.70 sounds amazing but somewhere I do miss Axon 7 Dolby. Guess I'll be back to 2.3.3 sooner or later.

Long Live ARISE.

Cheers.
[Android Software Development] mittalanmol22:
Yeah i checked the free system space after flashing the the rom..... It was about 120mb......and i only flashed sound system, V4A, arkamys, ice sound and the free space that remained after flashing all this was about 16mb and yet there was no V4A:(
[Android Software Development] Weetbix:
I've had this issue for ages on my 6P. Still haven't found a permanent way around it.

The only way I know of to get around it without rebooting with the headphones plugged in .... Is detailed in the troubleshooting guide in the zip file (in the core/support directory). It says:

Some say to use the older version of viper, but that never helped me...
[Android Software Development] clkehl:
How much system space is required for 2.71 core and viper 2.5 only? I have 92mb free and it maxes out system. 2.4 installs no problem and only uses 61mb total.
[Android Software Development] patrickbartalesi22:
I just looked up the definition of a swansong, The swan song (ancient Greek: κύκνειον ᾆσμα; Latin: carmen cygni) is a metaphorical phrase for a final gesture, effort, or performance given just before death or retirement.

This doesn't sound good.

I hope arise is not going to die.
[Android Software Development] Samsamxx:
I cant find any explination about the new updates, lile what is v70 and what is v70a?

And what do all mods do like xhifi, xperia sound arise mod, etc etc...

And can i install them all togother or not? Please somone explain short
[Android Software Development] marcoly:
I love you. I deleted raw & deep_buffer from sources in routes declarations, it's working awesome! Leviticus all the way :p
[Android Software Development] phoberus:
Our Onys don't support aroma zips. Use the modular zip with the prop file
[Android Software Development] Roi007leaf:
Deuteronomy is over, not ARISE
[Android Software Development] patrickbartalesi22:
Thanks for the clarification, I was getting worried there for a minute. I now understand your use of swansong. Arise up
[Android Software Development] Follow_and_Feel:
Hello all you lovely people and busy devs!

I don't wanna break the dev talk here with my questions of tremendous stupidity (lol), but have there been made changes to Esira in v2.71(a)? (You have no idea how much I crave for this player :D )

EDIT: Specifically the "refresh library" problem?
[Android Software Development] Shadowghoster:
Sadly not, Esira development is on hold atm.
[Android Software Development] gubacsek:
You have to flash the ARISE zip (non-aroma) after modifying the settings inside the prop file.

If you start flashing the ARISE zip, it checks this prop file and will install / set things based on what it is inside.

1. extract the prop file to /sdcard

2. modify contents, set up as you like

3. flash the ARISE zip file
[Android Software Development] mogul mobile:
Anyone know what the difference is between Swanson 2.71 and 2.71a?
[Android Software Development] mohand06:
Hail Leviticus!
[MENTION=4445176]guitardedhero[/MENTION], just noticed after reverting to that book for a test that Leviticus is really, really an AWESOME sound system on los 7.1.1, almost perfect (far better than on cm13) - V4A 2.3.4.0 alone or D.Atmos only already very powerful, but the two combined just blasting!
[Android Software Development] mittalanmol22:
[MENTION=4445176]guitardedhero[/MENTION] tried installing with 2.7.1a too and the system is not installing..............i had 120mb of space before flashing 2.7.1a aroma and had 16mb after flashing aroma with V4A 2.5.5, arkamys, icesound, and removed deep buffer.

none of the apps were even installed but yet the space was taken
[Android Software Development] Jsilver73:
This is awesome - surely worthy of a sub thread of its own as I'm sure it has got buried in this deep fast moving thread.

Of course I have an ulterior motive in that I'm hoping for updates as they roll out from Soundcloud :good::fingers-crossed::D
[Android Software Development] DEVILOPS 007:
It says error parsing package for me

---------- Post added at 05:32 PM ---------- Previous post was at 04:53 PM ----------

Could someone please tell me what ice sound config works for them on the nexus 6p. Thanks.
[Android Software Development] chikimonke:
I'm using 2 and the Pure preset
[Android Software Development] Ricardo89:
I installed 2.71A on my HTC 10. dolby atmos app is getting FC. i did check the permissive mode for nougat.

I also getting the message ''anyone call a doctor?'' during installation. Is this normal?
[Android Software Development] DEVILOPS 007:
On nexus 6p?
[Android Software Development] CynoMan:
I used 2.68 aroma version but there's no mention of any preset there during the installation. Would you mind telling where do I find the presets?
[Android Software Development] jugoslavpetrovic:
Where I can talk to Esira developers?

---------- Post added at 18:21 ---------- Previous post was at 18:18 ----------

As I remember I think it was the second choice or so in aroma. Then when u open the viper app in options you have load preset and there you choose. You can also make your own preset and load it after the same way.
[Android Software Development] liog:
I installed this mod but i have bootloop. How can I fix?
[Android Software Development] DEVILOPS 007:
How do I set the pure preset? I have installed Icesound and I am using 2. I see no app or anything to change presets. Thanks
[Android Software Development] psygarden:
Yes it's normal as you checked the last option (Fix permissions)
[Android Software Development] chikimonke:
Presets didn't show up until 2.70a I believe.