Well, the reason why I am trying to have libsvm.so build with the same functionality as what is distributed by you in .deb, is because I want to try to speedup/optimize the whole thing a bit. An example - in your early builds cvm memory allocation with Opera was about 12% (as shown in top) while in later it is 20% and more. Also Opera scrolling was silk smooth in those earlier builds, while there is a lot of stutter in later. Your builds does not use arm7l and SGX features, which I am familiar with. What I saw in cvm Qt sources is a memory inefficiency I am sure I can get rid of (framebuffer is memcpy'ed to a new buffer, which is then used for QImage, which is then used for QPixmap, and that QPixmap is rotated 270 deg when in portrait). And so on, and so on. But I need a working build tree, to be able to play with different options so at the end of a day a simple benchmark could prove is it faster or slower. Re location API - I don't think using Qt mobility is the best solution for n900, Qt is a memory hungry animal. There are better solutions AFAIK: http://wiki.maemo.org/Documentation/...ng_liblocation I think I can help a lot on that side, we can just agree on the interface you need, and I will implement it in a .so file, so you won't need scratchbox or anything to use native Maemo5 GPS support. The same is with multimedia support, but lets leave that for now. I would really appreciate if you could give me some hints on how to workaround missing parts that prevent me from having the fully functional libsvm.so build (to the point your build is functional, of course)