yashsingh1/xdaforums huggingface dataset:
[Android Software Development] wrongway213:
You're totally fine man. This is not something we've ever addressed before and so by no means should you take that as any sort of anger or anything directed at you. You happened to be the first person to give me or anyone on the team the reason to say this. If you could please edit your original post and just remove that link that would be appreciated. Other than that, no harm, no foul:svetius: just making sure people know in the future
[Android Software Development] ahrion:
No worries. Not all phones are the same. So what might work for you doesn't work for someone else.
[Android Software Development] ecsnead69:
Did anybody notice that 7.92 broke Pulse? As anyone used 7.95 with Pulse?
[Android Software Development] crackerjack1957:
Pulse still broke in 7.95 but sound is great!
[Android Software Development] chikimonke:
Pulse is actually working for me on 7.92 on DU on my 6P. Haven't flashed 7.95 yet.
[Android Software Development] joetheshmo:
Latest weekly? My pulse is broken in the latest weekly from today. Possibly because they updated pulse to 2.0 (which was working for me on 7.92)
[Android Software Development] chikimonke:
Yup, today's weekly release.
[Android Software Development] mrrocketdog:
htc m8. slimrom 4.4.4.

ARISE™Leviticus v.RC7.95. [MENTION=5463312]smeejaytee[/MENTION] tweakprop. profile = Soundaholic by [MENTION=4260736]RSDamasceno[/MENTION] (SP). irs = Dolby Pro Logic II.irs. sounds amazing as ever. really like this one :)

(dolby has stopped working. smh). good good work team A.R.S.I.E.:highasakite:

"err on the side of kindness"
[Android Software Development] Woody:
[MENTION=5357345]ahrion[/MENTION] and [MENTION=5964313]wrongway213[/MENTION] Just an fyi, I removed the link in the quoted parts of your posts. Just wanted to let you know.

****************

As an aside, I understand that this was the first time that the team had to address "mirrors" for builds that were not working properly and causing issues. We (users) are accustomed to builds showing up without changelogs and that is perfectly fine. But if a build or even a set of builds are removed from AFH/Drive, as was the case today, there needs to be a subsequent post in here about why and asking that mirrors to prior builds not be posted.

An absent changelog is one thing, but pulling builds that I know for a fact were downloaded and flashed (pointing at myself) and were causing problems, need to be addressed with even the simplest informative post by a team member and should be expedited. Doesn't have to be a Magna Carte, but something should be posted to warn and explain.

Everyone, have a great weekend and remember, Flashing is only a crime if you have no cloths on, not in recovery.
[Android Software Development] tcat007:
Pulse has worked on every release for me. Currently 7.95. DU weekly.
[Android Software Development] wrongway213:
Apologies, Woody and everyone else. Things got a bit disorganized while fixing this issue. Builds were pulled and Ahrion had addressed the issue and told how to fix here http://xdaforums.com/showpost.php?p=67760651&postcount=9093 and two posts after that, and then Guitardedhereo provided a fix in this post hours later http://xdaforums.com/showpost.php?p=67763524&postcount=9124. A formal post addressing why builds were pulled was overlooked as those of us available were all hands on deck pinpointing the issue, but more importantly restructuring a bit so that this doesn't happen again. My sincerest apologies to anyone affected by issues today - I promise you guys, the time between builds being pulled and Ahrion addressing the issue and that fix build being posted we all made it a point to ensure builds do not go out when they should not in the future. :good: Thanks for removing the offending links, and again, apologies for not formally addressing things amid the chaos.
[Android Software Development] ahrion:
Thank you for the heads up Woody. While I'm not sure about [MENTION=4445176]guitardedhero[/MENTION]s changelogs. We just changed our uploading methods so internal build or bad builds can be deleted immediately. This will also allow auto sync, so hopefully we can get much easier changelog's pushed. Especially for us team members who don't visit the forums as much as we'd like.

