yashsingh1/xdaforums huggingface dataset:
[Android Software Development] DingoDingo:
Round 6 hours?

Latest .SwanSong builds are really special, I think it is time to delete my old favorite 2.2.3 Classic.

I am with ARISE from begining, there was ups and downs but now... WOW!, just missing posts from few old ARISE team members.

My old Nexus 4 is really singing it's Swan song. Hope it will last untill new device and new magic from you guys.

Thank you ARISE!
[Android Software Development] ShinraTensei04:
None of the things I try to flash show up when I reboot, even though it says it's successful in the recovery... What should I do?
[Android Software Development] Drasickness:
put manual ARISE_version.prop in zip file to system folder, then flash again
[Android Software Development] raylogic:
Thanks for this, used root Explorer and it came up with the following:-

- sound right?

- missed any?

Thanks again.

R.
[Android Software Development] raylogic:
OMG, just changed the first one and this is the result.... WTF help..
[Android Software Development] Lughnasadh:
[MENTION=4445176]guitardedhero[/MENTION] Excellent job on the new OP. Well laid out and informative. Thanks for that!

I did notice the Troubleshooting Guide wasn't there (or maybe I just missed it, which wouldn't surprise me, lol). If it is indeed missing, it may be helpful to put it in there considering all the questions the team gets from people who don't read it beforehand. Just a suggestion.

Thanks for all the hard work and time you guys have put into this. It is truly audio Nirvana. Much appreciated! :):):)

ARISE UP!
[Android Software Development] guitardedhero:
First thing to ALWAYS check is the current free /system space available when navigating to /system. :good:

Please, this is absolutely incorrect advice. There are very specific reasons that we use Error 1 during recovery sessions. These Error 1's are always included with the necessary information and the next course of action depending on what prompts the Error 1.

In this user's case, Error 1 was the result of NOT instructing the installation script to install the Core System module (install.deuteronomy=true) while NOT having an installed Core System module (determined by the absence of /system/ARISE_version.prop).

The Core System module provides an extremely customized audio_effects configuration template that most of the optional modules depend on being in place in order to add/remove their entries.

That is also why the Core System module should only ever be installed a single time if planning to have several recovery sessions to experiment with the different modules without having to wipe system or dirty-flash the device rom zip (Skip to Modules in AROMA, remove the value of "true" from "install.deuteronomy=true" in non-AROMA).

We try our hardest to include you guys in as many aspects of the process in order for you to learn quite a bit as well as having a heavy influence on the resulting sound system installation. We realize that much of this stuff is new and unfamiliar as we always push the possibilities of the Android platform rather than do what everyone else does.

However, the screenshot displaying the recovery Error 1 also displayed precisely why the error is there as well as the necessary information and course of action to take. We can only do so much to keep you guys on the smooth pavement. :good:

Only setprop's in /system/su.d should be demoted with 0600 permissions for troubleshooting purposes. Leave the setprop binary in /system/bin as it is. :good:

---------- Post added at 01:28 PM ---------- Previous post was at 01:26 PM ----------

Damn, I wasn't quick enough. What's your state after a reboot?

Thank you very much for noticing both aspects! Troubleshooting documentation certainly should be made available in the OP! :good:

You deserve a high-five from the entire team for even knowing the Troubleshooting documentation exists! :high-five:
[Android Software Development] raylogic:
Dude help, file manager can't find anything now, am I OK to reboot? Into recovery and clean install my whole system?

Beep.
[Android Software Development] guitardedhero:
Boot to TWRP

Mount > check System

Advanced > File Manager

Navigate to /system/bin

Tap setprop > chmod > 0755 > Swipe to execute

Mount > uncheck System

Reboot
[Android Software Development] raylogic:
Sigh........

........ Of relief!

R.
[Android Software Development] royalh:
I have a Note 4.

are the non-Samsung folders needed if all i install is the "core" V4A component?

These folders:

/system/lib/soundfx/asus

/system/lib/soundfx/huawei

/system/lib/soundfx/sony

and these files

/system/lib/dolby*.*

/system/lib/DTS_HPX_MODULE. so

and any other file/folder not needed for the core install?

