Okay, we have got this figured it out.
So here are the facts (see below listed):
Problem at iStuffs -> We are working over secure connection (HTTPS). That screwes up the iShit HTML5 audio handling. They need some "intermedia certificate" - probably for authentication or I don't know - between the server's certificate chain. So the thing is not working on our test server via SSL. Who knew... It works in when you deploy it normally. But, here comes Android, watch out!
Android is funny, since (as documented -_O ) Droid does NOT support any media formats via SSL below version 3.1. This is a complete "screwing up with humanity". I don't understand why it is such a problem to make a fcking system able to play any multi/media via fcking SECURE connection in the 21th century. This must be some copyright law sh*t again which I have to vomit again.
In case you want to know what we have done to solve this sh*t:
We figured out that if we REALLY want to make our app cross-browser and "cross-device-compatible" (I don't know if this is correct naming for it but I'm sure you get it ;) ), we need to "take out" the audio (multi/media) from under SSL.
So for the sake of simplicity we have created a simple HTTP sub-domain (separate folder in the hierarchy) for our audio files (we only need audio by now) and make it accessible through that subdomain + authenticate/validate through a script file. So everything goes under HTTPS but the multi/media is separate on HTTP.
Works fine, on every f*cking device, anytime. I know it is a "larger" solution but this is the most "implementable" for any device we are testing these things on.