TOPIC:

About third part dev tools: our main focus is to give support to official development tools, that's why we put both Xamarin and B4A interfaces on open source.
We should take both xamarin and B4A interfaces up to date, but we don't give assurance about that.
Your team should adopt that code as basis to build their own development.

Hi,
to make the project smaller you can check the libs folder and delete the ".so" object of the device you don't support (be careful).
If you want to support all the device, you need to bring all the ".so" object in the jar.

Many thanks.
I think I bring all .so
AFAYK, where I could give the table with link from device to lib?

Hi,
what do you mean for "the table with link from device to lib"?

type of processor ---> file SO used (should be folder name?)
...
I mean a table (or something uman-readable, or something I can log in my program with a call)
SAMSUNG G8000 ---> type of processor
SAMSUNG N5200 ---> type of processor

So I can know what SO link to what physical device.

Sorry, we do not have such an info..
The android market is so wide..and it's not easy to keep track of these kind of information..
If your app should be compatible with almost all the android devices .. then you need to keep all .so files
But for example: you can delete "x86" and "mips" in libs dir, if you never run on x86 and mips devices.
The same for 64bit arch