Linked by Thom Holwerda on Thu 7th Jun 2012 16:40 UTC
PDAs, Cellphones, Wireless Exactly six months ago, Eric Schmidt made a remark that in the near future, developers might want to focus on Android first, instead of iOS. While developers haven't moved to Android-first, iOS-later en masse, there's no denying that we're seeing more and more former iOS exclusives move towards Android.
Thread beginning with comment 521219
To read all comments associated with this story, please click here.
Some problems with Android and SDK
by twitterfire on Thu 7th Jun 2012 18:26 UTC
twitterfire
Member since:
2008-09-11

Sometimes developers can't code for Android because either the OS has some broken part, some bits are missing or SDK has some broken parts.

As an amateur guitarist I would like to use my Android phone or tablet to emulate a guitar amplifier like it's possible using popular iOS app, iRig. Unfortunately, audio related apps can't be ported over to Android due to high latency issues and a lack of low latency audio api. This affects not only music software but to a lesser extent voip, too.

Video latency is also an issue, sometimes the interface is laggy compared to iOS. The shitty Java based SDK doesn't help improving performance. Extending the NDK, to be capable of handling everything the SDK can, would be a great improvement.

Reply Score: 2

shmerl Member since:
2010-06-08

You can make ALSA work with low latency. And then use something like Nemo or Plasma Active distros (with Mer Linux). They are way more flexible than either Android or iOS.

Edited 2012-06-07 18:37 UTC

Reply Parent Score: 1

phti Member since:
2012-06-02

yeah, like "I want to play guitar fx with my android phone" answer: "easy, just install another operating system on it, then learn to program, learn how to fiddle with a low latency audio driver, make an audio virtual fx app from scratch, and in just a couple of years you're done!" looks amazing! #fail

Reply Parent Score: 4

Radio Member since:
2009-06-20

I keep hearing about how developpers of music apps never even give a look at Android because of "latency issues" - but excuse me, I am completely clueless, what is it exactly? I never had any problem playing audio files, streams or fiddling with the few audio generators for android.

So, what is it? A urban legend, or something for which someone can provide a real, practical proof to show me?

Reply Parent Score: 5

gan17 Member since:
2008-06-03

Simple demo:
http://www.youtube.com/watch?v=Curn_fdMOBA

As for personal experience; try getting one of those piano apps and swipe your finger across the keys. That's basically the problem. It's not really a problem with Honeycomb/Gingerbread or prior version either. I've experienced on ICS with my Galaxy Nexus.

Google says it's an issue with the hardware. Hardware makers say it's an issue with Android. I'm guessing it's more probably the latter.

Edited 2012-06-07 19:43 UTC

Reply Parent Score: 2

dsmogor Member since:
2005-09-01

I second that, audio/input latency seems to be a sore point in Android atm, is ICS anywhere better it this regard? Too bad as Linux and Alsa have given Google great basis for fixing that.

Reply Parent Score: 2