yashsingh1/xdaforums huggingface dataset:
[Android Software Development] Zackptg5:
Okay, I've seen this error occur on my test device too. There's inconsistency between roms in which spolicies need applied. First of all, do you have arisesoundserver in system/su.d? If not, reflash arise, then the module. After that (or if you do have arisesoundserver in su.d, replace it with the attached file and see what happens. I added another sepolicy line that should fix the dts crash
[Android Software Development] hokiealumnus:
Take that file you downloaded. Extract arise_customize.prop and put it in your /sdcard/ directory. Edit that file with the word "true" behind every item you want to install. Save. Boot into recovery and flash the zip.
[Android Software Development] SimplyCity:
Thanks, I know.

Maybe I look like nob, but trying to not be one, I even think I am not. :)

I tried to place prop file in so many places, just to test if patched ARISE installer will find it. And I have failed...

OK, I ask for permission to modify installer script by my own. If succeeded, I will share it. But if ARISE great team could have an ideas what to do to make it work in DualBoot environment, I won't touch it.

Echoe™ team member / S7E
[Android Software Development] biggbear82:
Hi again, have generate a recovery log, but not a logcat, because i cannot get in my bootloop. But i'll share what i have.

What i remember is information about service media.audio_policy, and warning about AudioPolicyService, nothing more.
[Android Software Development] BigM69:
OK, after I move the prop file do I need to rename the .prop to .zip or do I just flash the magnum zip that I downloaded?

---------- Post added at 10:30 PM ---------- Previous post was at 10:24 PM ----------

OK I got it, I haven't flashes yet, because I'm trying to figure out if I need to put 'true' after everything..
[Android Software Development] hokiealumnus:
No renaming. If you rename it, flashing the mod does nothing because it doesn't have an installation configuration file to read.
[Android Software Development] BigM69:
OK so I just flash the zip that I extracted from?
[Android Software Development] mrrocketdog:
https://m.youtube.com/watch?feature=youtu.be&v=KTugNE7ML-4

here ya go. installation vid.:ARISEUP!!!:

"err on the side of kindness"
[Android Software Development] Thisguy129:
Well if I was to recommend the best results it is SuperSU for root even on a costume ROM I have tried it on stock ,costumes, and multiple device's and not one could get everything working except PAC man ROM with selinux permissive and SuperSU root manager I thinks its awesome now plays great.this is the reason I root if only for viper I'd still root. The icesound con figs bathsalt is that good or bad jk. What a name
[Android Software Development] BigM69:
Do I need to install all viper profiles? I know not to install v4a_xhifi. I'm not entirely sure what I should make true below the profiles. Just likebICEco IG=1. I have no clue if I should leave it false or make it true. That goes for the rest of the values.

---------- Post added at 10:39 PM ---------- Previous post was at 10:38 PM ----------

Thanks for doing that but its a dead link.

---------- Post added at 10:42 PM ---------- Previous post was at 10:39 PM ----------

Never mind I had to view in web mode.
[Android Software Development] oakley470:
Ok thanks I'll take a look, I had to reflash rom the lag made the device unusable. If this fixes the crash will it fix the lag too? That was really a big issue the device was rebooting and not responding constantly
[Android Software Development] Zackptg5:
There were a lot of audit errors about a "toolbox". I'm not sure what that is and I'm fairly certain it's not arise related. Lots of crashing would cause lag so hopefully
[Android Software Development] ffejy462:
I'd recommend starting simple. Put true after core and your choice (I recommend 2.5.0.5) of v4a. Add more as you wish. Viper has a learning curve, but just listening to music and enabling one setting at a time works great. Nowadays I only use Viper bass and clarity, because, imo, the rest degrade the overall experience.
[Android Software Development] BigM69:
Great advice. I'm getting ready to flash,wish me luck! I'll report back.
[Android Software Development] gannjunior:
Hi

any chance to get Viper4Arise work in Fiio X5 3rd ?

even if I activated them I have no change in the songs...

any advice or alternative solution?

thanks

ciao
[Android Software Development] BigM69:
I keep getting an error 1

---------- Post added at 11:26 PM ---------- Previous post was at 11:25 PM ----------

Yes I saved the prop file after editing

---------- Post added at 11:27 PM ---------- Previous post was at 11:26 PM ----------

