New Posts  All Forums:

Posts by Raenmor

Downsampling is an android "feature" for compatibility. It resamples every stream to 48/16 to work on every, even the cheapest DACs. It's not kernel related (well, partially), but mainly OS limitation, so bypassing this requires either heavy modifications to android sound logic, especially if you want bit perfect output. There is bunch of audio layers, such as mixer, dsp effects and so on. Global bypass is painful, but can be done relatively easy by using player, that...
There is nothing wrong with newbie questions, as long as you really want to learn something  And before I start - it's impossible to ruin your system with linux deploy (probably you can, but you have to do it on purpose, and even then you will probably fail to do so)   Ok, now let's start 1)Run linux deploy, go into your profile and run menu-status. Look for the line "Support loop device", if it says "yes", then you can install linux into .img file, if no, you have to do...
OK, I'll start from theory - on of android sound problems is its own sound layer. So every sound you play goes like this: music player --> android layer --> alsa --> dac --> speaker. Android layer can't pass stream higher than 48/16, so it will downsample anything above (and usually upsample 44.1/16 music as well). After that alsa is coming into play, but default alsa configuration on android includes upsampling as well. So even if your dac is working on android it...
Just a small update on my situation: bit-perfect playback on android without audiorecorderpro is possible.   I was able to run mpd on debian, running on top of android. So this way my audio stream goes directly to alsa (and my dac), bypassing any interference on android side (upsampling/downsampling and bunch of various effect). And I can simply control it with MPDroid app.   If anyone is interested I can try to explain it, but it requires root and a bit of luck ;)
Honestly i have no idea. Probably you can configure alsa through terminal, but it's much easier to use notepad++ or something like this to edit asound.conf. As for the audio_policy - I highly doubt that there is any way to do it through terminal.2All: Does anyone here is (or knows) any decent developer that can activate alsa output in aMPD found earlier? There are sources available including ported alsa_output module, but unfortunately straightforward approach didn't work,...
That's great! But now we have to convince the developer to include alsa output module, and we are good to go for bit-perfect audio output from android.
Now I want to try to run MPD server on android somehow, to bypass any interference from the os itself and communicate directly with alsa. Controlling it would be easy, there are tons of MPD Clients on android.But until then you can try to use XBMC, it supposed to communicate with alsa directly as well.EDIT: XBMC is no-go, at least for now. Alsa support isn't working properly. At least I can't get it to work. If someone else can - please share.
Hi all,   I was able to use FiiO E07K with HTC One X running CyanogenMod without using AuidoRecorderPro, or any other third-party applications. And it is running 96/24 as well. It involved a little bit of programming, but nothing too hard. If you're interested - check the thread at xda (http://forum.xda-developers.com/showthread.php?t=2305631), 'cause copying the instruction here will be messy.   Hope it will help at least some one 
New Posts  All Forums: