yashsingh1/xdaforums huggingface dataset:
[Android Software Development] Dbj.Dhaval:
Just to clarify what to do.

1.dirty flash the rom

2.flash arise 1.1.2 zip

Now about the most confusing(atleast for me) tweak.prop. There is a file name suggested tweak.prop in the zip itself and a folder named tweakpropscript(inside it another zip of tweak.prop) and a tweak.prop zip in op.. So which tweak.prop file or zip should I use and when ie before I flash 1.1.2 or after flashing.

Ps this is my first time flashing ARISE mod. I am using dirty unicorns rom nexus 6p.

Thank you in advance
[Android Software Development] meleelord:
Still a no go... Anything else you might like me to test?

Is anyone else having issues with the Lenovo version?
[Android Software Development] dingermtb:
If you flash A.R.I.S.E. and do not have a tweak.prop file set up or want to edit your tweak.prop file, no need to reflash A.R.I.S.E. just flash tweakprop.zip after your edits.

Sent from Outside the 9 using my Zombiefied Exodus OnyX
[Android Software Development] Lucki_X:
Quote:

Originally Posted by guitardedhero

While I await feedback from Ben would you mind testing this build that leaves that component still fully intact in my opinion?

https://www.androidfilehost.com/?fid=24549084345925819

Hi. With this TEST build I even wasn't able to boot into the system. I stacked on a boot logo. I tried dirty flash and clear flash even a flash in clear system. Thanks for your effort.

I wrote it in that other thread so I have moved with this problem here.

The main problem is that when I flash A.R.I.S.E. my recording app doesn't work. If I try to use it writes "internal error of app" so I started to check other [MENTION=4445176]guitardedhero[/MENTION]es modes and I recognised that it's caused by exB auralmaximizer. So I tried your test build.
[Android Software Development] guitardedhero:
Thank you again for yet another insightful and helpful review. As a reward, here is a 1.2 version especially for you! :good:

If I did everything properly, this should be able to be dirty flashed over any existing Genesis™ version including Lenovo Atmos. It also includes updated and additional scripts for compatibility that will be featured in the other versions once updated to 1.2.

Every bit of your info will be referenced and utilized in the Dolby files for the non DD+ and Lenovo Atmos versions. Bravo, fantastic job! :highfive:

ARISE Sound Systems™ Genesis™ 1.2 DD+™​
[Android Software Development] kuya38:
Great soundmod. But my sim card not detected after flashing.. I'm on cm13 gt-i9152.. Sorry for my bad english
[Android Software Development] guitardedhero:
Did you see the post where Ben mentioned it is likely caused by /system/etc/tinyalsa-audio.xml or one other file? Go back to the original post and try deleting one or both of those files after flashing a normal Genesis™ build.
[Android Software Development] Joy Bangla:
is there any difference with the atmos version other than the dolby gui? I ask cuz the file size is almost 2MB less for the lenovo atmos zip
[Android Software Development] guitardedhero:
Really? I wonder what could cause that... any ideas guys?

---------- Post added at 12:03 PM ---------- Previous post was at 12:02 PM ----------

The Dolby libraries I've been using for the other versions are quite massive.
[Android Software Development] Mars_Ammar:
I keep getting the driver not installed (You need to install driver) message, I am on Dirty Unicorns 10.2 ... Permissive.. Clean flashed
[Android Software Development] guitardedhero:
Delete/rename /vendor/etc/audio_effects.conf and reboot. :good:
[Android Software Development] Mars_Ammar:
Thank you that worked ..but I am not noticing major changes in audio quality nor loudness .. Anything I should do ?
[Android Software Development] Joy Bangla:
those libs are not needed if i have lenovo atmos version?
[Android Software Development] J.E.N.O.V.A.:
1.1.2 sounds very very good. Thanks for this awesome sound.

For all those people out there who are looking for a song to test clarity and bass. The ultimate song is

"blow your mind" by digitalboyhd. Download it and hear via your music player. :ultimate:

Oneplus One J.E.N.O.V.A.-Edition
[Android Software Development] guitardedhero:
Yes, begin audio playback and post a screenshot of v4a's Driver Status found in its menu.

Those libs will cause it to FC but I am very curious about the massive libstagefright_soft_ddpdec.so used in place of DD+'s file of the same name. Of course, it's also possible to test the massive libswdap.so in place of Lenovo's Atmos library by renaming it to libswdap-mod.so.
[Android Software Development] OmarUdave:
as installing Atmos no graphical user?
[Android Software Development] JellyTooth:
just install this .

