yashsingh1/xdaforums huggingface dataset:
[Android Software Development] BadBoy2K7:
I'm not sure where to begin with the problem I'm having I want to enable LDAC codec for my Sony MDR-100ABN with my Nexus 6P. Is it possible to do this or am I on the wrong thread for this type of question?

Ressurection Remix 5.8.3 date 051217

Magnum Opus 050617

install.core=true

install.v4a_2.5.0.5=true

install.v4a_profiles=true

install.atmos=true

install.sony=true

install.dirac=true

delete.deep_buffer=true

repair.sdcard.permissions=true

install.qc.effects=SONY

install.ICEsound=true

use.ICEconfig=1

use.ICEsound.preset=08

I flashed the aptx codecs prior to dirty flashing since the latest ROM and looks like the files are still in the lib folder and is processing fine with aptx, I also noticed a ldac lib file in the that folder but not sure if I need to flash certain files for ldac to work.

I'm a little puzzled what exactly happens when setting a specific install.qc.effects option I have only tried SONY with my current build and prior I have tried ANDROID_O and DAP. Also I may have no clue what I'm doing but I try! :victory:
[Android Software Development] mrrocketdog:
if ICE is installed , try #2. or delete alltogether. or could try deep buffer removal.

---------- Post added at 12:34 PM ---------- Previous post was at 12:31 PM ----------

could try disable/freezing any stock sound mod/tweak. or change from enforcing to permissive or vice-versa.

might try switching roms. or , can try deleting libv4a_fx_ics.so from lib/soundfx/deuteronomy. re-open V4a and should get prompt to re-install drivers.:high:

---------- Post added at 12:41 PM ---------- Previous post was at 12:34 PM ----------

oh ... wait ; gh is typing. will be back in 15.:high5:
[Android Software Development] guitardedhero:
The LDAC Bluetooth codec included in the Core module is from the new Android O Preview which provides an AOSP LDAC solution where previously Xperia devices had enjoyed an exclusivity of Sony's higher resolution Bluetooth wireless technology. Unfortunately, not having a device with an official Android O Preview factory image makes this feature nearly impossible to test properly (unless it works, of course, lol) and will still require the LDAC hardware in the Bluetooth receiver (I do have this capability, at least).

I'm hoping we find out as well as experience more of what Android O has to offer with the second preview that will land for those devices. As of now, you are on the forefront of this new Android O feature by having all necessary components, including the mandatory factory image introducing the LDAC codec to your device for the first time.

If I were in your scenario and with a determination of experiencing AOSP's LDAC, I would be testing with only the Android O Preview factory image installed. At that point, see what it will survive mod-wise lol. :good:
[Android Software Development] davidisflash:
I've been using the AROMA 2.94 Deuteronomy installer with no problem up until the April 7.1.2 update on my pixel and ever since then. From then on on any Rom including may updated ones, the installer breaks android auto, I get random reboots, and no system sound from the speakers (alarm, phone calls).

I looked for a new AROMA for Magnus and don't see it. I tried manually installing the latest zip in twrp and got the same error code message others got relating to the prop file, even when copying it to /sdcard directly.

Can someone help? Also, is it expected that Deuteronomy isn't fully compatible with newer Android nougat?
[Android Software Development] chikimonke:
You said you copied the prop to the sdcard, but did you edit it? You need to open it and read it and put the appropriate values for the effects that you want to install.

Edit: Also, Aroma is no longer supported.
[Android Software Development] davidisflash:
Didn't edit it. Thanks. So what fields are minimally required to be edited to get the installer to work? All I do is tweak eq in v4a. Never load profiles
[Android Software Development] chikimonke:
The bare minimum is core and choosing which v4a version you want. I personally go with the 2.5.0.5 version. I have attached my prop for you to look at. I install a few more things, but keep it pretty minimal. Had to rename the prop to txt to get it to upload.http://cloud.tapatalk.com/s/5917587fe8276/arise_customize.txt
[Android Software Development] weazie:
Put 'true' (without the apostrophes) next to

install.core=

and

install.v4a_2.5.0.5=

or

install.v4a_2.3.4.0=

Depending on which one you prefer.

Core is required for the modules to work.
[Android Software Development] jugoslavpetrovic:
Have you tried twrp app from store?
[Android Software Development] custommsp:
Hello. I'm using the LG V20 and am having SQ issues (I believe) over bluetooth in my 2016 Ford where the playback sounds like a low bitrate mp3 even while playing flac music. I've tried the various audio_effects from the list in the arise_config. file, but none seem to make a difference. I did notice that you have listed the Oppo R9S with some difference BT codecs in the OP, but I don't see that as an option in the arise_config? Is it a valid current option and would that possibly make a difference in BT playback quality?

Thanks!
[Android Software Development] gokart2:
Thank you for the time you took to give details on this, it's much appreciated. Always wondered about the effect table values and how it worked!

In the past I had taken/used build.prop commands to force xloud, clearphase, etc to be on system wide by:

ro.semc.xloud.supported=true
persist.service.xloud.enable=true
com.sonyericsson.xloud_enabled=true
ro.semc.xloud.default_setting=true

ETC....

After noticing the setprops weren't being applied after renaming the the folder to arisesound_setprop, I took the setprops from that folder and the sony_setprop ones, combined them, and copied the folder to /system/su.d. After a reboot it stuck from that point.

I then installed the sony module, and removed all the apks, leaving all the libs/etc.

On top of the arise/sony setprops from the earlier combination, I installed:

mpq.audio.decode=true
sony.support.effect=0x1FF
ro.semc.sound_effects_enabled=true
ro.semc.xloud.supported=true
persist.service.xloud.enable=1
ro.semc.enhance.supported=true
persist.service.enhance.enable=1
ro.semc.clearaudio.supported=true
persist.service.clearaudio.enable=1
ro.sony.walkman.logger=1
persist.service.walkman.enable=1
ro.semc.clearphase.supported=true
persist.service.clearphase.enable=1
persist.service.enhance.enable=1
ro.somc.sforce.supported=true
persist.service.sforce.enable=1
persist.service.dseehx.enable=1
com.sonymobile.dseehx_enabled=true
com.sonyericsson.xloud_enabled=true
ro.semc.xloud.default_setting=true
com.sonymobile.clearphase_enabled=true
ro.semc.cp.default_setting=true
com.sonymobile.sforce_enabled=true
ro.semc.sfs.default_setting=true

But in the setprop form.

After that I noticed quite a difference in sound.

Now, is there any conflict of doing this with the sony_setprops you have?

As for:

"Anything in /system/etc/init.d without init.d support will only execute if targeted specifically by the /system/su.d script if its permissions (0775) and shebang header (#!/system/bin/sh) are appropriate"

I checked it over multiple times and all looks well. Wondering if it's because of the SU version I have is kinda old, v2.62 i think....? Will eventually wipe and try again. But for now the su.d setprop folder is working.

Do you know of a way to find a setprop's location? There's a certain prop being executed in the off position and I want to test it on. I have a setprop in the same folders as the sony ones, and everything gets properly executed but that particular one. So there's something forcing it off? I have tried a bunch of shell cmd's but nothing has worked.

EDIT: Are there any setprops to force ArkymsAudio effect on without the APK?

Again, thanks for your time, knowledge, and work.

[MENTION=5511100]mrrocketdog[/MENTION] Thanks for getting Len pointed in my direction!
[Android Software Development] davidisflash:
It worked! Thanks again, you rock!
[Android Software Development] mrrocketdog:
[MENTION=4445176]guitardedhero[/MENTION] , hmmm .... did i forget to mention that i'm tone-deaf. :banghead: jk.

rofflmao.:highhero:

---------- Post added at 03:24 PM ---------- Previous post was at 03:23 PM ----------

[MENTION=4267845]gokart2[/MENTION] , ty for more info and really good q's.:cowboy:
[Android Software Development] maxxx83:
[MENTION=4445176]guitardedhero[/MENTION] what do you think what combination i install for Xperia Z2 Existenz rom based on stock 6.0.1?I install same,latest magnum opus only V4A,profiles,ice sound with config 2 and pure preset as on RR 7.1.2 but sound is much lower.
[Android Software Development] edrickmph:
[MENTION=4445176]guitardedhero[/MENTION], Any updated solution on this problem? There are i think other latest xda forumers reporting same issues. Processing=YES does not stick. Hope this issue can be resolved soon.
[Android Software Development] guitardedhero:
Provide as many relevant details describing this particular problem and I'll provide the insight I have. :good:
[Android Software Development] edrickmph:
https://plus.google.com/104899990711043580528/posts/VVNJH4MLG32
[Android Software Development] Logan:
[MENTION=4445176]guitardedhero[/MENTION] seems assisting needs alot of work xD god bless you, have you checked the audio_effecf.config of RR? I uploaded the required one couple of pages ago still curious how visualization breaks am4d. xD

