yashsingh1/xdaforums huggingface dataset:
[Android Software Development] grimmaniac:
Does TuneIn has an integrated equalizer? In Napster/Rhapsody I have to open the equalizer once after every new A. R. I. S. E. installation to make it work. Don't activate it, just open it. Might be worth a try.
[Android Software Development] DEVILOPS 007:
Try without dolby and try not setting permissive script.
[Android Software Development] JBNex:
Does anyone have a detailed explanation of the functionality of DTS Service module (DTSClientControllerService)? Description in the .prop file is quite vague...
[Android Software Development] mohand06:
S3, stock flavor 4.3 by Xerkan, Enforcing, SuperSU, Boeffla-kernel 5.1.1 Samsung I9300, Ainur Pandora v3 (su.d props) Modular SwanSong 3.09, V4A 2.3.4.0, ICEsound Ultra, config2, preset 09 (init.d arisesound_setprop): Good, loud and clear!
[Android Software Development] Zackptg5:
There are no files to mount so automount does nothing. It seems that the phone is "Waiting for service media.audio_flinger..."

That's not part of the module but part of arise. This likely has something to do with the arisesound_services script. Without the module, this script doesn't run. Can you try dirty flashing your rom, flashing a version of arise older than 3.x (like 2.94 aroma), and then reflashing the module?
[Android Software Development] Sek0n:
Yup, I'll do that now, and report back.
[Android Software Development] RSDamasceno:
Hello.

I'm trying to install ARISE with Dolby's ahrion.

I have already tried to install Dolby and then ARISE and tried to install ARISE first and then Dolby, but after restarting Magisk says it is not installed.

Can anyone using both mods help me with this?
[Android Software Development] access9:
I think I figured out the issue with the Magisk module and PN (at least for me).

In the module's post-fs-data.sh script:

12 if [ -e /system/su.d/arisesound_services ]; then
13 ./system/su.d/arisesound_services
14 else

Notice line 13, the leading dot. After a bootloop, I used magisk_mount to remove the module. That means the arise scripts are left in /system/su.d.

I extracted the post-fs-data.sh from the module zip, removed the leading dot from line 13, and manually ran the script via a root terminal: sh post-fs-data.sh

Next, I fired up Viper and to my surprise audio is now processing.

