yashsingh1/xdaforums huggingface dataset:
[Android Software Development] SSNJR2002:
Setprop v3.1 for alpha builds. Enjoy :good:
[Android Software Development] FinickyMan:
Give a try to 2-4 alpha 7. Just remove icepower_algo entry from audio_effects.conf in /etc/vendor before installing V4A driver (I myself use 2.3.4.0) and rebooting. For the setprops to process, if you don't have SuperSU, put them in /etc/init.d with 0755 permission. Hope that helps you to get the good sound level and effects I'm getting on cm14.1 custom rom. I don't use am3d and dolby acts weirdly (I flashed latest add-on and put arisesoundserver in init.d, worked for some time and stopped for no reason I'm trying to find out now)

edit: sorry, I meant system/vendor/etc/audio_effects.conf
[Android Software Development] U4mes:
Dear all

I am having driver install issue in my mobile (Honor 6 plus android M) as every time when i reboot its asking to install driver again and again . any help please :)
[Android Software Development] ecsnead69:
I'm using 2.3.3 on Shamu 7.0. I flash back to V4A 2.3.4.0. V4A works great but eventually stops processing? Anyone else have this issue and know of a fix? Rebooting fixes it but I'd like a real fix
[Android Software Development] hitesh1792:
Only deut..
[Android Software Development] dyval:
Can smeejaytee's toolbox be used along with Dolby Atmos? Thanks :good:
[Android Software Development] Alex Tian8800:
Yes,works well.
[Android Software Development] jitendra purohit:
Can someone send me best profile for latest deut?
[Android Software Development] abheeshdivakar:
Guys this mod is gona work with custom roms like RR or ASOP ?
[Android Software Development] bkayy:
Does it work with spotify seems not process in viper
[Android Software Development] anttaz:
It does on m8 on rr nougat build but supposed could also depend on rom or device
[Android Software Development] SupaKid:
Yessir!

Using ARISE Deuteronomy 2.3.3 Classic on my Samsung Galaxy Note 3, running 4.4.4 KitKat, W03 SlimKat.

ARISE is working perfectly.

Keep in mind, I'm on 4.4.4 KitKat.

It may be different for you on a later Android OS.
[Android Software Development] abheeshdivakar:
Okey. Gona try it
[Android Software Development] raylogic:
Bag of hard midget gems to anyone who can help me get Dolby Atmosphere working on my S5 SM-900F

- CM14.1

- Deut 2.3.3

- Boeffla Kernel 4.0

- Selinuxmodchanger (permissive)

3rd full wipe attempt and still no luck, closest I have got is the creation of the ax folders in system/priv-app. But no apk inside.

