Argh, this smells like the audio latency issue. An issue with 500 comments pleading Google to do something about it for 4 years. Ladies and gentlemen, I give you issue #3434:
This is one of the issues keeping Android from being an excellent platform for music applications. Coupled with the general hackability of Android devices (Accessory Development Kit, etc.), it could be an amazing platform for digital audio workstations, synthesizers, samplers, and audio effects processing.
iOS is better in this regard, but still not perfect. Audio routing between applications is a dicey affair (done through a 3rd party app that runs in the background), and it's not possible to charge while using USB accessories, like audio interfaces or MIDI keyboards.
Yep. Say what you will about Apple products, but it's no coincidence that professional audio applications are so much more prevalent on Apple products. Core Audio is a fantastic base for developers to work with.
I have a Nexus 10. It crashes about once a week restarting the gui (adb restore backup does so too). Playing audio via Bluetooth is choppy if the device hasn't been rebooted for a few days. It feels like several years ago when I had a Blackberry (no data service though) and a poll question was "which app do you use to daily reboot your phone?" I'm on the verge of writing one for Android.
https://code.google.com/p/android/issues/detail?id=3434
There has been some improvement lately but it is hard to find devices that support the "special" low latency mode.
This sounds like a similar thing. Just pointing out the level or response and engagement you'd expect from Google (hint: almost none).