I hope that helps tracking down the issue.
[Android Software Development] Sek0n:
Same as before. :( Stuck on the boot animation.

Added the new log.
[Android Software Development] Fdraco10:
ViperArise 2.5.0 on Nougat Audio crackle, dolby atmos don´t work properly.
[Android Software Development] Zackptg5:
Looks like it was still booting. You needed to give it more time. I recommend flashing everything but the module, verify everything works, then install the module so you won't be sitting there for 10 minutes after a clean flash wondering if it's working
[Android Software Development] Sek0n:
That's what I thought it looked like as well, but it took a lot longer than i've ever had it (successfully)boot before.

I'll do it again, just in-case, and let it sit.

Ok, booted fine without the module, trying with it again. I'll let it sit for 20mins or so. :P
[Android Software Development] Sek0n:
Ok, did as you suggested. It booted fine without the module, then tried again with it. Same result.

Logcat looks the same as well, but attached it anyways.
[Android Software Development] Zackptg5:
Shouldn't take that long. It should sit on the boot logo for a minute or so and then the actual boot time should be normal

---------- Post added at 12:19 ---------- Previous post was at 12:17 ----------

Wow, literally everything died. There's something weird going on with magisk by the looks of it. In twrp, mount -> system, advanced -> file manager

navigate to system/su.d and move arisesound_services to your sdcard. Then reboot and see if it works (don't change anything with the module or whatever)
[Android Software Development] Sek0n:
All that's in there is "arisesound_setprop," Is that what you mean?
[Android Software Development] Zackptg5:
Oh ya, you're on older arise version so that file shouldn't​ exist. Considering that everything crashed and burned, you should probably dirty flash your rom. Then as a last ditch effort, flash arise 3.09, the magisk module, then delete the arisesound_services file in twrp
[Android Software Development] Magz Heaven:
I dont know how and why, but flashing the permissive script of AROMA installer v2.94+ on AICP doesnt work.

El Psy Congroo
[Android Software Development] Zackptg5:
Can you open terminal and type in:

getprop

and paste the output?
[Android Software Development] Sek0n:
Ok, dirty flashed, then put on 3.09, then the module. Moved arisesound_services to the sdcard. Left it on the loading animation for about 10mins. Log attached; looks about the same as the last one. :(
[Android Software Development] Zackptg5:
Just remove the module for now. I may have identified the issue and am looking into what may fix it :(
[Android Software Development] Sek0n:
Ok, Thanks for helping. Good luck. :p
[Android Software Development] Mark_Draconian:
I flashed Swansong 3.09, everything fine on TWRP, but after that Arkamys and Dolby constantly FC(annoying pop up all the time)... what can i do to solve this?
[Android Software Development] access9:
K, props attached. Doesn't look like any of the arise props are set, but viper is at least processing now.

Fwiw, I tried sticking the (modified) post-fs-data.sh in /magisk/.core/post-fs-data.d and that resulted in a bootloop. Running it manually after boot works though.

http://cloud.tapatalk.com/s/58d94b88471af/props.txt
[Android Software Development] Mohit31:
Same here, for me even other apps were having FC like chrome, gallery

And there was no sound coming from speakers as well

Things had gone pretty haywire

Eventually, had to dirty flash the ROM
[Android Software Development] Zackptg5:
Arise props did set :)

What are the exact steps you took? You removed the post-fs-data file and instead run it manually after boot?
[Android Software Development] access9:
Awesome!

Yes, but before I ran it I edited it to remove the leading dot from the script's path as mentioned in my previous post, otherwise the path is invalid.
[Android Software Development] Zackptg5:
I completely overlooked that. Dot will be removed in next release. Should hopefully fix the stuck on boot issues
[Android Software Development] Minto107:
Is there any advantage of new magisk module if actual(3.09 AROMA) works just fine? I don't have any issues and long booting problem is gone with this version. Is there any advantage of using v2.1 over 3.09? Thanks I'm advance for your answers ;)
[Android Software Development] DEVILOPS 007:
There isn't 3.09 aroma yet is there?
[Android Software Development] Midomad:
No,not yet.
[Android Software Development] Minto107:
I meant ARISE4MAGISK 3.09 AROMA ;)
[Android Software Development] DEVILOPS 007:
Oh okay I thought so but I was like what do you mean aroma?
[Android Software Development] Zackptg5:
Okay, to everyone having issues with the magisk module. I made another edition of it that fixed the issue with one of my testers who was having this issue as well. Check out v2.1 LS here: https://xdaforums.com/android/software/r-s-e-sound-systems-auditory-research-t3379709/post71569390
[Android Software Development] nagi_007pk:
Flac bug oneplus 3T 6.0.1

Hello everyone

Long time viper user here and recently installed this mod on my 3T running Marshmallow. I wanted to know if this is a rom bug or the package itself but I can't seem to play flac files or anything over bluetooth. Mp3s work fine and I'm running Franco kernel for my phone. I want to know what's the issue here. For reference I used the new viper and the old viper. Processing works great. Sounds much more improved but I want to know if there's any way to fix this. Searched the thread and didn't find anything substantial for my phone. Would love if someone would help me out. I miss viper dearly and this mod is excellent as I can feel the processing on my mp3s. Huge difference tbh. Thanks again

Flacs don't play at all. Correction. Not just on Bluetooth. Also running Oxygen OS 3.5.4
[Android Software Development] access9:
In common/service.sh:

if [ -e /system/su.d/arisesound_services ]; then
system/bin/sh /system/su.d/arisesound_services
else
if [ -e /system/su.d/arisesound_setprop ]; then
system/bin/sh system/su.d/arisesound_setprop
fi

if [ -e /system/su.d/smeejaytee_setprop ]; then
system/bin/sh system/su.d/smeejaytee_setprop
fi

if [ -e /system/su.d/sony_setprop ]; then
system/bin/sh system/su.d/sony_setprop
fi
fi

Did you intentionally leave off the leading slashes before system/bin/sh and system/su.d?
[Android Software Development] Zackptg5:
Nope, that's borked. Those should all have slashes before them -_-

That's what happens when I do things to quickly, thanks for catching that. Reuploaded fixed ones.

A note about LS edition. Since all of the magic is happening during boot instead of before it, it won't hang on the boot logo for very long and so boot should be a little faster over all.
[Android Software Development] BSDADON:
This worked for me. Thanks! :good:
[Android Software Development] access9:
It works; scripts look good, no bootloop, viper works and props are set.

Thanks, I really appreciate the time you took to get this resolved!
[Android Software Development] sjamie:
Does anyone have dolby atmos running successfully on swansong 3.09? How does dolby dts compare to atmos?
[Android Software Development] weazie:
Yes, here's another confirmation - the module now works and not stuck on boot. Safetynet also passes.
[Android Software Development] Zackptg5:
Good to hear! The final test to make sure everything works is to type in terminal emulator:

getprop

If you see a bunch of lines for audio and media stagefright, then you know it worked
[Android Software Development] weazie:
Seems so!
[Android Software Development] Sourav95:
I am using miui 8.1.7.0. After installing the swan song module my phone is not booting up. It keeps on going back to twrp recovery. What should i do? I flashed swansong 2.83.1. Pls help. [MENTION=4445176]guitardedhero[/MENTION]
[Android Software Development] Sek0n:
Just woke up and checked here. Works great!

Thanks for the work :good:
[Android Software Development] luigidk:
I've just installed the new magisk module - and yes - everything is working great.

This is the first time I've used the magisk module and thanks for getting this latest version.

Up until recently I've been running ARISE on my 6P with PN unrooted. But now with Magisk I'm able to enjoy all the features of ARISE. as well as have a rooted experience and Android Pay - great stuff all!
[Android Software Development] grimmaniac:
All good here on a 6P w/ rooted stock.
[Android Software Development] umeshbluezzz:
How can i remove arise magisk compatibility module 2.1 via recovery? Stuck on boot logo.. plz help

---------- Post added at 02:57 PM ---------- Previous post was at 02:57 PM ----------

How can i remove arise magisk compatibility module 2.1 via recovery? Stuck on boot logo.. plz help
[Android Software Development] rohit3192:
Size of installation files should be reduced as low space left after flashing even pico gapps and nougat rom.
[Android Software Development] chikimonke:
Go to the Magisk thread and get the Magisk uninstall file. It will remove all modules as well as Magisk itself, then reflash Magisk 11.6, Arise 3.09 and the 2.1LS module, then your system should hopefully boot
[Android Software Development] hyewiz:
would love to know the deference between "Magisk" and "None Magisk" which one is better my ROM is not Magisk Rooted, should I flash ROM that has Magisk?
[Android Software Development] secone00:
No... If you want magisk then go for it but there are no features that are specific to magisk. If you like your ROM just install the normal version.
[Android Software Development] triskadeka:
I can't install it at all

I have Zenfone 2 running AICP N7.1.1 and TWRP 3.0.3.M4

This is what I did;

-Dirty flash current ROM

-Flash ARISE Deuteronomy 2.94 Modular AROMA Installer.zip

-Ended up with error 225

Thanks in advance
[Android Software Development] guitardedhero:
Yeah, I was hoping the p9 libraries would not cause you the same issues the p8 libraries did. Dirty flash your rom and compare the files in 0.9.6 or above with the files on your device with the rom's files intact. Let me know what are overwrites from the mid and what are additional files your rom does not have. It's also possible that a very minor name change has occurred with one or more files so look closely. :good:

First step is to ensure at least 100mb of free /system space is available. Second step is to create a Permissive Selinux environment unless you already have SuperSU for root management, in which case, Enforcing is fine. :good:

Is that after the Aroma zip? Flash the permissions zip below to fix your problem and wait for an announcement saying Aroma is safe to flash. I'll let RP know. :good:

Delete the af.resampler build.prop lines or change their values to 255, save changes, and reboot. :good:
[Android Software Development] guitardedhero:
I made this zip for you if you want to test to find the culprit file. Instructions are inside, just extract the zip and add one library at a time with 0644 permissions and reboot until you bootloop. Let me know what you find. :good:
[Android Software Development] aki_007:
If you haven't flashed Tweak_prop.zip after installing A.R.I.S.E. Then you don't need to do anything and just reboot ,

Lower your volume to close to 33 % and see if same error is reproduced .

I am guessing that after sometime the behaviour of Viper4android shows abnormal .
[Android Software Development] Zubaser:
Most IRS does not work since 0.9.5. How can I fix this problem?
[Android Software Development] RSDamasceno:
The 0.9.7.1 is fantastic!

Has raised the bar again!

Congratulations for the excellent work [MENTION=4445176]guitardedhero[/MENTION].

Here's my profile. I changed the equalizer and it's closed of the perfection. I love it!
[Android Software Development] mattyditfc:
Finally have my m8 back with working top speaker :) dirty flashed rom etc as always. Flashed 0.9.7 but set perm failing "some changes failed" so isnt flashing. Not sure what issue is. Im usually quite tech savy on **** like this haha ill have a mess around or try 0.9.7.1
[Android Software Development] rolarocka:
For me 0.9.6 is perfect with atmos and exodus preset. Need to try 0.9.7 [emoji4]

Oneplus One
[Android Software Development] so.hell:
which version should i flash??

when i open dolby atoms.its show dolby atoms has stopped..

how to fix it???
[Android Software Development] mantakos:
Could you explain to me what the XPlay3S AtmosDD+ preset does? Is it for better compatibility with the GUIs? I read the instruction file but I didnt really understand.. Thanks
[Android Software Development] ederekun:
Uhm... it changes the config of the sound mod (what libs for this and that) through the system as it is fixed, while GUI is like an activating app...

Thanks/Like button for me if I helped ya!

Sent By CM13+S4A
[Android Software Development] mattyditfc:
Successfully flashed 0.9.7 with GH tweak.prop . sounding awesome so far with my ****ty earphones. True test will be in the car after work ! Great stuff as always guys
[Android Software Development] mantakos:
Just want to share what I found out. Since 0.9.4 dts dcc has been force closing. I deleted the folder and installed it as a normal apk. The fcs stopped but the app wasnt running (wasnt able to force close it) and it didnt cache data too. So now on 0.9.6 after deleting the previous apk I had fcs again. But now instead of deleting the the folder, i just force closed it and installed the apk over that. And now it seems to be running with no Fcs :good:

I hope this will help somebody.
[Android Software Development] matssa:
So if I understand correctly, you updated to 0.9.6, removed the apk from System/app/XXXXX and not the folder using TWRP, then installed the apk?

Gonna test this out, cause I keep getting this FCs... Really want to test this out.
[Android Software Development] mantakos:
Before updating to 0.9.6 i deleted the apk as i had it installed in previous version. Then i forceclosed the originally installed dts by navigating to settings/apps/show system apps and after that i installed the dts apk which i extracted from the arise zip
[Android Software Development] matssa:
Ok gonna test out a second method. How did you check that the app wasn't working correctly? Can't force close it and no cache data?
[Android Software Development] mantakos:
yes
[Android Software Development] aki_007:
If the app fc's then just delete the apk from system/app

reboot

then again push extracted apk into system/app

reboot and see if it works .
[Android Software Development] matssa:
I just tested out the following : remove apk from system/app/XXXX using TWRP, boot, and install extracted apk (didn't push it to system/app). Gonna test out like this.

EDIT /// After testing (playing audio), Cache still at 0, data still at 0. Very strange... Gonna try to push apk to system/app.

EDIT 2 /// As expected, FCs came back, so the phone really doesn't like it when it is in system/app or something. Gonna try to force close and update it with the extracted one.

EDIT3 /// Ok works now with no issues (got some data, got some cache, no fcs). Used Aroma V3 and got Dobly FCs, so flashed script supplied and erased file but still doesn't work (no crash buuuuut app freezes).
[Android Software Development] JellyTooth:
I think that the lgv10 libs made that massive change in audio quality in 0.9.7
[Android Software Development] phamous42:
Currently on 0.9.7.1 and I can verify that the sound stage magic happens with the Dolby props off. Been switching back and forth and the difference is night and day. The sound is much more forward and less separated with Dolby on. I feel like it takes away from the phenomenal staging provided by the other dsp's in ARISE's chain
[Android Software Development] arvindr07:
Use the Non-AROMA version. Zenfone 2 doesn't support AROMA
[Android Software Development] umeshbluezzz:
Ok thanx bro
[Android Software Development] kyle_el:
If you're using a custom ROM, you can just reflash it.

This removes root (if the ROM comes unrooted), and any custom kernels, audio mods, etc
[Android Software Development] RCT1:
Can't install without the aroma version.

I've a OP2 with oxygen os.
[Android Software Development] chikimonke:
I don't believe a dirty flash of the ROM will remove the modules though, which is what he was looking to do. I could be wrong though, still relatively new to the Magisk world.
[Android Software Development] gibbsnich:
IMHO to help you debug this more information is required:

Which ARISE version did you try?

Which TWRP version are you using?

Can you provide a log from TWRP after flashing?
[Android Software Development] kyle_el:
Yeah, I suppose I don't really know that for sure. Doesn't the Arise Module just move some of the arise files from one file to another? I feel like dirty flashing would have the same effect on the modules as it would only the sound system itself in that case.

Am I flawed in that thinking?
[Android Software Development] Mark_Draconian:
I solved this by catching "arise_customize.prop" manually and placing at internal storage.

After doing this, you just put true to whatever you wanna installed and should be ok on TWRP installation
[Android Software Development] makingccc:
Have anyone installed the latest version in Android 7.1.1 and worked?
[Android Software Development] gibbsnich:
yes
[Android Software Development] cmo220:
Has anyone gotten any of the Magisk Modules to work on the Pixel XL? It always gives me error 1 and says it can't mount /system. I like trying to solve these problems on my own but I'm about to give up and send logs when I have the time.
[Android Software Development] pokipokipxorn:
The OP, 2nd, 3rd post installation guide is confusing. TMI without clear links or instructions for quick install.

How exactly do I download (where?), flash/install the core (which version? dizzying array of release names with version but without dates) for Asus Zenfone 2 Laser ZE550KL? On Lineage OS Marshmallow, custom kernel, twrp, magisk.

Thank you.
[Android Software Development] Zackptg5:
If you can send recovery log, I'll look into it
[Android Software Development] gibbsnich:
Uhmm the very first link in OP takes you to AFH download page where you choose Aroma and then you choose the latest version (highest version number which BTW contains a date: e.g. v2.94 was released 294 days after ARISE was born).

You boot to TWRP, flash the zip you downloaded, choose Beginner if asked, then just follow the instructions :)