Or maybe an easier answer would be, how can i just install the core V4A app and the Viper4Arise app without all the extra (unneeded? ) files & folders?
[Android Software Development] facethepro:
Hi, i removed deep buffer but for some reason its still not working on YouTube. Its okay in Spotify, but not in YouTube. Help?
[Android Software Development] guitardedhero:
What device? Is MusicFX installed or part of your rom?
[Android Software Development] facethepro:
Galaxy S3, my rom has AudioFX built in, which i have disabled. (crDroid 7.1.1)
[Android Software Development] mohand06:
Same device and rom, audiofx disabled. SwanSong 2.78-1, V4A, arkamys, ice preset2, pure config, musicefx, remove deepbuffer, permissive: V4A processing on local and streaming audio, youtube and all
[Android Software Development] facethepro:
Deuteronomy 2.78-1. I only installed V4A, deep buffer removed, permissive too.
[Android Software Development] tcat007:
I just reinstalled 2.78 aroma after updating ROM. Selected 2.5.0.5. When I check status it says 2.5.0.4. Which is it?
[Android Software Development] guitardedhero:
Install MusicFX and disable it if not already installed and reboot. :good:

Normal. :good:
[Android Software Development] nintendo424:
Can someone explain how to properly install ARISE on a Nexus 6P? I've tried the AROMA installer through TWRP and usually it ends in a bootloop.

My setup is like this;

Nexus 6P

Magisk V11.1

Rooted with Magisk

TWRP 3.0.3

Kylo Kernel

Stock ROM

I usually select all modules, but have tried with none installed other than ATMOS. I select Viper 2.5.05 as the core.

Maybe I'm missing something?
[Android Software Development] Techvir:
Nexus 6p here

Installed version 2.78 with most of the selection except esira, viper xhifi and dolby.

Persmissive mod

Terminal says

angler:/ $ su

angler:/data/data # su -c dumpsys media.audio_flinger

Unknown id: media.audio_flinger

Please advise

Sent from my Nexus 6P
[Android Software Development] ShinraTensei04:
I see... So here's my Error:1

I flash Deuteronomy 2.77 successfully, then remove the true value in it, then try to flash other stuff, but still get the error saying DU isn't installed. What's do I do now? How can I check if DU is installed?
[Android Software Development] LazerL0rd:
Can't you have MusicFX uninstalled?
[Android Software Development] guitardedhero:
Are you using the Magisk™ module linked in the OP?

You might try the dumpsys command in / or /system rather than /data/data.

If it's the Error 1 shown earlier, it means that there is no "true" value for "install.deuteronomy=" AND /system/ARISE_version.prop does not exist. Check for the presence of /system/ARISE_version.Prop.

Of course. We're simply troubleshooting a bit.
[Android Software Development] nintendo424:
I tried it. I flashed it after installing ARISE, and it gave a bootloop. I wiped and tried it before installing, and also got a bootloop. When is the 'proper' time to flash it?
[Android Software Development] Techvir:
Same thing again

angler:/ # su -c dumpsys media.audio_flinger

Unknown id: media.audio_flinger

1|angler:/ # cd /system

angler:/system # su -c dumpsys media.audio_flinger

Unknown id: media.audio_flinger

1|angler:/system #

Sent from my Nexus 6P
[Android Software Development] Shockz:
What does this module do? I have installed the latest AROMA and everything seems to work fine without the module and I am rooted with Magisk 11.1
[Android Software Development] mrrocketdog:
may have already tried but for me nothing in front of

"su -c dumpsys media.audio_fliinger" works.

"err on the side of kindness"
[Android Software Development] Enismirdal:
Since I'm wandering by and I write a very similar module for myself, might as well!

Short version: The module is primarily for those using Magisk with MagiskSU as their root solution, it replaces the SuperSU-only su.d scripts written by Arise. If using SuperSU, it's not necessary.

Long version: Arise needs an selinux patch to keep Viper running on most selinux enforcing ROMs, and a setprop file to set the system properties that it either requires or benefits from, and the module provides those for MagiskSU users. SuperSU users don't need it, because Arise already creates selinux and setprop scripts built for SuperSU.
[Android Software Development] ShinraTensei04:
It is the error shown a few posts above. I didn't initially have the ARISE_version.prop file in /system/ and then I flashed Deuteronomy successfully. But even then there wasn't any ARISE_version.prop file, so I had to manually place it, after which the other modules were getting flashed, but the apps weren't actually installed on reboot for some reason.... Is it because I had manually placed the ARISE_version.prop, or because Deuteronomy didn't get flashed right, or because I had to place the .prop before flashing DU?
[Android Software Development] Shockz:
Well I tried flashing it and it just causes a bootloop for me as well and everything seems to work fine without it so im not going to worry too much.
[Android Software Development] guitardedhero:
Did you verify sufficient free /system space to be available before flashing?
[Android Software Development] Enismirdal:
Edit: Ninj'd!