extract on your pc

put that updater-script file instead on the one you have in aroma .zip

this will fix your issue with the no GUI problem
[Android Software Development] whood:
I have no sound on 0.9.5. Tried new and old zips, different presets. All of the builds before were just fine.

Viper shows audio format unsupported. I've been on this rom since ViperAtmos 4.8 times, always did system wipe before flashing.

I'm on Jiayu G4S CM 13. I can flash it again and make logs if needed. Back to 0.8.9 right now and i hope release version will work just fine :)
[Android Software Development] :
Sonophilos 0.9.5 review [MENTION=4445176]guitardedhero[/MENTION]

Once again, everything in my tweak.prop // GH's updates is working beautifully... except the Dolby DS2 lines. I tried disabling them one at a time, even, to see if the hard bypass itself was the issue, but alas, no. So, with Dolby OFF:

The clarity and space of the sound have once again increased over 0.9.4 and previous 0.9.x builds. This is the closest yet to achieving the sound of 0.8.9+Dolby that I'd been returning to through every previous 0.9.x build test. Treble seems to have more presence and detail without seeming harsh; mids are well balanced and clear, not lost in the space created around them; bass is round and prominent without creating mud - indeed, this is the clearest bass I've heard so far. Still, I find myself missing the depth of the soundstage with Dolby DS2 ON, and the power of the physical presence of the bass. This comes very, very close, and with a cleaner mix overall than 0.8.9.

I notice the driver (libv4a_fx_ics.so) in use is still the 810k variant, which as I understand from a previous post might be the High Quality driver? I'll test removing and reinstalling Super Quality to see if this is indeed an issue.

UPDATE: Manually installed Super Quality driver and it's definitely 810k with a matching md5 to the one installed by ARISE. False alarm, people. :good:
[Android Software Development] JellyTooth:
back in days i was using only vanilla viper i usually felt that viper 2.4.0.1 drivers sounded better than the super audio quality drivers in the viper earlier versions . maybe its only me though
[Android Software Development] :
Ah, that's what you meant? I definitely disagree, when 2.4.0.1 came out GH built a branch of ViPERAudio around it, and the whole time I felt strongly that the 2.3.4.0 SQ driver was much better. Maybe it's only me, though...
[Android Software Development] Paschfire:
I'm with you on this one, the older 2.3.4.0-SQ driver sounds much better than the newer 2.4.0.1 driver does.
[Android Software Development] :
Presenting...

Sonophilos (Lover of Sound) Profiles and tweak.prop for ARISE 0.8.9 - ARISEN/REVISED

ARISE Exodus 0.8.9: https://www.androidfilehost.com/?w=files&flid=61641

-----

Changes

--

Profiles: increase Cure-Tech binaural effect on Headphones profile to Moderate to reduce listening fatigue. You may also want to toggle the FIREqualizer on to further tame sound if you find my profile too harsh by default.

tweak.prop: implement new properties and organization from 095 update, only properties that function in 0.8.9

*Dolby ON is now DEFAULT in this tweak.prop ONLY*

Since the reason I keep coming back to 0.8.9 is that Dolby DS2 is operational for me on this version but not 0.9.x, I have decided to set the DS2 properties ON by default for this revision (and any future revisions to this 089 branch, should there be any).

Users will still need to configure the following manually in tweak.prop BEFORE flashing the tweakprop.zip tool, if desired:

Dual mic noise cancellation for devices with dual mics

64bit audio offload property, for ARM64 devices only

Resampler quality "4" to force sinc/revised resampler, if device supports it

ARISE Exodus 0.8.9, these attached profiles and the attached tweak.prop with the three above changes is the setup I am currently listening with. Having tested 0.9.5 I find it comes veeeeery close to the sound achieved here, but I keep coming back here for a reason and I feel right doing so every time I get sunk into this setup for a short while.

Hope you enjoy it!
[Android Software Development] JJEgan:
As above older driver better for me.
[Android Software Development] chas_43:
Thanks for your excellent contribution to this great thread, with a really helpful Aroma installer.

In that updater-script you posted above, you've moved the tweakprop extraction & running of updater-binary to the end, outside of the

"if file_getprop("/tmp/aroma/disk.prop","selected.3") == n .... endif; loops

so, Twrp fails to run it as during it's initial parse of the zip/script (before the aroma part runs) as it can't find META-INF/com/google/android/update-binary, which is executed "globaly" as it were, even if you don't select any of the tweakprop install options.

I hope that makes sense.

I suspect you didn't mean to do that - apologies if I'm speaking out of turn.
[Android Software Development] Lucki_X:
I have problem with recording app again with exodus 0.9.5. I suppose that it's related to implemented of Huawei libs and I'm on Honor 7. I'm back on 0.9.4 because it's better for me than 0.8.2 I used before. I had had problems with recording app with versions 0.8.3 up to 0.8.9, so it's not comfortable for me use 0.8.9 even though you have best feelings of that sound.

Thanks for your great work.

Sent from PLK-TL01H
[Android Software Development] Syk69:
I have a Nexus 6p and in the new exodus .95 tweakprop added by [MENTION=4445176]guitardedhero[/MENTION] and [MENTION=5079472]sonophilos[/MENTION] there's a new tweak line:

persist.speaker.prot.enable=true

That makes the phone speaker audio significantly lower on my Nexus 6p. Just a heads up. I just either deleted it or commented it out to get the volume back to normal for the phone speaker.
[Android Software Development] smeejaytee:
Working after this thanks

---------- Post added at 06:53 PM ---------- Previous post was at 06:49 PM ----------

I do notice that irs files are in the zip but they are not present in v4a
[Android Software Development] JellyTooth:
what version of TWRP do you have? cuz its strange i tested all possible combinations and they all worked after i edited that script.
[Android Software Development] D_black84:
[MENTION=5079472]sonophilos[/MENTION] do I need to dirty flash ROM before flashing your new tweak.prop arisen? Or can I simply replace the previous one in my SD card directory with this one then flash the zip file?
[Android Software Development] Taranis01:
To flash it over is enough, no dirty flash needed
[Android Software Development] JaylanPHNX:
Almost the whole point of tweak.prop is to be able to modify your build.prop without all that extra hassle. Just replace your tweak.prop file and flash the tweak.prop.zip.

From my SlimTab Pro 8.4
[Android Software Development] chas_43:
TWRP 3.0.0 running on an HTC M7
[Android Software Development] :
If you're coming to 0.9.5 (or back to 0.8.9) from a different version of ARISE, it is recommended that you wipe /system and /cache and dirty flash ROM before installing ARISE, to get the complete benefit of GH's updates to the sound system. If you're just adding my tweak.prop to an existing install (such as 0.8.9 -> 089rev1, or 0.9.5 default -> 095), no need to wipe - just replace the tweak.prop you had in /sdcard with the updated one and flash tweakprop.zip again. :good:

This should go without saying, but please don't flash 0.8.9 over an 0.9.x build without wipes. That can only cause problems. :eek:
[Android Software Development] JaylanPHNX:
If by this you mean there might be a way to get it to work for Oneplus One, I hope you can. I got nervous when people started talking Aroma, since they fail on Oneplus One.

From my SlimTab Pro 8.4
[Android Software Development] kyzn:
Your mileage may vary. Some have difficulties, others don't. I'm using Magisk with Arise Aroma without any problem.
[Android Software Development] n@vier:
Yes it works for me (as I wrote above AICP ROM 12.1 has Magisk built-in) but you should test to be sure because these kind of mods (like audio, root etc.) can change from device to device and/or ROM to ROM...
[Android Software Development] parmafran:
I moved away from a ROM I liked because they switched to Magisk built in. I'll give it a whirl now and see how I go. Thanks for the report!
[Android Software Development] Joloxx9:
Where did you get version which is working under magisk??
[Android Software Development] musicman5844:
Just to add viper4rise 3.5 works flawlessly with aicp even after magisk was put in on zf2 zooa not sure about any other devices
[Android Software Development] sean222:
Actually you're right I just noticed I forgot to install BusyBox and V4A is processing, so must be in the Rom or something. Battery life is great with Flash, but is built very similar to Unicornblood[emoji14]Your battery drain is probably from and app/notifications, hit up the BetterBatteryStats thread :D Also the 6P is a bit old now, can't expect the battery to hold a charge as well as it did 15 months ago :(

V4A has no noticeable extra battery drain for me :) And if there was a bit, it would be worth it!
[Android Software Development] Mystique:
[MENTION=320288]parmafran[/MENTION]
[MENTION=5664999]n@vier[/MENTION]

Using the 2.76 aroma installer and Magisk 11.1.

Viper installs but Processing always says 'No'