Bah :(
[Android Software Development] InterestingTwist:
SuperSU or CM's root?
[Android Software Development] JaylanPHNX:
Try manually deleting the driver (libv4a_fx_ics.so) in system/lib/soundfx, then reboot and try installing from app again.
[Android Software Development] zilan:
sorry, but how to use setprop? works for all devices? mine is redmi note 3 pro.. please explain more.. thanks

i've flashed it but it always force closed.. can you fix it?
[Android Software Development] zilan:
Screenshot attached
[Android Software Development] Kyuubi10:
Use search tool.

You are Senior Member, you should know by now to use search tool.
[Android Software Development] hammmersmashface:
Here is mine ...seems to be going over well
[Android Software Development] Impius:
Here's my favorite setup. It uses a convolver I found in some thread I can't recall. It's in the zip too.

https://www.dropbox.com/s/umuqxa7jwqhz4po/MyDefaultAndConvolver.zip?dl=0
[Android Software Development] docnok63:
First make a nandroid of your current build/data. Next, Wipe everything (boot/system/data.) Flash your ROM and GApps only. I have no idea how you're flashing SELinuxModeChanger in recovery as the official build is an apk only which should be sideloaded on first boot. You might have some bogus version. You should ONLY be using this APK. Once you're set up, Flash Deut 2.3.3 only and reboot (no need to wipe anything.) Verify Deut's driver status. If all good, flash the dax Atmos in recovery. You should be good to go.

---------------------------

For those in this thread that have been wondering where official builds have been...I can tell you 100% that no one has been sitting on their hands (can't code that way :p ) If you look at the last official stable released, 2.3.3, that just hit 32 days since release. 2.4 Alpha 7 was released a week ago. Since then we're into build 8.x (not my place to say exactly which one) with MANY sub builds in between (like Alpha 4-1, 4-2, and 6-8 and patched 6-6 posted.) I've lost count flashing, but it's been well over 15 builds this week. It's not been without growing pains. One dev had to relock his bootloader and RUU back to factory settings. A tester had to completely wipe his internal sdcard and start from scratch. However, the team is on the verge of something truly special. Not only are Ark and ICE fully functional, but MANY other effects (think Baskin Robbins size.) Will it ever be working enough for public release? Who knows. I certainly don't. I do know, however, how hard the ARISE dev team and the testers are working in the background (into ungodly hours) to bring you the best sound system on Android. Please be patient. If it all works out, something truly special is on the way. ARISE UP!!! :highfive:
[Android Software Development] raylogic:
Cm's root
[Android Software Development] InterestingTwist:
Use SuperSU as ARISE uses su.d scripts
[Android Software Development] docnok63:
2.2.3 Classic isn't patched because it uses sono's setprop and not arise_setprop so it didn't need to be patched. As I said when posting 6-8_patched, the patch was to fix GPS/compass/navigation problems only. It will NOT fix Viper not processing or Ark/ICE FCing issues. Please stick with a stable version if Alphas are not working for you. If you're still having GPS issues with 2.2.3 Classic, look into ROM issues or try 2.2.3_patched.

That being said, we've had more success with Alpha 6-6 working for more people. It doesn't need to be patched because it didn't have the same bug that 6-8 did. You can grab it here. Good luck! Let me know how it goes.
[Android Software Development] raylogic:
Thanks very much for your help but the APK link on pg1 of your link is not working. Everything you said to do however I have tried (twice now).

R.
[Android Software Development] docnok63:
Fixed link and reading your above post, PLEASE flash SuperSU 2.7.8
[Android Software Development] Essentrix:
Have you considered moving back to stock from boeffla? That would be the main difference to my setup.

---------- Post added at 08:26 AM ---------- Previous post was at 08:23 AM ----------

Quick note: He can't use SuperSU with 14.1. It will break things such as Wi-Fi. Has to use superuser that comes with the ROM.
[Android Software Development] docnok63:
If that's the case he, and you, can use systemless SR5: https://download.chainfire.eu/1014/SuperSU/SR5-SuperSU-v2.78-SR5-20161130091551.zip
[Android Software Development] arek78:
After installation ARISE+Sound+Systems+Numbers+3.5 which dolby atmos I install? because those stock no longer work.
[Android Software Development] docnok63:
I'm not sure what you mean by "those stock" because Dolby Atmos was stock to only a few devices and ported for the rest of devices by [MENTION=5357345]ahrion[/MENTION]. You should be using this one: https://www.androidfilehost.com/?w=files&flid=106151
[Android Software Development] arek78:
:oLetv x500 with dolby atmos and dirac stock.
[Android Software Development] docnok63:
So, you're saying the native Atmos and Dirac sound systems (I had to Google Dirac) both broke with your Numbers 3.5 installation? Since I also had to Google your phone, can you please list: Current ROM, current root method, current recovery, current driver status of Viper with music playing.

You can first try making a nandroid (if you have TWRP/CWMR?) of your current status and try to find Dolby Atmos' folder in either system/app or, more likely, in. system/priv-app. Atmos may have weird folder names like Ax and AxUI. Delete that folder(s), reboot into recovery, and flash the Numbers Atmos I linked above.
[Android Software Development] SSNJR2002:
Rename SSNJR2002_setprop to arisesound_setprop. Now go to /system/su.d and delete the default arisesound_setprop and paste mine there with permission set to 700.
[Android Software Development] docnok63:
Sorry folks. My bad. Upon double-checking, 2.4 Alpha 6-6 did need to be GPS/compass/navigation/rotation patched. I've uploaded the file below:

https://www.androidfilehost.com/?fid=457095661767120825
[Android Software Development] zilan:
hi i've installed dolby atmos but it keep crash and stop, why?

i have selinux permissive. and already deleted /vendor/etc for audio_effects.conf but nothing solved my problem.

if i want to uninstall how? i can't find uninstaller.

thank you
[Android Software Development] hjjiang:
this is also happening to me on my Axon 7 =/
[Android Software Development] :
It will only process when playing audio.
[Android Software Development] hjjiang:
yea... its not processing when i am streaming from soundcloud when i click play, both atmos and v4a are not processing. This works on my Nexus5 but not on my Axon 7
[Android Software Development] docnok63:
I have no idea who told you to delete the audio_effects.conf file, but that was completely wrong. It's a key file to make V4A/Atmos/AM3D work. I hope you backed it up otherwise you're going to have to dirty flash your ROM. If you can't find that file and still want to delete Atmos, you will need to do dirty flash anyway. I'm curious. What build of ARISE are you using and why were you using [MENTION=5357345]ahrion[/MENTION] 's installer instead of the ARISE one?

---------- Post added at 10:23 PM ---------- Previous post was at 10:23 PM ----------

What version of ARISE? What ROM?
[Android Software Development] hjjiang:
I am on ARISE Deuteronomy 2.3.3 on stock Axon 7 rom (rooted - bootloader unlocked), playing media files from poweramp and shuttle+ player works fine (both atmos and v4a works)

v4a is the one from the zip and i also flashed the atmos zip for Deuteronomy
[Android Software Development] docnok63:
A quick search of the thread tells me that you should be using an older version of SoundCloud (don't let the Play Store update it):

https://drive.google.com/file/d/0B5-KizalaN5CT2FjRFlmTjhEWlU/view?usp=drivesdk
[Android Software Development] hjjiang:
yea i tried that APK already =/
[Android Software Development] docnok63:
Post your system/vendor/etc/audio.effects.conf ....I'll see if I can help.
[Android Software Development] zilan:
I read Sono FAQ on page1 what if dolby atmos crashing and it says to delete that files.

Ok i dirty flash my rom now cm14.1 and flash dolby atmos add on for arise but app not showing..

Im using arise deuteronomy 2.3.3.
[Android Software Development] hjjiang:
Here is the audio_effects.conf
[Android Software Development] docnok63:
Are you using this? https://www.androidfilehost.com/?fid=312978532265371208

If so, you're the second person saying the app doesn't show after flashing. Do you see the Ax and AxUI folders in system/priv-app yet it doesn't show in the app drawer?

I've looked through the file and it doesn't have the section I was looking to remove. Sorry, but I'm stumped.
[Android Software Development] hjjiang:
darn! thanks for trying though, the section might be gone because i flashed

ARISE+Sound+Systems+Deuteronomy+2.3.3_patched.zip

??? i thought the patched version might have fixed the soundcloud issue but it didnt =(

so far i have flash in these 2 scenarios:

1:

ARISE+Sound+Systems+Deuteronomy+2.3.3.zip

Dolby+Atmos+Add-On+for+Deuteronomy.zip

2:

ARISE+Sound+Systems+Deuteronomy+2.3.3_patched.zip

Dolby+Atmos+Add-On+for+Deuteronomy.zip
[Android Software Development] zilan:
Yes im using that version..

No Ax and AxUI folder in system/priv-app and no app in drawer. What step im wrong?
[Android Software Development] docnok63:
The patched versions had nothing to do with SoundCloud and only fixed GPS/compass/navigation/rotation issues.

There's nothing you're doing wrong. Try this file in recovery: https://www.androidfilehost.com/?fid=313042859668276259
[Android Software Development] zilan:
I hv also already tried dax_lemax it show on app drawer but it always force closed everytime i opened it.
[Android Software Development] docnok63:
If the app already has permission to storage, all I can tell you is it won't work on your system.

You can try AM3D: https://www.androidfilehost.com/?fid=313042859668276260
[Android Software Development] Alex Tian8800:
You shouldn't have deleted your audio-effects.conf!

Or you want to delete dolby atmos,you must dirty flash your rom.
[Android Software Development] zilan:
I try this:

Is it same files from your AFH right?

Im sorry i just read sonophile FAQ on OP and it say to deleted that files. Btw i dirty flashed my rom and flashed dax lemax2 r1.0 app show in drawer but forced closed everytime i opened it. App has storage permission as well.. Selinux permissive.

---------- Post added at 06:31 AM ---------- Previous post was at 06:13 AM ----------

AM3D is same with dolby atmos? and will it works on any device? thanks for your help :)
[Android Software Development] zilan:
This after i flashed dax_lemax2, is the permission wrong? It still crash everytime opened it..
[Android Software Development] U4mes:
I have done that but it still not enable and status shows as abnormal :)
[Android Software Development] Alex Tian8800:
It seems,doesn't work with Android Nougat. Work perfectly on Marshmallow.
[Android Software Development] dingermtb:
Check a couple posts back. A few of us had same issue. Just extract Viper app from zip file and also install as user app so you'll have Viper in system/priv-app and in data. This worked for me.

Sent from Outside the 9 using my Zombiefied Exodus OnyX
[Android Software Development] Lucki_X:
These FCs are caused by using sonophilos's tweak.prop. I recommend to use guitardedhero's tweak.prop.

Sent from PLK-TL01H
[Android Software Development] mattyditfc:
If you are using sonophilos tweak prop open the file up in an editor and delete these lines. Reboot and sony music player should not FC anymore ?

ro.somc.dseehx.supported=true

ro.semc.dseehx.enable=1

persist.service.dseehx.enable=1
[Android Software Development] harpin14789:
Thanks for this post. ARISE has always worked perfectly for my Nexus 6, but since exodus .9.x.x series update everything seems to be breaking. Ironically compatibility updates are breaking compatibility. Exodus.8.9 seems to be the best version that works with the N6 with perfect sound. On the Nexus 6, your tweak.prop causes no issues whatsoever on .8.9. looking forward to an Exodus 1.x series where Dolby can be enabled.

Cheers! Congrats on being added to the ARISE team.
[Android Software Development] dark_knight_95:
How do I do that just install as normal apk?I have tried install it as normal apk but no viper folder in android/data

Now there is a folder in data data/app.but it did not help
[Android Software Development] DingoDingo:
Seems guitardedhero is very busy with writing new book ☺️
[Android Software Development] aki_007:
Don't do that as there has been some major changes since .

Try to clean install rom and then install the apps , supersu , gapps etc , set your system and take nandroid backup of that , then flash the desired version as the backup will serve you best whenever you need to install ARISE on a clean installed rom .
[Android Software Development] yung40oz84:
A couple things I just wanted to mention that I notice on 0.9.3 with this tweak.prop is that I DO enable the mic props having the nexus 6P with dual mics and I no longer have people complaining about an echo when talking to them, which is great, so they are working where they should be working. Also, I set the dolby to on and is working fine although the aux I cannot test because I have bluetooth headphones and car stereo. The sound as a whole sounds great to me. Also, the 64 bit offload prop I enabled because nexus 6P )Angler) is arm64 and that has been fine. Great work with the tweak.prop, using it now :good:
[Android Software Development] aki_007:
I really don't know what exactly caused it but I had such issues sometimes since the E.I.A. was released .

