yashsingh1/xdaforums huggingface dataset:
[Android Software Development] DEVILOPS 007:
What about it? It looks fine. There are a lot of yellow links bunched together but I can find what I need easily enough.
[Android Software Development] Logan:
True xD but i like this golden op :) :P
[Android Software Development] DEVILOPS 007:
With modular you don't need to go through the setup every time you flash the rom so I don't get what you mean by the aroma is easier. All you do with the modular is type true basically and place it on your sdcard. That is literally it other than flashing the zip.
[Android Software Development] veez21:
Yeah, but unusual isn't it :D
[Android Software Development] Paschfire:
That's an issue with XDA Labs, this has nothing to do with the ARISE XDA Thread.

Using a Browsers, whether it be on Mobile or PC this issue is not present.
[Android Software Development] Zwulf:
True. No problem with Tapatalk though, just tried. Sorry. ;)

Gesendet von meinem Nexus 5X mit Tapatalk
[Android Software Development] Paschfire:
The decision to remove Aroma was not lightly taken and alot of thought was put into this fact, Aroma Will Not be returning to ARISE.
[Android Software Development] KirinRaikage:
Thank you so much for the latest 0605 build, now it works again for me !! With 30/04 it wouldn't do the "processing : Yes", don't really know why. I've tried both Enforcing and Permissive SELinux, installing the minimalistic setup (Core,V4A, Ice Config 2 with PURE preset)

It was the first time I've had such an issue since the beginning of ARISE. (Using ZUK Z1 with NucleaROM 7.1.2) But now you're making ARISE great again ! Keep doing your great work and don't mind haters, or if you do.... Make it so that they make you evolve as developers and hard workers !

Envoyé de mon ZUK Z1 en utilisant Tapatalk
[Android Software Development] leblvin:
I'm still unable to make Magnum Opus work on Freemdom OS for my OP3. Does anyone have a config that works that I can try?

Thanks!
[Android Software Development] DEVILOPS 007:
Yeah I agree with that.:)
[Android Software Development] KirinRaikage:
It was relevant for me, and I know mods wouldn't recommend doing that, but have you tried switching to Permissive SELinux if you haven't done so already ? It fixed the Abnormal status for me, but it wasn't processing (On the 30/04( build . Also, try the latest (06/05) build, maybe you'll have a workaround for that issue, at least, that's what has done the trick for me !

If you're using ICESound, make sure you use the 2 config.
[Android Software Development] leblvin:
I'm trying even with a barebones config (only 2.5.0.5 installed) and I get the Abnormal status. I will consider Permissive, but I'm hoping to find another solution!
[Android Software Development] Zwulf:
In my humble opinion this huge config file which you have to manually edit really is not a good idea. There should be an app where you can turn things on/off, switch settings etc. to be able to try out how several mods change the sound. It's extremely complicated to have to manually edit a file just to try out how a single setting changes the sound. And then have to reboot and flash again and then boot again. For every single mod. I know an app for that would mean a huge coding effort, but this config file really is the worst solution I could think of. I mean something like V4A itself where you have switches and could change the sound live and instantly can hear how it works out.

Edit:

That's exactly what's the problem. The suggestion to use a closed source root app is no real solution imo. Neither permissive SELinux is as it's very important for device security to leave it strict. Good sound is one thing but to be able to handle it easily is equally important, especially if there are so many options.
[Android Software Development] solis_f:
Even if you change the audio libraries through an app and other system files needed for arise tweaks to work, you would still need to reboot to load them. That's why it is a flashable zip in the first place. TLDR: live testing is not possible
[Android Software Development] leblvin:
I strongly encourage to develop this on your time, freely, and deal with the support of said app.
[Android Software Development] mohand06:
Wrong assertions since you didn't test the very latest Magnum 20170506. I wish you could listen to what I'm listening now on my A3, running 2.5.0.4 (2.5.0.5) and AM3D set off (to spare my ears on earphones)! I've been on this thread from the start and there's no way I'll go back to archived builds! And about handling, arise_customize.prop is far less hassle than aroma, one gets used quickly and, what, we're surely at the end of this sound mod way of installation, maybe soon an app, [MENTION=4445176]guitardedhero[/MENTION] only knows!:highfive:
[Android Software Development] Zwulf:
It's just a suggestion. I didn't request anything from anyone. But thanks for this meaningful argument.

Edit: I'll stop to post in this thread now as it seems like it's more about hurt feelings here than the subject I'm talking about itself. Sorry if anyone felt attacked or something.
[Android Software Development] leblvin:
It is meaningful. Look at that post count. Look at the number of versions on Android file host.

Think of the countless hours the devs have spent on this forum and developing. I'm certain they thought this through and figured that, for the time being at least, that was the best solution.

And I agree it's not intuitive or easy, don't get me wrong (you saw my post). But that's the price for incredible sound, and some are ready to pay that price.

Edited my tone, which was to passive aggressive
[Android Software Development] Paschfire:
There is nothing more complicated about the modular installer campared to Aroma.

You simply make your selections within the arise_customize.prop, save, reboot to recovery and flash the ARISE zip. With Aroma you made your selections during the recovery session, modular you do it before.

Having to edit the .prop file should take less than minutes, no difference than reading what each module had to offer within the Aroma Installer, you are convincing yourself it is harder than it actually is.
[Android Software Development] leblvin:
To his defense, I've never been able to make the modular install work, even after reading through the documentation in the zip and following this forum for months. And AROMA worked after 2 or 3 tries (because of ROM and ARISE interactions, not really a problem with ARISE itself).
[Android Software Development] Bryanx86:
Maybe this can help you....[youtube]KTugNE7ML-4[/youtube]&feature=youtu.be
[Android Software Development] Asiier:
People using OP3

Dirac is force closing all the time for me, right after my device boots. And AM3D just shows a black screen with nothing else.

Is does this happen with the OP3?

I'm using RR give Render Kernel and Magisk as root solution ( I have the needed module installed )

Currently, I'm running latest Magnus, but this has been happening since I long time ago, cannot tell when exactly.

I could provide logs is needed, but I want to know If this a normal behavior amongst OP3 phones
[Android Software Development] Lownita:
Is it possible that arkamys is causing audio lag when watching videos over Bluetooth speaker?
[Android Software Development] JaylanPHNX:
I don't have OP3, but I think I remember reading that you have to disable the built-in Dirac.
[Android Software Development] chikimonke:
In general you're going to get audio lag over BT. (Though that should be a thing of the past with the new BT 5 standard) but the more audio processing you add the more the lag is going to increase. I noticed on my own system that disabling most post processing the BT lag went to an almost imperceptible level.
[Android Software Development] leblvin:
It is normal, as yeah you should disable both Dirac system apps.

Also, can you copy your config file here? I have an OP3 and can't make Magnum Opus work...

---------- Post added at 02:25 PM ---------- Previous post was at 02:22 PM ----------

Thanks, I'll give it a look
[Android Software Development] Lughnasadh:
As for Am3d showing a blank screen, this may be caused by your rom not supporting its effect library. If you have Am3d installed you can do a dumpsys output and if the "Library am3daudioenhancement" doesn't appear, then you rom doesn't support it.
[Android Software Development] Asiier:
That's most likely the problem

Well, I just wanted to try it.

Is it like a game changer or something?

Might be the ROM you are using.

Right now I have enabled:

Core

Dolby Plus (As Atmos FC as well)

V4A 2.5.0.5

Arkamys

ICE Config 4 + HOLYSH*T

SD Card Permissions Repair

Remove Audio_Buffer

And I did uninstall stock Music FX

With that config, everything is working fine

I'm using a Custom ROM (Lineage Based) not Stock, So I don't have Dirac installed by default
[Android Software Development] Ninja Potatoe:
Dirac has been draining my battery for a couple of weeks. Took me a while to find the culprit as it was hiding in the kernel/android system wakelocks. Now, I really liked the audio boost/effects it gave to my music, is it possible to still have those effects somehow without the drain?
[Android Software Development] Lughnasadh:
Not being able to use Am3d is not a game changer at all. However, if you installed it you need to uninstall it or it will greatly drain your battery.
[Android Software Development] leblvin:
Well, after clean flashing my rom and using the ARISE build from yesterday, it seems I was successful and I'm now processing music of unequaled quality =D
[Android Software Development] A.R.I.S.E. Sound Systems:
Changelog:

[B]## Magnum Opus™ 20170506[/B] -

- More booted script corrections/enhancements.

- Enhanced the $SDCARD variable during recovery.

- Android O LDAC Bluetooth™ codec reassigned
as a satisfied scenario component.

- Experimental build with arisesound_setprop
disabled, enabling requires name change from
arisesound_disabled_setprop to arisesound_setprop.

##
[Android Software Development] justjr:
I should ask, in what regards the disabled setprop will affect the mod?
[Android Software Development] Asiier:
Yeah, I did uninstall it already

In your opinion, apart from V4A, is there anything else that really makes that great of a change?
[Android Software Development] Lughnasadh:
In my opinion, the sound quality really hit another level when they added Ice and Arkamys. But different phones, different roms, different ears, etc. give different experiences.

I am also using one of the earlier Magnum Opus builds that still has DTS in it. Having great sound with it, an excellent dumpsys and matlog outputs so I'm sticking with it for a while.
[Android Software Development] Asiier:
Understood, I might just uninstall Dolby as well. As it does bring much to the mix, just a more cinematic feel
[Android Software Development] guitardedhero:
/system/etc/init.d/arisesound_setprop is executed by /system/su.d/arisesound_services during boot, so changing the name to anything other than arisesound_setprop effectively disables the setprop script as it will not execute automatically nor by /system/su.d/arisesound_services.

I've been curious about testing with no setprop script for quite some time now. I've been borrowing my son's Moto G4 Play a bit while I wait on the OP5 to be available, which had a peculiar issue I remember being mentioned by a user more than once: Local FLAC media will trigger a "Cannot play file" or similar error when attempting playback.

As with all odd behavior issues, especially those out of nowhere, I performed the very first debug test action that we recommend in all scenarios:

Incapacitate the setprop script, reboot, and test for corrected behavior. This includes restricting any execute permissions already set for the setprop script or modifying its location path, either by renaming, moving, or deleting.

I felt users would be more comfortable renaming the setprop script than changing its permissions, additionally, installing the setprop script as /system/etc/init.d/arisesound_disabled_setprop during this experiment provides a visible indicator of it being "enabled" or "disabled".

This solved the odd playback issue I had, but it almost sounded even better.

Keep in mind, that results will vary widely. My Nexus 6 used throughout the entire development always benefited from setprop scripts. This Moto G4 Play absolutely sounded terrible with the identical ARISE installation used just before my Nexus 6 got destroyed. For example, it was immediately apparent (I cannot emphasize enough the importance of making a habit of using our Auditing section as part of your monitoring routine, checking v4a Driver Status, for example.) that the Android O libraries and /soundfx libraries as well as the Huawei component of the Core module were not recognized whatsoever, and therefore, were "broken" and pose a risk of affecting other components and even modules.

After testing confirmed that what was "broken" could not be repaired or be made recognized, I deleted those audio effects configuration entries and added Moto's libmmieffectswrapper.so entries, that are not currently provided by us, to restore the native AudioEffects functionality for this Moto G4 Play. I have no idea how many devices face similar support deficiencies this Moto G4 Play faces, but these need to be handled appropriately in order to achieve a most optimized sound system installation.

Of course, this can only come from detailed reports using our Auditing section found in the OP. :good:
[Android Software Development] justjr:
Awesome. Thanks for such in-depth explanation. I will certainly try, audit and report back on my Moto G3.

Enviado de meu MotoG3 usando Tapatalk
[Android Software Development] mohand06:
An apparent game changer, since it have an app in which you can adjust some effects to your liking is undoubtedly AM3D. Set off or combined with V4A 2.5.0.4, this mod most powerful!
[Android Software Development] hanut1:
Thank you for shining light on this eagerly waiting for O now ;)
[Android Software Development] guitardedhero:
Absolutely. I'm very curious what you find with your Moto G3.

