yashsingh1/xdaforums huggingface dataset:
[Android Software Development] Skittles9823:
I experience clear audio. When I used ice however I would notice white noise so I removed ice from my setup
[Android Software Development] Poipoii:
Actually I'm starting to think the noise comes from the tracks themselves. I guess it's either on purpose or the production's fault. If you have time, try listening to Kendrick Lamar - FEAR and/or Sza - Doves in the wind. First 20 seconds or so should be enough to decide if you hear it. In case you're wondering, I've tried lossless music files too. The static might have always been there, but I only started noticing it with the sound clarity of Viper. If you can confirm you hear it on either or both of the tracks, I'll take that as the conclusion. Thanks for your help, Skittles! :good:

P. S: I find it very noticeable on SZA's.
[Android Software Development] Skittles9823:
Listened to doves in the wind and instantly heard white noise. Its the songs. Pretty sure its on purpose. Some people including myself enjoy white noise over a chill song.
[Android Software Development] Poipoii:
Alright! Good news to me then! I personally don't enjoy white noise that heavy on a track. It sounds as if the track is low-quality to me :rolleyes: On the other hand I love a little vinyl crackling, guess that's just contradictory but that's just me.

Thanks again for your time then, that answers my question! Have a nice day and some great music experience :p
[Android Software Development] mrrocketdog:
try changing min cpu frequncy. cant remember the exact number (a search should suffice) but read alot of posts (bad memory :) ) about that being a fix. [MENTION=6449207]Roi007leaf[/MENTION] , are you around friend.? heard this before ?
[Android Software Development] frickinjerms:
I could be wrong here, but I believe all these effects end up raising the noise floor which will add static like sound and other artifacts to an audible level as I believe that viper uses a compression technique to achieve some of its magic which will raise the noise floor to give the sound more "punch". Since there are no noise gates (which are common in guitar rigs to remove hiss and other artifacts when not playing) to combat the noise floor gain and bring it back down, you'll end up with noise you may not have heard previously. It's really similar to having a chain of eq/distortion pedals before the amp (core, v4a, am3d, etc) the more there are, the more it raises that noise floor before it gets to the power amp (inside the headphones before the speaker) and speaker (headphone driver).
[Android Software Development] Skittles9823:
Thanks, we already found out the songs he was listening to had white noise in them so it wasn't an arise problem.
[Android Software Development] mrrocketdog:
MXR smart gate™ ftw :thumbup:
[Android Software Development] Poipoii:
Hey, thanks for your response, but if you read the rest of the discussion Skittles and I had, you'll see I was just being kind of stupid, listening to tracks with white noise (mentioned 2 if you want to check for yourself). After trying some other (older for some reason), I can say I don't have a general background noise issue. If ever do notice it, I'll keep your advice in mind. :good:

EDIT:

I'm too slow I guess haha.
[Android Software Development] frickinjerms:
I totally had one of those before going the rackmount route ? now I just use the one built in to the pod HD pro x and it works well enough
[Android Software Development] guitardedhero:
Nothing, I mean NOTHING, beats the ISP Decimator G-String. :good:
[Android Software Development] jcmm11:
Filter the log output, not just enter it into terminal emulator. How are you generating the log? If using something like catlog or matlog they have filtering available within the app. Enter "type=1400” there.

See screenshot
[Android Software Development] MobbareKurtZ:
Running latest Magnum Opus on latest FreedomOS on my OnePlus 3. Everytime I start listening to music neither Viper or Atmos will process. I have to make a soft reboot and then it'll start working. Anyone knows what the problem is?
[Android Software Development] frickinjerms:
I ran out of rack slots ? otherwise that would be a great addition to my rig! A buddy of mine had the stompbox version and it was legit, no matter how many effects were stacked in front of it
[Android Software Development] dorimanx:
Dear Arise DEVS, really love this mod you made.

was using the ARISE+Magnum+Opus+20170506 with CORE + Viper2.5 and nothing more, all was working perfectly with Selinux Enforce.

Updated to ARISE+Magnum+Opus+20170703 and now viper app is looking weird.... red and black check box like in android 2.2, no colors.... no fancy rollers for tuning, really liked that... i want the old app please :)

But that is not the issue.

now with enforce, app show driver status DEAD. you know unsupported :eek:

setenforce 0

exit app, start app, all great! and works just fine.

question. what can be done to get it working with enforce.

Personally i dont need any other fancy mods that cant live with selinux. just my old beloved viper and your great core drivers.

Thanks in advance.
[Android Software Development] Skittles9823:
If you use magisk I'm pretty sure there is a module to set to permissive at boot.
[Android Software Development] dorimanx:
no i dont use that "thing" and no, i dont want to loose security... it's was working, so i hope it's will keep working. in next build.
[Android Software Development] Skittles9823:
Fair enough.
[Android Software Development] Mars_Ammar:
I am getting abnormal driver status with Viper4rise 2.5.0.5

I just clean flashed, using SuperSu (flashed before flashing Magnus), busy box installed , on rom : Nitrogen OS 7.1.2 with EX Kernel.

I had it working perfectly before updating to the lastest build of nitrogen, don't know what went wrong, my setup is only Core + V4A + Atmos. Dolby Atmos is working normally.

I tried dirty flashing and reinstalling the whole system again but still same problem , what's wrong ?.

Thanks
[Android Software Development] mrrocketdog:
if not already , try setting SELinux to permissive.
[Android Software Development] Mars_Ammar:
Sorry, how can I do so?
[Android Software Development] jhobc:
Hi! Sorry for the delay. But answering your questions:

1 - No. Just Arise. I also tried your Dolby release (Did a dirty flash before) but Atmos still FC.

2 - I'm on Android 7.1.2 (SDK 25)

3 - The dumpsys output log is attached

Thanks for your attention!
[Android Software Development] RSDamasceno:
Bug report: Dolby Digital Plus FC.

With this: https://www.androidfilehost.com/?fid=817550096634785490

Resurrection Remix 5.8.3 - Android 7.1.2.

SELinux Permissive

Magisk 13.1

I'm suspecting that it has something to do with my custom dpi (433), since after switching to standard dpi the FC stopped.
[Android Software Development] mrrocketdog:
you can try using this app.

http://xdaforums.com/showthread.php?t=3574688
[Android Software Development] Mars_Ammar:
OK I switched it using the user settings in the EX Kernel manager app

All working now, thank you. I thought viper is working in enforcing now.
[Android Software Development] kaygoingpro:
Everything is working fine except these annoying problems like blank effect profile n no kernel found
[Android Software Development] roanepv:
Viper XHifi doesn't work , i have busybox 1.26.2 installed on system/xbin , using Android 7.1.2 ( LineageOS ) Selinux permissive , rooted and granted permission to the app , but everytime i try to launch it , it says Busybox not found what should i do?
[Android Software Development] mrrocketdog:
make sure V4a has storage permissions.

and if needed , see OP for possible locations of profiles , IRS's & DDC's.
[Android Software Development] guitardedhero:
Will someone upload /system/etc/init.d/arisesoundserver from the latest build? I am convinced this is where many issues begin for most of you. :good:
[Android Software Development] umidbek_97:
Here , rename from "arisesoundserver.zip" to "arisesoundserver"
[Android Software Development] jhobc:
I don't have this file on that folder.

Just these files:

arisesound_disabled_setprop

post-boot

service
[Android Software Development] RSDamasceno:
Here
[Android Software Development] krutik66:
i tried set up arise customize from r3v3nt3ch but after phone boot i have fc on arkamysaudio and dirac. same with dolby atmos from magnum opus and from dolby audio aroma from yesterday

Odesláno z mého LG-H815 pomocí Tapatalk
[Android Software Development] guitardedhero:
Flash the attached zip to update your ARISE scripts. :good:
[Android Software Development] jcmm11:
Just a quick look, but mount_magisk references $BIN ($BIN/toolbox and $BIN/toybox), which isn't defined anywhere.

Edit: it should work anyway. I can't see any remotely current phone not finding the mount specified before that section of code. That code is just a fallback if the plain mount isn't found for some reason.

You could also simplify the entire script by just assuming that execute and execute.sh do exist instead of testing for the existence.

mkdir -p will not throw an error if the directory already exists and rm -f will not throw an error if the file you're deleting isn't there. Just delete both of them.