Now that I'm thinking about it - actually, maybe the modular zip could benefit from some wording changes. It even got me confused for a good thirty seconds, and I took it apart and put it back together before use. (I did, however, accidentally put arise_customize.prop in the wrong folder by accident...)

Personally, I prefer to install modules from Magisk Manager. I have gotten a couple of bootloops flashing them from TWRP before, so in general I don't bother with that any longer. You could always give that a shot, if you haven't already?
[Android Software Development] ShinraTensei04:
Of course, I have over 350 MB free. I'm not having selinux set to permissive though.
[Android Software Development] luigidk:
Running 2.78, great, great sound. I've been following this v4a thread from WAY back and this is the best overall experience hands down.

I used the speakerphone on my n6p today and the callers all stated the echo from my end was untenable.

Is it possibly related to 2.78? It is just as likely i hadn't noticed before.
[Android Software Development] mrrocketdog:
[MENTION=7615104]ShinraTensei04[/MENTION] , not to be butting-in but ; did you put arise_customize.prop in root of sdcard? and did you mark "true" what you wanted installed?

just double checking.

"err on the side of kindness"
[Android Software Development] ShinraTensei04:
So in order to get it to work, did you have to manually place the .prop file and then flash Deuteronomy?
[Android Software Development] Enismirdal:
Oh. Don't mind my musings! What I meant - actually, nevermind, I'll just explain quickly.

When you first run the Arise modular installer, it places arise_customize.prop at the root of /sdcard. You then have to modify that file and set every entry you want (including the core install.deuteronomy option) to true. Once you've done that, you re-flash the installer, and it does what the arise_customize.prop file says.

I personally tried to manually place arise_customize.prop before flashing at all, and pre-set what I wanted, but I accidentally extracted it to a subfolder, not /sdcard, and so got Error 1 and was very confused.
[Android Software Development] Shockz:
Just tried it, still a no-go unfortunately. Not really sure how to figure out the problem, is there a boot log magisk creates I can check?

Edit: Looks like there is, made it to stage 5 looks like, I gave up after about 6 min of boot time.

** Magisk post-fs mode running...
** Magisk post-fs-data mode running...
/data/magisk_merge.img found
/data/magisk.img found, attempt to merge
/dev/block/loop0 /data/magisk.img
/dev/block/loop1 /data/magisk_merge.img
Merging: ARISE_Magisk_Module
Merge complete
MagiskSU: Moving and linking /sbin binaries
MagiskSU: Exposing su binary
MagiskSU: Starting su daemon
* Preparing modules
* Stage 1: Mount system and vendor mirrors
* Stage 2: Mount dummy skeletons
* Stage 3: Mount module items
* Stage 4: Execute scripts
post-fs-data: /magisk/ARISE_Magisk_Module/post-fs-data.sh
* Stage 5: Mount mirrored items back to dummy
* Reading props from /magisk/ARISE_Magisk_Module/system.prop
[Android Software Development] Enismirdal:
There is, check Magisk Manager. It ought to give you at least some clue, though if it doesn't give enough, there's a debug-level logging option in the settings that might help further. I've never actually run into that issue without a malformed module (usually my own fault), so I'm not offhand sure what causes those bootloops. I have heard that if you're using a whole Magisk ROM or a module that attempts to overwrite the same file or dir, it can cause issues, but that seems to be a pretty rare occurrence.

Edit: Oh nevermind, I see you found it yourself.
[Android Software Development] ShinraTensei04:
Yes, that's right. This time I put true for deuteronomy again, and then also for v4a. Both successfully flashed, but now my phone won't boot up anymore.... again.

I checked the selinux status from twrp, said permissive, idk how(I didn't set true for selinux in the .prop) .Also, the v4a app this time was indeed installed. I checked from file manager by going in /system/priv-app/Viper4Arise

So all I need right now is to boot into my phone properly...
[Android Software Development] guitardedhero:
Hey Luigi!

Was this a typical voice call using microphone and earpiece or through a hands-free Bluetooth™ connection? There is definitely some reverb and spatial effects, especially with multiple modules installed. Sometimes, it's only V4A though, and if placing a typical voice call using the phone's hardware, disabling V4A's Speaker output might be enough to resolve that annoyance completely. :good:

Edit*

I missed the speakerphone bit of information, definitely try another call with that same caller while V4A's Speaker output is disabled whenever convenient for you both. :good:
[Android Software Development] ShinraTensei04:
Wait, so it automatically places the customize.prop to /sdcard if you try to flash the installer without the customize.prop? I always place the customize.prop to /sdcard manually, and then set the values, then flash the installer.
[Android Software Development] guitardedhero:
What root management solution are you currently using?
[Android Software Development] Enismirdal:
It certainly did when I accidentally mis-placed my customize file. I still think it's better practice to place the prop file manually, as you do, and it saves you a reboot.
[Android Software Development] guitardedhero:
If you experience Error 1 only once, it explains everything clearly. :good:
[Android Software Development] mrrocketdog:
and that saves a flash/reboot by placing manually. as far as your phone now not booting up , i am truly at a loss. :( [MENTION=4445176]guitardedhero[/MENTION] , are you or another more knowledgeable person than me around to chyme in?

damn. ninja'd.:good:

"err on the side of kindness"
[Android Software Development] ShinraTensei04:
SuperSU. It comes as a module in the stock-based rom that I flash. Here's the .zip of the supersu it flashes.

https://drive.google.com/open?id=0B9aX5nm-yidFS3UyTUxWSkNuWVE
[Android Software Development] Enismirdal:
Honestly, I was confused for a solid half-minute by Error 1. Once I figured out what it was meaning, I was just fine, but that first sentence is a touch awkward. "This modular installer requires Deuteronomy to be installed or to be already installed." made me think 'Wat? But I just told you to install...' for a bit, even though I ought've known better.

To be fair, that's not wholly Arise's fault, I did accidentally extract the customize.prop file to a subfolder, rather than /sdcard root.

Edit: That all said, no criticism intended, I merely think that a slight wording change might improve clarity. Arise is an incredibly impressive piece of work and one I've been following closely (and poking at, and periodically breaking my own installs of, and writing personal setprops for) for a few books now, and I am (at this very moment) greatly enjoying the results of the latest version.
[Android Software Development] ShinraTensei04:
Another weird thing about my phone now, after getting the bootloop, is that it won't charge when it's switched off: it shows the battery for a sec, then shows a usb logo, then switches off. It only charges in fastboot or recovery mode...
[Android Software Development] Neo.Collin:
Looks like everyone missed my request since it was last post... Any suggestions on what I can do to get ARISE working on my Mi Max?
[Android Software Development] CygnusHyoga:
Reflash your rom :D

Thats something wrong with your rom.

Give a very specific information what device, cusrom/stock, recovery, etc etc etc and what procedure u use to flashing arise lol
[Android Software Development] Enismirdal:
Well that's a little more peculiar. There are a few possibilities, but I'm not familiar enough with the symptoms of errors, especially possibly ARISE-based ones, beyond my own device. It sounds, tentatively, like something got goofed up in the bootlooping. Personally, I'd probably reflash /system and /boot and see if that helps, and try a reinstall of ARISE afterwards if it does.

Edit: Oh, yeah, or you could just dirty flash your whole ROM, as mentioned....
[Android Software Development] saiz136:
Is it OK to install these with HTC Boomsound on a Sense UI?
[Android Software Development] ShinraTensei04:
Yeah, I'm going ALL THE WAY back to stock rom, which is gonna take a while, after which I'll root the phone, and then give the installer a shot.
[Android Software Development] luigidk:
Hi!

I'll give that a shot,

Thanks
[Android Software Development] Wolfcity:
Had the same until I made a log that told me: You have not enough space on your system partition. After deleting some things it worked flawlessly.

Btw, great stuff, until now I only used viper4android but after reading this thread I wanted more! Flashed latest aroma zip and installed viper4android 2.5.0.5, Dolby Atmos, Arkamys and ICE.

Will report later, the first impressions are awesome. Thx for this.
[Android Software Development] Roi007leaf:
New aroma is up!

Changes:

- Fixed HOLY**** ICEPreset for new user

- Added PURE**** ICEPreset By [MENTION=4445176]guitardedhero[/MENTION]

https://www.androidfilehost.com/?fid=457095661767138337
[Android Software Development] Raakakossu:
Am I correct that modular+aroma has everything I need for installation? I already flashed deuteronomy 2.78+1 modular+aroma and viper 2.5.0.5, dolby atmos, all ice stuff 2+holy**** etc. My question is do I need to make changes to prop files? And how do I know all those installed stuff are working? Atleast viper and DA is working. Thanks!!
[Android Software Development] fgbustoa:
2.79 non aroma version doesn't install ICE PURE**** preset. Can you check ???
[Android Software Development] kyzn:
How do you check? I mean, what should I be looking for to see if the feature was installed correctly?
[Android Software Development] DJ-Studd:
I would be keen for any Tasker interaction also, as per the above. :good:
[Android Software Development] mohand06:
Enter first: su

Then : dumpsys media.audio_flinger

---------- Post added at 08:22 AM ---------- Previous post was at 08:19 AM ----------

Same procedure
[Android Software Development] BodhiBrock:
My sounds are amazing thanks to ARISE. If you guys get bored how about a home screen widget for V4a? ?
[Android Software Development] ShinraTensei04:
Error: 255 on aroma installer, bootloop on non-aroma.
[Android Software Development] hypnoc:
I just installed ICEsound and toolbox. How do I know if they work because there is no app add up to app list like when I installed Dolby Atmos?
[Android Software Development] kyzn:
You can use the "su -c dumpsys media.audio_flinger" command in terminal to check if you have ICESound.

As for the toolbox, it's in "/root/system/su.d" directory.
[Android Software Development] Jsilver73:
[MENTION=4445176]guitardedhero[/MENTION] please could you help us to understand the difference between the driver in the 2.5.0.5 v4a and the old one in 2.3.4.0 ?

I see in the aroma explanation the comment that you like the 2.5.0.5 one so in my mind you being the ARISE guru and all this must mean it's the best one, but I often see other users insisting that 2.3.4.0 had better sound quality because of the superior quality driver.

So I'm confused - obviously being a flashaholic I want/need the very best of everything lol - honestly 2.5.0.5 sounds amazing to my tone deaf ears and when I tried 2.3.4.0 I can't honestly say whether I noticed a difference, although I did notice that viper seemed to be processing at a lower rate.

Looking forwards to getting the gospel according to [MENTION=4445176]guitardedhero[/MENTION] :laugh:
[Android Software Development] fgbustoa:
Open with a text editor /etc/icesoundpresets.def, and see name property
[Android Software Development] DEVILOPS 007:
What's the difference between pure**** and HOLY****?
[Android Software Development] kyzn:
Is that the 3rd line from the top? Mine says -

name ARISE_PURE****_WIRED.ist
[Android Software Development] :
Thanks.Working good
[Android Software Development] Roi007leaf:
There is
[Android Software Development] Techvir:
http://cloud.tapatalk.com/s/58a838c18cad8/log.txt

Can someone look at my dumpsys log please

Sent from my Nexus 6P
[Android Software Development] BodhiBrock:
Whaa? It's not on my widget list. I have the High Times Cellular 10. The only drawback for me is all the flipping back and forth for whatever situation occurs.
[Android Software Development] lieuliau:
I tried to flash Deuteronomy 2.3.3 on Nexus 9 but i have this error Updater process ended with ERROR: 1, how to fix it please?
[Android Software Development] ipmanwck:
Flash latest aroma version. I have now changed to it after having used 2.3.3 for ages.
[Android Software Development] Roi007leaf:
Bottom widget
[Android Software Development] SHEKARansd:
Is it works on android 7.1.1
[Android Software Development] kiva1:
Yes
[Android Software Development] z3nith66:
Ok I'm in a bootloop and I suspect the Magisk Module. How do I fix it?

Reflashed the ROM, still bootloop. OP3 with LOS14.1...
[Android Software Development] Shockz:
Delete the module from the magisk folder in TWRP. Use the mount-magisk zip from here https://xdaforums.com/apps/magisk/collection-magisk-modules-t3445257 to get access to the folder in TWRP.

Could you post your magisk.log so we can compare? Thanks!
[Android Software Development] SHEKARansd:
I am using ressurection remix 5.8 succesfully istalled but driver installation failed
[Android Software Development] Shadowghoster:
I have no idea but sometimes magisk seems to mess up things. Try most recent 2.77 module and latest installer. If you have some logs that would be nice too. There should be magisk.log or magisk_last.log in /cache.

Running fine for me with RR 2.8.1 on OnePlus One.
[Android Software Development] lieuliau:
I use 2.79 aroma installer but the background is transparent a lot, so it's hard to read text on that. Is there any way to fix that?
[Android Software Development] SHEKARansd:
Please give a direct link to latest build