yashsingh1/xdaforums huggingface dataset:
[Android Software Development] guitardedhero:
My post explaining the sudden SQ degradation beginning with RC9 must have been easy to miss. Here's the explanation:

After RC8.8 a generous member of our Telegram group provided me with the current Fiio™ X7 portable media player system dump. This came out of nowhere but also seemed to come at the perfect time as I was already planning to complete Exodus very soon. Those familiar with these devices would likely have the same feeling as I had, thinking these libraries and effects could only enhance the sound system.

RC9 denoted the first appearance of Fiio™ X7 libraries and effects. More than enough testing and reporting was able to confirm that this addition crippled the sound system. RC9.1 was an experiment to see if the SQ degradation could be traced to something else or even to the recent rom commits that would cripple a sound system build that was satisfactory on the previous rom build.

RC9.2 denotes the complete removal of all traces of Fiio™ X7 content, and is a natural update from the RC8.7 build. What we can take away from this is that the larger and more complex our library base becomes, the more temperamental it can be when introduced with additional libraries and that combining quality libraries more and more and more will never guarantee an enhancement or a positive result.

I've been working with countless libraries over the course of this project, more than ideally should be used - even the remaining ones currently in the system. I said long ago several times that removing a library can be just as impactful to SQ as adding a library can be. I've debloated several different combinations and the monstrous base of libraries currently used seem to be the minimum required to me at this point, as crazy as I know that sounds lol! These libraries account for over 135MB of the sound system so there are so many possibilities for incompatibility, bootloop, functionality loss, unusual behavior, and many other undesirables. The fact that this sound system achieves the SQ, compatibility, and functionality it has is nothing short of remarkable and unlike anything ever seen here before. Many mods under 20MB when compressed fall short in each category above to Exodus. Clearly, this is the difference rigorous research and attention to detail provide. Even then, that research is limited to testing environments and that is why every one of you have been such a crucial component throughout this entire process. Exodus 1.0 coming very, very soon so give these final test builds a full workout. :good:
[Android Software Development] xxbabiboi228xx:
Your right i noticed as well Alsa is not in 8.7 because i do not notice the usr folder nor do i see the alsa files in the bin folder as well. The last RC Build to have Alsa implenented was RC8.5

8.6 and on Alsa was removed.

---------- Post added at 02:54 PM ---------- Previous post was at 02:49 PM ----------

As Ben Feutrill has qouted in a post i have read the less files the more impact the sound mod will have. You dont need every lib known to man just to have a good sounding audio mod.
[Android Software Development] Jarheadflip:
[MENTION=4445176]guitardedhero[/MENTION] didnt know if you noticed my post cause i know you get a lot questions lol
[Android Software Development] Reechings:
Do the tweakprops included in the aroma zips get updated often? I always use guitardedhero one and am wondering if I need to update it every time I flash the new RC version? Thanks and is there supposed to be a GUI for the new Atmos or is it all behind the scenes? Cheers
[Android Software Development] wrongway213:
Kanged your sig [MENTION=5079472]sonophilos[/MENTION]! Thanks man :p
[Android Software Development] guitardedhero:
I realize every library is not needed, and it's not quite as simple as less is more. If I remove all but one library from the sound system I promise you it will not be a thunderous, crushing sound update. I was trying to explain that I've weeded all the libraries I am comfortable removing and the current base suffers in my opinion when weeded further.

Sure man, audio_policy.conf and similar files will help of you can provide those. I believe HTC has quite a bit scattered throughout so a system dump minus /app and /priv-app might be easier for you. Send me a link once zipped and uploaded. ?
[Android Software Development] Deadeye*:
I think what i felt was missing is more detailed change log. When V9 was released i did not notice any change log regarding use of Fiio.

Maybe in future updates would you guys able to post more detailed change log?

[MENTION=4445176]guitardedhero[/MENTION] regarding static noise on HiFi mode when recording video. I have flashed V9.2 without tweakprop sill have same issue.
[Android Software Development] :
No problem, enjoy. Here's the original image I used and the code for making it link to this thread:

[URL="http://xdaforums.com/android/software/r-s-e-sound-systems-auditory-research-t3379709"][SIGPIC][/SIGPIC][/URL]

[MENTION=5357345]ahrion[/MENTION] [MENTION=5648292]aki_007[/MENTION] [MENTION=5605825]Ben Feutrill[/MENTION] [MENTION=4445176]guitardedhero[/MENTION] [MENTION=6320543]RatchetPanda[/MENTION] [MENTION=5463312]smeejaytee[/MENTION] you're welcome to take and use these too, may as well have the Team with the same signature. (Did I miss anybody...?)
[Android Software Development] :
RC9.2 Aroma v2

Changelog

- Fixed set_perm

Notes

- Amazing build! Bass is great.

Link

https://www.androidfilehost.com/?fid=24591023225177385
[Android Software Development] angiest:
Saw this riiiiiiight before flashing 9.2.
[Android Software Development] harpin14789:
Guitardedhero has mentioned in previous posts that a changelog will be provided once 1.0 gets released. This thread is called Audio Research in Sound Enhancement. So guitardedhero conducts a lot of blind test to get an idea of what's good and what's bad. If the changelog was given then the results would've been skewed.

Since this is a research thread, if people are not comfortable flashing test builds they should flash a stable version and wait for 1.0

This way, the dev can get a clear idea what the additions and removal of files exactly does. :)

I asked the same question as you a few days back. :svetius:
[Android Software Development] Deadeye*:
Thanks going to try on my H10 but noticed that on first screen it says RC8.7 :)
[Android Software Development] xxbabiboi228xx:
I got what your doing your weeding out little by little in another words TROUBLESHOOTING!!!
[Android Software Development] mohand06:
[MENTION=6320543]RatchetPanda[/MENTION], no add-on zip this time? One more thing: previous Aroma allowed me to have AM3D Zirene working for the first time, why not in RC9.2 Aroma? Thanks all the same, I like the aroma flashing.
[Android Software Development] Deadeye*:
I'm just thinking if for example having more detailed change log lets say what code of line has been changed or something similar maybe we can do these test better? Let say if something does not work and we know whats changed we can try to fix and find faults ourselves and thus would relieve pressure from ARISE team?

---------- Post added at 11:56 PM ---------- Previous post was at 11:49 PM ----------

Flashed Aroma but no sound. Settings i used just chosed HTC and everything else as default. Dolby + that other app where opening and no FC.

When flashed 9.2 (not Aroma) sound is alive.

Going to flash couple more times without any Dolby, and report back.

BTW i'm on HTC 10 LeeDroid 2
[Android Software Development] :
Sorry forgot to change.

AM3D is still included.

Once 1.0 is released, we are hoping to open a github so everyone can see changes made in real time. This would also show that our work is original.
[Android Software Development] smeejaytee:
That was actually a genuine question lol, been using either stock HTC or PA for years, I did used to use player pro as I liked the skins and I recently tried jet but the free version wasn't good, it did look like the full version would be much better.

The thing I find with PA is although it has so many great options and settings half of them I don't touch really as v4a is in my opinion far superior in terms of customizing the parameters to your personal taste, also anther thing is all the good options are in the Alfa edition and themes aren't supported.
[Android Software Development] tcat007:
All errors fixed! IMO sounds about the same as 8.7, so ? Noticed that crackles happens in Pandora unless you switch governor to ondemand. GM sounds good w/o changing it. I seldom use Pandora and haven't checked many previous versions. Eagerly awaiting 1.0!
[Android Software Development] Deadeye*:
Installing 9.2 Aroma. Take 1

Version: LP/MM

Manufacturer: not lg, htc

Tweakprop: guitardedhero

Dolby: neither

AM3D: no am3d

DTS: System install

RP: No don't install (i hope i'm not)

Restart

