yashsingh1/xdaforums huggingface dataset:
[Android Software Development] djjohnnyblaze:
I can confirm. That file was not part of my original rom but was included with ARISE. After removing the file, blue tooth works again.
[Android Software Development] guitardedhero:
I apologize, I meant libbluedroid.so as libbluedroid_bdt.so is obviously in Exodus lol!:angel:

Fantastic! :highfive:

I'll get 0.9.9.2-2 prepared. :good:
[Android Software Development] FQuimson23:
Ok! Great job so far! Also, on the lib files, libbluedroid.so does not exist either in the stock rom
[Android Software Development] guitardedhero:
My device and rom do not support aptx (Nexus 6).
[Android Software Development] aki_007:
Vey annoying .

I dirty flashed my rom .

Installed latest ARISE without any bluetooth files .

then copied all bluetooth files from latest ARISE into my system one by one and a reboot each time to check which one breaks bluetooth .(I guess you've installed like this too .)

evrything works now .

same issue with dts app .

I flassh arise , dts Fcs , then I flash View attachment dts.zip

it fixes everything
[Android Software Development] guitardedhero:
Bluetooth Test 0.9.9.2-2​

---------- Post added at 01:44 AM ---------- Previous post was at 01:40 AM ----------

The builds are certainly built in that manner and I then zip up the files for flashing but I do flash the builds from time to time when I break something or can't boot lol!

Hopefully, you listen to quite a bit of Bluetooth as I'm anxious to hear your impressions with it fully working! :good:
[Android Software Development] aki_007:
sure as soon as I get to test it in my car's audio .
[Android Software Development] xevildoerxx:
ok bluetooth turns on with this build...but i cant test anything else until tomorrow...my wife is asleep and i dont want a divorce lol. so no music tonight. :). really appreciate all the work being put into this.
[Android Software Development] djjohnnyblaze:
Was the only change in the newest build removing the Bluetooth vendor file?
[Android Software Development] dialga13:
My nexus 5x doesn't seem to boot, it's stuck at the bootanimation after installing dolby atmos. It's rooted with Magisk and it has v4a, the audmodlib version, is it incompatible?
[Android Software Development] Skittles9823:
Reflash your ROM to be able to boot back to system. I've had some trouble with bootloops on my 5X after flashing things and I've found it's pretty random when it happens. Not sure if you're getting the same problem or not. But when you reflash arise don't use any magisk version of Dolby or v4a use everything from the official arise unless you wish to use the Dolby ports guitardedhero has been posting here.
[Android Software Development] divineazn716:
Magnum opus newest version not working for me. Latest version of magical 13.1 on Nexus 6p, rom aquarios, the arise deumotology works but try to flash the magnum and doesn't work, get stuck with the error 1. I'm running Franco kernel r54. Any suggestions?
[Android Software Development] dialga13:
I want to use the ports, I installed the ported dolby Atmos and got that weird bootloop. I got my phone to boot by reflashing the rom, now i'm going to try to see what's causing the bootloop. Thanks!
[Android Software Development] AquaBytez:
[MENTION=4445176]guitardedhero[/MENTION] Here's the Dumpsys output while playing audio after doing the steps you mentioned
[Android Software Development] guitardedhero:
That's better. You have the full Dirac effects-chain now, as well as the other premium effect-chains.

Exactly what is not performing to its potential? Have you confirmed that v4a is processing appropriately?

---------- Post added at 05:24 PM ---------- Previous post was at 05:01 PM ----------

For the record, error 1 in recovery is our forced termination of the script operations due to one of only a few scenarios that fail to allow our script to install YOUR specified sound system.

Much of Deuteronomy through Magnum Opus, we decided to provide an assortment of tested and worthy effect modules instead of a cookie-cutter, predictable sound system installation.

However, we (maybe just me, I think the team agreed with me lol) came to the conclusion that the best way to go the modular route was to require the user to be aware of the modules available.

Often, I was asked, "Why not just allow a minimal, automatic installation with zero input/effort from the user?"

Easy. I didn't want a user to boot from an installation and be confused by not seeing what they might have expected to see from past sound systems. I didn't want the user to test a minimal sound system installation against previous jam-packed sound systems.

By requiring just a single action by the user to achieve a successful installation of any kind with this modular method, the user is immediately made aware that they are in complete control over what installs.