Keep it up :)

(Tho disabling v4a clarity reduced most of cracking sounds or the static sounds in vocals dolby atmos seems to increase it to the limit)
[Android Software Development] guitardedhero:
Have you tried build 20170506?
[Android Software Development] edrickmph:
Yes.
[Android Software Development] maxxx83:
Not the most exciting answer, but cases where satisfaction has yet to be met with multiple modules, I recommend to uninstall a module - or even revert a change in one like that of ICEsound, for example, and focus on the impact this change or uninstallation has on the audio quality.

Modules are intended to enhance the sound, the capability, or just the overall atmosphere. When modules detract from one or more of those three, it can be quite frustrating.

However, don't let that persuade you not to experiment, experimentation is crucial to get the most of all that we offer. I know it can be overwhelming, but have confidence knowing the more time it takes you, the more valuable your experimentation becomes. :good:

[MENTION=4445176]guitardedhero[/MENTION] Thanks for your answer.I will try combinations and see how it goes.Do i need to disable sony's music fx or no?
[Android Software Development] edrickmph:
As seen from the Google+ post, I have already tried all suggestions from [MENTION=5866088]Paschfire[/MENTION], but still processing=YES does not stick.[emoji17]
[Android Software Development] guitardedhero:
Ah, yes, indeed, I did see it and was quite perplexed to see your rom's visualizer collapse without any interference! My next move in that scenario would be to test a different build of that rom or a different rom altogether to isolate the rom or the ARISE installation you're receiving. :good:
[Android Software Development] edrickmph:
What do you mean with roms visualizer without interference? So I need to test it myself? A new build of my rom will be coming for about 2 hours from now.
[Android Software Development] guitardedhero:
When you say previous build, is that describing rom or ARISE build?

No, leave MusicFX enabled, if possible. :good:
[Android Software Development] edrickmph:
Just to note again: I think this is not an isolated case. There are other people here reporting the same issue.
[Android Software Development] jcmm11:
[MENTION=4445176]guitardedhero[/MENTION] [MENTION=4267845]gokart2[/MENTION]

Actually persist properties can be modified by setprop. The difference between a persist prop (which always starts with the word persist) and a"regular" prop is that you don't have to reset it after every boot. It persists through reboots. Every persist prop has a file (text format, which contains the current value) in /data/property. You can edit that file to change the value, delete the file to completely remove the prop, or issue a setprop to change it (at least for ones I double checked before writing this).

Props which can't be changed are usually defined in build.prop. Those seem to be immutable, unless you go and change the build.prop entry.
[Android Software Development] guitardedhero:
By collapsing without interference, I was explaining that the visualization library and that library's configuration in audio_effects.conf was left entirely intact during the installation of ARISE and nothing was added or removed that might affect it and its function.

If this is a common scenario for multiple users of one rom, especially, one rom build, I'd focus on the rom build creating the issue. :good:
[Android Software Development] gokart2:
I can't find that specific property anywhere. Not in build.prop, su.d files, data/property files, etc.... Tried a bunch of rm -f cmd's to see if one would take. Then setprop'd the property to "on" and setprop'd a persist "on". Nothing works except a simple terminal setprop "on" cmd.

So, after a terminal setprop cmd, does the property change actually initiate after the cmd, or is a reboot required? Can't tell if it changed anything on the fly, and if a reboot is required....I have more work to do. LOL

Thanks for all your input! It's amazing how much one can learn by themselves using this site/users. I walked myself through kernel compiling and modifying, among other other things. Been learning a lot in this forum lately.:good:
[Android Software Development] edrickmph:
It's not just my rom, it's from different type of roms
[Android Software Development] guitardedhero:
Setprop has been unable to change the value he desires and setprop is only useful if the build property is wanting to utilized. His description most strongly indicated a persistent build property that could only be changed if deleted first.

Keep in mind, I'm proven wrong nearly on a daily basis, which I rather enjoy lol. :good:

---------- Post added at 05:40 PM ---------- Previous post was at 05:38 PM ----------

