I bet you don't use the NDK then.
- Gradle still doesn't provide half of the functionality of the ndk-build scripts
- Studio still not up to what Eclipse CDT provided
- We NDK users were left dry while they figure out how to provide proper support
For both NDK and SDK, lots of bugs to choose from:
https://code.google.com/p/android/issues/list
Then going back to the SDK, any professional Android developer can enumerate lots of issues when you need to get information.
Also I am yet to see a release of the support library that isn't followed by complaints in G+.
So what are those Google experts doing?
I like Java a lot, but C++ is the current kind of portability across mobile OS for native applications, as common language across SDKs.
If I would be doing this commercially, I would have gone Xamarin already.
Yeah, it's stunning how impossible it is in 2016 to profile native code on Android with Google tools. Meanwhile, Apple has had arguably the best CPU profiler available anywhere on any platform (Instruments.app) for years and years.
NVIDIA has done an incredible job making this basic functionality work on their Android systems…yet, sadly, their work doesn't extend to all Android platforms.