https://hastebin.com/ecomitidan.sql

ARISE+Deuteronomy+2.76+Modular+AROMA+Installer.zip.log.txt
[Android Software Development] n@vier:
https://www.androidfilehost.com/?fid=817550096634746597

---------- Post added at 02:34 PM ---------- Previous post was at 02:26 PM ----------

Try 2.77... the link is in the above post.
[Android Software Development] Mystique:
https://hastebin.com/ivetotilal.pas

2.77 install logs..

Processing: No

Still..

:(
[Android Software Development] Mystique:
Does yours actually show it's processing audio?

[MENTION=320288]parmafran[/MENTION] [MENTION=5664999]n@vier[/MENTION]
[Android Software Development] n@vier:
Yes it works for me with headphones and speaker both show processing audio "yes" (I tested with Spotify and Poweramp).
[Android Software Development] aojc1992:
In my One Plus One with stock Oxygen OS, don't know why all swan song version doesnt install properly

1) If I flash the zip with Aroma via latest TWRP, the recovery will hang

2) If I flash the normal modular one without Aroma, it will say flash successful. But when I boot into the OS and check the versions using Root Explorer and inside Viper4Arise. It's still the same old Deut 2.4 stable.

Someone help please, stucked at Deut 2.4 ):
[Android Software Development] Mystique:
logcat of Viper..

https://hastebin.com/urunonakab.sql

ViPER4Android: Convolver kernel does not exist

Looks to be something..

Again Magisk 11.1 and 2.77 Aroma installer..

