![]() I thought I’d post the info now because I seem to have got it to build, and well, there’s more than enough info here for a blog post. I havn’t built Qt Creator (the GUI IDE that Necessitas now offers) and nothing is running on my device yet - that’s a matter for more research. So far I’ve only got the libraries to compile. This post documents the steps I took to get the Necessitas Qt framework to compile with Cygwin and the official Android NDK r5b (the latest version as of this writing). Those links are still super helpful, but some things have changed since then - Necessitas has undergone significant structural change, and Google have released a new Android NDK r5b. Last year I managed to get it to build on Windows by following the instructions at android-lighthouse google code ticket 11 and this very helpful post by Damien Buhl (in French, Chrome will translate it for you). It’s a port of the Qt GUI framework to Android. I’ve been following the Necessitas project (formerly “Android Lighthouse”) for a while now. On YouTube as “Google I/O 2011: Fireside Chat with the Android Team” at 40:24 Google I/O 2011, “Fireside Chat with the Android Team” May 10, 02:30PM – 03:30PM Obviously it’s not going to solve the problems for legacy devices but it’s going to get better.”ĭave Sparks - Technical lead for the Android media framework. But it’s a problem we want to deal with and hopefully the next release will get it. That’s probably the biggest issue we’re running into right now. ![]() Because the fair scheduler makes it really difficult to make sure that these low latency audio threads get scheduled when we need them to be scheduled every single time. ![]() There are some interesting problems we need to solve in the scheduler, so I’ll be talking to Rebecca shortly about this. We started/ I think we introduced something in CDD Gingerbread which was a “should” hit certain latencies. So, that’s something we’re going to push on. Basically it’s happening in the drivers or in the chipsets or somewhere in there, and some of these are really obscene amounts like hundreds of milliseconds of latency in the audio path. Most of the latency is introduced below Android. There are a number of different places where latency gets introduced. As we investigated it it’s actually a pretty complex problem. We’re working at, hopefully we hope to be able to do something about it with ICS. In response to “There are questions about audio latency being a problem for Android, are you seeing this Dave?” Dave Sparks said: Over on the Andraudio list Robert Munro kindly pointed out that there was a question about the sad state of audio latency on Android at the Google I/O 2011 “Fireside Chat with the Android Team.” The question is at 40:24 in the video: This is old news but I just heard about it and thought it was worth posting for future reference.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |