[jsantell]

I'll look into more webkit browsers -- I know on my Nexus S webkit browser, it has awful performance, but the audio plays. If the webkitAudioContext/AudioContext isn't found, it falls back to the Mozilla implementation, which is an extension of the non-fancy HTML5 audio, which means it will play audio, just be unable to read the frequency data from it -- and while the glowy balls move around independent of that data, there'll just be no boom and shaking due to absence of the frequency data :)

Now to build Chromium and try on vanilla Webkit..

[HorizonXP]

That's exactly what I observe, so it likely is kicking back to the Mozilla implementation.

If you need me to test/debug, give me a shout. I'd be happy to help.

[jsantell]

Great, will let you know :) although I need to do research on when/if/how the Web Audio API is hitting mobile Webkit browsers..