ARISE, doesn't require permissive kernel, it is the atmos app that requiers it.Are there any ARISE versions that work on android Nougat with enforcing kernel?
Sent from my SM-G900P using XDA-Developers mobile app
ARISE, doesn't require permissive kernel, it is the atmos app that requiers it.Are there any ARISE versions that work on android Nougat with enforcing kernel?
So paste the individual profile folders in the master viper profile folder, the kernel contents in he kernel folder and what about the DDC folder contents, where do I place those?
So paste the individual profile folders in the master viper profile folder, the kernel contents in he kernel folder and what about the DDC folder contents, where do I place those?
Sent from my SM-N930f using Tapatalk
Stable: Deuteronomy™ 1.51
Stable: Numbers™ 3.5
Stable: Leviticus™ 1.3
Stable: Exodus™
May I ask what Pulse is?Yes, latest setprop will work with previous (one or two builds of) Deuteronomy, don't go further back than that. I'd hold out for the fixed Pulse build, though; I'll have a new setprop release to coincide with it. :good:
May I ask what Pulse is?
Thank you! Here I was thinking that I'm missing something from the extras folder.It's a graphic equalizer located at the bottom of the screen, it moves along whith music when played. Some ROMs have it, some don't.
@guitardedhero, could you or someone else on the team describe the differences between the following modules?
Look at navigation bar.....May I ask what Pulse is?
@guitardedhero any thoughts on this one?Flashed Deuteronomy 1.51 on my n6p running s-aosp 09/24 build, ex kernel, systemless root. I can't play any songs, but YouTube and y music is working, though the sound is not processed (haven't tested others out there). Driver status abnormal. Logcat from trying to play a song attached. Cheers
Any trick to get AM3D working?
Opens up but has a white screen only. I'm on deut 1.51. Thanks
Im confused lol. Are people having trouble with deut 1.6 or is it ok to flash?
Updated my op section with my latest toolbox for Deuteronomy enjoy!!!
Sent from my HTC One M8 using Tapatalk
Whats the difference between feel v3 and deut v1 profile?Updated my op section with my latest toolbox for Deuteronomy enjoy!!!
Updated my op section with my latest toolbox for Deuteronomy enjoy!!!
Sent from my HTC One M8 using Tapatalk
Anybody here using a S4 mini? Which version of arise would you recommend? Currently I'm on numbers 3.5
Works in Enforcing Kernel?DEFINITELY recommend the latest Deuteronomy. Should work on all devices, although, depending on your ROM, pulse seems to break on some devices. But latest Deut is ground breaking and earth shaking. Also...nice to see ya here bro?
A.R.I.S.E. with my Zombiefied Moto Z Force
@guitardedhero. Thank you Soo muvh for ARISE. YOU hrlped so many people to get great audio on the phones.We thank you for your continued interest and encourage you to reach out to us if there is anything with which we can assist you. :good:
# ARISE Sound Systems™ 20170424
#
# Magnum Opus
#
# /sdcard/arise_customize.prop
#
# www.arisesound.com
## !! This archive contains 300MB of data.
## !! Navigate to /system to ensure
## !! sufficient space is available in
## !! /system before flashing.
# Module description and information can be found in META-INF/getting_started/modules.
# The ARISE™ modular installation zip works by using this file (when present in /sdcard as /sdcard/arise_customize.prop) to determine if any modules are to be installed by a value of "true" for each line below.
# Any value other than "true" is the same as a value of "false".
# Add a value of "true" to desired add-on(s). Example:
install.xxxx=true
# The Core System module must be installed at least once and only once. Once the core module is installed, the value of "true" should be removed for future customization installing, uninstalling, or executing scripts and modules.
# If a rom update or system wipe is performed resulting in the need to reinstall the sound system, edit /sdcard/arise_customize.prop to include a value of "true" for the core module to complete your sound system installation, followed by removing the value of "true" from the core module once booted.
## START ##
install.core=
(40MB-175MB)
# Select either ViPER4Arise™ version below to be installed or ignore to not install ViPER4Arise™ at all.
install.v4a_2.5.0.5=
(4.5MB)
install.v4a_2.3.4.0=
(6.5MB)
# Add a value of "true" to any modules below to install.
install.v4a_profiles=
install.ddplus=
(15.3MB)
install.atmos=
(3.3MB)
install.am3d=
(3.5MB)
install.arkamys=
(170KB)
install.sony=
(70MB)
install.v4a_xhifi=
(700KB)
install.esira=
(3.6MB)
install.musicfx=
(200KB)
install.dirac=
(4.2MB)
delete.deep_buffer=
restore.deep_buffer=
repair.sdcard.permissions=
#
## Qualcomm™ Audio Effects Configuration START ##
# Qualcomm™ devices have the ability to select from four audio effects configurations using Android O (default), Asus, DAP (native Dolby Atmos), Huawei, Sony, or Stock /soundfx libraries.
# IMPORTANT!!
# If installing an audio effects configuration on a currently installed sound system, BE SURE TO INSTALL THE CURRENTLY INSTALLED MODULES AGAIN USING THE APPROPRIATE VALUES!!
# Installing Core is not necessary, but any other module IS NECESSARY so that those modules' entries are written to the new audio effects configuration!!
# As a reminder, any preferred or custom audio effects configuration can always be automatically installed during the Core System module installation by placing it directly in /sdcard named arise_effects.conf to result with /sdcard/arise_effects.conf.
ANDROID_O
ASUS
DAP
HUAWEI
SONY
STOCK
Example: install.qc.ef**cts=ANDROID_O
install.qc.effects=
## Qualcomm™ Audio Effects Configuration END ##
#
## ICEsound™ START ##
# Add a value of "true" to install the ICEsound™ module:
install.ICEsound=
(750KB)
# The following ICEsound™ configurations are available below. a value of "None" will remove an existing ICEsound™ configuration to use no ICEsound™ configuration. Values 1 (default), through 6 select the ICEsound™ configuration of the same number.
# Although, the available ICEsound™ configurations can have a substantial impact on sound quality, the different versions are provided to find the configuration most compatible with the rest of the installation with incredible sound quality.
# Because of the unpredictability of this file's impact on audio and functionality, descriptive names for the different ICEsound™ configurations are not logical and are simply numbered as they are Example:
use.ICEco**ig=1
1
2
3
4
5
6
None
use.ICEconfig=
# The following ICEsound™ presets are available below. A value of "None" will remove an existing preset to use no ICEsound™ preset. Enter a value of the preset name exactly as shown below. Example:
use.ICEsound.pr**et=01
BATHSALTS =01
DEEPBASS =02
HOLYSH*T =03
KRAZY =04
MOVIE =05
MUSIC2 =06
OUTDOORS =07
PURE (default) =08
PURESH*T =09
SHAT =10
WIDECLARITY =11
Default (pure) =12
None =None
use.ICEsound.preset=
## ICEsound™ END ##
# The ARISE™ modular installation zip works by using this file (when present in /sdcard as /sdcard/arise_customize.prop) to determine if any modules are to be UNINSTALLED by the value of "true" for each line below.
# Any value other than "true" is the same as a value of "false".
UNINSTALL.v4a=
UNINSTALL.atmos=
UNINSTALL.ddplus=
UNINSTALL.arkamys=
UNINSTALL.ICEsound=
UNINSTALL.am3d=
UNINSTALL.sony=
UNINSTALL.esira=
UNINSTALL.v4a_xhifi=
UNINSTALL.musicfx=
UNINSTALL.dirac=
## END ##
su
su -c dumpsys media.audio_flinger
su
dumpsys media.audio_flinger
[B]## Magnum Opus™ 20170506[/B] -
- More booted script corrections/enhancements.
- Enhanced the $SDCARD variable during recovery.
- Android O LDAC Bluetooth™ codec reassigned
as a satisfied scenario component.
- Experimental build with arisesound_setprop
disabled, enabling requires name change from
arisesound_disabled_setprop to arisesound_setprop.
##
/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
getprop