[Android Software Development] A.R.I.S.E. Sound Systems:
Pertinent Information

​

Mission Statement

The ARISE mission objective from the very beginning was to create the go-to resource for the most comprehensive collection of unique and independent sound systems. Each uniquely named sound system is its own entity and not an update or a recycling of a previous, differently named sound system. The only evolution is our research and knowledge along the way.

We understand that sonic perception and preference is among the most subjective of life's joys. To maximize our abilities and resources, the vision is to have a growing database of unique sound systems written from scratch from which the user can choose and experiment with the different available sound systems.

There is no denying that the many different variables combine to create different experiences for different users and different devices. Providing individual sound systems instead of maintaining and updating a single sound system also eliminates the itch that is being on the latest and greatest version even though the user may prefer the sound of a version several iterations previous to the current one.

Remain confident knowing that it is certainly expected that many users will prefer one sound system overall even over the course of several new sound systems afterwards. Never feel disappointed if unsatisfied with a newly released sound system or feel pressured to be satisfied with the latest offering. Remain confident knowing that those that have curiously optimistic experiences could very likely have had a less than satisfied experience with your favorite sound system. Furthermore, the two different viewpoints may intersect at several other sound systems. The near limitless variables provide near limitless results.

However, one objective remains a constant: To provide the best quality sound experiences from installation to fine tuning the adjustable settings to create a tailored sound profile seemingly made just for you. Only the latest and the greatest components are used and any legacy components used are those that have proven time and time again to be the absolute best available at what they do. All you have to do is extract and examine the contents of our sound systems and compare to all other sound mods available. You will quickly realize why our sound systems stand out among the rest and why all the others sound similar to one another and have similar issues.

Finally, the community vibe and quality support are second to none and the lifeblood of this project. This project's growth and success is the result of many, many users not mentioned in the OP. We also take the condition of your property extremely seriously. If we are to recommend a user to modify their device by installing our sound system then we assume the responsibility to exhaust all available resources to ensure that the intended experience is obtained - no compromises.

That is why you'll never see a disclaimer saying that you are on your own after installing any of our sound systems and that we are not responsible for any catastrophic results. We thoroughly research, test, and dissect everything we make available to you in order for us to locate and eliminate any unexpected obstacle in the way of experiencing a sound system as it is intended.

ViPER4Arise™ Setup

Open ViPER4Arise™

Menu > Show Notification (block if desired by long pressing notification)

Menu > UI Setting > Expert

Menu > Save Effect Profile > New Effect Profile > "Stock" (this will help you find your working v4a directory if using ViPER4Android 2.4.0.1 or below)

Begin playing audio file

Open v4a

Uncheck Enable v4a

Check Enable v4a

To use the Audiophile™ Profile with ViPER4Android 2.5.0.5's default directory path simply extract the Audiophile™ Profile zip and paste/merge the /ViPER4Android folder into /sdcard, /storage/emulated/0, or /data/media/0.

Paste/merge /ViPER4Android into the directory where /ViPER4Android/Profile/Stock exists if using ViPER4Android 2.4.0.1 or below.

Possible location paths using ViPER4Android 2.4.0.1 and below are:

/data/media/0

/data/media/legacy

/mnt/runtime/write/emulated/0

/mnt/runtime/write/emulated/legacy

/sdcard

/sdcard/0

/storage/emulated/0

/storage/emulated/legacy

Audiophile™ Profile ViPER4Arise™ Settings

ViPER4Arise™ > Enabled

ExtremeBeats™ Perfection EQ Preset > 3.5, 4.5, 5.0, 3.5, 1.5, 1.0, 3.5, 4.5, 5.0, 3.5 (Enabled only on Speaker)

Convolver > Enabled

Impulse Response > DFX Hip Hop Modern.irs or DFX Metal Rap Big Bass.irs

Cross Channel > 0%

Dynamic System > Enabled (Headset only, when needed)

Listening Device > Common Earphone v2

Dynamic Bass > 14%

ViPER Bass > Enabled

Bass Mode > Natural

Bass Frequency > 40hz

Bass Boost > 13dB

ViPER Clarity > Enabled

Clarity Mode > Natural

Clarity > 6dB

TweakProp

tweak.prop source

Preparing an /sdcard/tweak.prop file before flashing tweakprop.zip gives the user complete control over any entries to /system/build.prop and is purely optional.

One or more tweak.prop presets will be included in the sound system zip for the user to utilize if desired so always extract and examine for any updated entries. Typically, a suggested and an alternate tweak.prop preset will be included. If /sdcard/tweak.prop already exists, the user can simply copy the contents of the desired tweak.prop preset, paste over the same section in the existing /sdcard/tweak.prop, and save changes.

If the user does not wish to utilize tweak.prop but wishes to use the provided build.prop entries, a simple copy of the desired entries from the tweak.prop preset and paste into /system/build.prop is certainly an acceptable option. Save changes before rebooting to test the effect of any new or removed entries.

getprop

Our research is heavily dependent on knowing the properties of as many devices and roms as possible. The properties of your device and rom can be displayed by typing the following into any terminal emulator on your device after a rom flash or before installing the sound system:

getprop

Tap Enter and the full list will then be displayed which can be copied to a new .txt file named using your device model and operating system. You can contribute by adding yours to the A.S.S. getprop Database linked just below under Downloads.

setprop

The /extras/setprop folder holds one or more setprop files that execute during boot when placed in /system/su.d with 0755 permissions. It is recommended to "Enable SU during boot" in SuperSU's settings and, of course, SuperSU is required for this activity. When executed, the setprop script will add or modify build property lines until a device reboot to local.prop instead of permanent lines in /system/build.prop. This has the same effect as modifying /system/build.prop, but is less obtrusive and allows the user to boot to TWRP, in the case of a bootloop, and do the following:

Mount > System

Advanced > File Manager

Navigate to /system/su.d

Tap the recently placed setprop file

Tap Delete and swipe to confirm the deletion

Mount > uncheck System

Reboot

This is an easier maneuver than searching for a backup of /system/build.prop that was created at an earlier time, copy it over the bootloop-causing /system/build.prop, set 0644 permissions, and reboot. This is why /system/su.d is the recommended location to place a setprop by any name with 0755 permissions and not /su/su.d, as /su is inaccessible via TWRP'S File Manager.

The Numbers™ sound system will automatically install arisesound_setprop, (the same one in /extras/setprop which is only there for easy reference), during the Numbers™ sound system installation. However, at the very end of the installation, the installation script will search for /sdcard/arisesound_setprop and, if found, copy it over the default arisesound_setprop. This operation indicates that the user has decided to use a setprop other than what is provided by the sound system by default.

If an automatic installation of a custom setprop is preferred, the setprop must be directly in /sdcard and named arisesound_setprop resulting in /sdcard/arisesound_setprop. Again, this is only necessary if the user prefers the installation script to handle the entire custom setprop operation.

When a custom setprop is manually performed by the user, the setprop can be placed in /system/su.d with any name and 0755 permissions. It is important to ensure only one setprop is in this location so delete any other if existing after placing the preferred custom setprop.

Finally, setprop will only execute if in a proper script format beginning with a "she bang" header:

#!/system/bin/sh

Comments to describe or provide information should always begin with "#". A line that extends wider than a device's screen will always be viewed as a single line until Enter on the keyboard is pressed, ending the previous line and creating the next line, even though it may look like multiple lines exist on the screen by the time Enter is pressed. Only a single # is necessary at the beginning of this "comment line" and can be confirmed by viewing in landscape unless the single comment is a very, very long single comment line which extends further than the width of the device's screen even in landscape.

The third and final component is the command section of the script. The setprop script begins with the command, "setprop" if following, at any point, a "she bang" header:

#!/system/bin/sh

Following the setprop command is a space ( ) to indicate that the command is decided and ready to accept an "argument", which is essentially just data or content that is in a compatible form to be used by the particular command and space ( ) immediately before the argument. The setprop argument is very similar to the /system/build.prop lines when viewed as text. The only difference is that setprop follows the format of getprop, using a space ( ) in place of the equals sign (=) that is likely more familiar to most and almost always what is found when researching build property lines online.

To convert a resourced build property line to a single setprop script line using the necessary command and argument is shown below:

Typical build property format found online:

qemu.hw.mainkeys=0

Format to be used for the setprop command/script:

#!/system/bin/sh (only once at the very top)

setprop qemu.hw.mainkeys 0

audio_policy

To maximize ViPER4Android processing, edits to /system/etc/audio_policy.conf, /system/etc/audio_output_policy.conf, or similar file(s) are often required. These files and the necessary edits vary from devices and entries so providing a one-size-fits-all script to achieve this is not currently available that meets our standards. Our solutuon to this is to tackle each file one at a time to personally prepare it ourselves and make it available to our users.

Inside our audio_policy Database is an audio_policy Submissions folder that is intended for the user to upload the necessary file(s) for us to examine, prepare, and make available for use when placed in the audio_policy Downloads folder. We ask for the following format to be provided when uploading your rom's stock audio_policy file(s) to the audio_policy Submissions folder:

/(Device name and OS)/(Correctly named).conf

Once uploaded to the audio_policy Submissions folder, the prepared audio_policy can be found in audio_policy Downloads once finished and downloaded for use with the sound system at any time. After verifying everything is working properly with the prepared audio_policy, keep this file safe and accessible on your device any time you need to place it in your /system following a rom install or update. The audio_policy Database is linked below.

Please remember: The audio_policy Submissions folder is for you to upload stock files. The audio_policy Downloads folder is for us to upload prepared files for you to download and use.

Downloads & Links

arisesound.com

Older Buildshttps://www.androidfilehost.com/?a=show&w=files&flid=59044https://www.androidfilehost.com/?a=show&w=files&flid=59044

A.R.I.S.E. Sound Systems™ Profiles & Convolvers

A.R.I.S.E. Sound Systems™ getprop Database

A.R.I.S.E. Sound Systems™ audio_policy Database

A.R.I.S.E. Sound Systems™ on G+

A.R.I.S.E. Sound Systems™ on Telegram

For now, please Private Message any team member with your Telegram profile name to gain access to the ARISE Sound Systems™ Telegram group.

Bug Reports Form

ViPER4Android Support:

A comprehensive collection of ViPER4Android information and support can be found at the ViPER|Audio™ series thread linked

here

.