Did you perform the most important and first step of identifying the build property line? Without a single word of it provided, I simply have no clue what you're targeting. :good:
[Android Software Development] gokart2:
I double checked build.prop one more time and it's not there. It wasn't in the data/property file before. But after issuing the setprop persist cmd it is there. But it didn't force "on" after a reboot which is weird. I also can't open the file for some reason to verify the cmd output. So.....I'm assuming it's an apk command/reading. If it isn't on by the apk's command, or isn't an available feature then it outputs the state as off. That's my only thought at this point.
[Android Software Development] guitardedhero:
My best effort using the extreme minimum of information available is to attribute this issue with a script malfunction. This can be tested by the following in terminal:

getenforce

(I expect the output is "Enforcing")

su
setenforce 0
getenforce

(The output we seek here is "Permissive")

Exit v4a through the app, swipe v4a from recents, and open v4a to test for restored functionality. :good:
[Android Software Development] gokart2:
It's not in my build.prop, or anywhere it "should" be.

dolby.ds.virt.bluetooth off
[Android Software Development] guitardedhero:
/system/build.prop holds a fraction of the total build properties at any given time.

So, the output of getprop includes:

[dolby.ds.virt.bluetooth]: [off]

?

And what exactly is your goal regarding this build property?

This particular build property is among a large (imo) set of Dolby build properties. Do those exist as well?

Just trying to get some insight. :good:
[Android Software Development] tcat007:
I went back to Deut. 3.0.9 and feel the sound is cleaner on my 6p. Going to stick there.
[Android Software Development] gokart2:
Yes:

[dolby.ds.virt.bluetooth]: [off]

Looking to see if this has any Bluetooth improvement. Have a Chrysler 200s w/Alpine Audio, sounds really good IMO. Has surround sound and the sound staging is pretty kick-ass. Bassnector "Music is the drug" is bomb.

There are a few, haven't really checked. I flashed Ahrions dax_lepro3 v2.4 after all of your guys stuff. I have DAP QC effect and Ahrion"s ATMOS. So something in there? I looked and didn't find much.

:good::laugh:

---------- Post added at 07:36 PM ---------- Previous post was at 07:32 PM ----------

Was rocking 2.3.3 for awhile. Might jump back and try it with some of the improvements I've learned recently. (wasn't rocking current Sony setup).
[Android Software Development] guitardedhero:
That property is very likely from ahrion's /system/etc/dolby/dax-default.xml, which easily explains its seemingly inability to modify: Your desired setting with which to test will require making the appropriate edit in that XML. The file performs various operations such as setprop which is why your attempts have been ineffective. :good:
[Android Software Development] edrickmph:
[emoji17]
[Android Software Development] gokart2:
I dabbled through that a bit before, and just now. I hate xml. Searched for the property, and other similar search words and got nowhere. Not sure exactly how it's all compiled to output that property's state? Again, I hate xml. I'll keep at it.
[Android Software Development] guitardedhero:
Don't feel down, I see progress!

Is that PowerAmp controlling audio playback in the background? If so, dig into its audio settings and disable everything related to Direct Volume Control. :good:

Lol, I was worried you might venture that far. That's why my information for you abruptly stopped at that point lol! :good:
[Android Software Development] edrickmph:
It has been disabled since day 1.
[Android Software Development] guitardedhero:
Srandard or Alpha PowerAmp build?
[Android Software Development] edrickmph:
Alpha
[Android Software Development] jcmm11:
Ok. That prop doesn't exist for me. I'm guessing it's part of Dolby+, since I do have Atmos installed. Maybe I'll install plus and see if I can track it down.
[Android Software Development] gimpy1:
I have v4arise installed and working?. My modules installed are:

1. 2.5.05

2. Dolby Atmos

3. Ice #1

4. Module #10

Apparently I have profiles installed, although the profile module no longer has true written in. There are twenty or so profiles installed including one that I did.

My question about the profiles is: is there a way to determine what profile you are currently playing by just looking at the list? Can a "bullet" or something be put next to the active profile?

My second question has to do with the ice configuration. How can I tell that it is actually working? Dolly Atmos does have an icon that can be adjusted, heard and seen. Is Ice that type of program?

Thx
[Android Software Development] guitardedhero:
The Alpha PowerAmp builds have multiple Direct Volume Control settings throughout, covering nearly every audio output. :good:

Those particular props are generated from the Dolby XML configuration file. :good:

Yes, ViPER4Android will likely never see the day at least something minor would not add so much lol!