If they don't like something about their chosen combination of modules, they already know what can be done to change and further test the installed sound system.

I'm rambling again, Error 1 is our best attempt to inform you why the installation will not continue (before any /system changes are made) and the necessary information for you to avoid that particular Error 1 during your next recovery session. :good:

You know, I've noticed several times that my son's phone appeared to be in a boot loop numerous times the past couple months. However, holding down Power until it begins to boot again has nearly always resulted with a very quick full boot. Definitely try that if you haven't. Obviously, that leaves much room for improvement, but I have yet to discover precisely what has been causing that unusual behavior. :good:
[Android Software Development] mrrocketdog:
nvm. ninj'd.:good:
[Android Software Development] dialga13:
I got it working! the cause was a magisk module, I uninstalled it and it started working. I like this Atmos a lot, sounds way better than others. Thanks for your work, arise is the best!

If anyone has this same problem, the module was audmodlib.
[Android Software Development] AquaBytez:
[MENTION=4445176]guitardedhero[/MENTION] No, the main problem has always been that the Dolby ATMOS app from the Dolby Technologies AROMA Installer zip instantly crashes. Viper has always processed, and yeah, it definitely sounds better now.

Thank you for your help so far :)
[Android Software Development] Robot76:
[MENTION=4445176]guitardedhero[/MENTION]

I love you!

You're the best!

Haha

LOS A.R.I.S.E. Z3C MAGISK SUBSTRATUM
[Android Software Development] denf666:
Dolby atmos axon 7 is FC on RR magisk 13.
[Android Software Development] AquaBytez:
[MENTION=6731780]denf666[/MENTION] Yup, that's the same problem I'm having
[Android Software Development] R0BiN0705:
I can't seem to get my previous setup (v4a+ddplus) working on the latest aospa, tried the latest July build as well as some May Builds. It has worked on their first nougat release and I've used it on any other rom now without any problems except for this release, not sure if this is the right place here but maybe somebody has the same problem.

v4a states it's status is abnormal, not enabled, no processing. have you guys any ideas where to fix this? or what the problem could be?
[Android Software Development] solifice:
no sound after headphone unplug is fixed in 4 july build

---------- Post added at 04:32 AM ---------- Previous post was at 04:25 AM ----------

i used magnum opus on kenzo may build and working good but i am getting a bug that after unpluging of headphones or earphones there is no sound from phone speaker until i restart

i am using resurrection remix 5.8.3 7.1.2

help
[Android Software Development] jhobc:
[MENTION=4445176]guitardedhero[/MENTION]

Hi!

Flashed latest Magnum Opus (20170703) on my Zuk Z2 on AEX 4.4 with Magisk 13.1 but the Dolby Atmos FC when I try to open.

Logcat attached
[Android Software Development] guitardedhero:
My pleasure. Next, we examine filtered ("dolby", "dseffect", "dax") log output.

The best course for this is to begin audio playback after a device boot, launch v4a to confirm its functionality, launch Dolby to confirm its functionality (obviously, we expect a hiccup at this step), and then launch your logging application (Matlog is an excellent option) and use one of the dolby filters (merely searching through the output) to limit the output to only that of interest while debugging your issue.

The beginning of that filtered output will be the very first event logged containing your search parameter, the very end will be the most recent event, so no need to be concerned with timing your interaction with the logging application.

I'll be more than happy to examine everything you provide for me.

Also, be on the lookout for any native Dolby effect processing used by your rom as there is always the possibility that remnants survive the Atmos port installation creating certain conflict. I am not entertaining the option to go "all nuclear" on anything and everything Dolby before finally installing the port. The plan is to modify the Dolby effect libraries only as much as is necessary to assign unique UUID values which will solve the vast majority of potential conflicts with native or existing Dolby installations.

Lastly, what SDK number is your current rom?

:good:

Have you examined the dumpsys output of media.audio_flinger?

su -c dumpsys media.audio_flinger

OR

su
dumpsys media.audio_flinger

Also, examine the output of:

getprop

for the few entries in /system/etc/init.d/atmos-setprop. Even quicker, see if any output is generated at all by using "grep" to filter the output:

getprop | grep dmid

:good:

What is your current root solution with your rom?

:good:

Your log suggests to me that you are possibly facing a conflict with:

/system/etc/dolby/*

and/or

/system/vendor/etc/dolby/*

Are you working with a software base including Dolby of any kind?

What SDK version is your rom?

Is the Dolby effect-chain created when observing your dumpsys output?

:good:
[Android Software Development] AzraelX:
No. I didn't install deep_buffer either. Anyway I got fixed the problem.problem was ICEconfig number.I changed It to number 2. Then it works perfect. Thanks for your help.
[Android Software Development] Skittles9823:
[MENTION=4445176]guitardedhero[/MENTION] Dolby Atmos aroma fc.

Dolby and dax.txt are logcats searching each keyword respectively and dumpsys and getprop you know already.

I'm running magisk 13.1 on android 7.1.2.
[Android Software Development] guitardedhero:
Great, informative post! :highfive:

It is clear that the necessary service script and and the atmos-setprop, both in the Dolby zip, are not executed with your Magisk installation, which will result with precisely what you described.

Those two scripts I mentioned are, in reality, executed by a single script (also in the Dolby zip), /system/su.d/execute. Magisk detection will add additional commands to the writing of this script during installation:

/system/su.d/execute is renamed to /system/su.d/execute.sh with 0755 permissions (instead of the default 0700 when Magisk is not detected) and then symlinked as /magisk/.core/service.d/execute.sh.

This allows the execute.sh script to be automatically executed by Magisk during the late service portion of the device boot, which simply executes /system/etc/init.d/service and any /system/etc/init.d/*-setprop files that are found.

First, confirm the presence of /system/etc/init.d/service and /system/etc/init.d/atmos-setprop, followed by confirming the presence of /system/su.d/execute.sh (/system/su.d/execute is considered an error in a Magisk scenario).

If everything is found as described above, navigate to /magisk/.core/service.d to confirm the existence of execute.sh with 0755 permissions, which, of course, is merely /system/su.d/execute.sh.

My preference for symlinking 100% of any content destined for /magisk/.core/service.d (think Magisk's alternative to SuperSU's /system/su.d or /su/su.d) is purely logical:

If, at any time, an uninstall procedure is performed for any mods, the symlinks will disappear with the physical scripts, ensuring that Magisk never executes an unnecessary script.

If, at this point, everything is found to be the result of a successful Dolby installation with a Magisk installation, the problem(s) will be between Magisk itself and the contents of those three scripts. :good:
[Android Software Development] R0BiN0705:
Rooted with Magisk 13.1, seems like the ddplus app is unstable with this rom but its still processing the sound. every other module seems to be working too except v4a (both versions, didn't try xhifi though). I got prompted to install the driver which did actually never work for me on any nougat rom
[Android Software Development] aseferfan:
Anyone else having V4A status abnormal with latest magisk 13.1?

I am running a very close to stock rom rooted with magisk 13.1 and safetynet passed status.

I heard magisk 13.1 has changed some templeates that makes old magisk modules not work as intended (specifically to seinject-policy) HERE

problem is, that V4A is an old version and i would like the V4A inside ARISE to work(I can't find any post-fs-data.d or service.d folders either)

My current setup is V4A 2.5.0.5 with ICEsound config=2 and preset=puresh*t

I have also enabled magisk compatibility found inside the magnum opus, arise_customize.prop

using latest july build of magnum opus

Please anyone know how to fix,i have tried a lot of V4A for magisk and none of them seem to work right :/. And no im not looking forward to setting selinux to permissive
[Android Software Development] Roi007leaf:
Permissive might help you
[Android Software Development] solifice:
anyone facingheadphone unplug bug on latest july build
[Android Software Development] Barsko:
Hello friends! I have now some videos on youtube, how to install ARISE + Magnum + Opus + 20170703, but I found no one where it is also shown how to add the "guitardedhero or Paschfire". Can someone help me there? I have a samsung s6
[Android Software Development] Skittles9823:
Okay so everything is good except there is no execute.sh In /magisk/.core/service.d should I just copy /system/su.d/execute.sh to the folder and give it 0755 perms?
[Android Software Development] eldho43:
Which rom?
[Android Software Development] Skittles9823:
To answer my own question, yes. That fixed it.
[Android Software Development] jandia7381:
Now i'm using aex lite, before that aex. Fyi most rom i tried got no problems with ARISE, all working just fine. Usually i just install viper 2.3.4.0 + profiles, asus/stock soundmod, i/c 2 + pure****/shat and new port Atmos
[Android Software Development] guitardedhero:
Fantastic! That was a pretty damn efficient troubleshooting session, I'd say lol! :highfive:

I believe I've made the necessary corrections in the script to successfully symlink this script as intended (assuming the /magisk mount script I'm using is adequate) and will provide an updated package today. This will likely solve nearly every issue for those experiencing them with Magisk. Thank you very much for solving this for me. :good:
[Android Software Development] aseferfan:
I have flashed this : MAGISK Permissive Script

But my kernel info is saying that Selinux is still enforicing,

I believe samsung stock kernels do not support permissive mode,

as a result even after flashing it V4A is still saying status as abnormal,

I do not have any FC but Dolby atmos is also not processing any audio either(like no music was playing),
[Android Software Development] Skittles9823:
Viper>settings>dev mode>disable se Linux. Does that work?
[Android Software Development] aseferfan:
Nope,Still SElinux enforcing and viper status abnormal(after 2 times retrying and rebooting)
[Android Software Development] guitardedhero:
Reflash the Dolby port using the latest package found here:

AFH Dolby™ folder​

All three Dolby™ ports updated with script corrections to successfully symlink /system/su.d/execute.sh to /magisk/.core/service.d/execute.sh.

Magisk users, confirm effective update by the presence of /magisk/.core/service.d/execute.sh.

Everyone else, installation remains the same as before, no changes intended.

:good:
[Android Software Development] krutik66:
is it good install all modules+qc effects+icesound and this dolby zip?

Odesláno z mého LG-H815 pomocí Tapatalk
[Android Software Development] derkleinebroicher:
Dolby Atmos keeps FCing on my Nexus 5x. And no execute.sh in the described path.
[Android Software Development] R0BiN0705:
Didn't fix v4a for me :/
[Android Software Development] Kentut77:
it's not working on magisk 13.1
[Android Software Development] Zackptg5:
[MENTION=5368959]Shadowghoster[/MENTION] is working on an update
[Android Software Development] Kentut77:
glad to hear that, i change the selinux to permissive and it fixed the problem but i don't like having extra app just to change that :D
[Android Software Development] yochananmarqos:
Same here. The Atmos uninstaller works, but the Dolby Audio uninstaller does not.
[Android Software Development] slimcyril:
[MENTION=4445176]guitardedhero[/MENTION] the script below has set all the android devices(s4,s5 & s7) I ever used in permissive mode even when the selinux mode changer failed, review it and integrate into magnum opus!

Note: the author of this script claimed it should work on all android device.

#!/system/bin/sh

# by Walter.White aka Heisenberg

echo "SELinux is set to: `getenforce`"

busybox sleep 1

echo -n "Please wait..."

busybox sysctl -w kernel.kptr_restrict=0 >/dev/null

kvar_addr_hex=`busybox cat /proc/kallsyms | busybox grep ".*\ selinux\_enforcing$" | busybox cut -f 1 -d " "`

kvar_addr=`busybox printf '%d\n' "0x$kvar_addr_hex"`

busybox printf '\x00' | su -c busybox dd of=/dev/kmem seek=$kvar_addr bs=1 count=1 conv=notrunc 2>/dev/null

echo "done"

busybox sleep 1

echo "SELinux is now set to: `getenforce`"
[Android Software Development] Skittles9823:
But you don't need permissive for arise to work. It should be working no matter what your Linux state is.
[Android Software Development] slimcyril:
Well I have seen few posts of viper4android or viperarise not processing & selinux issues on here, there shouldn't be an adverse effect of setting selinux permissive once & for all.
[Android Software Development] Skittles9823:
Yes that's true. But the majority of the users don't need it. If I remember correctly there used to be a permissive script in either swan song or Deuteronomy but it was removed in magnum.
[Android Software Development] guitardedhero:
Scripts updated to do what they have been intended to do this whole time, we'll see lol. :good:

Thank you for your input on ways to improve the experience for everyone, however, forcing a Permissive SELinux Mode for users is simply unacceptable. :good:

Edit*

This is a perfect time while we're on this subject:

Users concerned that the provided sepolicy rules may be insufficient:

Provide a log output for me to examine filtered with "type=1400"

