[Android Software Development] sonophilos:
ARISE Sound Systems Deuteronomy 2.2.3 Mac 'n Cheese Edition

​

is Obsolete. No further development is to be expected. Original post contents archived/hidden for posterity.

Mac 'n Cheese Edition! This is essentially my Classic Edition, which includes ViPER 2.3.4.0 and its Super Quality driver by default, plus my most up-to-date setprop that's been cleaned up for compatibility across more devices. This is an alternative to any other ARISE build and should not be installed alongside any other ARISE build. This is compatible with @ahrion Atmos builds and AM3D as long as Mac 'n Cheese Edition is installed first. This is NOT compatible with Magisk; SuperSU only, I'm sorry to say. Hope this helps! :good:

Link removed 2023-03-18

{Mac 'n Cheese Edition}

~

ARISE Sound Systems Deuteronomy 2.2.3 Black 'n Cheese Edition

​

Presenting...

Mac 'n Cheese Edition with a special all-black ViPER4ARISE cooked up by the blood, sweat and tears of our @Roi007leaf and put under intense scrutiny by myself. It is to be considered 'in beta' and has a visual quirk when pressing a selection in the lists, because it is built on the Holo design language which is not as receptive to theming as Material Design. If you're using an inverted CMTE or Substratum theme you likely have no need for this, as many such themes cover ViPER4Android/ViPER4ARISE. See the original release post for a demonstration of both the black theme and the quirks.

Link removed 2023-03-18

{Black 'n Cheese Edition beta}

~

ViPER4Arise Black 'n Cheese Edition

​

Presenting...

ViPER4Arise apks with a custom pure black theme cooked up by @Roi007leaf. They are compatible with all ARISE versions, just choose the apk corresponding to the version of ViPER4Arise / ViPER4Android FX you have installed inside the archive.

NOT flashable; extract and replace the apk where it's installed (probably /system/priv-app) with the one inside the folder corresponding to your ViPER4Arise version, inside the extracted folder. Then set 0644 (rw-r-r) permissions on the replaced apk, and either kill ViPER and reopen (it will probably FC the first time you try to open it) or reboot and open ViPER after your reboot to see the beautiful inverted theme.

See the original release post for screenshots demonstrating the Black 'n Cheese themed ViPER4Arise looks.

Link removed 2023-03-18

{ViPER4Arise Black 'n Cheese Edition}

~

Sonophilos Databases

​

Presenting...

Sonophilos Databases for getprop, Profiles and setprop

These are hosted on my Drive and I'll be updating the Profiles and setprop folders with latest versions as they come. My files for the ARISE Sound Systems Exodus, Leviticus, Numbers, and Deuteronomy releases have been revised and uploaded. GH, Ben and smee have access also, and may make use of these as they see fit. (Anyone else on the Team is welcome to message me on Hangouts or PM me with your Gmail address for access.)

Links removed 2023-03-18

{getprop database}

{Profiles database}

{setprop database}

~

Sonophilos FAQ/INFO

​

This information is relevant for the Exodus and Leviticus releases; may or may not apply to Numbers/Deuteronomy+

Q: I installed one of the ARISE versions including DTS and when I boot I get this popup: "Unfortunately, DTS DCC Service has stopped." Every time I tap OK it comes back! What can I do?

A: Reboot into TWRP, mount /system if it's not mounted already, and delete the DTSClientController folder from /system/app. Reboot and install the APK normally - if you used the AROMA (for Exodus releases), it's in /sdcard; otherwise extract the ARISE zip and it's in /system/app (or, for Numbers/Deuteronomy, /numbers/priv-app or /deuteronomy/priv-app, respectively) inside.

Q: Dolby/Atmos force closes! What can I do?

A: First, ensure you have SELinux set to Permissive; Dolby Atmos only works properly on Permissive setups. Then, if the issue persists, check /vendor/etc for audio_effects.conf and remove it if it is present there - if this is your issue it's most likely a 0b empty file.

INFO:

HTC One M8 users, if you're using Boomsound DO NOT install ARISE without making a backup. M8 users have reported bootloops/stuck at "Starting Apps" on Boomsound setups.

Workaround: use HK. ARISE is reported working on M8 with HK.

Thanks @smeejaytee for bringing this issue to light.

Thanks @necktru for confirming the HK workaround.

HTC One M9 users, if you're on an AOSP ROM such as CandySiX you might experience issues with ViPER/ARISE. (Driver install issues, processing issues, volume issues)

Leedroid ROM with Lee's kernel might also experience issues. (Cracking, popping, skipping, even with Ondemand governor and raised min CPU freq as recommended by Woody)

ViperOneM9, linked in my signature, has no such issues, however M9 Sense users will have a known issue with Atmos where the service does not start on boot and doesn't persist, meaning it can be killed by minfree or from the switcher. This is a limitation of HTC's audio system on Sense MM and may affect M8 / 10 Sense MM users as well.

This post is under construction and will receive ongoing updates with new information and new versions of the attached/linked as they become available. Please check the Database links at the top of this post for the latest versions of profiles and setprops. This FAQ/info section was last updated to reflect its relevance for the Exodus and Leviticus releases; information may or may not be relevant or up to date for Numbers/Deuteronomy+.

~

Sonophilos Kit

​

To achieve an identical configuration to the one I listen and test with:

First wipe /system and /cache in TWRP, then dirty flash your ROM and any other installs to /system you may have. You may want to back up /system before you install ARISE so you have a quick restore point for future versions that may require wipes to work properly. I've done this and it's the difference between a 3-minute restore or 20+ minutes of installers. You shouldn't need to wipe the dalvik/ART cache as no installed apps should change during this process.

Then, flash either the latest ARISE Sound Systems for your Android version, check under Newest Uploads here:

{A.R.I.S.E Sound Systems AndroidFileHost developer profile}

OR flash my preferred ARISE Sound Systems Deuteronomy 2.2.3 Mac 'n Cheese Edition, here:

{Mac 'n Cheese Edition}

Then, follow the instructions in the setprop and Profiles sections (optional). (If you're using Mac 'n Cheese Edition you have my lastest setprop included already.)

-----

setprop:

--

Download the latest Lover of Sound setprop from the Google Drive database linked at the top of this post. Rename it to arisesound_setprop, and place it in /sdcard. Flash any Numbers/Deuteronomy zip (all have the setprop installation script built in, and it's okay if you already flashed it). This will replace the default arisesound_setprop in /system/su.d with the Lover of Sound version, which you can confirm by examining the file in that location after installation. As long as you have arisesound_setprop in /sdcard, it will continue to overwrite the default one with future installations. Anytime you modify or replace this file with a new one make sure you reboot - setprop properties are applied on boot, as opposed to entered semi-permanently into your build.prop. THIS IS THE PREFERRED AND OFFICIALLY SUPPORTED METHOD since Numbers, and I have officially stopped development and support for the deprecated tweak.prop method as of Deuteronomy 1.4.

To confirm setprop is fully operational, first examine the file in /system/su.d to ensure it's the Lover of Sound version (it's clearly marked as such), look for some unique properties that you know for sure aren't included in your default build.prop, then enter the command 'getprop' in your terminal emulator of choice and look for those properties in the output (which is helpfully alphabetized). If they're there, it worked! If something in setprop causes you issues, please let me know so I can troubleshoot, and in the meantime delete the arisesound_setprop file from /system/su.d with a root file manager or the TWRP File Manager in the Advanced section if for some awful reason you're unable to boot after using setprop (PLEASE let me know if this happens.)

-----

Profiles

--

Make sure V4A has Storage permissions in Settings -> Apps so it can read and write to the Profiles and Kernel (Convolver/IRS) folders. Toggle these off and back on if you're having issues - the usual symptom is that the Audiophile profiles installed by ARISE by default will not show in the Load Effect Profile menu, and/or that the numerous IRS installed by ARISE by default will not appear in the Convolver menu.

** Many users have been able to fix permissions issues by installing V4A as a /data app on top of the default ARISE /system install. To do this, extract an ARISE zip, look in /system/priv-app (for Exodus and Leviticus) or /customize/app (for Numbers and Deuteronomy+,) and install the V4A APK inside. It will appear to be an "update" since there is already an install in /system. Install, reboot, test to see if IRS/Profiles show up. **

To use my V4A profiles, extract Lover_of_Sound_Profiles_(version) and place the two folders inside (Sonophilos-Headphones and Sonophilos-Speakers) in your V4A Profiles folder. If you're not sure where to find this folder, check OP for possible locations. (It's probably either /sdcard/ViPER4Android/Profiles or /data/media/legacy/ViPER4Android/Profiles.) If you see the Audiophile profiles, you're in the right place. Mine (was) in a very unusual place, which is part of why I (was) having issues uploading before:

/mnt/runtime/write/emulated/legacy/ViPER4Android/Profile

To get the full intended effect of my Profiles:

Set Lock Effect Mode to Headset in the V4A menu to cause the settings applied in the Headset tab (which has the most options available to it) to apply to all audio outputs - aux/headphones, device speakers, Bluetooth and USB. I use two separate profiles because both are configured differently on the Headset tab.

Use Sonophilos-Speakers for device speakers, aux output, Bluetooth or USB speaker output. Use Sonophilos-Headphones for wired headphones or Bluetooth headphones, or headphones amplified through a USB DAC.

I encourage you to configure the Headphones profile to reflect your headset model and personal taste - by default it's set for my testing setup on ATH-M50s.

-----

tweak.prop (DEPRECATED):

--

Extract the ARISE zip and look in the Extras/TweakProp folder for the tweakprop.zip tool itself. DO NOT use the sonophilos_tweakprop.zip; it is nonfunctional at the time of the last edit to this post. My most up-to-date tweak.prop (up until Deuteronomy 1.4) are available on the Google Drive setprop database linked at the top of this post. tweak.prop is technically intended for use with Exodus and Leviticus only; Numbers and Deuteronomy+ use 'setprop', which is NOT equivalent to or compatible with tweak.prop - use one or the other, not both. (Theoretically, you could apply some properties with tweak.prop and then add some more with setprop, but this defeats the purpose of setprop which is to have an untouched build.prop. Setprop properties will overwrite tweak.prop properties on boot.) I no longer support, test with or use personally the tweak.prop method, as setprop appears to be fully functional on my device. Remove /system/su.d/arisesound_setprop if you intend to make use of my tweak.prop.

Then, rename sonophilos_Lover_of_Sound_(version)_tweak.prop (or your chosen/configured tweak.prop) to just "tweak.prop", and place it in /sdcard. You can safely replace the default ARISE tweak.prop with mine, mine will include all the same props/options included with the version number shown. Remember to remove /system/su.d/arisesound_setprop if you intend to make use of my tweak.prop with Numbers or Deuteronomy+.

Dolby DS2 is ON by default in my tweak.prop since in-dev release Exodus 0.9.9.3. Several users, including myself, experienced no audio from the aux/headset port when using in-development Exodus versions with Dolby DS2 ON, however this issue was fixed (for me) as of Exodus 0.9.9.3 and DS2 continues to work (for me) with the ARISE Sound Systems Exodus release, Leviticus release and Numbers release. Comment these lines out from tweak.prop before flashing tweakprop.zip if you want to try with Dolby DS2 OFF, or set them to "false" if you need to disable them after already flashing a tweak.prop that has them enabled.

audio.dolby.ds2.enabled=true
audio.dolby.ds2.hardbypass=true

The Dolby DS2 information is probably no longer relevant; DS2 has been fully operational (for me) and I've heard no reports of issues since Exodus was in development. DS2 is even included in the default setprop for the Deuteronomy release.

** Make sure you have no files named "tweak.prop" except the one you intend to flash, or the tweakprop.zip might use any file with that name in /storage! **

To apply tweak.prop (on Exodus or Leviticus, or optionally Numbers/Deuteronomy+), flash tweakprop.zip (inside the Extras/TweakProp folder in the ARISE zip) to amend the props in /sdcard/tweak.prop to your build.prop.

You can watch the output in TWRP to confirm it's working, to make sure the correct file was selected, and to check which props were overridden (ie present in your default build.prop) vs added.

~

Bonus Content

​

Special bonus for those of you who actually read this entire post: my Spotify playlist I've been using to test each build. The theme is heavy, low bass presence with detailed, dimensionally deep treble, to listen for balance, presence and space of the sound mix overall. I may or may not add to it as I find more that fits that theme. Enjoy!

Sonophilos - Zone

Another bonus for the thorough reader and those who returned to my OP after my return to XDA July 2017: my newer playlist. Focus is on complex rhythms and melodic basslines.

Sonophilos - Cusp

Another special bonus: fixes to two of Android's most annoying behaviors with audio can be found here: Don't Pause and SoundAbout - I am aware that, noticeably, since this posting, SoundAbout's feature that fixes the issue noted has become a paid feature. :confused:

As ever, I hope this helps! (y)