[Android Software Development] ephexxis:
you sound exactly like me. you SHOULD get worked up over the DAC (speaking of this, why did [MENTION=4445176]guitardedhero[/MENTION] or [MENTION=6449207]Roi007leaf[/MENTION] not alert me to this guys post! I'M THE DAC GUY FOR HIS NOODLINESS' SAKE JEEZ WAY TO DROP THE BALL ON THAT ONE), and you should want to find a way to solve this as you're one of MANY people who smartly picked up an external dac which makes a vast difference in sq when utilized properly. one of the reasons I've taken an interest is because i myself use a CreativeLabs portable soundblaster E3 in line to my cars audio system. considering i picked it up at frys on sale for around 65 USD after tax , I'd say it's been hands down the best irresponsible impulse purchase I've ever made in my life, and until a few weeks ago I'd seldom even utilized the dac, opting instead to just go phone > e3 via analog (using my phone dac and the e3 as essentially just an additional, adjustable amp in line with my bose system. just having the amp itself is a huge value that i hadn't even considered when i purchased it.

however lately I've had difficulty getting android to recognize it over usb (which is weird because ive definitely had it working a long time ago but ultimately chose the analog way due to having to use my phone heavily for both my jobs and have a hard time getting to all the things i have on my plate as it is, plus there is the obvious power issue (dont really want to use my dac in 1-2 hour increments punctuated by 1-2 hour charging sessions, i simply will not settle for that). almost every day i try a new configuration of combinations of otg adapters, different types of usb cables etc with no real success, though with each failure ive learned more and more. lately I've been using the surprisingly excellent quality bluetooth connection with this miraculous creative product (can't praise them enough, they've really upped their game from the days of just a notch above logitech quality desktop speakers that plagued them years back) and even though I'm still uncertain of my utilizing aptx (which both the e3 and e5 have the hardware for, and the source typically needs only the codec and i guess configuration to tell it to use aptx over vanilla sbc), as there is no user facing playback information that i can find indicating even what protocol is in use apart from a2dp (which is obvious, it would have to to do digital audio streams) the quality compared to just using the aux 3.5 TRS i/o is astonishing even with more than double the minimum latency. this has merely driven my motivation (into an obsession really) to find a solution to androids currently problematic and neglected implementation of digital usb out which i can go into more detail about later.

for reference/transparency/self-deprecating humor i will detail the money I've sunk into this thusfar:

- microusb male otg > usb type A female adapter for phone. ~4USD.

- USB 3.0 SS(superspeed) type A male> USB 3.0 SS type A male cable. ~10USD

- first USB (2.0)hub. Bus powered (draws power from an integrated usb cable}. turns out these are really meant for use with computers as the host, and in no other configuration. ~15USD

- USB 3.0 SS type A male > micro USB 3.0 SS male. ~18USD

- Micro USB 2.0 > USB2.0 type A male/female 3 way cable. This thing is actually still pretty cool, essentially a standard (flat which is nice) charging cable only the USBA side has a type A port attached to the plug, allowing another type A to be attached meaning you can charge 2 devices from 1 usba port on a charger. unfortunately effectively breaks otg as i learned. ~14 USD.

- SECOND (USB 3.0) USB hub. AC powered in addition to bus power provided by the host if necessary. Advertised as OTG compliant (driverless meaning it should work with a smartphone host). comes with a sweet, heavily shielded and sturdy USB3.1 SS type A male > USB3.1 microusb type B otg compliant cable. this special cable is ultimately what i think makes the usb hub "otg compliant" which sucks for me because the fact that the b side of the cable (otg cables soa lettermetimes conveniently stamp one end with A or B to indicate that the stamped side has an id pin that will announce whatever is connected to that side as either a device (slave) or host (master) which establishes the otg relationship with the phone)) is micro usb3.1 type b means thethe only device i can plug that side into its the hub itself, and that also means I'd need an adapter again anyways because my phone has no full sized USB port for the "host" end. i can charge both my phone and my dac (and in theory 2 additional devices, it's a 4 port hub), however this requires to give up the 1 AC plug i have available that i normally have my Boost master AC qc 2.0 charging block by ASUS plugged into. fail. ~26 USD

-non USB compliant, USB type A female > microUSB OTG male "y" cable with a USB Type A male offshoot that supplies power from a charger. I've put off this seemingly obvious solution till now because its technically not supposed to exist, and violates the USB stabdards guidelines. this is the next purchase though. may order it today to an Amazon locker nearby. ~15USD w/shipping.

The **** i do for you guys

---------- Post added at 12:10 PM ---------- Previous post was at 12:08 PM ----------

more and more dnb heads coming out of the woodwork. more encouragement and motivation to continue cracking out sick modificationes for you lot. join us on tg sometime friend, i know i can find some stuff around here that you'll enjoy ;) :good:

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

all kernels allow selinux to be permissive. it's merely a matter of setting it to be permissive which can be done vis terminal, through a script that runs on boot automatically (better) or ideally simply set in your thoughtful rom developers added toggle within developer options in settings (best).