rm -f $SUD/execute $SUD/execute.sh
mkdir -p $SUD
if [ -e "$MAGISKIMG" ]; then
. . .
echo "Symlink will still be attempted."
echo " "

fi
cp -f $EXEC $SUD/execute.sh
chmod -R 0755 $SUD
restorecon -R $SUD
ln -sf $SUD/execute.sh $MAGISKCORE/execute.sh

else

cp -f $EXEC $SUD/execute
chmod -R 0700 $SUD
restorecon -R $SUD
. . .

Actually you can go a step further and just use execute.sh in both cases (although you'd still need to check for Magisk to correctly set the symlink, but you could move the cp, chmod, and restorecon up to immediately follow the mkdir)
[Android Software Development] Metalartin:
Ok I've installed this for the V4A profiles and whatnot, I've just bought a Vifa Helsinki Bluetooth Speaker and wanted to get the best possible sound out of it so rooted my phone(ZUK Z2) and installed ressurection remix 5.8.3 just to enable the APTX bluetooth output. With Neutron (64bit processing, audiophile resampling, AGP, Dither, Audio Focus, Generic Driver, 32bit output) it sounded fantastic(much better than jetaudio+ for me), the cleanest and clearest I've heard a Bluetooth speaker in person.

Then I heard about V4A being a must and then ARISE but I think the quality has gone backwards, it sounds a lot thinner than it did without VFA with almost anything I try. I'm unsure whether to uninstall and be happy that speaker has flat enough response already, I really only wanted to enhance the soundstage if possible, maybe a little bit of bass bass boost a lively warmth added when I want fun instead of accuracy.

Has anyone got a higher-end bluetooth speaker profile to share? Or any pointers. I have flicked through the convolver settings and Paul-Stereo.irs sounds like a good starting point, it's times like these you wish you'd recorded the sound before installing new drivers so you can be sure you've improved on where you started from(I do remember I was happy with how clean and smooth it was). How much of my phones sound has this changed? I already had VFA installed via magisk so I only installed the core system module, vfa profiles, DD+ and D-Atmos but even with VFA turned off it still sounds different.
[Android Software Development] Skittles9823:
Since you already have great sound I would say stick to only one of the Dolby modules. I like Atmos but DDP may work better for you. You could also try only having V4A and work with that.
[Android Software Development] guitardedhero:
Ah, thank you for catching the omission! :highfive:

The execute detection (which adds additional unnecessary operations as you described) is actually in place for plans I have regarding that script. Of course this can change at any time, but currently, I am planning on the execute script evolving over time and adapting as different installations are performed, so this script would vary from device to device.

Regarding the shell extension, that can certainly be added since the possibility of being executed by something else is nearly nonexistent in Android.

Thanks again for examining the script. :good:
[Android Software Development] Metalartin:
I hadn't even got around to testing the Dolby apps, neither of them load they shut down as soon as you open. I've just uninstalled them and installed atmos via magisk and it's doing the same there. Haha things are never that simple are they with android hacks. Looks like I will have to do more reading to see why it's not working tomorrow... having said that I heard dolby atmos hasn't been well received, is it more of a headphone user enhancement than a speaker one?
[Android Software Development] Skittles9823:
Try the Dolby aroma installer guitardedhero posted some pages back. It works independent of ARISE.

Link: https://www.androidfilehost.com/?fid=817550096634785490
[Android Software Development] yung40oz84:
This is just if having issues correct?
[Android Software Development] Metalartin:
Ah thanks I will give that whirl and see how I go on.:good:
[Android Software Development] EstiR86:
Hey guys I have a problem with Viper4Arise not processing when I plug in headphones I have a few work arounds to this issue like denying and granting storage premission, rebooting device, and also flashing the fix SD card fix.

All of these are a hassel when it comes to just using it does anyone know another work around of maybe have a solution to my problem. After a reboot the device works fine and can allow me to switch from speakers to headphones fine and processes well.

I'm on Rooted Stock Android using SuperSU and I'm on July security patch I tried installing latest verison of magnum opum but it kept saying viper was processing so I uninstalled and flashed SwanSwong Aroma everything is working expect the switching between speakers and back.
[Android Software Development] Lughnasadh:
Did you try exiting V4A through the 3 dot menu and then opening V4A again?
[Android Software Development] EstiR86:
Not yet I'll give that a shot next time I just denied and granted storage premission for V4A I'll definitely look into this tho
[Android Software Development] guitardedhero:
Precisely. :good:

V4a > Headset > Disable (uncheck Enable)

Recents > clear v4a

Slooooowly insert auxiliary jack (the more crackles/pops, the better)

Begin audio playback

V4a > Headset > Enable

:good:
[Android Software Development] EstiR86:
Thanks for this ! I'll definitely give this a shot next time I never thought of putting in the aux cord slowly I just always pop it in and next think about it.
[Android Software Development] krutik66:
for what is qc effect? can i hear difference how find if it work and can i set true to all modules? and for what is iceconfig. cant find where is that explain

Odesláno z mého LG-H815 pomocí Tapatalk
[Android Software Development] Metalartin:
Ok just an update that could save someone else the trouble I just went trough, if you're installing and already have V4A 2.5.0.5 installed via the magisk method then before you begin uninstall that, furthermore you don't need to install the compatibility module if you have a Resurrection Remix 5.8.x rom, it could have been one of or both of these causing the dolby apps to crash.

I spent a few hours reading and flashing via different methods until RR got stuck on the boot animation... thankfully a dirty flash worked a treat and Titanium backup restored all my settings. Removed V4A and the compatibility module and tried RISE Magnum Opus installer from scratch.... V4A(the app is different?... Viper4Arise), VFA profiles, DD+, D Atmos all working now.
[Android Software Development] BlueJeans:
Does Dolby Digital Plus work in enforcing selinux for anyone? It processes sound but gets force closed on enforcing. Strangely, once I got it working even on enforcing (no FCs). But I forgot what I had done and now I cannot reproduce the same.
[Android Software Development] Metalartin:
Wow you seem to have lengthier replies than even myself there haha. Thankyou for the welcome and the informative post, I am new to all of this and will give Arise and V4A a fair shot.

I really think Neutron is the best player I've tried, JetAudio+ was really nice, as was power amp but Nuetron seemed much fuller and cleaner playing flac audio with the settings I mentioned. I've seen people mention USB Audio Player PRO but I think I've seen quite a few preferring Neutron over it, I think I will stick with that for now unless you can suggest something else?

I've actually already done what you said too haha(and I totally agree the aim should be to enhance not alter the sound of the speaker, if it sounds weird in any way or too boosted I get rid), as I felt a bit lost I turned everything off and went through the convolver settings as I mentioned in my last post, Paul-Stereo.irs seemed the best starting point to my ears. I also did play about with both Viper Bass and Clarity after I posted and I'm kind of relieved to hear that those three maybe all I need to focus on tbh.

V Bass

Natural Bass

Bass Freq: I wasn't sure so went with 58Hz as that's the lowest response the Helsinki can produce according to the specs. Not sure if this is too low but has to be better than the default 40Hz right?

Bass Boost: 14.8db I had it on a low volume so may have to lower that a bit for high volume

V Clarity

default settings seemed to not alter the sound too much, which are natural and 3.5db

I will play about some more, for widening the sound stage is there anything in V4A I should be looking at in particular? Someone mentioned the dolby apps for that so I will have a look there too when I have chance.

I'm not expecting miracles as I understand for it's size and physical dimensions it's already doing pretty well but if you can improve on it why not? That's what this is all about.
[Android Software Development] Xennet:
Any possibility of an update to magisk module to get arise working with magisk 13.2???
[Android Software Development] myheroduane:
Working fine on my HTC 10 with magisk 13.2
[Android Software Development] JaylanPHNX:
This definitely needs to be addressed, since the dev of magisk has made it clear that the next update or so will no longer support modules based on the old template.
[Android Software Development] Xennet:
You might have set the se linux to permissive or used a permissive script which I don't think is the right way to use as it compromises security..

Without that I think the module v3.3 doesn't support magisk 13.2..
[Android Software Development] Abhisht009:
I flashed the magnum opus but none of the apps were installed. I did edit the .prop file.

????!!!
[Android Software Development] Skittles9823:
What modules did you install? Did the installer give any errors? Magisk or SuperSU?
[Android Software Development] Abhisht009:
I'm using magisk 13.2

I choosed V4A, atmos, ice sound, V4A profiles

I did not get any errors
[Android Software Development] myheroduane:
All working fine just tested again.
[Android Software Development] Abhisht009:
Maybe it's because I do not have enough space in system
[Android Software Development] myheroduane:
:cyclops: omg
[Android Software Development] Xennet:
[MENTION=4445176]guitardedhero[/MENTION]

With new magisk 13.2 and magisk module v 3.3

ARISE+Magnum+Opus+20170703 viper doesn't process driver dead..

But...

ARISE+Magnum+Opus+20170506 viper processes and works good...

What's the reason???

Which is the version of magnum opus???
[Android Software Development] myheroduane:
Most current you can tell from UI on v4a. However I updated magisk after arise.( I had arise already set up on previous version of magisk and updated thru magisk manager app.
[Android Software Development] R0BiN0705:
I did the same but then on a fresh new rom somehow I couldn't replicate this..
[Android Software Development] Metalartin:
Just switched to Enforcing mode in resurrection remix and it's fully functional after a reboot with magisk 13.2 + SuperUser. You don't need the compatibility module if you have those two if I was reading the authors post right, in fact I had to uninstall it along with the V4A I installed via Magisk to get it all working.
[Android Software Development] aseferfan:
Sorry but V4A is still abnormal and now dolby atmos app is FC :/ ....anyone here have a working setup with V4A normal and magisk 13.1+ with selinux enoforcing?

I cannot set selinux to permissive even if i wanted to as samsung stock kernel doesn't allow it
[Android Software Development] Xennet:
You can't pass safety net with it....

Whatever the underlining fact is that the ARISE MAGNUM MODULE FOR MAGISK NEEDS TO GET UPDATED FOR ALL THE ERRORS DOWN HERE AT ARISE...
[Android Software Development] Slypnslyde:
People I'm passing safetynet just fine with any module on Magisk 13.2 by using safetynet passer

---------- Post added at 09:16 PM ---------- Previous post was at 09:12 PM ----------

https://xdaforums.com/showthread.php?t=3600431
[Android Software Development] yung40oz84:
Ya I am running Angler, DU, electron kernel, Enforcing, Magisk 13.2, Arise latest Opus. Pass safety net, and arise and viper fully functional

---------- Post added at 02:50 AM ---------- Previous post was at 02:48 AM ----------

I'm passing safety net right now with arise, and no safety net fix. Running Android pay. Magisk 13.2

---------- Post added at 02:53 AM ---------- Previous post was at 02:50 AM ----------

Just so all know and I can report. I am running Angler, DU, electron kernel, Magisk 13.2, enforcing, arise 703, with ice config 2, preset pure, viper 2.5.0.5, android O QC effect, deep buffer removed, and uninstall music fx. Viper is processing 100%, pass safety net every single time, no issues. Not using the safety net fix. Running Android pay as we speak.
[Android Software Development] JRJ442:
I'm actually running ancient Arise 2.93 and Magisk 13.2 on my 6p without any compatibility module or the Safety Net fix module. Passing Safety Net just fine. Arise processes just fine too.
[Android Software Development] EstiR86:
I did this but it says status normal, neon enabled: yes but it says no processing. I even flashed the permission fix only think that works is when I deny storage and reenable
[Android Software Development] Skittles9823:
To process you need to play music.
[Android Software Development] EstiR86:
I was playing music sorry if that wasn't clear
[Android Software Development] Skittles9823:
Remove deep buffer?
[Android Software Development] EstiR86:
Will try that later the deny storage premission and re-enable works for me
[Android Software Development] AquaBytez:
Well, the only thing that changed was Magisk. I think that I should have mentioned that I was using the Beta version of Magisk V13. Now I'm using stable Magisk v13.2 and Viper doesn't process after renaming arise_disabled_soundprop and disabling session0.

Dolby ATMOS from the Dolby Technologies zip (the most recent one). Still FCs. I'm also using Arise+Magnum+Opus+20170703
[Android Software Development] anil rajput:
Same here
[Android Software Development] denf666:
It is working fine with magisk 12.

V13 is not compatible.
[Android Software Development] Skittles9823:
Magisk 13-13.2 is actually compatible. I've used those plus every beta version of magisk 13 and it has all worked fine. It must be something to do with your device that has a conflict somewhere.