I fixed it by doing some edits .

If you can edit audio_effects.conf then just make changes to system/vendor/audio_effects.conf

like this (look for the red coloured codes )

# ARISE Sound Systems™ audio_effects
#
# Prepared by guitardedhero [MENTION=243864]xda[/MENTION]
#
# Auditory Research in Sound Enhancement™
#
# List of effect libraries to load. Each library element must contain a "path" element
# giving the full path of the library .so file.
# libraries {
# <lib name> {
# path <lib path>
# }
# }
libraries {
bundle {
path /system/lib/soundfx/libsrs.so
}.......
[COLOR="Red"]v4a_fx {
path /system/lib/soundfx/libv4a_fx_ics.so
}[/COLOR]
harman_kardon {
path /system/lib/soundfx/libharmancorehtc.so
}
dirac {
path /system/lib/soundfx/libdirac.so
}
}

# Default pre-processing library. Add to audio_effect.conf "libraries" section if
........
....
# ...
# }

effects {
compression {
library cm
uuid f27317f4-c984-4de6-9a90-545759495bf2
}....
.......
......
}
[COLOR="Red"]v4a_standard_fx {
library v4a_fx
uuid 41d3c987-e6cf-11e3-a88a-11aba5d5c51b
}[/COLOR]
dirac {
library dirac
uuid 4c6383e0-ff7d-11e0-b6d8-0002a5d5c51b
}
}