Would my selinux status being on permissive have anything to do with it not flashing?
[Android Software Development] mrrocketdog:
usually error 1 is not enough free system space. check for system free space. 300mb is recommended. 400 is better.

"err on the side of kindness"
[Android Software Development] hokiealumnus:
Are you sure it's in your base /sdcard/ directory? It can't be on an external SD card and has to be in the base directory. The same one as your default downloads, photos/dcim, music, etc folders.

Also make sure you have >200MB of free space in your /system/ partition.
[Android Software Development] BigM69:
This is were I have the prop located.http://cloud.tapatalk.com/s/58fe9010f15b5/Screenshot_20170424-194331.png?

---------- Post added at 11:57 PM ---------- Previous post was at 11:54 PM ----------

Owell I'm done for now its starting to piss me off??
[Android Software Development] hokiealumnus:
Yea, that's the right place.

If I had to bet, my guess is your system partition is too small for ARISE. As mentioned above 300MB is about the minimum, and 400MB is recommended. The Moto X Pure (XT1575) is a 16GB phone, so I doubt that it dedicates all that much extra space for the /system/ partition. You may not be able to use ARISE, I'm sorry to say.
[Android Software Development] BigM69:
Well that sucks. Everything in that directory I use,there may be a few files I can delete but if I did delete some stuff it probably wouldn't give me enough space. Why can't ARISE be put in SD card storage?

---------- Post added at 12:20 AM ---------- Previous post was at 12:19 AM ----------

I'm gonna try deleting some stuff and try to flash again....wish me luck

---------- Post added at 12:26 AM ---------- Previous post was at 12:20 AM ----------

Yeah I just checked and I should have plenty of space..

---------- Post added at 12:38 AM ---------- Previous post was at 12:26 AM ----------

YES YES YES!!??
[Android Software Development] hokiealumnus:
Did you get it?

Re: space - we aren't referring to your overall space. Rather, specifically your /system/ partition. Uninstalling apps shouldn't affect that at all, unless your phone was just plain full and couldn't take anything else in any partition.

For instance, the old 2012 Nexus 7 has a tiny system partition and only has room for the OS and a pico Gapps package.
[Android Software Development] BigM69:
Oh yeah I'm jammin out with my Bose Ae2 BT head phones. Wow 150% better sound I didn't think these head phones was capable of such pure,true,crisp sound! The bass is un-friggn real!
[Android Software Development] oakley470:
Dts crash is gone, but lag remains lots of apps not responding errors. This doesn't happen if the module isn't installed, everything runs fine then but I am guessing not all the effects are working. New log attached
[Android Software Development] Eyalkn:
This is also the only thing that worked for me
[Android Software Development] MikeW14:
in Magnum Opus, can dolby atmos be used with an enforcing kernel or does it have to be permissive? thanks so much.
[Android Software Development] JaylanPHNX:
Glad to see all the hassle was worth it.
[Android Software Development] geringv:
The same goes for my Nexus 4 too. Not enough space even if I'm installing just the core module. Looking at the logs, I think its because the installer extracts 'everything'..... is that right?
[Android Software Development] Lughnasadh:
It can be used with enforcing.
[Android Software Development] abhidangi:
Just got twrp and magisk on samsung Galaxy S8 SM-G950F (exynos)

and Viper i general works with some apps here.

Works in poweramp,but not in spotify.

Tried deep buffer remover, magnus opur arise and also viper magisk solution. Still no processing in spotify. The reason being i think is spotify is using samsung sound effects in place of viper. So if anyone founds anything about how to disable stock samsung sound effects, any one please shed some light.
[Android Software Development] crackerjack1957:
Equalizer turned on in Spotify?

If it is that would override Viper.
[Android Software Development] Roi007leaf:
Attention all the users who get error 1 even after having the prop in the right place and selecting install.core=true

We are aware of the issue and investigating...

Please try moving the prop to /system and replace the script with what I uploaded here

Let me know if it's successful.
[Android Software Development] darko454:
Does anyone having problems with AM3D ZIRENE APK?

I tried opening it but it only stays in a black screen. I'm on the latest build modular zip. Never had that problem before. Any advice?
[Android Software Development] Roi007leaf:
Known issue , am3d only works on Los based audioflinger