:good:
[Android Software Development] slimcyril:
I typed these "type=1400" without quotes in terminal emulator but got no additional log file in /data/ folder or sdcard, where am I supposed to find the log output or file?
[Android Software Development] AquaBytez:
[MENTION=4445176]guitardedhero[/MENTION] Viper doesn't process anymore. And none of the filters give any output. My rom is using SDK 25
[Android Software Development] guitardedhero:
That means your phone's services, processes, applications, etc. are operating unrestrained as if they were operating in a Permissive Mode SELinux environment. :good:

"anymore" suggests that something was likely done, resulting in this new behavior. Was it a Dolby installation? Please expound a bit on your v4a issue. :good:
[Android Software Development] guitardedhero:
Lol, my mistake. That debugging procedure is only relevant for those in Enforcing Mode. :good:
[Android Software Development] Bobbaloo:
Small price to pay imho, for such amazing sound
[Android Software Development] slimcyril:
Gotcha
[Android Software Development] BlueJeans:
Previously was it "/system/su.d/execute" or "/system/su.d/execute.sh"? And, what about "arisesound_services" in su.d folder? Do I have to rename it to "arisesound_services.sh" and copy it to "magisk/.core/service.d" and set permission to 755 if I'm using magisk?

EDIT: To answer my own question, arise magisk compatibility module does the same thing. It executes script from su.d
[Android Software Development] Skittles9823:
Just follow what guitardedhero said in his post. All I did was copy /system/su.d/execute.sh to magisk/.core/service.d and gave it 755 perms. I didn't rename it or edit it.

Dont touch arisesound_service at all you dont need to touch it.

Also he uploaded a new version which should fix the problem.
[Android Software Development] BlueJeans:
Thanks, I know you were talking about "execute.sh" but I was just wondering how would something from su.d execute without SuperSU installed. I think I know the answer now. :)
[Android Software Development] twe90kid:
thanks ,will give this a shot
[Android Software Development] Poipoii:
Hey guys,

I want to thank you first of all for Arise, great work! :good:

Anyway, I'm only using the Viper 2.5 module at the moment and I absolutely love it. However, I'm getting a constant background noise, like static, which becomes especially noticeable when playing music on speakers. I'd love to get rid of it. Any help on that?

I've looked around a bit beforehand but this issue isn't so well documented AFAIK. Only suggestion I found was to delete /system/lib/soundfx/libbundlewrapper.so. That doesn't work for me. I tried deleting the one in /system/lib64 as well for good measure, and also renaming any file with the same name in the /system folder (.bak) and that didn't work neither.

P. S: I also deleted the deep buffer in hope it would change something but it didn't. Should I try installing the QC Audio Effects or any module to fix the static?

Thank you in advance. :)
[Android Software Development] Skittles9823:
Dont use ICEsound. That is what was causing static for me, even when Viper wasn't enabled.
[Android Software Development] Poipoii:
Thanks for the quick response, but, as mentioned, I'm only using Viper.
[Android Software Development] Skittles9823:
Oh okay. Is the static happening if nothing is on except just viper being enabled?
[Android Software Development] Poipoii:
Hmm I'm not quite sure what you mean but Viper is my only sound processor if that's the right way to say it. If you ask if I get the static without any sound playing then no. I only get light, but constant static whenever I listen to music(most noticeable with music in Poweramp and Spotify). It might very well be there whenever any sound is processed, but I don't think so.
[Android Software Development] Skittles9823:
No what I mean is go into viper and uncheck everything except master power. Then see if you still get static.
[Android Software Development] Poipoii:
Yes I do still get the static that way, it's not an issue of settings. As a matter of fact I still get it if I disable it, but not when I don't have Viper installed. I'm somewhat experienced with Viper from older official versions. Of course the static is more noticeable with effects on as they make all sound louder & clearer.

EDIT: Just noticed that the static does indeed stop when there is total silence on the track I listen to, if that helps in any way.
[Android Software Development] Skittles9823:
That is very odd. I don't know what even to look for there. [MENTION=4445176]guitardedhero[/MENTION] do you know what logs he should retrieve for this?
[Android Software Development] Poipoii:
I'm not sure if that's revelant, but from my own research, some people were saying that background noise was present for anyone using musicfx or something similar. Skittles, if you really pay attention, and listen to a "not-so-loud" part of your songs, can you not notice any background noise? Like white noise, if you know what that is?
[Android Software Development] handers1234:
Umm...,simple question what's maxxaudio that guitardedhero uploaded with dolby?I don't see any new app nor heard any difference in sound(or it just my bad ear?).