Yeah, I think that's what makes this one so hard to fix. Google has to impose this on manufacturers as a first step. Google has some pull on the phone makers, but not that much. They mostly just licence their software (Market, Maps, etc.) and the rest is free. As you said, Apple have an advantage here because they ARE the hardware and software makers.kuniklo wrote:I've heard (I don't have hard technical evidence of this) is that it's the sound device drivers as much as anything in the kernel that's the issue. Apple has an easier time here thanks to their homogeneous hardware.polaris20 wrote: While it's true they have bigger fish to fry (notably their security issues) the low latency stuff depends on how much they've based Android off of Linux. There is a low latency kernel for Linux; Ubuntu Studio makes great use of it. But integrating that kernel into Android, on a general purpose phone? No idea how easy/difficult that is, nor if it's even possible.
I still think it'd be worth having a look at the drivers for some of the high-end phones to see if the number can't be brought down. But for all I know, someone has already tried and failed. I simply don't have the time to pursue this.
Anyway, back to improving my sequencer app