The ICEsound configuration is, at best, very unscientific lol. It's sole purpose is to foster harmonious processing of ICEsound and other audio effects. Satisfactory results can be confirmed during audio playback using the dumpsys utility to monitor the construction of effects-chains of ICEsound and other effects using a combination of an apk and a sound effect library such as v4a, AM3D, Dirac, Dolby Atmos/Digital Plus, Arkamys, etc... :good:
[Android Software Development] gokart2:
Hmmm, I have ATMOS.

Is it possible it could be from the QC DAP effect or one of it's files?

Might do a getprop with and without either mod and see when it gets pushed.
[Android Software Development] edrickmph:
I am using Google play music. Same.[emoji17]
[Android Software Development] edrickmph:
I think the problem is with v4a already.[emoji21]
[Android Software Development] guitardedhero:
What modules are installed other than Core and v4a?

There is always the option of disabling stock audio effects like AudioFX or MusicFX as well as trying the deep_buffer removal in /sdcard/arise_customize.prop. :good:
[Android Software Development] edrickmph:
Esira and Dirac.

Yes I have tried that already. Still the same.
[Android Software Development] mrrocketdog:
*edit*
[Android Software Development] zenjedi:
Oh it works wonderfully well! I rooted my phone just to install this mod.
[Android Software Development] mrrocketdog:
edit
[Android Software Development] gokart2:
Don't even try pal, I'm the edit king!

Edit: LOL!
[Android Software Development] mrrocketdog:
lmao:thumbup:

---------- Post added at 12:25 AM ---------- Previous post was at 12:20 AM ----------

approx. 36hrs?
[Android Software Development] harshil33:
[MENTION=6449207]Roi007leaf[/MENTION] [MENTION=4445176]guitardedhero[/MENTION]

I have used Roi007leaf.prop to install the magnus opus.

Viper drivers are supported. But I am getting this Unfortunately, Dirac Control Service has stopped at interval of like 20 seconds.

logs are attached of viper4android, dirac and ICEsound. please suggest me a solutions for this.

I am using Enigma V5 Rom on my Samsung Galaxy SM-J700F. (Exynos Processor)

Thank You for this awesome build.
[Android Software Development] Roi007leaf:
Dirac doesn't support Samsung devices fully
[Android Software Development] harshil33:
Also viper is not processing.
[Android Software Development] mohand06:
Have you installed SuperSU ? Busybox?

Try other icesoundconfig.def, the number 2 being the one working across all devices and check the permissions of any file you may have edited.
[Android Software Development] gokart2:
This is good to know. I was unaware of this. Is there any other "known" issues, directly related to Sammy devices. Specifically S8/S8+?

Is that taken with the music playing? Have you played music, toggled viper off, then back on?vMusic has to be played for it to process. And the toggle on-off-on does seem to change things. IMO.
[Android Software Development] harshil33:
Yes its with playing music.

Bdw i removed dirac and ICEsound completely.

Now the only thing i installed is viper 2.5.0.5. And its working perfectly. :svetius:
[Android Software Development] Domnisto:
Any recommendations, on a set up? For good bass and clarity. Preferably for EDM music. I experimented with most of it. But would like some suggestions.
[Android Software Development] jmxc23:
i know that I just didn't post an update.
[Android Software Development] lenigma1too:
I'm starting to realize that my having to manually install everything and jerry rig files around to get eventhing working with each new release seems to at least have taught me a few weird workarounds that maybe we'd never find otherwise haha... at least not until maybe ONE other zenfone 2 user started using the Arise as well, it' would be nice to have another person on x86 to bounce ideas off of...

until we get a friggin install script -glares at [MENTION=4445176]guitardedhero[/MENTION]- false hope givin' mammajamma...

I'm sure by now u have already acquired 1 or a few x86 users, however, I'm here with a a Zenfone Z00AU 4 u to bounce ideas off of if ever the need should *clears throat* ARISE! LOL.

I'm a daily user, on XDA 4+ times a day, and this ZF2 is not my DD, so we can flash away...

Sincerely, lenigma1too
[Android Software Development] aki_007:
Hey mate . how r you ?

Can you please share the IRS collection zip that you shared earlier .
[Android Software Development] fahad_maniar:
Hey guys, i have installed viper4arise with guitarded hero's script.. But when i use esira player the sound is not processed.. Any idea why its happening? I tried with blackplayer and it was working but not with esira..plz help
[Android Software Development] Roi007leaf:
ICE?