---------- Post added at 05:24 AM ---------- Previous post was at 05:22 AM ----------

Just tried P - AEX and it works fine for me
[Android Software Development] Ninja Potatoe:
I finally got the modular installer to work by installing a newer unofficial twrp . Now the apps/system is installed but I get no effects from them. Any idea on how to fix that? Using 3.1 magisk module, I wanted to try the 3.0 module but I can't find the download anywhere.
[Android Software Development] abhidangi:
How do i turn off the Spotify equilizer . Cause wat i have on my S8 is that spotify equilizer is just a link to default samsung sudio effects.

Also viper doesn't work with youtube while it works with Facebook.

Is there any way i can disable or uninstall that default samsung audio effects app. I am new to samsung.
[Android Software Development] gehess:
Here's a nice subjective question for users of Dolby Digital Plus (or perhaps even Atmos): What additional mods do you use that result in more clarity/separation in the recordings you listen to?

And as a follow-up question to any ARISE devs out there: Does the Core system module itself contain any sound optimisers or mods?
[Android Software Development] thereian2:
That did it

Thanks for the advice!!! That did it. It works perfectly now, and the sound is amazing!!!
[Android Software Development] Roi007leaf:
Yes it does, various libs and components you can see it all in the zip under /modules/core
[Android Software Development] lordhoekage:
If I use V4A, does it interfere with ICESound? I'm confused as to how ICEsound works lol
[Android Software Development] illuzi0n:
is the file arisesound_support.zip the main file to flash ?
[Android Software Development] ShouriX:
I want to upgrade to the new 3.1 module. Do I have to uninstall the 3.0 module beforehand?

Thanks
[Android Software Development] guitardedhero:
In Android Terminal:

su
am start com.oppo.dirac/com.oppo.dirac.activity.EqualizerActivity

The Main activity is:

su
am start com.oppo.dirac/com.oppo.dirac.activity.MainActivity

You could easily prepare a couple scripts, each one with one of the above commands underneath a proper booted system shebang header such as:

#!/system/bin/sh

With the proper read and execute permissions such as 0755, each script placed somewhere in /system (/system/etc, for example) could be launched anytime you want through most file managers by navigating to it and selecting the option to run as script or similar.

There are likely other options than in script form, but those options would use the am start activity lines above. :good:

---------- Post added at 01:24 AM ---------- Previous post was at 01:11 AM ----------

Yeah, lineagos, at some point, made significant audio framework changes, resulting with a disappointing reduction of supported effects libraries it previously supported, making the once top-recommended custom rom one that is now in the massive majority of roms that do not support the following effects libraries in our sound system:

libam3daudioenhancement.so

libAuro.so

libhpx.so

libmaxv.so

Lineageos for Nexus 6 lost support beginning with build 20170331, for example.

Fortunately, Screw'd supports these libraries and officially supports Nexus 6 among a handful of other devices.

This is where the dumpsys utility is a crucial tool for monitoring the rom support of the included libraries, detailed with all the necessary information to easily do so on your own in the Auditing section of our OP.

I recommend to use this utility to find a rom that supports these effects libraries for best results, if available for your device.

Keep in mind that libam3daudioenhancement.so will only appear if the AM3D module is installed.

You know how you see the constant barage of reports for AM3D (and the few AM3D apps shamelessly disguised as something else) not opening or open to a blank page? Well, the reason is because of lack of support for the effects library. That is why we put so much value on equipping you guys with the knowledge as well as the tools to acquire such knowledge if necessary. It's far too late, imho, for skeptics to proclaim our project as one of garbage or placebo content. At one time, it was a bit offensive as it suggests that all you users do not know any better. Yet, still, we are the first and only thread to provide an auditing section with free and simple tools/information to find out on your own. Go figure...

The other three effects libraries are part of the Core module so will always appear if supported by the rom. :good:

---------- Post added at 01:38 AM ---------- Previous post was at 01:24 AM ----------

Ah, that is a great point and must be taken care of immediately. So, your lineageos build has nothing unique to your device with regards to /system/lib/soundfx?
[Android Software Development] wrongway213:
Screw'd really has been just what the doctor ordered in terms of being able to use totally custom, like off the wall custom ROMs and not have any sort of ARISE issues, for myself at least. I was happy to hear you've been having the same experience. I remember how excited I was when I realized AM3D was just working one day... :good:
[Android Software Development] guitardedhero:
What is the exact path and spelling of the root of internal storage? I imagine this directory is shared by the roms installed. :good:

---------- Post added at 01:58 AM ---------- Previous post was at 01:41 AM ----------

No, your post illustrates precisely what we advise: Removing deep_buffer because testing has shown doing so enhances the functionality of ViPER4Arise. Our strongly worded advise was to lessen the temptation to do what seems to be the correct action because of long-held and popular belief that removing deep_buffer will always have a better result than not doing so, without testing the installed sound system with a fully intact audio policy even a single time.

The long-held and popular belief I mentioned is certainly one that resulted from extensive testing and in no way am I discrediting that. Newer devices with new and multiple configurations for audio policy are those that present scenarios where the removal of deep_buffer output and instances can have undesirable results.

Make no mistake, we encourage and celebrate experimentation. This project has been one experiment after another this entire time. Things like removing deep_buffer and forcing Permissive SELinux Mode automatically, without testing the alternative of each, is simply not experimenting or testing. It's simply habitual behavior. :good:

---------- Post added at 02:17 AM ---------- Previous post was at 01:58 AM ----------

An available workaround in such cases is editing the following line in /system/build.prop before flashing our zip to appear as:

ro.product.manufacturer=HUAWEI

Save changes and then install our zip.

This scenario installs the Core module without the Huawei component which amounts to just over 125MB of the Core module's total weight.

After installation, simply revert the change to /system/build.prop back to the original value if desired.

Additionally, avoiding the optional Sony Music module will not consume 70MB of /system space. :good:

Try disabling SoundAlive in system settings and then reboot to test for increased functionality.

If still experiencing less than perfect results, and the ICEsound module HAS been installed, experiment with alternative ICEsound configurations to see if one that is provided improves the experience to your satisfaction. :good:

Refer to the Auditing section to utilize the dumpsys utility to assess the support of libam3daudioenhancement.so when the AM3D module is installed to see if an available rom for your device supports the AM3D library. :good:

Disable SoundAlive through system settings and reboot to test for desired behavior. Furthermore, removing deep_buffer may resolve the remaining of your less than perfect experience. :good:
[Android Software Development] Logan:
Thank you so much :D

This is perfect explanation, Many devs didn't reply for reported issues but in this case you did it i really appreciate it.
[Android Software Development] guitardedhero:
This particular Dolby Atmos, the original and most commonly found port by [MENTION=981278]worstenbrood[/MENTION], has never had a dependence on a Permissive Mode SELinux environment, or even root for that matter. :good:

---------- Post added at 02:28 AM ---------- Previous post was at 02:22 AM ----------

This results when using an outdated arise_customize.prop.

Ensure the header of arise_customize.prop includes "Magnum Opus" when using the Magnum Opus installation archive. It can be extracted from META-INF/your_system directory of the Magnum Opus archive, placed in the appropriate location and edited before installation. :good:
[Android Software Development] SimplyCity:
While on primary, paths to internal storage - at the point I am now - are (thanks to FX Explorer) :

/mnt/user/0/primary/

/mnt/sdcard/

/sdcard/

/storage/emulated/0/

/storage/self/primary/

/data/media/0/

While on secondary, using same way for checking - above paths are the same plus you can find internal memory in:

/mnt/runtime/write/emulated/0/

/mnt/runtime/default/emulated/0/

/mnt/runtime/read/emulated/0/

All of them leads to the same place.

But while on TWRP, paths are:

/sdcard/

/data/media/0/

Do you think I could use the script (few posts above), which requires prop files to resident in /system/ folder? I think it may solve my problem...

:)

Wysłane z mojego SM-G935F przy użyciu Tapatalka
[Android Software Development] Roi007leaf:
Yes it would work, but we're trying to make it work for sdcard .. you can try this please
[Android Software Development] guitardedhero:
This type of peculiar behavior is best debugged by moving /system/etc/init.d/arise_setprop to anywhere but /system/su.d to test for corrected behavior that is broken by one or more build properties set by that script.