No sound :(

Nandroid restore

Installing 9.2 Aroma. Take 2

Same as before, only changing:

Tweakprop: no tweakprop

DTS: Data Install

Restart

No sound :(

Going to install V9.2 (non Aroma) it's seem with Aroma i'm having problems.
[Android Software Development] guitardedhero:
Testing phases are mostly void of changelogs and relevant information in the OP. This is all by design and yields the results I need to maximize the testing phase to provide a Stable build that surpasses standards found anywhere. RC9 with no changelog produced the most efficient and useful feedback than any included changelog would have provided. Fiio™ X7 libraries and effects gets everyone's attention and I can almost guarantee that the brutal reports would have been slightly more forgiving knowing that some really appealing stuff is inside creating an urge to try not to dismiss it so quickly and try to make it work.

It's not quite so cut and dry like that but it's been incredibly consistent throughout my projects here at XDA. I've been incredibly fortunate to have the success I've enjoyed at XDA because of an enormous user base that test my projects proficiently. There is no reason to deviate from what has been incredibly helpful. The only alternative is to go the other way and provide at least some info with a test build, but there is no way I'll be convinced that doing so would make any testing feedback more useful.

Finally, I promote the user's involvement and learning more than anyone else I am aware of. Long before my first flashable zip I stressed the importance of extracting and examining the contents of any zip you might flash. Changes made to a test build without any provided info can be found if examined carefully or might even be obvious upon first glance. It's the same reason why guitardedhero_tweak.prop will never have a name change or version number in the title. I want the user to examine the tweak.prop for any changes they might want to try. Tweak.prop is a 100% user activity, so I prioritize the means for the user to master the tweak.prop component as quickly as possible.

The more you look and the more you notice, the quicker you learn. Think about it this question and do your best to come up with an answer:

When viewing a changelog and nothing else over the course of a project or rom, what knowledge and mastery is gained that can be applied to everything in that project or rom besides the changelog?

Stable builds include a complete changelog as well as updates that follow. Testing phases are completely different and should be handled completely different. :good:
[Android Software Development] vibrantliker:
Does volume seem a little low?
[Android Software Development] tcat007:
Sounds exactly the same as 8.7 to my old ears. Loud at about 40%.
[Android Software Development] Deadeye*:
Thanks Hero and again thank you all ARISE team for this great MOD.
[Android Software Development] :
:good:

:crying:

Nah seems fine. Make sure to delete old Dolby stuff in vendor
[Android Software Development] guitardedhero:
I know this is not what you were hoping to hear and this is not a dismissal of the work RP invests into the Aroma Installer but I simply cannot consider a bug report without the following criteria having been done:

Dirty rom flash

No modifications to the rom's build.prop

Confirmation of 220MB+ available /system space

Flashing a zip that I have released except for an Aroma zip I may have released

No flashing of tweakprop.zip or Add-On's

If this sequence of events results in undesirable behavior then the behavior is isolated to the sound system zip or something simple like ungranted App permissions, Selinux environment, root management app, or native audio effects provided by the rom. :good:

This also ensures that Aroma is built using a bug-free sound system which otherwise, existing bugs can very likely be exaggerated by an Aroma installation. :good:
[Android Software Development] ahrion:
Does XDA labs display signatures?
[Android Software Development] Lucki_X:
[MENTION=4445176]guitardedhero[/MENTION] everything works good on version RC9.2 for me nevertheless I still notice low volume of sound in poweramp. I'm able to adjust it a little by change setting in "audio output options", especially by disabling "direct volume control" but I don't have to do it without flashed your mod. Other apps and system sounds are louder than on stock system.

Listening experience is amazing. Bass are great, mids and highs are clear.

Sent from Honor 7_PLK-TL01H
[Android Software Development] vibrantliker:
What stuff? I only have dax-default.xml in the system/vendor/etc/dolby folder.
[Android Software Development] Deadeye*:
No modifications to the rom's build.prop - i have flashed the standalone V9.2 and it's working fine

Confirmation of 220MB+ available /system space - checked via TB System ROM 1.73 GB free

Flashing a zip that I have released except for an Aroma zip I may have released

No flashing of tweakprop.zip or Add-On's[/B] - excluded any addons that Aroma had.

I'm open to suggestions, but please note i'm not flash guru, i'm still trying to get my head around what all the tweak props and other stuff do and how they work.
[Android Software Development] AquilaDroid:
On v9.2 - N5X, PureNexus (latest) ElX kernel, I get the crackling unless I switch to on-demand CPU governor. Other than that, all is good (Aroma install, all defaults)
[Android Software Development] Deadeye*:
Could you try another player just to test out, i'm using BlackPlayer, when i had PA alpha i did noticed lower volume.
[Android Software Development] Lucki_X:
In other apps and players I didn't notice low volume.

I don't complain I just wanted to write that I noticed this weird thing. [emoji1] [emoji1]

Sent from Honor 7_PLK-TL01H
[Android Software Development] vibrantliker:
deleted
[Android Software Development] scoobyjenkins:
Tried aroma for the first time with this version, holy cow, dat bass!

Tapatalked that shiznit.
[Android Software Development] vibrantliker:
Can I flash RP-Extras-v3 over your Aroma RC9.2 V2?
[Android Software Development] BodhiBrock:
Dolby FC's when played through FiiO Q1 on pretty much every build...but works fine when headphone is connected directly to my Sprint HTC M9 running LeeDrOiD w/ Minimalistic Kernel.

Also, there is no more H/K option?

:sad
[Android Software Development] :
Nope it kinda stinks.

Nvm

:good:

:good:

No, this has been said many times it'd included in aroma!
[Android Software Development] mikera67:
Rc 9.2 works great! Only gripe for me is the bass a touch too strong. Took the leap of faith during aroma install, might try without that and try again.

Many thanks, keep the builds coming!
[Android Software Development] Jarheadflip:
9.2 is out id try that
[Android Software Development] guitardedhero:
If my memory is correct, every PowerAmp Alpha build had much less output than other players, including the stable PowerAmp. The Alpha regained normal, expected output in either the latest Alpha or the build before it. This was with the sound system installed the entire time. Which Alpha build is installed? The Alpha installed on my Nexus 6 with no noticeable drop in output compared to other players is Alpha 704. :good:

I'm not sure if I am understanding your experience completely. Are you reporting that everything works properly with the normal zip? Flashing Aroma results with no volume output?
[Android Software Development] yung40oz84:
I got error when flashing, gonna try again. These latest builds to seem lower volume though for sure I can tell that
[Android Software Development] guitardedhero:
Do you have ViPER Bass enabled in v4a? It's not widely known that enabling ViPER Bass at 3.5 or 6 dB will usually result in a lower bass output than ViPER Bass turned Off. I also recommend not using v4a's FIREqualizer except for maybe Speaker output. This can cause noise disturbances and untamed frequencies. I use Convolver as my equalization curve in v4a. :good:
[Android Software Development] :
Its the same thing as regular... Is liballegro.so needed? I think I forgot that in 9.2
[Android Software Development] mikera67:
Only thing enabled is output gain in viper. Might try convolver. Just flashed again without the leap of faith, last option of current aroma build, slightly better, gong to try a few things.....
[Android Software Development] harpin14789:
I back that, I am also using alpha 704 and have not experienced any low volume on my nexus 6
[Android Software Development] vibrantliker:
Could it be the AM3D ?
[Android Software Development] angiest:
Anyone have am3d working on N6? It launches but doesn't display anything. Just the title bar and everything else is blank. This is across multiple versions, currently on 9.2. I did dirty flash the ROM. my N9 works just fine. Both were installed using aroma. Everything else is working great.
[Android Software Development] dirtyreturn:
I hope I don't get reamed for this... I own a Nexus 6p and flashed aroma 9.2 and I had a significant increase in notification and media volume even at the lowest possible level. I had only turned v4a on slight along with eq at treble boost. Can anyone give some insight into why the volume is extremely loud? Almost forgot, during the aroma install I clicked yes for every app and guitardedhero's build.prop tweaks. Anyone have any ideas?
[Android Software Development] mikera67:
Don't have amd3 installed, when I did have it installed, the sound was always off to me until I turned it off, prefer the sound from Dolby atmos.

Added a touch of clarity inside viper, only option I have enabled, getting to like the sound now.

I like the mods that sound great out of the box, to me it seems the more I try to shape the sound with viper, the worse it gets overall, one song sounds great, another not so much. The last few builds for me are getting super close. Even the wife noticed today, and she could care less about this stuff, she asked why my phone sounds much better in her car then her iPhone, tried to explain, but all she wanted was to me to fix her phone like mine, she didn't like the answer, lol, told her to fix her phone we'd need to toss it out the window on the freeway and get her a real phone. That won't happen anytime soon
[Android Software Development] mrrocketdog:
maybe this

http://xdaforums.com/showthread.php?p=67541485

ty [MENTION=4445176]guitardedhero[/MENTION].:5:

"err on the side of kindness"
[Android Software Development] tcat007:
Been mentioned several times. If you don't want them loud, just decrease output gain in v4a. I'm at -8db, gh suggested -14.
[Android Software Development] ephexxis:
not that i've seen, just predefined bylines.

semirelated: sometimes I'll follow a "mentioned" or "quoted" link and the post will only display my quoted material rather than the persons follow up even though the link in my inbox has a preview of the comment. friggin aggravating
[Android Software Development] xxbabiboi228xx:
Maybe #dolby.ds.volumeleveler.state= is ON

with the tweak.prop your using

To disable it just put # symbol in front of it like you see above or type off like you see above or do what

Tcat007 said.
[Android Software Development] ephexxis:
that's an interesting analogy, the convolution as an eq curve. that's pretty much how i think of the DDC "correction" filters. i use them as like a "weighted" curve relative to my output hardware, using whichever one provides me with, to my ear, the cleanest werighted baseline coloration and levels to then apply effects to.

man i love this stuff

---------- Post added at 01:28 AM ---------- Previous post was at 01:07 AM ----------

so as a little experiment in isolating my neutron/arise/android/java driver ****ery, after setting up a clean system restore with the new temasek cm build for my phone, i decided for the lulz to roll way back to Exodus v .8.9, the last version i felt comfortable publicly evangelizing to all of you lovely people.

for shame.

for anyone who was wondering, don't bother looking back with rosy tinted glasses and a yearning pang of nostalgia for the past. what we once thought was the end all be all of quality is little more than a hollow shell of what has since been acheived. i spent all of 2 hours reconfiguring, trying to recreate the sound which i had been so sure was real in my memory. i even flashed old tweak props of mine from back then (back then? its been literally less than a full week) and went so far as to import the k4 dolby system into that version of the mod just you know, because i could. nothing even comes close to resembling the latest iterations (though admittedly i haven't tried anything post the removal of ALSA out of an irrational fear of change and resistance to making this forced adaptation). i feel so jaded now. oh and neutron is still giving me the finger.

/situation report

tldr; if you are wondering how .8.9 sounds now, don't. drink a glass of water instead it'll be a better use of your time
[Android Software Development] jass65:
Its DD+, thats what happened to me.Just change the settings in the dolby app.
[Android Software Development] xerxes1511:
I flashed the xplay3s zip and i must say awesome and louder ?
[Android Software Development] cmo220:
It is in the Exodus .zip file. Extract that to SD card, rename to tweak.prop before flashing.

Since you already flashed you can still extract and rename, then flash the tweak.prop zip file from OP.
[Android Software Development] ephexxis:
same bose set up in my car and i find the atmos variants to be ideal, even without gui control (x86 lel), are you perhaps also a member of teamMAZDA???

:svetius::highfive:
[Android Software Development] aki_007:
What did you Create this time? Do you even have an idea that you have ported a part of DTS-X the latest audio tech after atmos.

Me and Ahrion were trying to port the DTS-X dsp but failed everytime and left the Project. Later He included sone Libs in his own audio mod Tweakdrypt. But you exactly did What we didnt think of. You used the common sense.

What an amazing performance, with am3daudioenhancement , Dolby atmos. Just perfect for me.

Try to use a patched Version of dts-service apk from vivo framework.

Also only Xplay3s has DTS-X.

You are so great... Love you...

Listening to my fav songs for more than 2 hours.
[Android Software Development] guitardedhero:
No, I took a look to see if I could create more space but I didn't see anything I could comfortably remove.

And you are now booted with your previous setup?

It does sound freaking sweet! :highfive:
[Android Software Development] Mar-cel:
Thanks ,I have installed but there is no Dolby Atmos app? ?

Gesendet von meinem SM-G900F mit Tapatalk
[Android Software Development] felipe4:
Yes. I made a nandroid backup and restored it.

Enviado de meu ASUS_Z00UD usando Tapatalk
[Android Software Development] dingermtb:
Sweet is an understatement. Although, it came a week too early. I'll be home alone for 4 days (Friday-Monday) next week. Wife said "you can test stuff till the cows come home" I looked and her and my son (wrong move, lol). But i'll have alot of time and loud music and can test, test, test?

Sent from Outside the 9 using my Zombiefied Exodus OnyX
[Android Software Development] K.khiladi:
Just installed on Moto X play running RR that had previously installed v4a. Just flashed it over the top of that and everything's fine.

I feel more clarity now.

Automated reply by JARVIS