[Android Software Development] ephexxis:
its cool i assume it works since mine does, mine just has a few other changes mainly aimed at those trying to use the mod on x86 devices. some of which is reflected in my tweak.prop which is done btw

BOOOOSH

[LINK] https://drive.google.com/file/d/0B1BDd-6AxZIGTTFkWGVZYWJOVEk/view?usp=drivesdk [/LINK]

I STRONGLY URGE YOU TO OPEN AND READ ALL THE ANNOTATIONS FOR THE PROPS PRIOR TO FLASHING/ADDING TO YOUR BUILD.PROP

some of them you might want to fiddle with but the configuration I've settled on shouldn't have any issues with compatibility apart from unknown issues caused by ALSA commands directing nonexistant files since I've left them enabled.

note: I honestly have no idea if it flashes properly with the tweak.prop zip when renamed and placed in /sdcard, and i don't know what I'd change to enable that. I'm also not going to spend time on that so if it won't flash just add it the manual way using build.prop editor. better to read and understand what you're adding to your system anyways.

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

there's also a survival script installed by those dolby apps in /system/addon whatever

so you need to delete that. i realize I'm over 10 pages behind and you probably got this answers already. **** me, right? :cool:

---------- Post added at 04:14 AM ---------- Previous post was at 04:03 AM ----------

its your noisefloor then most likely. lower digital gain and try adding a flat lowpass filter (0dB) @ 23999kHz if you use neutron. if you find your volume to be too low to be enjoyable, either try a louder irs, or use a headphone amp if you have one.

[MENTION=4445176]guitardedhero[/MENTION] if alsa was still included there's a prop line you could use to directly control the gain of your onboard dac which would be useful here :p :cool:

honestly though it could just be interference introduced by the unfortunate fact that the phone's dac lives in such close proximity to other electronic components and isn't made of miraculously shielded elements. there are tons of vectors during the journey from data in your storage - > voltage driving your speakers that your ears translate into sound that can easily introduce noise. there are a few other lines in my tweak prop you might look at that i've discovered can totally negate a lot of experience ruining electronic bull**** that i'd otherwise be tolerating right now

---------- Post added at 04:23 AM ---------- Previous post was at 04:14 AM ----------

uhh did i miss something? if you made a mistake its nature certainly hasn't been Illuminated here and if it genuinely was a mistake then yeah an apology is appropriate but Jesus man i better not hear you slash your wrists or some **** over it. you're a human being and we all make mistakes. you owned it and honestly if you only just realized the mistake then given that you lacked the perspective to acknowledge it, I'm sure pdesire and crew have no issue forgiving what's been acknowledged.

there's no reason to make a mistake something that causes you a ton of grief moving forward.

ps i apologize for not PMing you this, i briefly considered it and was afraid the unreasonable state of your inbox might cause it to go unread or unanswered. mainly i just would like to know the nature of the issue, what the mistake was. you mentioned alsa files, is it that the alsa configuration was written by someone (the files themselves make no mention of anyone, i figured it was created out of the sample content available on the alsa site). seriously though man let's keep our feet on the ground here. hope you're okay