I typically ask anyone who posts a link of a new Atmos version to at least mention the changes (it's typically done anyways) since it's my job to port, fix, or add any apps.

Typically Atmos is updated in my other thread before it is posted in here, which is just due to the different jobs us team members have.

I am currently in the process of building a script that backs up any file that might be replaced in the system, deletes any file that was removed from one version to the next, and allows for a SIMPLE complete uninstaller. I started it and Yoinx is helping me complete it (he kind of took the reigns in that job). The script also allows us to add files with less time in between updates. Essentially the script can be used for anyone who wants to flash something, but doesn't know how to edit files. So they could theoretically just drag and drop files and they will flash automatically for them (it sets permissions intelligently too). It's got multi-functionality.
[Android Software Development] Gunners_Classic:
A few sites ago I pretend RC 0.791 Aroma installer is all fixing for me. Yes it is but it doest survive a reboot. Than it doesn't processing. I'm able to help anyhow?
[Android Software Development] ephexxis:
delete it then reboot then carry on
[Android Software Development] yung40oz84:
It's not there anyway, but I got 7.9 aroma to work perfectly. No data corruption, and the only thing I had to do was make permissive kernel, and install user app update to Viper for IRS files to process, besides that working great. First Leviticus build that I got working, period, lol
[Android Software Development] guitardedhero:
Leviticus RC7.96​
[Android Software Development] Slypnslyde:
https://youtu.be/8khvLYW_fnM

Imagine if arise could give this sound to us for whatever earphones you have that would be amazing
[Android Software Development] tcat007:
This fixed the install issues I had with tweakprop. Thanks, 110% good.
[Android Software Development] pamplinas:
Leviticus RC 7.95 and 7.96 everything works perfect except pulse.
[Android Software Development] arcticnights:
Is pulse working for you on this build? :) You're on the latest DU weekly right?

---------- Post added at 03:05 AM ---------- Previous post was at 03:00 AM ----------

Do I have to put Selinux mode to enforcing to use this? Thanks.
[Android Software Development] Brock Guffman:
Are we LG friendly ? [emoji1]
[Android Software Development] tcat007:
Yes. Pulse working.
[Android Software Development] arcticnights:
Sorry, is the Yes to enforcing or to pulse working? ><
[Android Software Development] edyreena:
Yayy..finally leviticus version working with maxxaudio equaliser..from v1 until 7.9 all maxxaudio not working..but dolby still fc..i dont care bout that because im not using dolby..my phone suck with dolby..thxxx
[Android Software Development] nathanchance:
Well Pulse is shown in the screenshot so it is yes to Pulse working. As for enforcing versus permissive, you can test Dolby with enforcing and if you have issues with it, go to permissive.
[Android Software Development] Essentrix:
First Leviticus version to work on my S5 (Tamasek CM kltedv ROM stock kernel) correctly. Atmos didn't install initially but went into /system and installed manually with no problems and no FC! Sounds terrific...
[Android Software Development] joetheshmo:
Had to copy over the Leviticus /vendor/etc/audio_effects.conf to get Dolby to not FC and for viper to not ask to install drivers. Pulse isn't working but otherwise sounding pretty great!! Latest DU weekly.
[Android Software Development] Essentrix:
Deleted
[Android Software Development] gurneeraj:
I have managed to install RC7.92 but don't know how to install tweak.prop and what benefit it offer.
[Android Software Development] arcticnights:
Thanks! Pulse simply isn't showing up for me on the latest weekly. Not using xposed or anything, tried playing with gmmp, spotify and googleplay music... Anyone can help? :/ Thanks!

Edit: It works on googleplay music after turning the navbar on and off. Dosen't work on gmmp or spotify however.
[Android Software Development] harpin14789:
[MENTION=4445176]guitardedhero[/MENTION]

When I turn on pulse, I get this message. "visualizer tile will not work with pulse enabled" and pulse doen't work.

I flashed ARISE leviticus 7.95, could this be the cause? Currently on RR rom. It worked on past levitius builds.
[Android Software Development] colinmcg71:
[MENTION=4445176]guitardedhero[/MENTION] RC7.96 working and sounding great here.