If this resolves your issue, I suspect one of the lines towards the very bottom arise_setprop. Simply comment one of those lines that seems related to your issue by placing "#" at the beginning of the suspect line, save changes, and place in /system/etc/init.d with 0755 permissions before rebooting to test for corrected behavior by the responsible build property not being set by the script.

We would love to know these results if you succeed, so that we can help others in the same situation as you. :good:

---------- Post added at 02:55 AM ---------- Previous post was at 02:41 AM ----------

Placed in /system and installing an ARISE archive seeking the file in /system will certainly work as there are only two variables for /system, essentially non-Pixel devices or Pixel devices. There are multiple variables for /sdcard which pose more opportunities for error.

Our preference for using the internal storage rather than /system for this file is for it to survive rom installations/updates and TWRP factory resets so that the file could instruct a future sound system installation if no changes are desired and if it is still an appropriate arise_customize.prop for the sound system being installed. Changes can occur at any time requiring the latest arise_customize.prop to be used with the latest sound system.

However, now that I've read your post I quoted a second time, where was the file placed automatically by the initial installation and was this file then edited before installing again? I fail to see how the installation script would not see a file it explicitly placed, you know?
[Android Software Development] FReaX908:
Thank you all for your hard work! The sound of my N6 is so much better using ARISE!! Can't hear music without it anymore :)

[MENTION=4445176]guitardedhero[/MENTION] I want to try out the ARISE team members cusomize.props and I am very excited especially about yours because I always liked your profiles in the past.

But using Viper 2.5.0.5 I have to live with the headphone bug so i want to use Viper 2.3.4.0. If I use your customize.prop (or any other with 2.5.05) but install 2.3.4.0, does it "vary" the intended sound?
[Android Software Development] guitardedhero:
Audiophile™ X is older than ViPER4Android 2.5.0.5 and was prepared using ViPER4Android 2.3.4.0. :good:
[Android Software Development] BigM69:
Absolutely worth it!
[Android Software Development] SimplyCity:
Thanks for info, my friend. It is wise idea to have proper file in folder other then system. :)

Unfortunately, I couldn't find prop file installer has supposed to write. It just wasn't there, anywhere... It looks like installer did not write it...

Second try was with manual copy, but, as you've read already, installer can't see it.

Just now I thought it may be connected with permissions? I just checked prop file permission and it has 0600... Hmm... Changed to 0660, I can't set 0664 from file explorer. Will go to TWRP and check there...

0660 is not enough, is it?

Wysłane z mojego SM-G935F przy użyciu Tapatalka
[Android Software Development] BigM69:
Even though I have ARISE up and working,what is 'safetynet failed' mean? I only have 1 modual installed and its emoji one.
[Android Software Development] shuli81:
I'm on N6P running Pure Nexus rom. updated to ManumOpus today from 2.94.

Not quite sure what is going on but everything is crashing and Action Launcher wont even start.
[Android Software Development] guitardedhero:
Ah, that makes sense. A variable for sdcard was applied in installation scenario that does not exist. We'll investigate those variables. I suspect recent changes to add more variables for sdcard is causing the majority of these recent issues. :good:

Flashing your Pure Nexus rom zip will remove all the crashing as well as remove 2.94 entirely, providing an appropriate foundation to install Magnum Opus with its dedicated arise_customize.prop that you can extract and place into /sdcard with the necessary edits to install your desired sound system. :good:

---------- Post added at 03:48 AM ---------- Previous post was at 03:47 AM ----------

I promise I am not ignoring you. I am not a reliable resource for aspects relating to Magisk and SafetyNet. :good:
[Android Software Development] BigM69:
Its all good man

---------- Post added at 09:03 AM ---------- Previous post was at 08:56 AM ----------

Is there a forum related to majisk?
[Android Software Development] atulclassic:
[MENTION=4445176]guitardedhero[/MENTION]

I am not able to make my Fiio Q1 DAC work with ARISE.

Whenever i attach DAC through usb, driver fails to start whereas everything working fine when i directly plug in my headphones.

Device OP3, Rom OOS Open Beta 14, ARISE 3.31, DAC Fiio Q1 with inbuilt battery, Music App Poweramp
[Android Software Development] psycholyzern:
Hi. I couldn't make V4A working at all. I tried both app, they will just asking to install driver. Then after a reboot, still nothing happen. No sound changes. I am using LOS 7.1.2.