global_processing*{*...
....
}**

change it to :

# ARISE Sound Systems™ audio_effects
#
# Prepared by guitardedhero [MENTION=243864]xda[/MENTION]
#
# Auditory Research in Sound Enhancement™
#
# List of effect libraries to load. Each library element must contain a "path" element
# giving the full path of the library .so file.
# libraries {
# <lib name> {
# path <lib path>
# }
# }
libraries {[COLOR="red"]
v4a_fx {
path /system/lib/soundfx/libv4a_fx_ics.so
}[/COLOR]
bundle {
path /system/lib/soundfx/libsrs.so
}.......
harman_kardon {
path /system/lib/soundfx/libharmancorehtc.so
}
dirac {
path /system/lib/soundfx/libdirac.so
}
}

# Default pre-processing library. Add to audio_effect.conf "libraries" section if
........
....
# ...
# }

effects {[COLOR="red"]
v4a_standard_fx {
library v4a_fx
uuid 41d3c987-e6cf-11e3-a88a-11aba5d5c51b
}[/COLOR]
compression {
library cm
uuid f27317f4-c984-4de6-9a90-545759495bf2
}....
.......
......
}
dirac {
library dirac
uuid 4c6383e0-ff7d-11e0-b6d8-0002a5d5c51b
}
}