In my case with the Moto G4 Play, the dumpsys utility was used to discover the absence of HPX/libeagle.so, Hpx/libhpx.so and huawei_processing/libhuaweiprocessing.so., and just now, I remember sonyeffect_sw/libsonysweffect.so, sonyeffect_hw/libsonypostprocbundle.so, and proxy_sony/libeffectproxy.so (/soundfx/sony/*) not working either lol. I removed those entries as well, leaving only visualizer_sony, which does work, I just do not know if Pulse support is sustained without the sonyeffect effect.

Looking forward to your report and everyone else's. :good:
[Android Software Development] Minto107:
Can you 'hear' a difference? :D in running out of Internet data so downloads are slow af so I asked about some info but noone was able to give me any :P
[Android Software Development] Lownita:
What exactly are Qualcomm audio effects? Do they have a big impact on sounds?
[Android Software Development] Minto107:
For me, only on battery life ??? seriously now, not really. Tried Android 8 and Huawei, I'm sure it 'works' but I can't hear difference
[Android Software Development] mohand06:
On Google Music playing local flac or on streaming -- Jango radio, Discover, TuneIn for ones -- I can definitely feel the difference compared to stock or, what matters more for you I guess, to all other previous versions of Arise (If I believe my ears memory):good:
[Android Software Development] mohand06:
[MENTION=4445176]guitardedhero[/MENTION], if you want to have a look at a Samsung A3 system libs, reminding you that the Arise samsung ex audio_effects.conf has some references to non-existent libs (on my A3 & S3) and that in the attached listing there are some samsung libs whose names apparently indicate that they're related to sound effects.
[Android Software Development] guitardedhero:
Thank you very much for that, can you provide your rom's audio_effects.conf as well? :good:
[Android Software Development] radz_:
Dirty flash is ok? On top of 0430, anyone tried it?

Also, when dirty flashing should I remove "true" in Arise System?
[Android Software Development] mohand06:
It's me for the thanking though out of thanks for today.

Here you are for the A3 stock and 20170506 build audio_effects.conf. in latter, some entries commented by me.

Your latest build with v4a 2.5.0.5 and am3d as app modules makes really the difference. Though noted that TuneIn isn't any more processed as well as iceconfig6 deactivating v4a. Not really disturbing as config2 doesn't conflict with v4a and there are plenty of real quality streaming radios Jango, Discovery. :good::good::good:
[Android Software Development] nitramus:
Try removing convolver
[Android Software Development] JohnFawkes:
[MENTION=4445176]guitardedhero[/MENTION] here's my dumpsys on htc10 running viper10. I am running 5/06 arise with the 3.2 magisk module as I use magisksu. I have Sony, musicfx (frozen), Dirac, and Huawei qc effects. I have v4a installed via magisk module and atmos installed via magisk module. Would you mind looking at my dumpsys and let me know if everythingis working correctly? I also have arise setprop enabled. Thank you for your time
[Android Software Development] guitardedhero:
Dirty flashing is perfectly fine except for the setprop will still be enabled as it survives the entire installation and the only setprop provided is named differently in order to not execute unless you rename so it will execute. If you intend to use setprop then a dirty flash update is appropriate. If not, simply delete the existing /system/etc/init.d/arisesound_setprop so that it will not execute.

The reason Core should only be installed a single time is that the Core module is where you receive the audio effects configuration template with which all other modules simply add/remove their necessary entries. This means that any time the Core module is installed, any desired modules will need to be reinstalled as well in order for their entries to be included in the audio effects configuration to allow functionality of those other modules. :good:
[Android Software Development] DEVILOPS 007:
I dirty flashed and don't know if I want that setprop file you said about. Can you explain exactly what it does and whether there is any need or reason for me to remove it or not? Thanks a lot.
[Android Software Development] guitardedhero:
Those audio effects configurations target the /soundfx system and vendor libraries of specific devices, including Stock, which targets the native /soundfx libraries provided by your firmware and appear as they do in your firmware's audio effects configuration.

They will likely react differently in the scope of hardware and software the mod supports, but in my usage, Android O and Huawei seem to be the bass heavy configurations targeting those libraries. Asus and Sony seem to be more neutral and "clean". :good:

No joy with the default ICEconfig1?

The only thing missing besides the Huawei vendor effects, is /system/lib/soundfx/huawei/libeagle.so. Does that library exist in this location? I've found that libeagle.so does not appear available for me using my son's Moto, so this can always be the reason. the missing Huawei vendor effects leads me to believe that your sound system installation resulted with the HTC audio effects configuration. Check the header of that file provided by the installation to confirm which configuration with which you are working. :good:
[Android Software Development] gimpy1:
I have a quick question about volume settings on the different profiles. Using my earphones, the volume on most, if not all, of the saved profiles are way too loud when I load one of them. It hurts my ears. The volume bar is at the lowest setting on the left side off the bar. One click lower and the volume mutes. That setting seems to be the default. Is there a way I can reset it so the default is not so ear splitting? And so I can lower the volume a few clicks?

I have tried the phone sound settings, Dolby settings, but it didn't seem to help.

The profiles I am speaking of, are the audiophile ones included with the arise installation.

Thx.
[Android Software Development] JohnFawkes:
Yes that file exists. So does that mean those effects aren't working and I'm running the stock Audio effects? It existsin lib but not in lib64
[Android Software Development] Mervingio:
Not sure if this was answered before but any problems with the LG V20 on ARISE+Deuteronomy+3.31+SwanSong+AROMA??
[Android Software Development] JohnFawkes:
Here you go :)
[Android Software Development] Zackptg5:
Hi everyone, v3.3 of magisk compatibility module has been released! Some big changes here (in addition to updating it for latest magnus opus version - 5/6): I decided to no longer have it move the scripts to su.d to keep it consistent with the rest of arise. As a result of this, I was able to readd backwards compatibility without too much effort with previous versions of magnus opus (like 4/27). Check it out here: https://xdaforums.com/android/softw...y-research-t3379709/post71569390#post71569390
[Android Software Development] guitardedhero:
You guys are still missing the hell out of AROMA, eh?
[Android Software Development] veez21:
Nope :D

I think the guys who think arise_customize.prop is hard to work with is because they didn't read the instructions and then just said "man, this sh*t is confusing af!" :D
[Android Software Development] Lughnasadh:
Nah. As long as you read 1st people shouldn't have a problem. And once you do it once, its easy as pie afterwards :cool:
[Android Software Development] guitardedhero:
Thank you very much! Embarrasingly, I did not ever take focus to HTC's implementation of two differently named audio effects configurations until just now lol. Audio framework supporting the vendor audio effects configuration will always ignore the system audio effects configuration if the vendor audio effects configuration is found and is readable.

This seems to be the case for HTC, only the vendor audio effects configuration causing the system audio effects configuration to be ignored, is instead, /system/etc/htc_audio_effects.conf.

HTC typically only provides these two audio effects configurations, but I suspect that a vendor audio effects configuration would also be ignored along with the system audio effects configuration if /system/etc/htc_audio_effects.conf is found and is readable on all HTC devices with htc_audio_effects.conf.

Also, HTC has typically used the AOSP approach that is found in system audio effects configurations with their own htc_audio_effects.conf, with no instances of the three vendor effect libraries that are what allow the dynamic of the different QC audio effects configurations available.

The take away from observing this information is that HTC's best chances of enjoying the different QC audio effects configurations will require ignoring everything outside of /system/etc/htc_audio_effects.conf. :good:

Fantastic as always, Zack! :highfive:
[Android Software Development] justjr:
[MENTION=4445176]guitardedhero[/MENTION] here are my dumpsys, arise_customize and audio_effects on Moto G3 stock MM :good:

stock sudio effects is frozen, do you know that musicfx don't appear on the app list it I install it on MM? It is on the app-priv.

Also I have the libeagle on lib folder.

O god here we go again, hahaha. What files should I move so I can update the module without restoring the hole thing again, I just did it... And, what about if I keep the 3.2 module?

Thank you guys, you are amazing.
[Android Software Development] Zackptg5:
Don't bother updating the module unless you're updating arise. If it works, why fix it :)

Flash arise, flash module, profit. OR do nothing, profit
[Android Software Development] justjr:
But, I just updated ARISE to 0506... but all seem to be working amazing!!!! Much better then last version. I can only see that viper is processing, other modules have no UI, ICE and Arkhamys.

edit: matlog is showing me all modules working! :highfive:

Also, NO MORE CRACKING SOUND! YEAH! And I don't really care about Aroma.
[Android Software Development] JohnFawkes:
So what can I do, if anything, to get qc effects working or will it be something you guys have to do on your end with an update?