Thanks to anyone in advance.
[Android Software Development] Roi007leaf:
Please check your system free space..Iirc OxygenOS takes ALOT of space in my op3 I had to remove some system apps in order to install ARISE (custom.roms ftw) also...Log??
[Android Software Development] Shadowghoster:
[MENTION=3009130]Mystique[/MENTION] [MENTION=5664999]n@vier[/MENTION] possible that v4a is processing on magisk since v11 because of the pseudo-enforcing selinux (which is mostly permissive (Dolby still isn't working without further changes as it seems)) Magisk now uses. The props we apply on boot should't be applied when you simply install the modular version on a magisk install (except you use SuperSu with magisk).

I've created some modules for different versions of ARISE to set the props on boot and also change selinux for v4a to work on a fully enforced selinux environment.

For those interested in trying: https://www.androidfilehost.com/?w=files&flid=153681

Regards

PS: For working Spotify processing you need ICE with config 2 or 4 installed as far as I know.

PPS: As always the module will only work with STOCK install of ARISE and all modules not requiring permissive selinux (like atmos) or additional props (like sony)
[Android Software Development] parmafran:
Just flashed Validus which now comes with Magisk, and all seems to be OK. Processing Yes. Dolby works too. (Using Flash Kernel).
[Android Software Development] n@vier:
AFAIK last update of Dolby Atmos should work with selinux enforcing and Magisk v11.1 has its own supersu so I think that Roms with magisk built-in shouldn't have problems with ARISE SwanSong v2.77 this in general.... but as I wrote above different roms and devices = different behaviours so the only way is to test and report.

Thanks for your support :good:
[Android Software Development] metrohackz:
Quick questionable as to why am3d shows effects being used but v4a logs says otherwise.

My major concern is the audio_effects. Conf structure for certain phones I see you guys have a vault of sorts for audio effects conf and I've tried every one to hope to get more than 6 effects it seems the mods that write themselves in audio effects. Conf work for me rather than replacing my whole conf.

For example when I flash b&o add on from ainur along with arkamys add on it adds to my effects total of 17 keep in mind they write themselves in as when I flash arise I go straight down to 6 effects. I have a strong feeling its to do within audio effects.conf.
[Android Software Development] JaylanPHNX:
Anyone using Android Auto? I assume viper doesn't process while using AA because the system sends the raw data to be processed wholly by the head unit.
[Android Software Development] Shadowghoster:
[MENTION=5664999]n@vier[/MENTION] can you post the output of getprop? Then we can see if the props get applied because I don't think MagiskSu (which is still based on phh su) supports su.d
[Android Software Development] gk1984:
There's too much activity going on here to keep up. Is 2.77 just compatible with Magisk (well, for the most part)? Or is it a full Magisk module? Still rocking 2.68 with the Magisk compatible zip.
[Android Software Development] EVEDork:
I have no issues with 2.74a and magisk w/ magiskSU and busybox. I was having issues w/ processing turning off, but I ran the Aroma installer and uninstalled everything except V4A core and those issues went away, so something was conflicting (I've heard it's ICE).
[Android Software Development] gk1984:
I should clarify. I'm seeing that it works. I'm just curious if it still installs to /System or /Magisk
[Android Software Development] SSNJR2002:
Hey guys here is the version 4 of my setprop. Enjoy :good:
[Android Software Development] Shadowghoster:
Yeah as you can see the props aren't applied, so we still need my module to fix those. [MENTION=3443130]gk1984[/MENTION] you still need the compatibility zip (I linked them earlier, just use the latest one).

I have a magisk modulized version here but it's not fully working because something gets messed up on magisk side as it seems. When it's all working I'll release it, but not before because too much **** must be taken care of by the user when using the modulized version.
[Android Software Development] tcat007:
Just flashed 2.77 on 6p/DU supersu 2.79. 2.5.0.5, Atmos, ice2, toolkit, permissive, deep buffer remover. All is perfect. I did try removing permissive from su.d folder, and v4a does NOT process in enforcing mode. Added file back and all is good with permissive.
[Android Software Development] sandyss18:
Getting installation error status 1 with 2.74 non magisk version.

Any suggestions
[Android Software Development] guitardedhero:
The peculiar loss of all bass frequencies or experiencing "tinny" sound is almost always corrected by deleting:

/data/data/com.arkamys.audio

Then reboot. Or you can delete app data from the ArkamysAudio App Info page if you prefer, and then reboot. :good:
[Android Software Development] phoberus:
Can't find latest version (2.77) as non-aroma zip.

Latest I can find is 2.75
[Android Software Development] rexramesh:
Can anyone confirm Am3d working in nougat update. I tried its not working in nougat, in RR 5.8.1 moto g2 titan device stock kernel. Tried flashing aroma deu 2.76 . not working am3d , anybody have work around..?
[Android Software Development] guitardedhero:
Hey metro!

Our audio_effects database contains several different, device-specific, at times, audio effects configurations that act as templates. The core system will copy the audio_effects template most appropriate for your device and rom to /system/etc, any installed modules will then add their necessary entries to that file. V4A entries are not even included by default, for example. A V4A module would need to be installed.

In order to avoid all issues presented by thr recent use of vendor partitions and images, the stock vendor audio_effects will always be deleted and replaced with a symlink of the one placed in /system/etc.

So we do a combination of both of what you're describing. It is critical that you begin with the most appropriate audio_effects template (the responsibility of our installer) and that you install any modules that you are looking for in logs or dumpsys (the responsibility of the user).

If you can include your device/rom, the final audio_effects from /system/etc, and necessary logs and dumpsys output, we'll be able to see exactly what's going on and what to do from there. :good:

Ah, very good report!

I see that the removal of permissive should seek for the presence of /system/priv-app/ViPER4Arise, which will trigger a copy operation of arisesoundserver to system/su.d.

:good:

Error 1 in recovery is ALWAYS an intended error that we have created as a result of very specific scenarios or circumstances and ALWAYS include sufficient text explaining the error and what actions to do next, if necessary. :good:

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

I'm about to provide one, I'll be improving the permissive uninstallation as tcat found and then uploading.

Edit*

Lol, there is no permissive removal or uninstallation script, so about to upload 2.77 non-AROMA. :good:
[Android Software Development] xatou:
Nexus 6p here with abc rom and ex kernel rooted with magisk. Arise 2.77 working well. I choose viper 2.5, iceconfig2 icesound pure, toolbox, remove deep buffer and permissive.

Στάλθηκε από το Nexus 6P μου χρησιμοποιώντας Tapatalk
[Android Software Development] guitardedhero:
https://www.androidfilehost.com/?fid=745425885120708449
[Android Software Development] rexramesh:
Answer my previous post plz. What should I do ? Any work around

How to flash
[Android Software Development] guitardedhero:
Very nice! :good:

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

This issue is caused by /system/lib/libaudioflinger.so, you're best chance is trying different roms that have different audioflingers. Compare the MD5 of libaudioflinger.so to what you currently have. If a ROM has an identical audioflinger, it likely will not work, for example. :good:
[Android Software Development] fischwrap:
I flashed the aroma zip on my OnePlus one, running the latest TWRP recovery. I can barely read the options! The transparent background interferes with the TWRP text in the background... Is this normal? Makes the aroma menu virtually impossible to navigate