HTH & enjoy the sound!
[Android Software Development] secone00:
SwanSong I fully recommend over the others such as Genesis, Leviticus, Numbers, etc. Especially given the fact that you're on magisk, SwanSong is the only thing with any kind of magisk support. You can find the latest magisk version here:

https://xdaforums.com/android/software/r-s-e-sound-systems-auditory-research-t3379709/post71569390
[Android Software Development] cmo220:
I'm attaching the recovery log. Just so you know I'm using Pixel XL with the 3-17 version of Pure Nexus. I'm on Elemental X kernel and the 11.6 - Pixel version of Magisk. Magisk is working fine, except for this of course. Thanks for looking into it!
[Android Software Development] Zackptg5:
Can you upload the pixel edition of magisk so I can see the difference? Thanks
[Android Software Development] cmo220:
Here is the post with the link. I don't want to actually upload someone else's work. https://xdaforums.com/showpost.php?p=71573863&postcount=1029
[Android Software Development] Zackptg5:
Can you try these? Try regular version first. If you're unable to boot with it, provide a logcat and then flash ls version over top of it. Of course if regular version works, there's no need to try ls :)

Note that it will sit on the boot logo for a minute or so (this is normal - when scripts run)
[Android Software Development] cmo220:
Nope. They both booted back to recovery after sitting on the splash screen for a minute. Here's the log with trying both.
[Android Software Development] Zackptg5:
Doh! Stupid typo. Fixed in these ones. Same deal as before
[Android Software Development] cmo220:
Is there a simple file I can delete from recovery or something if it doesn't work again?
[Android Software Development] Zackptg5:
If you want to remove the module, just flash magisk uninstall script and then reflash magisk with your other modules. Note quite sure what you mean
[Android Software Development] cmo220:
Still not working.

What I was asking is whether there is a file somewhere I can delete to fix the not booting problem. The Uninstaller doesn't work. Not sure if my file is bad, or if it's because of Pixel being different, or because of the modified magisk. But the only way I have found so far is dirty flashing my ROM.
[Android Software Development] Zackptg5:
The magisk IMG is stored on the data partition so dirty flashing your rom wouldn't effect magisk modules. You'll need to flash mountmagisk zip (just Google it) and then delete stuff from twrp
[Android Software Development] cmo220:
OK. Maybe mount magisk will do it. I've only tried an uninstall. For some reason that fixes the not booting problem though. I don't wipe data when trying to fix not booting.

If you can figure it out it would be awesome but it's not too important. Everything seems to work right if I manually execute the Arise script. Thanks!
[Android Software Development] Zackptg5:
Think I got it this time. Another stupid typo...
[Android Software Development] cmo220:
This one works! I only tried 2.2. I didn't try the LS version. It didn't work the first time though. I tried again with dirty flashing Rom. Then boot to system. Then reboot recovery. Then flash Elemental X, magisk pixel, arise, your module, then reboot to system.

The module shows in magisk and getprop shows a lot of audio and media flinger stuff. Thanks a lot for all the work!