szantog
Marshmallow improves audio latency here and there on some devices, but even Android N has the fundamental audio stack problems we mention in the articles.
There is no Android version delivering <= 10 ms round-trip audio latency.
Audio can be handled by built-in hardware or external (USB) hardware.
External: Android is not able to deliver glitch-free low latency audio on USB devices. We introduced a solution for this last month, that's one of the links on the top of the article. It opens up a market of 1.1 billion devices (meaning, Android 4.4.4 and up) for USB audio on Android.
Built-in: The current article introduces a demo solution for the built-in audio hardware.
Those are two separate things:
1. Updated analysis on the latency with regards to Marshmallow.
2. Superpowered USB Audio and MIDI SDK opens a market of 1.1 billion devices.
Using a "pull" method is required for low latency audio, where the audio driver's interrupts are scheduling when audio is passed to and pulled from applications.
Another downside of halving the period size is CPU load/battery drain. There are simply too many layers in Android's audio stack, and it has quite a few unoptimised code as well (such as converting between audio sample formats with plain C code).
Android's media architecture with it's "push" design is not more compatible than anything else with a "pull". The many layers doesn't add any flexibility, they are "only" the result of many years hacking.