SuperSU is required to run su.d scripts, if you didn't have it that was probably why the permissive script was not working.:good:
Thanks man that work.
Thank you for trying! :good:
I believe I missed your situation and progress, would you mind providing device and rom information along with a couple examples of what wasn't working or particular disappointments? :good:
Thank you mate
Just copy all the text in tweakprop you want.go to build.prop in system.paste the prop text you just copied at the very bottom.set permissions to rw-r-r and reboot.the tweak.prop misses a lot of entries.Imo its more reliable to manually copy the lines.as always BACKUP first.Help, I am new here
I am trying to flash tweak.prop zip but got the error: cannot get write access on /data, script aborted. I did enable permission on app, what did I miss?
I am using TWRP to flash
Did you manage to make Dolby Atmos work..??
In my case Dolby Atmos opens up til black screen+logo and ->"Unfortunately, Dolby Atmos has stopped" appears.
Couldn't find storage permission... The apps doesn't appears on the "permission manager"
Xiaomi redmi Note 2 Xiaomi.eu MIUI8 beta 6.7.14/15 v5.0.2
Only for Atmos I believe mate do really to get the full benefit of Leviticus I'd go with permissive yes.hi im on exodus with selinux enforcing, do i have to have selinux permissive to get Leviticus to work??
current using Nexus 5 + Chroma + Elemental X 6.19 + Exodus
Very easy. Copy all tweakprops you like to your internal storage--sdcard--and each time you want to swap, rename the last tweak.prop to something like tweak.prop.bak (if you just delete it, you'll have to empty the waste bin as it will be the 1st on the path of tweakprop.zip flash) and give next tweakprop the name tweak.prop and flash in recovery.How to shift between tweak.prop profiles?
I am noob and dirty flashing rom to achieve just that.
Much thanks for the clarification. Used to have it on previous installation but this time, clean flashed the updated rom and didn't pay attention prior to flashing Lev 1.1.:good:SuperSU is required to run su.d scripts, if you didn't have it that was probably why the permissive script was not working.:good:
You can try any version you choose from the afh folder mate but as they say the latest is the greatest lol, have you tried 1.1 with a different tweak prop?Just someone's opinion, but which ARISE version pays the most attention to details in the music heard?
I hope that's not too vague a question.
I'm wondering this because I used to be able to hear certain elements in songs a little more clearly before I flashed ARISE.
Using ARISE Leviticus 1.1 at the moment, with the GH TweakPROP.
Apart from that, ARISE is too awesome for my limited vocabulary to truly describe, heh heh.
@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_220.127.116.11= (4.5MB) install.v4a_18.104.22.168= (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. ##