I don't know if it's my device or a problem with the install script but since 7.5 I've had to manually copy audio_effects.conf from the Leviticus zip to /vendor/etc because it doesn't happen when flashing the zip in recovery.
[Android Software Development] johnb380:
Leviticus 7.96 working on my N6 and latest weekly DU but Pulse is definitely not working here either. Just flashed so idk about sound yet... Speaker sounds ok.
[Android Software Development] harpin14789:
I am really considering going to back to exodus ahrion special edition.
[Android Software Development] arcticnights:
Is pulse working for you on the latest weekly without ARISE? (For other music players other than google music I mean) [MENTION=3556013]johnb380[/MENTION] [MENTION=4957514]harpin14789[/MENTION]

---------- Post added at 06:18 AM ---------- Previous post was at 06:17 AM ----------

Is pulse working for you on the latest weekly without ARISE? (For other music players other than google music I mean) [MENTION=3556013]johnb380[/MENTION] [MENTION=4957514]harpin14789[/MENTION]
[Android Software Development] harpin14789:
Yes, I just moved back to exodus 1.0 ahrion special edition and pulse works again. And yes, pulse worked without ARISE installed at all.

Pulse has always used work ever since [MENTION=4445176]guitardedhero[/MENTION] fixed it in genesis .5. Now the pulse problem comes back again in Leviticus RC RC 7.96 :(, it is a sad day indeed.
[Android Software Development] arcticnights:
Hmm even on spotify? Which music player/gapps/weekly version are you on? Thanks.
[Android Software Development] harpin14789:
I currently use poweramp, banks 7/14, RR ROM shamu. Was on Leviticus RC 7.96, but went back to Exodus 1.0 ahrion special edition.
[Android Software Development] desztan:
I see that Leviticus RC RC 7.96 profile has 4 xml files, how do I use them?
[Android Software Development] arcticnights:
Hmm could you link me to banks 07/14? Can’t find it anywhere.
[Android Software Development] harpin14789:
DELETED.
[Android Software Development] jass65:
Can someone tell me what pulse is? Is it a App? Iv'e already looked through a few pages looking for an answer.This thread moves so fast!! lol

Thanks
[Android Software Development] Szabi01:
http://xdaforums.com/android/apps-games/app-pulse-music-player-t3239725
[Android Software Development] harpin14789:
It was a feature introduced by DU. There is a basically an visualizer on the navigation bar when music is playing. Like seen in the picture. Its a cool feature to have.
[Android Software Development] anandmore:
[MENTION=4445176]guitardedhero[/MENTION] [MENTION=5357345]ahrion[/MENTION] [MENTION=5463312]smeejaytee[/MENTION] [MENTION=5079472]sonophilos[/MENTION]

I can confirm pulse is broken on Levticus 7.96.

Checked on Redmi 2 running DU 10.4

Hope you fix this in next build !

The sound quality is awesome as always...
[Android Software Development] guitardedhero:
What device/rom?

I'm thrilled you're enjoying the sound system so much! Thank you for the kind words, it's always nice to see how much you guys are getting out of it! :highfive:

Actually, XPlay3S Preset is just a set of audio_effects conf files. As is the Exodus™ preset. No other files are touched :good:

Did a previous build not have that issue? I wonder if the removal of deep_buffer from audii_policy.conf is the culprit

No changes are made to /system/build.prop unless an acceptable tweak.prop is found anywhere on /storage. :good:

Did this issue start with 0.7.3? Did you use one the new tweak.props? I wonder if it's the new HTC lines.

audio_policy.conf patching has been occurring since mid-Genesis when I finally found the error causing it not to patch.

Also, I had a user with a bootloop then flash the mod without the libs in /system/lib and then add a group of ten at a time and reboot until the bad lib was found. He never bootlooped while restoring the omitted libs. Really strange. I'm thinking about taking tweakprop support our of the next update among a couple other changes which I'm betting will not yield a single bootloop report.

Thank you very much for the kind words! We are certainly proud of its state, and you guys should as well! You all have done an incredible job providing feedback and being completely honest when reviewing! :good:

Fantastic! :highfive:

So glad you got it and I'm so happy that the result was worth the frustration! :good:

I apologize for that, I didn't even think of the consequences of using the XPlay3S preset as the default set of audio_effects.conf which do not have the Sony effect entries Pulse needs. You can flash the Exodus Preset zip or just manually move those files onto /system with 0644 permissions. :good:

I wonder if it's the audio_effects change to XPlay3S. Knowing your abilities, I'd probably make your own 0.7.3 using the Exodus Preset audio_effects and taking the tweakprop section out of updater-script. You could use the runme.sh script to write any build.prop entries instead of removing deep_buffer from audio_policy.conf if you wanted to try with your sock file. :good:
[Android Software Development] :
Yes, the issue started with 0.7.3. I've been using my modified tweak.prop, and I didn't add any new lines to it with 0.7.3 besides putting the Dolby props on, which I did with 0.7.1 as well. I don't think tweak.prop is the culprit here.

What (I've done) is just copy the audio_effects and audio_policy that are working currently (which, by the way, is with the preset flashed after 0.7.1) and replace them after flashing 0.7.3 to see if that change specifically is the issue. I've also looked at the new HTC props you mentioned and adding them didn't create issues (all but htc.audio.srs.defaultbundleHS=MAX300 are present and set to those settings in my stock build.prop). :good:

Updated: did the above, working now. I'm not sure if it sounds different, I'll need to test with it some more. :good:
[Android Software Development] arcticnights:
Which IRS/profile are you using btw? :)
[Android Software Development] crackerjack1957:
I have been testing various mods today from Genesis to Exodus, the winner for me is Exodus 7.1

When 7.3 is installed, the profiles I choose do not sound right compared to the other versions, something is broken for me on HTC M8 / DU 10.2

Exodus 7.3 prop:

AUDIODRIVER=alsa

ro.sound.driver=alsa

ro.sound.alsa=snd_pcm

alsa.mixer.playback.master=Speaker

alsa.mixer.capture.master=Mic

alsa.mixer.playback.earpiece=Earpiece

alsa.mixer.capture.earpiece=Mic

alsa.mixer.playback.headset=Headset

alsa.mixer.capture.headset=Mic

alsa.mixer.playback.speaker=Speaker

alsa.mixer.capture.speaker=Mic

alsa.mixer.playback.bt.sco=BTHeadset

alsa.mixer.capture.bt.sco=BTHeadset

af.resampler.quality=255

persist.af.resampler.quality=255

persist.dev.pm.dyn_samplingrate=1

clock.allow_streaming_errors=false

default.pcm.rate_converter=samplerate_zero_order

ro.ril.enable.amr.wideband=1

use.dts_m6=true

use.dts_m6_notify=true

use.dts_eagle=true

audio.offload.pcm.16bit.enable=true

audio.offload.pcm.24bit.enable=true

audio.offload.pcm.32bit.enable=true

sony.effect.custom.sp_bundle=0x122

sony.effect.custom.caplus_hs=0x298

sony.effect.custom.caplus_sp=0x2B8

htc.audio.global.state=0

htc.audio.global.profile=0

htc.audio.q6.topology=0

htc.audio.global.speaker=1

htc.audio.srs.defaultbundleHS=MAX300

dmid=-1286820014

audio.ds1.metainfo.key=273

audio.dolby.ds2.enabled=1

audio.dolby.ds2.hardbypass=1

Exodus 7.1 prop

AUDIODRIVER=alsa

ro.sound.driver=alsa

ro.sound.alsa=snd_pcm

alsa.mixer.playback.master=Speaker

alsa.mixer.capture.master=Mic

alsa.mixer.playback.earpiece=Earpiece

alsa.mixer.capture.earpiece=Mic

alsa.mixer.playback.headset=Headset

alsa.mixer.capture.headset=Mic

alsa.mixer.playback.speaker=Speaker

alsa.mixer.capture.speaker=Mic

alsa.mixer.playback.bt.sco=BTHeadset

alsa.mixer.capture.bt.sco=BTHeadset

af.resampler.quality=8

persist.af.resampler.quality=8

persist.dev.pm.dyn_samplingrate=1

clock.allow_streaming_errors=false

default.pcm.rate_converter=samplerate_zero_order

ro.ril.enable.amr.wideband=1

ro.config.hw_dts=true

audio.dolby.ds2.enabled=1

audio.offload.pcm.24bit.enable=true

audio.offload.pcm.32bit.enable=true

sony.effect.custom.sp_bundle=0x122

sony.effect.custom.caplus_hs=0x298

sony.effect.custom.caplus_sp=0x2B8

audio.offload.multiple.enabled=true

audio.offload.gapless.enabled=true

audio.offload.passthrough=false

audio.offload.pcm.16bit.enable=true

audio.offload.track.enabled=true

ro.somc.ldac.audio.supported=true

persist.service.ldac.enable=1

com.sonymobile.ldac_enabled=true

sony.ahc.supported=yes
[Android Software Development] :
Replying to myself to follow up... having the ds2 lines removed or commented out, the headphone output works. However, adding them with a value of "1" it does not. Also, I noticed those lines are in my stock build.prop, commented out, and by default they show a value of "false", indicating that property is meant to be "true"/"false". A quick Google search for audio.dolby.ds2.hardbypass returns a census showing that several devices have this property with a value of "true". I've put an experimental switch at the bottom of my build.prop, as pictured, and set it to "false" and headphone output is working again.

:eek:
[Android Software Development] god-sta:
Am on mltirom on nexus 6..I previously was on dirty unicorn an on exodus 0.4 and it was working well edited an stuff now flash another rom rr an new version of exodus 0.7.3 an it seem to not working well I try editing an seems like nothing is taking effect an also volume seems low.. Am wondering if the tweakprop zip on the first page of the thread is the correct one or I need an updated one.. An also the new presets in the exodus folder do I need to flash them or extract somewhere ?? Help would be kind.
[Android Software Development] :
I don't use the Convolver or IRS because they are a massive battery hog and tend to introduce latency that isn't acceptable for Piano Tiles. :D

I've been building and tweaking a set of profiles called "Lover of Sound" which I might just share once I get a stable testing environment and some assistance from [MENTION=4445176]guitardedhero[/MENTION] - for some reason every time I try to upload my archived profiles the archive doesn't open for anyone but me. :eek:
[Android Software Development] arcticnights:
Ooooh okay! I am correct to assume that the enhancements will still be applied even if I leave all the options within the app off (except for turning v4a on of course)?
[Android Software Development] :
Yes. All of the audio processing enhancements in ARISE are applied globally and on by default. Turning V4A on with no settings applied won't have any effect on your sound, though. You can try [MENTION=4445176]guitardedhero[/MENTION] 's Audiophile 4.0 profile included by default if you want a good example of what's possible with V4A... or you could build and tweak your own profiles! :good:
[Android Software Development] guitardedhero:
Sorry guys for the brief appearances today. My mother came to visit from out of town but I've been actively brainstorming what's keeping Exodus from completing its task. At this point, I feel the most important component to test for reported issues is the execution of the tweakprop script.

0.7.4 has the tweakprop script execution removed from the installation script and there is now a tweakprop folder with the tools to do this manually if the user chooses to do so.

0.7.4 also has Sony Effect added to the XPlay3S audio_effects as well as its preset. I wanted to keep those files as close to stock as possible, with already adding value and Dolby, this addition is important to maintain Pulse functionality for users of roms with the Pulse visualization feature.

Those that have experienced bootloops should only attempt any tweakprop or build.prop actions after confirming the sound system successfully flashed and all seems to be working properly.

Dirty flash should be fine if on 0.7.3.

ARISE Sound Systems™ 0.7.4​
[Android Software Development] :
Confirmed, dirty flash over 0.7.3 was fine, no issues. Thanks! :highfive:
[Android Software Development] arcticnights:
If I'm on 0.73 without the Xplay3 Preset (which is included by default right?), do I have to flash the Xplay3 preset zip again after dirty flashing 0.74? Since there have been changes to the Xplay3 audio effects? Thanks man.
[Android Software Development] :
Presenting...

Sonophilos (Lover of Sound) Profiles ARISEN

Lock Effect Mode - Headset (so Speakers/Bluetooth get all ViPER options) - I use separate profiles for Headphones and Speakers rather than the separate tabs. The Lover of Sound profiles include both preset as described below.

UI Setting - Expert (so you can see all these settings)

Sonophilos-Headphones:
PlaybackAGC - Enabled, Slight / 3x Max Gain / -3.0Db Max Output
ViPER-DDC - Enabled, audio-technica ATH-M50 (set this to your headset after first install, then save over Headphones profile)
Spectrum Expansion - disabled
FiREqualizer - (0.0, -0.6, -1.2, -1.8, -2.4, -3.0, -2.1, -1.3, -0.6, 0.0) disabled by default
Convolver - disabled
Field Surround - disabled
Differential Surround - disabled
Headphone Surround + Enabled, Level 1
Reverb - disabled
Dynamic System - enabled / Extreme Headphone (v2) / 12%
^You may want to set this to Common Headphone (v2) or if you have one of the specific models listed use that preset
ViPER Bass - Enabled / Natural / 40Hz / 6.0Db
ViPER Clarity - Enabled / Natural / 6.0Db
Cure Tech+ Enabled, Slight
Output Gain (-6.0Db) / Channel Pan 0.5:0.5 / Limit Threshold (-3.0Db)

Sonophilos-Speakers:
PlaybackAGC - Enabled, Slight / 3x Max Gain / -3.0Db Max Output
ViPER-DDC - disabled
Spectrum Expansion - disabled
FiREqualizer - (0.0, -0.6, -1.2, -1.8, -2.4, -3.0, -2.1, -1.3, -0.6, 0.0)
disabled by default
Convolver - disabled
Field Surround - disabled
Differential Surround - disabled
Headphone Surround + disabled
Reverb - disabled
Dynamic System - disabled
ViPER Bass - Enabled / Natural / 40Hz / 6.0Db
ViPER Clarity - Enabled / Natural / 6.0Db
Cure Tech+ disabled
Output Gain 0Db / Channel Pan 0.5:0.5 / Limit Threshold (-3.0Db)
[Android Software Development] :
Upload, sorry. For some reason pasting that large block of code hid the upload button on Labs.

Extract and place Sonophilos-Speakers and Sonophilos-Headphones in your Profiles folder (check OP if you're not sure where to find yours), make sure V4A has Storage permissions, reboot might be necessary. Enjoy! [MENTION=5475952]arcticnights[/MENTION] since you asked :good:
[Android Software Development] desirexel:
Thanks.. ;)
[Android Software Development] guitardedhero:
Great job! Perfect extractable zip! And thanks for the report on the Dolby lines. Those were killed from the HTC 10 system I sourced and I did see another HTC build.prop that only had the two lines dealing with device verification so I'll do that next. :good:
[Android Software Development] :
Woot! Root Explorer did the trick. Thanks! :good:

EDIT: so if I understand correctly, the Dolby DS2 lines are no longer applicable on 0.7.4? I have the verification lines and they're identical on my "stock" build.prop, and the DS2 lines are there but "false" and also commented out by default.

Hope this helps. :good:
[Android Software Development] arcticnights:
Woo thanks dude! Really excited to test it.

If I'm on 0.73 without the Xplay3 Preset (which is included by default right?), do I have to flash the Xplay3 preset zip again after dirty flashing 0.74? Since there have been changes to the Xplay3 audio effects? Thanks :p