global_processing*{*...
....
}*

and after editing copy that file to system/etc also .
Tell me if it still doesn't work
[Android Software Development] razrlover:
Just a quick shot out!

Left N6 and now on Tmobile version of HTC10.

Unlocked rooted and running arise.exodus 0.90.

Direct comparison stk with custom kernel or arise no contest. Much clearer and recognizeable sound.

Louder too, just by enabling before doing any custom configuration.

Thanks my dude
[Android Software Development] :
I have had those props in place since ViPERAudio SBE, which did have the DSEE libs working. I wasn't aware they were removed / nonworking since, but I'm seeing now it's possible that having those props in without the libs might be causing issues for Xperia users / with Sony Music Player where it wasn't causing issues for me.

[MENTION=4445176]guitardedhero[/MENTION] please confirm which sony_effects are still in use and I'll edit and upload a new tweak.prop to reflect that.

---------- Post added at 02:30 PM ---------- Previous post was at 02:30 PM ----------

---------- Post added at 02:32 PM ---------- Previous post was at 02:30 PM ----------

[/COLOR]

Try removing the lines with 'dsee' in them from build.prop and rebooting. I'll upload a new tweak.prop with those lines removed/commented out once I confirm that fixes the Sony Music Player FC issue, and (if) DSEE is no longer in use in Exodus 0.8.9.
[Android Software Development] desirexel:
Thanks..
[Android Software Development] 5ud0:
Guys,what's the version now with best audio output!?
[Android Software Development] :
Thank you for bringing this to my attention and sharing this with the users having issues. Once I get a couple confirmations this fixes the issue, I'll remove or comment out those lines from my tweak.prop and upload an update. I'd like to tackle all the Sony Edition props at once so I'm waiting on word from goodheartedhero as well. :good:

I want to add that users having this issue will have to remove these lines from build.prop manually and reboot - removing them from just tweak.prop won't remove them from build.prop even if you flash tweakprop.zip, it just "won't add them". You could set them to =false, =0 and =0 in tweak.prop, reflash tweakprop.zip and reboot, but that just disables them, it doesn't remove them.

--

0.8.9, in my opinion. Check OP2 for a link to my preferred version and the Kit I've used to hone and improve my sound. I think you'll like it if you can get it set up. :D
[Android Software Development] arcticnights:
What's OP2? :p
[Android Software Development] :
The second post, after OP. :p
[Android Software Development] JJEgan:
For me its still Genesis 1.2 .

Exodus no better .
[Android Software Development] necktru:
Just read the OP, any version is ok.

First be sure you don't have boomsound

[MENTION=5079472]sonophilos[/MENTION] [MENTION=4445176]guitardedhero[/MENTION] You must consider add a warning in OP that ARISE doesn't work with boomsound in htc phones.

Regards
[Android Software Development] :
Hi necktru,

I have the HTC One M9 on a Sense ROM with Boomsound and it's had no issues with ViPER or ARISE. Can you describe the issue you're having? The specific device/ROM you're using?
[Android Software Development] zilan:
Yes im on Nougat 7.1 CM14.1, okay i will wait an update till it works for N. thanks
[Android Software Development] docnok63:
That's completely inaccurate. See screenshots below.

Yes, just like Atmos....AM3D is supposed to be universal. Clean flash your ROM to clean up Atmos and give it a try. Good luck!

I think you can see some of the problems the devs have and making this mod universal. Over the last two pages, I've unsuccessfully tried to get Atmos working for you and V4A processing while streaming SoundCloud for [MENTION=4404831]hjjiang[/MENTION] . This is just two cases on two devices. Imagine the daunting task faced by [MENTION=4445176]guitardedhero[/MENTION] trying to make the mod work for all of people all of the time. Honestly, I think it's an impossible task. There's too many variables. But he's a perfectionist and works an insane amount of hours towards that goal.
[Android Software Development] Alex Tian8800:
Dolby Atmos works on CM 14.1 mine. Try to find,why it isn't working for U.
[Android Software Development] Inceptic:
Any chance to working Dolby atmos on lp?
[Android Software Development] JaylanPHNX:
No, it needs marshmallow or above.
[Android Software Development] FinickyMan:
Dolby Atmos R6.5: http://xdaforums.com/android/apps-games/mod-dolby-atmos-t3109446
[Android Software Development] ModelCitizen:
Any word on the compatibility issue with Pixels?
[Android Software Development] InterestingTwist:
Don't spread false information, it works perfectly fine on Nougat.
[Android Software Development] Alex Tian8800:
Yes,works perfectly on Nougat. I've already written about this. But it needs Supersu for work.
[Android Software Development] bbender716:
Hey man howd you get it working on Pixel? I flashed the Pixel zip but I always get "error 1" unable to update...
[Android Software Development] imarq24:
Where do I delete that at?
[Android Software Development] noonebhargav:
Works on android 7.0 right?(i am using a AOSP Rom)
[Android Software Development] mohand06:
Deut.2-4 alpha7 on cm14.1. Just found out that icepower_algo in vendor/etc/audio_effects.conf kept from processing both V4A and Dolby Atmos. Once deleted this entry, everything back on track.

Now listening to Discover Reverbnation with full effects of V4A irs and Dolby rich - just testing, don't really need all the effects applied at same time, somewhat overprocessing on earphones.
[Android Software Development] docnok63:
There's a Pixel only ARISE build in development to account for the new 7.1.1 file system. It'll be released when ready. The Error 1 problem is fixed.
[Android Software Development] bbender716:
Fantastic. I'm in the telegram thread ready to test whenever.